Custom portal development: when to build vs. use your ERP's built-in portal
Most buyers do not need a fully custom portal. Check what your ERP's built-in portal already covers before scoping a custom build on top of it.
"Custom portal development" gets scoped as a full custom build far more often than it needs to be. Before paying for one, check what your existing ERP or CRM already gives you for free, because the built-in option covers more buyer needs than most people assume.
What a built-in portal already covers
Odoo's customer portal, included with every plan, lets customers log in to view and pay invoices, track order and delivery status, approve quotes, and raise support tickets, all without being billed as a full Odoo user. For a straightforward "let my customers see their own orders and invoices" requirement, this is usually enough, and it is already live the day you implement Odoo. GoHighLevel offers a comparable client portal for appointments, invoices and messages. Check this first; a custom build to replicate what your platform already ships for free is money spent on nothing new.
When a custom portal is actually worth it
- A different login experience your customers expect, for example a branded app rather than a page inside your ERP's interface.
- Data from more than one system in a single view: ERP order status next to support tickets from a separate helpdesk tool, for instance.
- A workflow your platform does not model, such as a multi-step approval process specific to your industry.
- Scale or performance needs that the built-in portal's design was not built for, such as thousands of concurrent self-service users.
If none of these apply, the built-in portal is very likely the right answer, and the project is a configuration task, not a development project.
How a custom portal should be built, if you need one
Put a small back-end service between the portal and your ERP or CRM. Customers log in through a dedicated authentication provider, the back end identifies which account they belong to, and every request is filtered to that one customer's data before anything reaches the browser. API keys and credentials stay server-side; they never reach client-side code. For Odoo specifically, new integrations should use the External JSON-2 API, since the older XML-RPC and JSON-RPC endpoints are deprecated, and external API access on Odoo Online requires the Custom plan, which is worth confirming before scoping work against it.
Cost and timeline
A custom customer portal with authentication, ERP/CRM integration and a handful of core screens (orders, invoices, support) typically starts from the low tens of thousands of dollars and takes 8-14 weeks, depending on how many systems it needs to connect to and how much custom workflow logic it has to encode. That is a meaningful cost next to a built-in portal that already exists; make sure the gap it closes is worth it before committing to the build.
Frequently asked questions
Does Odoo's built-in portal cost extra?
No. The customer portal is included with every Odoo plan, and portal users (customers logging in to view their own data) are not counted or billed as Odoo internal users.
Can I extend Odoo's built-in portal instead of building a separate one?
Yes, in many cases. Odoo's portal can be customized to show additional fields or sections through standard module development, which is usually cheaper than building a fully separate portal application, as long as you stay inside Odoo's own interface.
What authentication should a custom portal use?
Use a managed authentication provider rather than building login from scratch, and test explicitly that no customer can reach another customer's records by guessing or modifying an ID in the URL or request.
How do I know if my ERP's portal is "enough"?
List the specific actions your customers need to take (view invoice, pay online, check order status, raise a ticket) and check each one against your ERP's documented portal features before assuming you need a custom build. Most straightforward self-service needs are already covered.
Thinking about a custom web app?
Get a scope, a price range and a timeline in a free 45-minute meeting.
Sources
Keep reading
ERP and app development: one partner or two?
Splitting ERP and custom app work across two vendors adds an integration risk most buyers underestimate. Here is when one partner is worth it, and when it is not.
Web appsHow much does a custom web app cost in 2026?
Custom web apps typically start from $8,000 for an internal tool and run to $60,000+ for a full platform. Here is what drives the price and what you pay after launch.
Web appsCustom web app vs off-the-shelf software: when to build
Buy software when it fits most of your process, build when the process is your edge or customers need your data. Here is how to decide, with a three-year cost view.