What you will find in this guide:
Introduction
Required Fields for Product Creation
Partial Updates: When and Why
Creating Variant Products
Creating Parent Products
Syndicating Images
Limitations & Best Practices
What Can Be Syndicated via API
1. Introduction
This guide outlines how to efficiently syndicate product data from PXM (Amplifi.io) to Amazon. It covers setup, required fields, and best practices to ensure smooth and accurate product listings.
Purpose: This guide is designed for both new and existing users who want a clear reference on best practices for Amazon syndication.
2. Required Fields for Product Creation
Full Product Creation – Required Fields:
These fields are typically required across most product categories when creating a new product listing on Amazon:
Field | Required? | Example Values |
merchant_suggested_asin | ✅ Yes | "B08XYZ1234" |
contains_liquid_contents | ✅ Yes | "false" |
generic_keyword | ✅ Yes | "cotton shirt" |
is_heat_sensitive | ✅ Yes | "false" |
manufacturer | ✅ Yes | "Acme Co." |
safety_warning | ✅ Yes | "Choking hazard: small parts" |
target_audience_keyword | ✅ Yes | "adults, unisex" |
Inventory Always Available | ✅ Yes | "true" |
condition_type | ✅ Yes | "New" |
list_price | ✅ Yes | "19.99" |
unit_count | ✅ Yes | "1" |
batteries_required | ✅ Yes | "false" |
Package Height/Width/Length/Weight | ✅ Yes | "10, 5, 1, 0.5" (units and values) |
Partial Product Update – Required Fields:
For updating existing products, the following fields are required:
Field | Required? | Example Values |
SKU | ✅ Yes | "TSHIRT-BLACK-M" |
Item Name | ✅ Yes | "Classic T-Shirt" |
Brand Name | ✅ Yes | "Acme Co." |
Item Type Keyword | ✅ Yes | "T-shirt" |
Dangerous Good Regulations | ✅ Yes | "non-hazardous" |
Product Description | ✅ Yes | "A soft cotton tee available in multiple colors." |
At least one Bullet Point | ✅ Yes | "Soft cotton material" |
Country of Origin | ✅ Yes | "USA" |
3. Partial Updates: When and Why
Use partial updates when only certain fields change, such as:
Field | Reason |
Bullet points / key features | To update bullet points or key features without changing other details. |
Description | To make adjustments or updates to product info. |
Images | To update the image stack on a product |
|
|
Benefits:
Speeds up updates – Making changes to only the necessary fields.
Reduces the chance of overwriting unchanged data – Only modify what's needed.
Ideal for active products with frequent changes – Such as inventory or pricing.
Note: Some platforms restrict what can be updated via partial updates. Always check Amazon’s limitations.
4. Creating Variant Products
Definition: Variants are different versions of a product (e.g., size or color) grouped under a single parent listing.
Required Fields for Variants:
Field | Required? | Example Values |
Merchant Suggested ASIN | ✅ Yes |
|
Parent SKU | ✅ Yes |
|
Child SKU | ✅ Yes | "TSHIRT-RED-S" |
Variation Theme | ✅ Yes | "Size" |
Price & Inventory | ✅ Yes | "19.99, 100" |
Variant-specific Images | ✅ Yes | |
Variation Attribute | ✅ Yes | "Size: Small" |
Child relationship type |
| “accessory” |
Steps to Set Up Variants:
Choose a Variation Theme – Size, Color, Material, etc.
Assign a Parent SKU to group the variants.
Create Child SKUs for each variant and assign unique attributes (size, color, etc.).
Link the correct images for each child SKU to showcase the variant.
Note: For Amazon, all variants are treated as individual SKUs, and not as a true parent-child structure like Walmart or Shopify. Variants are grouped under a parent listing using shared attributes.
5. Creating Parent Products
Parent SKU:
Used to group related child SKUs under a single product.
Does not carry price or inventory.
Variation Theme:
Defines how child products differ (e.g., size, color, etc.).
Child Products:
Each has its own SKU, price, inventory, and variant-specific attributes.
Titles & Descriptions:
Parent: General product description that applies to all variants.
Child: Specific descriptions related to the variant (e.g., size or color).
Images:
Parent: A generic product image that represents the overall product.
Child: A specific image for that variant (e.g., image showing the color or size).
Bundles & Kits:
Treated as variant products grouped under a parent.
Each item in the bundle has its own SKU, inventory, and price.
6. Syndicating Images
Amazon 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 |
Image Syndication Steps:
Upload images to Amplifi.io.
Assign images to the correct SKUs.
Push via the syndication API.
Verify image mapping on Amazon to ensure proper display.
7. Limitations & Best Practices
What Can’t Be Syndicated:
Videos – Must be uploaded manually via Seller Central.
Product reviews and seller feedback – These cannot be syndicated.
Certain compliance or certification fields – Specific legal or regulatory data.
Non-standard/custom attributes – Not supported by the standard API.
A+ content / below the fold content
Best Practices:
Regularly review product data to ensure it is clean and up-to-date.
Use partial updates when applicable to avoid unnecessary changes.
Always check error logs for any failed syndications and correct issues promptly.
8. What Can Be Syndicated via API
Here’s what you can sync from Amplifi.io to Amazon via the API:
Product creation (titles, descriptions, key attributes)
Price updates (for both parent and child products)
Inventory updates (for all variants and parent product)
Variant management (parent-child relationships)
Product images (main image and variant-specific images)
Standard product attributes (size, color, material, etc.)
Category-specific data (e.g., shipping restrictions, sizing charts)