After a voyage change, first separate the facts from the notification process. The carrier or agent reports a voyage adjustment; the required action is to identify its impact on specific orders and notify customers. If these two activities are not coordinated, subsequent records will be difficult to trace.
Local records in Paraguay need to identify the vessel or voyage involved, which orders are affected, what customers already know, and which party has yet to confirm details.
Identify Affected Orders by Vessel, Voyage, and VIN First
When voyage change information arrives, first check the vessel name or transport identifier, original voyage plan, update source, and vehicles involved. Then determine the scope of the impact. If only some orders are affected, separate them by VIN and process each order individually instead of replacing vehicle-by-vehicle confirmation with a batch notice.
After separating the orders, place each order's original and new plans side by side. If the vessel name or time in the new notice differs from the original record, return it to the carrier for confirmation instead of making assumptions based on the old record.
Who keeps records on voyage changes
The logistics coordinator records the voyage change notice and affected order list, the document handover coordinator checks whether the original voyage plan can be traced to the booking version, and the arrival arrangements lead confirms the customer notification record before releasing the related arrangements. Each role signs off separately on the information it verified.
| What to check | When you can proceed | When you must pause | Who is responsible |
|---|---|---|---|
| Voyage change notice | The notice is traceable to the carrier or agent and states the vessel name and voyage | Return for supporting evidence if it is unclear what the notice applies to | Logistics coordinator |
| Original voyage plan record | The record is traceable to the original booking or contract | Do not determine the scope of the change if the original plan cannot be found | Document handover coordinator |
| Affected order list | The list identifies each item by VIN or order | Do not include orders outside the list in customer notifications | Logistics coordinator |
| Customer notification record | The record matches the affected order list | Keep open while customer items awaiting confirmation remain unresolved | Arrival arrangements lead |
The hold points in the table control the scope of notifications. When a status changes from pending verification to notified, it must be traceable to the change notice, affected order list, and sending time.
Explain in three parts and attach to the record
Explain voyage changes to customers in three parts: confirmed changes, details still awaiting confirmation from the carrier or agent, and when the next results will be provided. Do not present unconfirmed information as definite. Before sending the notice, check each order against the affected order list. Orders outside that list must not be processed under this voyage change.
Append customer inquiries and responses to the original order record, retaining successive versions. When a new notice supersedes an earlier time, note which notice it replaces, and update the notification record and affected order list together.
Handover and Rechecking of Voyage Change Handling
During the recheck, compare the affected order list, customer notification record, and carrier confirmation together. Close the case only when all three match the same order. For customers whose confirmations are still pending, continue to identify the receiving role and follow-up time.
For the next batch of orders, reuse the approach to voyage change notifications and the record fields, but not this batch's customer conclusions. Check new orders again using their own vessel names, voyages, and VINs.
FAQ
How should customers be notified if only some vehicles are affected by a voyage change?
Notify customers order by order using the affected order list. State the vessel name, voyage, and new time for affected vehicles, and explain unaffected vehicles separately. Do not treat orders outside the list as affected. Avoid one vague notice for the entire batch; file each vehicle's results together with the original notice.
Can we pass along a carrier's one-line message saying “the voyage has changed”?
No. First ask the carrier or agent to provide the vessel name, voyage, and update source, then separate affected orders by VIN. Return notices that do not identify what they apply to. Keep unconfirmed information out of customer explanations, and send the notice only after checking the supplementary materials.
How should we respond if a customer asks for the new arrival time but the agent has not confirmed it?
Respond in three parts: the confirmed voyage change, the timing still awaiting the agent's confirmation, and when the next results will be provided. Also identify the role responsible for updates. Do not include a time the agent has not confirmed, to avoid presenting a pending detail as a definite result.
How can we avoid confusion if the voyage changes again after the notice is sent?
Append the second change to the original record for the same order, retain the first notice, and note which version supersedes it. Recheck the affected list by VIN before sending the new explanation. Do not create a separate, unlinked record.
Whenever a Paraguayan order raises questions on voyage change customer notices, submit the vehicle or order identifier, existing materials, and questions awaiting confirmation through the Starvia contact page or WhatsApp. Then use this article's table to check the available vehicle sourcing and export materials item by item. References: Paraguay DINATRAN official services portal; Starvia purchasing FAQ. This article provides order recordkeeping and communication methods for international logistics in Paraguay. It does not constitute local legal, tax, customs clearance, or technical conclusions, nor does it guarantee import eligibility, delivery timelines, warranties, selling prices, or business results. Materials checked on: 2026-09-07.