How does Astra decide which vehicles to load first from plant yard?

Astra scores each vehicle against dealer priority list (paid order allocation weighs higher than stock allocation), carrier capacity for the day, destination route efficiency, and SLA exposure. The plan is dispatch-ready, and dispatchers can override with reason codes that feed back into the model.

Can Shipsy track vehicles moving on rail rakes and coastal vessels, not just road carriers?

Yes. Multi-modal tracking is native. Rail movements integrate with rake-level milestones; coastal and short-sea shipping integrate with vessel schedules and port events. Atlas aggregates all modes into a single vehicle-level view.

How precise are predictive ETAs for vehicles in transit?

Accuracy depends on modality and network density. For domestic road and rail flows with reliable milestone data, 24–48 hour predictive ETAs typically run 90%+ accurate. Accuracy improves as the OEM's data density grows.

Does damage chain-of-custody hold up to warranty claims?

Yes. Photo-linked inspection capture at each yard transition, with timestamp and location metadata, creates an auditable chain. OEMs can pinpoint where damage occurred and settle with the responsible carrier through Nexa and Vera.

Can dealers access this visibility directly?

Yes. Dealers receive a tenant-isolated portal view showing only their own inbound vehicles with live ETAs. Dealer-initiated queries route to Clara for resolution.

Plant-to-dealer finished vehicle logistics: orchestrating FVL across national dealer networks

Finished vehicle logistics is where automotive OEMs lose the most working capital and dealer goodwill — vehicles sitting in plant yards, in transit loops, and at stockyards waiting for paperwork. Shipsy’s TMS for FVL gives OEMs a single control plane from gate-out at the plant to pre-delivery inspection at the dealer, with Astra orchestrating loading plans, Atlas tracking live milestones, and Nexa settling carrier freight automatically.

The FVL challenge in modern automotive networks

A global auto manufacturer with 12+ plants running commercial and passenger vehicle logistics faces three structural frictions:

Yard-to-yard latency. Vehicles roll off production, sit in plant compound, ship to stockyards, transfer to regional yards, then to dealers. Each hop adds days. None of it is reliably visible end-to-end.
Multi-modal carrier complexity. Road carriers, rail operators, coastal shipping, occasional river barge. Each modality runs a different tracking system and a different rate basis.
Dealer-side chaos. Dealers want arrival windows for allocation to customers who’ve already paid deposits. Without predictive ETAs, dealers over-order inventory to hedge, inflating network-wide working capital.

The commercial impact: days-of-supply metrics inflate, dealer NPS erodes, and inventory carrying costs expand. Shipsy TMS for FVL is designed to collapse each of these frictions into a single orchestrated flow.

How Astra and Atlas run plant-to-dealer FVL

Astra — planning. Builds daily loading plans at plant yard: which vehicles load onto which car-carrier / rail rake / coastal vessel, in what sequence, against which dealer priority list. Plans respect carrier capacity, dealer intake windows, route feasibility, and SLA exposure. The output is a dispatch-ready load plan that the yard team executes against.

Atlas — control tower. Tracks every vehicle from gate-out at plant to PDI at dealer. Milestone events — yard out, rail loaded, rake dispatched, destination yard in, dealer tender, dealer in, PDI complete — stream into Atlas continuously. Exception alerts surface when a vehicle is behind SLA at any milestone, routed to the right owner automatically.

Nexa — freight settlement. Matches carrier invoices against rate cards with lane rates, accessorials (detention, route-change, damage claims), and volume bands. The OEM’s freight audit shifts from quarterly sampling to continuous line-level reconciliation.

Clara — dealer CX. When a dealer asks about a specific vehicle, Clara answers from live Atlas data. No dealer relationship manager fielding calls about delivery ETA.

Yard management: the often-overlooked FVL bottleneck

Vehicles in yard aren’t inventory at rest — they’re inventory consuming space, dwell charges, and damage risk. Shipsy’s yard module handles:

Slot assignment by destination routing (pre-sequence for load planning)
Damage inspection capture with photo-linked audit
Carrier booking and gate-in / gate-out events
Dwell-time tracking with alerts on threshold breach
Multi-modal transition (road yard → rail siding → dealer)

The yard becomes a managed node, not a passive holding lot.

Comparative operating model: legacy FVL vs Shipsy-driven FVL

FVL dimension	Legacy ERP + spreadsheets	Shipsy AI-native FVL
Plant yard visibility	Manual clipboard + ERP booking	Gate-in/out events + slot tracking
Load planning	Manual dispatcher assignment	Astra plans against priority + capacity
Multi-modal tracking	Separate systems per mode	Unified Atlas control tower
Dealer ETA	Phone call + guesswork	Predictive ETA from live milestones
Damage chain-of-custody	Paper inspection reports	Photo-linked digital audit
Carrier settlement	Month-end invoice match	Nexa real-time reconciliation
Exception routing	Email to fleet manager	Atlas auto-routes by incident type
Dealer communication	Weekly status call	Clara proactive per-vehicle updates

Dealer experience: why FVL visibility moves dealer NPS

Dealers don’t complain about delivery times per se; they complain about uncertainty. A dealer who knows that VIN 8A7F… arrives Thursday afternoon can allocate to a customer, schedule PDI, and plan floor space. A dealer guessing between “could be Tuesday, could be next week” carries extra hedge inventory, mis-promises customers, and escalates the OEM.

Predictive ETAs from Atlas give dealers a 90%+ accurate window 24–48 hours out on typical domestic flows. That’s enough precision to run dealer-side operations tightly. Over time, network-wide days-of-supply come down because dealers hedge less.

The spare-parts and aftermarket adjacency

FVL doesn’t run in isolation. The same OEM usually also runs aftermarket parts distribution, returnable packaging loops, and inbound supplier logistics on the same platform. Shipsy supports all four as connected flows, with shared master data and shared carrier panels.

See the automotive aftermarket parts distribution guide for the adjacent flow, the automotive industry page for the full capability view, and a Tata Motors commercial vehicle case study for a real-world example of multi-plant automotive logistics running on Shipsy.