PAC Products Bridge for WooCommerce

Beskrivelse

PAC Products Bridge for WooCommerce is a real-time WooCommerce FileMaker integration that connects product and variation changes to Claris FileMaker Server through the FileMaker Data API.

Instead of polling WooCommerce with cron jobs, scheduled imports or repeated API requests, the plugin notifies FileMaker when supported product events occur.

The Free edition supports real-time lifecycle events for:

• WooCommerce products
• WooCommerce product variations
• Product creation
• Product updates
• Product deletion
• Variation creation
• Variation updates
• Variation deletion

A single FileMaker script receives the event name together with the WooCommerce object ID.

Examples:

product.created|123

product.updated|123

variation.created|456

variation.deleted|456

This gives you a direct WooCommerce to FileMaker bridge without polling, middleware or an external synchronization service.

Real-time WooCommerce to FileMaker integration

PAC Products Bridge reacts when supported product information changes in WooCommerce and immediately calls FileMaker through the FileMaker Data API.

Typical workflow:

1. A WooCommerce product or variation is created, updated or deleted.
2. PAC Products Bridge opens a FileMaker Data API session.
3. The configured FileMaker script is executed.
4. The WooCommerce event and object ID are passed to FileMaker.
5. FileMaker performs your own synchronization or business logic.
6. The Data API session is closed.

The FileMaker-side logic remains entirely under your control.

Your FileMaker script can create records, update existing records, archive deleted products, launch additional scripts, perform searches, maintain related data or call the WooCommerce REST API when additional product information is required.

Free edition

The Free edition provides a complete real-time notification workflow for WooCommerce products and variations.

You configure:

• FileMaker Server
• FileMaker database
• Layout
• Script
• FileMaker account

When a supported event occurs, the configured FileMaker script receives a compact script.param value using the following format:

event|ID

Examples:

product.created|123

product.updated|123

product.deleted|123

variation.created|456

variation.updated|456

variation.deleted|456

This lightweight format is useful when FileMaker only needs to know what changed and which WooCommerce object is involved.

Your FileMaker script can then decide whether to create, update, delete, archive or retrieve additional data for that object.

Supported Free events

PAC Products Bridge Free supports:

• product.created
• product.updated
• product.deleted
• variation.created
• variation.updated
• variation.deleted

Products and variations are identified by their WooCommerce IDs.

Professional edition

PAC Products Bridge Professional extends the real-time workflow with additional event types, delivery options and payload modes.

Professional adds support for:

• Product stock changes
• Variation stock changes
• Product price changes
• Variation price changes
• Background delivery using WooCommerce Action Scheduler
• Automatic retries after failed deliveries
• Manual resend tools
• Custom payload modes
• Full locally available WooCommerce product or variation JSON
• Custom HTTPS certificate verification
• Custom CA certificate support
• Advanced diagnostics

Full WooCommerce product JSON

Professional can send the complete product or variation data already available inside WooCommerce directly to FileMaker as the FileMaker script parameter.

This allows FileMaker to receive product information in the same transaction without making a second request back to WooCommerce.

Depending on the WooCommerce object, the JSON can include information such as:

• Product or variation ID
• Name
• Slug
• Status
• SKU
• Product type
• Prices
• Stock information
• Dimensions
• Tax settings
• Descriptions
• Images and image URLs
• Categories
• Attributes
• Variation data
• Other product information exposed by WooCommerce

The payload is prepared locally from WooCommerce data. PAC Products Bridge does not need to make an outbound WooCommerce REST API request just to build this payload.

This can significantly simplify FileMaker-side synchronization because the FileMaker script can create or update the product directly from the received JSON.

Professional payload modes

Professional is designed to support different FileMaker integration strategies.

Depending on configuration, the script parameter can use a compact event-and-ID payload or a richer JSON payload.

A compact event parameter is useful when FileMaker already has its own WooCommerce retrieval logic.

A full JSON payload is useful when you want WooCommerce to push the available product data directly to FileMaker.

This keeps the FileMaker architecture flexible and allows the same bridge to be used with simple notification workflows or more complete synchronization processes.

Stock and price events

Professional can distinguish product lifecycle events from stock and price changes.

This allows FileMaker workflows to react specifically to operational changes such as:

• Stock quantity updates
• Stock status changes
• Regular price changes
• Sale price changes
• Variation stock changes
• Variation price changes

A FileMaker solution can therefore use different scripts or script logic for catalog synchronization, stock management and price management.

Background delivery and retries

Professional can use WooCommerce Action Scheduler for background delivery.

This is useful when you do not want the FileMaker request to remain part of the interactive WooCommerce request that triggered the event.

If a delivery fails, Professional can retry according to the configured delivery workflow.

This makes the integration more resilient when FileMaker Server is temporarily unavailable or when a network problem interrupts the initial request.

Why use PAC Products Bridge?

Many WooCommerce and FileMaker integrations rely on scheduled polling.

That means FileMaker or another process repeatedly asks WooCommerce:

«Has anything changed?»

PAC Products Bridge works in the opposite direction.

WooCommerce notifies FileMaker when the change happens.

Benefits include:

• No cron-based polling for product changes
• No repeated searches for recently modified products
• No middleware required
• Immediate FileMaker script execution
• Lower synchronization latency
• Reduced unnecessary API traffic
• FileMaker business logic remains under your control
• Optional full product JSON in Professional
• Dedicated stock and price events in Professional

FileMaker Data API

Communication with FileMaker Server uses the standard FileMaker Data API over HTTPS.

The plugin authenticates using the configured FileMaker account and executes the selected FileMaker script using the configured database and layout.

No FileMaker plug-in or external middleware component is required.

PAC Products Bridge does not write directly to FileMaker tables.

It calls the FileMaker script you configure, and your FileMaker solution decides what happens next.

FileMaker-side workflow

A simple FileMaker script can inspect the received parameter and branch according to the event.

For example:

product.updated|123

can tell FileMaker that WooCommerce product ID 123 has changed.

The FileMaker script can then:

• Locate the corresponding FileMaker record
• Retrieve the current WooCommerce data if required
• Update selected fields
• Synchronize related records
• Recalculate business data
• Trigger another FileMaker script

With the Professional full JSON option, FileMaker can instead parse the product data directly from the received JSON parameter.

Products and variations

PAC Products Bridge treats products and variations as separate WooCommerce objects.

This is important because a variation has its own WooCommerce ID and may have its own:

• SKU
• Price
• Stock quantity
• Stock status
• Dimensions
• Attribute selections
• Image

FileMaker can therefore maintain separate records for parent products and variations if that matches your data model.

What PAC Products Bridge does not replace

PAC Products Bridge is focused on product and variation events.

WooCommerce taxonomy synchronization is handled separately by PAC Taxonomy Bridge for WooCommerce.

Order synchronization is handled separately by PAC Order Bridge for WooCommerce.

Keeping these workflows separate allows each bridge to remain focused and lets FileMaker solutions use only the integrations they actually need.

Requirements

• WordPress 6.4 or later
• WooCommerce
• PHP 7.4 or later
• Claris FileMaker Server with the FileMaker Data API enabled
• HTTPS connectivity between WordPress and FileMaker Server
• A FileMaker account with access to the configured database, layout and script

Related PAC integrations

PAC Products Bridge is part of the PAC family of real-time WooCommerce to FileMaker integrations.

PAC Order Bridge for WooCommerce can notify FileMaker when WooCommerce orders are paid.

PAC Taxonomy Bridge for WooCommerce can notify FileMaker when product categories, global attributes and attribute values change.

The three bridges can be used independently or together, depending on the FileMaker solution.

Trademark Notice

PAC Products Bridge for WooCommerce is an independent product and is not affiliated with, endorsed by, or sponsored by Claris International Inc. or Automattic Inc.

Claris and FileMaker are trademarks of Claris International Inc.

WooCommerce is a trademark of Automattic Inc.