Skip to main content

Amazon: Connect, Map and Publish from Pattern PXM

Connect Amazon Seller Central or Vendor Central, map product-type templates and publish listings from Pattern PXM.

Written by Sean Bentley

Pattern PXM publishes your approved product content to Amazon through Amazon's Selling Partner API (SP-API). You connect your Amazon account once, map your PXM attributes to Amazon's product-type templates, and then publish titles, bullets, descriptions, images and new listings whenever your content changes.

Publishing from PXM keeps one source of truth for your Amazon content, so you don't have to edit listings one by one in Seller Central or Vendor Central.

Before you start

  • Supported accounts: Seller Central (3P) in all Amazon regions, and Vendor Central (1P) in the US. Availability can vary by account; check with your Pattern CSM.

  • One account, one channel: each Amazon account and marketplace is its own connection, PXM channel and set of templates. For example, US Vendor Central, US Seller Central and Amazon Canada need three of each. A Vendor Central connection can't publish Seller Central listings, and the reverse.

  • What you'll need: your Seller Central or Vendor Central login, the region or vendor country, and for Vendor Central, your vendor codes.

  • 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.

  • Update in PXM first: edits made directly in Seller Central or Vendor Central can be overwritten by the next job that sends that field.

  • 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.

Step 1: Connect Amazon in Pattern Connect

Your Pattern CSM can walk you through this step.

  1. Go to connect.pattern.com and sign in with your Pattern PXM login.

  2. Confirm you're in the right organization, click Add new connection, choose Amazon, then click Next.

  3. Name the connection so your accounts are easy to tell apart, for example Amazon-US or Amazon-CA. Leave Support ID blank; Pattern fills it in if it's needed.

  4. Choose the account type: Seller Central (3P) or Vendor Central (1P).

  5. Choose the region (Seller Central) or vendor country (Vendor Central). For Vendor Central, enter your vendor codes, separated by commas if you have several.

  6. Click Connect, sign in to Amazon, approve the requested permissions, and confirm the success message back in Pattern Connect.

A live Amazon connection appears as a choice under API Channels when you create a channel in PXM. It doesn't appear under Settings > SYSTEM > INTEGRATIONS, which lists applications registered for the PXM API.

Step 2: Create the Amazon channel

  1. In Pattern PXM, open Settings in the left navigation, then go to MARKETPLACES > CHANNELS.

  2. Click CREATE CHANNEL (bottom right).

  3. Under API Channels, choose your Amazon connection.

  4. 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.

  5. Repeat for each Amazon account and marketplace.

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.

If you delete and recreate an Amazon channel, its template mappings don't carry over. Check your mappings again and use APPLY TO ALL CHANNEL TEMPLATES.

Step 3: Import and map your product-type templates

PXM holds one Amazon template per product type (for example TOASTER), built from Amazon's live schema for that product type.

  1. Go to Syndicate > TEMPLATES > API TEMPLATES and filter Channel to your Amazon channel. If you don't see templates yet, click IMPORT FROM LISTINGS to build them from your active listings, or click ADD API TEMPLATES and choose the channel.

  2. 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.

  3. 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.

  4. Map in this order: the ASIN or External Product ID attribute; then title, bullets, description, brand and every image field; then any category-required fields, such as browse node, item type keyword, dangerous goods and country of origin.

  5. Map images by media stack position: Main Image Location and each Other Image Location field.

  6. Set template default values for fields that rarely change, such as the exact brand name.

  7. 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

  • RECOMMENDED fields are required to create a new listing, and optional on updates.

  • Use Pick List attributes with Amazon's allowed values, rather than List attributes.

  • Give Amazon-only attributes clear names (for example "Amazon Bullet 1") so content doesn't go to the wrong channel.

  • Map Item Highlights to its own attribute. Amazon's title guidance is about 75 characters, and Item Highlights are about 105 characters.

  • Templates are per marketplace channel. A template on Amazon US doesn't exist on Amazon CA until it's added there.

  • Some yes/no fields, such as Batteries Required, make related fields required once they're set. Map those related fields too.

Step 4: Test, then roll out

  1. Run a Partial update on one or two products, sending one field.

  2. Confirm the job reaches HISTORY, then check the change in Seller Central or Vendor Central.

  3. Roll out by product type once the test lands.

Publish to Amazon

  1. In Products, select the products you want to send, then click PUBLISH TO CHANNEL (bottom right).

  2. In Channel*, choose your Amazon channel. CONTINUE TO REVIEW stays disabled until a channel is picked.

  3. Complete the publish options: choose the Seller Account (required), then the vendor code for Vendor Central jobs, the publish type (Partial is the default), any presets shown, the Template (required) and the media stack. Labels and order can vary by account.

  4. Select only the fields you're changing. Fields you don't select stay as they are on the channel.

  5. 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.

  6. Submit the job, then follow it under Syndicate > JOBS.

Bullets are all or nothing. Amazon replaces the whole set of bullets (and generic keywords), so always select every bullet field, even to change one.

If review shows an error on a field you didn't select, go back to the field selection step, tick the field and continue to review again. You don't need a new job.

Choose the right publish type

  • Partial update (most common): change specific fields on a live listing, such as title, bullets or images. Blank values don't overwrite Amazon. These fields generally can't be changed with a partial update: product type, brand, manufacturer, product identifiers and compliance fields. Use a Full update, and check with your Pattern CSM before changing them.

  • Full update: replace the listing's content, including a product type change. Blank values are sent too, and the listing needs every mapped required field.

  • Create: create a new listing. Fill every starred and RECOMMENDED field, or set template defaults. Amazon assigns the ASIN once the listing is accepted.

Use Create only for a product that isn't on Amazon yet, and Full update only for a listing that's already live.

Create a new listing

  • Fill every starred and RECOMMENDED field, or set template defaults. Each product type adds its own required fields.

  • No UPC, GTIN or EAN? Set Has GTIN Exemption to Yes, then deselect External Product ID and External Product ID Type.

  • List Price is the MSRP, in numbers only (no currency symbols, separators or "N/A"), and List Price Currency must be filled in with it.

Variations (parent and child)

Grouping products inside PXM doesn't create an Amazon variation family. Send the variation fields instead.

  1. Create the parent: publish with Create. In field selection, add Parentage Level, Child Relationship Type and Variation Theme Name, and leave Parent SKU unselected. In review, set Parentage Level to Parent and choose a theme Amazon allows for the category (for example SIZE).

  2. Add the children: publish the existing SKUs with Partial update. Add Parentage Level, Parent SKU, Child Relationship Type, Variation Theme Name and the theme value (for example Size).

  3. On every child, enter the exact Parent SKU, set Child Relationship Type to Variation, and give each child a unique theme value.

  4. Click Revalidate Content until review shows no errors, then submit.

The parent needs a unique SKU, no UPC, a general title and no price, inventory or images. Each child needs its own SKU, price, inventory and images.

Change a variation theme or combine variation families

  1. Change the theme: create a new parent with the new variation theme, re-attach the children to it using the steps above, and delete the old parent in Seller Central only after the children show as live under the new parent.

  2. Combine two families: re-attach the children of one family to the parent you're keeping, use Revalidate Content and submit the job, and delete the old parent in Seller Central once the children show under the kept parent.

  3. Update the product grouping in PXM to match, so future jobs send the right Parent SKU.

Change a product type

  1. Change the product type on the PXM product so it matches how the item should be classified on Amazon.

  2. Publish it as a Full update. A partial update won't change the product type.

  3. If the job reports "Submitted value was not applied to the listing", Amazon kept its existing product type. Align the PXM product type with Amazon's, or request the change from Amazon.

Don't use the Update Product Type action to fix a mismatch. Contact your Pattern CSM instead.

Images

  • Upload the images to the product, then use Edit Media to add them in order to a dedicated Amazon media stack (for example Amazon US).

  • Confirm the template maps the image fields to the media stack, then choose that media stack when you publish.

  • Don't paste third-party image URLs. PXM handles the image hosting Amazon requires.

  • Check Amazon's current product image guidelines for size and format rules.

  • Amazon processes images separately from the rest of the listing, so new images can take a while to appear.

  • If an accepted image doesn't show on the product page, Amazon may not have ingested it. Upload it for that ASIN in Seller Central's Image Manager.

Track your jobs

  • Syndicate > JOBS has four tabs: DRAFT, ACTION REQUIRED, IN PROGRESS and HISTORY. Filter Channel to your Amazon 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 Amazon. "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 Amazon rejected in full or in part. A rejected job shows REJECTED with FIX ISSUES. Amazon's rejection reasons are under Review, on each product row (Marketplace errors). FIX ISSUES archives that job and opens a new draft; correct the errors there and publish again.

  • 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. Amazon's back end usually updates shortly after, but the product page follows Amazon's own publish delay. Check the ASIN in Seller Central or Vendor Central.

  • Retrying a partly failed job resubmits every product in it, not only the failures.

  • The Partial update history file can list every loaded column. Only the SKU and the fields you selected were sent.

  • 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 rather than waiting longer.

Pre-release view; your screen may differ slightly.

What PXM can't send to Amazon today

Delisting, product videos and reviews aren't sent through PXM; manage them in Seller Central or Vendor Central. A+ content and Brand Story aren't part of regular publishing. Ask your Pattern CSM whether A+ content tools are available for your account; otherwise manage A+ content in Seller Central or Vendor Central. If you want to send only a price change, check with your Pattern CSM first. Delist in Seller Central or Vendor Central; unassociating a listing in PXM doesn't remove it from Amazon. Availability can vary by account; check with your Pattern CSM.

Automatic syndication is available only on some accounts, for Amazon US partial updates. Availability can vary by account; check with your Pattern CSM.

Common errors and fixes

First check the basics: the right channel and seller account (and vendor code), an active template for the product type, the values are approved, and the field was selected in the job.

  • No templates available, or a product type is missing: the template for that product type isn't added or isn't active. Add it or use IMPORT FROM LISTINGS, map every starred field, then publish again. Amazon's product type names can differ from what you expect, so search for alternatives.

  • An expected field isn't on the template: the PXM product type probably doesn't match Amazon's classification. Fix the product type, not the template. If Amazon's schema for that product type doesn't include the field, PXM can't send it.

  • Missing required attribute, or an error on a field you didn't select: map the field on the template, or go back from review and tick it.

  • A correct value is rejected, or "additional properties not allowed": Amazon updated its schema. Click SYNC MY TEMPLATE, then start a new job. An existing job won't pick up the change.

  • A unit or list value is rejected (for example "IN" instead of "Inches"): use Amazon's exact allowed values, and fill both the value and its unit.

  • Browse node "greater than 15 characters": enter only the numeric browse node ID, not the category path.

  • Product ID errors: UPC applies in the US and EAN in Europe. An ASIN belongs in Merchant Suggested ASIN.

  • Brand mismatch, or "brand needs Amazon approval": the brand must match Brand Registry exactly, including capitals, and the seller must be approved for it. Set the brand as a template default.

  • "SKU/UPC/ASIN have multiple matches": resolve the duplicate listings in Seller Central or Vendor Central, then publish again.

  • "Wrong vendor code": check the vendor codes on your connection and the one chosen in the job.

  • Job shows success, but nothing changed: spot-check the ASIN. In Seller Central, look for the SKU in drafts with missing fields, then send those fields. If your brand isn't the Brand Registry owner for that ASIN, Amazon may keep the owner's content; check brand ownership with your Pattern CSM.

  • Review shows a message about mandatory attributes: contact your Pattern CSM with the Job ID and the product type. Don't unselect attributes to clear the message.

  • The connection shows Active, but category templates don't load or Match doesn't see the connection: reconnect Amazon in Pattern Connect with the view and edit permission box checked, then publish again.

  • Errors remain after you fix a value in review: click Revalidate Content to check the content again.

  • More missing-attribute errors on Amazon DE partial updates: Amazon DE checks the full product-type schema. Fill the listed attributes and resubmit.

  • Image flagged for "abusive or offensive words": this is a false positive from Amazon's image scanner. Dispute it with Amazon.

Still stuck? Contact your Pattern CSM with the Job ID, the Amazon channel, the seller account (and vendor code), an example SKU or ASIN, the exact error and when it happened.

FAQ

Can one connection publish to both Seller Central and Vendor Central?

No. Each account type is its own connection and channel.

Why can't I pick my Amazon channel when I publish?

The channel has no active template. Map every starred field on at least one template.

Do I have to send every bullet to change one?

Yes. Amazon replaces the whole set of bullets, so select every bullet field.

Can I update only the price, or delist a product?

For a price-only change, check with your Pattern CSM first. Delisting isn't done through PXM; delist in Seller Central or Vendor Central.

How do I check my content on Amazon?

Check the ASIN in Seller Central or Vendor Central first. If your account uses Match, it compares your PXM content with Amazon's back end and live page every day. See Match: Find and Fix Marketplace Content Mismatches.

Did this answer your question?