Business software · Amberg, Bavaria
We build, adapt and maintain business software for companies whose standard systems no longer fit their processes.
Odoo is one of our core platforms, with experience across Odoo 17, 18 and 19.
The real problem
Most Odoo projects start with the same question: can the standard do this? If yes, we configure it. If not, we adapt it, build it, connect another system — or tell you a different solution fits better.
You don't need to know whether you need a module, a customization or an integration. Describe what should work differently. Classifying it technically is our job.
Sound familiar?
Most enquiries start not with a requirement but with a sentence like one of these. If you recognise one, that is already enough for a first conversation.
"We plan in Excel and correct things verbally."
Usually a module of its own. That is exactly how our shift planner came about.
"The same data gets typed twice — once in the warehouse, once in accounting."
Usually an interface. Sometimes automation in the existing system is enough.
"From January we have to send e-invoices. Nobody knows whether our system can."
Often the standard already handles it. We check and set it up rather than sell you something.
"A colleague built this years ago. He has left, it still runs, nobody touches it."
First read it, then decide: document it, replace it, or keep maintaining it.
"We are stuck on an old Odoo version because our custom modules block the upgrade."
Migration including custom modules, tested on a copy before anything goes live.
Why we understand the process
Before Turbo Solutions I was employed at a company where the same question came up every morning: who is working today, in which area, on which shift. Planning happened in Excel and corrections happened verbally.
That is why the shop-floor screen is part of the module. It puts the schedule where the people actually need it.
I have worked with Odoo since 2022, by now across three major versions. If your process looks different from the one I saw back then: that is the normal case. Describe it to us.
What came out of it
Both modules came out of a real process, not a feature list. They are listed in the official Odoo Apps Store, run in production databases, and we maintain them across Odoo 17, 18 and 19 — you can check for yourself.
01 — Shift planning
A planning grid that removes the mental arithmetic: planned hours against target, open absences and detected conflicts sit above the grid and jump straight to the cell in question.
€99one-time, per database
On the Odoo Apps Store
02 — Warehouse & shipping
A delivery order becomes pallets: quantities fill one pallet up to its capacity, then the next begins. Lots, dimensions and weights belong to the individual pallet, not to the shipment.
€79one-time, per database
On the Odoo Apps StoreFor Odoo partners
We take on development as a subcontractor or on a project basis — when your own team is booked out, a project has a peak, or a migration is stuck between two other deadlines.
Coordination runs directly between your project lead and the developer writing the code. For larger scopes we work with regular partners — your point of contact stays the same.
Discuss project capacityFAQ
Not for our modules. The shift planner depends on hr, hr_holidays and mail; the pallet module on stock, stock_delivery and sale_stock — all Community. For customizations we work with whatever you're running.
Yes, that's the most common case. We look first at what has already been customized — existing in-house development often decides what's sensibly possible.
Yes. The standard modules are rarely the problem — the custom ones are. We maintain both of our own modules across three Odoo versions, and testing always happens on a copy.
After we've talked through the process, we estimate the effort and give you a price before any work starts. The estimate itself costs nothing. Small customizations are billed by effort; clearly scoped modules at a fixed price.
Yes. You should keep working with us because it fits — not because you have no choice.
First we check whether your Odoo already handles it — the German localization covers XRechnung and ZUGFeRD in current versions. Usually it is a question of configuration and process rather than development. Where the invoicing process still needs manual rework, we look at that separately.
Our modules call nothing external: no CDN requests, no telemetry, fonts served from your own server. The kiosk view is off by default and, once enabled, shows only “absent” rather than the reason.
Contact
You don't need to know the technical solution. Describe what your process looks like today, which Odoo version you're running, and what the result should be.
Usually a reply the next working day. No follow-up spam if we're not the right fit.
Your enquiry reaches a developer directly, not a sales funnel.
Turbo Solutions