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, 20.0 (Community or Enterprise) |
| Current source versions | 17.0 → 17.0.2.5.4, 18.0 → 18.0.2.5.4, 19.0 → 19.0.2.5.4, 20.0 → 20.0.2.5.4 |
| 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.4
2.5.4 makes Walmart webhooks work and hardens the connector against the failure cases real stores hit. (2.5.2 and 2.5.3 were never published; their changes ship in 2.5.4.)
Walmart webhooks work. Walmart's event notifications used to be refused
every time, so nothing they reported reached Odoo. Each delivery is now checked
before anything happens: HTTP Basic credentials for order, offer, Buy Box,
inventory and report events, or Walmart's WM_SEC signature for
seller-performance events, inside a bounded replay window. A checked delivery
runs the sync for the event Walmart actually sent, is processed once even when
Walmart sends it again (one successful delivery per eventId), and is kept on
a delivery log with Walmart's own payload. A delivery that cannot be checked is
still answered with HTTP 403 and nothing in it is used. Subscriptions are
created, paused, resumed, tested and deleted from Odoo, the event list is
Walmart's own (existing records are moved over on upgrade), and a Walmart
manager who is not a system administrator can create them. See
Webhook subscriptions.
Each Walmart account keeps its own customers. Customer sync matches a Walmart customer only against contacts bound to the syncing store (then older unbound contacts), so a second Walmart account can never rewrite the first one's contact.
Imported records are bound to the store that produced them. Products, orders and buyers imported from Walmart now carry the store configuration they came from, and a re-import resolves against that binding before it falls back to older unbound rows. A seller running two Walmart accounts that expose the same SKU or order id no longer has one account's import overwrite the other's record.
The financials are complete and honest. Walmart reports order money as typed charges; shipping, tax and platform-, seller- and co-funded discounts are now stored as distinct values — including when they are zero, because "not charged" and "not captured" are different facts — with the raw breakdown preserved so an unfamiliar charge type stays recoverable. A cross-currency order whose currency has no exchange-rate evidence is refused rather than restated at parity, and the dashboard totals are grouped by the order's own currency: a currency that cannot be converted is named instead of being added at parity.
Settlement reports can be ingested and reconciled. Settlement lines carry shipping, discount and reward buckets distinct from commission, fees, tax and refunds; a report's own rows are classified with their raw type preserved; refund rows create reconcilable refund records; and a settlement whose lines do not explain its reported total, or which carries no currency, refuses to reconcile rather than rounding the difference away.
A historic order can be corrected. Re-importing an existing order used to mark it done and move on, so a mapping fix or a corrected exchange rate could never reach an order imported months ago. An existing order is now reprocessed in place, and its lines are matched and updated rather than duplicated.
A manual import template that round-trips. The import wizard can download a CSV template and import the populated file. The template's columns and the importer's columns are one definition, so the downloaded file can never omit a column the importer requires.
The current day is included in the dashboard totals, the store counters now describe the catalogue rather than the number of syncs, a rejected token request no longer echoes the credential back, and a bare image reference is resolved through the documented item endpoint rather than being fetched as if it were a URL.
Newly visible and newly refused. The marketplace identity and the sync, finance and imagery evidence are visible on the product, order and contact forms; Walmart item ids, SKUs, barcodes and order identifiers are searchable; and each connector action binds its own list view. Affiliate attribution, the affiliate wire contract and creator-profile refresh are refused explicitly with their reason — Walmart's Marketplace Seller API documents no affiliate or creator endpoint, so an empty result would have been indistinguishable from "there is no attribution data".
The dashboard's shortcuts open the right screens. The Orders, Products and Customers tiles pointed at screens that did not exist, so clicking them did nothing; they now open the imported orders, products and customers, and the Queue tile opens the pending queue records it counts. The Order Status chart is drawn from the real order data, both charts say so when there is nothing to plot, and loading and error states are shown at the top of the page with a Retry button. The dashboard also follows Odoo's dark theme and keeps the store name inside the header on a phone.
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.