IFS Cloud and BigCommerce integration

What moves between them

Orders and customers move from BigCommerce into IFS Cloud. When a customer places an order on BigCommerce, ml-connector reads it and creates a CustomerOrderSet record in IFS, mapping the customer email to an existing IFS Customer and allocating revenue to the configured GL account. Payment and shipment events from BigCommerce trigger fulfillment adjustments in IFS as GL voucher entries. Refunds are also synced and mapped to revenue reversals. The flow is primarily one-way (BigCommerce to IFS); IFS sales orders are not pushed back to BigCommerce.

How ml-connector handles it

ml-connector stores the BigCommerce static API key encrypted and presents it on every REST call. For IFS, it uses OAuth2 client credentials to obtain a bearer token (cached for 60 minutes with refresh on 401), and stores the customer-provided company code in per-customer configuration so financial records land in the correct GL dimensions. BigCommerce webhooks are registered for order/created, order/updated, order/statusUpdated, and payment events; ml-connector validates each webhook signature using the HMAC-SHA256 stored secret and then immediately fetches the full order details via REST API since webhook payloads are stubs only. For orders created in BigCommerce, ml-connector queries IFS Customer records to match on email, maps the order total and line items to the configured revenue account, and creates the CustomerOrderSet with all required GL mappings before posting. Shipment and refund events trigger follow-up voucher adjustments in IFS with the ETag concurrency header to prevent conflicts. Webhook failures are retried by BigCommerce up to 11 times over 48 hours; ml-connector also implements fallback polling on a schedule if webhooks are missed. BigCommerce enforces a maximum of 10 webhooks per store plus the rate limit, so ml-connector consolidates multiple event types under a single endpoint. If signature validation fails or the endpoint response rate drops below 90 percent, BigCommerce auto-deactivates the webhook, so ml-connector monitors endpoint health and reactivates as needed.

A real-world example

A mid-market retailer runs IFS Cloud for inventory, procurement, and GL accounting across three warehouses, and BigCommerce for direct-to-consumer e-commerce sales. Before the integration, orders entered BigCommerce were exported daily and re-entered into IFS by the sales team, creating order-entry delays and duplication errors. Revenue was recognized after shipment-confirm in BigCommerce but IFS GL rows were posted a day later, causing month-end reconciliation delays. With IFS Cloud and BigCommerce connected, each order flows into IFS within seconds of placement, allocated to the correct customer and revenue account, and fulfillment events trigger GL postings automatically. The sales team no longer re-keys orders, and month-end close finds revenue already reconciled to the GL.

What you can do

• •Sync BigCommerce orders into IFS Cloud as sales orders, mapped to customer records and GL revenue accounts.
• •Capture payment and refund events from BigCommerce and post adjustments into IFS GL as journal entries.
• •Bridge OAuth2 (IFS) and static API key (BigCommerce) authentication with encrypted credential storage per customer.
• •Map BigCommerce transaction details and shipment status to IFS order fulfillment and revenue GL dimensions.
• •Validate BigCommerce webhook signatures and retry on failure with a fallback polling schedule if webhooks are missed.

Questions

What records move between BigCommerce and IFS Cloud in this integration?

Orders and customers flow from BigCommerce into IFS Cloud. When a customer places an order on BigCommerce, ml-connector creates a corresponding sales order in IFS, mapping the customer and allocating revenue to the configured GL account. Payment confirmations and shipments from BigCommerce then trigger fulfillment adjustments and revenue recognition in IFS. The sync is primarily one-way (BigCommerce to IFS); IFS orders are not pushed back to BigCommerce.

How does ml-connector handle BigCommerce webhooks and the signature validation requirement?

ml-connector registers webhooks for order/created, order/updated, order/statusUpdated, and payment events on your BigCommerce store. Each webhook payload includes an HMAC-SHA256 signature in the X-BC-Signature header that ml-connector validates using the stored client secret. BigCommerce webhook payloads are stubs (type and ID only), so ml-connector immediately calls the BigCommerce REST API to fetch the full order and transaction details before creating records in IFS. If webhooks fail repeatedly, BigCommerce auto-deactivates them after 48 hours, so ml-connector monitors health and can reactivate when needed.

How does the integration map BigCommerce customers to IFS Cloud customer records?

ml-connector queries IFS Customer records on email address to find the matching customer. If a customer in BigCommerce does not have a matching email in IFS, ml-connector can either skip the order (requiring manual intervention) or create a new IFS customer record based on the name and billing address from BigCommerce, depending on your configuration. Line items and order totals are mapped to the revenue GL account you specify per connector instance, ensuring consistent accounting dimension allocation.