Calculate a fidget keyboard reorder quantity for each exact SKU using the demand you expect to cover, usable stock already available and relevant inbound stock. Keep light-up and non-light versions separate. A total for a whole product family can hide the fact that one version needs replenishment while another remains unsold.
The calculation below is a planning worksheet, not a demand forecast or an order recommendation for every store. Replace the illustrative numbers with your own sales, stock and supplier information.
Count usable inventory first
Start with physically available, sellable units of the selected version. Exclude damaged stock, permanent demonstration pieces and units already allocated to customers. If returns are waiting for review, keep them outside usable inventory until your receiving decision is complete.
Record confirmed inbound quantities separately, with their expected availability date. Count only the arrivals relevant to the planning period, and avoid counting the same inbound shipment both as available stock and as a future receipt.
Keep the version attached to the sales record
The one-key keyboard series identifies LC-01 as non-light and LC-02 as light-up. Use individual SKU rows when reviewing sales and replenishment. Do not add one version's sales to the other's simply because both use a one-key format.
If the retail listing combines variants, export or record sales at the variation level. For shared displays, count remaining units by variant rather than estimating them from the display's overall appearance.
Choose the period the order should cover
State how long it is expected to take until stock becomes sellable and how often you review purchasing. For a periodic review approach, a starting coverage period is the expected replenishment time plus the time until the next purchasing review. Both inputs should reflect your actual operation.
If you add a buffer, explain why: uncertain arrivals, uneven sales or a minimum display requirement. A buffer is a business choice, not a universal percentage. Avoid extrapolating a short promotion or one unusually large sale as a permanent weekly rate.
Use the same unit throughout the calculation
Planning quantity = expected demand during the coverage period + chosen buffer − usable stock − relevant confirmed inbound stock. If the result is negative, use zero as the starting purchase requirement. This formula assumes you have already excluded committed units from usable stock.
Illustrative example: expected demand is 8 pieces per week over 5 weeks, with a chosen buffer of 8 pieces. Usable stock is 14 and a relevant confirmed inbound shipment contains 10. The calculation is (8 × 5) + 8 − 14 − 10 = 24 pieces. None of these figures is a RUIWO MOQ, sales result or delivery commitment.
| Input | Where to get it |
|---|---|
| Expected demand | Your sales record with stockouts and promotions identified |
| Coverage period | Current replenishment estimate and purchasing review schedule |
| Buffer | A documented operating decision |
| Usable stock | Physical count less excluded units |
| Inbound stock | Confirmed orders with relevant arrival estimates |
Check order constraints after calculating need
Ask for the current minimum quantity and order increment for the selected SKU. If the quote requires more than your calculated need, compare the extra stock commitment with alternatives such as a later order or a different approved assortment. Do not silently round up and call the result customer demand.
Confirm the current version and package using the keyboard version guide. A reorder calculation does not authorize a feature substitution.
Review after the new stock arrives
Record the actual date the units become available for sale, reconcile quantities using the receiving checklist, and compare your planning assumptions with what happened. Keep the calculation version so you can improve the next purchasing decision.
Send RUIWO the exact keyboard SKUs and calculated quantities to check the current offer, packing constraints and availability before placing the next order.
