The number that survives at month-end is usually just a total deployed count — nobody has written down how many actually came back per hub, how many are sitting forgotten in a corner of an apartment recycling area, or how many were quietly failed and scrapped during washing. Logistics operators, shippers, and carriers all need to see these three numbers together for one simple reason: without a shared sheet, the point where usable inventory is leaking — hub non-return, collection delay, or wash rejection — becomes a finger-pointing exercise instead of a fixable problem. This piece gives you a circular-logistics pilot operations sheet that records per-hub input, returns, non-returns, collection cycle, wash rejection, loss, re-entry day, and hold conditions on a single page — copy it and take it into today’s operations meeting.
Why this sheet matters right now
A July 2026 report from OpinionNews described how Ecofriend rolled out a model in which reusable packaging is delivered to consumers, returned to designated hubs such as apartment complex recycling areas, then collected, washed, and resupplied. The structure of that model — consumer behavior governs delivery-to-return, and the operator’s collection-and-wash operation governs return-to-resupply — maps directly onto the problem this operations sheet is built to solve. That said, the per-bag cost target mentioned in the report is a goal the individual operator set for itself, not an industry-wide operating standard. If a shipper or logistics team preparing its own pilot borrows that figure as a pass/fail benchmark for return rate or cost, it risks locking itself into a target that has nothing to do with its own hub conditions — collection accessibility, wash infrastructure, contract terms.
For background on how to design a reuse-and-return circular model, the Ellen MacArthur Foundation’s 2019 report “Reuse – rethinking packaging” is a useful reference. It evaluated more than 100 reuse initiatives and drew on over 50 interviews to build a framework of common failure and success factors in B2C reuse models. This should be read as general background for designing a collection-wash-reentry loop, not as evidence tied to a recent event. In other words, the actual trigger for this piece is the July 2026 domestic case; the Ellen MacArthur Foundation material functions as a background checklist for failure points that are easy to miss when translating that case into an operations sheet.
Circular-logistics pilot operations sheet
The table below is designed to be filled in per hub, on a weekly basis. The key is the “Reference source / status” column — it deliberately contains no arbitrary target return rate or pass rate. Before the pilot starts, the shipper, logistics operator, carrier (or collection contractor), and wash contractor need to agree in writing on the definition and standard for each field.
| Input field | Observed value (field record) | Reference source / status | Action |
|---|---|---|---|
| Input count per hub | Initial quantity deployed per hub code, with input date | Shipper’s order-system lot record — the lot unit (per dispatch vs. daily cumulative) must be agreed with the shipper before the pilot starts | The logistics operator logs the quantity in the per-hub input register at every lot deployment and reconciles it against the shipper’s system weekly |
| Returns per hub | Quantity actually returned to the collection bin, with return date | The contract’s definition of “return” (bin drop-off time vs. staff confirmation time) is undefined — must be agreed with the hub operator before the pilot | Hub staff log the returned quantity with a photo in the app or register at every bin open/close, and the logistics operator confirms it by the next morning |
| Non-returns per hub | Input count − returns − quantity currently in collection transit | No target return rate exists — the company should set its own baseline after collecting sufficient pilot data | The logistics operator identifies hubs where non-returns rose week-over-week and reports them to the shipper in the weekly meeting, requesting a site check |
| Collection cycle | Days elapsed from collection request received to collection actually completed | The consignment collection contract’s SLA is undefined — must be formalized with the carrier or collection contractor before the pilot | The carrier’s operations staff log request and completion times in the system; SLA breaches trigger an automatic alert to the logistics operator |
| Wash rejection | Quantity failed as non-reusable during the wash process on receipt, with reason (contamination/damage/foreign matter) | The wash contractor’s inspection standard is undefined — the judgment criteria (e.g., photo comparison) must be agreed with the wash contractor before the pilot | Wash contractor inspectors attach a reason code and photo to the system at each rejection; the logistics operator shares the cumulative reasons with the shipper monthly |
| Loss | Quantity whose location cannot be confirmed after a defined grace period from input | The loss-determination grace period is undefined — must be agreed with the shipper before the pilot | The logistics operator moves units past the grace period into the loss register and notifies the shipper whether they are subject to settlement |
| Re-entry day | Days from wash completion to being back in a resupply-ready state — the key turnaround variable | The wash contractor’s processing SLA is undefined — must be agreed before the pilot | The wash contractor logs wash-completion time; the logistics operator reflects the average re-entry days in the weekly report |
| Hold-condition status | Whether each pilot-pause trigger item is met or not | No hold-trigger figures exist — the shipper, carrier, and wash contractor must jointly define them before the pilot starts | The logistics operator checks hold conditions weekly and, if met, immediately proposes a pilot pause to the shipper in writing |
What each role should do today
Logistics operator
- Reconcile the per-hub input/return register against the shipper’s system weekly, and flag hubs where the numbers diverge.
- Pull the list of hubs where non-returns rose week-over-week and request a joint site check with the carrier and shipper.
- Compile the weekly hold-condition check results in writing for the shipper, and agree on next week’s response priorities together.
Shipper
- Finalize, in writing before the pilot starts, the definition of “return” (bin drop-off vs. staff confirmation) and the loss-determination grace period.
- Review per-hub return-rate data monthly and decide whether low-performing hubs need bin relocation or additional bins.
- Review cumulative wash-rejection reason codes and, if a specific cause (e.g., damage) recurs, consider changes to packaging spec or usage instructions.
Carrier (or collection contractor)
- Log request-to-completion times for collection in the system, and notify the logistics operator immediately of any SLA breach.
- Regularly review collection routes per hub to identify why any hub’s collection cycle runs unusually long (accessibility, missed requests, staffing).
- Photograph badly damaged or contaminated returns at the point of collection and pass them to the wash contractor as judgment evidence.
When to apply hold conditions
The pilot should be immediately reassessed for continuation under the following circumstances. The specific thresholds must be jointly defined by the shipper, carrier, and wash contractor before the pilot starts — this piece deliberately provides no arbitrary numbers.
- A specific hub’s non-return count shows a clearly abnormal upward trend relative to other hubs
- A hygiene or safety issue actually occurs (e.g., a wash-rejected unit re-entering circulation)
- Repeated collection SLA breaches make contract renegotiation necessary
- Per-hub input/return figures cannot be consistently reconciled against the shipper’s system, undermining the reliability of the data itself
Documents to check today
- Hub contract (definition of return, number/location of collection bins, termination conditions)
- Consignment collection contract (collection SLA, penalty clauses for delay)
- Wash contractor’s inspection standard (rejection criteria, photo-comparison procedure)
- Loss-determination and settlement clauses (grace period, who bears the cost)
- Hygiene and personal-data rules governing use of hub sites such as apartment recycling areas
The point of this sheet isn’t to hand you a magic number for raising the return rate. Early in the pilot, accurately measuring how much is leaking is itself the achievement. Once enough observations show whether inventory is disappearing at the hub, in collection, or in washing, the company has a defensible basis for setting a return-rate standard that fits its own conditions.
About the Author
PackingMaster: Editor of Paper Pack Log. We collect and organize market trends, product information, and technical insights for the paper packaging industry.