Suomi — the national module

Finland is where this toolkit goes deepest.

Full producer-responsibility handling — jätelaki 646/2011 and VNA 1029/2021 side by side with the PPWR, in one product record: the professional-operator gate, the registration routes, the per-kilo fees, the two deadlines that get confused, and the annual report itself.

The Suomi module: producer responsibility, computed

The gate, the routes, the destination test and the fee engine — the Finnish layer the EU tools ignore, computed per product from data the dossier already holds.

The Suomi tab of one product: the producer-responsibility questions, the per-part fee classes and channels, and the fee estimate
  • The professional-operator gate is asked first — no gate, no producer status — and the threshold is evaluated by date, so the rule that answers is the one in force today, not the one that was
  • Registration routes as they really are: a producer community via the Rinki service or Sumi, own registration as the authority-granted exception it is, and the separate Åland contract
  • Consumer or business fee channel resolved per packaging part by the destination test — where the packaging ends up, not who you invoice — with defaults shown as defaults and overrides by hand
  • The per-kilo fee engine prices on the operators' published price lists — Suomen Pakkaustuottajat and Sumi, detailed and light forms — to the cent, with VAT at 0% and 25.5% and the clamped annual service fee
  • Both deadlines, kept apart: packaging data to your producer community by 31 January, and the statutory end-of-June return to Lupa- ja valvontavirasto that the community files for its members
  • A per-product period history: every reporting period this product was counted in, with its units, kilograms and fee — and filed figures marked as filed

The Rinki module: the annual report as records, not a scramble

One record per filing period over the whole catalogue — because a year is not always one period, and the figures you filed must keep saying what you filed.

The Rinki reporting module: the list of reporting periods with payees and statuses, and the deadline note above it
  • Multi-period records: switch producer community in June and you file two partial periods — the module holds both side by side, each with its own payee and its own figures
  • ERP CSV import with explicit column mapping — the SKU, EAN, quantity and date columns are suggested from the header, and you confirm before anything is read
  • A preview that writes nothing: matched, unmatched and ambiguous rows are counted and listed, and the units land only when you apply them
  • Automatic producer-vs-distributor classification from the answers on file: resale sourced from a Finnish operator is their report, the same product sourced from abroad is yours — and every verdict carries its reason
  • Where the answers cannot decide, the verdict is UNDECIDED — never a guess in either direction — and an override stores your note beside it
  • The gate is honest too: when no Finnish product passes the professional-operator gate, the module says no report is due instead of preparing one

Totals you can carry into the reporting portal

Kilograms and fees per material group and channel, charts over the period, and a summary in the same taxonomy the reporting service asks in.

One reporting period opened: kilogram and fee totals per material group and channel, with charts and the Rinki-compatible summary
  • Kilogram and fee totals per material group, split consumer / business — the same split the price lists price
  • Charts over the period's composition — and partial totals say they are partial until every gap is closed
  • Gaps are named per product: missing weights, missing material codes, missing units — the exact thing to fix, not a red light
  • The Rinki-taxonomy summary to transfer into your producer community's own reporting service, with your producer identity and the period on it
  • Draft periods recompute from current product data every time they open; marking a period filed freezes the figures, because what was reported must keep saying what was sent
  • Every figure is an estimate priced on published lists and marked with its rate year — the binding invoice is always the producer community's own

The Finnish journey, drawn out.

Pick what your company is in Finland and the chart draws only your path — every step, what it needs from you, and the violet side-steps where the Suomi and Rinki modules do the work. Click any step for the plain-language version.

This is the Finnish leg. The EU-wide PPWR journey has its own interactive map.

Honest limits

What the app deliberately does not do.

A compliance tool earns trust by knowing where its authority ends. Three lines this product does not cross.

The filing happens in your community's own channel

The app prepares the figures and the summary in the community's taxonomy; it does not press the button. Neither Rinki nor Sumi publishes a machine-readable submission format, so the app does not pretend to produce an upload file.

Deposit-scheme artwork comes from Palpa

For a deposit container the app screens the deposit class, the reverse-vending geometry and the barcode rules, and writes the request — but the deposit and material marks themselves are Palpa's official artwork, never drawn here.

Estimates say they are estimates

Fees are computed on the operators' published price lists and marked with their rate year. The binding invoice is always the producer community's own — verify against the current list before filing.

Start where the fees actually land.

Fourteen days free, ten products, no credit card. Load your catalogue, answer the Finnish questions once, and watch the period report compute itself.