Returnable Packaging Tracking Software Guide

01The guide

Six chapters and an RFP template.

For teams writing a shortlist or an RFP. It works for any supplier you compare, including us.

Buying returnable packaging tracking software.

A buyer's guide for multi-partner loops

Buyer's guideEdition 2026

Contents

01Know your loop before you shop.
02The requirements, weighted.
03Ten questions for every supplier.
04Types of tools and where each one stops.
05Data, integration and exit.
06Plan and measure a pilot.
AAppendix: an RFP requirements template.

02Requirements

Build your requirements list.

Tick what your loop needs. Each line has a suggested weight; change it to fit. Copy the list into your RFP.

R.01Each asset has its own ID and history, not only a balance per partner.
R.02Every handover records who holds the asset, with the scan as evidence.
R.03One scan per pallet or load (SSCC) keeps asset-level traceability.
R.04Partners join with a phone and a link, with nothing to install.
R.05Partner users do not add to the price.
R.06Each partner sees only its own assets, balances and statements.
R.07The partner portal shows in the partner's language.
R.08Reads the codes already on the fleet: QR, barcode, RFID and GS1 GRAI.
R.09Works with phones first; sensors only where they pay off.
R.10Standard connectors for your ERP, WMS and TMS, set up by the supplier.
R.11An open API and webhooks.
R.12Full data export at any time, in open formats, also after the contract ends.
R.13Hosting in the EU and single sign-on.
R.14Deposits charged and refunded by scan, on statements partners can accept or dispute.
R.15Reuse rates and cycle counts per packaging category, traceable to the scans, for the PPWR.
R.16Flags missing returns and proposes the next step, instead of showing only the last scan.

Nothing here yet.

Must

R.01Each asset has its own ID and history, not only a balance per partner.
R.02Every handover records who holds the asset, with the scan as evidence.
R.03One scan per pallet or load (SSCC) keeps asset-level traceability.
R.04Partners join with a phone and a link, with nothing to install.
R.05Partner users do not add to the price.
R.06Each partner sees only its own assets, balances and statements.
R.07The partner portal shows in the partner's language.
R.08Reads the codes already on the fleet: QR, barcode, RFID and GS1 GRAI.
R.09Works with phones first; sensors only where they pay off.
R.10Standard connectors for your ERP, WMS and TMS, set up by the supplier.
R.11An open API and webhooks.
R.12Full data export at any time, in open formats, also after the contract ends.
R.13Hosting in the EU and single sign-on.
R.14Deposits charged and refunded by scan, on statements partners can accept or dispute.
R.15Reuse rates and cycle counts per packaging category, traceable to the scans, for the PPWR.
R.16Flags missing returns and proposes the next step, instead of showing only the last scan.

Nothing here yet.

Should

R.01Each asset has its own ID and history, not only a balance per partner.
R.02Every handover records who holds the asset, with the scan as evidence.
R.03One scan per pallet or load (SSCC) keeps asset-level traceability.
R.04Partners join with a phone and a link, with nothing to install.
R.05Partner users do not add to the price.
R.06Each partner sees only its own assets, balances and statements.
R.07The partner portal shows in the partner's language.
R.08Reads the codes already on the fleet: QR, barcode, RFID and GS1 GRAI.
R.09Works with phones first; sensors only where they pay off.
R.10Standard connectors for your ERP, WMS and TMS, set up by the supplier.
R.11An open API and webhooks.
R.12Full data export at any time, in open formats, also after the contract ends.
R.13Hosting in the EU and single sign-on.
R.14Deposits charged and refunded by scan, on statements partners can accept or dispute.
R.15Reuse rates and cycle counts per packaging category, traceable to the scans, for the PPWR.
R.16Flags missing returns and proposes the next step, instead of showing only the last scan.

Nothing here yet.

Nice

Your requirements list

Requirements selected

Paste it into your RFP. The guide has the full template.

03Supplier questions

Ten questions to ask every supplier.

Ask each one in the demo. A good answer is one the supplier can show you on screen.

Q.01Show me one asset's history across three partners.

Why it matters: Balances per partner hide where assets go missing. Only a per-asset history shows which handover lost it.
A good answer: A timeline for one asset with each holder, place and time, and the scan behind every step.

Q.02What does a partner need to install, learn or pay?

Why it matters: Your loop is only as good as the partner who scans least.
A good answer: Nothing to install, a link to join, and partner users that do not add to your bill.

Q.03Do we have to relabel our fleet?

Why it matters: Relabeling costs money and months, and stops a pilot before it starts.
A good answer: It reads your QR, barcode, RFID or GS1 GRAI codes as they are, and one asset can carry more than one.

Q.04What happens when a scan is missed?

Why it matters: Scans get missed in every loop, so the gap needs to stay visible.
A good answer: The gap is flagged, the next scan closes it, and the record shows what was inferred.

Q.05How do we get all our data out?

Why it matters: Your asset history is your evidence. It should not stay with the supplier.
A good answer: Full history as CSV or through the API, at any time, also after you leave.

Q.06Which systems do you connect to as standard, and who builds it?

Why it matters: Integrations are where projects slow down and costs grow.
A good answer: Named standard connectors that the supplier sets up, and custom work quoted before you sign.

Q.07How is the price built, and what will year one cost?

Why it matters: Prices per user grow with every partner you add.
A good answer: Published plans, priced per fleet or platform, with year one written out line by line.

Q.08How do you calculate a reuse rate?

Why it matters: Under the PPWR, reuse figures need to stand up to an auditor.
A good answer: The formula on screen, each figure traceable to its scans, and read-only access for an auditor.

Q.09How does a partner dispute a balance?

Why it matters: Disputes settled by phone and spreadsheet cost more than the assets.
A good answer: Statement lines linked to their scans, accepted or disputed by the partner in its own portal.

Q.10What does our first loop look like in week one?

Why it matters: A pilot shows more than any slide.
A good answer: One loop with two or three partners, live in weeks, measured on returns and scan coverage.

04Types of tools

Know which kind of tool you are looking at.

Most tools in this space were built for one job. Each is good at that job; check where it stops.

Type of tool

Built for

Where it stops

Balance administration

Built forCounts per partner, documents and invoices.

Where it stopsNo identity per asset, so losses cannot be traced to a handover.

Hardware trackers

Built forLive location of high-value carriers.

Where it stopsA tracker, battery and subscription per asset; the cost turns against you on large crate fleets.

Indoor positioning

Built forReal-time location inside your own site.

Where it stopsThe walls of your own site, and it needs installed anchors.

ERP and WMS modules

Built forPackaging as stock in your own system.

Where it stopsPartners cannot see or confirm anything themselves.

Pooling provider portals

Built forThe provider's own pool.

Where it stopsOne provider's assets, not your mixed fleet.

Circulation platformsWhere Rotion sits

Built forOne record per asset shared by every partner, with custody, deposits and reuse reporting.

Where it stopsIt is software on the codes your assets carry; it does not do live indoor positioning.

05Before the demo

Two checks before you book a demo.

Both save time on your side and ours.

When Rotion is not the right choice.

Save yourself a demo if one of these is you.

01You track fixed IT assets on one site.
02Your packaging is one-way and never comes back.
03You want a hardware tag and nothing else.
04You need live positions inside a building.

If your assets move between partners and come back, plan a pilot.

Plan a pilot you can measure.

Start with one loop, two or three partners and six to eight weeks. Agree up front on what counts as success.

M.01Scan coverage at each handover.

M.02Days until an asset comes back.

M.03Assets unaccounted for at the end.

M.04Partners scanning without a reminder.

Starter lets small teams try Rotion free for 14 days. See Starter

Czech Republic

Goodlok in Czechia runs its reusable packaging on Rotion Starter.

Choose trackingsoftware with care.

Six chapters and an RFP template.

Get the guide by email.

Build your requirements list.

Ten questions to ask every supplier.

Q.01Show me one asset's history across three partners.

Q.02What does a partner need to install, learn or pay?

Q.03Do we have to relabel our fleet?

Q.04What happens when a scan is missed?

Q.05How do we get all our data out?

Q.06Which systems do you connect to as standard, and who builds it?

Q.07How is the price built, and what will year one cost?

Q.08How do you calculate a reuse rate?

Q.09How does a partner dispute a balance?

Q.10What does our first loop look like in week one?

Know which kind of tool you are looking at.

Two checks before you book a demo.

When Rotion is not the right choice.

Plan a pilot you can measure.

See it on your own loop.

Talk to Rotion