Tote and RPC tracking software
Tote and RPC tracking software for fresh produce and retail loops: serialized identity, SSCC batching, per-partner balances, and loss recovery with Rotion.
Last updated: 29 September 2026
Rotion is tracking software for totes and reusable plastic containers (RPCs): each container gets a scannable identity, per item or per batch, and every issue, return, and wash is logged across suppliers, distribution centers, and stores. Leaking loops show up immediately, balances reconcile per partner, and the labels already on your containers keep working.
What are totes and RPCs, and where do they circulate?
Totes and reusable plastic containers (RPCs) are stackable returnable containers that move goods in repeating loops: fresh produce from growers to retail, dairy and bakery distribution, store replenishment from distribution centers, and e-commerce fulfillment. In EU terminology they are returnable transport items (RTIs); the operational problem is the same everywhere.
A tote fleet is a working asset pool, not packaging that disappears at the customer. It only pays off when containers keep rotating, which makes visibility over the loop the core management task.
Why do totes go missing in retailer and supplier loops?
Totes leak because nobody in the loop is accountable for individual containers. Stores stack them in back rooms, suppliers hold them as free storage, carriers mix fleets, and counts at handover disagree. Without per-container records, loss is discovered at inventory time, long after anyone can say where it happened.
Tracking changes the failure mode. Each tote carries a named holder and a last confirmed location, leaks surface in the data as they form, and getting containers back becomes a standard follow-up rather than a replacement order. Rotion is scan-based accountability: location means the last confirmed scan and the responsible party, not a live sensor feed.
Put a number on it: estimate what tote loss costs your fleet per year.
What does asset loss cost you per year?
Assets lost per year
800
Annual replacement spend
€9,600
Capital in the fleet
€120,000
Your numbers, not ours: the calculation is fleet size × loss rate × replacement cost.
Should you track RPCs per batch or per serial?
Both are valid, and Rotion assigns identity at container level or at batch level. Give containers their own serials where deposit value, condition history, or reporting needs demand per-container evidence; run batches where containers are interchangeable and partners think in counts. The tradeoffs are covered in asset-level vs balance-level tracking.
Moving an asset type from balances to serials later is a data change, not a system migration, so most fleets start simple and serialize the flows that hurt.
Does tracking mean scanning every single tote?
No. With SSCC grouping, a loaded pallet or cage of totes registers with one scan at each shared checkpoint, and the individual record of every tote inside keeps building. Scanning effort concentrates where it matters: at issue, at return, and at the wash. The mechanics are covered in SSCC batching.
How do balances, wash cycles, and existing labels fit in?
Rotion keeps a balance per partner, per store, and per site, reconciled from scans instead of spreadsheets. Wash and wear counters accumulate per container as hygiene and condition evidence for food loops. And Rotion is hardware-agnostic: QR, barcode, and RFID all work, alone or mixed, and codes already on the containers keep working wherever they can be mapped in.
| Tote and RPC loop pain point | What tracking changes |
|---|---|
| Totes vanish into store back rooms | Named holder per tote; sitting stock shows up immediately |
| Handover counts disagree | A shared scan record replaces spreadsheets that disagree |
| Loss found only at the annual count | Dwell-time anomalies flag leaking loops as they form |
| Hygiene questions in food distribution | Wash cycles logged per container |
| No proof of reuse for reporting | Logged rotations per container and per flow; see reuse reporting and compliance |
| Relabeling cost blocks the project | Codes already on the containers keep working |
Do stores and suppliers need to install anything?
No. Stores and suppliers confirm handovers in the browser or on a phone, and your drivers can record scans for stores that do nothing at all, so the loop works without every store on board. Rotion sits next to your WMS and ERP and adds what they miss: the history of each tote, where losses concentrate, and what each partner currently holds. Plans by fleet size are on plans and features.
Trace your tote loop
Reusable packaging reporting under US state EPR laws
How to report reusable packaging under US state EPR laws like California SB 54: which states apply, why reuse is favored, and the records that prove it.
How Rotion integrates with your systems
Rotion runs alongside ERP, WMS, and transport systems like SAP and Odoo, and works with phones, existing scanners, and QR, barcode, or RFID labels.