Answer first
Plan depth by SKU, not by collection name alone. Define each sellable variation, classify it as core, seasonal, or test, then set units from comparable demand, selling period, channel, space, cash budget, and replenishment options. Give proven core SKUs more depth; keep new or trend-led SKUs controlled until sell-through evidence improves. Review units sold, availability, weeks of supply, stockouts, returns, markdowns, and aged inventory. Treat every quantity as a planning assumption to validate with your own data and written supplier terms. [1] [2]
1. Define SKU depth and breadth
SKU depth is the planned unit quantity for one sellable variation, such as a pendant with a specified crystal description, finish, size, chain, and pack configuration. Breadth is the number of distinct options or lines. A range can be broad but shallow, or narrow but deep.
Define the SKU before comparing demand. If stone description, finish, size, chain, or pack configuration changes, decide whether it needs a separate SKU. Oracle describes assortment planning as balancing product variety and product variation, while its documentation reviews depth by product attributes.
| Term | Buyer meaning | Use |
|---|---|---|
| Breadth | Number of product options | Choose styles and lines |
| Depth | Units per SKU | Set the buy quantity |
| Channel depth | Units by store, ecommerce, region, or cluster | Match local demand |
Buyer checklist
- Give every sellable variation a unique code.
- Separate confirmed specifications from assumptions requiring an approved sample.
- Use one consistent sales and inventory period.
2. Classify each SKU before setting quantity
Core SKUs have repeatable demand or a clear range role. Seasonal SKUs depend on gifting periods, events, weather, or regional calendars. Test SKUs are new, trend-led, or supported mainly by qualitative evidence.
A core item may justify deeper opening depth when comparable sales and replenishment evidence are credible. A test item should earn additional depth through evidence. These are commercial planning labels, not claims about wellness, healing, energy, medical, spiritual, or feng-shui efficacy; this article does not validate such claims.
| Role | Depth posture | Monitor |
|---|---|---|
| Core | Relatively deeper, subject to budget | Comparable sales and stockouts |
| Seasonal | Deeper only for the selling window | Calendar and prior event sales |
| Test | Controlled opening quantity | Early sell-through and feedback |
Buyer checklist
- Assign every SKU a documented role.
- Set the evidence needed to deepen or stop a test SKU.
- Set review dates for seasonal and test items.
- Keep product storytelling separate from substantiated demand data.
3. Build the demand signal at SKU level
Use the same or closely comparable SKU first, then comparable attributes, channel demand, seasonality, price architecture, and planned selling time. Oracle identifies historical sales, product attributes, location hierarchy, and calendar hierarchy as relevant data; Shopify recommends reviewing inventory, customer data, seasonality, and SKU-level performance.
Normalize comparisons. A SKU selling 30 units while available for 30 days is not directly comparable with one selling 30 units while available for 90 days. Flag launch dates, promotions, price changes, stockouts, and channel exposure.
| Signal | Use | Caution |
|---|---|---|
| Sell-through | Shows stock conversion | Define the denominator |
| Weeks of supply | Shows likely coverage | Forecasts are not guarantees |
| Stockouts | May hide demand | Check availability first |
| Returns/markdowns | Flags expectation or price issues | Investigate cause |
Buyer checklist
- Calculate sales only during availability.
- Compare like with like by form, price band, material description, and channel.
- Separate full-price, promotional, and markdown sales where possible.
- Label every new-SKU forecast as an assumption.
4. Convert evidence into opening depth
A practical starting calculation is: opening units = expected sales during the review window + approved safety buffer − usable stock already on hand or committed. The review window should reflect the selling calendar and reaction time. The calculation organizes a decision; it does not guarantee an outcome.
For a new SKU, define locations or channels, opening units, review date, and reorder, hold, transfer, markdown, or exit triggers. If supplier MOQ, pricing, lead time, capacity, documentation, or availability matters, obtain it from written quotation rather than assuming it.
Buyer checklist
- Document the review window and evidence source.
- State the safety-buffer rationale.
- Create separate rules for core, seasonal, and test SKUs.
- Confirm terms with written quotation, applicable requirements, documentation, and approved sample.
5. Allocate depth by channel and market
A total buy is not a good allocation by itself. Allocate units to channels where the SKU has a reason to sell and where it can be presented and replenished. A flagship store, ecommerce site, travel-retail location, and regional boutique may need different depth.
Use clusters when store-level data is thin. For Europe, North America, and the Middle East, treat country and regional assumptions separately unless data demonstrates comparability. Language, labeling, claims review, import requirements, and local merchandising are launch-readiness checks, not reasons to invent demand.
Buyer checklist
- Create a channel or cluster allocation table.
- Use local sales, event, customer, and space evidence.
- Assign an owner for reallocations.
- Review market-specific product information and import requirements.
6. Govern depth with an in-season scorecard
Review units sold, net available units, sell-through, weeks of supply, stockout days, returns, markdown exposure, and gross margin against plan by SKU and channel. Use thresholds as retailer-specific decision aids, not universal standards.
Record why each action was taken. A transfer may solve a location imbalance; a reorder may address proven demand; a hold may protect cash while evidence develops. Before repeat orders, reconfirm approved specifications, disclosures, finish references, packaging information, and quality controls.
Buyer checklist
- Review at a fixed cadence during the selling period.
- Separate availability problems from demand problems.
- Log every reorder, transfer, markdown, hold, and exit.
- Reconfirm specifications and documentation before repeat orders.
7. Buyer checklist for supplier discussion
Ask the supplier to respond against each SKU rather than only at collection level. Match the quote to the SKU record and approved sample. Do not assume GemMira MOQ, pricing, lead time, capacity, certifications, testing, material origin, treatment status, stock, logistics, delivery, warranty, packaging capability, or customer outcomes; those details are subject to written quotation, applicable requirements, documentation, and approved sample.
Buyer checklist
- Does each SKU have a unique code and variation definition?
- Is opening depth tied to evidence or a stated test assumption?
- Are market and claims-review owners assigned?
- Are commercial and technical details documented?
- Is an approved sample required before release?
- Are reorder, transfer, markdown, and exit rules documented?
Frequently asked questions
What is a sensible starting depth for a new crystal jewelry SKU?+
There is no universal unit number. Use the review window, comparable demand, available space, cash budget, replenishment path, and a documented test-risk limit. Treat the result as an assumption to validate.
Should retailers buy more styles or deeper quantities of fewer styles?+
Choose from range role and evidence. Proven focused items can justify more depth; uncertain markets may need broader, shallower tests. Compare both options against SKU demand, space, budget, and review capacity.
How often should SKU depth be reviewed?+
Set a cadence matching the selling window and reaction time, with extra checkpoints for seasonal launches, events, new channels, or material changes. Document it before launch.
What should buyers ask before increasing depth?+
Request written confirmation of the exact specification, quotation, applicable requirements, documentation, and approved-sample reference. Do not assume MOQ, price, lead time, capacity, certifications, testing, origin, treatment, stock, logistics, delivery, warranty, packaging, or outcomes.
Conclusion
Crystal jewelry assortment depth planning works best when every quantity has a reason, a channel, and a review trigger. Define the SKU, classify it, use comparable evidence, allocate by market, and manage the result with a live scorecard. Supplier-specific commercial and technical decisions remain subject to written quotation, applicable requirements, documentation, and approved sample.
Product category references
Explore relevant GemMira formats.
Next step
Move from general guidance to your specific brief.
For a GemMira wholesale, private-label, or custom inquiry, share the product category, market, material direction, and any available reference images. Commercial terms, final specifications, and sample options are confirmed in a quotation and approved pre-production sample. Email your requirements to info@gemmira.com.
Start an inquiry with this guide →Email info@gemmira.com