Distinguish Vendor Central from Seller Central
Amazon Vendor is a supplier relationship: you sell to Amazon, which then sells the products. Amazon describes Vendor Central as invitation-only. Registering as a marketplace seller is a different process, covered on our separate Amazon Seller integration page.
Your approved account, target market and agreed Amazon data requirements determine your Vendor workflow. They establish which product information and media you need to prepare and how to submit them.
Build a shared product-data foundation
| Area | What your team prepares |
|---|---|
| Identity | Unique item numbers and the agreed product identifiers |
| Variants | Sizes, colours and configurations with their own correct data |
| Content | Titles, product features, descriptions and localised information |
| Media | Images and documents for the specific configuration |
| Logistics | Product dimensions, packaging dimensions and shipping packages kept separate |
This table is a preparation aid, not an official Vendor template. Prices, stock, orders and logistics need their own responsibilities and processes. A product-data transfer does not automatically include support for those workflows.
Agree the transfer process with a sample range
- Gather the requirements. Bring a current Vendor template or the requirements of your agreed process.
- Define the scope. Establish which information comes from shopvibes and which systems provide other data.
- Check the mapping. Compare fields, units, permitted values and variant relationships.
- Test representative products. Include a single item, a variant group and, where relevant, a set.
- Check the result. Review feedback and the data actually accepted through your Vendor process.
Whether a template export or a configured interface fits your Vendor workflow depends on that agreed scope. For file-based partners, our retailer-template guide explains how to build reusable mapping.
Example: one table in two sizes
A fictional dining table is maintained in widths of 120 and 160 cm. Each configuration has its own item number, correct width and matching images. A shared series description adds context; it does not replace variant-specific values. Compare the two outputs side by side before submission. This example is not an official Amazon schema.
Which details need a separate agreement?
Record the categories and markets covered by your account, the transfer method to be configured and who checks subsequent changes. Review rich content, pricing and stock workflows separately. Terms and any deductions follow your agreement with Amazon.
Bring your Vendor data process to a demo. A current template and a small product group provide a practical basis for discussing the preparation you need.
Sources and review date
Reviewed on 3 November 2026.
