IFS Cloud and Walmart Marketplace integration

What moves between them

IFS Cloud is the source of truth for finished goods master data and inventory quantities. Product master, pricing, and available-to-promise inventory flows from IFS to Walmart Marketplace to keep listings current and prevent oversell. Walmart orders and inventory adjustments flow inbound to IFS where they trigger fulfillment and accounting workflows. Walmart return events are ingested; WFS returns are read-only and reported only.

How ml-connector handles it

ml-connector stores OAuth credentials for both systems encrypted and manages separate token refresh cycles: every 60 minutes for IFS, and every 12-15 minutes for Walmart. On the IFS side, it polls the OData API for items and inventory, capturing the ETag value required for any PATCH operations, then validates the company code configuration against IFS before posting. For Walmart, it receives webhook events for orders and returns, validates signatures, and translates Walmart shipment nodes to IFS warehouse codes. Pricing updates to Walmart use bulk feed operations rather than single-item calls to avoid throttling. Every inbound order from Walmart is checked against IFS inventory to prevent double-allocation, and records are queued with deduplication keys so a webhook retry does not create duplicates.

A real-world example

A mid-sized consumer goods manufacturer sells through Walmart Marketplace alongside direct channels. Before the integration, the operations team updated inventory in IFS each morning, then manually logged into Walmart to adjust listings based on available stock and edit prices when costs changed, often leaving Walmart listings out of sync for hours. With IFS Cloud and Walmart Marketplace connected, inventory from IFS auto-syncs to Walmart on an hourly basis, pricing updates push via bulk feed, and incoming Walmart orders land in IFS automatically for picking and invoicing. The team no longer manually maintains Walmart listings, and oversell incidents have dropped to near zero.

What you can do

• •Push finished goods inventory quantities and pricing from IFS Cloud to Walmart Marketplace on a configurable polling schedule, with bulk feed operations for large price changes.
• •Ingest Walmart orders and shipment address information into IFS Cloud for picking, packing, and invoicing.
• •Map Walmart shipment nodes to IFS warehouse and location codes so inventory is allocated to the correct fulfillment source.
• •Authenticate both systems with OAuth 2.0 Client Credentials, managing IFS 60-minute tokens and Walmart 15-minute tokens with automatic refresh and error handling.
• •Deduplicate inbound webhook events from Walmart and validate orders against available IFS inventory before posting.

Questions

How does pricing synchronization work given Walmart's 100-updates-per-hour throttle on single items?

IFS Cloud feeds pricing changes to Walmart via bulk feed operations rather than single-item API calls. This avoids the per-item throttle and allows large price updates across hundreds of SKUs in one operation. Price changes are sent on a schedule aligned with your cost-change windows.

What happens when a Walmart order arrives and the item is out of stock in IFS?

ml-connector validates every inbound Walmart order against current IFS inventory before posting. If inventory is insufficient, the order is queued for manual review or rejection rather than creating a backorder in IFS. This prevents oversell and ensures fulfillment can proceed immediately for accepted orders.

How are Walmart warehouse locations and shipment nodes mapped to IFS?

Each Walmart shipment node (e.g., Walmart fulfillment center vs. third-party drop ship node) is mapped to an IFS warehouse and location code during setup. Inbound orders carry the shipment node, and ml-connector looks up the matching IFS location so picking and invoicing routes through the correct warehouse.