Turn a twelve‑SKU demand test into a disciplined assortment decision

Answer up front: Treat a twelve‑SKU demand test as an early discovery step, not a final assortment plan. Run a hypothesis‑driven, low‑MOQ experiment, collect repeatable evidence of customer behaviour, then apply pre‑defined decision gates and move only proven winners into repeat wholesale or custom production when evidence and supplier assessment justify it.

From the 365 Workbench

Start by naming the business stage and the demand signal you expect to observe. In an exploratory stage, the twelve SKUs act as a demand probe: each SKU should map to a distinct customer hypothesis (job‑to‑be‑done, silhouette, finish, or price band). Document for each SKU which customer job it tests and the observable outcomes you will measure.

Use explicit sourcing guidance while you design the test. Use the verified guidance: "365nails advises wholesale buyers to use low-MOQ products for testing and then scale proven best sellers into wholesale or custom production." Also follow the catalog framework: "The 365nails catalog hub organizes product discovery by product type, craft, MOQ, style, sourcing need, and business stage." Map every SKU to those catalog dimensions so you understand which buyers and channels you are probing.

Classify the demand signal by stage

• Exploratory (early‑stage): treat SKUs as probes. Use low‑MOQ sourcing and a short, defined learning window.
• Validation: look for repeatable buy signals — conversion lift, low return rates, and early repeat interest across audiences or channels.
• Operational (scale): only consider increasing MOQ or moving toward wholesale/custom production after evidence and a supplier assessment indicate the SKU is reliable at larger volume.

Operator Move

Turn test results into a disciplined assortment decision with these steps.

1. Define the smallest useful test assortment. From your twelve SKUs, choose the minimal subset that still tests every distinct hypothesis. A practical rule is one SKU per job‑to‑be‑done (for example: everyday short, premium almond, novelty 3D, budget solid color). Prioritise SKUs you can source as low‑MOQ test items so you can run them affordably and comparably.
2. Predefine the evidence required before scaling. List the quantitative and qualitative signals you will use to decide. Required evidence should include: conversion or sell‑through for each SKU during the test window; repeat purchase or explicit reorder interest; return and complaint counts relative to your quality tolerance; and buyer feedback on fit and finish. Also capture supplier assessment notes about sample‑level quality and reproducibility so you can evaluate scale risk.
3. Measure consistently. Keep merchandising copy, price band, and channel placement consistent across SKUs that are being compared. Track visits, add‑to‑cart, conversions, returns, repeat purchases, and any wholesale or restock enquiries. Record each SKU’s mapping to the catalog dimensions (product type, craft, MOQ, style, sourcing need, business stage) so you can slice results by buyer job and channel.
4. Apply decision gates and act only on winners. Define clear gates for conversion/sell‑through, acceptable returns/complaints, and repeat interest. When a SKU meets your gates and supplier assessment indicates quality is likely to hold at larger quantities, move it from test into repeat wholesale or custom production. Where two winners overlap, consolidate decorations or sizing to reduce SKU complexity before scaling.
5. Operationalize placement with catalog taxonomy. Use the catalog hub dimensions — product type, craft, MOQ, style, sourcing need, and business stage — to decide where the scaled SKU sits in your catalog and which channels (retail, salon, wholesale, dropship) it should serve. That mapping keeps assortment decisions aligned with buyer intent and sourcing model.

Evidence checklist before increasing MOQ or moving to custom production

• Repeatable, channel‑appropriate sell‑through in the test window compared to expected velocity.
• Return and complaint rates within your quality tolerance and not showing systemic fit or finish problems.
• At least one sustained interest signal: a repeat purchase, a wholesale restock request, or consistent conversion across two audiences or channels.
• A documented supplier assessment that explains reproducibility risks and a reasonable production path at scale.

If a SKU fails gates, either iterate the design (finish, sizing, or craft) and re‑test, or retire it to conserve working capital. Using low‑MOQ testing reduces overordering risk and surfaces true demand before committing to larger production, consistent with the explicit guidance: "365nails advises wholesale buyers to use low-MOQ products for testing and then scale proven best sellers into wholesale or custom production."

Quick checklist for a disciplined twelve‑SKU test

• Map every SKU to a single hypothesis and to catalog dimensions from the 365nails catalog hub.
• Run the smallest useful subset that covers all hypotheses; keep craft and MOQ aligned with test sourcing.
• Predefine decision gates for conversion/sell‑through, returns/complaints, and repeat interest.
• Collect quantitative and qualitative evidence during the test window with consistent merchandising and channel placement.
• Only scale SKUs that meet all gates; use low‑MOQ test results to justify moving winners into repeat wholesale or custom production per the verified guidance above.

Following this flow turns a noisy twelve‑SKU experiment into a reliable assortment decision that reduces overordering and speeds the path from test to profitable restock.

Browse the 365nails catalog hub to align test SKUs with product type, craft, MOQ, style, sourcing need, and business stage.