One database
Sales, stock, purchasing and accounting share the same products, partners and journals, so a quote, a stock move and a ledger entry are the same data, not three copies.
BIR noticeCAS and CBA users register their 2026 computerised books online through ORUS by 30 January 2027 (calendar-year taxpayers).Computerised books: register in ORUS by 30 Jan 2027.
CAS set-up in Odoo
Partner in Singapore · teams in Taguig City & Ho Chi Minh City
Standard Odoo first. It's one database across every department, with modules switched on as you need them. Where your process genuinely differs, we build the Odoo 20 module, workflow or report you need, in a way that survives version upgrades and that another developer could maintain.
RequirementFive sample requirements, placed
Upgrade riskLow
EffortModerate
MaintenanceLow
Each change sits on the lowest layer that can carry it. Upgrade test passed on the next version.
Sample requirements. The meters are relative, not estimates.
Odoo customization at TechNext starts from standard Odoo: one database across every department, with apps switched on as you need them. Where your process genuinely differs, we build the module, workflow, report or approval you need, in a way that survives version upgrades and that another developer could maintain.
Every change TechNext makes to Odoo lives on the lowest layer that can carry it: standard features, then configuration, then Studio, and only then a custom module on Odoo.sh or an integration. Drag a requirement onto a layer, or press Suggest to run the decision tree, and watch the upgrade risk, effort and maintenance move.
All eight placed. Run the upgrade test to see what each layer costs at the next version.
Odoo standard: a customer portal where customers download their orders and invoices is standard Odoo.
Configuration: a purchase approval above S$5,000 is a Purchase setting; a trade price of 12% off from 50 units is a pricelist rule.
Studio: a new field on the delivery slip and an invoice layout with your own columns are Studio work, with no code.
Custom module on Odoo.sh: a tiered, split sales commission with clawback and a multi-level approval matrix with delegation need a separate, tested module.
Integrations: a nightly sync with a legacy system is an integration, with mapping, scheduling and error handling.
Each step up the stack adds upgrade risk, effort and maintenance, so the decision tree asks in order: does standard do it, can configuration, can Studio, and does it involve another system.
Sample requirements. The meters are relative, not estimates; the right layer for your case is confirmed in discovery, for your version and edition.
Standard first: each piece below is altered only where your process genuinely differs.
Sales, stock, purchasing and accounting share the same products, partners and journals, so a quote, a stock move and a ledger entry are the same data, not three copies.
Switch on Accounting, Sales, Inventory, Purchase, CRM and more only when you need them. The core stays the same as you grow.
Extra fields, tidier screen layouts, and quotation and invoice templates in your branding, plus the regulatory print-outs you have to produce.
Multi-level approvals, automated actions and validations that stop a wrong entry before it posts, not after.
Management reports, margin analyses and dashboards on live Odoo data, so leadership reads one set of numbers.
Processes standard Odoo doesn't model, built as a separate module so the core stays clean and upgradable.
Four steps, in this order. Each one climbs only as far as the last one showed it must.
Map your flows and decide what standard Odoo covers and what genuinely differs.
Chart of accounts, taxes, warehouses, pricelists and approvals set in Odoo's own features.
Separate modules, workflows and reports, version-controlled, reviewed and tested.
Choose Odoo Online, Odoo.sh or on-premise; then migrate, train and support.
Where Odoo runs is a scoping decision, not a default. We size the edition and hosting with you, then keep every customisation upgrade-safe, because custom code is a liability we deliberately keep small.
One database where sales, stock, purchasing and accounting share the same records, instead of separate apps that don't talk to each other and have to be reconciled by hand.
No. Modules are switched on as you need them. Most companies start with Accounting, Sales and Inventory and add more as they grow.
Odoo Online for the fastest start on standard apps, Odoo.sh when you need custom development, or on-premise / your own cloud when data residency or existing infrastructure decides it. We help you choose.
We build to keep upgrades manageable; each upgrade is still tested on staging. Customisations live in separate modules, are tested and documented, and never edit Odoo's own code, so the upgrade path is easier to plan.
Odoo licences are billed by Odoo per user per month. Our implementation and customisation work is quoted separately, so you can see each part clearly.
On quotation, scoped to the apps, data and customisation you need: request a quotation.
We'll say which apps to switch on first, what standard Odoo already covers, and what genuinely needs building.