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.
Last updated: 29 September 2026
SSCC batching groups assets under a Serial Shipping Container Code so one scan moves an entire load, stack, or cage past a shared checkpoint, while every asset inside keeps its own identity. Rotion uses temporary SSCC batches to keep scan volume low without giving up asset-level traceability. It is available on the Scale plan and up.
How does batching with SSCCs work?
A Serial Shipping Container Code (SSCC) is a GS1 identifier for a logistic unit: a pallet of crates, a stack of trays, a cage of totes. In Rotion, assets are grouped under an SSCC once, and from then on the whole group moves through dispatch, transport, and receiving checkpoints with a single scan.
The batch is temporary. When the load is broken up, at a store, a washing station, or a return point, assets fall back to individual scanning, and every event the batch passed through is already written to each asset's digital packaging passport. Grouping works for serialized and batch-identified assets alike; see asset identification for how identity is assigned.
Why does SSCC batching keep scan volume low?
Because teams scan once per handling step, not once per item. A driver picking up a full pallet of returnable transport items (RTIs) scans one SSCC instead of every crate on it, and the same is true at each shared checkpoint the load passes: warehouse out, truck, cross-dock, warehouse in.
This is what makes asset-level tracking workable at real warehouse and transport speed. Without batching, per-item identity would mean per-item scanning at every handover, which no dock schedule survives. With SSCC batching, scan effort scales with the number of movements, not the number of returnable containers, reusable plastic containers (RPCs), or dunnage pieces in them, and each asset still stays traceable.
Which Rotion plan includes SSCC batching?
SSCC batching is available on the Rotion Scale plan and up. Launch covers straightforward per-item and per-batch scanning; Scale adds SSCC grouping for operations where loads move through multiple shared checkpoints.
| Plan | Price | Fleet size | SSCC batching |
|---|---|---|---|
| Launch | 499 EUR/month, or 399 EUR/month billed annually | Under 100.000 assets | Not included |
| Scale | 999 EUR/month, or 799 EUR/month billed annually | Under 500.000 assets | Included |
| Custom | Custom pricing | Unlimited assets | Included |
When is SSCC batching the right fit?
Whenever assets move in loads through checkpoints that several parties share: full pallets between producer and retailer, cages between stores and a distribution center, stacks of trays into a washing station. If your assets travel individually, plain per-item scanning is enough; if they travel grouped, batching removes most of the scanning without removing any of the history.
Batching also pairs naturally with balance-based exchange flows, since both reduce per-item effort where per-item detail is not needed. The trade-offs between the two tracking models are laid out in asset-level vs balance-level tracking.
See group scanning on a real load
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.
How does deposit management work?
In Rotion, a deposit is charged on the issue scan and released on the return scan, and every venue and return point keeps a balance that updates itself.