A master order ledger should be established for multi-dealership deliveries: the group contract stipulates commercial conditions, and each delivery point receives its own vehicle and documents by VIN. Any changes in configuration, receiving entity or delivery location must be written back to the master ledger and leave an approval record.
The standardized definition and reuse of cross-border data described in WCO Data Model provides management reference for this article. When actually used in Chile, transaction documents and local professional opinions must be combined.
Fixed configuration fields with Toyota Avalon full version name
Taking Toyota Avalon 2026 2.0L Luxury Edition as an example of table creation, the main order and each dealership sub-table should retain the complete version name, and cannot just write "Avalon" or "2.0L". This allows the quotation version, VIN allocation and vehicle documentation to be checked in the same record.
This example only illustrates how to control the vehicle model identity, and does not mean that this version has met Chilean access or group customer requirements. After entering the actual order, you still need to check the vehicle parameter table, invoice, shipment documents and local procedures according to VIN.
Group contracts and vehicle-by-vehicle delivery must use the same set of identifiers
Order numbers are easily split during group headquarters negotiations, subsidiary payments, and vehicle handovers at different dealerships. The total price may still be consistent, but the specific vehicle is duplicated, the invoice body does not match, or the attachment version is used incorrectly. The main order number, sub-order number, VIN and receiving entity need to be traceable to each other.
How to verify four tables with each other
| Process location | Archive content | Control objectives |
|---|---|---|
| Master order | Business conditions and total scope | Group purchasing approver |
| Vehicle allocation table | VIN, Configuration and Delivery Point | Vehicles cannot be reoccupied |
| Document list | Invoices, shipments and delivery documents | The main body is consistent with the VIN |
| Dealership receipt form | Actual vehicle, keys and missing parts | Exception returns to main order |
VIN is the key to connect the form, not a free field.
ISO 3779:2009 stipulates the content and structure of vehicle identification numbers and will be confirmed in 2024. When actually building a table, the group order number can change due to the purchaser's internal management, but the VIN should remain consistent character by character from acceptance, distribution, invoicing to delivery. If the system allows the dealership to manually rewrite the VIN, the original value, modifier, reason, and secondary review results should be retained.
Cross-border documents will also be reused among different parties. The core value of WCO Data Model is to unify data definition and electronic messages. Corresponding to multi-dealership delivery, it is recommended to set the vehicle model description, quantity, buyer's name and VIN as controlled fields, and put the dealership remarks in the uncontrolled area. When a controlled field changes, the system should prompt all affected files and cannot just update the last table.
Changes come from one entrance
When the dealership temporarily changes vehicles, the group adjusts the recipient, or a certain vehicle is delayed, it is not appropriate to directly modify the local table. Submit change orders uniformly, specifying the old value, new value, reason, impact document and approver, and then synchronize them to each delivery point.
In order for key account delivery managers to track conclusions, it is recommended to retain:
- Mapping of main orders and sub-orders
- VIN configuration snapshot
- Version and recipient of each document
- Dealership vehicle handover exception record
- Change approval and write-back results
If the three fields do not match, the release of the vehicle will be suspended.
If any of the VIN, recipient or delivery location is inconsistent with the approved allocation table, the vehicle will first enter the pending confirmation state. On-site personnel only record differences and do not replace vehicles or reopen business documents themselves.
Create an auditable quotation-VIN-document record
| Project | Suggestions in this article |
|---|---|
| Fields to record | Quotation version, contract item, VIN, complete vehicle model, color, invoice number, delivery order number, exception number |
| Decision rules | Changes to any field generate a new version and reference the old record, without overwriting the original quotation or VIN assignment. |
| Output | A secondary reviewer can follow a single line of records to the contract, vehicle and final delivery documents. |
FAQ
Can a group only use one order number?
The group master order number can be retained, but each delivery point must still have a sub-record that can be located and associated with the VIN one by one.
How to deal with temporary vehicle swaps at dealerships?
Initiate allocation changes first, and then update the affected documents and receipt forms; Oral consent is not sufficient to close the record.
What information is appropriate for all dealerships to see?
Just share vehicle status and delivery tasks. Price authority, payment information and personal information should be controlled by position.
First do a cross-check with the allocation table
After organizing the main order fields, VIN list and dealership receipt template, you can check whether the three files can locate each other through Starvia Contact Page.
You can check the vehicle model entry from Starvia New Vehicle Catalog, and use FAQ to understand the general document process. Specific inquiries should be accompanied by the order version, VIN list, recipient and delivery dealership.
This article explains a document-review method for the vehicle and transaction scenario described for chile. It does not determine local import eligibility, customs, tax, registration or technical outcomes, or guarantee a vehicle's price, availability, delivery or warranty. Each transaction depends on current official requirements, the contract, VIN-specific records, the vehicle's actual condition and confirmation by the competent local party. No conclusion should be inferred for vehicle variants, destination markets or transaction terms not stated here. Review date: 2026-09-24.