Trilha 05 · Módulo 05 de 6
Variant groups and re-parenting: grouping supplier items and changing a live group
How a supplier variant group works — shared ID, attribute names and values, the primary — building one in the Setup Hub, what you can change on a live group yourself, what needs the merchant, and checking the result option by option.
12 min de leitura
Neste módulo você aprenderá a
- ✓Explain what a variant group does for a supplier's items and what it leaves to the merchant.
- ✓Build a group in the Setup Hub spreadsheet with a shared Variant Group ID, allowed attribute names, distinct values, and a primary variant.
- ✓Add a new item to a live group, confirm it joined, and decide which other changes you can submit, which the Catalog lets you make, and which go to the merchant with the item numbers and intended structure.
- ✓Check a live group as a shopper and attribute each failure to its owner.
A supplier variant group is navigation between approved items, not a decision about what Walmart carries.
Walmart 3P → Variant groups covers a group's structure and Amazon 1P → Variation families the parent-and-child equivalent. This module covers what differs for a supplier: how a group is submitted, what you can change on a live group — by file or in the Catalog — and what only the merchant can.
What a group is for a supplier
On Walmart.com a variant group is one item page with option selectors — color, size, count — where each option is a separate item with its own Walmart item number, GTINs and content. There is no parent record: the group is a relationship between real items, not a non-buyable parent as on Amazon.
For a supplier the group lets a shopper switch options on one page and, in most categories, share ratings across them. It does not decide what Walmart carries: the merchant approves each item on its own and decides its stores, and an option not approved for online sale shows as unavailable or not at all.
Who may change a live group follows the same split between the supplier's data and the merchant's decisions. Supplier One's Catalog — your item list, with a variant details view per group — shows each group's structure but lets you edit it only in some cases; Changing a live group covers which.
Building a group at setup
New groups are usually built in the Setup Hub by bulk spreadsheet (Item setup covers both routes), since one file keeps every row's ID and attribute names identical. Columns vary by spec version; typically:
- Variant Group ID — a string you define, identical on every row: the shared key.
- Variant attribute names — the attributes that differ, from the product type's allowed list (check the current cap), identical on every row.
- Values — each row's value per attribute, consistent in spelling, casing and units; no two rows may share a combination, since Walmart rejects a duplicate at submission.
- Primary variant — a flag on exactly one row: the item the page opens on.
- Images and swatches — each row's own images and, where the product type supports them, swatches for the named attribute.
Submit the rows together. The Submissions Manager (older guides called it the Activity Manager or Activity Monitor) tracks each item; the merchant approves each separately, and the live group shows only approved, published items.
Changing a live group
You submit — your own items' values, images and swatches through the Maintenance Hub, editable group or not (item fields, not structure); and a new item joining via the Setup Hub:
- Confirm the group's attribute names and values in the Catalog or live selector.
- Submit the item with the Group ID and values matching in spelling, casing and units.
- Check the Submissions Manager for its status and reason.
- Check the option selector once it is live.
- Log the result against the item number.
You edit in the Catalog, when every item is yours — its variant tools (labels like Manage Variant and Edit Variant Details) group, merge, split and change the primary in current accounts. Not by maintenance file as of this writing — a bulk variant edit is planned; check the current help article.
The merchant — a read-only group (another supplier's items), re-grouping live items in most accounts, and an item that fell out after clean resubmission. Send item numbers, GTINs, the intended grouping, values and primary: a request, not a support ticket.
QA on Walmart.com
The live page is the only proof. Once every item is approved and published, open the group as a shopper and check:
- Every option is visible and named as intended; a missing option is a group fault — a mismatched name, a rejected duplicate, or an unpublished item.
- Selecting an option switches the page — image, name and availability become that item's own.
- No near-duplicate values — Walmart rejects a true duplicate at submission, so two look-alike options are usually a near-duplicate (
NavyandNavy Blue, a casing or unit difference); make the values distinct, or add a second attribute so each combination is unique. - The primary makes sense — the default item is published, available and representative.
- Out-of-stock options behave — in most categories an option with no stock stays visible but unavailable; one that disappears entirely is a group or publishing fault, not a stock event.
A group passes only when every option does.
Common failures and owners
Five causes cover most broken groups:
- Items in different product types — each type has its own allowed list, so the group cannot form; fix the type before submitting, in the Catalog if editable to you, or through the merchant.
- Mismatched attribute names — one item declares
color, anothercolorandsize; the odd item lands outside the group. - Duplicate values — two items carry the same values; Walmart rejects the later one, so change one value or add a second attribute (Blue/Small, Blue/Medium) and resubmit.
- An unpublished or unapproved primary — the page opens on an item you did not choose; a field rejection is yours, a merchant-review hold the merchant's; meanwhile make an approved, published item primary, in the Catalog or through the merchant.
- DSD (direct store delivery) and owned items mixed — different logistics and setup paths; the group may not form, so ask the merchant first.
If clean data still will not group and the merchant asks for a ticket, Supplier support tickets covers it.
Lembre-se
The Submissions Manager proves the row was accepted; only the option selector proves the group changed.
Coloque em prática
Cenário
A fictional insulated bottle group has three colors live under Variant Group ID BOTTLE-GRP-01, Walmart item numbers 100000001 to 100000003. A fourth color, Slate, is approved for setup. Meanwhile a colleague reports that the Navy option vanished from the selector last week, although the Navy item's own page is still live and in stock.
Exercício
- Establish the live group's attribute names and the exact color values the three items carry before writing the Slate row.
- Prepare the Slate item for the Setup Hub with the Group ID and matching attribute names, and name where you will confirm it joined.
- Diagnose the missing Navy option and decide whether it is a correction you submit, a Catalog edit, or a request to the merchant.
Mostrar uma abordagem sugerida
Read the attribute names and values from the Catalog's variant details view or the live selector, and write Slate to match in attribute, spelling and casing; the Submissions Manager, then the selector, confirms it joined. Navy's live page rules out stock and publishing, so compare its attribute names and values with the other two: a value in the wrong style or units you correct through the Maintenance Hub and resubmit; a mismatched attribute name is a Catalog edit if editable to you, otherwise the merchant's. If its data matches and it still stands alone, send the merchant all four item numbers, the Group ID, each color value and the intended primary, logging the request against item 100000002.
Verifique seu entendimento
Ir à fonte
Documentação oficial do marketplace para este módulo.