It does the job. It stays.
If a system works and your team can run it, we say so, and connect what needs connecting.
ADUNO
We modernise the platforms that run orders, stock and invoicing for Australian organisations of 30 to 500 users. We decide what to keep, what to modernise and what to replace. When replace is the answer, we implement Odoo. Where Shopify is already how you win, it stays.
If a customer emailed an order tonight, could your system check the stock and the credit and raise the order by morning, or would someone still retype it?
Sound familiar?
None of that needs a slogan. It needs a decision on each system, and a plan your finance team will sign off.
Three outcomes
If a system works and your team can run it, we say so, and connect what needs connecting.
A supported version, tidy data, integrations that don't depend on a CSV, and a process people can follow.
When the order, the stock and the invoice live in too many places, we move them onto Odoo. For a product business whose shop is not already a winning Shopify store, this is a common outcome. It is not where we start.
One order, end to end
Illustrative sample, not a client engagement. Supplier invoices matched to the purchase order and the goods receipt follow the same pattern.
How we work
A short assessment, fixed once it is scoped in writing. We map your systems, data, processes and integrations, draw one future order path that names the steps the system runs and the step a person takes, and make a keep, modernise or replace call on each system, including whether Odoo should be the shop. The plan is yours whether or not we do the work.
In phases, with the gates written down: scope before configuration, standard Odoo before custom code, a staging copy, opening balances that reconcile, training on your own data, and cut-over at a period boundary. Dates come out of the assessment.
The same people after go-live: the first month-end, fixes, upgrades, and the next Odoo app once the first phase is stable, quoted on its own.
Two bills
Odoo licences are priced per user by Odoo and billed by Odoo separately. Our work is quoted in writing from an agreed scope. We don't publish a starting price: a number without your users, your data and your systems attached would not mean anything.
Common questions
No. There are three outcomes: keep, modernise and replace. The assessment makes the call on each system, and it is allowed to say keep. If you sell online, the Shopify rule applies as well.
If Shopify is how you are winning, it stays, and Odoo runs the stock, the orders and the invoicing behind it. If there is no such shop, Odoo can be the shop. More on ecommerce.
The order, the stock valuation and the invoice, and the accounts they post to. Not payroll, Single Touch Payroll or pay runs, unless that is scoped in writing.
We work with organisations of about 30 to 500 users. If you are either side of that, the first conversation will tell us both.
No. The work is quoted in writing once the scope is agreed. Odoo licences are billed by Odoo, separately.
Odoo can run on Odoo Online, on Odoo.sh, or on infrastructure you control. The hosting option and region are chosen in the assessment and written into the scope.
Odoo's own AI features are Odoo's product, metered and billed by Odoo. We can switch on the ones that fit, with a person approving anything that moves money. One clean system is also where agents work best later. Designing, governing and costing that work is our sister AI practice; see About.
Get started
A conversation first, with no obligation. Tell us what runs your orders, stock and invoicing today, and where it hurts.