Inbound Logistics / Milk Run and Supplier Delivery-Window Pages on Changzhou Manufacturer Websites: How Should They Be Accepted?

Direct answer: Inbound logistics / milk run is not "the supplier delivers to the gate". The website page should state the delivery model (supplier direct delivery, milk-run collection, consolidation/cross-dock), booking windows and ASN, route/frequency/cut-off, packaging/labelling/loading, unloading/receipt, damage/shortage liability, KPIs/costs and exception handling. On the law: risk of loss/damage generally passes from seller to buyer on delivery (Civil Code Article 604, unless law or contract provides otherwise); where the seller delivers the goods to a carrier at the agreed place, risk may pass to the buyer (Article 607); if the buyer refuses to take delivery, risk passes from the time of breach (Article 608). The carrier is liable for loss/damage during transport unless it proves force majeure, the nature of the goods/reasonable loss, or the fault of the shipper/consignee (Article 832); compensation follows the contract or, absent agreement, the market price at the destination at delivery (Article 833). Freight operators should meet road-transport licensing/vehicle-certificate requirements (with an exception for ordinary freight vehicles of 4,500 kg or less); driver/visitor personal data should follow minimal necessity, notice and security. Information is current to 2026-11-07. This is a review of public rules and page practice, not legal, logistics, insurance or procurement advice; the contract, carrier agreement and site rules control.

This guide is for procurement, logistics, warehouse, quality, EHS and website teams at equipment, electronics/electrical, automotive, medical device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby areas. This page most often misses model, window, ASN, route, packaging, unloading, damage and KPIs, ending up as "please book in advance".

How does this page relate to the supplier portal, three-way match and packaging pages?

The inbound logistics page answers "how, when and where the supplier delivers, how it is unloaded, and what happens on damage"; the supplier portal / SRM page answers registration, RFQ, orders/ASN, e-signature and data security; the procurement three-way match/reconciliation page answers how order/receipt/invoice align; the packaging, shipping marks and delivery page answers crates/pallets, Incoterms, risk transfer and damage claims. Inbound logistics is execution; an order page or packaging page cannot replace it.

Common breakpoints: only "book in advance", no window/ASN; milk-run route/frequency/cut-off unclear; packaging/labelling does not match the receipt; unloading/detention fees not stated; damage/shortage liability unclear; carrier qualification/insurance not checked; KPI "on time" without a definition; exception/line-stop escalation missing. Separate "model—window—route—packaging—unloading—damage—KPI—exception"; then procurement, logistics, warehouse and suppliers share one playbook.

This page map is editorial; the contract, order, carrier agreement and site rules control.

How should the inbound logistics model be defined?

Common models: supplier direct delivery (supplier or its carrier delivers to the plant), milk run (the manufacturer/3PL collects from several suppliers on a fixed route), consolidation/cross-dock (goods go to a consolidation point/warehouse and then to the plant), and VMI/consignment (supplier stock on site or nearby, settled by usage). The model changes the window, ASN, packaging, liability and cost. The page should state which suppliers/categories use which model, who books the carrier, who pays freight, who bears in-transit risk and who files the ASN.

Acceptance checks: model; applicable suppliers/categories; who books/carries; freight/insurance; in-transit risk; ASN responsibility; exception contact. Common gaps: mixed models; unclear freight/insurance; milk run but supplier still self-delivers; VMI stock ownership/settlement unclear; no exception contact.

The model definitions are editorial; the contract/carrier agreement/site rules control.

How should delivery windows, booking and ASN be accepted?

A delivery window should state which day/time range, which gate/dock, how far in advance to book, the booking channel, and what happens on late/early arrival, cancellation or rescheduling. An ASN (advance shipping notice) should at least include supplier, PO number, item/model, quantity, batch, packages/pallets, vehicle/driver and estimated arrival. Without an ASN/window, the warehouse cannot plan docks/labour and the supplier may be turned away. The window should be tied to capacity/docks/receiving hours, not "any time".

Acceptance checks: window; booking channel/cut-off; ASN fields; late/early; cancellation/reschedule; dock/gate; contact; records. Common gaps: no booking; ASN missing PO/batch; window not matching dock capacity; no late handling; no cancellation cut-off; no driver contact.

Window/ASN is editorial; warehouse/logistics policy controls.

How should milk-run routes, frequency and cut-off be accepted?

A milk run should state the route/area, supplier sequence, collection frequency/day, each stop's pickup window, loading cut-off, vehicle/driver, maximum load and exception handling (traffic, shortage, breakdown). A route is not "on the way"; it needs a fixed timetable and capacity constraint. Suppliers need to know "ready by what time, where to place goods, who loads, and what happens if missed". The page may show a route map/schedule/contact, but should not publish sensitive supplier information.

Acceptance checks: route/area; sequence; frequency; stop window; cut-off; vehicle/capacity; loading responsibility; exception; records. Common gaps: unclear route; frequency not matching capacity; late cut-off; overload; unclear loading; no contingency.

Milk-run rules are editorial; the route/carrier agreement controls.

How should packaging, labelling and loading be accepted?

Packaging/labelling should support matching, counting, stacking and damage prevention: outer carton/pallet label with supplier, PO number, item/model, quantity, batch, destination/receiving warehouse; pallet size/height/wrapping/edge protection; fragile/moisture/this-side-up marks; mixed/pallet rules; returnable packaging ownership/cleaning/recovery. Loading should be secured/anti-tilt/rain-proof, without overload/overheight; dangerous goods/lithium batteries follow regulations/carrier requirements. Packaging/labels should match the ASN, delivery note and receipt.

Acceptance checks: label fields; pallet spec; stacking/wrapping; fragile/moisture; mixed/pallet; returnable; load securing; dangerous goods; consistency. Common gaps: label missing PO/batch; pallet too high; mixed without list; returnable ownership unclear; load not secured; dangerous goods mixed.

Packaging/loading is editorial; the packaging spec/carrier requirements control.

How should documents, ASN and receipt be matched?

The delivery note/ASN/packing list/goods receipt should match: supplier, PO number/line, item/model, quantity, batch, package count, vehicle/driver and arrival time. On receipt, count pieces/pallets against the ASN/delivery note, check packaging/seals/temperature (if applicable) and take photos; record shortages/overages/damage/wrong item/no documents, then route to GR/inspection/claims. If documents do not match, do not let the driver "unload first and fix later"; confirm before unloading to avoid unclear liability.

Acceptance checks: delivery note; ASN; packing list; GR; field consistency; signature; deviations; photos. Common gaps: no documents; ASN vs delivery note mismatch; batch/count mismatch; unload before documents; no deviation record; no photos.

Documents/receipt are editorial; warehouse/quality/finance policy controls.

How should unloading, waiting and detention be accepted?

The page should state how vehicles queue/take a number on arrival, which gate/dock, who unloads (supplier/warehouse/third party), unloading time limit, waiting/detention fee standard, how overtime is calculated, and holiday/night arrangements. Detention is a common dispute: early/late arrival, warehouse busy, dock occupied and incomplete documents all cause waiting. Rules should state "free waiting time, how overtime is charged, who confirms, how evidence is kept", not just "follow site arrangements".

Acceptance checks: queue/number; gate/dock; unloading responsibility; time limit; free waiting; detention fee; confirmation; records. Common gaps: no queue rule; unclear unloading; no time limit; verbal detention fee; no overtime confirmation; no holiday arrangement.

Unloading/waiting is editorial; site/carrier agreement controls.

How should damage, shortage and liability be accepted?

First check the contract/order delivery place and risk transfer: under Civil Code Article 604, risk of loss/damage is borne by the seller before delivery and the buyer after delivery, unless law or contract provides otherwise; Article 607 provides that where the seller delivers the goods to the carrier at the agreed place, risk may pass to the buyer; Article 608 provides that if the buyer refuses to take delivery, risk passes from the breach. The carrier is liable for loss/damage during transport unless it proves force majeure, the nature of the goods/reasonable loss, or the fault of the shipper/consignee (Article 832); compensation follows the contract or, absent agreement, the market price at the destination at delivery (Article 833). The page should state who insures, who claims, deadlines, evidence and deductibles/limits.

Acceptance checks: delivery place; risk transfer; carrier/insurance; claim deadline; evidence (photos/seal/signature/inspection); deductible/limit; responsible party. Common gaps: unclear risk transfer; carrier unlicensed/uninsured; damage photographed but not reported; claim out of time; deductible/limit unknown; all responsibility pushed to the driver.

Risk/carrier liability follows Civil Code Articles 604/607/608/832/833; the contract/policy controls.

How should KPIs, costs and exceptions be accepted?

KPIs need definitions: OTIF (on time in full), window compliance, ASN accuracy, unloading waiting/detention time, damage/shortage rate, exception response time, freight/expedite cost. Costs should include freight, loading/unloading, waiting/detention, expedite/dedicated vehicle, returnable packaging deposit/cleaning and insurance; state who bears them, how they are calculated and reconciled. Exceptions should cover late/no-show, vehicle breakdown, shortage, incomplete documents, damage, system/ASN failure and line-stop escalation; each needs a contact, deadline and contingency.

Acceptance checks: KPI definition/denominator; cost items; bearer; calculation; reconciliation; exception type; contact; escalation; records. Common gaps: KPI without definition; missing cost items; verbal expedite fee; no exception contact; no line-stop escalation; no review.

KPIs/costs are editorial; the contract/carrier agreement/company policy control.

How should driver/visitor personal data be handled?

Delivery booking/gate access often collects driver name, mobile number, plate number, ID/driving licence. Under the Personal Information Protection Law, processing should have a clear, reasonable purpose directly related to that purpose and use the least intrusive method; collection should be limited to the minimum scope necessary, with no excessive collection (Article 6). Processing needs a legal basis (consent/contract necessity/legal duty, etc., Article 13); before processing, the processor should clearly and intelligibly inform the individual of its name/contact, purpose/method/categories/retention period and rights (Article 17); and adopt encryption/de-identification, access control, training and contingency plans (Article 51). The page should state what is collected, why, how long it is kept, who can see it, and how to delete/correct it.

Acceptance checks: fields; purpose; legal basis; notice; retention; access; security; deletion/correction. Common gaps: excessive ID collection; no notice; indefinite retention; over-broad access; no deletion/correction; no breach plan.

Personal data follows Articles 6/13/17/51 of the Personal Information Protection Law; the law/company policy controls.

How should the inbound logistics/milk-run page be written?

Suggested content: (1) applicable suppliers/categories/model; (2) delivery window/booking/ASN; (3) milk-run route/frequency/cut-off; (4) packaging/labelling/loading; (5) documents/receipt; (6) unloading/waiting/detention; (7) damage/shortage/liability/claims; (8) KPIs/costs/exceptions; (9) driver/visitor personal data; (10) contact/version/update date. The public page explains rules, routes, time windows and capability; it should not publish supplier lists/prices/sensitive route points; after login, suppliers can see their own window/ASN. State "the contract/carrier agreement/site rules control"; do not write "deliver any time / unloading guaranteed / compensation guaranteed".

Use consistent English terms (inbound logistics, milk run, delivery window, ASN, dock, goods receipt, detention, risk transfer, carrier liability, OTIF) and state the review date. Link to the supplier portal/SRM, three-way match and packaging/shipping marks pages, but do not present inbound logistics as outbound sales logistics.

This structure is editorial; external statements must be truthful and verifiable, per the contract/carrier agreement/site rules.

What must not be written?

High-risk claims: "deliver any time / no booking" (windows/docks/labour are limited); "milk run is just on the way" (fixed route/schedule/capacity); "delivered means transferred" (risk depends on contract/delivery place); "damage is always the driver's fault" (carrier/insurance/liability allocation); "unloading guaranteed / detention free" (responsibility/cost must be stated); "unload first, fix documents later" (deviation/liability unclear); "collect driver data freely" (minimum necessity/notice/security); "KPI is only on-time" (OTIF/window/ASN/damage); "publish routes/supplier lists" (commercially sensitive). These are inaccurate or misstate the model, risk or responsibility.

Safer wording: "This page applies to [supplier/category], model [direct/milk run/consolidation/VMI]; window [time/gate/dock], ASN [fields]; route/frequency [schedule]; packaging/labels [spec]; unloading/waiting [responsibility/time/fee]; risk/carrier/claim [contract/policy]; KPI [definition]; exceptions [contact/escalation]; personal data [fields/purpose/retention]. The contract, carrier agreement and site rules control." External promotion must comply with advertising and fair-competition rules; supplier/route data need authorisation or redaction.

Go-live acceptance checklist

Ten checks: model, window/ASN, milk-run route, packaging/labels, documents/receipt, unloading/waiting, damage/liability, KPIs/costs, exceptions/contact, personal data/page wording. Each needs an owner, evidence and review date. The pass condition is not "the page says booking", but that procurement/logistics/warehouse/suppliers can find the window, route, packaging, unloading, damage and exception rules.

Before go-live, run one real supplier/route through: model → window/ASN → route → packaging → delivery/receipt → unloading → damage → KPI/cost → exception → personal data → page wording. Any step that fails is a gap in the page or site process.

This checklist is editorial; the contract, carrier agreement and site rules control.

Who should read this, who should not, and what decisions does it support?

It suits procurement, logistics, warehouse, quality, EHS and website teams at equipment, electronics/electrical, automotive, medical device, hardware, chemical, packaging and export manufacturers in Changzhou and nearby areas; also companies building a milk-run/inbound logistics page for the first time, or facing detention/damage/late arrival/window conflicts. It does not suit teams that only handle outbound sales logistics, do not involve supplier deliveries, or want one page to replace the carriage contract/insurance/legal advice.

Read it if you are building an inbound logistics/milk-run page; windows/ASN are unclear; route/frequency/cut-off are unclear; packaging/labels do not match; unloading/detention disputes; damage/shortage liability is unclear. Skip it if you treat "any time" as a rule, milk run as "on the way", damage as the driver's fault, or want to publish routes/supplier lists. It supports self-review of model, window/ASN, route, packaging, documents/receipt, unloading/waiting, damage/liability, KPI/cost, exceptions and personal data.

FAQ

What is a milk run?

A milk run is a circular collection/consolidation model: a vehicle follows a fixed route, frequency and timetable to collect from several suppliers and then delivers to the plant. The route, frequency, capacity, loading responsibility and costs follow the company/carrier agreement; it is not "the supplier delivers on the way" and not the same as direct delivery.

What should the delivery window/ASN include?

The window states day/time/gate/dock/booking cut-off; the ASN states supplier, PO number, item/model, quantity, batch, packages/pallets, plate/driver and estimated arrival. Without an ASN/window, the warehouse cannot plan docks/labour and the supplier may be turned away.

Who is liable for damage/shortage?

First check the contract/order delivery place and risk transfer: Civil Code Article 604 (seller before delivery, buyer after, unless otherwise agreed); Article 607 (delivery to carrier may pass risk to buyer); Article 608 (buyer refusing delivery bears risk from breach). The carrier is liable for loss/damage during transport unless it proves force majeure/nature of goods/reasonable loss/fault of shipper or consignee (Article 832); compensation follows the contract or, absent agreement, the market price at destination (Article 833).

What carrier qualifications should be checked?

Freight operators should obtain a road-transport operating licence/vehicle operating certificate (with an exception for ordinary freight vehicles of 4,500 kg or less in ordinary freight operation); operators should prevent cargo falling/spilling; dangerous goods follow special requirements. The page/contract should state carrier qualification, vehicles, insurance, liability and claims.

How are detention/waiting fees calculated?

The page should state free waiting time, how overtime is charged, who confirms and how evidence is kept (arrival/start unloading/departure timestamps), plus holiday/night arrangements. Detention is a contract/site rule, not a uniform statutory standard; "follow site arrangements" alone is not enough.

How should driver/visitor data be collected?

Under the Personal Information Protection Law: clear/reasonable purpose and minimum necessity (Article 6); a legal basis (consent/contract/legal duty, Article 13); notice of purpose/categories/retention/rights before processing (Article 17); and security measures such as encryption/de-identification/access control/training/contingency (Article 51). The page should state what is collected, why, how long, who can see it and how to delete/correct it.

One-sentence takeaway

A Changzhou manufacturer's inbound logistics/milk-run page is not about "book in advance". It should turn model, window/ASN, route/frequency, packaging/labels, documents/receipt, unloading/waiting, damage/liability, KPIs/costs, exceptions and personal data into a reviewable checklist—so procurement, logistics, warehouse and suppliers can deliver, unload, match and claim from the page.

Method and limitations

This is a review of public rules and page practice, not legal, logistics, insurance or procurement advice. No undisclosed customer, price, route or supplier data were used; processes, fields, tables and acceptance items are editorial, not legal/logistics conclusions. Risk transfer/carrier liability follows Civil Code Articles 604/607/608/832/833; road-transport licensing/vehicle requirements follow the Road Transport Regulations; personal data follows Articles 6/13/17/51 of the Personal Information Protection Law; the contract, carrier agreement, policy and site rules control.

Sources and scope

Information is current to 2026-11-07. The following are official pages; their text controls.

1. Civil Code of the People's Republic of China: Supreme People's Court. Risk transfer (Articles 604/607/608), carrier liability (Articles 832/833).
2. Road Transport Regulations of the People's Republic of China: National Administrative Regulations Database. Freight operating licence/vehicle certificate, prevention of cargo falling/spilling, dangerous goods transport.
3. Personal Information Protection Law of the People's Republic of China: NPC website. Minimum necessity (Article 6), legal basis (Article 13), notice (Article 17), security measures (Article 51).