RotionDocs
Guides

Reusable takeaway container tracking

How Rotion tracks reusable takeaway containers, cups, and meal boxes: QR flows at issue and return, deposit management, and per-venue balances.

Last updated: 29 September 2026

Rotion is tracking software for reusable takeaway containers, returnable cups, and reusable meal boxes. Each container gets a digital identity, issue and return scans record who holds what, deposit flows follow the scans, and balances per venue and return point reconcile automatically. You keep your own containers, wash partner, and branding.

How does software track reusable cups, bowls, and meal boxes?

Rotion tracks identity per item or per batch. A container gets its own serial when the deposit or its value calls for the detail; when it does not, batch identity is enough. A serialized meal box carries its own scan history: issued at which counter, returned at which point, washed and reissued when. A batch of cups moves as one traceable group.

That choice is made per asset type, not per scheme, so a deposit-bearing meal box can be serialized while low-value cups run as batches in the same system. See asset identification for how identity levels work.

How do QR flows work at issue and return?

Scans at issue and return run on ordinary phones or on the scanners a venue already has, so no new hardware is needed. At issue, a scan links the container to the venue or, via its public passport page, to the customer who claims it. At return, a scan closes the loop, and a QR-based return point works without staff.

StepWho scansWhat Rotion records
IssueCounter staff, or the customer via QR claimContainer out, holder known, deposit charged if applicable
ReturnCustomer at an unattended QR return point, or staffContainer back, deposit released
CollectionDriver or wash partnerContainers routed to wash, return point emptied
ReissueVenueClean stock back in circulation

How do deposits follow scans?

A deposit is charged on the issue scan and released on the return scan, and each venue and return point carries a balance that updates itself, with no spreadsheet work. The REPASYS scheme runs this pattern at production scale on Rotion: 100.000 packages, a 0.30 EUR deposit per item, 6 participating retailers, and sub-ten-second returns. The mechanics are described in deposit management.

Free-return schemes skip the deposit and keep the same scan flows, a common choice in closed populations; see reusable packaging for canteens and campuses.

Can a pool flex across venues and events?

Yes. Because every container or batch has an identity, a pool is not tied to one venue. Rotion keeps balances per venue and per return point, so stock can shift to a festival or event for a weekend and come back, and because fill levels at each return point are visible, collection is scheduled before anything overflows.

Is Rotion a managed reuse network?

No. Rotion is the software layer, not a managed network. You keep your own containers, your own wash partner, your own machines and branding, and Rotion runs identity, scans, deposits, and venue balances underneath. Full-stack operators bundle all of that into one service; with Rotion the scheme, and its data, stay yours.

That also means Rotion fits horeca groups, caterers, and foodservice reuse schemes that already have wash logistics, and managed reuse networks themselves that want a stronger tracking layer under their own brand.

Keep the scheme yours

We show how your containers, wash partner, and branding run on Rotion.
Book a demo

How fast can we start?

Put codes on the items or batches, then scan when they go out and when they come back. A typical scheme proves the loop at a single venue or event before growing. Pricing follows asset count: the Launch plan at 499 EUR/month (399 annual) covers under 100.000 assets. See plans and how a rollout works.

Start with one venue

One venue, one return point, and a small pool are enough to prove the loop.
Book a demo

On this page