How much does a custom Odoo app cost?
By Tal Oz, OdooWebApps. Published 18 September 2026.
What does a custom Odoo app cost? The short answer
On this site, from $390 for a single focused screen and typically $490-$890 for a polished multi-screen app built around one workflow. Those are real starting prices for apps that sit next to Odoo and talk to it through its API, not ranges invented for a pricing page. Bigger systems are quoted individually. The table below is the whole price list.
| App | From | What that covers |
|---|---|---|
| Custom single workflow | $390 | One screen, one Odoo model, one clear action. An approval, a simple report, a small data entry tool |
| Management dashboard | $490 | Read-only KPIs and charts from live Odoo data. No writes, so the least risk and the least validation work |
| Warehouse picking app | $590 | Mobile picking against stock.picking, writing quantities back. One warehouse, one operation type |
| Sales ordering app | $690 | Customer, products, submit. Creates and confirms real sale orders from a phone |
| Supplier portal | $790 | External users, purchase orders, confirmations written back to Odoo |
| Customer ordering portal | $890 | Authentication, a per-customer catalogue and prices, checkout into Odoo Sales |
| Bigger idea | Quoted | Several apps, several user roles, or work inside Odoo as well as outside it |
How does that compare to an Odoo module or an implementation?
These are three different things that get quoted very differently, and mixing them up is why cost research on Odoo is confusing. A licence is what you pay Odoo. An implementation is configuring Odoo for your business. A custom module changes Odoo from the inside. A connected app leaves Odoo alone and adds one screen next to it.
| Typically priced as | Who does it | What it changes | |
|---|---|---|---|
| Odoo licence | Per user per month, from Odoo | Odoo | Nothing; it is the subscription |
| Implementation | Day rate or fixed project, usually five figures | Partner or integrator | Your Odoo configuration and data |
| Custom module | Day rate, per module | Odoo developer or partner | Code inside your Odoo database |
| Connected app | Fixed price per app, from $390 to $890 here | A studio like this one | Nothing inside Odoo; one app beside it |
Quotes you see elsewhere are often hourly. At the rates Odoo freelancers and partners commonly charge, a fixed price of $590 for a picking app is a small number of days of work, which is exactly what it is. The reason it can be a fixed number at all is the narrow scope: one workflow, one or two Odoo models, no reimplementation.
What actually moves the price within a tier?
| Driver | Cheaper | More expensive |
|---|---|---|
| Reads or writes | Read-only display | Creates and confirms records in Odoo |
| Screens | One screen | A flow across several screens |
| Odoo models | One model | Several models with relations between them |
| Users | Internal staff on one company | External users, several roles, multi-company |
| Edge cases | Happy path only | Partial stock, backorders, lots and expiry, concurrent edits |
| Data quality | Clean, consistent Odoo data | Configuration that has to be fixed first |
The one people underestimate is the first row. A read-only dashboard that is slightly wrong is a trivial fix and nothing in Odoo is at risk. An app that creates sales orders or updates stock has to handle a write failing partway, data that does not satisfy Odoo's own validation, and two people acting on the same record at once. That care is the difference between the low and high end of any estimate; see read-only vs write-back integrations.
Why is 'it depends' the usual answer everywhere else?
Because most Odoo work quoted online is implementation work, where the scope genuinely is open-ended: how many modules, how much data migration, how many people to train. That is a real reason for a range. It stops being a good reason when the question is much smaller, as it is here: one workflow, one screen or two, a handful of Odoo models. At that size the honest answer is a number, which is why the table above exists.
What pushes a project into 'let's talk' territory?
Anything that stops being one focused workflow: multiple integrated apps, a system with several distinct user roles each seeing different data, or a workflow that turns out to need changes inside Odoo itself (a custom module) in addition to the external app. These are quoted individually rather than against a fixed tier, because at that scope the cost genuinely depends on specifics that a landing page can't responsibly generalize.
What's the single biggest cost driver most people underestimate?
Whether the app needs to write back to Odoo, and how carefully. A read-only dashboard just displays numbers. If a query is slightly wrong, the fix is trivial and nothing in Odoo is at risk. An app that creates sales orders, confirms purchase orders, or updates stock has to handle what happens when a write fails partway through, when the data submitted doesn't actually satisfy Odoo's own validation, and when two people try to act on the same record at once. That extra care is real engineering time, and it's usually the difference between the low end and the high end of a given app's estimate.
How is a final number actually reached?
Through a short scoping conversation about the actual workflow: which Odoo models it touches, how many screens, read-only or write-back, how many user roles. That's a more useful process than a generic quote calculator, since two projects with the same one-line description can have meaningfully different scope once the details are on the table.