Infor CloudSuite and BigCommerce integration

What moves between them

Two flows run in opposite directions. From BigCommerce into Infor CloudSuite, ml-connector reads new and updated orders, their payment transactions, and refunds and posts them as sales and GL entries against the matching Infor accounts, and aligns the ordering customer to an Infor customer record. From Infor CloudSuite out to BigCommerce, item master data and inventory levels are pushed to the BigCommerce catalog so product details, prices, and stock on the storefront reflect the ERP. Order webhooks trigger the inbound work as soon as a sale lands, and a scheduled poll of both sides backfills anything a webhook missed. GL accounts are mastered in Infor and never created from BigCommerce data.

How ml-connector handles it

ml-connector stores both credential sets encrypted and sends the BigCommerce X-Auth-Token on every storefront request, while on the Infor side it accepts the full .ionapi field set per customer, requests an OAuth Bearer token with the password grant, and refreshes that token proactively before its 1 to 24 hour lifetime expires rather than reacting to a 401. BigCommerce order, product, and inventory webhooks arrive signed with HMAC-SHA256, so each delivery is verified against the client_secret before processing, and because the payload is only a type and id the connector immediately calls GET on the v2 order or v3 transaction endpoint to fetch the full record. Storefront SKUs are mapped to Infor item numbers and order totals are mapped to Infor GL accounts up front, so every posting references records that already exist. Because Infor offers no idempotency key, the connector queries by external id before each Add transaction to avoid duplicate sales entries, and refunds are processed one at a time per order since BigCommerce does not allow concurrent refunds on the same order. BigCommerce rate limits return HTTP 429 with reset headers and Infor returns 429 from gateway throttling, so ml-connector backs off and retries, tracks that BigCommerce auto-deactivates idle webhooks and re-registers them, and keeps a full audit trail with replay on every record.

A real-world example

A mid-sized consumer goods manufacturer with roughly 150 staff runs Infor CloudSuite M3 for production, inventory, and finance, and sells direct to consumers through a BigCommerce store. Before the integration, a clerk exported the prior day's BigCommerce orders to a spreadsheet and re-keyed the sales and tax totals into M3, while a second person manually updated storefront prices and stock counts whenever the ERP changed, which left the website out of date and month-end sales hard to reconcile. With Infor CloudSuite and BigCommerce connected, each order and refund posts into M3 automatically against the right GL accounts, and item and inventory updates flow out to the catalog on a schedule. The double data entry is gone and the storefront stays in agreement with the ERP.

What you can do

• •Post BigCommerce orders, payment transactions, and refunds into Infor CloudSuite as sales and GL entries against the correct accounts.
• •Push Infor CloudSuite item master data and inventory levels out to the BigCommerce catalog so product details and stock stay current.
• •Map BigCommerce storefront SKUs to Infor item numbers and order totals to Infor GL accounts so postings land on valid records.
• •Verify BigCommerce HMAC-SHA256 webhook signatures, then fetch the full order or transaction from the REST API before posting.
• •Bridge the BigCommerce X-Auth-Token and the Infor ION OAuth token, with retries and a full audit trail on every record.

Questions

Which direction does data move between Infor CloudSuite and BigCommerce?

Both directions. BigCommerce orders, payment transactions, and refunds move into Infor CloudSuite as sales and GL entries, while Infor item and inventory data moves out to the BigCommerce catalog. GL accounts are mastered in Infor, so ml-connector posts against existing accounts rather than creating financial structure from storefront data.

How does the integration handle BigCommerce webhooks when the payload is so small?

BigCommerce webhooks are verified against the client_secret using the HMAC-SHA256 X-BC-Signature header, then processed. Because each payload carries only a resource type and id, ml-connector immediately calls the BigCommerce REST API to fetch the full order, transaction, or product before posting it into Infor CloudSuite. It also re-registers webhooks that BigCommerce auto-deactivates after a period of inactivity or repeated delivery failures.

Does Infor CloudSuite need webhooks set up for this to work?

No. Infor CloudSuite has no self-service webhooks for cloud connectors, and configuring an ION Desk document flow requires an Infor admin. ml-connector polls the Infor REST API on a schedule for changed items and inventory and authenticates each call with an OAuth token from the customer's .ionapi credentials, so no Infor-side push setup is required.