Enterprise RAG implementation guide: architecture, steps and best practices
What RAG is, the reference architecture for enterprise RAG, the build steps, common failure points and how to measure answer quality.
DeadlinesE-Invoicing by Dec 31, 20262026 Computerized Books in ORUS by Jan 30, 2027E-Invoicing Dec 31 · ORUS Jan 30
Check ReadinessEvery customisation is paid for twice: once when it is built, and again at every upgrade. This is how TechNext decides what to configure, what to build in Studio, and what deserves custom code.
By TechNext · · Updated · 4 min readTechNext & Odoo
Key takeaways
"Can Odoo do it exactly the way we do it now?" is the question behind most customisation requests. Often the honest answer is: it could, but it shouldn't. Standard Odoo encodes how thousands of companies run sales, stock and accounting, and bending it to match an old habit usually costs more than changing the habit. That is why TechNext works standard first. It is not a refusal to customise. It is a rule about what earns the right to be customised.
| Level | What it is | Cost at upgrade |
|---|---|---|
| Configuration | Settings, workflows, taxes, routes, approval rules, templates and access rights | Low: carried forward by Odoo |
| Studio | No-code fields, views, reports and automations (Custom plan) | Medium: needs checking after each upgrade |
| Custom modules | Python code for new logic, integrations or apps (Odoo.sh or on-premise) | High: must be ported and tested every version |
Odoo ships a major version every year, and Odoo 20 has just arrived. Each custom module has to be ported to the new version and retested, and each Studio change checked, before a company can upgrade. A database with dozens of customisations can end up stuck on an old version because upgrading it has become a project of its own.
If a request survives all five, it is worth building, and worth building properly: as a clean module in version control, tested on staging and documented, rather than as a quick patch.
Five questions before approving any customisation: does standard Odoo do it; could the process change instead; can Studio do it without code; what does it cost to maintain through the next three upgrades; and who owns it. Configuration costs least at upgrade, Studio needs checking after each upgrade, and custom modules must be ported and tested every version.
During discovery, every gap between your process and standard Odoo is written down with a proposed answer: configuration, Studio, a process change or a custom module. You see the trade-off before anything is built. Custom modules are built on staging, kept in version control and included in upgrade testing, which is part of our support plans. When a client asks for tailored modules and workflows, that work sits under our ERP customisation service, with the same rules.
The result is a system that fits the business and still upgrades cleanly. You can read how the whole project runs in How an Odoo implementation works.
Configuration uses the settings and options Odoo already has, such as taxes, workflows and approval rules. Customisation changes the software itself, either with Odoo Studio (no code) or with custom Python modules.
Yes. Odoo releases a major version every year, and custom modules must be ported and retested for each one. Studio changes need checking too. The fewer customisations, the easier each upgrade.
Yes, when a requirement justifies it. TechNext builds custom modules on staging, keeps them in version control and includes them in upgrade testing, after checking that configuration or Studio can't do the job.
About TechNext. TechNext Pte. Ltd. is a BIR compliance and integration partner for accounting firms and finance teams: an Odoo Ready Partner headquartered in Singapore, with its main development and consulting hub in Taguig City, Metro Manila. We plug Odoo into the system you already run, and our own experts implement it end to end (discovery, configuration, data migration, training and support), set up with the Philippine (BIR) and Singapore (GST) localisations, for clients in 25+ countries. We are not affiliated with, accredited by or acting for the BIR or any government agency, and we do not file or register on your behalf. About us · Get my custom blueprint
What RAG is, the reference architecture for enterprise RAG, the build steps, common failure points and how to measure answer quality.
Discovery, staging, data migration, training, integration and support: what happens at each step, and what your team brings.
Who hosts it, whether custom modules are allowed, how upgrades work, and which plan each option needs.
TechNext sets up your Odoo, can build your website and brand on it, and stays on after go-live, in Singapore and the Philippines. An adviser reviews your situation first.
2027 BIR Audit Guide · sent by our team
Four details. A BIR Compliance Expert sends the guide to your work email within one business day. Inside: the eLA rules, the 10-day document rule, what examiners ask for, and a routine for audit requests.