Insights
Recycling collection software: what an operator should require
Collection software fails in the field, not in the demo. These are the requirements we would put in a tender, written from building RecycleOrigin in Istanbul. They apply whoever the vendor is.
Who has to share one record?
A collection loop has three parties. Generators hand over material: households, shops, and offices. Collectors drive to them. Facilities receive and weigh what arrives. If each party has its own tool, the same pickup exists three times with three different weights. RecycleOrigin puts all three roles on one data model, so a pickup is one record that each party sees from its own side.
Ask a vendor to show the same pickup from all three roles. If the facility's intake does not close the generator's request, the platform is three apps with an export between them.
Why do streams and verified weight come first?
Separate collection is the direction of regulation. The EU's Waste Framework Directive requires separate collection for at least paper, metal, plastic, and glass. Turkey's Zero Waste Regulation, published in 2019, sets out how institutions and municipalities build a zero-waste management system around collection at source. Turkey also runs a national deposit system for beverage packaging. A platform that records only a single mixed weight cannot report against any of them.
RecycleOrigin's generator flow records eight streams: plastic and PET, glass, copper and brass, iron and metals, aluminum, cardboard and paper, tin cans, and electronics. The weight a generator estimates is a claim. The weight the facility measures is a fact. The platform should keep both and make clear which one a reward or a report is based on. In RecycleOrigin the verified weight is the one that is tokenized.
| Requirement | Why it matters | How to test it in a demo |
|---|---|---|
| One record for three roles | A pickup must not exist three times | Follow one pickup as generator, collector, and facility |
| Source-separated streams | Reporting is per material | Record a pickup with two materials |
| Verified weight at intake | Estimates are claims, intake is the fact | Enter a different weight at the facility and see which one is reported |
| Exclusive driver routes | Two vehicles at one door doubles the cost | Cancel a stop and watch the route update |
| Works on a weak connection | Drivers lose signal | Close a job in flight mode, then reconnect |
| Audit trail | Every reported figure must trace to a pickup | Open the history of one record |
| Exports and hosting | Reports leave the platform; data stays in a named region | Export a month and ask where it is stored |
What should routing do?
Routing decides whether the service is affordable. Assigning stops to vehicles is a vehicle routing problem, and its constraints are operational: vehicle capacity, time windows, and which driver owns which stop. RecycleOrigin gives each driver an exclusive route, so two collectors are not sent to the same door. The design reasoning is in route optimisation for recyclable collection.
Ask what happens when a generator cancels, a vehicle fills early, or a driver goes offline in a basement car park. The answer shows whether routing is a real component or a map with pins.
What will an auditor ask for?
Every figure in a sustainability report should trace back to a pickup: who requested it, who collected it, when, which stream, and what the facility weighed. That chain is the audit trail. It has to be written as the events happen. It cannot be reconstructed later from a spreadsheet.
Ask for exports in a format your reporting team can use, and ask where the data is hosted. If personal data of residents is involved, KVKK applies in Turkey and GDPR in the EU.
What do we not claim?
RecycleOrigin is live in Istanbul first, with a stated path to other Turkish cities and then Europe and Australia. We do not publish a tonnage, a savings percentage, or a list of municipal clients, and this page should not be read as claiming them. BTM Camp supported the product as an incubation programme. It is not the operational proof. The proof is the collection loop at recycleorigin.com.
The product is described on RecycleOrigin. For a platform of your own see cleantech software solutions and the cleantech industry page.
Sources and further reading
- Directive 2008/98/EC on waste — the EU Waste Framework Directive, on EUR-Lex.
- Sıfır Atık (Zero Waste) — the Turkish Ministry of Environment's zero-waste portal.
- Depozito Yönetim Sistemi (DOA) — Turkey's national deposit management system for beverage packaging.
- Vehicle routing problem — Google OR-Tools documentation on assigning stops to vehicles.
- RecycleOrigin — the live product this note describes.
FAQ
What features should recycling collection software have?
One shared record for generators, collectors, and facilities; source-separated streams; weight verified at the facility; an exclusive route per driver; offline-tolerant mobile apps; an audit trail; and exportable reports.
Why does verified weight matter in recycling software?
A generator's estimate is a claim and the facility's measurement is a fact. Rewards and reports based on unverified weight cannot be audited. RecycleOrigin tokenizes the verified weight.
Which materials does RecycleOrigin record?
Eight streams: plastic and PET, glass, copper and brass, iron and metals, aluminum, cardboard and paper, tin cans, and electronics.
Where is RecycleOrigin live?
Istanbul first, with a stated path to other Turkish cities and then Europe and Australia. Reorigin does not publish a tonnage or a savings percentage for it.