Asset-level vs balance-level tracking
Balance-level tracking keeps per-partner exchange balances; asset-level tracking keeps serialized per-item history. Rotion runs both in one system.
Last updated: 29 September 2026
Balance-level tracking keeps a running exchange balance per partner, while asset-level tracking gives every item a serialized identity and its own history. Rotion runs both models in the same system, so a fleet can manage exchange pallets by balance and serialized crates, kegs, or IBC totes by individual passport at the same time.
What is balance-level tracking?
Balance-level tracking records how many assets each partner owes or holds, without identifying individual items. It is the classic model for exchange flows such as EPAL exchange pallets: a delivery of loaded pallets against empty pallets returned, netted into a per-partner balance.
Rotion keeps these balances per partner and per location, so disputes are settled from a shared ledger instead of two spreadsheets that disagree. Balance-level tracking answers "who owes us how many", which is often exactly the right question for interchangeable, low-value returnable transport items (RTIs).
What is asset-level tracking?
Asset-level tracking gives each asset a serialized identity and records its complete history: every issue, handover, return, wash, and repair. In Rotion, that record is the digital packaging passport, and it answers "which asset is where, in what condition, and who handled it".
Asset-level tracking is what makes loss attributable, deposits enforceable, and condition history auditable. It fits returnable containers, reusable plastic containers (RPCs), kegs, dunnage, and any asset whose value or deposit justifies per-item identity. Identification options are covered in asset identification.
How do the two models compare?
Balance-level tracking is lighter to operate and fits interchangeable assets; asset-level tracking carries more information and fits assets worth following individually. Rotion treats them as two views of the same operation, not two products.
| Balance-level | Asset-level | |
|---|---|---|
| Unit of record | Per-partner exchange balance | Serialized individual asset |
| Typical assets | EPAL exchange pallets, uniform crates | Kegs, IBC totes, deposit trays, dunnage racks |
| Question answered | Who owes how many | Which asset is where, and its history |
| Loss handling | Net balance drift per partner | Named asset at a named partner |
| Condition and repairs | Not tracked per item | Full per-item wash and repair history |
| Deposit support | Aggregate only | Per-item deposit from issue to refund |
| Scan effort | Counted at handover | Scanned per item, or grouped via SSCC batching |
When does each model fit, and can they run together?
Use balance-level tracking where assets are interchangeable and partners already think in exchange terms. Use asset-level tracking where the deposit or item value justifies serialization, or where condition, compliance, or reuse reporting needs per-item evidence. Rotion runs both in the same system, in the same fleet.
Most operations mix them: exchange pallets on balances, serialized crates and kegs on passports. Because both live in one platform, a partner's page shows their exchange balance and the serialized assets they hold side by side, and moving an asset type from balances to serials later is a data change, not a system migration.
Not sure which model fits?
How are reusable assets identified?
Rotion identifies reusable assets with QR codes, barcodes, RFID, or combinations, using GS1-compliant asset IDs. Existing labels and scanners are reused.
What is SSCC batching?
With SSCC batching, one scan moves a full load, stack, or cage past a shared checkpoint while every asset inside keeps its own record. Available on Rotion Scale.