Industry · Automotive

The Line Stops for Want of a Rack, Not a Part.

And the rack is the one asset that crosses the fence between two companies — owned by one, sitting most of its life inside the other, with the cost of its disappearance landing on whoever wasn't holding it.

Get a Demo Explore 26 use cases
One rack, two companies, one read
The dock read

The Gap Between Two Gatehouses Stops Existing

While each side counts what it can see, the two numbers never reconcile — and the difference becomes a commercial meeting instead of an operational correction. A read at the dock door records the movement as a single event, not as two independent notes someone has to reconcile later.

The same fact for both sides
One event, read once, at the moment the load crosses. Not two counts that never match.
The event reaches the ERP
Dock verification feeds the corporate system, so physical movement and corporate record stop telling different stories.
The trail has a map
Chain of custody from dispatch to return on one screen, with the route travelled — not just a table of events.

In practice: 200,000 pallets verified at the dock with bidirectional ERP integration, 40,000 returnable containers tracked with two dock portals, and 30,000+ assets updated daily across four process stages.

The cycle between two companies

Four Moments, and Two of Them Aren't Yours

The device spends half its life inside another company's plant. The solutions below follow the order of the cycle — and the first two cover exactly the stretch where control usually ends.

01
The Fleet That Lives Elsewhere
How many devices do you have, and how many are where they should be?
Returnable Transport ItemsRacks, totes and containers as a circulating fleet, not an expense line.Explore → Assets Held by CustomersAgeing, pending return and exposure by partner.Explore → Loss PreventionMisplacement and misuse are different problems and need different answers.Explore →
02
The Passage Through the Dock
The one moment both sides can agree on the same fact.
Yard ManagementGatehouse, scheduling and dock — the queue starts before the truck arrives.Explore → Receiving and ShippingVerification on the move, with the discrepancy surfacing at the dock.Explore → IdentificationA tag that survives washing, impact and years of cycling.Explore →
03
What Happens Inside
Between receiving and shipping, the order has to advance on its own.
WIP Production ControlA read in the zone closes one stage and opens the next, with no manual reporting.Explore → Real-Time LocationWhere the moving things are: device, subassembly, trolley.Explore → Parts and StoreroomAn incomplete kit is the most common reason an order stalls for no visible reason.Explore →
04
What Has to Be Right
Measurement and maintenance hold up everything above.
Calibration and MetrologyTorque wrench and instrument with a valid certificate on the day they measured.Explore → Maintenance ManagementWork orders, plans and parts for both the production fleet and the devices.Explore → Inspections and ChecklistsVerification with structured data and attached evidence, not a written account.Explore →
Why one platform

Two Counts Never Reconcile. One Event Does.

While each company logs the same passage in its own system, the difference is inevitable — and it turns into a commercial meeting rather than an operational correction. An event read at the dock is the same fact for both sides, and from there the conversation stops being about who is right.

01
The same fact for both sides
The dock read records the passage as a single event, not as two independent counts that never reconcile.
02
The event reaches the corporate system
Verification feeds the ERP, so physical movement and corporate record stop telling different stories.
03
The trail has a map
Chain of custody from dispatch to return with the route travelled — not a table of events nobody accepts as proof.
04
The order advances without manual reporting
Inside the plant, a read in the zone closes the stage and opens the next — with planned against actual by process.
05
The instrument was valid
Torque wrench and measuring instrument with a verifiable certificate on the date they measured — not merely registered.

What this platform does not do

We do not address the automotive quality management standards. The sector's quality management system standard, the reference manuals for part approval and advanced quality planning, and the structured problem-solving methods are not part of this offering. In an industry where that certification is a condition of supply and not a differentiator, saying so is an obligation — and better heard from us than discovered in a supplier audit.

We do not do electronic data interchange with the supply chain. Advance shipping notices, delivery instructions and release schedules in the formats the OEMs require are a different class of system. The platform sends events to your ERP by API and webhook; what the ERP does with the chain stays with it.

We are not a lean manufacturing system. We do not do production sequencing, card-based scheduling or synchronised replenishment calculation. What we do is record physical movement and stage advance — the data those disciplines consume, not the disciplines themselves.

What the platform does and does not do is set out in the trust center.

Start here

Ask for the Number From Both Sides

Pick one returnable device model and ask your supplier how many they believe are with you. Then look at how many you believe you have. The difference between those two numbers is the fleet nobody is counting — and it is usually large enough to pay for the project before any process improvement at all.

Request a Demo Calculate the return
Frequently asked

Automotive Industry — Common Questions

We start with three that need answering before any demo — and the first is the one that matters most in this chain.

Do you meet the automotive quality standard?
No. The sector's quality management system standard, the part-approval and advanced-planning reference manuals, and the structured problem-solving methods are not part of this offering. In an industry where that certification is a condition of supply, saying so is an obligation — better heard now than in a supplier audit.
Do you do EDI with the OEMs?
No. Advance shipping notices, delivery instructions and release schedules in OEM formats are a different class of system. The platform sends events to your ERP by API and webhook; the conversation with the chain stays with it.
Does this do sequencing, kanban or synchronised replenishment?
No. We do not do production sequencing, card-based scheduling or replenishment calculation. We record physical movement and stage advance — the data those disciplines consume, not the disciplines themselves. Whoever schedules keeps scheduling, with better data.
Why are returnable containers the central problem here?
Because they are the only asset that crosses the fence: owned by one company, spending most of their time inside another, with the cost of disappearance landing on whoever wasn't holding them. Each side counts the stretch it can see, the numbers never match, and the difference gets absorbed as relationship wear rather than treated as loss.
How do the two sides come to agree?
Through the read at the dock door, which records the passage as a single event rather than two independent notes. That event feeds the ERP, so physical movement and corporate record stop telling different stories. See returnable transport item tracking.
What if the supplier says they returned it?
The custody trail shows the chain from dispatch to return on one screen, with the route travelled rather than just a table of events. It is operational evidence and usually ends the discussion. ⚠️ It is not a forensic report.
What changes inside the plant?
The order advances without manual reporting: a read in the zone closes the active stage and opens the next, recording planned against actual by process. It lets you say which stage overran, not merely that the order was late. See WIP production control.
How is this page different from manufacturing?
The manufacturing pages organise around the part's journey inside the plant. This one organises around the device's cycle between two companies — the only one of our industrial segments whose subject crosses the fence. Many operations need both readings.
Where should we start?
With one device model and a pair of plants. Instrumenting the whole fleet at once is the most common start and the slowest, and a single model already produces the number nobody has today: how many went out, how many came back and how long they took. Everything else is negotiated from there — including with the partner.

See the full module set in platform modules, the technical detail in RFID in manufacturing, and the delivered projects in case studies.

error: Content is protected !!