Finished Vehicle Logistics Software: Who Pays When the Dealer Finds the Damage

Why finished vehicles break every generic logistics assumption

A dealer signs for a delivery at 7am and notices a scuff on the rear quarter panel of a unit that came off a vessel eleven days earlier. He marks the delivery receipt. That mark starts a process costing somebody between $400 and $3,000, and the only question is who. The stevedore who drove it off the vessel. The compound that parked it in row 42 for nine days. The team who fitted the cargo tray. The car haul driver who chained it down. Or the dealer's own lot porter, a real possibility nobody says out loud.

Every one of those parties handled the vehicle and every one signed something. What they signed was usually a paper listing unit counts, or an electronic receipt with a checkbox saying no visible damage, ticked at 5am in the dark by someone with eighty more units to move. So the chargeback goes to whoever has the weakest documentation, which allocates cost rather than finding truth, and everybody knows it.

This is what makes finished vehicle logistics different from any other freight. A unit is serialised, worth tens of thousands of dollars, cosmetically fragile, and passes through five or six custody changes between the plant and the dealer. The freight is not the cost. The liability is the cost, and a compound handling 60,000 units a year that cannot defend its handovers will absorb damage it did not cause as a permanent line item its own team believes is unavoidable.

Problem 1: the yard does not know where the car is

A 4,000 space compound holds units that arrive in vessel discharge order and leave in dealer allocation order, which are unrelated. A unit is parked wherever there was room, and finding it later means a driver walking rows with a printed list. When a car haul arrives to load nine specific vehicle identification numbers, the difference between a well organised yard and a poor one is an hour of a truck's time per load, every load.

Super Dispatch and Central Dispatch are strong tools for the market they serve, which is over the road auto transport: load matching, dispatch, electronic bills of lading with condition photos. They are carrier facing and load centric, and they do not do yard management because a load board has no concept of a parking slot. Vinturas addresses cross party visibility at network level and Ship.Cars serves carrier operations. None is a compound operating system, because none set out to be.

What a custom build does: give every unit a location that changes through a scan, not through a note. Slot level or zone level depending on your yard discipline, captured on a rugged handheld or a phone, so a picking list for tomorrow's loads can be sequenced by yard walking order rather than by dealer name. The immediate payoff is loading time. The larger payoff is that custody becomes provable, because you know which unit was in which slot on which day, and that becomes evidence later.

Problem 2: the inspection is a signature, not a record

Damage liability is only allocable if condition was recorded at each interchange, and in practice the interchange inspection is compressed to nothing by time pressure. Vessel discharge happens fast, car haul loading happens in the dark, dealer delivery happens while the store is opening. So the condition record becomes a signature on a manifest, which proves a handover happened and nothing about the state of the vehicle when it did.

Electronic bill of lading products do capture photos and are a real improvement over paper. The limitation is that they capture them for a load in a carrier's app, from the carrier's perspective, at the two points that carrier touched. They do not produce a continuous condition history across the whole chain from vessel to dealer, and they do not enforce a consistent capture standard across parties who use different systems or no system.

What a custom build does: define one inspection standard and apply it at every custody change, including the ones inside your own operation that currently have no record at all, such as moving a unit from discharge staging to long term parking. A fixed set of angles, timestamped, geotagged, tied to the vehicle identification number by scan rather than by typing. This is where computer vision earns its place, and only here: a model trained on your own captured images flags a likely new panel difference against the prior inspection, so the inspector is directed to look at the left rear door instead of being asked to compare 24 photos from memory. It does not adjudicate anything. It raises attention. Every damage decision stays with a person, because the money is real and the model is not accountable.

Problem 3: damage codes are a shared language nobody speaks the same way

Damage is recorded as an area, a type and a severity, and the industry has standard code structures for exactly this reason. In practice one compound records a scratch on the left front door one way, the carrier records the same scratch differently, and the manufacturer's claim system expects a third form. The same defect becomes three unrelated records, which is the ambiguity a chargeback dispute lives in.

What a custom build does: hold codes as structured data with a mapping layer per counterparty, so the internal record is consistent and the outbound record matches whatever each manufacturer or carrier requires. Severity thresholds get defined once, in writing, with reference photos, because the argument is almost never about whether a mark exists. It is about whether it counts. A build that ships an agreed severity guide with example images embedded in the inspection screen removes more disputes than any amount of claim workflow.

Problem 4: accessorisation and quality work is a factory nobody planned

Port and compound operations increasingly include real work: fitting accessories, protective film removal, software updates, fuelling, charging electric units, wash and pre delivery inspection. That is light manufacturing inside a parking lot, with parts inventory, labour, sequencing and quality gates, usually managed on a whiteboard.

Load board and carrier systems have no model for this because it is not transport. Warehouse systems have none either, because their unit of work is a pallet and their process is putaway and picking, not a two hour job on a serialised asset in a fixed bay.

What a custom build does: treat accessorisation as work orders against a vehicle identification number, with parts consumption, bay assignment, labour capture and a quality gate before the unit is released to dispatch. The commercial benefit is that you can invoice the manufacturer accurately for work performed, with evidence, which most compounds currently under claim because their records are incomplete. Electric vehicles add a specific requirement worth naming: state of charge tracking and charge scheduling, because a unit that sits at low charge for weeks becomes a warranty conversation and a dead unit that will not move on load day.

Problem 5: the claim arrives without a story attached

Three weeks after delivery, a claim comes in. Someone has to reconstruct where the unit was, who touched it, and what it looked like at each point. If the answer takes a week to assemble across three systems and a paper file, the economically rational decision is to accept the charge, and that is exactly what most operations do most of the time.

What a custom build does: make the claim response a query. Enter the vehicle identification number, get the full custody chain with inspection images at each transfer, yard location history, work orders performed, and the load and driver for each move. Where the evidence shows the damage first appeared between two specific inspections, the responsible party is not a matter of opinion. Operators who put this in place usually find two things: they stop paying for damage they did not cause, and they discover a specific bay, shift or route where damage genuinely originates, which is a fix worth more than the claims.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, this category prices as follows. A focused first release, meaning vehicle identification number level custody with scan based location, a consistent photographic inspection at every handover, and damage records with structured codes, runs $90,000 to $180,000 and ships in 14 to 18 weeks. A full platform adding accessorisation and quality work orders with parts and labour, car haul load planning and driver app, dealer delivery confirmation, claim adjudication with evidence packets, and manufacturer reporting and billing runs $220,000 to $500,000 phased over 8 to 14 months.

What pushes the number up here: the number of manufacturers you serve, because each brings its own damage code structure, reporting format and billing rules. Port operations, which add vessel manifests, discharge sequencing and customs interaction. Electric vehicle handling, which adds charge state monitoring and charging infrastructure scheduling. Image storage and computer vision, since 12 to 20 photographs per handover across tens of thousands of units a year is a real cost that must be designed rather than assumed. And adoption work, if carriers and dealers who are not your employees must use your app.

What holds it down: start inside your own fence. Custody, location and inspection within your compound covers most disputable events and requires nobody else to change how they work.

Build versus buy, said directly

Buy if you are a car haul carrier moving dealer trades and remarketing units. Super Dispatch and Central Dispatch serve that market properly, the electronic bill of lading with photos is solid, and building your own would take two years to reach parity with something that costs a few hundred a month.

Build when two or more of these are true. You operate a compound of more than roughly 1,500 spaces where finding a unit is a daily problem. You absorb damage chargebacks you believe are not yours and cannot prove it. You perform accessorisation work and invoice for it from records you know are incomplete. You serve more than one manufacturer. Or you handle electric vehicles at volume and charge state is already causing delivery failures.

Our position: the industry has good tools for moving vehicles between parties and almost nothing for the compound in the middle, where units spend most of their time and where most disputed damage occurs. That gap is a market the vendors have not found worth serving, and it is where a build creates advantage you can defend commercially with your manufacturer customers.

How to choose a developer for finished vehicle work

Ask them to model custody before anything else. The right shape is a chain of transfers, each with two parties, a timestamp and a condition record, and a vehicle whose current holder is derived from the chain rather than stored as a status. If they propose a status field on a vehicle table, every dispute you have will be unanswerable.

Ask what happens when a photograph is missing. It will be, constantly, because operations happen at 5am in the rain. The system needs a defined behaviour for an incomplete inspection, visible to a supervisor within the hour, rather than silently accepting a gap that surfaces during a claim months later.

Ask about the volume of images. Twenty photos per handover across five handovers and sixty thousand units a year has to be designed for in storage, upload behaviour on poor yard connectivity and retention policy. A developer who has not asked about retention has not built this.

Ask who owns the code and settle it in writing before kickoff. You should hold the repository, the infrastructure accounts and the right to bring in another firm. At Digital Heroes the client owns the code from the first commit, and in this domain you also want unambiguous ownership of the image archive, since it is the evidence base for every claim you will ever defend.