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:
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.
Official product page:
https://pacage.it/pac-product/
Technical documentation:
https://pacage.it/pac-product-documentation
The product page provides an overview of PAC Products Bridge and its editions. The documentation page contains installation, configuration, payload, FileMaker-side and troubleshooting information.
PAC Products Bridge reacts when supported product information changes in WooCommerce and immediately calls FileMaker through the FileMaker Data API.
Typical workflow:
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.
The Free edition provides a complete real-time notification workflow for WooCommerce products and variations.
You configure:
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.
PAC Products Bridge Free supports:
product.createdproduct.updatedproduct.deletedvariation.createdvariation.updatedvariation.deletedProducts and variations are identified by their WooCommerce IDs.
PAC Products Bridge Professional extends the real-time workflow with additional event types, delivery options and payload modes.
Professional adds support for:
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:
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 is designed to support different FileMaker integration strategies.
The Professional settings page provides one Script parameter menu with these four choices:
Event + WooCommerce ID sends the compact event|ID value, such as product.updated|123.Basic product JSON sends a compact JSON object with the event, WooCommerce ID, product identity, prices and stock fields.Custom template sends the value generated from the configured template and its placeholders.Full WooCommerce JSON sends the complete locally available WooCommerce REST product or variation representation, plus pac_bridge_event.The Parameter template field is used by the Custom template choice. The full JSON choice does not embed image files; it includes image metadata and URLs when WooCommerce provides them.
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.
Professional can distinguish product lifecycle events from stock and price changes.
This allows FileMaker workflows to react specifically to operational changes such as:
A FileMaker solution can therefore use different scripts or script logic for catalog synchronization, stock management and price management.
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.
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:
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.
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:
With the Professional full JSON option, FileMaker can instead parse the product data directly from the received JSON parameter.
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:
FileMaker can therefore maintain separate records for parent products and variations if that matches your data model.
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.
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.
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.