Skip to main content
All CollectionsAdvanced Topics
Walmart Syndication Guide

Walmart Syndication Guide

Brynlee Weibell avatar
Written by Brynlee Weibell
Updated over 2 weeks ago

Walmart Syndication Guide

Walmart Syndication Guide

  1. Introduction

  2. Required Fields for Product Creation

  3. Partial Updates: When and Why

  4. Syndicating Images

  5. Managing Variants and Grouped Products

  6. Limitations & Best Practices

  7. What Can Be Syndicated via API

  8. Common Issues

1. Introduction

This guide explains how to efficiently and accurately syndicate product data from PXM/Amplifi.io to Walmart. It includes setup, required fields, and best practices to ensure your product listings are optimized for Walmart's platform.

Purpose: To provide a clear and concise reference for users managing Walmart product syndication through Amplifi.io.


2. Required Fields for Product Creation

When creating a new product listing on Walmart, these fields are typically required across most product categories:

Field

Required?

Example Values

SKU

✅ Yes

"TSHIRT-BLACK-M"

Product Name

✅ Yes

"Classic T-Shirt"

Brand

✅ Yes

"Acme Co."

Price

✅ Yes

"19.99"

Product Description

✅ Yes

"Soft cotton crewneck T-shirt available in multiple colors."

Key Features

✅ Yes

"Soft, breathable fabric, machine washable"

Main Image URL

✅ Yes

Shipping Weight

✅ Yes

"0.5 kg"

Product Identifiers

✅ Yes

"GTIN: 123456789012"

Category-Specific Attributes

✅ Yes

"Size: Medium, Color: Red"

Compliance Attributes

✅ Yes

"Prop 65 Warning: None"

Multipack/Count Information

✅ Yes

"countPerPack: 1"

Condition

✅ Yes

"New"

Fulfillment Method

✅ Yes

"Walmart Fulfillment Services"


3. Partial Updates: When and Why

What Are Partial Updates? Partial updates allow you to update specific product fields (like price, title, dimensions, etc.) without re-uploading the entire listing. This is useful when only a few details change and helps prevent unintentionally overwriting other product data.

When Should You Use Them? Use partial updates when you're only updating specific attributes—rather than the entire product record. This is common for frequently changing fields such as:

Field

Reason

Title (Product Title)

To adjust or refine the product name.

Price

To adjust pricing without modifying other details.

Measurements

Adjust product dimensions or net content.

Fulfillment Method

To switch between Walmart Fulfillment Services and Seller Fulfilled.

Product Identifiers

When changing SKU, productId, or productIdType.

Other Common Fields for Partial Updates:

Field

Required?

Example Values

SKU

✅ Yes

"TSHIRT-BLACK-M"

productIdType

✅ Yes

"GTIN"

productId

✅ Yes

"123456789012"

Price

✅ Yes

"17.99"

Title (Product Title)

✅ Yes

"Classic T-Shirt - Red"

Fulfillment Method

✅ Yes

"Walmart Fulfillment Services"

Net Content

✅ Yes

"1"

Product Dimensions

✅ Yes

"length: 20 cm, width: 15 cm, height: 3 cm, weight: 0.5 kg"

Benefits:

  • Faster, more targeted updates – Only update what’s necessary.

  • Avoids overwriting unchanged product details – Only modify the fields that need attention.

  • Ideal for quick adjustments to pricing, packaging, or shipping data.

Tip: Always follow Walmart’s expected formats and measurement units for data consistency.


4. Syndicating Images

Walmart Image Requirements:

Image Type

Minimum Size

Recommended Size

File Format

Main Image

1000 x 1000 px

2000 x 2000 px

JPEG (preferred), PNG, TIFF, GIF

Additional Images

500 x 500 px

1000 x 1000 px

JPEG, PNG, TIFF

File Size

<10MB

Ideal: 1-2MB

Image Quality

High-resolution

Clear, white background

No text or watermarks

Steps to Syndicate Images:

  1. Upload product images to Amplifi.io.

  2. Assign images to the correct SKUs.

  3. Place images in desired Image Stack.

  4. Publish to Channel via the Walmart syndication API.

  5. Confirm that the mainImageUrl is properly mapped to the product listing on Walmart.


5. Managing Variants and Grouped Products

Variant Support on Walmart:

Walmart supports product variants (e.g., different sizes or colors) through item relationships using attributes like variantGroupId, variantAttributeNames, and shared product IDs.

Key Setup Elements:

Field

Required?

Example Values

variantGroupId

✅ Yes

"group123"

variantAttributeNames

✅ Yes

"Size, Color"

Parent Title and Description

✅ Yes

"Classic T-shirt, available in multiple sizes and colors."

Individual SKUs

✅ Yes

"TSHIRT-RED-S, TSHIRT-BLUE-M"

Steps to Create and Syndicate Variants:

  1. Define your variant group and assign a variantGroupId to each variant.

  2. Specify the differing attributes in variantAttributeNames (e.g., size, color).

  3. Syndicate each variant SKU with both shared and unique attributes.

  4. Include variant-specific images if applicable.

Note: Walmart does not use a true parent-child structure like Amazon. Instead, all variants are treated as individual SKUs with shared identifiers.


6. Limitations & Best Practices

What Can’t Be Syndicated via API:

  • Product videos – Must be uploaded manually via Seller Central.

  • Reviews or ratings – These cannot be syndicated via API.

  • Some custom or unsupported attributes – Not available through the standard API.

Best Practices:

  • Use clear, compliant data in required fields.

  • Stick to Walmart’s formatting and attribute guidelines.

  • Regularly review sync logs for errors or skipped fields.


7. What Can Be Syndicated via API

Here’s a summary of what you can sync from Amplifi.io to Walmart via the API:

  • Full product creation (titles, pricing, descriptions, attributes)

  • Partial updates (SKU, price, measurements, content changes)

  • Images (main and additional)

  • Fulfillment details and product packaging

  • Variant groupings using variantGroupId and variantAttributeNames

  • Standard and category-specific attributes (size, color, etc.)


8. Common Issues

  1. Walmart does not always expose all required fields properly in the schema they vend to PXM. This can result in some fields appearing as though they are not required even though they may be required under certain circumstances (e.g. If a product has batteries, the marketplace will make the battery type and battery capacity fields required for item setup)

  2. “<Field XYZ> is not present in the schema and additional fields cannot be added”. This error often occurs when a user has attempted to syndicate a field that is not available for a certain publish type. For example, Walmart only allows pricing or fulfillment changes to be made through Full Updates. If a user tries to edit these fields using a partial update, Walmart will not allow those changes to be made.

Note: Specific fields may vary slightly depending on the product category. Refer to Walmart's item spec documentation for category-specific requirements. (e.g. cosmetics products or consumables often include an “active ingredient” field that is required for item setup.)

Did this answer your question?