Elbuz connects to your Walmart Marketplace (US) seller account with a Client ID and Client Secret: it imports products and orders, acknowledges orders on Walmart, and sends back prices and stock.
When you need this:
- You sell on Walmart and elsewhere: all marketplaces' stock and orders live in one catalog.
- You fear missing an acknowledgment: Elbuz acknowledges new orders itself.
- Prices change often: a run's changes go in one feed, within Walmart's hourly limit.
- You list new products: a barcoded product becomes an offer on an existing Walmart page or a new one.
Where to start: create keys in the Walmart Developer Portal and paste them into a “Walmart” template.
What the Walmart connection can do
- Connection with your own keys: Client ID and Client Secret from the Developer Portal.
- Product import: name, SKU, barcode, price, stock, category.
- Orders: the last 30 days on the first run, then only changes; new orders are acknowledged on Walmart automatically.
- Prices and stock back to Walmart: one feed per run, or separate requests when there are few products.
- New products: an offer on an existing product page by , or a new product page based on a mapped Walmart product type.
Where to get Walmart keys
The seller creates API keys in the Walmart Developer Portal. The portal is in English only, so the item names below are as they appear there.
- Open developer.walmart.com and sign in with your Seller Center account.
- Go to API Keys (key management) and choose the keys for the live environment: Production Keys.
- Copy the Client ID and Client Secret. The full Secret is shown only when the key is created or reset.
- In the “Walmart” template, paste the Client ID into the “Client ID” field and the Client Secret into the “Client Secret” field. Save the template. “Active” and “Orders” are already on in a new template: within 5 minutes of saving, Elbuz starts fetching orders for the last 30 days and acknowledging them on Walmart. Elbuz maps marketplace statuses to yours automatically, by name; the template's “Order statuses” window shows what came in and how it was mapped. Want to check first? Clear “Orders”.
- Click “Test connection”. If the keys are correct, you'll see “Connection works. Walmart US”.
1
Client ID field2
Client Secret field- Client ID field — paste the Client ID from the Walmart Developer Portal here.
- Client Secret field — the secret half of the key; it is hidden after saving.
Keys from the Walmart test environment (Sandbox) don't work with a live account: Elbuz calls the live Marketplace API. If you reset or reissued the Client Secret in the portal, paste the new one into both the import and the export template; otherwise both stop with an authorization error.
Walmart's documentation for sellers: Walmart Marketplace API — Get started. It explains how to get keys and which request limits apply.
What comes into the catalog
Elbuz pulls your Walmart product list in pages of a thousand, then requests stock for each SKU separately. Each product lands in the catalog as a card linked to its SKU; prices and stock travel by this key later.
| Walmart data | Product field in Elbuz |
|---|---|
| product name | Name; if Walmart returned no name, a new product gets the SKU as its name |
| seller SKU | SKU |
| GTIN or UPC | Barcode; a 14-digit GTIN with a leading zero becomes a 13-digit EAN |
| price, USD | Price, as a number, with no currency conversion |
| SKU stock | Quantity |
| publication status | Status: published means an enabled product, anything else means disabled |
| shelf or product type | Category |
Walmart doesn't return descriptions, manufacturers, specifications or photos in the product list. The “Photo”, “Manufacturers” and “Attributes” checkboxes add nothing in a Walmart template. Fill these fields in Elbuz or pull them from another source, such as a supplier price list.
The price arrives in dollars and goes into the “Price” field as is. If your catalog's main currency isn't the dollar, the card will hold a dollar amount with no currency mark.
Categories
A Walmart shelf is a path, for example “Home / Kitchen”. Elbuz looks in the tree for a category with that name, starting from the deepest level, and if none is found, creates the branch “Home” → “Kitchen”. A product without a shelf gets a category named after its Walmart product type.
Products with no category at all land in the service category “Products - walmart”. It's created disabled and excluded from exports, so these products go nowhere until you sort them into your own categories. How to remove a service category safely: service categories and brands.
What a repeat run overwrites
A repeat import finds its card by SKU: Elbuz remembered the link on the first run. A product that isn't linked yet is looked up by name, and only then is a new one created.
| What the run does | Fields |
|---|---|
| Overwrites with Walmart data | name, SKU, barcode, price, quantity, the “enabled” flag |
| Leaves as is | description, manufacturer, old price, tags, photos, specifications, position in the category tree |
| Doesn't touch quantity | if the SKU stock request failed, the previous quantity stays |
If you correct a name in Elbuz, the next catalog run brings back the Walmart name. The Walmart template has no separate “don't update name” checkbox. There are two ways to stop marketplace names from coming in:
- turn on “Do not update” on the product card, in the “Import protection” group: the run won't change anything on the card;
- after the first import, clear the “Products” checkbox and leave only “Orders”: the SKU links are kept.
The “Fixed Price” switch in the same group protects the price from being overwritten: other fields update, the price stays yours.
A product that isn't in the “published” state on Walmart (removed, under review, with an error) becomes disabled in Elbuz after the run. A disabled product isn't included in exports to other channels. If you sell it elsewhere, lock the card with the “Do not update” switch.
The import doesn't touch a product that wasn't in the run: it keeps its last price and stock and isn't deleted. Remove discontinued items by hand.
How orders arrive and get acknowledged
The first run picks up orders created in the last 30 days. After that, Elbuz takes only what changed since the previous run, with a twelve-hour margin. An order is recognized by its Walmart number (purchase order) and updated rather than duplicated.
The “Customer order” document gets:
- the customer order number, creation and last-change dates, the Walmart status;
- the recipient's first and last name, phone, and the buyer's email: it's a Walmart relay address, and emails to it are forwarded to the buyer;
- the shipping address: street, city, state, ZIP code, country;
- the Walmart shipping method (for example, Standard or Express) in the “Delivery service” field;
- line items by SKU with price and quantity, currency USD.
Automatic acknowledgment on Walmart
A new Walmart order has the status Created and waits for the seller to acknowledge it. Elbuz acknowledges such orders by itself, right after saving them to the database, so an order that wasn't saved is never acknowledged.
In the log, the summary looks like this: “Walmart: orders loaded: 12 (acknowledged on Walmart: 3)”. The first number is all orders in the run, the second is the new ones acknowledged just now.
Statuses
The status arrives as a Walmart code: Created, Acknowledged, Shipped, Delivered, Cancelled. Elbuz maps Shipped, Delivered and Cancelled to your statuses by itself, while Created becomes “New” and Acknowledged becomes “Confirmation”; you can adjust this with the “Order statuses” button in the “Related settings” card.
1
Order statuses2
Schedule setup- Order statuses — match Walmart statuses with your own.
- Schedule setup — set when the import runs.
Other repeat-run rules are shared with other marketplaces: your status changes only when the Walmart status changed, the address and line items are written once, and the run doesn't write to a posted document. Details: what a repeat run does with an order. A reservation for the order appears after the document is posted (order, stock and reservation).
How prices and stock go back to Walmart
The reverse direction is a separate export template of type “Walmart” with the “Products” checkbox in the “What to export” card. Keys go into its “Client ID” and “Client Secret” fields. Elbuz learns product SKUs from the catalog import, so import the catalog from Walmart once first, then set up the export.
Hourly feed limit
Walmart accepts price and stock updates as feeds, files with many products, and allows about 10 such feeds per hour. So Elbuz works like this:
| Linked products in the run | How it goes to Walmart |
|---|---|
| up to 10 | Separate price and stock requests for each product. The result is immediate: “Walmart: prices and stock updated, items: N (errors: M)” |
| more than 10 | One price feed and one stock feed for the whole run. The log shows “price feed sent” and “inventory feed sent” with the feedId |
Walmart doesn't process a feed right away. Elbuz waits about 15 seconds for the result. If it doesn't arrive, the log shows “… feed is still processing … the result will be collected on the next export”, and the next run first reads that feed, then sends a new one.
Run the Walmart export no more than once every 10 minutes. More frequent runs use up the limit, and Walmart rejects the new feed. Nothing is lost: the next export sends current prices and stock.
Price, currency and markup
Elbuz sends the price as dollars, rounded to cents, with no currency conversion. A price in hryvnias or euros goes to Walmart as the same number, but in dollars.
If your catalog keeps prices in a currency other than USD, set the export template's price field with a formula using the dollar rate and the markup you need: the “Export fields” button in the export template's “Related settings” card. The formula can use the rate of any currency from the currency list.
Stock goes as a whole number; negative stock is sent as zero. Walmart doesn't accept two products with the same SKU in one run: the second is skipped with the line “SKU … has already been sent for another product”.
Elbuz can't take down or delete products on Walmart: a product that dropped out of the template's filtered set simply stops getting updates. To stop selling, set the stock to zero and wait for the export, or take the product down in Seller Center.
Publishing new products
With “Publish new products” checked, the export template lists on Walmart products that aren't linked to a SKU yet. A barcode is required: GTIN, EAN or UPC, at least 8 digits. The Walmart SKU is your “SKU”, or the Elbuz product ID if it's empty.
What gets created depends on the product's category:
| Product category in Elbuz | What Walmart gets |
|---|---|
| not mapped to a Walmart product type | An offer on an existing product page by barcode. If Walmart has no such page, the item is rejected |
| mapped to a Walmart product type | A full product page: name (up to 200 characters), brand from the “Manufacturer” field, description (up to 4000 characters), up to 10 photos, price, weight, condition. If a page with that barcode already exists, Walmart attaches the product to it |
The product type is set in the “Marketplace Category and Attribute Mapping” window (Directories → Categories → the “Marketplace mapping” tile) on the “Walmart” toggle tab, in the “Walmart product type” column. The type list is loaded with the “Load marketplace dictionary” button once the Walmart import template has keys. General rules for the window: mapping categories to marketplaces.
1
Walmart chip2
Walmart product type column3
Filled product type- Walmart chip — shows the columns of this marketplace only.
- Walmart product type column — whether a new card is sent depends on it.
- The filled product type in the category row.
- Weight is taken from the “Weight” field with its unit (kilograms or grams) and converted to pounds, since Walmart reads weight in pounds. An empty weight is sent as 1 pound.
- Condition is taken from the “Product condition” field: “New” and “Discounted” become new, “Used” becomes used, “Refurbished” becomes refurbished.
- Each product is published as a separate product page, without grouping into variants by color or size.
When the result appears
Publishing also goes by feed, so the result often arrives only with the next export. A product is linked to a SKU only once Walmart accepts the item; while the feed is processing, the product isn't sent again. The summary in the log: “Walmart: new items published: N (errors: M)”.
Elbuz retries an item Walmart rejected (most often, no product page found by GTIN) no more than once a day. Once you fix the barcode or map the category, the product goes out with the first export after the day has passed.
Schedule and limits of one run
Walmart sends no instant notifications, so Elbuz fetches and acknowledges orders by itself every 5 minutes if “Orders” is checked and the keys are filled in. The shared “Marketplace orders” task in the “Job schedule” window does this; the interval is set there. This pass skips the catalog, and orders also picked up by the template schedule aren't duplicated.
The catalog is updated by the template's own schedule — the “Schedule setup” button. Set it to run rarely, for example at night: while the catalog is running, the orders pass is skipped until the next one. Export prices and stock no more than once every 10 minutes.
The “Active” / “Disabled” badge takes the template off the schedule and out of automatic order fetching, as with other sources (disable a template). The export is a separate template with its own switch.
| What | How much |
|---|---|
| Product page / order page | 1000 / 200 per request |
| Writing to the catalog | in batches of 500 products |
| Separate requests instead of a feed | up to 10 products per run |
| Price and stock feeds | about 10 per hour, the Walmart limit |
| Waiting for a feed result within a run | about 15 seconds; the next export reads the rest |
| Retrying a rejected item | no more than once a day |
| Waiting for one response | 120 seconds, 30 for the connection |
The catalog takes longest to import: each SKU needs a separate stock request. To see how long it takes for you, check the “Time spent” column in the template list and “Run history” in the template card header. Repeating a broken-off run is safe: products are found by SKU, orders by number (if a run broke off).
Scenarios
1
Products checkbox2
Orders checkbox- Products — import the item catalog from Walmart.
- Orders — import Walmart orders.
Move Walmart products into Elbuz
What to turn on. Fill in “Client ID” and “Client Secret”, test the connection, and leave “Products” in the “Select data to import” card.
What you get. Each product becomes a card with name, SKU, barcode, price in dollars, stock and a category based on the Walmart shelf. Add descriptions, photos and specifications from another source.
Receive orders without missing acknowledgments
What to turn on. The “Orders” checkbox; Elbuz maps the statuses by itself, and the “Order statuses” button is for adjustments. Orders need no template schedule: they arrive by themselves every 5 minutes.
What you get. New orders arrive as documents and are acknowledged on Walmart right away. A cancellation on Walmart changes the status of an unposted document; a posted one stays as it was.
Manage prices in Elbuz and send them to Walmart
What to turn on. Import the catalog once with “Products” checked: this links cards to SKUs. Then leave only “Orders” in the import template. Create a “Walmart” export template with “Products” checked, set the price in dollars and a schedule of once every 10–15 minutes.
What you get. Each run's changes go in one price feed and one stock feed. The catalog run no longer overwrites your prices with Walmart's numbers.
List new products
What to turn on. “Publish new products” in the export template. Fill in the barcode and SKU on the products. For your own products that aren't on Walmart yet, map their categories to a Walmart product type.
What you get. Products with an existing product page become offers on it; the rest go as full product pages for Walmart review. The link appears once Walmart accepts the item.
What to do when Walmart won't send or accept data
| What you see | Why | What to do |
|---|---|---|
| “Walmart: enter the Client ID and Client Secret from Seller Center or connect the account via Elbuz” | One of the key fields in the template is empty | Paste both keys and save the template (where to get keys) |
| “Connection failed: HTTP 401…” or “Walmart: API error — HTTP 401…” | The key was copied incompletely, it's a Sandbox key, or the Client Secret was reissued | Copy the Production Keys again and paste them into the import and export templates |
| “Walmart: the hourly limit of … feeds is used up … the next export in ~N min will send current prices and stock” | The export runs more often than Walmart allows | Nothing is lost. Run the export less often in the schedule: once every 10 minutes or less (hourly limit) |
| “Walmart: … feed is still processing (feedId …)” | Walmart didn't finish processing the feed during the run | It's not an error: the result appears in the log of the next export |
| “Walmart: … feed processed — succeeded: N, failed: M” and lines “Walmart: SKU … — …” | Walmart rejected some items; the reason is after the dash | Fix the price, stock or barcode on the product and wait for the next export |
| “Walmart: … feed rejected entirely” | Walmart didn't accept the feed file as a whole | Forward the line's text to Elbuz support; the products export with the next run after the fix |
| “Walmart: “…” has no GTIN/EAN/UPC barcode, it cannot be published on Walmart” | Without a barcode, Walmart can't find or create a product page | Fill in a barcode of 8 digits or more on the product (publishing) |
| “Walmart: SKU … has already been sent for another product — “…” skipped” | Two catalog products have the same SKU | Give each product its own SKU |
| “Walmart: could not acknowledge order …” | Walmart refused the acknowledgment; the order is already saved in Elbuz | Acknowledge the order manually in Seller Center so Walmart doesn't cancel it |
| Some products got disabled after the catalog run | On Walmart they aren't in the “published” state | Check their state in Seller Center or lock the cards with the “Do not update” switch (repeat run) |
| Products in the “Products - walmart” category aren't exported | The service category is created disabled | Move the products to your own categories (categories) |
FAQ
Can I connect Walmart without my own API keys?
No. For now the connection works only with a Client ID and Client Secret that you create in the Developer Portal (where to get keys).
Why did products from Walmart arrive without photos or descriptions?
Walmart doesn't return them in the product list. Fill in descriptions and photos in Elbuz or pull them from a supplier price list (what comes into the catalog).
My catalog prices are in hryvnias. Will they go to Walmart in dollars?
They'll go as the same number, but as dollars. Convert the price with a rate formula in the export template (price and currency).
The export finished, but the Walmart price is still old. Why?
Walmart processes feeds with a delay, and the product page doesn't update instantly. The log shows the feed result with the next export (hourly feed limit).
Do I need to acknowledge orders in Seller Center?
No, Elbuz acknowledges new orders by itself during import. Do it manually only if the log says “could not acknowledge” (acknowledgment).
A new product was rejected. When will Elbuz try again?
No sooner than a day after the rejection. Fix the barcode or map the category to a Walmart product type (publishing result).
Where to find it and who has access
- Menu
- Directories → Operations → Data import → new template of type “Walmart”
- Other entry points
- Directories → Operations → Data export: a template for prices, stock and new products
- Access right
- the “Import” window in “Group permissions”
- Have ready
- a Walmart Marketplace (US) seller account, Client ID and Client Secret
One template = one seller account. Keys are pasted separately into the import template and the export template, each into its own fields.
Related topics
- If you need the general import mechanics (schedule, broken-off runs, service categories): data import overview.
- If your categories aren't mapped to any marketplace yet: mapping categories to marketplaces.
- If you also sell on Amazon or Kaufland: connecting Amazon, connecting Kaufland.
- If you receive orders from several marketplaces: importing orders via API.
