Aktualności

Welcome to the KodaSoft blog — what to expect

We are starting a blog. Expect ERP implementations, Poland's compliance digitisation, and a look inside how the Opero platform gets built.

Konrad JarosińskiKonrad Jarosiński · Tech Lead
2 min read

Updated 17 August 2026

Hello. Whether you arrived from a search engine, from LinkedIn, or from a link someone on the team sent you — welcome. This is the first post on the KodaSoft blog, so it seems only right to explain why we started it and what you can expect to find here.

Who we are

KodaSoft is a software house based in Pomerania, Poland. We build Opero — a modular business platform that, rather than pretending every company works the same way, lets you assemble a system around an actual process: custom objects, custom forms, automation rules, reports and an API. Day to day we work on implementations, integrations and maintenance — and that work is the fuel for this blog.

What we will write about

In short: the things we had to work out ourselves, and the things that are hard to find a straight answer to online. No marketing fluff, no “AI revolution for your business”. Four main threads:

  • ERP implementations, unvarnished — what actually decides whether a project succeeds, where budgets leak, and why data migration always takes longer than someone promised.

  • Compliance digitisation in Poland — KSeF, e-Delivery, JPK and the rest. Practically: what you have to do, by when, and what it means for the systems you already run.

  • How we build Opero — architectural decisions, trade-offs, and the things that did not work the first time round. Plenty of detail for anyone who likes looking under the hood.

  • Processes worth automating — document flows, approvals, reporting. Concrete examples rather than generalities.

Why now

Because 2026 is an unusually dense year for companies operating in Poland. KSeF, the national e-invoicing system, is already mandatory — since February for the largest taxpayers and since April for everyone else — but the grace period without penalties runs only to the end of the year. In practice, the coming months are the last comfortable window to fix whatever is currently working “more or less”.

In parallel, 1 October 2026 is approaching — the date by which every business registered in CEIDG before 2025 must hold an electronic delivery address. And since an uncollected letter is deemed delivered after fourteen days, this is not a topic that rewards postponement.

Coming up next

  1. KSeF after go-live — what the first months of mandatory e-invoicing taught us.

  2. Electronic delivery step by step — who is affected, by when, and how not to miss an official letter.

  3. When a custom module beats an off-the-shelf system — and when it very much does not.

  4. Anatomy of an implementation — timeline, roles, risks, and what usually goes wrong.

If one of those topics is urgent for you, get in touch. The running order is not set in stone, and the best pieces tend to come out of real questions anyway. See you in the next one.

Tags

About the author

Konrad Jarosiński

Inżynier i architekt z 15 letnim doświadczeniem.

All articles

Next step

See how this works on your own processes.

We can walk through your operations, show how Opero would model them, and be direct about what fits and what does not.