Most explanations of reusable cup schemes end at the return point. You finish your drink, return the cup and get your deposit back. From the customer's perspective, that's exactly how it should feel.

Behind the scenes, however, the cup's journey is far from over.

Getting a cup back is obviously important, but a returned cup only delivers the benefits of reuse if it can be washed, put back into circulation and used again. Having spent the last few years implementing reusable cup schemes at venues including the Eden Project and Blenheim Palace, we've learnt that what happens after a cup is returned matters just as much as getting it returned in the first place.

So what actually happens?

1. It starts by making the return obvious

Before anything else can happen, the customer has to return the cup.

That sounds straightforward, but we've seen how much difference the design of the return journey makes. Customers need to know where to take their cup, what they need to do and how they'll get their deposit back. Return points need to be convenient and clearly signposted, and staff need to understand the scheme well enough to explain it.

If somebody has to walk around a venue looking for somewhere to return their cup, you've already introduced unnecessary friction. The best return journey is one the customer barely has to think about.

2. The cup needs to be identified

When the cup is returned, you want to know that a specific reusable asset has come back. At re-universe, we use RFID to give each cup its own digital identity, so its return can be recorded rather than simply having another cup dropped into a collection bin.

At a small scale that distinction might not seem particularly important. At a stadium, visitor attraction or other venue managing tens or hundreds of thousands of reusable items, it becomes much more useful. Instead of estimating what is happening to your stock, you can build a record of what is actually happening to individual reusable assets as they move through the system.

3. The refund needs to be instant

For the customer, this is arguably the most important part of the return.

If they've paid a deposit, returning the cup should complete the transaction. They shouldn't have to wait several days for their money back, download an app or create an account.

We think the refund should be instant. The cup is returned, the return is recognised and the money goes back to the customer. The technology can do the complicated work in the background while the customer experience remains very simple.

From their perspective, that's the end of the journey. For the cup, it's really only the halfway point.

4. Now the cup needs to become usable again

Returned cups need to be collected and washed before they can go back into circulation. Depending on the scheme, that might happen on site or the cups might leave the venue to be washed by an external provider.

This is where treating each cup as an identifiable asset becomes particularly useful. As cups are washed, they can be automatically scanned again and the wash recorded against their digital identity. The system can then distinguish between a cup that has simply been returned and one that has completed the wash process.

That isn't just useful information. It can provide an additional operational safeguard by preventing a cup that hasn't been recorded as washed from being served again.

5. What if the cups leave the venue?

A lot of reusable cup schemes involve external washing, logistics or managed cup hire. In those situations, large quantities of cups can regularly leave a venue and come back again.

Those movements can be recorded too. Cups can be scanned as they leave the site and again when they return, giving the venue an accurate record of how many reusable assets have gone off site and how many have come back.

That becomes particularly useful when external partners are responsible for washing, logistics or managing the cup pool. The venue has its own data against which it can validate the service it is receiving and the associated costs. It can see how many cups were sent away, how many came back, how many were lost and, where the relevant wash events are recorded, how many required additional washing before they were ready to circulate again.

For organisations paying per wash, per movement or for losses, those differences can have a real financial impact over thousands of cups and an entire season. Rather than relying entirely on figures provided by an external operator, the venue has an independent record of what happened to its reusable assets.

The same principle can be applied inside the venue. A stadium, for example, might want to record how many clean cups have been stocked at a particular bar before an event. Another operator might only care about returns and washing.

There isn't one journey that every reusable item has to follow. The important thing is being able to record the stages that matter to your operation.

6. From four events to a complete picture

In our current deployments, there are four core events we typically record:

Sold → Returned → Washed → Served again

But those aren't fixed. We can add additional events wherever they are useful, whether that's a cup leaving a site, returning from an external wash facility, going through an additional wash, arriving at a particular bar or passing through another stage in the operation.

That means the data can answer much more useful questions than simply "How many cups did we buy?" or even "What was our return rate?"

You can understand how many cups have actually been reused and how many times they have circulated. You can see how many left the venue and how many came back, how many were lost, whether returned cups have been washed and whether some required washing more than once. Where external partners are involved, that same data can help reconcile operational performance and costs against what actually happened.

You don't necessarily need to record every possible event. The point is that once every item has its own digital identity, you can capture the events that are useful to your operation and build a much clearer picture of the true cost and performance of reuse.

7. The important bit: the cup gets used again

Ultimately, getting the cup returned isn't the objective. Getting it used again is.

Once it has been returned, washed and made available for service, the same cup can be handed to another customer and the whole cycle starts again. Multiply that process across thousands of cups and hundreds of thousands of drinks, and you begin to see the difference between simply buying reusable packaging and actually operating a reuse system.

For the customer, none of this should feel complicated. They buy their drink, use the cup, return it and get their deposit back immediately. The complexity belongs behind the scenes.

The same infrastructure can work for more than cups

Although today we're doing this predominantly with reusable cups, there is nothing particularly special about a cup from a technology perspective.

The same principle can apply to almost any reusable item.

It could be a takeaway food container moving between a restaurant, customer and wash facility. It could be a hotel dressing gown moving between a room, laundry and hotel. It could be a reusable vape that needs to be returned, processed and put back into circulation.

The events that matter will be different in each case. A cruise ship may care about when an item is removed from the ship by a guest or goes to laundry. A food operator may care about returns, washing and redistribution. Another business may need an entirely different set of events.

The object changes, and so does the journey. The underlying principle doesn't.

Give each reusable item a digital identity, record the important events in its lifecycle and use that information to keep it circulating for as long as possible.

For the customer, reuse should be simple. Behind the scenes, the operator should have the information it needs to make that simplicity possible.

That's the infrastructure that turns a reusable product into a reuse system.