Amazon 1P · Vendor Central

路径 02 · 模块 01 / 4

Vendor catalog: item identity, packaging hierarchy, and account context

How a Vendor Central item is identified — ASIN, GTIN, vendor code, external ID — how consumer units and cases differ, and why you search the catalog before you create anything.

阅读约 5 分钟

在本模块中你将学会

  • Reconcile the identifiers for one item: ASIN, UPC/EAN, vendor code, and your internal item number.
  • Tell a consumer unit from a case and a pallet, and know which fields belong to which packaging level.
  • Confirm the vendor code and marketplace before acting in any workflow.
  • Decide whether to add an existing ASIN to your catalog or set up a new item.
阅读

Start with a dependable item record.

A vendor catalog needs a reliable source of product identity and attributes. Reconcile the references before preparing new content, submitting an item, or investigating a discrepancy — most 1P mistakes trace back to a source sheet that mixed two things up.

Identifiers on the 1P side

  • ASIN — Amazon's catalog identifier, shared with every seller and with Amazon Retail. The same ASIN can be supplied by a vendor and sold by third parties at once.
  • UPC / EAN / GTIN — the GS1 barcode of the consumer unit. Cases carry their own GTIN-14 (ITF-14) barcode; never put a case code in the unit field.
  • Vendor code — the short code that identifies your vendor account (one company can hold several: by country, category, or legal entity). Every item lives under a vendor code, and cases, POs, and support are scoped to it.
  • External ID / vendor SKU — your own item number. Amazon stores it so POs and reports can be matched back to your systems.

Keep the four together in one row of your source of truth. A support case that cites the ASIN but the wrong vendor code goes nowhere.

Packaging hierarchy

Vendor items are set up as a hierarchy, and the fields are not interchangeable:

  • Each (consumer unit) — what the customer receives. Its GTIN, dimensions, weight, and content describe one sellable unit.
  • Case — how you ship to Amazon's fulfillment centers. Case quantity, case GTIN-14, case dimensions and weight.
  • Pallet — layer and tie-high configuration for large volumes.

A capacity that is right for the unit is wrong for the case, and vice versa. Amazon uses case data to write purchase orders and to route inbound freight, so a unit dimension entered in the case field produces chargebacks and refused shipments, not a listing error.

Account context

Before using any workflow, confirm three things: which vendor code you are acting under, which marketplace (amazon.com, .co.uk, .de… each is a separate Vendor Central), and whether the ASIN is already in that catalog. Vendor Central's account switcher makes it easy to submit a perfectly correct item to the wrong account.

Search before you set up

In Items → Add Products, search by UPC/EAN first. If the ASIN already exists — because a third-party seller created it, or because it is already in another of your vendor codes — you add it to your catalog rather than creating a duplicate. Amazon merges duplicate ASINs eventually, and the merge can take your content and your purchase-order history with it.

Only when the search returns nothing do you proceed to new item setup: choose the product type, complete the required attributes, provide the unit and case data, and submit for approval.

Where the work happens in Vendor Central

  • Items → Catalog — every ASIN under the vendor code, with availability status.
  • Items → Add Products — search, add existing ASINs, or set up new items one at a time.
  • Items → Bulk product submissions (new item setup spreadsheets) — set up or update items at scale, and check submission status.
  • Items → Edit Products — change detail page content for ASINs already in your catalog.
  • Support → Contact Us and the Case Log — everything that cannot be done in a feed.
  • Support → Resource Center — Amazon's own vendor guides, behind login.

请记住
Treat a blank field as missing information, not permission to infer a value. A guessed case quantity becomes a wrong purchase order.

练习

付诸实践

场景

A fictional item sheet lists a single 750 mL bottle, while a second source describes a case of six. Neither says which packaging level its identifier and dimensions represent, and the brand is set up under two vendor codes.

练习

  1. Flag the unit-versus-case conflict, and identify which GTIN belongs to which level.
  2. Check the approved packaging specification for unit and case dimensions, weight, and case quantity.
  3. Document the confirmed item, packaging references, and the vendor code the item belongs under, together.
显示建议方法

Resolve the packaging level before using the data. The consumer unit and the shipping case are different records with different GTINs and dimensions; the source must state which is which. Confirm the vendor code the ASIN should sit under, then search Add Products by the unit UPC to see whether the ASIN already exists before setting anything up.

检测

检验你的理解

第 1 题

01Two source files disagree on the packaging level. What should you do first?

第 2 题

02You search Add Products by UPC and find the ASIN already exists, created by a third-party seller. What is the right move?

第 3 题

03Which field must hold the GTIN-14 (ITF-14) barcode?

查看官方来源

本模块对应的平台官方文档。