Walk-in collections — the intake flow at your collection point

Not every waste handover comes from a known supplier. Every collection point occasionally gets someone with no account, no contract, no entry in any list — a neighbor bringing in an old fridge, an occasional customer handing over a batch of scrap metal without ever having registered before. Until this sprint, VanaGreen required the source of a collection to be a company or an individual already existing in the catalog. For a walk-in, the operator first had to create a person profile — name, national ID (CNP), address — just to start the collection. For someone dropping off a small quantity, once, that step is disproportionate.

What's new: the "household" source

VanaGreen now has a fourth source type on the collection form — "Household" — for anonymous or one-off handovers at the collection point, with no need for a pre-existing company or person in the catalog. In practice, a new tab appears on the intake form, alongside "Company" and "Individual," and the operator can finalize the collection directly, without searching for or creating an entity first.

The underlying constraint — that a collection must have exactly one valid source — was rebuilt to allow the case where neither company nor individual is filled in, exactly the walk-in scenario. It's a small change at the data level, but it fixes a real bottleneck at the counter: the operator no longer wastes time entering identification data for someone who has none to give, or doesn't want to, for a handover of a few kilograms.

What doesn't get generated — and why that's intentional

For "household"-type collections, official documents (NIR, PV, Annexes) aren't generated automatically, in this first phase. The collection still finalizes normally — stock updates, the movement is recorded correctly in the system — but the document set stays suppressed, with an explicit internal error code, not a silent failure or a blank document sent to the printer.

The reason is simple: without a complete source identity, an official NIR or PV document has nothing to put in the "handed over by" field, and generating an incomplete document would be riskier than not generating one at all. The bulk collection import flow rejects "household"-type rows the same way — only company and individual are supported there, again for identification-data traceability reasons.

Why it matters for an operator at the counter

For a collection point that serves the general public, not just contracted suppliers, intake friction translates directly into wait times and, sometimes, people giving up and going elsewhere. Being able to log a walk-in in a few seconds — without opening a separate "add new person" form, without asking for a national ID from someone dropping off an old appliance once — means a shorter queue and less administrative work for cases that never warranted a full catalog profile anyway.

It's still the operator's choice whether they want official documents for a given handover — in which case they register the source as an individual, with the required data — or whether they treat it as a simple, paperwork-free walk-in. Both flows coexist, each suited to its own situation.

What else shipped in the same sprint

The same sprint also gave every logged-in user the ability to change their own password from within the app (not just through an admin-driven reset), and creating a new operator or tenant account now automatically sends a welcome email with the login address and initial password — a small step, but one that removes the need to hand off fresh credentials manually, by phone or WhatsApp.