Smart Lock Glossary: Drop Ship Definition for B2B Buyers
Working Entry: What Drop Ship Means in This Programme
The drop ship definition used in this handbook is a programme-specific working definition, not a universal trade term. In this programme, drop-ship fulfillment means that a supplier or named fulfillment partner ships smart-lock units to the importer’s customer or another named destination in response to the importer’s order, without the units first passing through the importer’s own inventory. It describes the order-to-dispatch pattern, not ownership of the stock, the importer-of-record role, the payment method, or the point at which risk passes. The matching reference, written for procurement, is Smart Lock Factory vs Trading Company: Which Should B2B Buyers Choose?. The comparable treatment of the same question sits in Smart Lock Glossary: Shock and Vibration Test Definition for B2B Buyers. The product family this applies to is the smart door locks.
Direct answer. In brief, this article covers drop ship definition from drop ship definition to drop-ship. It states what to confirm about drop ship definition on the dated product page where a figure is involved. A drop ship definition is the general entry point for this category. drop ship definition anchors the vocabulary. drop ship definition has to survive later projects.
- Set the conditions — use one vocabulary for drop ship definition across the project
- Set out the choices — list the routes available for drop-ship and what each is for
- Set out what each costs — record what you give up with each route in working entry
- Treat this as the drop ship definition sequence, with drop ship as the reference.
For a smart lock importer, this working taxonomy prevents a broad label from concealing several different commercial arrangements:
| Working pattern | Where the units are held | Commercial purpose | Clause that needs special attention |
|---|---|---|---|
| Supplier-held drop ship | Supplier or partner holds the units | Avoids importer stocking | Inventory ownership, cancellation, and unsold stock |
| Order-triggered procurement | Supplier obtains units after an accepted order | Limits inventory commitment before demand is confirmed | Order acceptance and fulfillment availability |
| Partner-held drop ship | A named partner pools and dispatches units | Supports distributed wholesale lock distribution | Partner identity, selection, and control evidence |
| Wholesale buy-in | Importer receives units before onward sale | Classic resale inventory | Outside this handbook’s working definition of drop ship |
These labels are for the buyer’s own programme controls. They do not assert that every company uses them in the same way.
flowchart TD
A[Importer receives an end-customer order] --> B[Order identifies the fulfillment model]
B --> C[Supplier-held stock]
B --> D[Partner-held stock]
B --> E[Order-triggered procurement]
C --> F[Carrier receives the consignment]
D --> F
E --> F
F --> G[Shipping and control records are issued]
G --> H[Importer closes the order record]
Clause 1 — Scope, Parties, and the Fulfillment Model
The scope clause should state whether the agreement covers supplier-held stock, order-triggered procurement, partner-held stock, or a combination. It should also say which transactions are excluded. A normal wholesale purchase followed by the importer’s own dispatch is not a drop-ship transaction under this programme’s working definition, even if both orders sit under the same master agreement.
Name each party by function rather than relying on labels such as “platform,” “seller,” “vendor,” or “supplier.” At minimum, identify the buying entity, the entity issuing the order, the entity providing the products, any fulfillment partner, the carrier, and the recipient named on the shipment. The end customer should appear as a permitted destination where direct shipment is intended.
| Role | Minimum information to record | Evidence requested before use |
|---|---|---|
| Buyer | Legal name, buying entity, order authority | Corporate record and authorized signatory evidence |
| Supplier | Contracting entity, product source, order contact | Supplier profile and signed agreement |
| Fulfillment partner | Physical dispatch entity and stock location | Address, operating role, and service description |
| Carrier | Carrier identity and booking party | Carrier booking or dispatch record |
| Importer of record | Party responsible for the import entry | Written confirmation from the broker and buyer |
| End customer | Legal or trading name and delivery address | Customer order or approved destination record |
CONFIRM-WITH-LOCAL-LEGAL: Confirm whether any named party acts as seller, importer of record, agent, or customer of the carrier in each destination market, and whether the agreement reflects the parties’ actual conduct.
Clause 2 — Order Acceptance and Purchase Order Authority
A purchase order sent to a supplier is not necessarily evidence that the supplier has accepted it. The drop-ship schedule should define the point at which an order becomes binding, identify the acceptance document, and state how changes to the accepted configuration are handled.
A workable clause distinguishes four events: order submission, supplier acknowledgment, commercial acceptance, and dispatch confirmation. It should identify which fields must match across those events. Those fields normally include the buyer’s order number, product identity, quantity, finish or configuration, destination, requested delivery date, and any approved accessory list.
Use How a Supplier Is Actually Verified: Procurement Version before building the purchase order template. Its role is to expose missing decisions early, so the acceptance clause has concrete fields to confirm rather than an undefined instruction to “ship as agreed.”
The acknowledgment should use the buyer’s order reference, state accepted items and quantities, identify the fulfillment model, name the ship-from location, and record any rejected line. It should also identify the version of the commercial terms that applies. Silence should not be treated as acceptance unless the agreement deliberately says so.
CONFIRM-WITH-LOCAL-LEGAL: Have counsel confirm whether the intended order-formation process and authorized-signature requirements satisfy local contract law for the entities and destination markets involved.
Clause 3 — Product Identity and Configuration Baseline
The agreement should describe the product with enough precision that the buyer can tell whether the dispatched unit is the unit ordered. Product name alone is usually too broad for a configured smart lock. The order record should identify the SKU, finish, door-preparation requirement, mounting components, accessories, lock body or faceplate combination where ordered, and any separately supplied parts.
| Configuration field | Why it matters in a drop-ship order | Required evidence |
|---|---|---|
| SKU and product description | Distinguishes the ordered lock from adjacent variants | Supplier acknowledgment and packing list |
| Finish and appearance | Prevents mismatched project finishes | Packing list and inspection record |
| Door and frame preparation | Connects hardware selection to installation conditions | Approved configuration sheet |
| Accessories and separate items | Stops omitted components from being hidden inside the order line | Itemized packing list |
| Credential and programming responsibility | Separates hardware delivery from access provisioning | Delivery and provisioning responsibility record |
| Serial or batch reference | Connects the physical unit to its order and shipment | Serial-level packing list |
Where several units are shipped, the packing list should reconcile the physical quantity, the order quantity, and the serial references. A count that matches without matching configuration only proves that the right number of cartons arrived.
Clause 4 — Inventory Ownership, Title, and Risk of Loss
Inventory transfer and ownership are separate from the physical shipment. Stock may remain owned by the supplier until dispatch, or ownership may pass when the importer accepts the order. The agreement must say which model applies and must connect that choice to the accounting, cancellation, and unsold-stock provisions.
| Event | What must be identified | Evidence |
|---|---|---|
| Inventory transfer | Which party owns the stock before dispatch | Accepted order and stock allocation record |
| Order cancellation | What happens to reserved or unsold units | Cancellation procedure and stock notice |
| Dispatch | When and where the consignment leaves the fulfillment location | Carrier booking or acceptance record |
| Risk transfer | Which party bears loss or damage from the agreed point | Contract clause linked to a named Incoterm |
| Operational control | When the buyer can direct onward handling | Dispatch and delivery-control record |
| Reconciliation | How stock is removed from one party’s records and added to another’s | Inventory ledger and serial record |
CONFIRM-WITH-LOCAL-LEGAL: Confirm the local rules that determine when title, risk, and possession pass, including any mandatory effect of the agreement or carrier documents for the destination market.
Clause 5 — Fulfillment Point and Transfer of Control
The fulfillment clause should name the dispatching entity, the ship-from address or approved location, the named destination, the recipient, and the contact authorized to receive the shipment. If units may be dispatched from different partner locations, the clause should require the actual location to appear in the dispatch confirmation.
Transfer of control should also be stated separately from proof of delivery. Control may pass when the carrier accepts the consignment, while proof of delivery is produced only at or after arrival. If the contract treats them as the same event, a lost shipment can leave both parties waiting for a document that will never arrive.
What Happens Between Order and Arrival: Diagram Walkthrough provides a useful handoff map for separating order acceptance, warehouse release, carrier acceptance, customs activity where relevant, arrival, and proof of delivery. The drop-ship clause should assign an owner and evidence requirement to each handoff rather than describing the route as one movement.
Clause 6 — Carriage, Incoterms, and the Named Place
Incoterms and drop-ship fulfillment answer different questions. Incoterms allocate specified responsibilities, costs, and risks between seller and buyer. Drop-ship fulfillment describes the order-to-dispatch route. A contract can use both, but it should not use one as a substitute for the other.
Every Incoterm needs a named place and version context. For example, FCA allocates the handover to a named carrier at a named place, with the goods cleared for export. EXW places the handover at the seller’s premises and shifts most onward responsibilities to the buyer. Those are different starting points for a drop-ship order, particularly when the importer expects the supplier to arrange carriage.
| Question | Clause allocation | Evidence |
|---|---|---|
| Who books the carrier? | Supplier, buyer, or named fulfillment partner | Written booking responsibility |
| Who presents the goods to the carrier? | Named dispatch entity | Carrier acceptance record |
| At what point does risk pass? | Incoterm plus named place and version | Contract clause and routing map |
| Who handles export or import formalities? | Named party, subject to local confirmation | Broker or authority records |
| Where does the customer receive the goods? | Delivery or Incoterm destination, clearly distinguished | Dispatch and delivery records |
| Who controls the freight booking? | Party named in the logistics schedule | Booking confirmation |
The phrase “DDP” or “CIF” without a named place is incomplete. It may also be wrong for the physical route, especially when the seller only controls part of the journey. The clause should identify whether the Incoterm describes the supplier-to-customer movement or the supplier-to-importer movement.
CONFIRM-WITH-CUSTOMS-BROKER: Confirm the export and import responsibilities, entry structure, valuation basis, and importer-of-record role for each route; contractual labels do not by themselves determine the customs treatment.
Clause 7 — Charges, Duties, Taxes, and Accessorial Charges
The commercial-cost clause should allocate each category of charge rather than use a single phrase such as “all costs paid.” Relevant categories may include the product charge, international and local carriage, insurance arranged by either party, handling, inspection, customs entry, import duty, consumption tax, storage, and other carrier or terminal charges.
Duty and tax treatment depends on the goods, transaction, importer status, destination, and applicable rules. The importer should obtain transaction-specific advice rather than infer the result from a VAT number, a customer classification, or the term “drop ship.”
CONFIRM-WITH-CUSTOMS-BROKER: Confirm which customs entries, classifications, origin questions, and duties apply to the actual transaction and product facts.CONFIRM-WITH-LOCAL-TAX-ADVISOR: Confirm the consumption-tax treatment, invoicing requirements, recoverability questions, and responsibilities of each entity in the destination market.
Avoid promising that direct shipment will always cost less. The relevant buyer comparison is the total cost of ownership under the selected operating model, including inventory carrying, order administration, exception handling, returns, and customer service. What Total Cost of Ownership Means for Locks: Terms and Tables helps separate a purchase charge from the wider cost of operating the lock programme.
Clause 8 — Shipping Documents and Proof of Delivery
An advance shipping notice tells the receiving party what is expected and which documents are associated with the cargo. It is not the bill of lading and does not itself transfer title. A bill of lading is a carrier document for goods shipped on a vessel, but it is not proof that the customer received the ordered goods. For a drop-ship transaction, retain arrival evidence separately.
| Document or record | What it supports | What it should not be used alone to prove |
|---|---|---|
| Order acknowledgment | Commercial acceptance and accepted configuration | Physical dispatch |
| Itemized packing list | Package contents and quantities | Condition of the contents |
| Serial-level packing list | Which unit or units were assigned | Customer receipt |
| Carrier booking or receipt | Carrier acceptance and route reference | Final delivery |
| Advance shipping notice | Expected arrival and document reference | Title transfer |
| Proof of delivery | Delivery to the named destination | Absence of concealed damage |
| Exception or damage record | Condition observed at the relevant point | Root cause of later failure |
For electronic access-control products, the serial-level packing list also supports installation, configuration, credential issuance, and later service records. It should be stored in a way that links the physical unit to the correct order without exposing unnecessary customer access data.
How a Supplier Is Actually Verified: Diagram Walkthrough is relevant here because document templates are only useful when the party issuing them can show how its operational records are created, checked, and retained.
Clause 9 — End-Customer Data and Credential Confidentiality
A direct-ship model may require the supplier or fulfillment partner to receive an end customer’s name, contact details, delivery address, installation information, or order references. The agreement should limit each data field to a defined operational purpose and identify who may access it.
Customer access credentials should not travel merely because an address travels. If programming is part of the scope, name the party responsible for provisioning, revocation, handover, and records. If programming is excluded, say so in the delivery record so the absence of a credential does not become an implied service failure.
| Information | Permitted purpose in the working model | Control to request |
|---|---|---|
| Delivery name and address | Carrier routing and delivery | Restricted order record |
| Customer contact details | Delivery issue or access coordination | Named contact and limited access |
| Installation and door details | Product preparation and compatibility check | Approved project record |
| Order and serial reference | Configuration and service traceability | Linked order dossier |
| Access credentials | Only where expressly assigned | Controlled handoff and revocation record |
The confidentiality clause should also cover screenshots, dispatch labels, installation notes, and retained customer records after the transaction closes. Data-retention instructions should identify the operational record, responsible party, and removal or access process rather than use an indefinite blanket term.
CONFIRM-WITH-LOCAL-LEGAL: Confirm the privacy, data-protection, cross-border transfer, employee-access, and record-retention requirements that apply to customer and installation data in every relevant jurisdiction.
Clause 10 — Inspection, Acceptance, and Nonconformance
The buyer needs a route for reporting a quantity discrepancy, visible damage, incorrect finish, missing accessory, wrong configuration, damaged packaging, or a serial mismatch. The first action should be defined for each issue: preserve the package and serial reference, photograph the condition, notify the named party, and await disposition instructions.
| Nonconformance | Minimum first record | Required disposition before stock is reused |
|---|---|---|
| Wrong item or configuration | Order, acknowledgment, and serial reference | Supplier identifies the correction or replacement route |
| Visible transit damage | Carton, unit, and package evidence | Carrier or supplier disposition |
| Missing accessory | Itemized packing list and site check | Correct item supplied or other documented resolution |
| Serial mismatch | Physical label and serial-level list | Reconcile the physical unit and order record |
| Customer refusal at delivery | Carrier exception and delivery attempt record | Return, redelivery, or cancellation route approved |
Acceptance procedures must not remove mandatory consumer, contractual, or product-protection rights in the destination market. Write the operational process, then have local counsel review its effect.
CONFIRM-WITH-LOCAL-LEGAL: Confirm whether inspection, acceptance, rejection, or claim procedures can be applied without restricting mandatory rights under the applicable sale, consumer, and product law.
Clause 11 — Returns, RMA, and Spare-Parts Routing
A direct-ship agreement needs a return path that does not assume the importer physically receives the goods. The clause should name the party that issues an RMA reference, the address or approved collection point, the carrier booking party, and the required documentation.
| Return type | Evidence at issue | Routing question |
|---|---|---|
| Wrong configuration | Order and serial reconciliation | Who identifies the correct shipment location? |
| Transit damage | Packaging and carrier exception record | Who initiates the carrier claim? |
| DOA handling | Serial, symptom record, and initial checks | Where is the unit quarantined? |
| Warranty claim | Purchase and service evidence | Who authorizes diagnosis and disposition? |
| Spare-parts request | Approved configuration and part identity | Which stock location can supply the item? |
A warranty claim process should state how evidence is submitted and how decisions are communicated. It should not state a warranty period or imply that the process replaces rights that cannot be limited.
CONFIRM-WITH-LOCAL-LEGAL: Confirm mandatory warranty, consumer, product-liability, and return-right provisions that apply to direct-to-customer lock sales in the destination market.
Clause 12 — Change Control, PCN, and Replacement Planning
Product Change Notification, or PCN, is the notice a supplier gives when a product or its specification changes. A change is still a change when it is presented as an improvement, simplification, replacement, or corrective action. The approved order baseline must be protected against silent substitution.
| Change type | Required buyer action | Record to update |
|---|---|---|
| Documentation-only clarification | Confirm whether the shipped configuration changed | Order evidence |
| Packaging or labeling change | Check shipment identification and customer information | Dispatch and site records |
| Component or accessory change | Compare the change with the approved configuration | Configuration baseline |
| Product or firmware change | Review compatibility, provisioning, and installed-base implications | Product and service record |
| Obsolete SKU | Identify open orders, stock, spares, and service commitments | Lifecycle plan |
Clause 13 — Liability, Records, and Evidence Preservation
Liability allocation should follow the events the parties can control and the evidence they can preserve. The contract should not use a blanket statement that one party accepts every loss. Instead, it should connect risk allocation to specific events such as nonconforming goods, carrier loss, delayed disclosure, inaccurate documentation, unauthorized stock substitution, or failure to follow the agreed route.
A complete evidence set should be available when an exception occurs:
- The issued purchase order and supplier acknowledgment.
- The approved product and configuration record.
- The itemized and serial-level packing lists.
- The carrier booking, tracking, and delivery records.
- The inspection or exception report.
- The RMA, repair, replacement, or credit record.
- Any PCN or change notice connected to the affected units.
CONFIRM-WITH-LOCAL-LEGAL: Confirm the enforceability and scope of limitation, indemnity, liability, insurance, and dispute-resolution provisions for the contracting entities and relevant destination markets.
Clause 14 — Suspension, Termination, and Stock Run-Out
A long-term drop-ship schedule should say what happens when one party cannot continue the agreed model. Suspension may be tied to an unresolved evidence gap, repeated nonconformance, unauthorized fulfillment through another party, or a material failure in the order and documentation process.
The build-up behind that decision is in smart lock factory in china a b2b buyer s. That is the same question drop ship definition has to answer here.Termination does not erase open transactions. The exit section should address accepted but unshipped orders, goods already in transit, customer deliveries awaiting proof, open RMA cases, reserved stock, spare-parts commitments, and records that must remain available for service or legal purposes.
It is worth pairing this with how smart lock manufacturing works. That is the same question drop ship definition has to answer here.
| Open item | Required treatment in the exit plan |
|---|---|
| Accepted order not yet dispatched | Cancel, fulfill, or replace under an express written decision |
| Stock reserved for an order | Confirm whether it remains reserved or returns to available stock |
| Shipment in transit | Preserve carrier, insurance, customs, and delivery records |
| Return under investigation | Keep the unit segregated and retain the RMA record |
| Customer installation | Preserve configuration and service documentation |
| End-customer data | Apply the agreed access, return, or deletion process |
CONFIRM-WITH-LOCAL-LEGAL: Confirm termination, notice, survival, data handling, and outstanding-liability provisions under the applicable governing law.
Clause 15 — Order of Precedence and Contract Control
The agreement should establish which document wins when the purchase order, acknowledgment, fulfillment schedule, carrier instruction, and operational policy differ. A sensible order of precedence may place the master agreement first, the drop-ship schedule next, the accepted purchase order and acknowledgment after that, and operational policies last.
| Document | Purpose | Required control |
|---|---|---|
| Master agreement | Sets the commercial and legal framework | Version and authorized signature |
| Drop-ship schedule | Defines roles, route, evidence, and exceptions | Version attached to the agreement |
| Purchase order | Requests a specific order | Buyer reference and approval |
| Supplier acknowledgment | Records acceptance and dispatch details | Match to order and schedule |
| Carrier record | Confirms the physical route | Reconciled with dispatch notice |
| Operational policy | Explains routine handling | Cannot override higher-ranked terms without approval |
CONFIRM-WITH-LOCAL-LEGAL: Confirm the governing law, dispute forum, hierarchy of contractual documents, and enforceability of electronic order acceptance for the transaction.
Importer Clause Acceptance Worksheet
| Clause check | Buyer question | Evidence required | Hold if unanswered |
|---|---|---|---|
| Working model | Which stock and dispatch model applies? | Written scope and role schedule | Label remains ambiguous |
| Order acceptance | Which event creates the binding order? | Purchase order and acknowledgment | Dispatch basis unclear |
| Configuration | Which fields define the ordered lock? | Signed configuration schedule | Unit identity unclear |
| Inventory | Who owns the stock and when does risk pass? | Inventory and title clause | Loss exposure unclear |
| Fulfillment | Who dispatches from which location? | Dispatch confirmation | Carrier route unknown |
| Incoterms | Which term and named place apply? | Completed Incoterms field | Cost and risk unallocated |
| Charges | Who pays each duty, tax, and accessorial charge? | Cost-allocation schedule | Invoice responsibility disputed |
| Documents | What record proves dispatch and delivery? | Document index | Order cannot be closed |
| Customer data | Why is each field shared? | Data schedule and role record | Disclosure lacks purpose |
| Nonconformance | How is a mismatch reported and dispositioned? | Exception procedure | No operational remedy |
| Returns | Who issues and controls the RMA? | Return-routing schedule | Failed unit has no path |
| PCN | How are product changes communicated? | Change-control clause | Approved baseline can drift |
| Evidence | Which records support a claim? | Evidence-retention rule | Attribution depends on memory |
| Exit | How are open orders and stock closed? | Exit schedule | Transition risks orphaned units |
Questions to Put to the Counterparty Before Signing
Ask the supplier to answer these questions in the agreement or attach a completed schedule. The answers should be consistent across the master agreement, order acknowledgment, and dispatch process.
- Which entity legally offers the products to the buyer?
- Which entity holds the stock when the buyer’s order is accepted?
- Which entity physically packs and presents the goods to the carrier?
- Is the buyer named as importer of record, consignee, or another role?
- Which Incoterm and named place govern the route?
- When does risk pass, and how is it evidenced?
- Which document closes the order: acknowledgment, dispatch notice, proof of delivery, or another record?
- Who receives a shortage, damage, or configuration complaint from the end customer?
- What serial-level information accompanies the shipment?
- Which customer data may be shared with the fulfillment partner?
- What happens to accepted orders, reserved stock, and returns when the arrangement ends?
The answers reveal whether “drop ship” is an operational instruction or merely a marketing label. For B2B wholesale lock distribution, the label becomes commercially usable only when the parties can trace the same transaction through acceptance, stock allocation, dispatch, arrival, customer installation, and exception handling.
When the file is ready, request a quote against the written requirement.

