Definition
SKU onboarding is the process of taking a new product from source data to catalog-ready through six fixed gates: identifier, category, required attributes, imagery, validation, and publication to every channel that carries it. It is a workflow with a defined finish line rather than an open-ended editing session. A SKU is either onboarded or it is not, and naming the gates is what makes that question answerable.
Key points
- Identifier — a stable internal SKU and, where the product carries one, a GTIN, so the record can be matched anywhere else it appears.
- Category — a single node in the taxonomy, which is what determines which attributes are required of this product at all.
- Required attributes — every field the category and the target channels mark mandatory, each holding a real, sourced value.
- Imagery — a primary image meeting the channel's size, background, and framing rules, plus any alternates the category requires.
- Validation — the record clears the automated rule set with no waived errors and no outstanding exceptions.
- Publication — pushed live to the storefront, the feeds, and the marketplaces that carry the category, and confirmed accepted by each.
Who moves a SKU through the gates?
A buyer or the supplier provides source data; catalog operations maps and completes it; a merchandiser or category owner approves the classification; studio or the supplier delivers imagery. What makes it a gate rather than a task is that each has a named owner and an explicit exit test that either passes or does not. Elapsed time is then measured gate to gate, which is how a team locates its actual bottleneck — almost never publication itself, and usually waiting on imagery or on an attribute only the manufacturer can answer for. Blocked SKUs should sit visibly at the gate that stopped them.
Common pitfalls
- Waiving a gate "temporarily" to hit a launch date, after which the exception becomes the record's permanent state because nothing is scheduled to revisit it.
- Declaring onboarding complete at storefront publication while marketplace and shopping feeds are still rejecting the same record.
- Reporting on SKUs touched rather than SKUs that cleared every gate, which makes a growing backlog look like throughput.
FAQ
How is SKU onboarding different from catalog enrichment?
Onboarding is a bounded workflow for one new product, with a start and a finish. Enrichment is ongoing improvement of records that already exist. Enrichment is one of the things done inside onboarding — clearing the required-attributes gate — but it keeps running long after a SKU has gone live.
What actually makes onboarding slow?
Usually waiting rather than working: source data arriving in an unusable shape, imagery not yet shot, or a required attribute only the manufacturer can supply. Gates make the waiting visible. A team measuring only total elapsed time knows onboarding is slow; a team measuring gate to gate knows where and why.
Source
The identifier gate rests on the GS1 GTIN standard, which defines the globally unique keys used to identify a trade item consistently across trading partners and channels. The required-attribute and imagery gates can be read almost directly off Google's Merchant Center product data specification, which lists what a record must carry to be accepted.