Acumatica and Walmart Marketplace integration

What moves between them

Orders flow from Walmart Marketplace into Acumatica. ml-connector pulls released Walmart orders and creates the matching Acumatica sales documents, then writes carrier and tracking back to Walmart once the order ships. Inventory and pricing flow the other way: Acumatica stock-item quantities and prices push to Walmart through bulk feeds so listings stay current. Settlement data flows from Walmart into Acumatica, where reconciliation reports covering payouts, fees, and refunds post against the right GL accounts. SKU and price mapping is aligned so every order line and inventory update references an item that exists on both sides.

How ml-connector handles it

ml-connector stores both credential sets encrypted, requests a fresh Walmart token before the 15-minute expiry, and sends WM_SEC.ACCESS_TOKEN plus WM_SVC.NAME on every Walmart call. On the Acumatica side it accepts the full tenant URL and the exact endpoint version per customer, since a mismatched version returns 404, and it wraps every field value in the required value object. Because Walmart single-item APIs are throttled to as little as 100 price updates per hour, inventory and price changes are submitted as MP_ITEM, inventory, and price feeds, then polled by feed ID for results. Walmart orders are read from the released-orders endpoint within the 180-day window and acknowledged before shipment, while each Walmart SKU is mapped to an Acumatica InventoryID so sales lines resolve correctly. Walmart returns HTTP 429 under its token-bucket limits and Acumatica throttles near its license tier, so ml-connector backs off with jitter and retries. Every record carries a full audit trail and can be replayed if a downstream call fails.

A real-world example

A mid-sized consumer-goods seller runs Acumatica Cloud ERP for inventory, pricing, and finance, and sells several hundred SKUs on Walmart Marketplace. Before the integration, staff exported Walmart orders to a spreadsheet and keyed them into Acumatica by hand, updated Walmart inventory and prices manually as stock moved, and pieced Walmart payouts together against the ledger at month-end. Oversells happened when a Walmart listing showed stock that Acumatica had already committed elsewhere. With Acumatica and Walmart Marketplace connected, released orders become Acumatica sales documents automatically, stock and price feeds keep the listings accurate, and settlement reports reconcile against GL accounts, so the manual re-keying and the oversell risk are gone.

What you can do

• •Pull released Walmart Marketplace orders into Acumatica as sales documents and write tracking back after shipment.
• •Push Acumatica stock-item quantities to Walmart through inventory feeds to keep listings accurate and reduce oversells.
• •Sync Acumatica prices to Walmart through bulk price feeds instead of the throttled single-item endpoint.
• •Reconcile Walmart payouts, fees, and refunds against Acumatica GL accounts from the settlement reports.
• •Map each Walmart SKU to its Acumatica InventoryID, with retries and a full audit trail on every record.

Questions

Which direction does data move between Acumatica and Walmart Marketplace?

Orders and settlement data move from Walmart Marketplace into Acumatica, where orders become sales documents and reconciliation reports post against GL accounts. Inventory and pricing move from Acumatica out to Walmart through bulk feeds. Tracking and shipment status are written back to Walmart once an order ships, while Walmart reconciliation reports are read-only.

How does the integration deal with Acumatica's version-locked endpoints and lack of push?

ml-connector accepts the full Acumatica instance URL and the exact endpoint version per customer, because a version that does not match the running ERP release returns HTTP 404 immediately. Since Acumatica cloud offers no guaranteed push for connectors, it polls on the LastModifiedDateTime filter on a schedule you control and stores a high-water mark between runs.

Why does ml-connector use Walmart feeds instead of single-item updates?

Walmart's single-item sync calls are aggressively throttled, with price updates capped at about 100 per hour, and Walmart documents them as for emergency use only. ml-connector submits inventory and price changes as bulk feeds and polls each feed by its ID for results, which respects Walmart's rate limits and scales to a full catalog without hitting 429 errors.