SAP Business One and Walmart Marketplace integration

What moves between them

Orders flow from Walmart Marketplace into SAP Business One as PurchaseOrders (if inbound) or SalesOrders (if outbound), mapped to matching BusinessPartners by Walmart seller account. Inventory quantities flow in both directions: SAP item stock levels push to Walmart via bulk inventory feeds on a schedule you control, and Walmart order fulfillment updates pull back into SAP to decrement on-hand. Pricing changes in SAP Items flow to Walmart via bulk price feeds. Reconciliation reports from Walmart (settlement amounts, payouts, fees) are available for pull but do not write back to SAP, since financial posting is SAP's responsibility. Syncs run on a daily or weekly cadence tied to your fulfillment and reconciliation cycles.

How ml-connector handles it

ml-connector stores the SAP customer Service Layer URL and Walmart OAuth credentials encrypted. On startup, it acquires a Walmart access token via Client Credentials and holds the SAP session token returned after B1SESSION login; both are refreshed before expiry (Walmart at 15 minutes, SAP before the 30-minute inactivity window). Walmart order webhook events trigger order creation in SAP; if webhooks are not enabled, ml-connector polls the Orders endpoint every 1-4 hours. Each Walmart order's seller is matched to a BusinessPartner in SAP by matching seller account identifiers, or manually mapped if no match exists; unmapped orders are held in a queue for manual review. Inventory feeds from Walmart push quantity into a staging table where ml-connector matches by SKU to SAP Items, accounting for multiple Walmart ship nodes and a single SAP warehouse. Price feeds from SAP Items use the bulk feed mechanism to avoid Walmart's single-item throttle (100 updates per hour). SAP session tokens can expire mid-request (-5002 error), so ml-connector re-authenticates and retries the request; Walmart 429 rate-limit responses trigger exponential backoff. Every record carries a full audit trail and can be replayed if a downstream write fails.

A real-world example

A small-to-midsize retailer runs SAP Business One on-premise for inventory, purchasing, and accounting, and sells through Walmart Marketplace to reach additional volume beyond their direct channels. Before the integration, the operations team manually pulled orders from Walmart and entered them into SAP as purchase records, then separately updated inventory and shipping status by hand after each fulfillment. With SAP Business One and Walmart Marketplace connected, each order from Walmart automatically becomes a record in SAP mapped to the correct supplier or sales order, inventory in SAP is the source of truth for what is available on Walmart, and when the operations team marks an order shipped in SAP, the shipment notification flows back to Walmart. Month-end reconciliation between Walmart payouts and the revenue booked in SAP now requires a simple variance check rather than reconstructing the flow by hand.

What you can do

• •Import Walmart orders into SAP Business One as PurchaseOrders or SalesOrders mapped to matching BusinessPartners.
• •Push inventory quantities from SAP Items to Walmart in bulk feeds, accounting for multiple ship nodes.
• •Sync pricing updates from SAP Items to Walmart via bulk price feeds to avoid single-item API throttles.
• •Refresh Walmart OAuth tokens every 15 minutes and SAP session tokens before the 30-minute inactivity timeout.
• •Maintain a full audit trail and replay failed writes when Walmart or SAP connectivity resumes.

Questions

How does ml-connector map Walmart seller accounts to SAP BusinessPartners?

ml-connector matches Walmart seller IDs to a SAP BusinessPartner custom field you designate during setup, or allows manual mapping if no match is found. Orders with unmapped sellers are held in a queue for manual review. Once mapped, all future orders from that seller automatically link to the correct BusinessPartner.

What happens when SAP session tokens expire or Walmart OAuth tokens time out?

SAP session tokens expire after 30 minutes of inactivity and Walmart OAuth tokens after 15 minutes. ml-connector refreshes Walmart tokens proactively every 15 minutes and re-authenticates to SAP before the inactivity window closes. If a request fails with a token error, ml-connector re-authenticates and automatically retries the operation.

Can ml-connector handle Walmart's 100-item-per-hour single-price-update limit?

Yes. ml-connector uses Walmart's bulk feed mechanism for price updates instead of single-item calls, avoiding the throttle entirely. Feeds are processed asynchronously and can update thousands of prices per day without hitting the per-item rate limit.