Infor CloudSuite and Walmart Marketplace integration

What moves between them

The main flow runs from Walmart Marketplace into Infor CloudSuite. Orders placed on Walmart Marketplace are read via polling or webhook, mapped to CloudSuite customers and GL accounts, and posted as revenue transactions into the ledger. Returns approved by the seller flow in the same direction as adjustments to revenue. Reference data such as customer master records may be aligned in both directions if a seller maintains a product catalog in both systems. Walmart data is read-only in most respects, so ml-connector does not write pricing or inventory back to Walmart.

How ml-connector handles it

ml-connector stores both credential sets encrypted and refreshes the Walmart access token proactively every 14 minutes to avoid the 15-minute expiry. On the CloudSuite side, it parses the per-customer .ionapi credentials file to extract the region-specific base URL and token endpoint, authenticates with the OAuth 2.0 resource owner password credentials grant, and polls orders and returns on a cadence tied to your selling and returns processing calendar. When Walmart Marketplace webhooks are enabled, ml-connector receives and verifies push notifications for orders and returns, then reconciles against the polling schedule to avoid duplicates. Each order line is mapped to a CloudSuite customer and a GL revenue account configured per seller, and the transaction is posted with the order date and Walmart order ID for audit traceability. Returns are posted as negative revenue adjustments to the same accounts. ml-connector respects Walmart's rate limits and CloudSuite's per-minute request quotas, tracks token expiry on both sides, and maintains a full audit log so a failed GL posting can be replayed once the issue is resolved.

A real-world example

A mid-sized seller runs Infor CloudSuite Financials for accounting and general ledger, and uses Walmart Marketplace to sell consumer goods across multiple fulfillment nodes. Before the integration, the finance team exported daily order reports from Walmart Marketplace and manually entered the revenue totals and returns into CloudSuite each morning, which meant lag time between order placement and ledger posting, and frequent reconciliation errors during month-end close when Walmart's export and CloudSuite's AR aging did not agree. With Walmart Marketplace and CloudSuite connected, each day's orders and returns post automatically to the revenue ledger, allocated to the correct GL accounts by category, and the seller can close the books on day one of month-end knowing Walmart revenue is already locked in.

What you can do

• •Post Walmart Marketplace orders into Infor CloudSuite's receivables and revenue GL accounts daily, mapped to customer master records and GL dimensions.
• •Track Walmart returns and refunds as adjustments to revenue, maintaining full traceability with order ID and return date.
• •Authenticate Walmart Marketplace with OAuth 2.0 and bridge the 15-minute token expiry, and CloudSuite with region-specific tenant credentials.
• •Receive Walmart Marketplace webhook push notifications for orders and returns when enabled, while also polling on a schedule to ensure no data is missed.
• •Maintain a complete audit trail on every order and return, with the ability to replay a posting if a downstream GL call fails.

Questions

Which direction does data move between Infor CloudSuite and Walmart Marketplace?

The main flow is Walmart Marketplace into Infor CloudSuite. Orders and returns move from Walmart into CloudSuite as revenue and adjustment transactions posted to the GL. Customer master records may be aligned in both directions if the seller maintains the same product catalog in both systems. Walmart Marketplace data is read-only in the integration, so ml-connector does not write pricing or inventory back.

How does ml-connector handle Walmart's 15-minute token expiry and webhook retries?

ml-connector refreshes the Walmart access token proactively every 14 minutes before expiry, eliminating downtime from token refresh failures. When Walmart Marketplace webhooks are enabled, ml-connector receives push notifications for orders and returns, verifies them, and reconciles them against the polling schedule to ensure no duplicates are posted to CloudSuite. Webhook events that fail to process are replayed according to Walmart's retry schedule.

Does the integration work with Infor CloudSuite's region-specific URLs and lack of traditional webhooks?

Yes. ml-connector parses the per-customer .ionapi credentials file to extract the region-specific base URL and OAuth token endpoint, since CloudSuite publishes no shared hostname. Because CloudSuite does not support traditional webhooks, ml-connector polls orders and returns from Walmart on a schedule you control, and can also integrate with Walmart's webhook push notifications for lower-latency posting.