FAQ
Not catalogue copy — short, practical answers on quote, mode choice and coordination.
Topics
QTE / Quote & planning
A quote is not a price list — it is cargo, lane and time window read at the same table.
Minimum set: cargo type, estimated weight/volume, origin and destination, target delivery window and preferred transport mode. ADR, cold chain or oversized cargo should be stated at planning start — not at transfer.
On a standard road or sea lane, with complete information the first operations plan is usually readable within the same business day. Project cargo, multimodal routes or permit-heavy lanes depend on site survey and carrier capacity — no fixed SLA is promised.
Transit is not map distance — it is loading window, border/port cut-off, transfer slot and delivery dock combined. The plan is read backwards: delivery hour locks, then port cut-off and plant departure follow.
MOD / Transport modes
Mode label is not chosen from a catalogue; volume, time, risk and delivery window are read together.
FTL assigns the full vehicle to one shipment — preferred when delivery window is tight, border crossing matters or transfer risk is not acceptable. LTL shares volume; it can balance cost when flexible departure and consolidation are acceptable. Read delivery window and transfer risk before tonnage.
FCL assigns the container to one shipment — when volume is sufficient, port cut-off and arrival flexibility read more clearly. LCL requires consolidation; it works for low-volume regular shipments. Port cut-off, merge day and arrival window matter as much as volume in the choice.
Intermodal can balance cost and time on lanes where sea, rail and road legs lock on one plan. It is not right for every cargo — short road or direct sea may be clearer. Transfer points should be planned as slot and window.
OPS / Operations & coordination
Visibility is not a tracking screen — it is information where decisions happen at transfer.
A location pin is not enough. Visibility is plan, booking, transfer status and exception information staying in one operations file. Data from carrier, terminal and warehouse partners is read in one language — the client is informed before a break.
VELTRON coordinates carrier, port agent, customs broker and warehouse partner in one operational language. It does not replace official customs or regulatory authorities; it manages document and communication lines as part of the plan. It is not a fleet or terminal owner.
Dock suitability, stacking limits, loading equipment and delivery type should be read at planning. Loading is not the moment paperwork chases — it is the step where the plan reaches the field. Last-mile delivery conditions are defined before the destination address alone.
SPC / Warehouse, project & support
Warehouse, project cargo and insurance coordination continue the transport plan — not a separate catalogue.
Warehouse is not the end of the route — it is the layer where wave plan, pick rhythm and outbound hour align with the transport calendar. Stock visibility is read as part of the shipment plan — warehouse and road/sea legs are not watched on separate phone lines.
For oversized or heavy cargo, booking alone is not enough. Site survey, route permits, specialist trailer/crane booking and port operation move in one project file. Project freight is read differently from a standard shipment calendar.
VELTRON is not a cargo insurance provider or broker; it includes insurance coordination in the operations plan based on cargo value, transport mode and route risk. Policy scope, coverage limits and claims process are set by insurance parties — VELTRON makes no legal guarantee.
Quote
If the answer is not enough, share your transport request — we read the operation need together.
