Walmart Store Management
Walmart Store Management connects Odoo with Walmart Marketplace while keeping provider-facing claims tied to current source, executed tests, and the Walmart API contract.
| Odoo versions | 17.0, 18.0, 19.0 (Community or Enterprise) |
| Current source versions | 17.0 → 17.0.2.5.1, 18.0 → 18.0.2.5.1, 19.0 → 19.0.2.5.1 |
| Odoo code licence | OPL-1 |
| Runtime licence dependency | None — the connector installs and runs without an ECOSIRE licence-client add-on or key check |
| Live demo | walmart.demo.ecosire.com |
What is proven
- OAuth 2.0 client-credentials token exchange against Walmart's
/v3/tokencontract. - Marketplace requests use
WM_SEC.ACCESS_TOKENand the contract-required Walmart headers; the connector does not replace this with plain Bearer authentication. - Credentialed contract evidence for Items, Item Taxonomy, Item Spec, and MP_ITEM feed submission with per-item ingestion-result polling.
- Provider-shaped automated tests for order import, masked buyer derivation, pagination, multi-company isolation, dashboard calculations, and failed/partial sync reporting; the public demo also has fresh desktop and mobile browser-smoke evidence.
- Odoo operator surfaces for configurations, products, orders, order-derived customers, feeds, queues, logs, mappings, and a company-scoped dashboard.
- Pulled Datasets: one action in the configuration reads every documented read family and stores each answer verbatim, with the route it came from, on a screen you can audit line by line.
What changed in 2.5.0 and 2.5.1
2.5.0 widened the reachable surface to the whole documented Walmart API — seller performance, listing quality, item health, WFS inbound shipments and labels, MCS fulfilment orders, claims and their documents, returns overrides, the report centre, assortment recommendations, GTIN exemptions, lag time, rule exceptions, shipping reference data and the webhook subscription lifecycle — and added the Walmart Connect (advertising) client, the Pull Documented Datasets action and its screen, the documented feedType for the bulk price feed, and company-currency formatting on the dashboard.
2.5.1 fixes the Pull Documented Datasets button. It reads seven families and calls each one by name; the reference-data family was named but had never been written, so the run stopped the moment it reached that entry — after three families had already been stored, which made the families after it look as though Walmart had returned nothing. The reference family now exists and reads the seller's lag time, the current rule exceptions and Walmart's shipping reference data (ship nodes, shipping utilities, taxonomy departments and shipping templates).
Honest demo boundary
The public demo contains sanitized local records. It does not contain a seller's credentials, does not claim to be connected to a live Walmart account, and does not trigger provider mutations. The read-only walkthrough exposes the dashboard, products, orders, masked buyers, feed outcomes, and sync logs while keeping imports, connection testing, and configuration manager-only.
The current contract still lacks recorded live calls for these 11 endpoint families: claims, fulfillment, insights, inventories, inventory, price, promo, report, reports, returns, and webhooks. Some corresponding local models or guarded methods exist in the module, but they are not presented as live-proven demo flows.
Installation
- Download the ZIP matching your Odoo major version.
- Extract the single
walmart_store_management/directory into an Odoo addons path. - Install the Python
requestspackage in the interpreter that runs Odoo. - Restart Odoo, update the Apps list, and install Walmart Store Management.
The module depends only on standard Odoo apps: Sales, Inventory, Accounting, Delivery, Mail, Web, Products, and Contacts.
Connection setup
Create a Walmart configuration, choose the market (us, ca, mx, or cl), enter the Walmart Client ID and Client Secret, and use Test Connection. Keep automatic synchronization disabled until the connection succeeds and mappings have been reviewed.
Walmart's current official flow uses Basic client credentials to obtain a short-lived token, then sends that token in WM_SEC.ACCESS_TOKEN on Marketplace calls. See Walmart's Token API guide.