Fixed price, in writing
Your full implementation cost, locked before you sign a thing.
Fixed-price Odoo implementation for Canadian manufacturers and distributors with 20–100 employees. We build a working system on your own data — custom development included — and you decide after you have run it yourself.
In this 30-minute working session, we'll map your operational workflows and confirm scope for your zero-dollar proof-of-concept build.
Trusted by growing manufacturers & distributors across Canada
Not a sandbox demo with sample products in it. We build your system, with your data, and we write the custom code your process needs — before there's a contract.
of your operations, running, before you sign anything
Your cost to get here:
$0
A sample of your SKUs, BOMs, routings, customers, price lists and open orders. Whatever you actually run on today, even if it's a spreadsheet.
Your workflows, your warehouse logic, your document layouts. Configured the way it would be on day one of production — not a generic Odoo instance.
Where standard Odoo doesn't fit your process, we write the module. Most partners scope custom work as a change order after you've signed. We build it into the proof.
Your team clicks through their own daily work in the system. If it isn't right, you walk away and you owe us nothing.
Simply the best Odoo partner. Professional, available, and helpful at every stage of the project.
We were in a tricky situation with another Odoo partner, and Kerning Code unlocked the situation at a very reasonable price compared to the crazy pricing we often see with Odoo partners.
They didn't focus on the price but on how they could help us — and they delivered on time, with no extra budget, even though they provided far more than expected.
Thank you Anthony, and thank you for your support. I definitely recommend Kerning Code.
You're probably talking to more than one of us. Here's what we'd ask in your position — including if you're considering going direct to Odoo.
| Ask them | KerningCode | What to watch for |
|---|---|---|
| Can I see my system before I sign? | Yes — 70% built, on your data, free. | A generic demo instance, or a slide deck of screenshots. |
| Is the price fixed before I sign? | Yes, in writing, after your free build. | Billed by the hour as they go, or a range that only moves up. |
| Who writes the custom code? | Our own developers. Canadian team, coast to coast. | Subcontractors or offshore teams you'll never speak to. |
| What if your estimate was wrong? | We absorb it. Fixed price means fixed. | A change-order process explained in detail on the first call. |
| How many builds last 12 months? | 30+, with 400+ users on systems we manage. | Partners who count lifetime projects instead of recent ones. |
| Who owns the database? | You. Always. Including the custom modules. | Code held in the partner's repo, or licensing on their modules. |
| What happens after go-live? | 6 months of support included in the price. | A separate support retainer quoted the week you go live. |
Scroll the table sideways on mobile →
Your full implementation cost, locked before you sign a thing.
Where Odoo doesn't fit your process, we build the module. In scope, not extra.
Products, customers, suppliers, open orders, historical transactions.
Dedicated people on call through your go-live, when it matters most.
Both included. Your floor staff and your controller, in French or English.
Clients get our library. Most "custom" requests already exist and cost you nothing.
Process manufacturing (batch, recipe, formula) or discrete (BOMs, assembly, serial numbers) — we've built both, repeatedly, in Canada.
Every partner talks about outcomes. We put ours in the contract.
Free working build — 70% of your system, on your data, before any money changes hands.
Fixed price — the number in your contract is the number you pay.
6 months of post-go-live support — go-live is the start, not the finish.
You own everything — the database, the configuration, the custom modules. Always yours.
Payments follow delivered work — milestones you've accepted, never promises.
Weekly milestones, shared — you always know exactly where things stand.
30+ implementations in the last 12 months. 400+ users we manage. Zero failed go-lives.
30 minutes. We map your operation and tell you if we're a fit.
We go deep on your real processes and pull a sample of your data.
Your system, your data, custom development included. You run it.
Scope and number locked. Low deposit, then payment per accepted milestone.
Staffed through go-live week and supported for half a year after.
Nobody budgets for a second attempt. But an ERP implementation that stalls doesn't stop — it runs alongside your business while you keep paying for both.
Licences, consulting hours and internal time all keep running while your team quietly goes back to the spreadsheets. The old process never actually stopped.
Someone has to unpick the configuration before rebuilding it. Undoing a bad data model is slower than building a good one from scratch — and you're paying someone to do both.
Twelve more months of manual order entry, stockouts you didn't see coming, and a month-end close that takes two weeks. That number is almost always larger than the implementation itself.
The second attempt runs into resistance that has nothing to do with the software. You've spent credibility you can't buy back, and the people who have to use it every day have already decided it won't work.
This is the entire reason we build 70% of your system before you pay us. Not generosity — scope guessing is what makes these projects fail, and we would rather delete the guess than manage the fallout. It's also why we can put a fixed number in a contract and mean it.
Every Odoo project is priced on complexity, and anyone who quotes you a number on day one is guessing. You'll pay for that guess later, as change orders. So we do it in this order instead:
This is a multi-month engagement with a dedicated team, not a weekend install — so it isn't the cheapest way to get Odoo running, and we won't pretend otherwise. You'll get real numbers in the first 30 minutes, not after three meetings. Odoo licence fees are separate and paid directly to Odoo.
Building a free working system takes real engineering hours, so we only run a few at a time. A typical build runs a few months after that — which means a January 2027 go-live starts with a conversation now.
Claim a free build slot30 minutes, no deck. We'll give you honest cost ranges for a company your size and tell you whether now is the right time — including if the answer is no.