Wholesale Sourcing
Building a Jewelry Wholesale Catalog: SKU Structure That Scales
A catalog that starts as a spreadsheet and ends as a pile of confused rows is the most common wholesale operations failure. Here is the SKU structure that scales.
By the time a wholesale catalog reaches 200 rows, three things have usually broken: sizes are written inconsistently ("7" vs "US7" vs "N"), the same design appears under two SKUs because two salespeople added it, and nobody can pull a report of "all sterling studs in stock" without an afternoon of filtering. The cause is not bad staff. It is a SKU structure that was never built for growth. A catalog is only sortable if the SKU itself carries the information.
The six-part SKU that carries the data
A scalable jewelry SKU reads as six hyphenated blocks, e.g. STU-SS-RND-04-DF-01. Breakdown: category (STU = stud, TEN = tennis bracelet, RNG = ring, PEN = pendant, CHN = chain); metal (SS = sterling silver, GF = gold-fill, 10K, 14K); stone shape or type (RND = round, OVL = oval, CZB = cubic zirconia, MOS = moissanite, LGD = lab-grown diamond); size (04 = 4 mm, 65 = 6.5 mm, chain length in cm); colour/grade (DF = D-F colour, GN = green, PK = pink); sequence number (01, 02 for multiple designs in the same group). Every block is a fixed code, not free text. This structure mirrors how buyers actually filter — see the category logic in stud earring SKU planning.
The columns every catalog row needs
Beyond the SKU, each row should carry: design name, category, metal and stamp, stone type and carat/mm, size range, unit wholesale price, MOQ, lead time, weight (grams), packaging reference, and supplier code. Weight matters because it drives shipping cost; packaging reference ties to the box and tag system in private-label tags and boxes. Keep one row per size break, not one row with "sizes 6-9" — you need to know which size reordered. Metal and stamp wording must match FTC 16 CFR Part 23 and ISO 9202 fineness marking so the catalog reads the same as your tags.
What to keep out of the SKU
Do not put supplier name, price, or launch date in the SKU. Supplier name changes if you dual-source; price moves every season; launch date is metadata, not identity. Do not encode colour in a free-text way ("light pink" vs "rose" — pick one code). Do not reuse a retired SKU for a new design — retired numbers stay retired so old purchase orders still trace back. For the import and disclosure side, keep the treatment and origin file alongside the catalog row; see lab-grown traceability files.
How the catalog grows without fragmenting
Add a catalog review every quarter: merge duplicate SKUs, retire slow lines, and re-check size and colour codes against what actually shipped. A catalog that is not reviewed becomes a fiction within a year. Tie retirement to reorder data — lines that have not reordered in two quarters move to "archived" and out of the active sheet. Build the active sheet around the 2025 reorder leaders in the 2025 wholesale reorder report, and keep MOQ and price columns aligned with the supplier terms in new-buyer payment terms.
How to migrate an existing messy catalog
If your current sheet has free-text sizes and duplicate rows, do not retype everything at once. Build the new SKU structure as a second column, then migrate one category per week. Start with studs (highest reorder volume), then tennis bracelets, then rings. Leave the old SKU in a retired column so old POs still trace. Within two months the new sheet is the active one and the old sheet becomes an archive. Trying to rebuild all 500 rows over a weekend creates more errors than it fixes.
Whatever tool you choose, the one rule that matters is this: every size and colour value must be a controlled list, not free text. As soon as two people can type 7, US7, N or size 7 into the same column, the catalog stops answering questions and starts creating them.
FAQ
Should we start with a spreadsheet or a proper PIM?
A structured spreadsheet is fine up to about 500 SKUs. Beyond that, move to a PIM or ERP so the SKU codes are enforced rather than typed freely.
How many sizes should one SKU cover?
One size per SKU. Ring sizes, mm stone sizes and chain lengths are separate rows — otherwise reorder reporting breaks.
Do we need a supplier code in the row?
Yes, as a column, not in the SKU. It lets you pull "everything from supplier A" when you need to QC or replace them.
What about private-label vs own-brand SKUs?
Add a channel code (e.g. WL = wholesale, PL = private label) as a leading block. Same design can serve both channels under different codes without mixing pricing.
HOLYCOME delivers wholesale orders with a SKU sheet already structured by category, metal, stone, size and colour, plus a weight and MOQ column. Ask for the current catalog template and SKU code list.
