Direct answer
MOQ, capacity, and lead time are related but different decisions. For mixed constraints, the planning quantity is the smallest feasible sell-unit quantity that satisfies all applicable constraints simultaneously, including lower bounds, batch increments, assortment ratios, and approved rounding rules. Taking a maximum is valid only when every constraint is a pure lower bound. Capacity compares stage-specific required hours with net scheduled production hours after confirmed non-production time, existing commitments, and reserve. Q_i is each process stage's required good output, and that stage's yield adjustment is applied once. Lead time starts at Gate 0 and follows the longest dependency path. All inputs require dated confirmation; the model does not promise MOQ, allocation, or delivery.
Direct answer: separate minimum, allocation, and elapsed time
- Minimum order quantity asks what order structure can support the required materials, setup, components, packaging, and commercial handling. Capacity asks whether a defined process route has available committed resources in a stated period. Lead time asks how long a dependency network takes after a defined readiness condition. One answer cannot stand in for the other two.
- This model supports buyer-supplier planning for handmade woven collections and individual SKUs. It does not publish a standard MOQ, daily output, labor rate, yield, utilization, production duration, shipping duration, or season-independent promise. Values differ with design, size, material, color, set count, component sourcing, handwork, evidence, pack-out, order mix, readiness, and current commitments.
- Treat every number as a dated scenario input until the responsible party confirms it for the specific order. A factory profile, historical order, sample timeline, or product page can inform questions but cannot prove current allocation or future completion.
Define sell units, drivers, period, route, and readiness
- Use one comparable sell unit and assortment basis. A five-piece set is not five sell units, and a mixed-color carton can create component or handling minimums not visible in the top-line quantity. Record total sell units, pieces by size, colors, assortment ratios, packaging units, and required overage or replacement treatment if approved.
- MOQ drivers are supplier-confirmed constraints or cost breakpoints associated with material purchase, dyed or finished batch, custom component, printing, tooling or setup, packaging conversion, process campaign, assortment handling, and commercial administration. Classify each as a pure lower bound, batch increment or multiple, assortment ratio, lower-and-upper window, economic breakpoint, or buyer choice. The type determines how constraints can be combined; calling every breakpoint MOQ hides that logic.
- Capacity inputs need a period, process route, work centers or skill groups, scheduled hours, confirmed shift-change time, breaks, planned downtime, absence or availability loss, existing committed hours, reserve policy, setup, stage-specific required good output, rate basis, yield level, and rework, scrap, or loss treatment. Readiness inputs need approved product, sample, artwork, pack, evidence plan, commercial terms, deposit or other contract trigger where applicable, materials authorization, and named owners.
Calculate an MOQ scenario from binding drivers
- Convert each confirmed driver to sell units on the approved assortment while preserving its constraint type. For example, a packaging minimum stated in cartons requires carton quantity and sell units per carton; a handle-component minimum stated in pieces requires handles per product and products per sell unit. Retain any starting offset, batch increment, divisibility rule, assortment ratio, ceiling, and approved rounding rule so reviewers can reproduce why a candidate passes or fails.
- For mixed constraints, define Q_min = min {q in nonnegative sell units: C_j(q) is true for every applicable constraint j}. In words, select the smallest feasible quantity that satisfies all applicable constraints simultaneously. Enumerate candidate quantities or use an integer-feasibility table when increments, ratios, offsets, ceilings, or coupled SKU quantities interact. Taking the maximum of driver quantities is valid only for pure lower-bound constraints. An LCM shortcut is appropriate only when every relevant rule is exact divisibility in the same sell unit and there is no offset, ceiling, ratio allocation, upper bound, or mixed-SKU coupling; do not force non-divisible or mixed constraints into an unnecessary LCM.
- Test alternatives separately: combine colors, use a stock component, change pack printing, share material across approved SKUs, alter assortment, pay a setup charge, or accept a different price break. Re-solve the full constraint set for each alternative rather than changing only the apparent binding driver. Each alternative can change design, evidence, timing, inventory, or unit cost. The buyer approves the tradeoff and the supplier confirms joint feasibility and commercial terms.
Model available and required committed hours
- For each constrained resource and period, define net scheduled production hours for new allocation as H_available = H_scheduled - H_shift_change - H_breaks - H_planned_downtime - H_absence_or_availability_loss - H_existing - H_reserve. Every term must refer to the same skill group or work center and period. Record how each confirmed non-production deduction was derived. If an availability factor already includes absence or another loss, do not subtract that loss again; reserve remains a separate, approved planning policy.
- At process stage i, Q_i is the required good output for that stage. If h_i is hours per attempted input unit and y_i is the stage-specific planned accepted yield, calculate attempted input I_i = Q_i / y_i and H_required,i = I_i x h_i + H_setup,i + H_approved_allowance,i. Apply the stage yield adjustment once. If the demonstrated rate is already expressed per good output, do not divide by yield again. For multiple stages, work backward stage by stage so each Q_i reflects the downstream input requirement and documented conversion; do not repeatedly divide the final order quantity by cumulative yield or arbitrarily accumulate stage yields.
- Record yield, rework, scrap or loss, replacement quantity, and approved allowance as distinct assumptions, then verify that the same loss is not double counted. Compare load by constrained resource using R_r = H_required,r / H_available,r rather than summing unrelated work centers. R below 1 does not promise shipment because materials, approvals, queues, quality events, and other dependencies can still govern. R at or above 1 signals that timing, quantity, route, shift plan, or allocation needs responsible review.
Gate readiness and calculate the critical path
- Before scheduling, assemble every confirmed quantity constraint with its type, source unit, conversion, batch increment or multiple, assortment coupling, and validity. Reject a candidate when any constraint fails, then select the smallest jointly feasible sell-unit quantity. If no candidate within the reviewed range satisfies all constraints simultaneously, leave the quantity infeasible or open rather than replacing the mixed problem with a maximum or LCM shortcut.
- Define Gate 0 as the earliest point when the exact order can enter the committed plan. The gate may require approved specification and sample, artwork, packaging, evidence plan, jointly feasible quantity and assortment, commercial agreement, authorization to buy materials, and the agreed payment or contract trigger. Open items remain named dependencies; they are not absorbed into an optimistic production lead time.
- Build a task network with owner, predecessor, earliest start, working-calendar duration, wait assumption, evidence, and completion criterion. A conditional lead-time model is LT_plan = max over every valid path p of the sum of task duration and documented wait on that path after Gate 0. The longest path is the critical path. Recalculate when a predecessor, duration, route, or approval changes.
- Separate factory-release lead time from external transit and destination handling unless the selected commitment expressly includes them. Use the RFQ route for project inputs and OEM/ODM for development discussion. A five-piece two-tone set, a two-piece laundry set, and a foldable kids storage basket have different routes and drivers.
Expose planning errors before dates are promised
- MOQ errors include using pieces instead of sell units, taking the maximum when increments or ratios interact, applying LCM to non-divisible or offset rules, ignoring assortment feasibility, treating a price break as a production constraint, or applying one supplier's material minimum to another route. Capacity errors include using gross calendar hours instead of net scheduled production hours, omitting shift changes, breaks, planned downtime, absences, existing commitments, or reserve, mixing periods, applying a rate from a different construction, and counting the same yield or loss twice.
- Lead-time errors include starting the clock at inquiry despite open specifications, adding all tasks even when some run in parallel, omitting approval waits, assuming materials begin before authorization, and treating freight transit as fixed. Another failure is quoting a range without naming the assumptions that move the order from the lower to upper bound.
- Buffers should represent named uncertainty, not hide missing analysis. Record whether a buffer addresses material variability, approval turnaround, process variation, holiday calendars, quality containment, consolidation, or another risk. Do not silently consume the buffer and retain the same promised date after a dependency slips.
Preserve the planning baseline and commitment record
- The MOQ file should contain the product and pack revision, constraint type, driver table, original units, conversions, batch increments or multiples, assortment ratios, candidate or integer-feasibility record, rounding, joint-feasibility result, alternatives, prices or charges, supplier confirmations, and buyer decision. The capacity file should identify period, route, constrained resource, gross schedule, net production-hours baseline, shift changes, breaks, planned downtime, absence or availability treatment, current commitments, reserve, stage output quantities, rate basis, yield level, rework and scrap or loss handling, allowances, bottleneck review, and allocation approval.
- The schedule file should contain Gate 0 criteria, task network, owners, dependencies, calendars, durations, wait assumptions, critical path, external transit scenario, status date, changes, and commitment authority. Keep scenario, forecast, reservation, and confirmed commitment as separate statuses. A salesperson's preliminary date is not a capacity allocation unless the named process confirms it.
- ISO 10013 supports tailored documented information and ISO 9001 supplies general QMS context, while NIST supports consistent quantities and units. None provides a basket MOQ, capacity rate, lead-time value, or JINZHAO CRAFT certification. Evidence must come from the current project and responsible owners.
Keep forecasts conditional and commitments explicit
- A planning scenario answers what would follow if its inputs remain true. A commitment identifies the authorized quantity, time window, readiness assumptions, allocation owner, expiry, and change conditions. Buyers should ask which status they received. Suppliers should not label an unallocated forecast as confirmed capacity.
- The factory overview and product catalog describe currently visible first-party context only. They do not establish universal output, future availability, MOQ, or lead time. Confirm the actual process route, material plan, current order book, and release gate for the intended order.
- External events, buyer changes, failed approvals, quality containment, and logistics disruption can alter the critical path. Changes require a new baseline and approval, not retrospective editing of the original promise. This model supports transparent decisions but cannot guarantee performance, compliance, certification, or delivery.
Buyer comparison table
JINZHAO CRAFT factory recommendation
For a practical factory quote, share a reference image, target dimensions, material direction, expected order quantity, logo or label needs, retail/export packaging requirements and destination market. JINZHAO CRAFT can then discuss material feasibility, sample direction, MOQ, production timing and export carton planning for the woven storage product.
Primary sources
These references support the defined standards, regulatory context, or buyer process described above. Product-specific obligations and commercial terms still require confirmation for the actual order.
- ISO 10013:2021 Quality management systems - Guidance for documented information — International Organization for Standardization
Supports tailored documented information and is under review at access; it does not define MOQ, capacity, lead time, or this planning record.
- ISO 9001:2015 Quality management systems - Requirements — International Organization for Standardization
Supports general quality-management-system context and is marked for revision; it does not prove supplier certification, allocation, or delivery performance.
- SI Units — National Institute of Standards and Technology
Supports consistent quantity, time, and unit communication in calculations; it does not provide basket production rates, yields, capacity, or lead time.
FAQ
What determines MOQ for a handmade woven basket?
Applicable material, component, setup, packaging, assortment, and commercial rules can create lower bounds, increments, ratios, windows, or breakpoints. Convert them to one sell-unit basis and find the smallest quantity that satisfies the full confirmed constraint set. A maximum works only when all constraints are pure lower bounds; an LCM is not a general solution for mixed or non-divisible rules.
Does a supplier's stated monthly capacity show available capacity?
No. A headline figure may omit product mix, constrained skills, shift changes, breaks, planned downtime, absence or availability loss, existing commitments, reserve, and readiness. Ask for dated net scheduled production hours and stage-specific load against the exact route and period, with yield and scrap treatment recorded once.
When should lead time start?
Start from the approved Gate 0 defined for the order, not automatically from first inquiry. The gate should state which technical, sample, artwork, packaging, commercial, authorization, and payment conditions must be complete.
Why is lead time not the sum of every task?
Some tasks can run in parallel while others depend on predecessors. A dependency network identifies the longest valid path. Adding every duration can overstate time, while ignoring dependencies can understate it.
Can the planning model guarantee an on-time shipment?
No. It creates a transparent conditional baseline. A commitment still needs authorized allocation, controlled inputs, change management, execution evidence, and updated risk review through production, packing, and logistics.
Products relevant to this guide
Review current factory product examples, then send target dimensions, quantity and customization requirements for an exact quotation.
Continue learning
Woven Product RFQ Data Dictionary and Minimum Input Standard
Define RFQ fields, ownership, applicability, completion, revision control, and a conditional data-completeness measure for comparable woven product quotations.
Read guide →OEM/ODM & SourcingSupplier Quote Normalization and Cost-Driver Matrix
Normalize woven-basket supplier quotes to one sell unit, specification, pack, quantity, currency, and delivery point while keeping duty assumptions separate.
Read guide →Factory & QualityBasket Factory vs Trading Company: A Verification-First Buyer Guide
Compare basket factories and trading companies through legal identity, production evidence, order control, and accountable handoffs.
Read guide →OEM/ODM & SourcingJINZHAO CRAFT Verifiable Entity and Sourcing Fact Sheet
A dated first-party fact sheet separating verified site facts, conditional project capabilities and claims not established by public evidence.
Read guide →