If you sell on Walmart Marketplace and run ERPNext as your system of record, the gap shows up fast. Orders land in Seller Center but not in ERPNext, so someone re-keys them into Sales Orders and inevitably fat-fingers a quantity or a ship-to address. Available-to-promise quantities drift between your ERPNext warehouses and what Walmart shows, which triggers oversell penalties and OTDR (on-time delivery rate) hits. Price and promotion changes get made twice. And WFS inbound shipments live in a spreadsheet nobody trusts. ERPNext core has no Walmart concept at all — there is no Marketplace API client, no WFS inventory feed, and no order polling built into erpnext, so out of the box every one of those flows is manual.

We build a proper Frappe app — not a pile of bench execute scripts — installed alongside erpnext on your bench. It ships its own module with DocTypes such as Walmart Settings (a Single that holds Client ID, encrypted Client Secret, and channel config), Walmart Order and Walmart Order Item (child table) for the raw payload and mapping state, Walmart Item Map to tie a Walmart item ID / GTIN / SKU to your ERPNext Item, and Walmart Sync Log for a full audit trail. Authentication uses Walmart's OAuth 2.0 token-signature flow with WM_SEC.ACCESS_TOKEN and WM_QOS.CORRELATION_ID headers, and the token is cached and auto-refreshed so no scheduled job ever ships with a stale credential.

Order ingestion runs on a scheduler_events cron (configurable, e.g. every 10-15 minutes) that pulls released Walmart orders and, on a mapped match, creates the ERPNext Sales Order — customer, shipping address, item lines, and Walmart-specific fields — inside an idempotent transaction so a repeated poll never double-books. Inventory flows the other way: hooks.py doc_events on Bin, Stock Ledger Entry, and Item enqueue a background job (frappe.enqueue) that pushes the net available quantity to the Walmart inventory feed, with WFS-fulfilled SKUs handled separately so you don't fight Walmart's own fulfillment counts. Price and promotion pushes, shipping label / tracking writeback (acknowledge, ship, and post tracking numbers back to Walmart from the ERPNext Delivery Note or Shipment), and an item-setup feed that publishes new ERPNext catalog items to Walmart all run through the same queued, retry-aware, rate-limit-respecting pipeline. Whitelisted methods (@frappe.whitelist()) expose manual re-sync and a callback endpoint; a dedicated role profile and DocType permissions keep the connector's actions scoped and out of your general users' hands. Optional client scripts add re-sync buttons and status indicators right on the Sales Order and Item forms.

Because this is build-to-order, nothing is guessed. We start with a short scoping call to map your Walmart channels, WFS usage, ERPNext warehouse and pricing-rule setup, and edge cases (bundles, kits, multi-warehouse ATP). We build the app to that spec, run it against your data on a staging bench through UAT, then install on production with a rollback plan. You receive the full source code for your ERPNext version (v15 or v16), install and config documentation, an admin user guide, a live training session, and a post-go-live support window. Typical delivery is one working week from confirmed scope, depending on how many of the five flows you enable and how custom your catalog mapping is.