A distributor has space for 100 selling units in a trial order. The first draft contains 20 SKUs with five units each. It looks diversified, but seven products are compact vibrators in similar price positions, four are color variants, and several products are too shallow to support even one normal retailer reorder.
The problem is not simply that 20 SKUs are too many. The problem is that the order cannot explain what each SKU is supposed to prove.
The quantities below are a planning example, not a recommended order or a statement of current supplier minimums.
This guide is for a distributor or established retailer that already has customers, traffic or order history. A new store without a baseline needs a different starting method, because it cannot classify a product as strong or weak before the product has received a fair amount of qualified exposure.
First remove products that do the same commercial job
Compare every proposed SKU across five fields:
- Downstream customer type
- Main customer need
- Expected retail price position
- Product format and explanation required
- Closest substitute already in the order
If two products match on four or five fields, they probably do not create two different tests. Keep both only when there is a clear reason, such as a meaningful function difference, a different downstream channel or evidence that both price positions are needed.
Color alone is usually not a new commercial role. If a distributor wants to test color preference, treat that as a deliberate color test instead of counting every color as assortment breadth.
Give every selected SKU one job
For a 100 unit worked example, a distributor might reduce 20 shallow SKUs to six clearly different roles:
- Core product A: 30 units for the broadest group of existing retailers
- Core product B: 25 units for a second established customer need
- Margin product: 15 units with a visible reason for a higher retail price
- Channel specific product: 15 units for a retailer type not covered by the core items
- Test product A: 8 units for a new format or function
- Test product B: 7 units for a second controlled question
This is not a universal allocation. Its value is that the quantity follows the job. A core product has enough depth to serve several downstream orders. A test product receives limited exposure. A channel specific item earns its place by reaching a buyer that the core range does not serve.
An equal split of roughly 17 units across six SKUs would be simpler mathematically, but it would ignore the different purpose of each SKU.
This allocation is a prelaunch hypothesis. It helps the distributor avoid obvious duplication before sales history exists. It must be replaced by actual sales, margin, inventory and customer data after the first operating period.
Check whether the quantity is usable for downstream orders
Suppose the distributor’s typical retailer takes six units of a core product. Five units in stock cannot even support one normal order. Thirty units can support five similar orders before safety stock and samples are considered.
This calculation should use the distributor’s own retailer order pattern, not the example above.
For each core SKU, write down:
- Typical units ordered by one downstream customer
- Number of customers expected to receive the item
- Units reserved for samples, replacements or sales use
- Supplier purchasing condition and carton quantity
- Time needed to replenish after a reorder
If the planned quantity cannot support the expected customer count, the assortment is broad but not operationally usable.
Convert package dimensions into occupied space
Do not compare only product photos. Calculate the packaged volume for each SKU:
Package length × package width × package height × ordered quantity
Use the same unit for every product. Then compare the total carton quantity, gross weight and any special packing condition.
A compact product and a large stroker can appear equally large in catalogue thumbnails but use very different warehouse and shipping space. Product dimensions are useful for understanding scale, but package and carton data are what the distributor needs for freight and storage planning.
Our sex toy product variant and SKU planning guide explains how unnecessary colors and variants create separate inventory records without necessarily adding customer coverage.
Replace the first order hypothesis with operating data
Each SKU should have a next decision written beside it, plus the data needed to make that decision. After sales begin, record units sold, selling period, gross margin, current stock, inventory age, customer questions, return reasons and actual replenishment lead time.
For a core SKU, the next question might be whether enough downstream customers reorder before stock reaches the distributor’s chosen reorder point. For a test SKU, the question might be whether retailers understand the new format and whether product pages receive qualified interest. For a margin product, the question might be whether the visible difference supports the intended price position.
A practical reorder point starts with:
Average demand during replenishment lead time + safety stock
If a SKU sells an average of two units per day, replenishment takes 20 days and the distributor chooses ten units of safety stock, the worked reorder point is 50 units. This is only an arithmetic example. The distributor should use its own sales history, confirmed lead time and risk tolerance. New, seasonal or irregular products may not have enough stable data for an automatic formula, so a manual review is still required.
Do not apply one reorder point or one sales target to every SKU. Core, channel specific and test products have different demand patterns and service roles.
How long should a test SKU remain in test?
There is no universal test duration. A product that receives 2,000 qualified visits in one month has produced more evidence than a product that receives 80 visits in the same period. Supplier lead time, promotion timing, seasonality and the retailer’s normal order cycle also change the answer.
Retail operating systems still provide useful reference points. Square recommends a short inventory review every week or two, while Lightspeed recommends a trailing sales period of 30 to 90 days for products that remain available through most of the year. These are reference practices, not sex toy industry rules.
For an evergreen sex toy SKU, AIYUEWEI uses the following working cadence as a practical starting point:
- Days 0 to 14: verify that the item is actually available, correctly listed, visible in the intended channel and tracked correctly. This period checks execution. It is too early to call a winner from sales volume alone.
- Around day 30: run the first operating review. Compare qualified traffic, orders or enquiries, conversion, margin, customer questions, returns, remaining stock and any discount or placement that affected the result. Fix an obvious content, price or visibility problem before rejecting the product.
- Days 60 to 90: make the first Test, Core or Stop classification for a product that has received enough qualified exposure. Use weekly or biweekly reviews so a stockout, promotion or one unusual order does not control the conclusion.
- Days 90 to 180, or after at least one complete replenishment cycle: decide whether a proven Core SKU is strong enough to become a Hero product and receive deeper purchasing, stronger placement and more marketing attention.
The calendar does not replace evidence. If the page has almost no qualified traffic, 90 days of waiting is not a valid test. If a distributor sells mainly through sales representatives, use retailer enquiries, quotation requests, order lines and repeat orders instead of ecommerce conversion.
Move a SKU from Test to Core, then from Core to Hero
Felix’s proposed operating logic is sound, but total sales alone can give the wrong answer. Homepage placement, paid traffic, discounts and stock availability can make one product look stronger or weaker than it really is.
Before moving a Test SKU into the Core group, check whether it has:
- Consistent demand across several weeks, not one promotion or one large order
- Positive gross profit after discounts, freight support, returns and channel costs
- A healthy response rate for the traffic or sales effort it received
- Acceptable return, complaint and product explanation rates
- Evidence of repeat orders, repeat enquiries or more than one downstream customer
- A replenishment route that can support the expected demand
Before moving a Core SKU into the Hero group, require it to remain in the top group for at least two consecutive review windows and to perform after a reorder or increase in exposure. The product should still create healthy profit, not merely unit volume, and the supplier lead time, purchasing condition and stock plan must support deeper buying.
Increase the purchase quantity in steps. A fast selling product can justify a larger reorder, but a large jump based on one short period can create excess stock if the result came from temporary promotion.
Consider a simple comparison. Test SKU A sells 24 units from 2,400 qualified product page visits, while Test SKU B sells 18 units from 600 qualified visits. A has more unit sales, but B converts at three times the rate. If B also sells at full price, receives fewer returns and repeats the result after replenishment, it may be the stronger Core candidate. The decision changes again if B cannot be replenished reliably.
After the review window, place every SKU into one of five actions:
- Promote from Test to Core and reorder with more depth
- Promote from Core to Hero only after repeated strong performance
- Keep the customer need but change the product, price, content or channel
- Keep only one of two overlapping SKUs
- Stop because the SKU added no useful customer coverage
As more history becomes available, review each SKU’s profitability, carrying cost, customer response and position in the product lifecycle. A product that looked different in the catalogue may prove redundant in real orders. Another product with modest volume may still earn its place because it serves a profitable customer group that no other SKU covers.
The low MOQ sex toy trial order guide explains why a small order should still lead to a defined decision.
Send the supplier a usable mixed order brief
Before asking for a final quotation, provide:
- Target downstream customer types
- Target product categories and price positions
- Total budget or quantity range
- Maximum workable SKU count
- Products already selected and their assigned roles
- Color variants that are essential, not merely preferred
- Warehouse or carton limitations
- Data still required, including package size, carton quantity, weight and current purchasing condition
This gives the supplier enough context to identify obvious overlap and operational conflicts. It is more useful than sending a long catalogue screenshot with circles around many products.
How AIYUEWEI can help with a mixed order
AIYUEWEI can organize candidate products by downstream customer, customer need, price role, product size and nearest substitute. We can flag repeated functions or variants before they consume the trial budget.
For the shortlisted products, we can coordinate with relevant partner factories and supply resources to verify specifications, package dimensions, carton information and current purchasing conditions. These details are verified for the selected products and are not presented as universal guarantees.
Frequently asked questions
Is 20 SKUs always too many for a first mixed order?
No. The right number depends on budget, downstream order size, purchasing conditions and operational capacity. Twenty SKUs become a problem when the quantity is too shallow, the products overlap or the distributor cannot maintain the product data and reorder decisions.
Should different colors be counted as different tests?
Only when color preference is the question being tested. If the main question is whether the product format sells, too many colors can divide one demand signal into several weak signals.
Which data should be confirmed before estimating freight and storage?
Confirm package dimensions, units per carton, carton dimensions, gross weight and any special packing requirement. Product size alone is not enough.
Is 30 days enough to decide whether a test product should become a core product?
Usually not by itself. Thirty days is a useful first operating check. A stronger first classification normally needs enough qualified exposure across roughly 60 to 90 days, followed by at least one replenishment cycle before a Core product is promoted to Hero status. Low traffic, seasonality or long B2B order cycles require a longer window.
Turn a product list into an operating plan
Share the downstream customer types, target categories, budget range, expected SKU count and warehouse limits through our enquiry page. AIYUEWEI can help reduce overlap and organize a candidate mix with clear roles and verifiable data requirements.
