Route optimisation for recyclable collection

RecycleOrigin is a product Reorigin Technology designed and built. It is live at recycleorigin.com. The operational loop is source-separated collection: a generator requests a pickup, a collector runs a route, a facility receives material. Those are three roles on one product. The first city is Istanbul. The stated path is other Turkish cities, then Europe, then Australia. BTM Camp is an incubation context for the product. The proof we point at is the live loop, not the program name.

Why the route is exclusive

An exclusive route means the stops on that run belong to that driver for that plan. It is not a shared pool where two collectors can claim the same generator. Shared pools look flexible and produce double arrivals, missed windows, and a weight that nobody can attribute. Exclusivity is how the system can say who was supposed to be at the door.

Optimisation here is not a leaderboard of kilometres. It is the assignment of requested pickups onto a route a single collector can finish, in an order that respects the requests that exist that day. We do not publish a “30 percent less fuel” figure, because that number is not a measured result we are willing to cite. If a later study produces one, it will be labelled as a study. Until then the product claim is the mechanism: requested stops, one driver, a recorded outcome.

Three roles, one record

Generators create the demand. Collectors execute the route. Facilities receive the material. If each role had its own database, the route would be a rumour. RecycleOrigin keeps them as roles on shared services: Flutter clients, Go and Python services, PostgreSQL for the operational record, Docker for the deploy. A collector should not need a second login to see the stop a generator created. A facility should see the load that route was supposed to deliver.

The material list in the product is specific. Eight streams are supported: plastic and PET, glass, copper and brass, iron and metals, aluminum, cardboard and paper, tin cans, and electronics. A route that treats “recyclables” as one undifferentiated bag cannot tell a facility what arrived. Separation at the request is what makes the route about collection rather than about a generic courier job.

Weight is the evidence

Tokenization in RecycleOrigin is attached to verified weight, not to a photo of a bag. The point of the record is that someone can point from a route to a quantity. We do not describe a token price, a market, or a yield. Those are not figures on the case study. The engineering claim is traceability: the route, the role that ran it, and the weight that was accepted.

A route is done when the assigned stops and the received weight refer to the same job. A shorter line on a map is not, by itself, the product.

The clients are mobile because the work is not done at a desk. A generator confirms a pickup, a collector sees the next exclusive stop, a facility confirms receipt. Those are separate screens on one backend, which is why the product is Flutter rather than three websites. Push or offline behaviour, if a route runs with a poor signal, is a scoped addition — the case study does not claim that every screen works offline. Store release is part of shipping a collector build. A binary that cannot be installed on the device the driver actually uses is not a launched route.

What we would repeat for another operator

Another city or another material program does not start by cloning a consumer map app. It starts with the same questions. Who requests the stop. Who is allowed to run it. Who receives it. What unit is verified. Which streams are actually accepted. The first release is one city or one flow made traceable, which is the same planning shape as the cleantech software page: often 12–20 weeks for that first flow, scoped after discovery. Field clients, when the work happens at a gate or in a vehicle, sit with mobile and web.

We will not pretend a routing library is the product. The product is the operational loop the route serves. Read the RecycleOrigin case study for the system as shipped, and cleantech if you are an operator comparing sectors. Discovery is where we say whether your loop is this shape or a smaller integration into a system you already run.