Infor CloudSuite and Shopify integration

What moves between them

Shopify orders and customer records flow into Infor CloudSuite via webhooks. ml-connector receives Shopify webhook pushes for order creation and updates, then transforms the order data into a CloudSuite purchase order or sales order (depending on your mapping strategy), and adds or updates customer records in CloudSuite's AR module. The flow is one-directional: from Shopify into CloudSuite. ml-connector polls CloudSuite periodically to confirm the records were created and to handle any creation failures or business rule rejections from the ERP.

How ml-connector handles it

ml-connector accepts and verifies Shopify webhooks by validating the X-Shopify-Webhook-Id header signature against the registered webhook secret. It extracts order items, quantities, customer contact data, and billing addresses from the Shopify order payload and transforms them into CloudSuite purchase order lines and GL account allocations. For each Shopify order, ml-connector looks up or creates a customer record in CloudSuite using the customer email, then posts the order as a purchase order or import document via the ION API Gateway to the per-tenant OAuth endpoint and base URL extracted from the customer's stored .ionapi credentials file. CloudSuite token lifetimes vary by tenant (1-24 hours), so ml-connector proactively refreshes the bearer token before expiry. CloudSuite's infrastructure-level rate limit (typically 100-500 requests per minute per client) is respected with exponential backoff on 429 responses. If a CloudSuite insert fails due to a missing GL account or invalid CONO, the record is flagged in the audit log and can be replayed once the mapping is corrected.

A real-world example

A B2B e-commerce business sells industrial parts through Shopify, serving hundreds of small manufacturers and distributors. Previously, the operations team downloaded Shopify order reports daily and manually entered order details into Infor CloudSuite for procurement and fulfillment planning. Salespeople and the warehouse team had no real-time visibility into which orders had been confirmed in CloudSuite. With Shopify and CloudSuite connected, each order pushes into CloudSuite within seconds of checkout, the fulfillment team sees orders in their native CloudSuite interface, and customer records from the storefront update automatically. The manual daily data-entry step is eliminated, and order-to-fulfillment lead time drops.

What you can do

• •Push Shopify orders into Infor CloudSuite as purchase orders or import documents on every order creation and update.
• •Sync Shopify customer names, email addresses, and billing details into CloudSuite customer master records.
• •Map Shopify order line items to CloudSuite GL accounts and allocate costs to the correct CONO (company number) per order.
• •Authenticate Shopify with offline OAuth tokens and CloudSuite with per-tenant OAuth credentials extracted from the .ionapi file.
• •Verify Shopify webhook signatures and poll CloudSuite to confirm order creation, with a full audit trail on every record.

Questions

Do orders flow both ways between Shopify and Infor CloudSuite?

No. Orders and customer data flow from Shopify into CloudSuite only. Once an order is created in CloudSuite, ml-connector does not push changes back to Shopify. This keeps the e-commerce storefront and the ERP independent; inventory and pricing updates in CloudSuite do not override Shopify's product catalog.

How does ml-connector handle Infor CloudSuite's per-tenant OAuth endpoints and regional ION API Gateway URLs?

ml-connector accepts the customer's .ionapi credentials file, which contains the region-specific base URL, tenant ID, OAuth token endpoint, and service account credentials. Each customer's CloudSuite tenant may be in a different region (US, EU, APAC), and the ION API Gateway URL varies accordingly. ml-connector constructs the correct endpoint per customer and refreshes tokens proactively before expiry.

What happens if a Shopify order cannot be created in Infor CloudSuite?

If a CloudSuite insert fails (for example, a missing GL account, invalid CONO, or rate-limit rejection), ml-connector logs the error with the full order payload in the audit trail and marks the record as failed. The order can be replayed once the mapping or configuration is corrected, without re-sending the Shopify webhook.