Colombian fleet buyers can first use pilot vehicles to verify handover and operating conditions, agreeing in advance on pause conditions. Before committing funding, after-sales staffing and subsequent orders, confirm whether port-arrival documents, actual vehicle identity, operational handover and issue records can all be attributed to the same vehicle. A reorder review should not rely solely on trial feedback or a single department's decision; it should answer a specific question: is the existing evidence sufficient to support taking on procurement and support responsibilities for the next batch of vehicles?
The official Colombia DIAN customs procedures portal can be used to check the importing entity, customs procedures and declaration responsibilities. Actual transactions should still be reviewed against current system information and local professional advice. For technical materials, the United Nations Economic Commission for Europe vehicle regulations can help procurement teams understand the vehicle technical rules framework; that framework does not mean Colombia has approved a specific model or version.
First Divide the Reorder Decision into Four Risk Categories
A pilot vehicle's ability to start, be handed over or operate briefly on site cannot alone justify a reorder. The procurement manager can divide the discussion into four categories to prevent positive information held by one department from being generalized into a conclusion about the entire transaction.
The first category is identity risk. Whether the purchase order, vehicle identification information, shipping records, acceptance records and after-sales repair orders refer to the same physical vehicle determines whether later disputes can be traced. The second is document risk. The declaring entity, responsibility boundaries and versions of received documents need to remain reviewable and be recorded separately from checks of DIAN-related procedures. The third is operational risk. Pending matters arising during actual fleet use must distinguish pre-handover leftovers, on-site findings and feedback after use. The fourth is support risk. Parts, repair bays, customer-service intake and procurement payment milestones need clear ownership and handover timing; they cannot be left to be documented after the reorder is placed.
This division allows the team to pause the relevant step and continue obtaining evidence when an item remains unmet, without turning the pilot into an all-or-nothing judgment. Stop/go conditions are management boundaries, not predictions about vehicles or import outcomes.
Replace Verbal Reports with Per-Vehicle Logs
Each pilot vehicle should have its own log, with one fixed reference number running through procurement, logistics, workshop and fleet-use records. The log should record what each document proves, who checked it and who handles discrepancies.
For example, procurement retains confirmation sheets for version comparisons and payment conditions; vehicle acceptance staff record identification information, exterior condition and accompanying documents; the fleet manager logs use scenarios, pending matters and withdrawal-from-service decisions by date; and the after-sales lead records intake time, initial classification, required materials and the next contact. If the BYD Sealion 06 EV enters the fleet shortlist, first confirm the specific VIN available for testing, then register that vehicle's charging, shifts and withdrawal-from-service records. A version name on a webpage is neither Colombian operating authorization nor a substitute for this test's results or supply confirmation.
The log should allow unresolved items. Clearly recording them supports procurement decisions better than covering problems with generalized conclusions. Each unresolved item should state at least when it was found, where the evidence is located, its scope of impact, interim action and the trigger for another review.
Set Stop/Go Conditions with a Decision Tree
The following table can be completed item by item during weekly pilot reviews. It does not replace contracts, professional advice or requirements of the relevant authority's system; its purpose is to shift reorder discussions from impressions to verifiable evidence.
| Review branch | Evidence to check | When progress can continue | When to pause the reorder review |
|---|---|---|---|
| Vehicle identity | VIN, actual vehicle photographs, acceptance records and procurement version records | Records correspond, and differences have been noted and rechecked | Information cannot be matched, or the source of differences remains unclear |
| Import responsibility | Importing entity records, declaration-related records and responsible-person confirmation | Responsibility boundaries and pending tasks have written ownership | Declaration responsibilities or document versions have gaps |
| Pilot operation records | Use logs, exception classifications, withdrawal and return-to-service records | Exceptions are graded, with a clear review route and responsible person | Similar exceptions recur and evidence is insufficient to assess their scope |
| After-sales support | Repair-order intake point, parts list and workshop contacts | Intake method, escalation route and record location are confirmed | No clear receiving party exists on site, or issues cannot be traced |
| Procurement pace | Pilot conclusions, payment terms and the next batch's document checklist | Unresolved items do not affect the current review scope and have scheduled review deadlines | Unresolved items affect vehicle identity, responsibilities or delivery boundaries |
Continuing progress in the table is not a release approval. It means only that, within the established procurement scope, the team has the materials needed to continue to the next review. Any issue involving import declarations or locally applicable requirements must still be confirmed separately under DIAN's current procedures and local professional advice.
Let Payment Arrangements Follow Evidence Readiness
Staged payments align commercial commitments with document readiness. During contract negotiations, buyers can link each milestone to a deliverable and verifiable document or actual vehicle status, such as complete version records, accepted vehicle identity, submitted pilot-operation records, or written arrangements for unresolved matters. The focus is agreeing on verification actions and a dispute-handling entry point, not turning payment milestones into promises about customs clearance, registration or operating performance.
A first trial shipment also needs boundaries. The fleet can first establish the number of pilot vehicles, observation scope, review frequency and stop conditions before discussing reorder size. If document comparisons reveal discrepancies, procurement should first freeze the affected assessments, retain on-site records, and enter the person and timing responsible for supplementary materials into the log. This prevents subsequent orders from carrying forward unconfirmed versions, attachments or responsibility descriptions.
The Proper Place of Technical Records in the Review
The UNECE page is an entry point for understanding the vehicle technical rules framework. The United Nations Economic Commission for Europe vehicle regulations do not constitute approval of a pilot vehicle, version or configuration by Colombian authorities. Technical records therefore serve three appropriate purposes during a pilot: version comparison materials, a common language for issue descriptions, and an index of matters needing separate verification.
Procurement can ask suppliers to submit document versions, acquisition dates and corresponding vehicle identification information together. Workshop findings should also avoid vague descriptions and instead note the conditions of occurrence, visible symptoms, on-site documents and whether continued use is affected. These records do not assign responsibility in advance or replace diagnosis; they help subsequent participants examine the same factual basis.
What Should a Reorder Review Meeting Produce?
An effective review need not resolve every issue, but should produce clear outputs: which vehicles move into the next commercial discussion, which matters remain under verification, which risks require reordering to stop, and who will resubmit materials. Conclusions should be divided into continued observation, limited-scope progress and paused review, each with evidence references and review dates.
When the team chooses limited-scope progress, document the limits, such as continuing document checks only, retaining procurement quotation discussions only, or arranging after-sales resources only. This prevents sales, finance and operations from interpreting limited progress as default confirmation of the next order. A pilot's value comes from a learning process that can be revisited, not from a one-off meeting conclusion.
FAQ
If a pilot vehicle has no issues over a short period, can we directly submit a reorder request?
That alone is not a complete basis. Also check vehicle identity, import responsibility records, pilot-operation records and after-sales support arrangements, and record how unresolved matters affect procurement of the next batch.
What should the fleet do first if a version discrepancy appears between the VIN and procurement records?
Pause reorder assessments affected by that discrepancy, retain records linking the actual vehicle and documents, and ask the responsible parties for verifiable explanations. Until the difference is clarified, do not extend conclusions about that vehicle to other vehicles.
What is the DIAN official portal used for in a pilot vehicle project?
It serves as an official reference for confirming the importing entity, customs procedures and declaration responsibilities. Specific declaration operations and transaction arrangements still need review against current system information and local professional advice.
How should a pilot-operation report be written for joint use by procurement and after-sales?
Organize the report around the individual vehicle reference number, listing use scenarios, findings, evidence locations, interim actions, responsible people and review status separately. Avoid reporting only overall satisfaction or a single conclusion.
If you are arranging pilot vehicles and subsequent procurement reviews for a Colombian fleet, submit your existing logs and document scope through the Starvia contact page, or use WhatsApp to discuss handover items suitable for the verification checklist.
Public sources: Colombia DIAN customs procedures; United Nations Economic Commission for Europe vehicle regulations. Information checked on: 2026-09-03.