Pattern PXM publishes your approved product content to Walmart through Walmart's Marketplace API. Once your Walmart account is connected, you map your PXM attributes to Walmart's product-type templates, then create items and send content, image, price and fulfillment updates whenever they change.
Publishing from PXM keeps your Walmart content consistent with your other channels, without editing items one at a time in Seller Center.
Before you start
Supported accounts: Walmart Marketplace (3P, Seller Center) in the US, Canada and Mexico, and Walmart 1P (Vendor) in the US. Availability can vary by account; check with your Pattern CSM.
Confirm 1P or 3P first: a Vendor (1P) connection can't publish Seller (3P) items, and the reverse. Each Walmart account is its own connection, PXM channel and set of templates.
Who does what: your Walmart admin retrieves your API keys and shares them securely; Pattern creates the connection; then you (or Pattern) set up the channel and templates in PXM.
Your role: setting up channels and templates and publishing need the Admin or Super Admin role. What other roles can do depends on how your account's permissions are set up. See User Roles and Permissions in Pattern PXM.
Only approved values are sent. Draft values don't publish until they're approved, and approving a value doesn't publish it. Someone still has to publish it to the channel.
Only mapped, selected fields are sent. A field reaches the channel only when it's mapped on the channel's template and selected in the job.
No parent listing: on Walmart, each variant is its own item, linked to its siblings by a Variant Group ID. Every variant needs its own complete content.
Step 1: Share your Walmart API keys
Walmart retired Delegated Access, its older way for partners to connect, so new connections use your account's own primary API key. Walmart connections that already work keep working. For Walmart Marketplace (3P), a Walmart admin on your team does this:
Sign in at seller.walmart.com as an Admin and open Settings (the gear icon, top right).
In the settings sidebar, scroll to the API section and click Consumer ID and Private Keys. This opens the API Keys page in the Walmart Developer Portal.
Select the Production Keys tab (not Sandbox). Under My API Key, copy the ClientId and ClientSecret. Use the eye icon to reveal a masked value.
Share the ClientId and ClientSecret with your Pattern CSM through a secure share, along with your region (for example US) and whether the account is Seller (3P) or Vendor (1P).
A banner saying new Delegated Access keys are no longer available is expected. This setup uses your own primary key. Use Reset only if you really need a new secret: it invalidates the old one, so coordinate with your Pattern CSM so the connection is updated the same day.
For Walmart 1P (Vendor), the same Production ClientId and ClientSecret are needed. 1P admins may reach them through their vendor developer path instead of Seller Center. If the ClientSecret isn't visible, the admin needs admin access to the Walmart Developer Portal.
Keep your keys private. Your primary key gives full access to your Walmart account. Treat the ClientSecret like a password, and never paste it into email, chat, support tickets, documents, product fields or templates.
Step 2: Pattern creates the connection
Pattern creates the Walmart connection in Pattern Connect with the keys you shared, then confirms it's active. A live Walmart connection appears as a choice under API Channels when you create a channel in PXM.
Step 3: Create the Walmart channel
In Pattern PXM, open Settings in the left navigation, then go to MARKETPLACES > CHANNELS.
Click CREATE CHANNEL (bottom right).
Under API Channels, choose your Walmart connection.
Choose a Default Media Stack, then create the channel. A default media stack is required. If you don't have one yet, create it under Settings > Assets > Media Stack Group.
Repeat for each Walmart account.
Under each channel name, a green Marketplace · [name] line means the channel is connected through the API, and grey No API connection means a spreadsheet channel. CHANNEL STATUS shows ACTIVE or INACTIVE (No active template). A new channel stays inactive until at least one of its templates is active, and an inactive channel can't be picked when you publish. For more on channels, see Creating a Channel in PXM.
Pre-release view; your screen may differ slightly.
Step 4: Map your product-type templates
PXM holds one Walmart template per product type, built from Walmart's item spec for that product type. Templates are specific to each seller account. Once your connection is live, Pattern adds templates for your product types.
Go to Syndicate > TEMPLATES > API TEMPLATES and filter Channel to your Walmart channel. If a product type has no template, click IMPORT FROM LISTINGS, or ask your Pattern CSM to add it.
Click EDIT on a template. Fields marked with an asterisk (*) are mandatory, and some fields carry a RECOMMENDED tag. Use the search and filters at the top of the template to find fields.
Each row shows the TEMPLATE ATTRIBUTE, EXAMPLE VALUES, the MAPPED ATTRIBUTE and ACTION. Click MAP and choose a PXM attribute, a default value or a media stack position. A dash (—) means the field isn't mapped yet.
Map the core fields. These usually include SKU, the product identifiers (productIdType and productId), fulfillment method, Product Name, Brand, Description, Key Features, category attributes, compliance attributes, count per pack and condition.
Map measurements as separate value and unit fields, for example a shipping height of 550 and a unit of centimeters.
Map images to media stack positions. Position 1 is the main image; map your other images to the template's additional image fields.
Click SAVE TO THIS TEMPLATE to save the mapping on this template, or APPLY TO ALL CHANNEL TEMPLATES to copy the same mapping pattern to the channel's other templates.
Pre-release view; your screen may differ slightly.
A template stays inactive until every starred (*) field is mapped. For a full walkthrough of the template editor, see Channel & Marketplace Templates in PXM.
Mapping tips
Map conditional fields even when they aren't starred. Walmart's spec doesn't flag every conditional field. Products with batteries need Battery Type and Battery Capacity; a warranty URL is needed when the written-warranty field says there's a warranty URL; and Prop 65 warning text is needed when a Prop 65 warning is required.
Visible and Orderable fields: some older templates show two parallel field sets. Use Visible fields for partial updates, and Orderable fields for Create and Full update.
Choose a specific product type. Walmart retired its generic "Other" product type. Products still mapped to Other fail, so choose the specific product type and remap.
Use Pick List attributes with Walmart's allowed values, rather than List attributes.
If you delete an attribute that a template still uses, the job sends a blank value without warning. Check your templates before you clean up attributes.
Step 5: Test, then roll out
Run a Partial update on one or two SKUs, sending one field.
Confirm the job reaches HISTORY, then check the SKU in Walmart Seller Center. The walmart.com product page can take up to about 48 hours to catch up.
Roll out by product type, in jobs of under 100 items.
Publish to Walmart
In Products, select the products you want to send, then click PUBLISH TO CHANNEL (bottom right).
In Channel*, choose your Walmart channel. CONTINUE TO REVIEW stays disabled until a channel is picked.
Complete the publish options: the publish type, the seller account, the template for each product type and the media stack. Labels and order can vary by account.
Select only the fields you're changing. Fields you don't select stay as they are on the channel.
Review the content and fix any errors inline. You can filter the review columns by Required, Recommended or Errored, and use a column's pencil icon to edit down the column.
Submit the job, then follow it under Syndicate > JOBS.
Key Features are all or nothing. Walmart replaces the whole set, so always select every Key Features field, even to change one.
Keep jobs under 100 items. Larger jobs can fail with API errors. Split big batches into several jobs.
Choose the right publish type
Create: a new item (3P, and 1P in the US). Fill every required, category-required and conditional field.
Partial update: content changes such as title, description, Key Features, images and attributes. Include the item's identifiers (SKU, productIdType and productId) in every partial update so Walmart can match the item. Your template may require other fields too, such as Net Content; check its starred (*) fields.
Full update: price or fulfillment changes. A partial update rejects these with "[Field] is not present in the schema and additional fields cannot be added".
Variant groups
Give every variant its own SKU and a real, unique product identifier.
Map variantGroupId with the same value on every variant in the group, and variantAttributeNames with the attributes that differ (for example size or color), plus the variant attribute values your template asks for.
Fill full content on every variant: Key Features, images and description. Content doesn't carry over from one variant to another.
Never type CUSTOM as a placeholder identifier. Variants that share it look identical to Walmart and get flagged or merged as duplicates.
Images
Add the images in order to your Walmart media stack. Position 1 is the main image.
Keep each file under about 5 MB, with a proper file extension and no query string in the URL. PXM doesn't check file size before it sends.
To update images, run a Partial update with the image fields selected.
Walmart can silently drop an oversized or malformed image on a job that shows Accepted. If images don't appear, check the file, then resend.
Check Walmart's current Seller Center image guidelines for size and format rules.
Track your jobs
Syndicate > JOBS has four tabs: DRAFT, ACTION REQUIRED, IN PROGRESS and HISTORY. Filter Channel to your Walmart channel.
A new job can take up to about 10 minutes to appear. Click REFRESH (bottom right) to update the list.
IN PROGRESS means the job was sent and PXM is waiting on Walmart. "0 of N" means it's still processing.
HISTORY holds finished jobs. Expand a job to see PRODUCTS IN THIS JOB and each product's Item Status, or click DOWNLOAD REPORT for the detailed results.
ACTION REQUIRED holds jobs that Walmart rejected in full or in part. A rejected job shows REJECTED with FIX ISSUES: open it, correct the highlighted errors and resubmit.
A job is a snapshot of your content and template when it was created. If either changes afterwards, start a new job.
Accepted isn't the same as live. Check the SKU in Seller Center first; the walmart.com page can take up to about 48 hours.
On jobs with more than 50 items, a few Walmart rejections may not be reported in PXM. Confirm results in Seller Center.
A job can show REJECTED with blank errors while Walmart is still processing it. Don't resubmit; contact your Pattern CSM.
If Pattern manages syndication for you, failed jobs can stay in IN PROGRESS while the Pattern team works on them.
If a job stays IN PROGRESS for more than about 2 hours, contact your Pattern CSM. Regulated categories (for example chemical, aerosol or pesticide products) can take 24 to 72 hours or more in Walmart's compliance review, so allow that time first. Don't resubmit or use FIX ISSUES while a job is still pending; that creates duplicates.
Pre-release view; your screen may differ slightly.
What PXM can't send to Walmart
Automatic syndication and some custom attributes aren't sent through PXM. Upload product videos in Walmart Seller Center. Reviews aren't sent through PXM. PXM isn't an inventory or order system.
Common errors and fixes
First check the basics: the right channel and account type (1P or 3P), an active template for a specific product type, the values are approved, and the field was selected in the job.
A correct value is rejected, or "additional properties not allowed": Walmart updated the item spec. Ask your Pattern CSM to refresh the template (you can also try SYNC MY TEMPLATE), then start a new job.
A field was retired or split: a template refresh doesn't replace a mapping that's already in place. Remove the old field's mapping, map the new fields, save and resubmit.
"[Field] is not present in the schema and additional fields cannot be added": send price or fulfillment changes as a Full update.
"Item Spreadsheet deprecated", or invalid field names such as mainImageUrl: the product is mapped to the retired Other product type. Choose the specific product type and remap.
"template_id is invalid": re-add or resync the template in PXM and run the job again. The mappings don't need to change.
ERR_PDI_0034: required fields are missing or out of range. Fill every mandatory field with the right type and range.
ERR_EXT_DATA_0101116: the title or price doesn't match an existing Walmart item with the same product ID. Align with that item, or contact Walmart Seller Support.
Missing-field errors on fields that aren't starred: map and fill the conditional field (for example Battery Type).
Duplicate-item flags: often the text CUSTOM in productId on several variants. Give every variant a real, unique identifier.
Accepted, but images don't show: fix the file size, extension or URL, then run a Partial update with the image fields selected.
API errors on a large job: split it into jobs of under 100 items.
"Feed ended without item results": Walmart returned no item results. Resubmitting is fine.
Accepted, but the content doesn't show on walmart.com: Walmart may hide content that fails its quality checks. In Seller Center, turn on the option to show that content, fix the flagged fields in PXM and publish again.
Partial update rejected for a missing identifier: include the SKU, productIdType and productId, plus any other starred fields on the template.
If Seller Center shows the wrong content after you've ruled out page delay, image files and mapping, open a case with Walmart Seller Support.
Still stuck? Contact your Pattern CSM with the Job ID, the Walmart channel, the account type (1P or 3P), an example SKU, the exact error and when it happened.
FAQ
Why can't we connect the way we used to?
Walmart retired Delegated Access for new connections. Your Walmart admin shares your primary Production API key securely, and Pattern creates the connection. Existing connections that work keep working.
Sandbox or Production keys?
Production keys.
Why did my price change fail?
Walmart accepts price and fulfillment changes only in a Full update.
Why hasn't walmart.com changed yet?
Correct data in Seller Center can take up to about 48 hours to reach the live product page. Check Seller Center first.
Where's the Walmart Feed ID for my job?
A Walmart Feed ID exists only after the job finishes, and PXM may not show one. Give your Pattern CSM the PXM Job ID and the time you published.
How do I check my content on Walmart?
Check the SKU in Seller Center first. On Walmart US, Match compares your PXM content with Walmart every day if your account uses it. See Match: Find and Fix Marketplace Content Mismatches.