Amazon SP-API + Code2ASIN: Sell on Amazon from Your PIM (2026 Guide)

For retailers who sell on the platform, Amazon is often their largest channel by volume. However, selling on Amazon via a PIM requires an understanding of two distinct issues: creating product listings in the Amazon catalogue (Code2ASIN), and managing inventory, pricing and orders on a day-to-day basis (SP-API). These are two separate modules for two very different use cases.

Amazon SP-API and Code2ASIN: two modules, two roles

Confusion is common. Here is the fundamental distinction:

• Code2ASIN— creates new ASINs in the Amazon catalogue from your PIM product data. This is the listing stage: you do not yet have an ASIN for a product, so you create one. Used once per new product.
• Amazon SP-API— manages the ongoing operational relationship with your Seller Central account: updating stock levels, synchronising prices, retrieving orders, managing existing listings. Used continuously, several times a day.

In practice, the workflow is sequential: Code2ASIN first to create the ASIN, then SP-API to manage the listing on a day-to-day basis.

Code2ASIN: listing a product on Amazon

Creating an Amazon ASIN is one of the most time-consuming steps for retailers listing new products or importing lesser-known brands. The manual process via Seller Central is lengthy, error-prone and limited in volume.

The Code2ASIN module in Pixee PIM automates this process using data from the PIM:

1. Existence check— the module begins by checking whether an ASIN already exists for the product’s EAN. If so, it suggests joining the existing listing rather than creating a duplicate.
2. Selection of Amazon product type— Amazon imposes different data models depending on the category (Electronics, Home & Kitchen, Clothing, etc.). Code2ASIN maps your PIM attributes to the corresponding Amazon Product Type.
3. Flat file generation— Pixee PIM generates the ASIN creation file in the format required by Amazon, with all mandatory and recommended attributes populated from the PIM.
4. Submission and tracking— the file is automatically submitted to Amazon. Amazon validation errors are reported back to Pixee PIM with details of the affected attribute and the required correction.
5. Retrieval of the ASIN— once the ASIN has been created, it is saved in the PIM product record and automatically used by the SP-API module for listing management.

The pitfalls of Amazon listing

Amazon has strict requirements regarding data quality when creating ASINs. The most common errors that Code2ASIN helps to avoid:

• EAN not recognised by GS1— Amazon checks the validity of barcodes. An incorrectly formatted EAN or one not registered in the GS1 database is rejected. The EAN Manager validates the barcode before submission.
• Non-compliant title— Amazon imposes strict rules depending on the category : maximum length, absence of certain characters, "Brand + Model + Key Feature" format. The module automatically suggests a reformatted title.
• Missing mandatory attributes— each Amazon category has its mandatory attributes. If your PIM does not have them, Code2ASIN specifically flags what is missing before submission (not after rejection).
• Brand conflict— if the brand is registered in the Amazon Brand Registry, creating an ASIN may require additional validation. The module alerts you in advance.

Amazon SP-API: managing your listings on a daily basis

Once the ASINs have been created, the day-to-day management of Amazon listings is handled via the SP-API module. It covers recurring operational use cases:

• Stock synchronisation— your stock levels in the PIM are reflected in your Amazon listings. Out of stock = listing automatically suspended to prevent unfulfillable orders. Back in stock = immediate reactivation.
• Price updates— price changes in the PIM (following a supplier update or a repricing rule) are synchronised with Amazon. The module complies with Amazon’s price parity rules.
• Content updates— titles, descriptions, bullet points, images: any enhancements made in the PIM are pushed to existing Amazon listings (within the limits of the editing rights granted by Amazon).
• Order retrieval— Amazon orders are fed back into Pixee PIM to trigger logistics workflows. Useful for FBM (Fulfilled by Merchant) sellers who manage their own shipping.
• Listing performance tracking— Buy Box won/lost, update acceptance rate, alerts on listings removed by Amazon.

Sync cadence and API call limits

Amazon does not let a seller call its API at whatever rate it likes. Access is regulated operation by operation, with a credit mechanism that replenishes over time: a short burst goes through, a continuous flow beyond the permitted rate is throttled and then refused. The exact values differ between operations and are revised by Amazon — quoting them here would amount to publishing a figure that expires before it is read. The rule to remember lies elsewhere: an integration is designed on the assumption that the constraint applies, never in the hope of escaping it.

In practice, a synchronisation that holds up over time respects four principles:

• Send the event, not the catalogue— only the records that actually changed go to Amazon. A full daily sweep spends the quota rewriting identical values.
• Batch— mass updates go through feeds rather than one call per SKU.
• Absorb throttling— when Amazon replies that there are too many requests, the update must be queued and retried later, never silently lost.
• Prioritise— stock and price come before marketing content. A description that waits two hours costs nothing; an incorrect stock level costs an order you have to cancel, and cancellations weigh on your seller performance metrics.

Parent/Child ASINs: managing Amazon variants

Amazon structures variants as Parent/Child families: a parent ASIN groups together child ASINs that correspond to variations (size, colour, capacity, etc.). This structure is directly derived from your variant model in the PIM.

• Parent ASIN→ corresponds to the parent product in Pixee PIM. It cannot be purchased directly; it is used to group variants.
• Child ASINs→ correspond to the SKUs/variants in the PIM. These are the purchasable ASINs, each with their own stock, price and specific images.
• Variation axes→ configured once in the PIM → Amazon mapping by category (e.g. "Size" and "Colour" for textiles, "Capacity" for electronics). The module manages Amazon’s limits (maximum 2 variation axes per family).

Repricing and Price Monitor

Retailers active on Amazon face constant price competition. The Price Monitor module in Pixee PIM integrates with SP-API for automatic repricing:

• Real-time monitoring of competitor prices on your ASINs
• Configurable repricing rules: "match the lowest price without falling below X€", "maintain a 2% margin below the main competitor"
• Automatic updating of Amazon prices via SP-API as soon as a rule is triggered
• Alerts if automatic repricing would fall below your configured minimum margin

Amazon automatic repricing is available from the Scale plan.

An illustrative scenario: multi-brand importer, 3,500 Amazon SKUs

The orders of magnitude below describe a typical situation, reconstructed from setups we commonly encounter. They are not the measured results of a named customer.

Take an importer distributing 30 brands on Amazon France and Amazon Germany with 3,500 active SKUs:

• Before: manual creation of new ASINs via Seller Central (one to two hours per new product), stock updates via daily flat file, close to one listing in ten permanently suspended due to incomplete data
• After Code2ASIN + SP-API: creation of a new ASIN in about fifteen minutes (automatic validation + submission), stock updated in real time, and virtually all listings staying active
• Additional benefit: batch enrichment of Amazon descriptions from the PIM (a few hours for 3,000 AI-generated bullet points, against several weeks manually), and an Amazon completeness score moving from around 50% to close to 90%

On which plans are Code2ASIN and SP-API available?

The Code2ASIN and Amazon SP-API modules are two separate modules, both available from the Starter plan. Automatic repricing is exclusive to the Scale plan. Both modules are included in all paid plans at no extra cost per SKU or per API request.

Frequently asked questions

Should you create a new ASIN or join an existing listing?

Join it, whenever an ASIN already exists for the product’s EAN. Creating a duplicate exposes you to a merge or a deletion decided by Amazon, and scatters sales history and reviews across two competing records. Creating an ASIN is only justified for a product genuinely absent from the Amazon catalogue: own brand, exclusive import, brand-new reference. That is precisely why Code2ASIN always starts with an existence check before any submission.

Why does a content update sent from the PIM not appear on the listing?

Because the listing belongs to the Amazon catalogue, not to the seller. Several sellers can contribute to the same ASIN and Amazon arbitrates between contributions; the brand owner registered with Brand Registry usually prevails. Your submission can therefore be accepted technically without ever being displayed. Before concluding that the integration is at fault, look at the update acceptance rate reported by the module: it distinguishes a formatting rejection, which can be fixed, from an editorial arbitration, which cannot.

How often should stock levels be synchronised?

As soon as possible after the change, which is not the same thing as as often as possible. A synchronisation triggered by the stock movement itself sends fewer calls and arrives faster than an hourly sweep of the entire catalogue. Keep scheduled sends for data that moves slowly — content, technical attributes, images — and keep the quota available for what expires within minutes.

How do you run several European Amazon marketplaces from a single catalogue?

By keeping one single source of record and overriding only what differs by country: the language of the listing, the price, and the regulatory statements required in the destination market. The structural attributes — EAN, brand, dimensions, variation axes — have no reason to be duplicated per marketplace. Only the surface layers are, translation first, which Pixee PIM handles through DeepL in BYOK mode.