Answer — name the customer jobs your starter assortment was built to solve, then convert each job into a measurable test cell with a clear pass/fail rule and a small, low‑risk SKU set. Run those tests, record the demand signal linked to each job, and only scale a job‑winner when evidence meets your predefined pass criteria.
Why the business stage and demand signal matter
An assortment assembled around customer jobs usually reflects an early discovery stage: you are learning which practical needs (for example, quick at‑home application, salon‑grade durability, or reusable sets) drive repeat purchases. Make that business stage explicit in your plan and capture the demand signal you observe — e.g., sell‑through velocity, sample requests, DTC conversions, salon reorder interest — so your decisions are evidence‑led rather than opinion‑led.
The smallest useful test assortment
- Limit the test to the smallest number of SKUs that still isolates job hypotheses — typically 3–6 SKUs, one SKU per job hypothesis.
- Choose low‑risk supply: select low‑MOQ products so you can run live tests without large upfront inventory.
- Keep variables minimal per SKU (one shape, one adhesive option, one finish) so KPIs reflect the job, not the styling differences.
- Track identical KPIs across SKUs: sell‑through rate, repeat purchases or reorder requests, return/fit rates, and qualitative customer feedback tied to the job outcome.
Evidence required before scaling
- Consistent sell‑through at your channel’s standard velocity over the evaluation window.
- Repeat restock or reorder requests from channels, salons, or customers demonstrating demand beyond an initial impulse buy.
- Acceptable defect and return rates on the job outcome you promised (fit, longevity, reusability).
- Qualitative confirmation: customer feedback that explicitly links the purchase to the job solved.
From the 365 Workbench
Operational guidance to reduce risk while you learn: 365nails advises wholesale buyers to use low‑MOQ products for testing and then scale proven best sellers into wholesale or custom production. Use low‑MOQ tests to collect the evidence listed above before moving a SKU into larger runs or custom manufacturing.
Operator Move
Run tests with a one‑page brief per job hypothesis, a 4–8 week evaluation window, and clear pass/fail rules tied to the evidence checklist. Put results into three buckets: keep (scale), iterate (request new sample or refine), or retire. When a SKU passes, promote it into your core assortment and update merchandising so customers can find solutions by job as well as by look.
Practical navigation tip: use the 365nails catalog hub to shortlist test SKUs — the catalog hub organizes product discovery by product type, craft, MOQ, style, sourcing need, and business stage — making it easier to pick low‑MOQ candidates that match each job hypothesis.
