PAC SOFTWARE DOCS
PAC Order Bridge for WooCommerce
Technical documentation for real-time WooCommerce order delivery to Claris FileMaker through the FileMaker Data API.
Version 1.1.5 • Updated Aug 2026
WooCommerce order event
PAC Order Bridge
FileMaker Data API
FileMaker script
1. Overview
PAC Order Bridge for WooCommerce is a WordPress plugin that connects your WooCommerce store with Claris FileMaker Server through the FileMaker Data API.
Whenever a relevant event occurs in WooCommerce (for example a new order), the plugin sends the order data to a FileMaker script in real time, allowing you to keep your business data, workflows and integrations under full control inside FileMaker. No polling, no middleware and no external synchronization services.
Real-time. Direct. Under your control.
Orders are sent immediately when they happen, with no polling or third-party services.
2. Key benefits
Real-time sync
Orders are sent to FileMaker immediately when they happen.
Your business logic
Keep all the logic in FileMaker, using your own scripts.
Reliable
Background processing, automatic retries and diagnostics (Pro).
Native integration
Built for WooCommerce and FileMaker, no unnecessary third-party services.
3. How it Works
PAC Order Bridge uses WooCommerce hooks to detect order events and calls the FileMaker Data API to execute your script.
WooCommerce
Order event
PAC Order Bridge
(prepares and sends data via Data API)
FileMaker Data API
(executes your script)
FileMaker script
(your business logic)
- A new order is created (or another configured event occurs) in WooCommerce.
- PAC Order Bridge collects the order data and prepares the payload.
- The plugin opens a FileMaker Data API session and executes your script.
- Your FileMaker script processes the data (create/update records, launch workflows, etc.).
- The plugin logs the result and closes the Data API session.
You remain in control.
The FileMaker-side logic is entirely under your control. The plugin simply delivers the data.
4. Requirements
To use PAC Order Bridge for WooCommerce, you need the following components:
WordPress (supported and up to date)
Data API enabled on your FileMaker Server
HTTPS-enabled website
Claris 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
5. Installation
PAC Order Bridge uses WooCommerce hooks to detect order events and calls the FileMaker Data API to execute your script.
1
Download
the plugin
2
Upload to
WordPress
3
Activate
the plugin
4
Configure
correction settings
3
Activate
the plugin
Installation is quick, but betore going live you should always pertorm end-to-end testing in a staging environment to ensure everything works as expected.
6. Configuration
PAC Order Bridge is configured directly from WooCommerce.
Where to find the settings
WooCommerce
Settings
Integrations
PAC Order Bridge for WooCommerce
From this page you can configure the FileMaker Data API connection, choose when WooCommerce sends an order to FileMaker, define the value passed as script.param, configure reliability options and run connection, script and end-to-end tests.
The Free edition provides the standard payment-completed → immediate delivery → WooCommerce Order ID workflow. Professional unlocks additional triggers, background delivery, parameter formats, retry options, manual resend, custom CA certificates and advanced diagnostics.
6.1 Connection settings
These are the real fields from the PAC Order Bridge settings page used to connect to FileMaker.
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 Order 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 Order 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
Orders
Layout
WebOrders
Script
new_order
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. Trigger events (Pro)
This section determines when WooCommerce notifies FileMaker and how the data is delivered.
Important: the values shown below are examples of a valid configuration. Choose the event and delivery mode that best match your own workflow.
This section determines when WooCommerce sends data to FileMaker and how the delivery is performed.
- Event defines the WooCommerce event that triggers the integration. For example, you may want to send the order when payment is completed, when the order enters processing, or at another supported stage of the order lifecycle.
- Delivery mode defines whether the request is sent immediately during the WooCommerce action or processed in the background.
In general:
- use payment completed when the FileMaker workflow should run only after a successful payment;
- use immediate delivery when real-time execution is preferred;
- use background delivery when you want to reduce the impact on the checkout/request flow and let WooCommerce process the call asynchronously.
The Professional version provides additional trigger and delivery options compared to the standard Free workflow.
WooCommerce trigger
Event
Payment completed (recommended)
Delivery mode
Immediate
6.3. Payload and script.param
PAC Order Bridge passes a value to the configured FileMaker script through script.param.
Important: the examples shown below are demonstration values only. Configure the parameter format that matches the expectations of your FileMaker script.
PAC Order Bridge passes a value to FileMaker through script.param. This is the input your FileMaker script receives when it runs.
- Script parameter defines what kind of value is sent.
- A simple option such as WooCommerce Order ID sends a single identifier, which is often the best choice when the FileMaker script is responsible for loading the rest of the order data.
- Other available formats can send a different identifier or a richer structured value, depending on the selected option.
- Parameter template is used when a custom template-based value is required.
When a template is used, placeholders such as:
{order_id}, {order_number}, {status}, {total}, {currency}, {email}, {transaction_id}
are replaced with real order values before the request is sent.
Use a simple identifier when your FileMaker script already knows how to retrieve the order context. Use a custom or richer format only when your workflow explicitly requires it.
Script parameter
Script parameter
WooCommerce Order ID
Parameter template
(order_id)
Used only with Custom template. Avaliable placeholders: (order_id), (order_number), (status), (total). (cucrency). (emall), (transaction_id),
6.4. 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
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.5. 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.
8. Professional features
The Professional version of PAC Order Bridge includes advanced features for reliable, flexible and production-ready integrations.
Professional includes all features available in the Free edition.
The features below extend the standard payment-completed → immediate delivery → WooCommerce Order ID workflow with additional WooCommerce triggers, delivery modes, FileMaker script parameter formats, recovery tools and certificate options.
Choose these options according to the requirements of your integration. They do not change your FileMaker data model or business logic: PAC Order Bridge still executes the FileMaker script you configure, while your FileMaker solution remains responsible for processing the received parameter.
Additional WooCommerce triggers
React to payment completed, Processing, Completed or checkout-created orders
Additional script.param formats
React to payment completed, Processing, Completed or checkout-created orders
Basic order JSON
Send structured order information directly as the FileMaker script parameter.
Background delivery
Process delivery through WooCommerce Action Scheduler instead of the interactive request.
Automatic retry
Retry temporary network or server failures with configurable attempts and delay.
Manual send / resend
Send or resend individual WooCommerce orders to FileMaker from the order actions.
Custom certificate handling
Use additional certificate verification modes and custom CA certificate chains.
Advanced diagnostics
Additional diagnostic tools for production integrations and troubleshooting
9. FileMaker side implementation
On your Filemaker server, you need to prepare a script to receive and process the order data sent by PAC Order Bridge.
The steps below describe a typical implementation pattern, not a mandatory FileMaker architecture.
PAC Order Bridge does not create FileMaker records or impose a database schema. Its responsibility ends after authenticating with the FileMaker Data API, executing the configured script and passing the configured value through script.param.
Your FileMaker script decides how to interpret that value and what happens next. In a simple Free workflow, the parameter is the WooCommerce Order ID and FileMaker can use it to retrieve or process the complete order according to your existing business logic. Professional workflows may use another supported parameter format instead.
1
Create a dedicated integration account
Create a FileMaker account with the fmrest extended privilege and only the permissions required by the integration
2
Enable the Data API
Make sure the FileMaker Data API is enabled and that the server is reachable from your WordPress host over HTTPS.
3
Prepare the target layout and script
Configure the FileMaker file, layout context and script that PAC Order Bridge will use.
4
Read script.param
Use Get ( ScriptParameter ) to receive the value sent by PAC Order Bridge.
5
Interpret or retrieve data
Process the parameter according to the configured format and retrieve any additional WooCommerce data required by your workflow.
6
Implement your business logic
Create or update records, start fulfilment, invoicing, notifications or any other FileMaker workflow.
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
Here’s a typical workflow from a new WooCommerce order to completed business processes in FileMaker.
After the script starts, all validation, data retrieval, record creation and downstream processing are implemented by your FileMaker solution. For example, FileMaker may use the received WooCommerce Order ID to retrieve order details, verify the customer and payment state, create or update records and then start fulfilment or invoicing.
Other workflows are equally valid: PAC Order Bridge does not require a specific FileMaker schema or processing model.
New order in WooCommerce
A customer places an order in your WooCommerce store.
PAC Order Bridge executes FileMaker script
The plugin captures the order and sends the data to FileMaker viathe Data API.
Interpret / retrieve order data
Your FileMaker script validates customr data, payments status and order details.
Create or update records
Orders, customers and related records are created or updated in FileMaker.
Trigger business actions
Invoicing, notifications, fullfillment and other workflows are executed automatically.
11. Security and reliability
PAC Order Bridge is built with security and reliability in mind, using the FileMaker Data API for direct, encrypted communication.
PAC Order Bridge communicates directly between your WordPress/WooCommerce server and the FileMaker Server configured by the administrator. PAC Age does not proxy the FileMaker connection and no third-party middleware is required.
The Free edition includes HTTPS certificate verification, encrypted FileMaker password storage, duplicate protection and connection, script and end-to-end testing. Professional adds recovery and production-oriented features such as automatic retry of temporary network/server failures, manual resend, additional certificate options and advanced diagnostics.
Authentication errors, configuration errors and FileMaker script errors are not treated as temporary failures and are therefore not automatically retried.
HTTPS encryption
FileMaker Data API requests are sent directly from WordPress to the configured FileMaker Server over HTTPS.
Encrypted FileMaker password
The stored FileMaker password is encrypted using WordPress security salts.
Certificate verification
The Free edition verifies the FileMaker Server HTTPS certificate.
Duplicate protection
Prevents automatic redelivery of an order that has already been delivered successfully.
Custom certificate handling (Pro)
Adds custom CA certificate chains and additional certificate verification options.
Advanced reliability and diagnostics (Pro)
Adds automatic retries, manual resend tools and advanced diagnostic capabilities.
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.