PAC SOFTWARE DOCS
PAC Products Bridge for WooCommerce
Technical documentation for real-time WooCommerce product and variation notifications to Claris FileMaker through the FileMaker Data API.
Version 1.0.0 • Updated Sep 2026
WooCommerce product event
PAC Products Bridge
FileMaker Data API
FileMaker script
1. Overview
Connect WooCommerce product and variation changes to FileMaker in real time.
PAC Products Bridge for WooCommerce is a WordPress plugin that connects WooCommerce product and variation events to Claris FileMaker Server through the FileMaker Data API.
Whenever a supported product or variation event occurs in WooCommerce, the plugin calls a FileMaker script in real time and passes information about the affected WooCommerce object. Product creation, product updates, product deletion, variation creation, variation updates and variation deletion are supported in the Free edition.
The integration is event-driven: WooCommerce notifies FileMaker when a product or variation changes. No scheduled polling, middleware or external synchronization platform is required. Your FileMaker solution remains responsible for interpreting the received parameter, retrieving any additional data needed by your workflow and applying your own synchronization or business logic.
Professional adds production-oriented options such as stock and price events, background delivery, automatic retries, manual resend tools, custom payload modes, full locally available WooCommerce JSON, certificate options and advanced diagnostics.
Real-time product changes, under your control.
PAC Products Bridge tells FileMaker what changed as soon as WooCommerce fires a supported product or variation event, while all processing logic remains inside your FileMaker solution.
2. Key benefits
Real-time notifications
FileMaker is notified immediately when supported product or variation data changes in WooCommerce.
Products and variations
Handle parent products and individual variations as separate WooCommerce objects, each with its own ID.
Your business logic
Use your own FileMaker scripts to retrieve data, update records, archive deleted items and launch downstream workflows.
Direct integration
Connect WooCommerce directly to the FileMaker Data API without polling or third-party middleware.
3. How it Works
PAC Products Bridge listens for supported WooCommerce product events and executes the configured FileMaker script.
WooCommerce
A supported product or variation event occurs
PAC Products Bridge
Builds the script parameter for the configured payload mode
FileMaker Data API
Opens a session and executes the script
FileMaker script
Applies your catalog synchronization or business logic
- A WooCommerce product or variation is created, updated or deleted.
- PAC Products Bridge identifies the affected object and the event type.
- The plugin opens a FileMaker Data API session and executes the configured script.
- In the Free edition, the script receives a compact event|ID value through script.param.
- In Professional, the script can receive a compact event parameter or a richer payload such as locally available WooCommerce product or variation JSON, depending on configuration.
- Your FileMaker script interprets the parameter, retrieves or parses any additional data required by your workflow and updates your solution.
- The plugin records the result and closes the FileMaker Data API session.
You remain in control.
PAC Products Bridge notifies FileMaker and starts your script. It does not impose a FileMaker schema or modify FileMaker records directly.
4. Requirements
To use PAC Products Bridge for WooCommerce, you need the following components:
WordPress (supported and up to date)
Data API enabled on your FileMaker Server
HTTPS-enabled website
productsClaris FileMaker Server or a compatible FileMaker Data API endpoint
WooCommerce (supported and up to date)
Reachable host and valid credentials (for example, a dedicated account)
A target script and layout configured on the FileMaker side
PHP 7.4 or later.
5. Installation
Install PAC Products Bridge from WordPress, then configure and test the FileMaker connection.
1
Download
the plugin
2
Upload to
WordPress
3
Activate
the plugin
4
Configure
correction settings
3
Activate
the plugin
Installation is quick, but before going live you should always pertorm end-to-end testing in a staging environment to ensure everything works as expected.
6. Configuration
PAC Products Bridge is configured directly from WooCommerce.
Where to find the settings
WooCommerce
Settings
Integrations
PAC Products Bridge for WooCommerce
From this page you can configure the shared FileMaker Data API connection, define the FileMaker destination used by the bridge, choose how Professional deliveries are processed, select the payload strategy and run connection and end-to-end tests.
The Free edition uses one FileMaker database, layout and script for all supported product and variation lifecycle events. The configured FileMaker script receives a compact event|ID value through script.param. Professional keeps the same direct FileMaker Data API model and adds stock and price events, background delivery, automatic retries, manual resend tools, custom payload modes, full locally available WooCommerce JSON, certificate options and advanced diagnostics.
6.1 Connection settings
Define how PAC Products Bridge connects and authenticates to FileMaker Server.
Important: the values shown below are example values only. Replace them with the actual connection details of your own FileMaker environment.
Use this section to define how PAC Products Bridge connects to the FileMaker Data API.
- Enable turns the integration on or off.
- FileMaker Server is the full HTTPS URL of the FileMaker Server that exposes the Data API.
- Data API version selects the API version used by the plugin. In most environments, Latest (recommended) is the correct choice.
- Database is the name of the FileMaker file to connect to.
- Layout is the layout used by the Data API context.
- Script is the FileMaker script that PAC Products Bridge will execute.
- FileMaker user and FileMaker password must belong to an account with Data API access and sufficient privileges for the target file, layout and script.
- Certificate verification controls how the plugin validates the server certificate. Use the recommended/default mode for standard public certificates; use a custom CA option only if your server relies on a private or internal certificate authority.
- Custom CA certificate is only required when using a custom certificate authority.
- HTTP timeout defines how long the plugin waits for a response from FileMaker Server before considering the request failed.
Settings
Enable
√
Enable PAC Order Bridge
FileMaker Server
https://my.site.com
Data APl version
Latest (recommended)
Database
Products
Layout
WebProducts
Script
new_update_product
FileMaker user
restapi
FileMaker password
Password saved - leave blank to keep it
Alternatively, define PAC_ODBER_BRIDGE_FM_PASSWORD In wp-config.php.
Certificate verification
Custom - verify with a custom CA certificate
Custom CA certificate
—–BEGIN CERTIFICATE—–
MIIGjjCCBPagAwIBAgIQfU6C0+iJYtOlBn9V3uRmxDANBgkqhkiG9w0BAQsFADBg
MQswCQYDVQQGEwJHQjEYMBYGA1UEChMPU2VjdGlnbyBMaW1pdGVkMTcwNQYDVQQD
Ey5TZWN0aWdvIFB1YmxpYyBTZXJ2ZXIgQXV0aGVudGljYXRpb24gQ0EgRFYgUjM2
MB4XDTI1MTIwNzAwMDAwMFoXDTI2MTIwNzIzNTk1OVowGzEZMBcGA1UEAxMQc2Vy
djAxLnBhY2FnZS5pdDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL6f
fkU9oWz7Xb0zeh1NG4JVDDLPo8sfAPeZK2PgyIYL8VtTF0No7y7k6qVEeNVA6Yme
1mpJruMES/n7zzXu9Srw1BFSjhgPESoE3FFGyw4V9Vg6HhZRB3+PT+nuzr4ZsWhU
HTTP timeout
30
6.2. Supported events and script.param
PAC Products Bridge passes the event information through FileMaker script.param. The exact parameter depends on the installed edition and the selected payload mode.
Important: the values shown below are configuration examples. Match the parameter format to the expectations of your FileMaker script.
Free sends product and variation creation, update and deletion notifications immediately. All six lifecycle events are enabled through the main Enable setting; there are no separate switches for each event.
Supported lifecycle events:
product.created • product.updated • product. deleted variation.created • variation.updated • variation.deleted
Professional adds the settings illustrated below:
- Stock changes sends product. stock_changed or variation. stock_changed when the corresponding WooCommerce stock-setting hook runs. A stock-status-only change is not guaranteed to trigger these events.
- Price changes sends product. price_changed or variation. price_changed when regular, sale or active price metadata is added or updated. Repeated price events for the same object are suppressed for three seconds.
- Delivery mode selects Immediate delivery during the WooCommerce request or Background processing through Action Scheduler, with WordPress scheduling as a fallback.
- Full WooCommerce JSON passes the locally prepared product or variation representation with pac_bridge_event.
It overrides the Script parameter selection when the object is available. Image files are not embedded. - Script parameter selects Event + WooCommerce ID, Basic product JSON or Custom template. Free always uses event|ID.
- Parameter template is used only with Custom template. Supported placeholders are shown below the field.
The compact format is event|ID. For example, product.updated|123 identifies product 123, while variation.updated|456 identifies variation 456. Professional examples include product.stock_changed 123 and variation. price_changed 456.
A variation ID is not its parent product ID. Compact parameters do not include SKU, parent ID or additional product fields.
Deletion handling: moving an object to Trash and permanently deleting it both generate a deleted event before removal completes. Handle the explicit event in FileMaker; an immediate lookup may still find the object. There is no dedicated restore event.
Read the parameter with Get ( ScriptParameter ). Your FileMaker script decides how to process the event and retrieve any additional data. Professional payload details are documented in section 6.3.
Free lifecycle events
Product and variation create, update and delete events are sent immediately. Professional adds stock/price events, background delivery, retries and richer payloads.
Professional delivery
Professional adds stock/price events, background delivery, retries, custom payloads and full WooCommerce product JSON.
Enable
√
Notify FileMaker when product or variation stock changes
Price changes
√
Notify FileMaker when regular, sale or active price changes
Delivery mode
WooCommerce Order ID
Full WooCommerce JSON
√
Pass the complete WooCommerce REST product/variation JSON to FileMaker
When enabled, script.param contains the complete WooCommerce REST representation available locally, plus pac_bridge_event. No WooCommerce API call is required by FileMaker.
Image files themselves are not embedded.
Script parameter
Event + WooCommerce ID
Ignored when Full WooCommerce JSON is enabled
Parameter template
{event}|{id}
Placeholders: (event), (id), (parent_id), (sku), (name), (type), (status), (regular_price), {sale_price), (price), (stock_quantity), (stock_status).
6.3. Reliability options (Pro)
Control duplicate protection, automatic retries and manual recovery tools.
Important: the settings shown below are examples only. The correct values depend on how tolerant your workflow is to retries, duplicate protection and manual intervention.
This section controls how PAC Order Bridge behaves when delivery problems occur.
- Duplicate protection prevents the same order from being sent again automatically after it has already been delivered successfully.
- Automatic retry enables automatic retries for temporary network or server-side failures.
- Maximum attempts defines how many retry attempts are allowed.
- Retry interval defines the waiting time between one attempt and the next.
- Manual resend adds an order action that allows an administrator to send or resend the order to FileMaker manually.
- Order notes stores the result of the delivery in the WooCommerce order notes, making troubleshooting and auditing easier.
In general, retry options should be used for temporary connectivity problems, while duplicate protection should remain enabled unless a very specific workflow requires otherwise.
Reliability
Control duplicate protection, automatic retries and manual recovery tools.
Duplicate protection
√
Do not automatically resend an order already delivered successfully
Automatic retry
√
Automatically retry temporary network/server errors
Authentication, configuratio and FileMaker script errors are not automatically retried.
Maximum attempts
3
Retry interval
5
Manual resend
√
Add "Send/Resend to FileMaker" to WooCommerce order actions
Order notes
√
Add delivery result to WooCommerce order notes
6.4. Diagnostics and testing
These tools test the connection, script execution and end-to-end delivery, and provide safe diagnostics.
Important: the values and results shown below are examples only. Use the real tools in your own installation to validate the connection and the behaviour of your FileMaker script.
This section provides the tools needed to test the integration and troubleshoot problems safely.
- Debug log enables detailed WooCommerce-side logging for troubleshooting.
- Last communication shows the most recent delivery result, making it easier to verify whether the last request succeeded or failed.
- Connection test verifies that the plugin can reach FileMaker Server and authenticate successfully, without running the target script.
- Script test executes the configured FileMaker script using the test parameter you provide.
- End-to-end order test sends a real WooCommerce order through the complete integration flow, allowing you to validate the entire process from WooCommerce to FileMaker.
- System diagnostics provide a technical summary of the environment and plugin configuration, useful for support and troubleshooting.
A good practice is to run the tests in this order:
- Connection test
- Script test
- End-to-end order test
This makes it easier to identify whether a problem is caused by connectivity, authentication, script logic or order-specific data.
Diagnostics and tests
Debug log
√
Enable detailed WooCommerce logging
FileMaker passwords and session tokens are never written to the log, Errors are also recorded when debug logging is disabled.
Last communication
Test connection
Clear status
Shows the most recent result of connection, script, automatic delivery or test
Connection test
Test connection
Checks server reachability and FileMaker authentication without executing a FileMaker script. Uses the current connection fields even if they have not been saved yet.
Script test parameter
123456
Script test
Run script test
Executes the configured FileMaker script using the test parameter above. Uses the current connection fields even if they have not been saved yet.
Test WooCommerce order ID
59456
End-to-end order test
Send test order
Sends the test order even if it has already been delivered, but does not mark it as delivered in WooCommerce and does not schedule new retries
System diagnostics
PAC Order Bridge for WooCommerce – Diagnostics
—————————————————-
Plugin version
WordPress: 6.8.10
WooCommerce: 10.7.0
PHP: 7.4.33
Host FileMaker: https://my.site.com
Copy diagnostics
Safe technical information for support. Credentials and session tokens are excluded
Manual resend
√
Add "Send/Resend to FileMaker" to WooCommerce order actions
WooCommerce order metadata is intentionally retained as an audit trail.
7. Free vs Professional
Choose the version that fits your needs. The Professional version unlocks advanced features for reliable, production-ready workflows.
Binary image transfer is not currently provided by PAC Products Bridge. Product images can be referenced through WordPress media URLs, but direct binary image synchronization depends on WordPress media management rather than WooCommerce product data. A dedicated WordPress-to-FileMaker media synchronization plugin is currently under development.
8. Professional features
Extend lifecycle notifications with more event detail and delivery control.
Professional includes all features available in the Free edition.
The additional options change which events are sent, how the parameter is built and how delivery is handled. They do not replace your FileMaker business logic.
Stock and price events
Receive dedicated product and variation stock-setting events and notifications from price metadata changes.
Automatic retries
Retry eligible failures with a configurable total attempt limit and interval, including after an immediate first attempt.
Basic JSON and custom templates
Send a defined set of product fields or compose a text parameter from supported placeholders.
Manual product send
Send the current product from its Products-list row action using the saved configuration.
Full WooCommerce JSON
Pass the locally prepared object representation with pac_bridge_event, including image metadata where available.
Custom certificate handling
Use public CA verification, a custom PEM CA or an explicitly selected encryption-only mode.
Background delivery
Queue the prepared parameter through Action Scheduler, with a WordPress scheduling fallback.
Diagnostic support code
The package includes a diagnostic collector; version 1.0.0 does not expose it as a settings-page tool. See section 6.5.
9. FileMaker side implementation
Prepare the entry-point script that receives and processes product events.
The following steps describe an implementation pattern, not a required FileMaker schema. PAC Products Bridge authenticates, executes your script and supplies the parameter. Your FileMaker solution owns data validation, record matching, updates and downstream processing.
1
Create an integration account
Grant fmrest and the minimum access needed by the target file, layout and script.
2
Enable the Data API
Make the server reachable from the WordPress host over HTTPS.
3
Prepare the target layout and script
Use the names configured in the bridge’s connection settings.
4
Read script.param
Read Get ( ScriptParameter ) at the start of the FileMaker script.
5
Interpret or retrieve data
Validate the compact parameter or JSON and retrieve any additional WooCommerce data needed.
6
Implement your business logic
Create, update or archive records, preserve variation relationships and run downstream workflows.
Example FileMaker script flow (pseudo code)
# Receive the parameter sent by PAC Order Bridge
Set Variable [ $param ; Value: Get ( ScriptParameter ) ]
# Free:
# $param contains the WooCommerce Order ID
# Professional:
# $param may contain the Order ID, displayed order number,
# basic order JSON or a custom template value
# Interpret and validate $param according to your configuration
# Retrieve any additional WooCommerce data required by the workflow
# Create or update FileMaker records
# Trigger downstream actions
# (fulfilment, invoicing, notifications, etc.)
FILEMAKER-SIDE TOOLKIT
Want to accelerate the FileMaker-side implementation?
PAC WooCommerce SDK for FileMaker provides a reusable set of FileMaker scripts and integration building blocks designed to work with PAC Order Bridge and WooCommerce workflows.
Instead of starting from a blank script, you can use prebuilt patterns for receiving script.param, validating incoming values, retrieving WooCommerce data, creating or updating FileMaker records and launching downstream business processes.
The scripts remain open and editable, so they can be adapted to your own FileMaker data model and workflow.
Explore PAC WooCommerce SDK for FileMaker →
10. Real-world example
A product update in WooCommerce starts a catalog workflow in FileMaker.
This example illustrates a possible integration. The bridge performs event detection and delivery; the FileMaker steps require your own script implementation.
A store administrator updates product 123. With the compact format, FileMaker receives product.updated|123. The entry-point script validates the event, retrieves the product information it needs and updates the corresponding FileMaker catalog record.
With Professional Full WooCommerce JSON, the script instead receives the locally prepared product data and reads pac_bridge_event. If that payload contains everything the workflow needs, FileMaker can process it without a second WooCommerce request.
Product changes in WooCommerce
A supported product update triggers the bridge.
PAC Product Bridge executes the script
The prepared parameter is delivered immediately or through the selected background mode.
FileMaker interprets or retrieves data
Your script validates the event and ID and reads or retrieves the required fields.
Records are updated
Your FileMaker logic updates the matching product and any related records covered by the workflow.
Business processes continue
Your scripts can update internal catalog views, generate exports or start further business processing.
A later product.deleted event can archive the matching FileMaker record. A variation.updated event identifies the individual variation. Neither operation requires the bridge to impose a particular FileMaker table structure.
11. Security and reliability
Security and reliability features included in both editions, plus Professional controls for delivery, recovery, certificates and diagnostics.
Product parameters travel directly from your WordPress server to the configured FileMaker Server. PAC Age does not proxy that connection. The package also includes Freemius for licensing and optional usage opt-in; this is separate from the product-delivery path.
Both editions provide HTTPS communication, encrypted password storage, Data API session handling, connection and delivery tests, the latest communication status and protection against overlapping delivery of the same event.
Professional extends this shared foundation with six operational capabilities documented for the paid edition: background delivery, automatic retries, manual product resend, a configurable HTTPS certificate policy, custom CA certificate support and advanced diagnostics. The supplied version 1.0.0 exposes the first five in the plugin interface; its advanced-diagnostics collector is present in code but is not connected to a visible diagnostics panel. The distinction is documented in the Professional group below.
HTTPS and certificate verification
Requests use the configured FileMaker HTTPS endpoint. Free verifies the server certificate; Professional uses verification by default and adds the controls listed below.
Encrypted saved password
The FileMaker password is stored using authenticated encryption and a key derived from WordPress security keys and salts.
Data API session handling
The client opens a session for delivery and attempts to close it after the script request. Session credentials are handled by the bridge.
In-progress delivery lock
A per-event, per-object lock reduces overlapping sends. It does not permanently suppress later updates, retries or different events for the same object.
Tests and latest delivery status
Connection, script and end-to-end product tests help verify the integration. Last communication records the latest product-delivery status; it is not a complete history.
Controlled FileMaker access
Requests use the configured FileMaker account and its permissions. Configure a dedicated account with the required privileges and validate incoming parameters in your script.
Additional Professional controls and diagnostics
HTTPS and certificate verification
Requests use the configured FileMaker HTTPS endpoint. Free verifies the server certificate; Professional uses verification by default and adds the controls listed below.
Encrypted saved password
The FileMaker password is stored using authenticated encryption and a key derived from WordPress security keys and salts.
Data API session handling
The client opens a session for delivery and attempts to close it after the script request. Session credentials are handled by the bridge.
In-progress delivery lock
A per-event, per-object lock reduces overlapping sends. It does not permanently suppress later updates, retries or different events for the same object.
Tests and latest delivery status
Connection, script and end-to-end product tests help verify the integration. Last communication records the latest product-delivery status; it is not a complete history.
Controlled FileMaker access
Requests use the configured FileMaker account and its permissions. Configure a dedicated account with the required privileges and validate incoming parameters in your script.
Direct connection. No middleware.
12. Troubleshooting
Find solutions to common connection, delivery and FileMaker-side integration issues.
Cannot connect to FileMaker
First run Test connection from the PAC Order Bridge settings page.
Verify that the FileMaker Server URL is correct and reachable from the WordPress server over HTTPS, that the FileMaker Data API is enabled, and that the configured database is open.
Also check the database name, FileMaker account and password. The account must have the fmrestextended privilege and sufficient access to the configured file, layout and script.
If the connection works from another computer but fails from WordPress, also check firewall rules, DNS resolution and whether FileMaker Server is reachable from the web server itself.
HTTPS or certificate error
PAC Order Bridge connects to FileMaker Server over HTTPS and verifies the server certificate.
Make sure the certificate is valid, has not expired and matches the hostname configured in FileMaker Server.
If your FileMaker Server uses a certificate issued by a private or internal certificate authority, the Professional edition can use additional certificate verification modes and a custom CA certificate chain.
Avoid disabling certificate verification unless the environment specifically requires it and you understand the security implications.
Authentication failure
An authentication failure means FileMaker Server was reached but rejected the supplied credentials.
Verify the FileMaker user and FileMaker password, and make sure the account has the fmrest extended privilege and access to the configured database, layout and script.
If the password has changed, enter the new password and save the settings before testing again.
Script not found
Check that the script name configured in PAC Order Bridge exactly matches the script in the selected FileMaker database.
Also verify that the configured FileMaker account has permission to execute it and that the selected layout belongs to the correct file.
If the script has been renamed, update the PAC Order Bridge settings and run Script test again.
Order not sent to FileMaker
Start by checking Last communication and the WooCommerce log, then run the connection and script tests independently.
Confirm that the WooCommerce event configured as the trigger has actually occurred. In the Free edition, the standard workflow sends the order when payment completes. Professional can use additional WooCommerce triggers.
If the connection and script tests succeed but automatic delivery does not, verify the selected trigger, delivery mode and the order state.
Duplicate sends
PAC Order Bridge includes duplicate-delivery protection to prevent an order that has already been delivered successfully from being sent again automatically.
Your FileMaker workflow should nevertheless be designed to handle repeated requests safely whenever possible. A common approach is to store the WooCommerce Order ID and check whether the corresponding FileMaker record already exists before creating another one.
Manual test and resend operations may intentionally bypass parts of the normal automatic-delivery workflow.
Background job failure
Background delivery is a Professional feature and uses WooCommerce Action Scheduler when available.
If a background delivery fails, check the PAC Order Bridge diagnostics and the WooCommerce scheduled-action environment.
Temporary network or FileMaker Server failures can be retried automatically according to the configured retry settings. Authentication, configuration and FileMaker script errors are not treated as temporary failures and are not automatically retried
Missing data in FileMaker
First determine which script.param format is configured and what your FileMaker script actually receives.
The Free edition sends the WooCommerce Order ID. Professional can also send the displayed order number, basic order JSON or the result of a custom parameter template.
Verify the value returned by Get ( ScriptParameter ) and make sure your FileMaker script interprets it according to the selected PAC Order Bridge configuration.
If your workflow uses only an Order ID, any additional WooCommerce information required by FileMaker must be retrieved by your own FileMaker-side logic.
13. FAQ
Does PAC Order Bridge require any middleware?
No.
PAC Order Bridge communicates directly from your WordPress/WooCommerce server to the FileMaker Server configured by the administrator through the standard FileMaker Data API.
No Zapier, n8n, polling service or PAC Age intermediary server is required. PAC Age does not receive or proxy your FileMaker requests.
Does it work in real time?
Yes.
When the configured WooCommerce event occurs, PAC Order Bridge can immediately authenticate with FileMaker Server and execute the configured FileMaker script.
The Free workflow reacts to completed payments. Professional also provides additional WooCommerce triggers and optional background delivery.
What’s the difference between the Free and Professional version?
The Free edition provides a complete real-time workflow for completed payments: WooCommerce calls the configured FileMaker script immediately and passes the WooCommerce Order ID as script.param.
Professional adds additional WooCommerce triggers, background delivery, additional script.param formats, automatic retries, configurable retry behaviour, manual resend, custom CA certificate support, additional certificate verification options and advanced diagnostics.
See Free vs Professional for the complete feature comparison.
Can it be used with custom FileMaker workflows?
Yes.
PAC Order Bridge does not impose a FileMaker database schema or predefined workflow.
It executes the FileMaker script you configure and passes the selected value through script.param. Your FileMaker solution decides how to interpret that value and what happens next: retrieving WooCommerce data, creating or updating records, starting fulfilment, invoicing, notifications or any other business process.
Do you offer custom integration services?
Yes.
PAC Age development provides custom WooCommerce and FileMaker integration services, including FileMaker-side implementation, workflow design, data mapping and integration with existing business processes.
We can also help adapt PAC Order Bridge to complex FileMaker environments and develop the FileMaker-side logic required by your solution
Does PAC Order Bridge require a FileMaker plug-in?
No.
PAC Order Bridge uses the standard FileMaker Data API. No FileMaker plug-in is required.
Does PAC Age receive my WooCommerce order data?
No.
Requests are sent directly from your WordPress server to the FileMaker Server URL configured by the administrator. PAC Age does not proxy the FileMaker connection
Does PAC Order Bridge support WooCommerce HPOS?
Yes.
PAC Order Bridge declares compatibility with WooCommerce High-Performance Order Storage (HPOS).
Can I resend an order manually?
Yes.
With the Professional edition. Individual WooCommerce orders can be sent or resent to FileMaker using the manual order action.
14. Changelog
15. Related products
Complete your integration with other PAC products for WooCommerce and FileMaker.
PAC Taxonomy Bridge for WooCommerce
Synchronize WooCommerce categories, global attributes and attribute values with FileMaker in real time.
PAC Products Bridge for WooCommerce
Send product and variation changes to FileMaker in real time, with advanced stock, price and payload options in Professional.
PAC WooCommerce SDK for FileMaker
Reusable FileMaker scripts and integration building blocks for PAC WooCommerce workflows.