Walmart as a Channel
June 27, 2026
Summary
The Walmart channel in Flxpoint publishes listings, syncs price and quantity, imports orders, and sends tracking back via Walmart's Marketplace API. Connect with a Client ID and Client Secret from your Walmart Developer Center; a separate Walmart Canada connection is also supported, with its own publish format and a required post-publish quantity sync.
What this integration does
Publish Listings
Creates new Walmart listings from your Flxpoint product data – Description, GTIN/UPC, Title, Images, Price, Weight and Category.
Sync & Link Listings
Links your Flxpoint listings to their Walmart listings, then keeps Price, Quantity and SKU in sync (includes Auto Delist).
Get Orders
Imports new Walmart orders into Flxpoint – addresses, line items, totals and timestamps.
Sync Orders
Sends carrier, method and tracking back to Walmart once the order is fully shipped.
How to connect - credentials you need
Open Sales Channels, click +, choose Walmart and name the channel. On the credentials step, select Walmart as the Integration Type, create a New Connection, paste your Client ID and Client Secret, then click Save and Proceed.
Client IDRequired
Generated in your Walmart Developer Center. Go to API Keys → Add New Key for a Solution Provider, select Flxpoint as the Solution Provider, grant Full Access to Content, Inventory, Price, Orders, Returns, Fulfillment, Settings and Shipping, then copy the Client ID.
Open developer.walmart.com
Client SecretRequired
The secret paired with your Client ID from the same Walmart Developer Center API key. Copy it alongside the Client ID and paste both into the Flxpoint connection.
Shown when the API key is created – store it securely.
Consumer Channel TypeSetting
Walmart Canada only. Note your Consumer Channel Type value from Walmart and enter it so the Walmart CA connection routes correctly.
Only needed for Walmart Canada connections.
Don't see API Keys in your Walmart Developer Center? Ask your Walmart account admin to grant access or to create the Client ID and Client Secret for you.
Important - read before configuring
Auto Delist can "retire" items on Walmart – not just hide them
When Auto Delist is enabled and a SKU hits zero quantity, Flxpoint calls Walmart's delist endpoint, which in some cases sets the item to a Retired lifecycle state. Retired items can't simply be re-published – you must run the un-retire override job in Flxpoint first. Turn Auto Delist off if you don't want this behavior.
New listings may need a separate quantity sync after the first publish
After the first successful publish, a brand-new listing can show 0 quantity until a separate inventory/quantity sync runs from Flxpoint – publish and quantity sync are two distinct operations. If the item was already live on the store before the publish, quantity updates right away; if it's a new listing, quantity is picked up on the next scheduled sync instead. This applies to both Walmart Canada and Walmart US. Note: this behavior is specific to this channel and may not apply on other marketplaces.
"keyFeatures requires 3 entries" blocks publish on Walmart US
Walmart US requires a minimum of 3 Key Features for most item specs. Flxpoint can auto-build them from the product description, but only when there's enough content to split into 3 bullets. If auto-generation fails, map your own Key Feature / aspect field with at least 3 values in the Publish Listings template.
"Published" in Flxpoint doesn't mean live on Walmart
Flxpoint marks a listing Published when Walmart accepts the feed submission – not when the item goes live. New listings can take up to 24 hours to appear on Walmart.com. If an item is Published in Flxpoint but still invisible after 24 hours, check the Walmart feed/item report for item-level errors that silently rejected it.
Mapping - fields to know
| Flxpoint Field | Maps To (Walmart) – Notes |
|---|---|
| Listing Parent → Description | → Description. Required. Parent or variant description; HTML is split to build the keyFeatures array. |
| Listing Variant → GTIN / UPC / EAN | → Product ID. Required (one valid identifier). Ensure valid length; pad 11-digit UPCs to 12 with a leading-zero rule. |
| Listing Parent → Brand | → Manufacturer / Brand. Required. |
| Listing Variant → Weight | → Weight. Required – weight is mandatory to publish. |
| Listing Variant → List Price | → Item Price. Required. Your selling price on Walmart; use rules to round or guard MAP. |
| Listing Parent → Category (Walmart) | → Category / Aspects. Required. Sub-category must match Walmart's taxonomy; Walmart Canada may auto-assign the final category. |
| Listing Variant → SKU | → SKU. Required. Primary item identifier. |
| Images (Parent / Variant) | → Images. Required. Provide at least one valid image URL. |
| Flxpoint Field | Maps To (Walmart) – Notes |
|---|---|
| Listing Variant → List Price | → Item Price. Required. Use rules for pricing adjustments or rounding. |
| Listing Variant → Quantity | → Quantity. Required. Reflects available stock; enable Auto Delist to remove sold-out items. |
| Listing Variant → SKU | → SKU. Required. Primary match key for Linking Priority – add rows (usually SKU ↔ SKU) that Flxpoint tries top to bottom until a match is found. |
| Walmart Field | Maps To (Flxpoint) – Notes |
|---|---|
| Walmart Customer Order ID | → Order → Order ID. Required. Primary order identifier. |
| Order Date | → Order → Date Created. Required. Also used for Ordered On. |
| Shipping Method | → Order → Channel Shipping Text. Map to your shipping names (Value, Standard, Two Day, etc.). |
| Total Price / Total Tax / Shipping Total | → Invoice → Total / Tax / Shipping Cost. Totals shown on the order invoice. |
| Addresses (Address1/2, City, State, Postal, Country, Phone, Ship Name) | → Billing & Shipping Address fields. PII is redacted after your configured retention window. For Canada, map the postal FSA to the correct province/territory code. |
| Order Item → SKU / Quantity / Item Price / Title | → Order Line Item → SKU / Quantity / Price / Title. SKU & Quantity required; hidden characters in SKUs are cleaned automatically. |
| Flxpoint Shipment Field | Maps To (Walmart) – Notes |
|---|---|
| Carrier | → Carrier Name. Required. Must match a Walmart-accepted value (UPS, FedEx, USPS, DHL). |
| Method | → Shipping Method. e.g. Ground, Standard. |
| Tracking Number | → Tracking Number. Required. Primary tracking identifier. |
| Tracking URL | → Tracking URL. Direct link to the carrier's tracking page. |
| (Optional) Intent to Cancel Override | → Intent to Cancel Override. US-specific; only map if your workflow requires it. |
| (Optional) Ship From Country | → Ship From Country. "US", "CA", etc., when needed. Only fully shipped orders are eligible – partial shipments aren't supported. |
Common issues
"'productName' is a required attribute. Enter value for the attribute 'productName'. | IB_MISSING_ATTRIBUTE"
productName (the item's title/name in Walmart's spec) isn't mapped in your Publish Listings template. Map your Title or Product Name field to the productName Walmart attribute. It's required for every Walmart item type, even when a matching item already exists on Walmart.com.
"Product ID is invalid. Ensure GTINs are 14 digits and UPCs are 12 digits" – but the UPCs look correct
Walmart validates UPC check digits, not just length. The value usually has a bad check digit, a leading zero stripped on import, or is a proprietary internal code not registered with GS1. Use a rule to pad 11-digit UPCs to 12 with a leading zero; if the identifier is genuinely invalid you'll need a valid registered GTIN/UPC or a Walmart GTIN exemption.
"expected minimum item count: 3, found: 1 for keyFeatures | IB_ARRAY_MINITEMS"
Walmart requires at least 3 values in the keyFeatures array for affected item specs. If the description is too short for Flxpoint to auto-generate 3 bullets, map a Key Features / aspect field with at least 3 distinct bullets in the Publish Listings template. This commonly affects only a subset of variants where description content varies.
Publish shows a category error – products won't list
Walmart requires the sub-category to match its taxonomy exactly; a generic or parent-level category is rejected. In the Publish Listings template, verify Category maps to a valid Walmart sub-category. For Walmart Canada, republish using the current JSON feed format so Walmart CA can auto-assign the final category, which resolves most "invalid category" errors there.
"Could not find Carrier Name for: UPS" on Sync Orders
The carrier value doesn't match a Walmart-accepted carrier code. Walmart expects specific values (UPS, FedEx, USPS, DHL). Add a carrier-name normalization rule in the Sync Orders template to translate values like "United Parcel Service" or "UPS Ground" to the exact string Walmart accepts. If the carrier isn't on Walmart's list, use "Other" with a valid tracking URL.
Walmart Canada products show 0 quantity after a successful publish
On Walmart CA the Publish job submits item content only – it does not push inventory. After publish completes, run a separate Sync & Link Listings (inventory/quantity) job from Flxpoint to push current stock levels. This is a required two-step process for new Walmart Canada listings.
Thousands of listings not syncing even though the sync jobs run successfully
When sync jobs finish without errors but a large batch isn't updating on Walmart, the affected SKUs are usually not linked. Run Link Listings (Sync & Link) first so they're matched between Flxpoint and Walmart. Also check for hidden listings – hidden items are skipped silently during quantity sync and need the hidden-listing setting disabled before they can receive updates.
FAQs
What credentials do I need to connect Flxpoint to Walmart?▸
A Client ID and Client Secret from your Walmart Developer Center account. Go to developer.walmart.com, open API Keys, and add a new key selecting Flxpoint as the Solution Provider. Grant Full Access to Content, Inventory, Price, Orders, Returns, Fulfillment, Settings and Shipping. For Walmart Canada, also note your Consumer Channel Type value.
Does Flxpoint support partial shipment syncing to Walmart?▸
No – Sync Orders only supports fully shipped orders; partial shipments aren't sent. Hold the sync until every item in the order has shipped, then run Sync Orders to push carrier, method and tracking number to Walmart in a single update.
How do I handle MAP pricing on Walmart?▸
There's no dedicated MAP/MSRP field in the Publish Listings or Sync Listings template, but MAP can still be mapped if needed – map the "MAP" value from another available pricing dropdown field, or add a mapping rule that pulls the MAP value from the same pricing mapping. To enforce MAP, use a pricing rule that sets Item Price equal to your MAP floor or blocks prices from falling below it. Alternatively, configure Walmart's Repricer in Seller Center – Flxpoint sends the base Item Price and Walmart applies the repricer adjustments on their side.
Orders aren't importing – which statuses should I select in Get Orders?▸
By default, new unshipped Walmart orders arrive with a Created status. If only "Shipped" is selected in your Get Orders settings, new orders won't import. Select at least Created and Acknowledged to capture incoming orders, and confirm the "Fetch Orders for the Last X Days" window is wide enough to cover the dates you expect.
What is Fulfillment Lag Time and when is it required?▸
Fulfillment Lag Time is the number of days between when an order is placed and when it ships. It's required for Walmart Canada and recommended for Walmart US to avoid SLA violations. Set it to match your actual operational lead time – for next-business-day shipping, use
1. An invalid or out-of-range value causes offer rejections.Why are hidden listings blocking my quantity sync?▸
Walmart does not accept quantity updates for listings in a hidden state – the sync returns an error for those SKUs. If specific listings repeatedly fail quantity sync, check whether they're hidden on Walmart. Disable the hidden-listing setting in Flxpoint for those SKUs (or delist and republish them) so they can receive updates again.