Delivery & quality · Available now
PDI & Vehicle Delivery Centre
A scratch found in the yard costs a repair. The same scratch found after handover costs a repair, a claim and a customer. PDI is the cheapest correction in the whole chain — and the easiest step to reduce to a signature.
Prefer Chinese? The Chinese edition of this page carries the full source list and every numeric caveat. 本页中文版
- SegmentsBody · electrical · software · documents
- GatesRe-inspection · document completeness
- RecordOne check sheet per VIN
- AttributionPosition · batch · model
- BoundaryNot a statutory inspection
1. A check sheet full of ticks
PDI usually fails for a structural reason: it is recorded as a signature instead of as a record.
The vehicle is at the port, the customer is asking for a delivery date, sales has already scheduled handover. PDI becomes the step where someone signs so the schedule holds. Every box is ticked and nobody looks.
Four weeks later the customer finds a repainted rear door. The check sheet says 'exterior acceptable'. Written that way, the line was never decidable: two technicians looking at the same car would not reach the same conclusion, so the record could not have caught anything.
- Paper check sheets. Filed and never counted. Who did what, and what was found, cannot be summarised after the fact.
- Undecidable items. 'Exterior good', 'functions normal', 'interior clean' give no basis for a fail, so the default is a pass.
- Defects without closure. A scratch is reported verbally to the prep shop; the prep shop finishes; nobody writes the result back. The item stays open forever.
- Software and configuration missed. Head-unit language, navigation maps, Bluetooth pairing, ADAS calibration — the items most often missed in a new market, and the first thing a customer notices.
- Documents checked on delivery day. Invoice, certificate of conformity, warranty booklet — a missing item means the customer cannot register the car, and it is discovered at the worst possible moment.
The response is one traceable technical file per vehicle: decidable check items, defects that cannot close without re-inspection, an initialisation list per destination market, and a document completeness gate before handover.
The second benefit is managerial. Once defects carry a position and a batch, a repeating defect can be attributed to transport, to loading or to the plant — instead of being met again next month with the same surprise.
2. Four segments, three defect classes
Segments decide who inspects. Classes decide who is allowed to decide.
| Segment | What is checked | Usually performed by | Typical finding |
|---|---|---|---|
| Exterior and body | Paint, panel gaps, glass, tyres, visible underbody | Technician | Transit scratches, repaint, gap out of tolerance |
| Function and electrical | Lights, wipers, windows, air conditioning, seats, cluster warnings | Technician | Inoperative function, noise, warning lamp |
| Software and configuration | Head-unit language, maps, Bluetooth, ADAS calibration, OTA state | Technical role | Language not switched, maps absent, calibration not performed |
| Documents and handover state | Invoice, certificate of conformity, warranty booklet, onboard tools | Delivery coordinator | Missing item, tools absent, plate details mismatched |
Items and tolerances are configured per model and per destination market; the table is the segmentation, not a fixed checklist.
<strong>A — functional.</strong> Affects whether the vehicle can be delivered: repair first, then re-inspect that segment. The gate is hard — the delivery step cannot proceed. A soft warning will be bypassed, every time.
<strong>B — cosmetic.</strong> Affects saleability and price, so it is graded: minor (disclose, with a price adjustment or prep), moderate (prep, then deliver), severe (repair or replace the vehicle). Sales and delivery decide together, because the cost lands in the price rather than in a work order.
<strong>C — documentary.</strong> Affects whether the vehicle can be registered. Completeness is verified before handover and a missing item blocks the delivery confirmation. This is the cheapest check in the process and the most expensive one to skip.
Mixing the three into a single queue turns every defect into 'let us discuss it later'. The grading is not academic — it assigns the right to decide, and it decides who pays.
3. Eight steps, two hard gates
This process has a loop: a defect goes to rework and must come back to re-inspection. The loop is the process, not an exception.
| Step | Gate | What must be true | What is recorded |
|---|---|---|---|
| 1. Arrival and receipt | VIN and accompanying documents matched, vehicle in an inspectable state | Receipt record | |
| 2. Four-segment inspection | Body, electrical, software and documents inspected | Check sheet | |
| 3. Defect grading | Class A/B/C assigned, handling path set | Graded defect list | |
| 4. Prep and repair | Work order raised, parts and hours recorded | Rework order | |
| 5. Re-inspection | Gate | The original inspector confirms the defect is gone and nothing new was introduced | Re-inspection result |
| 6. Configuration initialisation | Language, maps, calibration and OTA set from the destination list | Initialisation record | |
| 7. Document completeness | Gate | Invoice, certificate, conformity certificate and handbook checked item by item | Completeness result |
| 8. Handover and acceptance | Customer inspects and signs; the record is sealed as the after-sales starting point | Delivery note |
A missing or mismatched document sends the batch back for correction; the vehicle stays in storage and the delay is costed.
The real path is often longer than the drawing: re-inspection finds a mark introduced during prep, the defect is re-graded (this time as a process problem), and another order is raised. The system keeps every iteration — without that, 'repaired three times and still wrong' cannot be seen, let alone escalated.
One boundary has to be stated plainly: PDI is not a statutory inspection. It does not replace the manufacturer's pre-delivery check, and it does not replace the type-approval process of the destination market. It is the seller's own gate before handover, and describing it as anything else will not survive a customer question.
4. Eight fields decide whether a defect can be attributed
A defect record without a position or a class produces a count, not a conclusion.
Each defect carries: position (which part of the vehicle), class (functional / cosmetic / documentary), grade, point of discovery, handling method, who repaired it, re-inspection result, and iteration count. Drop one of these and the record can still be counted — it just cannot be explained.
The record is keyed on the VIN, which is what makes it usable twice: as a delivery quality file, and as the line between a condition that existed at handover and a failure that appeared afterwards.
| Written by | What it contributes to the VIN file |
|---|---|
| Delivery coordinator | Receipt, VIN, accompanying documents, inbound state |
| Technician, exterior | Body positions, defect description, photos, grading |
| Technician, function | Item-by-item results, warnings, noises |
| Technical role | Head-unit version, maps, calibration, OTA state |
| Prep shop | Work order, parts replaced, hours, cost |
| Original inspector | Re-inspection result, iteration count |
| After-sales | Defect list at handover, warranty start |
Photos are part of the check item, not a supplement: fixed angles at the four corners, cluster mileage and plate, bound to the check sheet and not replaceable afterwards.
Why this granularity: if cosmetic defects across three consecutive batches concentrate on the same rear door, a position field turns that into a hypothesis about how the vehicles were secured in transit. A summary line reading 'twelve cosmetic defects' does not — it only says there are many.
It is also the warranty boundary. A defect present at handover and a failure that appears afterwards carry different responsibility, and the PDI record is the only artefact that separates them. Without it, every claim becomes a negotiation.
5. Five terminals, one record
PDI happens in the yard, so the phone is the main terminal — not the office screen.
| Terminal | Where it is used | What it does |
|---|---|---|
| Desktop / internal workspace | Delivery centre managers, technical leads | Checklist templates, defect statistics, exception approval, handover scheduling |
| Mobile | Technicians, delivery coordinators | Item-by-item checks, photos, defect submission, re-inspection — works offline |
| Dealer portal | Overseas dealers | PDI status and estimated handover date for their own vehicles |
| Group dashboard | Management | Pass rate by market, defect class distribution, average handling time |
| Public website | — | Not used for this line |
A submitted inspection result cannot be edited; only supplementary notes and re-inspection results can be appended. If it could be edited, it would stop being evidence.
Two hard rules. Submitted conclusions are immutable. Defect photos cannot be replaced after the fact — the file and the submission time are bound together, which is the only mechanism that prevents a photo taken after handover from being filed as if it were taken before.
The portal deserves a specific cut: a dealer sees status and estimated date for its own vehicles, with defect detail and internal cost excluded. That is enough for scheduling and not enough to leak pricing.
6. Where PDI becomes a signature ceremony
Four of these are about execution. Two are about what may be claimed.
- Undecidable items. 'Good', 'normal', 'clean' cannot fail. If two technicians disagree on the same car, the item is still too coarse.
- Paper check sheets. Nothing can be counted, attributed, or used as an after-sales boundary. A paper sheet ends in a filing cabinet.
- Defects reported verbally. No work order, no re-inspection, and the defect sits in 'pending' until it is forgotten.
- Handover without re-inspection. Prep itself introduces damage. Skipping re-inspection trades one defect for another and calls it closure.
- Document completeness checked on delivery day. A customer who has paid and cannot register the car is the most expensive scenario in this line.
- Claiming PDI is a state inspection. It is a commercial gate held by the seller. Saying otherwise will not survive a customer question or a regulator's.
Execution problems make PDI ineffective — annoying, and expensive over a year. Claiming problems make the company carry a promise it never made, and those are the ones that end in writing.
7. Questions we are asked most
Six, in the order they arrive.
Does PDI delay delivery?
Inspection time depends on the item count and on whether prep is needed. What delays delivery is finding a defect late, not inspecting early. Move PDI to right after inbound and the delivery schedule becomes more stable, not less.
Does every vehicle need the full checklist?
Grade by risk: new models, high-value vehicles and first batches in a new market get the full list; a homogeneous batch with no defect history can be sampled. Two items are never sampled — document completeness and software configuration, because both fail visibly at handover.
Why is software a separate segment?
Because it is the most frequently missed and the most immediately noticed. Language, maps and calibration are not 'broken car' items but 'car not ready' items, and the customer experiences them as the former. Configure the list per destination market rather than per model — the same model sold into two countries needs two lists.
Where is the line with after-sales repair?
PDI is the gate before handover; repair is the service after it. The PDI record is the dividing line: defects present at handover belong to the earlier stage, failures afterwards fall under warranty. Repair management itself — full work orders, parts consumption, hours costing — belongs to the after-sales line.
What can defect statistics show?
Three conclusions: by position (transport or assembly), by batch (loading or storage), by model (plant or design). Each points at a different counterparty. Averaged together they only produce 'many defects', which is not actionable.
Is the demo data real?
No. Demo environments contain constructed sample data only, with no real customer, vehicle or defect records.
Citation
Suanshu Haiyuan. PDI & Vehicle Delivery Centre. Shanghai Siyang Information Technology Co., Ltd.. https://eficien.com/en/solutions/wai-pdi.html (source list verified 2026-10-17; English edition 2026-10-29).
This page describes how the system carries these stages and fields. It is not legal, tax or customs advice. Rates, categories, deadlines and document requirements follow the competent authority's current rules and must be confirmed by your responsible staff and professional advisers. The Chinese edition lists the official reference entry points; this edition does not restate them, and deliberately gives no numeric conclusions.
8. A five-sheet test
Pull five completed check sheets. Three questions decide whether this line is worth installing.
- Can each item be decided, or would two technicians disagree on the same car?
- Are there photos of the key positions, and do they carry a submission time?
- Does every open defect have a work order and a re-inspection conclusion?
- At which point is document completeness verified today?
- Walk through the defect loop and the initialisation list in the demo environment.
Where does PDI usually get reduced to a signature?
Send five recent check sheets; we will show which items are undecidable and which defects never closed.
Book a 30-minute walkthrough