Pfad 04 · Modul 02 von 4
Item setup: the Setup Hub, requirements, and merchant approval
Set up new supplier items in Supplier One — mapping requirements to approved sources, resolving blockers before submission, tracking the item through the Activity Monitor, and what merchant approval means for the timeline.
4 Min. Lesezeit
In diesem Modul lernst du
- ✓Map every required field to an approved source before opening the Setup Hub.
- ✓Identify and resolve setup blockers — unconfirmed packaging values, missing images, unclear item model.
- ✓Track a submission in the Activity Monitor and understand merchant approval.
- ✓Review the processed item result instead of stopping at submission.
Give every required field a reliable source.
Prepare supplier item data against the current requirements of the setup flow. Record what is ready, what is missing, and who can resolve each gap — an unconfirmed value is a blocker, not a placeholder.
Requirements
The Setup Hub in Supplier One walks a new item through product identity, product content (the product type's attributes, description, images), packaging hierarchy, logistics, and cost. The product type decides which attributes are required, and the item model (owned or DSD) decides which logistics fields appear. Pull the requirement list from the setup form for that product type, not from the last item you set up.
Readiness
Before submitting, confirm against approved sources:
- identifiers at every packaging level,
- packaging dimensions, weights, and quantities, labeled by level,
- the product-type attributes and content (name, description, features),
- image references that meet Walmart's content standards,
- cost and logistics data agreed with the buyer.
Keep a readiness tracker with three states per field: ready, missing, owner asked. The tracker is what lets several people set up a range without guessing at each other's gaps.
Submission and merchant approval
Submitting an item does not make it live. The item is validated, then routed to the Walmart merchant (buyer) for the department, who approves it for ordering — often after checking cost and assortment. The Activity Monitor shows where each item is: submitted, needs attention (with the specific error), pending approval, approved. Errors at validation come back per field; fix and resubmit the item, not the whole batch.
Follow-through
After approval, review the item record in Supplier One and, for online items, the Walmart.com page: identifiers, packaging, content, and images should all match the source. Record the Walmart item number in your master data at this point — it is the reference every later ticket and report will need.
Merke dir
A ready-to-submit item has supported values, clear mapping, and no unresolved required-data gaps — and an approved item still needs a look at the result.
In die Praxis umsetzen
Szenario
A fictional bottle's item data is ready except for case quantity. One email from sales suggests six; the approved packaging sheet has no value; the buyer wants the item submitted this week.
Übung
- Treat case quantity as unresolved and record who owns the answer.
- Request a confirmed packaging value from the responsible source owner, stating what the blank blocks.
- Plan the final mapping, validation, and post-approval check once the value arrives.
Lösungsvorschlag anzeigen
Keep the unresolved field visible — an informal 'six' is not a source. Ask packaging for the confirmed case quantity and the case GTIN-14, explaining that the item cannot be received correctly without them. When confirmed, update the source record, complete the Setup Hub, watch the Activity Monitor through validation and merchant approval, and verify the approved item's packaging data before closing.
Teste dein Verständnis
Zur Quelle
Offizielle Marketplace-Dokumentation zu diesem Modul.