Set a low-MOQ sweater reorder point for each sellable style-color-size SKU, not for the style total. Trigger review when usable inventory plus confirmed inbound stock approaches forecast demand during the full replenishment lead time plus a buyer-chosen safety buffer. Before ordering, test whether the factory MOQ, yarn availability, cash exposure and remaining full-price selling window still make the reorder commercially sensible.
Separate the alert from the buying decision
A reorder point is an alert that available inventory is approaching the quantity expected to be consumed before replenishment arrives. It is not an automatic instruction to repeat the original order. Oracle's inventory documentation expresses the basic logic as safety stock plus forecast demand during replenishment lead time, with available quantity including on-hand stock and planned receipts.
For a small sweater brand, translate that into a review rule: compare usable on-hand units plus reliable inbound units, less committed orders, with expected SKU demand during the complete reorder cycle plus the chosen buffer. Then make a commercial decision. A mathematically triggered reorder can still be wrong if the minimum quantity creates excessive tail-size stock, the season is ending or an approved yarn can no longer be obtained.
Build the calculation at SKU level
A style may look healthy in total while its best size is almost unavailable and slow sizes remain. Create one row for every style-color-size combination. Record usable stock, committed stock, confirmed inbound stock, recent paid sales, returns placed back into saleable inventory, cancellations, stockout days and the required availability date. Exclude damaged, reserved, sample or uninspected units unless they can genuinely fulfill customer demand.
Use a demand period that matches the business. Weekly demand may be practical for a small brand, but do not divide a launch spike across many weeks and call it a stable average. Separate paid sales from wait-list signups, and flag days when an SKU was unavailable because recorded sales then understate demand. Promotions, wholesale orders, influencer activity and seasonal weather can also make a simple average misleading.
Measure the whole replenishment lead time
The relevant lead time starts when the brand can issue an actionable repeat order, not when knitting begins. Include commercial confirmation, deposit or payment milestone, yarn confirmation, any necessary color or material approval, production, finishing, inspection, packing, export handling, transport, customs and warehouse receiving. Use the route actually planned for the reorder rather than the fastest past order.
Ask the manufacturer to reconfirm capacity and material availability. A prior approval helps control specifications, but it does not reserve the same yarn lot, price or production slot. If color continuity matters, follow a written dye-lot plan and decide whether a new lot requires a shade approval before production. The calendar must also include buyer response time; an unanswered approval is part of real elapsed time.
Choose safety stock from uncertainty, not habit
Safety stock is the brand's buffer against demand and supply variation. There is no universal percentage for custom sweaters. A core, year-round SKU with repeatable demand may justify a different service target from a fashion color with a short selling window. Review demand variability, lead-time variability, lost-sale consequence, substitute sizes or colors, carrying cost and markdown exposure.
For limited data, use scenarios instead of false precision. Model a base demand case, a stronger case and a delayed-arrival case. State which case the buffer is intended to protect. Revisit the result as sales and supplier information improve. A larger buffer can reduce stockout risk but increases cash and end-of-season exposure; the formula cannot decide that trade-off for the brand.
Test the MOQ against the size curve
The trigger answers when to review; MOQ and commercial demand answer whether and how much to buy. Confirm whether the minimum applies by style, color, yarn or another production condition, and whether sizes may be assorted. Do not spread a color minimum evenly across sizes merely to complete the quantity.
Rebuild the size curve from SKU sales, returns and stockout evidence. If only one or two sizes justify replenishment but the required run would create unwanted units elsewhere, compare alternatives with the supplier: a later consolidated order, fewer repeated colors, a compatible yarn plan or no reorder. Every option is subject to technical and commercial feasibility; never assume that combining styles or colors satisfies a production minimum.
| Signal | What it may mean | Decision check |
|---|---|---|
| Core sizes near trigger, tail sizes high | Original size curve is misaligned | Rebuild the curve; do not repeat it unchanged |
| All SKUs selling, season closing | Demand exists but arrival may be late | Compare required delivery with full-price window |
| Sales spike after promotion | Recent velocity may not persist | Separate baseline and campaign demand |
| Trigger reached, yarn unavailable | Original route cannot be repeated immediately | Review new lot, substitution approval and timing |
| MOQ greatly exceeds forecast need | Stockout risk may be smaller than overstock risk | Model cash, markdown and no-reorder cases |
Use a dated go, hold or stop gate
Set a recurring review date before inventory reaches the trigger. At each gate, record the data cut-off, forecast assumption, available and inbound quantities, lead-time confirmation, MOQ, proposed size curve, landed-cost estimate, latest useful arrival date and decision owner. Choose go, hold for more evidence or stop. A hold needs a next review date; otherwise it becomes an accidental stockout decision.
Once approved, send a controlled repeat-order pack: purchase order, current tech pack, sealed-sample reference, yarn and color standard, measurement chart, labels, packaging, inspection requirements and all approved changes since the original order. Treat a substitution, revised finish or new label as a controlled change, not as an invisible shortcut.
Reorder-point checklist for small sweater brands
- Track usable, committed and inbound inventory by style-color-size SKU.
- Correct sales history for stockout days, returns and one-off promotions.
- Forecast demand across the complete replenishment lead time.
- Choose and document a safety buffer based on uncertainty and service intent.
- Reconfirm yarn, dye lot, capacity, approvals, production and transport timing.
- Check whether arrival precedes the useful full-price selling window.
- Rebuild the size curve rather than copying the first order.
- Test factory MOQ against forecast demand, cash and markdown exposure.
- Record a dated go, hold or stop decision with an owner.
- Release the reorder from one current, controlled specification pack.
Start with the low-MOQ collection planning guide, then review reorder dye-lot control and yarn-booking decisions. Yushengda develops custom knitwear across wool, cotton, acrylic, viscose, cashmere and blends, subject to project requirements. Send the approved style, SKU demand, target arrival date and proposed reorder quantity for a project-specific feasibility review.
Primary reference: Oracle, Reorder Point Planning, for the relationship between available quantity, safety stock, forecast demand and replenishment lead time. Oracle also notes that order lead time combines processing stages. This article adapts that general inventory logic to buyer-controlled custom-sweater decisions; it does not prescribe a universal forecast, safety-stock percentage or reorder quantity. Competitor content was reviewed only for apparel terminology and coverage gaps; no ratios, cases, claims, wording or images were reused.