Pad 01 · All marketplaces
Foundations: The groundwork every marketplace track builds on.
Every marketplace has its own workspace, templates and vocabulary, but the work underneath is the same: a product has to be identified without ambiguity, described from an approved source, moved through a spreadsheet without being damaged, and checked on the live page before anyone calls it done. Sellers and suppliers who skip that groundwork learn each platform's rules as a list of surprises.
This track covers the four skills that the Amazon and Walmart tracks assume: how a listing is put together, how GS1 identifiers work and fail, how to handle catalog spreadsheets safely, and how to verify your own work.
Werkomgeving
All marketplaces
Relatie
You → the catalog
Work from a source of truth. Every identifier, attribute and image you submit anywhere should trace back to an approved record, and every change should end with a check of the live page.
4 modules
44 min leestijd- Module 0111 min leestijd
Anatomy of a listing: identity, content, offer, and the page a shopper sees
The four layers every marketplace listing is built from, who owns each one, how shared pages are assembled from ranked contributions, what a variation family is, and how to read a live page against your own record.
Module openen → - Module 0211 min leestijd
GS1 identifiers: UPC, EAN, GTIN-14, who owns a code, and why marketplaces reject it
How the GS1 numbering system works — the GTIN family, one code per sellable unit, the packaging hierarchy — who a code is licensed to, the three ways marketplaces reject one, and a verification routine to run before any product is set up anywhere.
Module openen → - Module 0311 min leestijd
Spreadsheet skills: handling catalog files without damaging the data
The spreadsheet habits every marketplace template, export and error file depends on: respecting the file structure, keeping identifiers intact, joining sheets by key without trusting a bad merge, working on large files safely, and a pre-upload checklist to run every time.
Module openen → - Module 0411 min leestijd
The QA mindset: evidence, verification, and knowing when something is done
Why a successful submission is not a finished change, where every value must come from, what evidence to keep, how to classify a problem before fixing it, and the weekly loop and definition of done that keep catalog work provable.
Module openen →