Creating variation families as a Vendor.
The Vendor Central path for variation families is its own workflow — different from Seller Central, with NIS forms, cost-and-MSRP fields, and the variation theme baked into the new-item submission so deeply that getting it wrong means starting over.
Sellers and Vendors don't create variation families the same way, and the gap is bigger than most teams expect. Module 4 covered the Seller Central UI and flat-file routes; this episode is the Vendor Central path, which is structurally a different workflow with its own forms, its own validation rules, and its own review cycle.
The NIS form — Vendor Central's all-at-once submission
Vendor families start as a New Item Submission (NIS) — a multi-tab form that bundles the parent, the children, the variation theme, attributes, packaging, cost and MSRP into one submission. Amazon's internal catalogue team evaluates the whole thing as a unit. Unlike Seller Central, where you can iterate on a live parent piece by piece, the NIS expects the whole family submitted in one go and reviewed in one go.
The NIS has four logical sections that map to four tabs in Vendor Central: Product (the parent attributes and category), Offer (cost, MSRP, lead time, case pack), Variation (the theme and the child sheet), and Content (title, bullets, description, images).
Picking the variation theme up front — the irreversible step
Unlike Seller Central, where you can attach a child to a parent later with a flat-file edit, the Vendor NIS asks for the variation theme on the parent at creation time, and treats it as immutable. Pick Color and later discover you need ColorSize — the only fix is delete-and-re-create, which means waiting for the original NIS to clear, opening a new NIS, and losing whatever review history accumulated on the wrong family. This is the single most expensive mistake on the Vendor side.
The theme picker is also category-gated. Vendor Central will only show the themes Amazon has approved for the browse node you picked on the Product tab. If your theme isn't in the list, the underlying problem is the category, not the theme — switch categories before fighting the theme picker.
The child sheet
Inside the Variation tab is the child SKU sheet — one row per child SKU. Each row needs:
- Its own GTIN (or a GTIN-exemption pre-approved on the brand). Vendor central never accepts a missing GTIN.
- The attribute value for the variation theme — "Red", "Blue", "Black" for Color; "S", "M", "L" for Size; both for ColorSize.
- Cost — the per-unit price Amazon pays you. Set per child because pack counts and material costs differ.
- MSRP — the recommended retail price. Drives the strike-through-price comparison on the detail page.
- Packaging weight and dimensions — Amazon plans pallets and FC space based on these; wrong values delay PO acceptance.
- Case pack — how many units ship per inner case. Critical for replenishment.
The Vendor-only fields Sellers never see
Cost, MSRP, case pack, lead time, hazmat classification, country of origin at SKU level — these are all required on the NIS and don't have Seller Central equivalents. The cost field in particular is non-negotiable: Amazon's category buyer will renegotiate it after the NIS clears, but you have to submit a starting number.
What happens after submission
Amazon Vendor Central runs an internal review that can take anywhere from a few hours to a few weeks depending on category, brand history, and Q4 timing. The whole family lives or dies together — one rejected child blocks the parent until you either fix that row or remove it from the family. Rejections come back with a code (missing attribute, category mismatch, GTIN already in use) and a free-text comment from the catalogue team.
The two failure modes to plan for
- Silent stall. The NIS sits in "Submitted" for two weeks with no rejection, no progress. The fix is a contact-buyer ticket through Vendor Central asking for an expedite — the catalogue team will usually surface what's blocking it within 48 hours.
- Approved-then-orphan. The parent goes live but one child is missing its GTIN match. The family selector shows the parent and the approved children; the orphan child is in the catalogue but unsellable. Fix by resubmitting just that child as a single-row NIS attached to the live parent.
The Seller-to-Vendor migration trap
If your brand operates both Seller and Vendor accounts on the same ASINs (common with hybrid brands), the variation family will exist as a Vendor entity even if you originally built it on Seller Central. Once a Vendor NIS lands on an ASIN, the Seller-side editing surface narrows sharply: the title, bullets and category go read-only on Seller Central. Plan the structure on the Vendor side first, and use Seller Central only for offer-level changes (price, stock) on the children.
Watch Module 5 · Episode 03 — Creating variation families as a Vendor. (German)
A walk through the Vendor Central NIS workflow for new variation families.
Track every Vendor NIS submission through to live status.
AMALYZE pulls the live status of every Vendor ASIN you've submitted, so you know which children are approved, which are stuck in review, which were rejected, and which are silently blocking the parent.