Leakage shows up late.
Stockpiling, misuse and breakage surface at the yearly count, long after they could be recovered.
Q · A
What does Rotion do for a pooling operator?
Rotion gives a pool operator one shared record per asset across every customer, carrier and wash center. It shows where each asset is and who holds it, and flags leakage and stockpiling while it is still recoverable. Settlements rest on scan evidence, and the same scans produce reuse figures for customers and PPWR.
- Runs alongside your existing RTI and ERP systems
- Customer-specific views and reporting
- Neutral: Rotion owns no fleets and competes for no customers
01The problem
Inventory is not control.
Traditional RTI systems show stock per customer. They cannot show how assets behave or where returns slow down, and margins leak there.
Disputes eat the margin.
Balance discussions with customers run on spreadsheets that neither side trusts.
Customers ask for reuse data.
Brands and retailers need rotation and reuse figures for PPWR. Aggregating them by hand does not scale.
02Closed loop
Everyone in the pool, one record.
Each party scans the assets it handles, with a phone or the reader it already has. Custody moves with every scan, so the pool knows who holds what.
- 01Producers
Register new assets as they enter the pool, with the codes already on them.
- 02Fillers
Scan assets in and out per load. Their balance updates with every scan.
- 03Carriers
Confirm pickups and deliveries, so assets in transit have an owner too.
- 04DCs
Book incoming and outgoing loads and see what they hold per asset type.
- 05Retailers
Return empties and see their own balance, not the whole pool.
- 06Wash centers
Log receipts, wash cycles, inspections and repairs per asset.
03Views
Every customer sees its own pool.
You see the whole fleet. Each customer and service partner sees the assets in its own custody and nothing else. Pick a view to compare.
View as
OperatorYour team · every customer and partner
| Party | Holds | Avg dwell | Overdue |
|---|---|---|---|
| Filler 07 | 1,282 | 9 d | 24 |
| Retailer 3 DC | 3,410 | 14 d | 310 |
| Grower 12 | 860 | 6 d | 0 |
| Wash center B | 2,150 | 2 d | 0 |
Filler 07Customer · its own custody
| Party | Holds | Avg dwell | Overdue |
|---|---|---|---|
| Filler 07 | 1,282 | 9 d | 24 |
| Other party | |||
| Other party | |||
| Other party |
Wash center BService partner · its own site
| Party | Holds | Avg dwell | Overdue |
|---|---|---|---|
| Other party | |||
| Other party | |||
| Other party | |||
| Wash center B | 2,150 | 2 d | 0 |
Sample data · Each customer logs in to its own view. Access is set per customer and per role.
04Settlement
A quarter closed on evidence.
Every line on a customer statement points to the scans behind it. When a customer questions a number, you both open the same record.
Settlement statementFiller 07 · Q3 2026 · crates
Sample data- Opening balance, 1 July1,180Closing balance of Q2Agreed
- Issued to Filler 07+4,32052 issue scans, one per loadAgreed
- Returned to Wash center B−4,18261 receipt scans at the wash centerAgreed
- Return of 2 August24Filler 07 counts 120, the wash center scanned 96Questioned
- Lost, attributed to Filler 07−36No scan for 90 days, last seen at Filler 07Agreed
- Closing balance, 30 September1,282Includes the 24 crates in question
Deposit on attributed losses: 36 × € 4.00 = € 144.00
Field results from operators running Rotion across pools, retail and industry.
28%
S.01fewer assets lost
9%
S.02smaller fleet needed
575,310
S.03assets tracked
Trusted by these organizations.
05How it works
Every handover on one record.
Customers, carriers and wash centers scan with any phone or reader. Each scan moves custody, so the pool always knows who holds what.
- 01
Issue
Assets leave your depot to a customer. One batch scan per load.
- 02
In circulation
Customers fill, ship and pass assets on. Custody follows every handover.
- 03
Return and wash
Returns, washes, inspections and repairs log per asset.
- 04
Settle and report
Balances, deposits and reuse figures per customer, from the same scans.
06Platform
Built for multi-customer fleets.
Fleet intelligence
Location, rotation and utilization across customers and regions.
Read more
Leakage and anomaly detection
Autopilot flags stockpiling, breakage and slow returns per customer before they hit margins.
Read moreRotation per customer
Cycle time, dwell and turns per customer, so a slow loop shows before it needs more assets.
Read more
Next to your current systems
Connectors for ERP, WMS and TMS keep orders, customers and scans in step with the systems you already run.
Read more07Autopilot
It notices first.
Autopilot watches every scan in your loop, flags what is going wrong, proposes the fix with its reasoning, and acts once you approve.
How Autopilot worksRetailer 3 DC holds 1,140 more pallet boxes than its 90-day average.
Why
Returns from Retailer 3 DC dropped 18% since week 36 while issues stayed flat. The pattern matches stockpiling before a peak.
Proposes
Send the customer a balance statement and propose a collection slot.
ApproveEditconfidence 92%
Leakage caught this quarter3.4%
Sample data08Migration
Start next to your RTI system.
Rotion runs alongside the system you have. Start with one customer group or region and widen the scope when the numbers hold.
- 01
Use the codes you have
Rotion reads the QR, barcode, RFID or GS1 GRAI codes already on your assets. Nothing is relabeled.
- 02
Pick one customer group
Start with one customer group or region. Opening balances come from your current records.
- 03
Run both side by side
Compare the balances in Rotion with your current system for a few cycles, until they match or every gap is explained.
- 04
Widen the scope
Add customers and regions when you are ready. Your current system can keep the work it already does well.
The assets pools run on Rotion.
Q.01Do we need to replace our RTI or asset management system?
No. Rotion runs alongside existing systems and adds what they lack: asset-level behavior, leakage detection, reuse figures and visibility across parties.
Q.02Will customers see each other’s data?
No. Access is set per customer and per role. You decide what each customer sees and what you share with brands or regulators.
Q.03Can Rotion handle customers with different requirements?
Yes. Rotion is built for multi-customer, multi-loop operations where reporting, integrations and visibility differ per customer.
Q.04How does this help commercially?
Better utilization improves asset ROI, settlements stop leaking margin, and customer-facing reporting becomes a service you can charge for.
Q.05Does Rotion help with PPWR?
Yes. Rotion produces reuse rates and cycle counts from asset-level scans. PPWR calculation rules apply from 30 June 2027 and reuse targets from 2030. See the PPWR Navigator for deadlines.
Q.06How is this different from a traditional RTI system?
A traditional RTI system books stock and transactions per customer. Rotion keeps a record per asset, so it shows dwell, rotation, losses and reuse per customer, and Autopilot acts on them. You can keep your RTI system and run Rotion next to it.
Q.07Do we have to relabel our fleet?
No. Rotion reads the codes already on your assets: QR, barcode, RFID or GS1 GRAI. You start with one customer group or region and add the rest when you are ready.
