Infor CloudSuite and Orderful integration

What moves between them

Purchase orders and invoices flow from Infor CloudSuite to Orderful for EDI translation and delivery to suppliers. ml-connector polls CloudSuite for new or modified POs and invoices on a schedule you control, typically daily or after each order entry batch. For inbound, Orderful sends 855 acknowledgments, 856 advanced ship notices, and 861 receiving advice to ml-connector via webhook or polling, which are translated back to CloudSuite receipt records and matched to the original PO by supplier reference and ISA identifier. The supplier master and GL accounts remain in CloudSuite; Orderful has no persistent copy of them.

How ml-connector handles it

ml-connector extracts the OAuth2 endpoint and base URL from your Infor CloudSuite .ionapi credentials file and uses them to request a bearer token on startup, refreshing proactively before the configured token lifetime expires. It polls CloudSuite's PPS100MI list endpoint for purchase orders and APS100MI for invoices, deduplicating on the CloudSuite document number and revision level stored in an external map. Each CloudSuite PO carries a supplier reference and company number (CONO parameter required by M3); ml-connector extracts those and maps them to ISA identifiers for Orderful routing. Translations from CloudSuite data structures to X12 850 (purchase order) and 810 (invoice) are built on Orderful's Mosaic v4 schema. For inbound, ml-connector listens for 855, 856, and 861 documents via Orderful webhooks or polls /v3/polling-buckets if webhooks are not enabled, translates the EDI back to CloudSuite's APS receiving transaction format, and creates receipt records matched to the original PO. Rate limit backoff and retry logic respect both CloudSuite's 429 responses and Orderful's per-region throttling. All mappings and upstream failures are logged for audit and replay.

A real-world example

A mid-market distributor runs Infor CloudSuite M3 for supply chain and procurement. The company operates in three regions and works with dozens of suppliers through an EDI network. Previously, the purchasing department received orders from CloudSuite as printed forms or email, manually typed them into their EDI provider's portal, and waited for email notifications of shipment and delivery confirmations, which were logged by hand back into CloudSuite as receiving records. With Infor CloudSuite and Orderful connected, each purchase order created in CloudSuite is automatically formatted as an X12 850 and sent to the supplier via their preferred EDI channel within minutes. Supplier acknowledgments come back through Orderful as 855 documents and are automatically posted to CloudSuite as confirmed receipts. The distributor eliminates the manual EDI step and gains real-time visibility of supplier commitments and shipments in their ERP.

What you can do

• •Push Infor CloudSuite purchase orders and invoices to Orderful for translation to X12 850 and 810 EDI formats and delivery to suppliers.
• •Receive 855 acknowledgments, 856 ship notices, and 861 receiving advice from Orderful and post them back to Infor CloudSuite as confirmed receipts and invoice records.
• •Map supplier references and company numbers from Infor CloudSuite to ISA identifiers for accurate Orderful routing and back-matching on return.
• •Handle Infor CloudSuite OAuth2 token refresh and region-specific URLs, and Orderful API Key authentication across US and EU regions.
• •Poll Infor CloudSuite and Orderful on a schedule you control with rate-limit backoff, external deduplication, and a full audit trail for every translation and match.

Questions

Which direction does data move between Infor CloudSuite and Orderful?

Purchase orders and invoices move from Infor CloudSuite to Orderful for EDI translation and delivery to suppliers. Acknowledgments, ship notices, and receiving advice flow from Orderful back to Infor CloudSuite. The supplier master and GL accounts stay in Infor CloudSuite and are not replicated to Orderful.

How does the integration handle Infor CloudSuite's region-specific URLs and lack of webhooks?

ml-connector reads your .ionapi credentials file to extract the OAuth2 endpoint, base URL, and tenant ID for your region. Because Infor CloudSuite has no native webhooks, ml-connector polls the ION API Gateway on a schedule you control, typically daily. It respects per-tenant rate limits and refreshes OAuth2 tokens before expiry to avoid outages.

How are Infor CloudSuite purchase orders matched to Orderful acknowledgments and receipts?

Each purchase order carries a supplier reference and company number (CONO) from Infor CloudSuite. ml-connector extracts these and maps them to ISA identifiers for Orderful routing. When a 855 acknowledgment or 861 receiving advice comes back from Orderful, ml-connector reverses the mapping to find the original Infor CloudSuite PO and posts the receipt to the correct order.