What we have built on Odoo
Odoo covers most of what you need, and it always stops somewhere. Here are the exact places where we stepped in for French SMEs: what the software could not do, and what we built on top of it. Each case covers the starting need, the limit we hit and the solution delivered.
Eco-contribution and regulatory fees
Show the eco-contribution clearly on quotes and invoices, even though it varies from one product variant to another and an Odoo tax would give the wrong amount.
Staggered deliveries and backorder tracking
A delivery date on each order line, a visual flag on partial orders, and the expected date carried through to backorders and the invoice.
Truly bilingual sales documents
Odoo translates its own labels, not the text you add. The result: a customized document ends up bilingual by accident. Seventeen templates made conditional.
Meeting room booking for a coworking space
Two journeys on one website: members who book without paying and visitors who pay online, with the time slot blocked as soon as the request is made. Six modules.
Lease financing and insurance tracking
Contract assignment to the refinancing company, residual value, interim rent, fees prorated to the actual day, and enforceable compliance. None of this exists in Odoo.
Telavox phone system connected to the CRM
The call log on the contact record, matching on a normalized number, and an unknown number that becomes a sales lead without any data entry.
Product blocking flag
The blocking product warning disappeared in version 19. We rebuilt the flag teams relied on every day, all the way to the delivery slip.
Customs tariff codes and import duties
The customs code and two duty rates, including anti-dumping, shown at the top of the product form without installing a full customs declaration module.
Production forecasting and individual targets
Forecast volumes by product and by delivery month, and track a sales target for each salesperson where Odoo only knows the team.
Drop shipping invisible to the end customer
Have the supplier ship directly without the supply chain showing on the documents. Case study in progress.
Coming soonOur rules for custom development
A customized ERP without discipline becomes impossible to evolve. Here are the rules we hold ourselves to, and that we explain to every client before we start.
Configuration first
Custom development only comes in when configuration cannot do the job, and we tell you so.
Never a field that duplicates data
If the information already exists, we show it where it is useful. We do not copy it somewhere else.
Never two synchronized copies of the same data
One single source, derived fields. Two copies that sync with each other always end up drifting apart.
No automation that sends or invoices on its own
Buttons prepare a draft, a human approves it. This is the rule that prevents customer incidents.
Internal flags stay internal
An alert banner meant for your teams never appears on a customer or supplier document.
Every automation is bounded by a date
A rule created without a start date replays the entire history the day it is turned on.
Does your need look like one of these cases?
Most of these developments started with a sentence like: Odoo can't do that. In half the cases, configuration was enough. Let's talk about yours before writing any code.
Talk to an Odoo expert