Collections from institutions, collection centers, and campaigns — not just companies and individuals

A recycling operator doesn't only take in waste from companies or individual private persons. A meaningful share of volume, especially for WEEE (waste electrical and electronic equipment), comes from other sources: a municipality running a neighborhood-by-neighborhood collection campaign, an intermediate collection center that aggregates handovers from several points, a seasonal event ("bring in an old appliance, get a discount") that brings in dozens of handovers in a single day. Until this sprint, none of these situations had a natural place on the collection form — everything had to be forced into either "company" or "individual," even when the real information (which campaign, which locality, which center) was lost, or ended up crammed into a free-text notes field.

Three new source types

The collection form now has three additional options, alongside company, individual, and household:

• Institution — for handovers from a public entity (municipality, school, state institution) that doesn't behave administratively like a private company, but still needs the same traceability.
• Center — for an intermediate collection center that aggregates waste from multiple points before handing it over to the final operator.
• Campaign — for handovers collected as part of a seasonal or one-off campaign, with a dedicated field for the campaign locality, required for this source type.

Each source type has its own specific fields, not a generic relabeled form. An operator running a WEEE collection campaign in a city can now correctly record the origin of each handover, with the campaign locality saved as structured data, not buried in a free-text field that can't be filtered or reported on later.

A naming cleanup, in the same release

Alongside the three new types, the internal names of the existing source types were aligned to Romanian — what used to be internally labeled "company," "person," or "walk_in" became "companie," "persoana," "domiciliu." It's not a visible change for the operator at the interface level (the label there was already in Romanian), but it consistently aligns all the app's internal terminology with the language actually used day to day by the operators who work with it — less mental translation between what you see on screen and what it means technically underneath.

Control over which source types show up

Not every operator works with all six source types. An operator who processes exclusively metals from companies doesn't need to see the "campaign" or "center" options on the form, just as one who frequently runs seasonal campaigns doesn't want visual clutter from unused options. From settings, each tenant can now individually enable or disable which source types appear on the collection form — by default, all six are active, but the configuration is left to the operator.

Why it matters for an operator who also works with institutions

For an operator whose volumes don't come solely from classic supplier contracts, but also from partnerships with municipalities or from their own collection campaigns, the difference isn't cosmetic. Monthly and annual reports (ANPM, AFM — Romania's Environmental Fund Administration, and the HG 856 registry) get more accurate when the real source of each handover is recorded correctly from day one, not reconstructed later from memory or a separate notebook. And when an audit asks "where did this batch come from," the answer is already in the system, structured, not in a separate notebook kept just for campaigns.

A side benefit: more forgiving imports

Also in this release, the CSV import flows for people, companies, and waste types became tolerant of Romanian-language column headers, with or without diacritics — the import file no longer needs English-language columns to be accepted. A small detail, but a useful one for anyone importing data from a spreadsheet kept in Romanian format for years.