Smart Lock Glossary: MOQ Definition for B2B Buyers
The moq definition is the smallest order a supplier says it will accept for the stated scope. In a B2B smart-lock purchase, it is a commercial floor tied to a SKU, configuration, ordering unit, and quotation basis. It can determine whether the importer has enough usable demand to place the order and whether a different quantity would qualify for a price break. It does not automatically reveal the lowest safe quantity for a door programme, and it is not the same thing as a factory test batch or the quantity needed to make one unit work.
Direct answer. Short version — moq definition is treated here as moq definition first. the decision record comes second. The evidence for moq definition is named in the sections below. A moq definition is a reference entry. It holds definitions, options and trade-offs. moq definition is the entry point for moq definition.
This article defines moq definition through moq definition. The definition of moq definition is deliberately narrow. It is non-statutory, and it applies to the market and product being discussed.
- Fix the terms — use one vocabulary for moq definition across the project
- Present the options — list the routes available for runbook control card close and what each is for
- Present the trade-off — record what you give up with each route in setting working definition
- For moq definition, moq is what each step has to answer to.
This runbook explains how to capture that commercial floor without confusing it with demand, technical constraints, packaging, or forecast uncertainty. No factory MOQ is published here. Obtain the current value from the supplier’s written quotation, record its basis, and retain the evidence used to accept or challenge it. The output is a purchase-order decision another importer can audit without relying on memory.
Runbook control card Close the loop with [requesting a quote
Use this runbook when a quotation, supplier response, or order review contains the term MOQ and the importer needs to decide whether the order can proceed. The runbook does not set the MOQ. It creates a traceable decision from the supplier’s written terms to the approved purchase order. The second take on moq definition is Smart Lock Glossary: IC Card Definition for B2B Buyers. Before the next supplier meeting, read Smart Lock Factory vs Trading Company: Which Should B2B Buyers Choose?. If the answer has to survive a supplier meeting, Smart Lock Glossary: Card Encoder Definition for B2B Buyers is the next one to read. The catalogue side of this is the smart door locks.
| Control point | Required action | Owner | Evidence retained |
|---|---|---|---|
| Trigger | Open the runbook when MOQ appears in a quotation or order review | Importer or procurement lead | Quotation and buyer request |
| Definition | Capture the smallest order the supplier will accept and its basis | Procurement lead | Supplier quotation and clarification |
| Demand | Compare the accepted quantity with the approved requirement | Operations planner | RFQ quantity schedule |
| Decision | Accept, request clarification, negotiate, or hold | Buying lead | Signed decision log |
| Release | Transfer the approved terms into the purchase order | Purchase-order owner | Purchase order and approval trail |
| Closure | Reconcile the purchase order with the quoted basis | Import controller | PO-to-quotation check |
Run the procedure again whenever the quoted floor, product configuration, order mix, or approved demand changes. An earlier decision remains valid only while its recorded assumptions still hold. The second take on moq definition is Smart Lock Glossary: UL Listing Definition for B2B Buyers.
Establish the working definition
The minimum order quantity is the smallest commercial order the supplier is prepared to accept for the scope stated in its quotation. For this programme, an MOQ is a supplier commercial floor, not a universal quantity for smart locks and not automatically a technical minimum. The supplier’s current written terms define the floor for that quotation.
At importer level, the moq definition should therefore answer four questions. What quantity will the supplier accept? Is that quantity measured per order, SKU, configuration, or other unit? Can eligible items be combined? Which conditions, if any, apply to the price break? A bare entry reading “MOQ applies” does not answer these questions.
A price break is a separate conditional point. It may be attached to a different quantity or set of aggregation conditions, so reaching the quoted floor does not automatically place the order in the most favorable commercial tier. The buyer should record the condition and its evidence separately from the MOQ itself.
Until the supplier provides written evidence, use this programme’s working definition: “The smallest order accepted by the supplier under the scope, unit, configuration, and quotation terms stated in the current quotation.” That wording is operational; it does not pretend that every supplier calculates an MOQ in the same way.
CONFIRM-WITH-LOCAL-LEGAL: Confirm that the purchase-order wording, governing law, and enforceability of the agreed quantity and price-break conditions fit the importer’s circumstances.
Keep four quantity fields separate
A quotation becomes difficult to control when MOQ, break quantity, required quantity, and forecast quantity share one column. Give each field a separate owner and definition. This prevents the buyer from treating a forecast as a commitment or a commercial floor as a technical constraint.
| Quantity field | Working meaning | Decision it supports | Evidence |
|---|---|---|---|
| MOQ | Smallest order the supplier will accept under stated terms | Whether the quotation can be accepted | Current supplier quotation |
| Order quantity break | Quantity at which the supplier applies a stated commercial condition | Which quotation tier applies | Quoted tier schedule |
| Required order quantity | Approved units needed for the importer’s actual plan | Whether the order is necessary | Authorized requirement schedule |
| Forecast quantity | Expected future demand used for planning | Whether buying above the requirement creates exposure | Dated demand forecast |
The order quantity break is not automatically the MOQ, and neither figure should be inferred from the other. If the approved requirement sits below the supplier floor, the decision is not to silently enlarge the order. The importer must identify the commercial consequence, evaluate alternatives, and approve any resulting excess.
Track quantity variance as the difference between what the importer ordered, what the supplier accepted, and what the importer can deploy. A zero variance at the commercial level can still conceal a variance in configuration, packaging unit, or usable demand. Those differences belong in the same review.
Read the quotation and resolve its unit rules
Treat the quotation as a structured commercial record, not as a paragraph to summarize. Extract the MOQ field and its surrounding conditions before comparing it with another supplier or another project phase. Copying only the quantity can hide the rule that makes it meaningful.
| Field to extract | Question answered by the field | Evidence status |
|---|---|---|
| Quoted minimum | What order will the supplier accept for this scope? | Stated in quotation or awaiting clarification |
| Ordering unit | Are items counted as units, sets, cartons, or another basis? | Must match the PO |
| Aggregation rule | Does the minimum apply to the total order or separately to each SKU? | Must be explicit |
| Configuration scope | Which finishes, readers, or other variants are covered? | Must match the product schedule |
| Break condition | What must be true for the stated tier to apply? | Must be explicit |
| Quote version | Which document and revision control the terms? | Retain exact version |
Ask whether the minimum is order-level, SKU-level, or configuration-level. Determine whether samples count toward it, whether cartons must be treated as whole ordering units, and whether mixed configurations can be aggregated. These questions are especially important where a quote says only “per model” or “per order,” because each phrase leaves a different calculation path.
The written supplier answer must identify the scope to which it applies. If a response addresses only the visible quotation but not the attached SKU list, treat the aggregation rule as unresolved. Do not rely on a sales conversation, an internal note, or an older quotation to fill the gap.
Build the RFQ quantity schedule
The RFQ quantity schedule converts an abstract MOQ into a request that can be quoted and audited. Include one row for each SKU and approved configuration. Use the same schedule to request commercial terms, compare responses, and later reconcile the purchase order.
| Schedule column | Required entry |
|---|---|
| SKU and configuration | Exact commercial identifiers for the item being requested |
| Ordering unit | The unit in which the supplier will accept the order |
| MOQ basis | Order, SKU, configuration, or supplier-defined basis awaiting clarification |
| Quoted minimum | The supplier’s current accepted quantity |
| Order quantity break | Quantity and aggregation condition for the relevant tier |
| Approved requirement | Quantity justified by the importer’s plan |
| Forecast reference | Dated source used for demand planning |
| Evidence reference | Quotation, clarification, or prior approved schedule |
A complete RFQ quantity schedule also separates requests from assumptions. Mark each field as quoted, confirmed by the supplier, buyer-approved, or unresolved. This makes a missing answer visible before quotation comparison begins. The broader documentation discipline is covered in What an RFQ should contain: terms and tables.
Use the schedule to describe what the importer needs; do not backfill it with a remembered MOQ. If the supplier changes the minimum after receiving the request, record the change and return the affected line for approval rather than overwriting the earlier evidence.
Test the order against import order planning
Import order planning asks whether an order that is commercially acceptable is also coherent for the importer’s deployment, storage, configuration, and cash plan. Compare the supplier floor with authorized demand, project phasing, warehouse capacity, and the expected mix of configurations. The comparison should reveal whether ordering more units merely to cross a commercial threshold would create a better position or unwanted exposure.
Do not reverse-engineer the requirement from the MOQ. Begin with the units the importer can use, then test the proposed order against that basis. Separate firm need from forecast need, and separate a finished lock from services, installation materials, or replacement stock maintained under a different policy. This avoids turning a supplier’s commercial threshold into an undocumented buying mandate.
The execution sequence beyond the order should also be understood before approval. What happens between order and arrival: terms and tables explains the handovers and records that sit between purchase order and use. MOQ review should capture any dependency that affects configuration, documentation, packing, or receipt reconciliation.
This procedure does not determine customs classification, duty treatment, or landed-cost treatment. Those conclusions require the actual product facts and destination-market rules.
CONFIRM-WITH-LOCAL-CUSTOMS-BROKER: Verify how the importer’s actual product configuration and shipment will be classified and treated in the destination market.
Separate a commercial floor from a technical constraint
A technical constraint concerns whether a defined unit or configuration can be produced or supplied within its stated conditions. A commercial floor concerns what the supplier will accept as an order. The two may coincide, but one does not prove the other.
| Possible constraint | Question for the supplier | Evidence needed |
|---|---|---|
| Packaging unit | Must the order follow a defined carton or set basis? | Packaging schedule |
| Configuration setup | Does the quoted scope include separate preparation for each variant? | Configuration-specific quotation or clarification |
| Sample approval | Does production remain tied to an approved reference? | Approved sample record |
| Product specification | Does the minimum depend on a dated SKU page or product brief? | Dated product evidence |
| Component or process condition | Is there a supplier-imposed technical boundary behind the commercial floor? | Written technical explanation |
Ask the supplier to label each restriction as commercial, technical, or both. If it is technical, request the product-specific evidence rather than accepting an unexplained quantity. For any SKU-specific configuration boundary, confirm on the dated product page for the specific SKU.
The distinction matters after approval as well. A first article or sample identifies the production reference, while the MOQ identifies an order condition. How a sample becomes a production standard: procurement version explains why those records should not be collapsed into one another.
Match the route to the order stage
Samples, pilot orders, and production orders have different purposes. Each may have a different commercial treatment, but none should be assumed to have the same floor without written terms. Record the route before applying the MOQ rule.
| Order stage | Primary purpose | MOQ treatment | Required next evidence |
|---|---|---|---|
| Sample | Approve or investigate a defined reference | State whether samples are counted or exempt | Sample approval record |
| Pilot order | Test a limited production and deployment route | Quote the accepted quantity and aggregation rule | Pilot acceptance and issue record |
| Production order | Supply the approved requirement | Apply the quoted floor to the exact SKU and configuration schedule | Purchase order and approval trail |
A pilot order may be commercially separate from the production MOQ, but that separation must appear in the quotation or supplier confirmation. Do not let a limited pilot become an implied promise that later production can use the same quantity treatment. How a pilot order reduces programme risk: procurement version gives the pilot route its own decision gates.
Likewise, a sample request does not prove that the supplier’s production floor is waived, and crossing the production MOQ does not prove that the pilot has served its purpose. Keep the commercial and technical approvals attached to the stage they actually cover.
Negotiate the floor without changing the requirement
MOQ negotiation should change an unsuitable commercial condition through an agreed commercial solution, not conceal a forecasting error. Start with the requirement and the supplier’s written basis. Then test whether consolidation, staging, packaging, or a clearly scoped exception can reconcile them.
Practical negotiation options include the following:
- Consolidate genuinely compatible SKUs or configurations under one written aggregation rule.
- Phase the purchase when the programme permits staged deployment.
- Align the ordering unit with the supplier’s documented packaging basis.
- Separate samples, pilot units, and production units when their commercial treatment differs.
- Request a quotation for an approved order mix rather than an arbitrary total.
- Record any supplier exception in writing with a defined scope and expiry or review point.
Each option has a consequence. Consolidation may reduce operational complexity but increase unused configuration. Phasing may protect demand alignment but create separate handling events. Changing the ordering unit can clarify the contract but does not change the need. An exception may solve the immediate decision while leaving the next order exposed if its scope is vague.
Present options with the evidence attached. “We need this quantity” is only one input; the supplier also needs the SKU scope, configuration list, ordering unit, and desired aggregation basis. Do not accept a revised MOQ without checking whether the price-break condition, packaging rule, and configuration scope changed at the same time.
Make the commercial decision in one table
The decision table should sit beside the RFQ quantity schedule, not replace it. It converts the available evidence into an explicit accept, clarify, negotiate, or hold decision.
| Decision field | Record before approval | Accept when | Hold when |
|---|---|---|---|
| Supplier source | Current quotation and written clarification | Both are identified and retrievable | Only an informal statement exists |
| MOQ basis | Order, SKU, configuration, or other stated basis | The basis is unambiguous for the requested scope | The basis remains open to interpretation |
| Ordering unit | The unit used to state the minimum | PO and schedule use the same unit | Units differ between documents |
| Aggregation rule | Items that may be combined | The rule is explicit and applies to the requested mix | Combination is only presumed |
| Required quantity | Approved importer requirement | It is tied to an authorized plan | The order quantity was created only to meet the floor |
| Order quantity break | Quantity and qualifying condition | The condition is documented and met by the proposed order | The tier depends on an unconfirmed assumption |
| Configuration scope | Included SKUs and variants | Each included item is authorized | Scope changes between schedule and PO |
| Forecast exposure | Difference between order and usable need | The decision owner accepts the exposure | The excess is unexplained |
| Decision owner | Named buying or procurement authority | Approval and evidence are recorded | Responsibility is absent |
| PO alignment | Purchase order against approved schedule | Terms match without silent edits | The PO changes the commercial basis |
Do not average several supplier answers to create a working MOQ. If one quote has a different unit or aggregation rule, compare the records first. If the evidence remains incomplete, the correct operational result is clarification or a hold, not an invented assumption.
Control configuration and price-break conditions
Quantity alone does not identify a smart-lock order. The SKU, finish, reader arrangement, power basis, dimensional configuration, labeling, and other commercial identifiers may determine whether items can share a common floor or tier. Record the approved configuration before asking the supplier to aggregate quantities.
Keep the configuration scope synchronized across the RFQ, supplier quotation, decision table, and purchase order. A quantity schedule that groups several variants under one label must still show which specific variants the quotation covers. If the supplier treats configuration boundaries differently, hold the affected line until the written rule is known.
A price break also has conditions beyond quantity. Its validity may depend on the eligible SKU mix, aggregation rule, ordering unit, quote version, and other stated commercial terms. Compare the complete condition set rather than extracting the quantity beside it. Do not infer that the break quantity creates a second MOQ; each field controls a different decision.
| Price-break condition | Evidence to demand | Importer check |
|---|---|---|
| Eligible quantity | Quoted tier schedule | The proposed order can satisfy it as defined |
| Eligible items | Supplier statement of covered SKUs | Every included SKU qualifies |
| Configuration treatment | Written aggregation rule | Variants are not combined without permission |
| Ordering unit | Quotation and packaging basis | Tier calculation uses the same unit |
| Commercial validity | Quote version and stated validity | The approval rests on the current document |
No price or price-break value is reproduced in this glossary. The point is to preserve the rule that makes a quoted commercial term usable in a decision.
Handle exceptions and changes through one route
Exceptions should follow the same route as normal approvals. Record what changed, which decision it affects, what evidence supports the new position, and who accepts the consequence. This prevents a conversation or revised attachment from becoming an untracked change.
flowchart TD
A["Open the commercial decision"] --> B{"Quoted basis is complete"}
B -->|No| C["Request written clarification"]
B -->|Yes| D{"Order matches approved need"}
C --> B
D -->|No| E["Negotiate or request approval"]
D -->|Yes| F{"Configuration and tier are confirmed"}
E --> F
F -->|No| C
F -->|Yes| G["Release the purchase order"]
G --> H{"Terms change before receipt"}
H -->|Yes| I["Hold and reopen the decision"]
H -->|No| J["Close with reconciled evidence"]
Use this route when the required quantity is below the quoted floor, the supplier changes the floor, the configuration mix changes, or the approved demand is revised. It also applies when the price-break condition cannot be demonstrated or a purchase order differs from the approved schedule. The output is either a revised decision with evidence or a documented hold.
Put the decision into change control
After approval, preserve the exact quotation version, quantity schedule, supplier clarification, decision record, and purchase-order comparison. Give each record a date, owner, and clear relationship to the same order scope. This makes it possible to identify what was known when the decision was made.
A change can enter through many routes: a revised quotation, a configuration adjustment, a forecast update, a supplier notice, or an internal change to the deployment plan. None should be applied only through a message. Determine which approved field is affected, whether the MOQ basis or break condition also changes, and whether the original decision remains valid.
If the change affects quantity, unit, aggregation, configuration, or commercial terms, pause release of an unreconciled purchase order and reopen the relevant check. If it affects only an administrative record, document that assessment. The important control is not the size of the change; it is whether the evidence and approval still align.
Register risks that create false confidence
A complete-looking quotation can still carry unresolved commercial risk. Register the risk where it can be detected and assign the control before approval.
| Risk | Early warning | Control | Owner |
|---|---|---|---|
| Ambiguous ordering unit | Quote and schedule use different units | Reconcile the unit before comparison | Procurement lead |
| Minimum applied per configuration | Quote references a model family rather than an approved mix | Obtain the configuration-specific rule | Buyer |
| Unapproved aggregation | Several SKUs are grouped under a generic heading | Require the eligible-item list | Procurement lead |
| Forecast used as requirement | Order quantity is defended only by expected demand | Separate approved need from forecast | Operations planner |
| Configuration drift | PO uses abbreviated or altered identifiers | Reconcile SKU and configuration fields | Product owner |
| Stale commercial evidence | Approval relies on an older attachment | Confirm the current quote version | Procurement lead |
| Hidden packaging constraint | Carton or set language appears only in fine print | Align the ordering basis | Import controller |
| Untracked verbal change | Supplier or buyer summary differs from the record | Keep written confirmation with the decision | Decision owner |
Do not transfer a risk to the next team merely because the purchase order has been issued. The risk remains open until the receiving, configuration, and quantity records reconcile with the approved decision.
Convert the decision to a purchase order and confirm
The purchase order should carry the accepted commercial basis, not merely repeat the quantity. Include the approved SKU and configuration schedule, ordering unit, quoted minimum, aggregation rule, order quantity break, evidence references, and authorized approvals. State explicitly that the MOQ is a commercial condition for the scope shown on the order.
Before release, ask the supplier to confirm the questions below in writing. Their answers should be retained with the same revision control as the quotation.
| Confirmation question | Why the importer needs it |
|---|---|
| What is the smallest order accepted for this scope? | Establishes the actual floor |
| Is the minimum applied to the order, SKU, or configuration? | Determines aggregation |
| In which ordering unit is it expressed? | Prevents quantity conversion error |
| Are samples included in the quoted minimum? | Separates approval samples from production |
| Which stated items may be combined? | Identifies eligible aggregation |
| Which commercial tier applies to the proposed order? | Confirms the break condition |
| Which quotation version controls the terms? | Anchors the decision |
| Does any configuration or document requirement alter the floor? | Reveals technical or scope boundaries |
A concise supplier response is enough, provided it is unambiguous and attached to the relevant quotation. Save the response rather than copying it into an untracked internal message. If the supplier cannot answer, preserve that fact in the decision log and obtain an approved path forward.
Preserve evidence, hand off, and close the runbook
The evidence pack should let a later reviewer reconstruct the decision without interviewing the people who made it. Keep the current quotation, written clarifications, quantity schedule, decision table, purchase order, and any approved exception together. Record changes as revisions rather than replacing earlier evidence.
The build-up behind that decision is in what smart lock should a factory buy. That is the same question moq definition has to answer here.
| Record | Minimum content | Handoff check |
|---|---|---|
| Quotation | Supplier, scope, commercial terms, and version | Matches the approved scope |
| Supplier clarification | Questions asked and written answers | Attached to the correct revision |
| Quantity schedule | SKUs, configurations, units, requirement, and forecast | No blank commercial fields |
| Decision log | Option chosen, evidence, owner, and consequence | Shows why the order can proceed |
| Purchase order | Approved quantities and configurations | Reconciles to the schedule |
| Receipt reconciliation | Ordered, accepted, and received scope | Explains any variance |
The same evidence discipline supports broader supplier checks. How a supplier is actually verified: procurement version is useful background, but the MOQ decision still needs its own order-level proof.
Hand off in three checkpoints. Before quotation, confirm the requirement, forecast, SKU list, and configuration scope. Before purchase-order release, confirm the quoted floor, unit, aggregation rule, break condition, evidence, and approval. Before closure, reconcile the ordered scope with the accepted and received scope. Any mismatch returns to the decision table rather than being corrected informally.
It is worth pairing this with how many smart locks should i order for a pilot project. That is the same question moq definition has to answer here.The recurring questions have direct answers. MOQ is a commercial floor, not automatically a technical minimum. One figure does not cover several SKUs unless the supplier says it does. A price-break quantity is not automatically another MOQ. Samples count only when the written terms say they do. Forecast demand does not replace an approved requirement. Crossing the quoted floor does not resolve configuration, documentation, or packaging issues.
To complete this runbook, prepare one quantity-schedule row for every SKU and approved configuration, obtain the supplier’s current written basis, compare that basis with import order planning, and document the chosen route. Submit the completed schedule with the request for quotation. When the response arrives, use the decision table to accept, clarify, negotiate, or hold—then carry the same terms unchanged into the purchase order and retain the evidence for the next handover.
Put the answer on paper and request a quote against that document.

