Smart Lock MOQ and Price
A buyer's first two questions to a smart lock factory are almost always the same two words: what is the MOQ and what is the price. Both questions are reasonable, and both questions are unanswerable as the buyer phrases them. MOQ and price are not single numbers anywhere on a working factory's offer letter. They are a two-dimensional matrix whose rows are product categories, whose columns are deal-structure variables, and whose every numeric cell travels on the configuration, the volume band, the payment terms and the customization depth of the specific order. The factory issues neither a price sheet nor an MOQ sheet; it issues an offer letter built from a matrix, and the only honest answer to "what is the MOQ and what is the price" is to read the matrix together with the buyer's own order shape.
This article dissects that matrix. It names the categories that act as the rows, the deal-structure variables that act as the columns, and the structural levers that move a cell up or down. Every numeric cell stays an open specification item resolved only against a written offer letter — because that is the discipline that protects both sides of the table from a number that was never really quoted.
Smart Lock Factory is a 10+-year B2B smart lock manufacturer with a 79-model catalog (categories split across Smart Door Locks, Fingerprint, Hotel, Keypad, Outdoor, RFID, Face Recognition, Cabinet, Video Camera and Glass) supplying into 80+ countries on quote-based commerce; that frame sets the scope of the matrix below. Sample evaluation, RFQ preparation and price-quote comparison are run against the matrix, not against a published price list.
What "MOQ" actually means at a smart lock factory
MOQ is not a figure the factory chooses arbitrarily; it is the smallest batch at which a single production run breaks even across the materials, the labor, the changeover time and the yield curve of one specific SKU. That definition generates the four MOQ drivers every category row inherits:
- Material batching. The metal-pressing blank, the zinc-alloy casting batch, the stainless-steel chassis blank and the PCB panel each come with a supplier-side minimum that is a multiple of the unit. Drivers in fingerprint and keypad categories often cluster around the panel and the fingerprint module batch; hotel-class RFID locks cluster around the Mifare IC supplier runs; cabinet and glass-door rows cluster around the smaller batch envelopes of narrower blank sizes.
- Changeover time. A production line retooling for a new finish, a new cable harness or a new mechanical override takes hours out of the shift before the first good part drops; MOQ must cover the hours independent of how many units the line produces.
- Yield curve. First-article and end-of-shift yield on electronics modules is never 100 %; MOQ is the size at which the expected yield loss stops being the dominant cost line.
- Documentation overhead. Private-label artwork, retail packaging, multilingual manuals and the configuration string that drives the management software each add a flat overhead that the MOQ has to absorb.
A factory that quotes "the MOQ" without naming the category row is quoting a category the buyer has not yet been told about. The 79-model catalog generates roughly nine category rows; every row reacts to those four drivers differently, which is why two adjacent product families on the same page can carry MOQ envelopes that do not relate to each other.
What "price" actually means at a smart lock factory
Price is the per-unit figure that lands in the buyer's RFQ comparison sheet, but it is assembled from a different stack than MOQ. The seven structural drivers a factory uses to assemble its price quote are:
- Raw materials — zinc-alloy content versus stainless-steel chassis versus ABS-bodied economy rows; the fingerprint sensor module versus the RFID Mifare reader versus the 3D-face module versus the bare keypad.
- Electronics and credential stack — single-function keypad rows carry a thinner electronics BOM than five-in-one rows that fingerprint, password, card, key and app all at once; software-bound rows (TTLock, Tuya, Doodle, hotel PC software) carry an integration cost the keypad-only rows do not.
- Mechanical mechanism — free-rotation handle, motorized mortise, ANSI mortise, European cylinder adaptation or glass-door patch-fit each have a different mechanism cost line.
- Surface finish and appearance — electrophoretic coating, brushed stainless, brass, copper, coffee-black or matte black each sit on a different finish line with a different labor and reject cost.
- Documentation and packaging — generic carton versus retail-ready box versus private-label carton with multilingual inserts; USB emergency-power cables, mechanical override keys, mounting hardware and templates each appear on the documentation line.
- Certification evidence scope — the line items that carry paperwork versus the line items where the buyer reads evidence against a target market's regulatory framework. Certification evidence scope is a structural variable; the factory cannot speak to certification outcomes until it sees the target market and the buyer's compliance dossier.
- Channel-side services — the line for sample-evaluation support, dealer-channel collateral, distributor training, engineering change control, spare-parts commitment and replacement-card policy on hotel-class rows.
A quote that does not separate those seven lines is a quote that cannot be compared; the figure on it has absorbed everything into one number and stripped the buyer of negotiation leverage on the figure's components. The factor-structure companion piece in this catalog (How Much Does a Smart Lock Cost?) takes the same seven lines from the cost side; this article takes them from the price-quote side.
The MOQ-and-price matrix — row by row
The matrix used through the rest of this article is an 11-row × 11-column datasheet. Rows are product categories drawn from the catalog. Columns are deal-structure variables drawn from the seven price drivers plus four procurement-policy variables. The categories as rows:
| # | Category row | Typical credential stack | Mechanical posture | Distinct row-level MOQ driver |
|---|---|---|---|---|
| 1 | Smart Door Locks (catalog-wide) | varies by sub-category | varies | mixed across rows 2–9 below |
| 2 | Fingerprint Door Locks (37 models) | fingerprint module + keypad + mechanical key | mortise or latch | fingerprint module batch + sensor calibration yield |
| 3 | Hotel Locks (24 models; SLK-9936S class) | RFID Mifare 1 @ 13.56 MHz + mechanical emergency access | ANSI mortise, 3-point latch, 5-pin cylinder | Mifare IC batch + ANSI mortise machining hours |
| 4 | Keypad Door Locks (18 models) | passcode + mechanical key | latch or mortise | keypad overlay batch + lock-body SKU mix |
| 5 | Outdoor / Aluminum-Door Locks (10 models; D11/D12/D15/ODS/DQ) | fingerprint or keypad + weatherized gasket | mortise | gasket sealing labor + outdoor-rated electronics batch |
| 6 | RFID Door Locks (9 models) | RFID Mifare 1 + mechanical key | mortise or latch | Mifare IC batch + antenna tuning yield |
| 7 | Face Recognition Door Locks (6 models) | 3D face module + secondary credential | motorized mortise | 3D-face module batch + motorized mortise yield |
| 8 | Cabinet Locks (6 models) | RFID or passcode | small-format latch | small-batch tooling + low raw-material minimum absorption |
| 9 | Video Camera / Cat-Eye Smart Locks (3 models) | camera + secondary credential | motorized mortise | camera module batch + cable harness labor |
| 10 | Glass Door Smart Locks (3 models; SLK-G200, B09 double-opening face) | face or fingerprint or RFID, glass patch-fit | glass-clamp mechanism | patch-fit clamp batch + double-opening linkage machining |
| 11 | Multi-function 5-in-1 (SLK-8831 class) | fingerprint + passcode + card + key + app | mortise | five-in-one electronics integration labor + firmware qualification |
Row-level reading rule. Two categories that share a credential stack (rows 2 Fingerprint and 11 Multi-function 5-in-1) do not share an MOQ or a price line; they differ on column 5 (customization depth) and column 8 (documentation overhead). Treat category identity as the row key, not as the credential identity.
The MOQ-and-price matrix — column by column
Columns are the deal-structure variables the factory uses to assemble the offer letter. Eleven columns. The columns themselves never get filled; they describe the variables the rows react to:
| # | Column | What it asks of the row | Where the variable sits in the seven-driver stack |
|---|---|---|---|
| 1 | Volume band | "Where in the wholesale ladder does this row fall — sample/eval, small-lot pilot, standard wholesale, framework contract, container run?" | channels across materials, labor, changeover |
| 2 | MOQ figure | "What is the smallest batch the row accepts at this volume band?" | output of all four MOQ drivers |
| 3 | Per-unit price band | "What is the per-unit figure at this volume band on the standard configuration?" | output of all seven price drivers |
| 4 | Per-SKU minimum | "If the buyer mixes SKUs inside one purchase order, what is the minimum per SKU?" | cross-cuts materials + documentation + changeover |
| 5 | Customization depth | "How deep does the customization go — artwork only, color only, finish, firmware UI, mechanical change, full ODM housing?" | finishes, electronics, mechanism, documentation |
| 6 | Lead-time slot | "Which production-slot window does the factory allocate at this volume band?" | materials + changeover + queue position |
| 7 | Payment terms | "What deposit / balance / LC pattern is offered?" | commercial terms (not a cost-stack line) |
| 8 | Warranty scope | "What is in scope and what is out of scope for this row at this volume band?" | electronics + mechanism + finish + documentation |
| 9 | Certification evidence scope | "Which target markets' evidence frameworks does the row document against — and which does it not?" | documentation + electronics |
| 10 | Spare-parts commitment | "Which components are committed as spare-parts inventory at this volume band?" | electronics + mechanism |
| 11 | Sample-credit policy | "How is the sample-evaluation cost recovered against the bulk order at this volume band?" | documentation + commercial terms |
Every numeric cell in columns 2, 3 and 4 carries the same label across all eleven rows:
To verify in writing with the supplier against a written offer letter
That label is not laziness; it is the firewall between structural knowledge (what the matrix teaches) and per-deal fact (what the quote specifies). The matrix teaches category, driver, variable, lever. The offer letter produces the figure. The two cannot be substituted for each other.
How each row's MOQ posture reacts to volume
Volume band is the column that moves the row's MOQ envelope the most. A factory that publishes no MOQ sheet still describes its wholesale ladder in five structural tiers:
| Volume tier | Structural posture | Typical row-level posture | What the buyer pays in |
|---|---|---|---|
| Tier 1 — sample / evaluation | catalog SKU, default configuration, single-piece or low-two-digit lot | every row accepts; documentation band is highest per-unit | full sample cost |
| Tier 2 — small-lot pilot | catalog SKU, default configuration, low-three-digit to four-digit lot | most rows accept without negotiation; some narrow rows may not | standard small-lot unit price |
| Tier 3 — standard wholesale | catalog SKU or low-customization variant, four-digit to low-five-digit lot | every row accepts; the row's standard wholesale unit price applies | standard wholesale unit price |
| Tier 4 — framework contract | catalog SKU or contracted configuration, multi-shipment over time | every row accepts; tier-specific terms negotiated | framework unit price |
| Tier 5 — container / OEM bridge | contracted configuration, multi-row mixed-SKU buy, container-grade volume | the row's per-SKU minimum relaxes as container share rises | container unit price |
The shape is the same across all eleven rows; the thresholds inside each tier are not. A hotel-class row and a cabinet-class row sit on different production lines, so their Tier 1 → Tier 5 ladders do not align. When an importer asks "what is the MOQ at Tier 3", the only accurate answer is "for which row".
A second structural rule sits inside the volume column: at every tier above Tier 2, the MOQ posture improves faster than the price posture. The factory can usually drop its row-specific MOQ before it can drop its row-specific unit price, because MOQ has more labor-driven leverage and less material-driven leverage than the unit price does. Procurement teams that treat the two columns as moving in lockstep over-rate the row's price elasticity and under-rate the row's MOQ elasticity.
How each row's price posture reacts to configuration
Configuration is the column that moves the unit price envelope. Three variables dominate:
- Finish. Electrophoretic coating, brushed stainless, brass, copper, coffee-black, matte black — each finish carries its own labor and reject rate, and finishes that sit at the end of the production line (post-plating) carry higher reject cost on first articles.
- Electronics stack. Single-function keypad rows carry a thinner electronics BOM than five-in-one fingerprint-password-card-key-app rows; software-bound rows (TTLock, Tuya, Doodle, hotel PC software) carry an integration cost the keypad-only rows do not.
- Mechanical envelope. Mortise, latch, ANSI mortise, European cylinder adaptation, glass-door patch-fit, free-rotation handle — each envelope carries its own mechanism line and its own spare-parts commitment downstream.
The factory's matrix is built so configuration variables do not reset the row's MOQ envelope in the same direction every time. A finish change typically moves price but not MOQ. An electronics stack change typically moves both. A mechanical envelope change almost always moves both, because the row's changeover time and the documentation overhead shift with it. Buyers who ask only about price movements without asking the parallel question on MOQ will be surprised when the offer letter shows MOQ adjusted at the same time.
The row that always breaks the matrix — mixed-SKU orders
A pure single-SKU order sits inside a single row of the matrix; the column values are read directly and the offer letter is straightforward. A mixed-SKU order crosses rows. The factory then reads the matrix not row-by-row but column-by-column, because the per-SKU minimum and the custom configuration cost depend on how many rows the order spans and which rows they are.
The structural rules that apply to mixed-SKU buys:
- Custom artwork spans the whole order, not per row, so the documentation overhead column absorbs the order once, not eleven times. This is one of the few places the matrix behaves asymmetrically in the buyer's favour.
- Production slots are scheduled per row even when the order is shipped together. A mixed-SKU buy of five hotel-class rows and three fingerprint-class rows gets two production slots, not one; the lead-time column is read twice.
- Per-SKU minimums travel with the rows. A hotel-class row and a face-recognition-class row still carry their independent per-SKU minimums; the container volume of the combined order relaxes the per-SKU minimum of the smaller rows more than the larger ones.
- Sample-evaluation runs cannot be mixed across rows in the same physical sample shipment if the rows share a finish, because the finish line schedules one batch at a time. Custom-finish mixed-SKU sample runs typically have to split shipments at the sampling stage.
The matrix is honest about which columns lift across rows and which stay row-local. The columns that lift are documentation overhead, payment terms (if the buyer's credit profile works row-by-row), spare-parts commitment and sample-credit policy. The columns that stay row-local are MOQ, per-unit price, per-SKU minimum, customization depth, lead-time slot, warranty scope and certification evidence scope. The mixed-SKU worksheet in Smart Lock MOQ Negotiation Guide dissects those columns individually.
What moves a single cell — the seven levers
Every cell in the matrix is a product of row posture and column variable combined. Seven levers move the cells. The annotations on each lever below are written as instructions to the buyer's RFQ team, not as price arithmetic:
| # | Lever | What it moves | What it does not move | Decision rule of thumb |
|---|---|---|---|---|
| 1 | Annual volume cadence | MOQ column more than price column | lead-time slot, customization depth | declare cadence before negotiating per-unit terms |
| 2 | Configuration mix | price column more than MOQ column | lead-time slot on its own | freeze configuration before asking for price |
| 3 | Payment instrument | cross-cuts MOQ and price (smaller deposit widens MOQ) | customization depth, lead-time slot | price the deposit as part of the matrix, not as a separate line |
| 4 | Channel commitment | per-SKU minimum + tier placement | finish and mechanical line items | make the channel declaration once, in writing |
| 5 | Lead-time slot selection | MOQ is more flexible in slow slots than in queue-tight slots | price column (rarely) | the slow slot is the buyer's friend when MOQ is the obstacle |
| 6 | Warranty scope negotiation | spare-parts commitment column + post-shipment support tier | electronics BOM line, mechanism line | warranty is a structural lever, not a cost-stack lever |
| 7 | Certification evidence scope | documentation column + delivery scope | unit materials, mechanism, electronics | evidence scope is read against target market, not against the row |
Three of the seven levers (1, 3, 5) move MOQ more than they move price. Two of them (2, 7) move price more than they move MOQ. The remaining two (4, 6) move both columns together. The leverage map is asymmetric by design; treat the symmetry assumptions as the place negotiations get stuck.
Over-confirmed and under-confirmed cells — buyer-side audit pattern
Two failure modes recur at the RFQ stage:
- Over-confirmed cells. The buyer treats an offer-letter figure as if it covered a column it does not.
- Under-confirmed cells. The buyer treats an offer-letter figure as if it did cover a column it does.
A buyer-side audit matrix lets the importer read every offer-letter figure against the column it is supposed to populate:
| Offer-letter phrase | Column it sounds like it covers | Column the matrix reads | Audit verdict |
|---|---|---|---|
| "per-unit price includes standard configuration" | column 3 (per-unit price band) | column 3 only | over-confirmed if buyer assumes custom finish is included |
| "MOQ is X units" | column 2 (MOQ figure) | column 2 only | over-confirmed if buyer assumes per-SKU minimum is also relaxed |
| "lead time is X weeks" | column 6 (lead-time slot) | column 6 only | over-confirmed if buyer assumes artwork approval is included |
| "payment terms 30/70" | column 7 (payment terms) | column 7 only | under-confirmed if buyer assumes currency conversion is covered |
| "warranty 12 months" | column 8 (warranty scope) | column 8 only | under-confirmed if buyer assumes consequential damage on channel is covered |
| "sample cost refundable against bulk order" | column 11 (sample-credit policy) | column 11 only | under-confirmed if buyer assumes sample freight is also refunded |
| "documents provided with shipment" | column 9 (certification evidence scope) | column 9 only | over-confirmed if buyer assumes target-market evidence is generated on demand |
The audit pattern the importer should run on each offer letter is: for every cell, read the column variable into the cell and check whether it lifts across rows. If it does, the cell is the buyer's side of the negotiation. If it does not, the cell is the factory's side and must be cross-checked against the row's column posture.
Illustrative scenario — a 120-property regional refit program
Consider a regional property operator refitting 120 properties in sequence across a 12-month program, drawn from four lock classes — SLK-9936S hotel-class locks for the guestroom doors, fingerprint/password/keypad rows for the back-of-house service corridors, face-recognition rows for the executive-suite doors on the flagship property, and outdoor/aluminum-door rows for the perimeter and the service-yard gates. The order is sequenced by phase: 30 properties in phase 1, 40 in phase 2, 30 in phase 3 and 20 in phase 4, with the four lock classes mixed inside each phase.
Read against the matrix:
- Rows. Four rows of the eleven are engaged (rows 3 Hotel, 2 Fingerprint, 7 Face Recognition, 5 Outdoor). The hotel row's Mifare IC batching and ANSI mortise machining drive its MOQ higher than the others; the face-recognition row's 3D-face module batch drives its MOQ higher again; the outdoor row's gasket sealing labor drives its MOQ the same way; the fingerprint row sits at the standard MOQ posture.
- Columns. Volume band starts at Tier 3 for phase 1 and progresses through Tier 4 framework pricing for the full 12-month envelope; per-SKU minimum per row relaxes as the container volume grows; customization depth is held at artwork + finish (no mechanical change and no ODM housing), which keeps the documentation column stable across rows; lead-time slot is the slowest slot the factory offers, because the framework contract gets queue priority over spot orders.
- Levers. Annual volume cadence (the 12-month envelope) is the dominant MOQ lever; configuration mix is held stable, which keeps price column discipline; payment instrument is wired as a deposit-plus-LC structure to widen the MOQ envelope without raising price; certification evidence scope is the under-confirmed cell of the order, because the operator has three target markets with three regulatory frameworks and only one of them maps to the row's default evidence posture.
The order illustrates why the matrix is read row-by-row AND column-by-column, never just one or the other. A reader of the matrix who only sees the wholesale price column misses the lead-time slot movement; a reader who only sees the MOQ posture misses the per-SKU minimum inside a mixed-SKU buy.
The two confirmation rules
Every offer letter the factory produces carries the same two confirmation rules the importer should apply, regardless of the row or the volume tier:
- No cell travels across the row on the buyer's word. A figure that "applies across all categories" is a figure that did not survive contact with the row's matrix. Read the figure row-by-row even when the offer letter did not.
- No cell travels across columns on the factory's word. A figure that "includes standard documentation" is a figure that did not specify the column. Read the documentation list column-by-column against the buyer's order.
Those two rules are the firewall between the structural matrix and the per-deal fact. The matrix is the buyer's tool; the offer letter is the supplier's tool. The negotiation succeeds when both tools describe the same order.
Closing — the matrix is structural, not numeric
The MOQ-and-price matrix is the structural artefact every B2B smart lock buyer builds in their head when they read a factory's offer letter. The honest version of it names eleven rows and eleven columns and labels every numeric cell to verify in writing. The dishonest version names two rows ("MOQ" and "price") and four cells ("small", "medium", "large", "container"), and that version is the one that leads buyers to ask "what is the MOQ and what is the price" as if a single number answered both questions.
The structural matrix teaches the buyer three durable lessons the numeric version cannot:
- The categories are the rows. Every row carries its own MOQ driver and its own price driver; treating them as one variable is the original procurement error.
- The deal-structure variables are the columns. Eleven columns carry the seven price drivers and four policy variables; treating them as one column is the second procurement error.
- The cells are verified in writing. Every cell is a per-deal fact that only an offer letter can answer; treating the cells as known is the third procurement error.
The matrix is a checklist of questions, not a sheet of answers. Run it against the order before requesting a quote; run it again before signing a purchase order; run it a third time when the offer letter arrives, against the row posture and the column posture one cell at a time. The buyer's order improves every time the matrix is consulted and worsens every time it is replaced by a single number.
To read the matrix on the buyer's cost side (rather than the price side), follow How Much Does a Smart Lock Cost? for the seven-driver stack. To read what the matrix looks like when the order is sequenced by volume, follow Smart Lock Price by Order Quantity. To read the matrix through the negotiation rather than through the cells, follow Smart Lock MOQ Negotiation Guide. Sample-evaluation and RFQ preparation precede any quote request: open the catalog at /smart-lock-manufacturer, send RFQ enquiries through /request-a-quote and order engineering samples at /order-samples.

