Smart lock lead time negotiation is the per-order, per-SKU discipline of separating the fourteen calendar variables that actually drive delivery dates —

Đăng lúc: Th04 14, 2026

Smart Lock Lead Time Negotiation

Smart Lock Lead Time Negotiation

Smart lock lead time negotiation is the per-order, per-SKU discipline of separating the fourteen calendar variables that actually drive delivery dates — model mix, order size, customization depth, firmware lock-state, holiday blackout, sample-to-bulk gap, inspection windows, payment milestones, Incoterms choice, port congestion, custom-software release window, packaging line time, peak-season pre-build slot, and after-sales handoff — into named clauses that can be priced, accelerated, or de-risked one at a time, with the only quoted number for any specific deal coming from the factory on the dated product page for the SKU and order under consideration. A B2B order for hotel locks, residential smart locks, or commercial-grade readers does not have one lead time. It has at least fourteen interlocking ones, and the conversation that pins each one down is the conversation that decides whether the project opens on schedule or slips a season. The transcript that follows is one of those conversations. A procurement lead and a factory sales engineer sit at a table with a project schedule, an order plan, a list of customization asks, and a deadline the buyer's client has already promised. The dialogue is annotated in the margin because the annotations are half the lesson: every number that "looks obvious" turns out to be a per-model, per-order, per-season fact the buyer cannot assume.

For the upstream sourcing flow this negotiation sits inside, see How to Source Smart Locks From China. For the quantity-side companion — the conversation about minimum order quantities that the production slot itself depends on — see Smart Lock MOQ Negotiation Guide. For the upstream gate that the lead-time clock should not start until — sample approval — see Smart Lock Sample Order Process. What follows is the delivery conversation, clause by clause, with the supplier-side margin notes calling out where the catalogue answer ends and the per-order confirmation begins.

Setting the table — the fourteen-variable rule

Procurement lead (PL): I'm buying for a 220-room renovation. The project opens in Q3, my client has locked the soft-opening date, and my installer needs product on the dock roughly eight weeks before opening to clear unpacking, commissioning, audit, and walk-through. I've sent RFQs to three factories. Two came back with a single number — "lead time is X weeks." The third came back with a list of fifteen open questions about my order before they'd quote a number. The third one is the one I want to sit down with, because the other two were guessing. What are those fifteen open questions?

Factory sales engineer (SE): There are fourteen, not fifteen, but the instinct is right. A factory that quotes one lead-time number without knowing your model mix, your customization depth, your sample status, your port, your Incoterm, your payment term, your inspection posture, and your peak-season window is guessing. A factory that asks the questions first is going to quote a number they can actually keep. The fourteen variables fall into four families — production-time variables, queue-time variables, shipping-time variables, and post-arrival variables. Each family has a different lever, each lever has a different cost, and each cost is per-order. None of them can be lifted off a brochure.

Annotation — the fourteen-variable rule. Production / queue / shipping / post-arrival. Four families, fourteen named variables. The smallest set that lets the procurement lead write a delivery clause that survives the buyer's client's project manager, the factory's production scheduler, the freight forwarder's port rotation, and the installer's commissioning window. Any catalogue line that does not name a date for one of these fourteen is a catalogue that does not own that date. Check the model’s published specification for the model and order under consideration.

The production-time variables, one through six

1 — Model mix and per-model production line

PL: Variable one. Model mix. I have six SKUs in this order — three hotel-class mortise locks, one narrow-edge aluminum-frame for the stair doors, one cabinet-class for the minibar, and one multi-function residential for the manager's apartment. How does that change the clock?

SE: A lot. Each model has its own production line, its own jigs, its own PCBA test fixture, and its own firmware build pipeline. A factory running six SKUs in parallel is running six queues. The line that finishes first sets the optimistic date. The line that finishes last sets the realistic date. The order ships when the last SKU clears its final test, not when the first SKU does. If your order is six SKUs, the lead time is the maximum of the six, not the average.

PL: Per SKU, where do I find the per-line cycle?

SE: On the dated product page for each model. The catalog may list "production time per SKU" as a generic line; the actual cycle is per-SKU confirmation.

Annotation — lead time is the maximum of the SKUs, not the average. Multi-SKU orders should hide behind the slowest line, not behind the headline number. Confirm the per-SKU cycle on the product page.

2 — Order size and per-batch cycle count

PL: Variable two. Order size. The hotel-class order is the largest — that drives the clock. The cabinet-class order is small. The narrow-edge is mid-volume. Does order size change the cycle count, or just the queue length?

SE: Both. Larger batches often run on a single line without re-tooling, so the per-unit cycle can drop. Very small batches — under a threshold the factory will name per order — can require a full re-tool anyway, which resets the cycle. The cabinet-class order is the one I'd watch: it might be small enough that the line sets up for it, runs it, and tears down for the next SKU, and the tear-down eats more hours than the run. Per-batch cycle count is per-order confirmation.

Annotation — per-batch cycle count is per-order. Don't assume linearity. Check the model’s published specification.

3 — Customization depth (logo, finish, packaging, firmware, mechanical)

PL: Variable three. Customization. I want my logo on the inside escutcheon, my retail packaging on the outside carton, a custom firmware build with my brand in the mobile APP boot screen, the SLK-9936S-class mortise in a non-stock finish to match the corridor pulls, and a custom mechanical-key override because my client is a hotel chain that already has a master-key system.

SE: Five customization lines. Each adds to the clock in a different place. Logo on the inside escutcheon adds laser-set-up time and laser-cycle time on the inside line — usually hours, not days, once approved. Custom packaging adds a packaging-line changeover, plus a printed-box proofing step that you have to sign off before the line runs — days. Custom firmware adds the longest tail: the firmware team has to fork the codebase, build your branded APP variant, run the certification tests your distribution market requires (confirm which tests your market requires with counsel and your local authority — not the factory), and lock the build. The custom finish on the mortise matters because non-stock finishes often sit on a different plating line and a different curing window. The custom mechanical-key override is the most variable — it depends on whether the factory uses a standard cylinder platform that can accept your key section or has to commission a new cylinder tooling. None of these are zero-time. Confirm the per-customization cost and time on the dated product page.

PL: Which one bites hardest?

SE: Custom firmware, almost always, because the lock-state of the firmware has to be declared before production starts. If you change your mind about the APP branding mid-production, the line stops. Per-order confirmation, per customization line.

Annotation — customization depth is per-line and per-declaration moment. Five customization lines, five different clocks. The lock-state of each has to be declared before the line starts. Check the model’s published specification.

4 — Firmware lock-state and the no-mid-run-change rule

PL: Variable four. Firmware lock-state. Tell me what that means in calendar terms.

SE: The firmware for your build has to be frozen — locked — at a specific point in the cycle. Once locked, no further changes are accepted, because every locked firmware unit has to ship with a matching firmware version on the management software and a matching user manual. If you change the firmware mid-build, the locked batch has to be re-flashed or scrapped. Most factories declare the firmware lock window in the per-order production plan. Per-order confirmation.

PL: What's the cost of changing it after lock?

SE: The cost is on the buyer side — re-flash or scrap. The factory's cost is the schedule slippage on the production line. Both are reasons to commit to the firmware build early. Confirm the firmware lock window on the dated product page.

Annotation — firmware lock is a one-way door. Declare once, ship as locked. Per-order confirmation on the dated product page.

5 — Component supply chain and the sub-tier parts list

PL: Variable five. Components. The smart lock factory doesn't make everything. What does the factory not make, and what does that do to the clock?

SE: A smart lock is an assembly of sub-tier parts — RFID readers, fingerprint modules, Bluetooth/Wi-Fi modules, motors, batteries, PCBs, mechanical latches, cylinders, finishes, packaging. The factory assembles them. The sub-tier suppliers each have their own cycle. If a sub-tier part is on a long cycle or in short supply, the factory's cycle inherits that sub-tier's cycle. The smart lock factory's lead time is the longest sub-tier lead time plus the factory's own cycle. Per-order confirmation — the factory should be willing to walk you through the sub-tier bottleneck for the SKU under consideration.

PL: What if a sub-tier part is replaced during my order?

SE: That's a substitution question, and it's a contract question, not a calendar question. Confirm the substitution rule on the dated product page.

Annotation — the assembly line inherits the sub-tier cycle. Lead time is longest sub-tier plus factory cycle. Per-order confirmation.

6 — Quality control and inspection windows

PL: Variable six. Quality control. I want pre-shipment inspection. How does that change the clock?

SE: Pre-shipment inspection (PSI) sits between the end of production and the start of shipping. It is not free time. PSI windows are typically a few days, scheduled at a point in the cycle where enough of the lot is finished to be representative. The PSI window has to be booked in advance; it is a queue, not an on-call service. Per-order confirmation. For the inspection framework upstream of PSI, see the smart-lock quality inspection cluster for the umbrella five-pillar frame.

PL: What if I also want during-production inspection (DPI)?

SE: DPI is an additional booking at a defined point in the production run — usually around the 30%–60% completion mark. Each booking adds a window to the calendar. Per-order confirmation.

Annotation — inspection windows are calendar events, not free time. PSI, DPI, container-loading inspection, and production inspection each book a window. Per-order confirmation.

The queue-time variables, seven through nine

7 — Production slot and peak-season pre-build

PL: Variable seven. Production slot. Why does the factory ask me for my target ship date before quoting a lead time?

SE: Because the production slot is the queue. A factory runs on a queue. Your order enters the queue, waits behind the orders in front of it, runs when its slot opens, and exits. If your target ship date is during the factory's peak season — late Q3 and Q4 are typical for B2B locks because buyers want them on the dock before year-end project openings — your slot is further back in the queue. If your target ship date is off-peak — early Q1, for example — your slot is shorter. Lead time is queue position plus run time, not just run time. Per-order confirmation. The peak-season uplift is a calendar fact the factory knows and the buyer should ask about.

PL: Can I pay to move up the queue?

SE: That's the rush-order conversation — variable eight. Confirm the rush-order posture on the dated product page.

Annotation — queue position plus run time is the calendar. Off-peak vs peak changes the queue. Per-order confirmation.

8 — Rush-order posture and the cost-of-acceleration ladder

PL: Variable eight. Rush order. If my client's project date slips and I need to compress the cycle, what are my options?

SE: Three. First, partial-shift acceleration — running the line at higher utilization for your batch, with an uplift on per-unit cost. Second, line re-prioritization — moving your batch ahead of a later order in the queue, which is possible only if the factory's pipeline has slack at the moment of your request. Third, air-freight substitution for part of the order (a small first-batch rush shipped by air while the bulk ships by sea) — see variable ten. None of these are free, and the cost varies per order, per SKU, and per season. Confirm the rush-order ladder on the dated product page.

PL: What's the cheapest acceleration lever?

SE: Usually partial-shift acceleration on the slowest SKU in your mix, not on the whole order. Cheaper than air-freight, faster than re-prioritization. Per-order confirmation.

Annotation — rush-order is a ladder, not a switch. Three levers, three costs. Check the model’s published specification.

9 — Sample-to-bulk gap and the sample-approval gate

PL: Variable nine. Sample-to-bulk gap. The bulk clock starts when?

SE: When the sample is approved and the sample-approval document is signed. Until that gate is closed, the bulk clock has not started. This is why the sample-order process sits upstream — sample approval is the gate that opens the bulk queue position. Per-order confirmation.

Annotation — the sample-approval gate opens the bulk clock. Until signed, no calendar. Per-order confirmation.

The shipping-time variables, ten through twelve

10 — Shipping terms and the Incoterms choice

PL: Variable ten. Shipping terms. FOB, EXW, CIF, DDP — how does the Incoterms choice change the clock?

SE: A lot, and not in the way most buyers think. EXW means you own the calendar from the factory gate to your dock — pickup, export clearance, freight, customs, last-mile. FOB shifts the freight and the export-clearance clock to the freight forwarder, with the buyer taking ownership at the port of loading. CIF adds the freight and insurance to the supplier side, with the buyer taking ownership at the port of discharge. DDP adds customs clearance and last-mile delivery to the supplier side. The clock you negotiate is the clock up to the term you've chosen — anything beyond is on the side that owns the leg. Per-order confirmation. Confirm the Incoterms clause in the PO.

PL: Which Incoterm gives me the most calendar control?

SE: None of them give you calendar control — they give you calendar ownership. The clock is the same physical clock; the question is who owns each leg of it. The shortest buyer's calendar is the Incoterm that shifts the longest leg to the supplier — DDP, in most cases — but it also shifts the most risk and the most cost. Per-order confirmation.

Annotation — Incoterms is calendar ownership, not calendar shortening. Each term shifts a leg. Per-order confirmation on the dated product page.

11 — Freight mode (sea / air / courier / multimodal)

PL: Variable eleven. Freight mode. Sea vs air vs courier.

SE: Sea is the cheapest and slowest. Air is the most expensive and fastest. Courier sits between for small parcels. Multimodal (sea + last-mile truck, sea + air for a partial rush) is the practical lever for compressed schedules. The factory can advise per order, but the buyer usually controls the freight mode choice. Per-order confirmation.

PL: How does peak-season freight congestion affect this?

SE: Sea freight has its own peak-season — Chinese New Year, late-summer back-to-school, pre-Christmas — and rates and transit times both rise. Air freight has weather and capacity cycles. Per-order confirmation.

Annotation — freight mode is a buyer-side lever that interacts with peak-season congestion. Confirm the freight calendar on the dated product page.

12 — Port rotation, customs clearance, and last-mile

PL: Variable twelve. Port rotation. The factory ships out of which ports, and how does that change my calendar?

SE: The factory's shipping ports depend on the order's destination region and on the factory's logistics setup. Closest-port matters: a sea shipment from the closest Chinese port to the buyer's destination port reduces transit time and customs friction. A misrouted port adds days. Confirm the port rotation on the dated product page and with the freight forwarder.

PL: Customs clearance?

SE: On the buyer side under FOB, on the supplier side under DDP. The clock segment between arrival at port and clearance is on whoever owns customs. Per-order confirmation.

Annotation — port rotation is a calendar fact. Closest-port saves days. Per-order confirmation.

The post-arrival variables, thirteen through fourteen

13 — Receiving, unpacking, and the installer's commissioning window

PL: Variable thirteen. Receiving. The clock I care about is on my dock, not on a ship. What's the realistic unpacking-to-installer-handover window?

SE: That's on the buyer side. Unpacking, inventory check, lot segregation, and the installer's commissioning window are not in the factory's calendar. The factory can advise a recommended unpacking protocol (per the packaging inspection framework), but the buyer owns the post-arrival clock. Per-order confirmation.

Annotation — post-arrival clock is buyer-owned. Unpacking, inventory, commissioning. Per-order confirmation on the dated product page.

14 — After-sales handoff and the spare-parts / firmware-update window

PL: Variable fourteen. After-sales. The installer's commissioning window ends and the operator's after-sales window begins. What's in scope?

SE: After-sales is its own conversation — warranty handling, replacement parts, firmware update pathway, lock-management-software support. Per-order confirmation. The lead-time implication is that spare-parts orders and replacement-unit orders have their own queue and their own cycle, and that cycle is not the same as the original order's cycle. Confirm the spare-parts cycle on the dated product page.

Annotation — after-sales is a separate cycle. Spare-parts and replacement-unit queues are not the same as the original-order queue. Per-order confirmation.

The factory-side matrix — what the supplier actually controls

Variable familyVariableFactory controlBuyer-side leverCost lever
Production1. Model mixYes — line schedulingMix consolidationLower line count
Production2. Order sizePartial — per-batch cyclePer-SKU split ordersSmaller batches
Production3. Customization depthPartial — per-line changeoverStandard SKU when possibleUse catalog defaults
Production4. Firmware lock-stateYes — lock windowEarly commitmentAvoid re-flash
Production5. Sub-tier supply chainPartial — sub-tier cyclesMulti-source qualificationSub-tier substitution
Production6. Inspection windowsPartial — queueSingle combined inspectionFewer bookings
Queue7. Production slotYes — slot schedulingOff-peak targetAvoid peak season
Queue8. Rush-order postureYes — acceleration ladderPartial-shift on slowest SKUCheapest lever
Queue9. Sample-to-bulk gapPartial — sample gateEarly sample approvalSign-off speed
Shipping10. IncotermsPartial — clause choiceBuyer vs supplier legCaliper last-mile
Shipping11. Freight modeNo — buyer-sideMode choice per legAir vs sea mix
Shipping12. Port rotationPartial — port choiceClosest-port ruleReduce transit
Post-arrival13. ReceivingNo — buyer-sideInstaller schedulingInternal caliper
Post-arrival14. After-salesPartial — cycleSpare-parts pre-orderSeparate queue

Annotation on the matrix — every cell in this matrix is per-order confirmation. None of these are quoted as fixed in this article. Every entry routes to the dated product page for the SKU and order under consideration.

The buyer-side checklist — fourteen items for the negotiation call

Use this checklist on the call. Each row is a yes/no you can verify in the meeting, and a follow-up you can confirm in writing on the dated product page.

#Item to verifyYes / NoFollow-up to confirm
1Per-SKU production cycle is named for every model in the mixrequest by namePer-SKU cycle on the product page
2Per-batch cycle count is named for the order size under considerationrequest by sizePer-batch cycle on the product page
3Customization lines are listed one-by-one with per-line time impactrequest per linePer-line clock on the product page
4Firmware lock window is declared in the per-order production planrequest in planLock window in the PO
5Sub-tier bottleneck for the SKU is namedrequest by SKUBottleneck on the product page
6PSI / DPI / CLI windows are bookablerequest by windowInspection calendar in the PO
7Production slot position for the target ship date is namedrequest by dateQueue position on the product page
8Rush-order ladder cost for partial-shift acceleration is namedrequest by leverAcceleration cost on the product page
9Sample-approval gate is defined and the gate-closing document is namedrequest by documentGate in the PO
10Incoterms leg ownership is named for every segmentrequest per legIncoterm clause in the PO
11Freight mode recommendation is named per legrequest per legFreight mode in the PO
12Closest-port recommendation is named for the buyer's destinationrequest by destinationPort on the product page
13Receiving protocol and installer commissioning window are buyer-ownedacknowledgeBuyer internal schedule
14Spare-parts / replacement-unit cycle is separate from the original orderacknowledgeSpare-parts cycle on the product page

Annotation on the checklist — the fourteen items are the negotiation-call checklist. Each item closes a clause in the PO. The PO is where the calendar lives, not the verbal agreement.

The seven clause-handling rules

When the negotiation lands on a clause, follow these seven rules. They are the difference between a calendar that holds and a calendar that drifts.

Rule 1 — One number per clause, not per order. A delivery clause that names a single date for a six-SKU order will slip on the slowest SKU. Per-SKU dates are the only dates that hold. Confirm each per-SKU date on the product page.

Rule 2 — Calendar ownership follows the Incoterm. Whoever owns the leg owns the calendar for that leg. Don't accept a calendar for a leg the supplier doesn't own.

Rule 3 — Acceleration cost is per lever, not per order. Don't accept a "rush order uplift" without naming which lever (partial-shift, line re-prioritization, air-freight substitution) and which SKU. Confirm the per-lever, per-SKU cost on the product page.

Rule 4 — Inspection windows are calendar events, not free time. Each inspection (PSI, DPI, container-loading inspection, production inspection) books a window. Don't accept a delivery date that doesn't include the inspection calendar.

Rule 5 — The firmware lock window is a one-way door. Declare once. Late changes cost the buyer re-flash or scrap, and the factory a production-line stop. Confirm the lock window in the per-order production plan.

Rule 6 — Customization depth is per-line, per-declaration moment. Each customization line has its own lock-state. Don't accept a blanket "customization time" — name the per-line declaration moment for each line.

Rule 7 — The post-arrival clock is buyer-owned. Don't accept a delivery clause that includes unpacking, inventory, or commissioning time. Those are on the buyer's calendar.

Annotation on the seven rules — the rules are the negotiation discipline. Each rule is what the buyer should say on the call when the supplier proposes a single number. Confirm each per-order fact on the dated product page.

The negotiation transcript — second pass, with the clauses attached

PL: Let's run the order again, but this time with clauses. I'll ask in the order of the fourteen variables.

SE: Good. I'll answer per variable, with the clause I'd put in the PO.

PL: Variable one — per-SKU cycle. The order has six SKUs. What does the PO say?

SE: The PO says "production cycle per SKU per order: check the model’s published specification." For the six SKUs in this order, that's six dates, one per SKU. The PO does not name a single date.

PL: Variable two — per-batch cycle count. For the hotel-class SKU, the largest volume. What does the PO say?

SE: "Per-batch cycle count for the hotel-class SKU at the order quantity under consideration: check the model’s published specification."

PL: Variable three — customization depth. Five customization lines. What does the PO say?

SE: The PO names each customization line on a per-line basis — logo on the inside escutcheon, retail packaging on the outside carton, custom firmware build, non-stock finish on the mortise, custom mechanical-key override — and for each line, the clock impact is "check the model’s published specification."

PL: Variable four — firmware lock-state. What's the clause?

SE: "Firmware lock window for the order is declared in the per-order production plan. Changes after lock window: buyer-side re-flash or scrap cost."

PL: Variable five — sub-tier bottleneck. What's the clause?

SE: "Sub-tier bottleneck for the SKU under consideration: check the model’s published specification. Substitution rule: per-substitution rule in the PO."

PL: Variable six — inspection windows. What's the clause?

SE: "PSI / DPI / CLI windows booked in the per-order inspection calendar. Each booking has a calendar cost; check the model’s published specification."

PL: Variable seven — production slot. What's the clause?

SE: "Production slot position for the target ship date: check the model’s published specification. Off-peak vs peak-season queue position: check the model’s published specification."

PL: Variable eight — rush-order posture. What's the clause?

SE: "Rush-order ladder cost per lever (partial-shift / line re-prioritization / air-freight substitution) per SKU: check the model’s published specification."

PL: Variable nine — sample-to-bulk gap. What's the clause?

SE: "Bulk clock starts on sample-approval document sign-off. Gate-closing document name: check the model’s published specification."

PL: Variable ten — Incoterms. What's the clause?

SE: "Incoterm: EXW / FOB / CIF / DDP. Calendar ownership per leg: name per leg."

PL: Variable eleven — freight mode. What's the clause?

SE: "Freight mode per leg: sea / air / courier / multimodal. Calendar per leg: check the model’s published specification."

PL: Variable twelve — port rotation. What's the clause?

SE: "Closest-port rule: Name. Calendar impact: check the model’s published specification."

PL: Variable thirteen — receiving. What's the clause?

SE: "Receiving / unpacking / commissioning window: buyer-owned, not in factory calendar."

PL: Variable fourteen — after-sales. What's the clause?

SE: "Spare-parts / replacement-unit cycle: separate from the original-order cycle. Check the model’s published specification."

PL: That's the PO. Fourteen variables, fourteen clauses, every per-order fact routed to the dated product page. No single number on this page that the factory has to defend.

SE: Right. The calendar is in the clauses, not in the verbal handshake. The clauses survive the buyer's client's project manager, the factory's production scheduler, the freight forwarder's port rotation, and the installer's commissioning window.

Annotation on the second pass — the second pass is where the calendar becomes a contract. Every per-order fact on this page is a confirmation, not an assertion. The buyer leaves the call with a clause-by-clause PO, not a handshake.

The decision matrix — when to push, when to accept, when to walk

When the supplier's response to a variable doesn't match the buyer's target, the buyer has three moves: push, accept, walk. The right move depends on the variable.

VariablePush if the variable is...Accept if the variable is...Walk if the variable is...
1. Model mixStandard SKU in catalogCustomization-heavySole-source for a non-listed feature
2. Order sizeWithin factory's normal bandAt the edge of the bandBelow the factory's per-batch floor
3. Customization depthLogo / packaging onlyFinish or firmware forkMechanical-override re-tool
4. Firmware lock-stateEarly declaration possibleMid-production declarationAfter production start
6. Inspection windowsBuyer-side onlyStandard PSI / DPIInspection that exceeds the production slot
7. Production slotOff-peak targetShoulder-season targetPeak-season target with no slack
8. Rush-order posturePartial-shift accelerationLine re-prioritizationAir-freight substitution for bulk
10. IncotermsEXW / FOBCIFDDP for an unfamiliar market
11. Freight modeSea for bulk, air for rushMultimodalAir-only for full bulk
12. Port rotationClosest-port possibleOne-transit routingMulti-transit routing

Annotation on the decision matrix — the matrix is the buyer's move-set per variable. Push, accept, walk. Each cell is per-order confirmation; check the model’s published specification.

A realistic buyer-side scenario — the 220-room renovation timeline

Consider a 220-room renovation with a soft-opening date in Q3 and an installer's commissioning window six weeks before opening. The buyer wants product on the dock roughly eight weeks before opening to clear unpacking, inventory, lot segregation, audit, and walk-through. Working backward from the dock date, the buyer needs the factory to ship eight to ten weeks before the dock date. Working forward from the sample-approval gate (variable nine), the buyer needs the bulk clock to start as soon as the sample is signed off, which means the sample order (see Smart Lock Sample Order Process) has to be placed months earlier.

The buyer's order plan looks like this: sample order placed; sample produced, shipped, received, evaluated, approved, signed off; bulk order placed the same day the sample is approved, with the sample-approval document attached; firmware lock declared in the per-order production plan; production slot booked for the target ship date; rush-order posture declared as "partial-shift acceleration only" on the slowest SKU in the mix; Incoterms chosen (the buyer typically takes FOB to retain calendar control over the freight leg); freight mode is sea for the bulk, with an air-freight partial-batch rush for the manager's apartment and the front-of-house doors that need to be commissioned first; port rotation routed to the closest Chinese port for the buyer's destination; PSI booked at the standard window; CLI booked at the standard window.

The buyer's internal calendar is separate from the factory's calendar. The factory's calendar runs from sample-approval sign-off to FOB port-of-loading. The buyer's calendar runs from FOB port-of-discharge to installer's commissioning sign-off. The two calendars meet at the Incoterms boundary. Every variable on the factory side is recorded in the model specification for each SKU and order under consideration; no number on this page is asserted as a fixed lead time.

What the factory never quite says on the first call

A factory that quotes a single lead-time number without walking through the fourteen variables is not negotiating — it is closing. A factory that walks through the fourteen variables, names per-SKU cycles, declares firmware lock windows, books inspection windows, and asks the buyer to verify in writing sample-approval sign-off before starting the bulk clock is negotiating. The buyer's job on the call is to listen for which type of factory is on the other end. The annotation that follows is the buyer's listening rule.

Annotation — what the factory never quite says. A factory that opens with a single number is guessing. A factory that opens with fourteen questions is quoting. The buyer's listening rule is to wait for the questions before accepting the number. Confirm each per-order fact on the dated product page.

The contract-side mirror — what the PO looks like

The PO is the calendar's home. Every per-order fact from the fourteen variables becomes a PO clause. The PO is not the verbal handshake; the PO is the document the buyer's client's project manager, the factory's production scheduler, the freight forwarder, and the installer's commissioning lead all hold at the same time. Each clause names the per-order fact and routes the specific number to the dated product page. No clause asserts a fixed lead time; each clause asks for confirmation.

The PO structure has four sections that mirror the fourteen variables. Section A is production-time clauses (variables 1–6). Section B is queue-time clauses (variables 7–9). Section C is shipping-time clauses (variables 10–12). Section D is post-arrival clauses (variables 13–14). Each clause names the per-order confirmation source (the dated product page) and the per-order acceptance rule (the buyer's PO sign-off).

For the broader supply-agreement considerations that sit around this PO — quality, warranty, OEM/ODM clauses — see the C12 supply-agreement cluster. The PO is the per-order contract; the supply agreement is the per-relationship contract; the lead-time clauses in this article are the per-order calendar that sits inside both.

The negotiation-call closing checklist

Before the call ends, the buyer should have the following ten items in writing or on a follow-up email, each routed to the dated product page for the model and order under consideration.

  1. Per-SKU cycle date for every SKU in the mix.
  2. Per-batch cycle count for the order size under consideration.
  3. Per-line customization clock for every customization line.
  4. Firmware lock window in the per-order production plan.
  5. Sub-tier bottleneck for the slowest SKU.
  6. Inspection window calendar (PSI / DPI / CLI) booked.
  7. Production slot position for the target ship date.
  8. Rush-order ladder cost per lever per SKU.
  9. Sample-approval gate definition and gate-closing document.
  10. Incoterms leg ownership, freight mode per leg, port rotation, and receiving / after-sales ownership.

If all ten are in writing, the PO can be drafted with confidence. If any are missing, the buyer should hold the PO until they are filled. The seven clause-handling rules and the fourteen-variable checklist are the buyer's tools to fill them.

Closing — what the buyer walks away with

A B2B lead-time conversation that ends with a single number is a conversation that will slip on the slowest variable. A B2B lead-time conversation that ends with fourteen named variables, each with a per-order confirmation routed to the dated product page for the SKU under consideration, is a conversation that holds. The fourteen-variable rule is the buyer's tool. The seven clause-handling rules are the buyer's discipline. The negotiation checklist is the buyer's call script. The PO is the buyer's home for the calendar.

For the broader four-stage sourcing flow that this negotiation sits inside, see How to Source Smart Locks From China. For the quantity-side companion, see Smart Lock MOQ Negotiation Guide. For the upstream gate that opens the bulk clock, see Smart Lock Sample Order Process. For the inspection framework that books the calendar windows, see smart-lock quality inspection.

The conversation the buyer wants to have is the conversation where the supplier answers fourteen questions before naming a date. The factory that answers fourteen questions is the factory that keeps the date. The single number the buyer walks away with is not a lead time — it is the output of fourteen per-order confirmations. To start the per-order confirmation for your own SKU mix, request a quote at Smart Lock Factory Request a Quote, order your samples at Smart Lock Factory Order Samples, and request the catalog at Smart Lock Factory Request Catalog.

Giỏ hàng của bạn
Trải nghiệm của bạn trên trang web này sẽ được cải thiện bằng cách cho phép cookie Chính sách cookie
Chat on WhatsApp