Creating a product in the Seller Central backend.

The Seller Central backend Add a Product flow is the most common path to creating a new ASIN — the right tool for any catalogue under roughly ten SKUs, the right tool for a first new SKU even in a larger catalogue, and the right tool any time you need to see exactly what fields the category template surfaces. The flow looks simple at first glance and gets dramatically more complex once you understand that the fields it shows depend entirely on the browse node, the Style Guide attached to that node, whether you are creating a parent or a child, and whether your account holds the relevant category approvals.

The flow in five canonical steps

1. Search by GTIN — paste the EAN/UPC/ISBN. If a matching ASIN exists, Amazon offers to attach (Episode 07). If not, the flow proceeds to creation. If the product has no GTIN, click "I don't have a product ID" and reference the GTIN exemption from Episode 05.
2. Pick the category. This commits the field schema for the listing — it locks in which attributes appear, which Style Guide applies, which referral fee you'll pay, and which BSR you compete in. See Episode 08 for how to pick correctly.
3. Fill the Vital Info tab. Brand, manufacturer, item name (the title), product ID type, model number, item type keyword. These are the indexable hero fields and the ones the Style Guide validates hardest.
4. Fill the Offer tab. Seller SKU (your internal identifier), price, condition, fulfilment channel (FBA or MFN), launch date if delayed, sale price and sale date range if applicable, restock date if low.
5. Fill the remaining tabs: Product Details (dimensions, weight, materials, attributes specific to the category), Images (main image plus 6–8 secondaries), Description (the long-form prose covered in Module 3 Episode 07), Keywords (the backend search-term field), More Details (compliance, certifications, hazmat status), and Variations (if applicable).

The Vital Info fields that decide everything downstream

• Brand Name. Must exactly match your Brand Registry record if you're enrolled. A mismatch — even a trailing space — disconnects the new ASIN from your brand and unlocks none of the Brand Registry features for it. Verify the exact spelling in Brand Registry before typing it here.
• Manufacturer. Usually identical to Brand for private-label sellers; differs for resellers and for white-label partnerships. The field is used by Amazon's catalogue dedup pass.
• Item Name (Title). The title field; covered in depth in Module 3 Episode 02. Subject to the category Style Guide.
• Product ID Type + Product ID. EAN/UPC/ISBN/GCID. Mistyping this field is the most common cause of "submission accepted, ASIN never created" — Amazon silently rejects the underlying record.
• Model Number / Part Number. Manufacturer's internal SKU. Optional for some categories, mandatory for Electronics, Automotive, Industrial. Indexed by Amazon's search and used to match the listing to spare-part queries.

The save points and the autosave that isn't

Seller Central's Add a Product flow does not autosave. Every tab has a "Save and finish later" button that commits the current tab's fields to a draft. Tab navigation without explicit save will lose the draft if you close the browser, navigate away, or let the session time out (sessions expire at 30 minutes of inactivity). The defensive workflow:

• Save after every tab, not at the end.
• Verify the draft is recoverable by reloading the page and checking that the previously-entered values are still there.
• For complex listings (variation families with 20+ children, A+ Content with 6+ modules), prepare every field in a separate text document first and paste into Seller Central tab by tab.

Silent field rewrites — the most under-documented behaviour

When you click Submit, Amazon runs the Style Guide validator against every field. The validator does not always reject violations cleanly — it frequently rewrites them silently and accepts the rewritten version. The most common silent rewrites:

• Capitalisation — "STAINLESS STEEL WATER BOTTLE" silently becomes "Stainless Steel Water Bottle".
• Duplicate words — "Premium Premium Quality" silently becomes "Premium Quality".
• Title truncation — titles exceeding the category byte limit get cut at the limit, sometimes mid-word.
• Prohibited words — "Best", "#1", "Free Shipping" get stripped, leaving a malformed sentence.
• Symbol replacement — em-dashes, smart quotes, and non-ASCII punctuation get replaced with their ASCII equivalents or stripped entirely.
• Whitespace normalisation — double spaces collapse to single spaces, trailing spaces strip.

Always re-open a saved draft (or a freshly-created live listing) and read back what Amazon actually stored, field by field. The submitted value and the stored value frequently differ, and only the stored value matters for what appears on the PDP.

When the UI fights you

• A field you need isn't visible. You're in the wrong category. The Add a Product UI shows only the fields the category template defines; if your product has an attribute the chosen category doesn't expect, the field simply does not appear. Solution: re-pick the category, or use the flat-file (Episode 10) which exposes the full superset of attribute columns.
• A category demands a field you don't have. Almost always a missing certification (CE, FCC, GS, RoHS) or a missing regulatory registration (FDA, EMA). The field is mandatory because the category requires it. Either secure the certification, or pick a category that doesn't require it (rarely the right move — it usually means you're in the wrong category).
• Submission accepted but the ASIN never appears. Most common cause: silent GTIN rejection (the GS1 lookup failed). Check Seller Central → Catalog → Manage All Inventory and search for the SKU; if the SKU is there but the ASIN column is blank, the GTIN is the issue.
• Submission rejected with a generic error. Look at the error code in the response. Specific category-attribute errors usually resolve by filling the missing attribute; vague errors typically resolve by re-picking the category or by switching to flat-file submission where the error messages are more granular.
• UI silently overwriting your bullets. Either a Brand Registry-contributed higher-trust value exists, or the Style Guide validator is rewriting on submit. Re-read what was stored after submission to diagnose.

Variations — when the parent–child flow is involved

Creating a variation family through the UI follows the same five-step flow but with an additional "Variations" tab that asks for the variation theme (covered in Module 3 Episode 14) and a child-by-child attribute matrix. The parent is created first as a non-purchasable shell, then each child is added with its own SKU, GTIN, image, and price. The UI handles small families (under ~10 children) acceptably; anything larger should move to the flat-file flow because the per-child editing in the UI becomes tedious and error-prone. Module 5 covers variation creation across both surfaces in much more depth.

Speed-runs and the "good enough to launch" listing

For internal-team test launches and for SKUs that will be replaced within weeks, the temptation is to skip the Vital Info and Product Details polish and just push something live. Resist this. Amazon's catalogue layer caches initial-state attributes more persistently than later edits — fields entered sloppily at launch often re-appear weeks later after a re-validation pass, overwriting the cleaner edits you made in between. The minimum-viable launch: complete title, complete brand, GTIN or exemption, primary image meeting Module 3 Episode 03 rules, at least three bullets, and the correct browse node. Everything else can be improved iteratively, but those six fields lock in baselines that are hard to change retroactively.

Seller vs Vendor — completely different creation surface

Vendors do not use the Seller Central Add a Product flow. Vendor product creation runs through the NIS (New Item Setup) form in Vendor Central — a multi-tab Excel-style template that bundles the parent, the children, the cost prices, the MSRP, the packaging dimensions, and the variation theme into one submission that Amazon's catalogue team reviews as a unit. The two flows have completely different field schemas, different validation, and different turnaround. Module 5 Episode 03 covers the Vendor NIS flow in depth; for now, if you are a Vendor, treat this Seller Central walkthrough as background context rather than as your daily workflow.

What to take into the next episode

The UI is the right tool for one-off SKUs and for visual editing. The next episode covers the alternative — building flat-files for any catalogue larger than ten SKUs, where bulk operations win on speed, on auditability, and on safety.