Instead of Odoo
Stop paying Odoo per user, per month. Own your workshop system.
Enterprise DNA shapes your version to the way your shop quotes, builds and bills, carries your Odoo products, partners and open orders across, and keeps it running for you. Nobody is counted as a seat.
Odoo's published pricing in Australian dollars: Standard is AUD 54 per user a month billed monthly or AUD 43 billed yearly; Custom, which adds Studio, multi-company and the external API, is AUD 100 per user a month billed monthly or AUD 80 billed yearly. Implementation and custom code are extra.
- check_circleYour data in a database you own
- check_circleOpen source, no lock-in
- check_circleBuilt and run by Enterprise DNA
Where the per-user fee goes
An Odoo bill grows with headcount, apps and changes
At list price a single user on Standard costs AUD 648 a year billed monthly, and on Custom AUD 1,200 a year. Multiply by everyone who logs in, then add the partner. Underneath it all are your products, customers, suppliers, work orders and invoices.
The free plan stops at one app
You will want Purchase and Sales beside Manufacturing. A second app moves the whole company onto a paid plan, charged per user.
Most people who log in are a full fee
The owner glancing at the numbers is a user too. The Light User add-on is quoted only after a meeting with an Odoo advisor.
Changes live on the dearer plan
Studio, the tool for adding your own fields and screens, along with multi-company and the external API, is on Custom. Standard cannot run custom modules at all.
Implementation is a separate purchase
Odoo lists implementation, expert services and maintenance of custom code as not included in any plan. Small firms are pointed at Success Packs, with no price on the pricing page.
Hosting your own code costs again
Run custom work on Odoo's developer platform and its hosting is billed on top of the Custom plan, as the page notes.
A discount that runs out
The lower first-year prices apply for 12 months and only to the users ordered at the start. Year two, and every new hire, is at full price.
What you get instead
One workshop system, priced by nothing
Seats
The whole floor, no per-user meter
Estimator, store, office and owner all work in the same records, and adding a person adds nothing to the bill.
- check No user count, no app count, no plan to move up to
- check Quotes, jobs, stock, purchasing and costing come together, not as separate apps
- check Each person asks their own question in plain English and gets the answer from shared data
- check A hire, a casual or a contractor costs nothing to add
Jobs
Promise dates you can stand behind
Every open job against the date the customer was given, with what is holding it and what has stalled.
- check Jobs past their promise date, counted in days late
- check Material short per job, beside the purchase order due to cover it
- check Supplier orders overdue, with the job each one is blocking
- check Jobs where nothing has been issued or booked for a week
Costing
Margin on each job, not a month-end guess
Issued material, booked hours and outwork add up to one cost figure that the job board, billing and work in progress all read.
- check A warning when a fixed-price job has used 80% of its quote and is still open
- check Work in progress on any day: cost in open jobs with no invoice against it
- check Completed work that has not been invoiced stays on the list until it is
- check Construction work drafted as a payment claim, with retentions chased on their due date
Change
Reshape it in a sentence
The thing Odoo puts behind Studio and the Custom plan is a plain request here, and your records stay in a database the business controls.
- check Ask for a new field, a renamed status or a new rule and it is added for you
- check Quotes, invoices, job travellers and cost reports printed under your own name and logo
- check Traceable steel gated by heat number before it goes to structural work
- check MIT licence: no subscription, no renewal date, nothing to give notice on
Make it yours
Design your own Odoo replacement
Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Odoo. Try it here, and we build the real one.
2. What it runs
3. Make it fit
4. Your colour
Answered from your own database
Good morning. Here is what needs you today.
We build it from the open-source base, bring your Odoo data across and run it for you.
Switching
How to switch from Odoo
The move involves exporting the workshop records you need, mapping Odoo’s fields to Job Shop, and deciding how much history to bring across.
- 1
Export your Odoo records
In Odoo, open a list, select the records, then choose Export from the Action menu. Pick the fields you need and save the export as a spreadsheet. Start with the workshop records you plan to use, such as contacts, products, purchase orders and manufacturing orders. You can save a field list as a template and reuse it. Check with Odoo if you are unsure which records your account allows you to export.
- 2
Load a test copy
Odoo names its columns differently from Job Shop, so the exports will not load unchanged. Have the fields matched to Job Shop’s records, then test the import against a copy before using it for your live data. When Enterprise DNA installs and runs Job Shop for you, they handle this matching and trial. If you are doing the move yourself, confirm how your import setup handles the Odoo spreadsheets before loading the full set.
- 3
Review the test results
Check the test results for records or fields that could not be matched, and resolve those before proceeding. Compare the records loaded with the records you exported, including a sample of contacts, products, purchase orders and manufacturing orders. Check that the details you rely on, such as item codes and job information, appear correctly. Decide which older records you need in Job Shop and which can stay in Odoo for reference.
- 4
Run both systems briefly
Keep Odoo running while you start using Job Shop for workshop work. For a short period, check the records and figures you rely on in both systems, including quotes, jobs, stock, purchasing and job costing. Note any gaps or differences and correct the mapping or records before you make Job Shop the working system. Keep the period focused so you can make a clear cutover decision.
- 5
Switch off Odoo carefully
Once you have checked the records you need and are using Job Shop for workshop work, plan the Odoo shutdown. Job Shop replaces the workshop side, not every Odoo app. If Odoo also holds your accounting ledger or website, arrange what happens to those separately before switching it off. The ledger can move to Xero or MYOB, with invoices drafted in Job Shop and sent through your accounting system.
Where the real effort goes
The export is usually not the main work. The time goes into matching Odoo’s fields to your records, adapting your own fields and rules, and choosing how much history to bring across. A clean starting set and a full archive are different choices. When Enterprise DNA installs and runs Job Shop for you, they handle the mapping and trial on a copy before the live move.
Not ready for a call?
Get your Odoo switch plan by email
We will send you the step-by-step plan for moving your business off Odoo, what the move really involves, and how we would do it for you.
Sent. Check your inbox.
Your Odoo switch plan is on its way.
Rather talk it through? Book a call arrow_forwardTwo ways to start
Run the free version, or let Enterprise DNA build and run yours
Open source
Do it yourself
Free
- 1 Download Job Shop for Claude Code from GitHub
- 2 Load the demo workshop and open it in Claude Code
- 3 Ask what needs attention today
- 4 Map your Odoo spreadsheet exports in when you are ready
Omni by Enterprise DNA
Have Enterprise DNA build and run it
One setup fee, then a monthly retainer
- check We move your Odoo products, customers, suppliers and open work across, checked against the old system
- check Your bills of materials, work centres, rates and costing rules set to match your floor
- check A link to Xero or MYOB so drafted invoices flow into it
- check Run for you inside Omni, our managed Command Center, alongside the rest of the business
Questions
Instead of Odoo, answered
Odoo has a free open-source edition. Why not just use that? expand_more
You can, and some shops do. The free edition still asks you to host a large system, keep it upgraded and pay a partner for any change, and several features sit only in the paid edition. Job Shop for Claude Code is far smaller, built for a fabrication or engineering shop, and you change it by asking rather than by hiring a developer.
How do we get our records out of Odoo? expand_more
Odoo's own documentation shows the way: open any list, select the records, choose Export from the Action menu, pick the fields and save as a spreadsheet file. You can save the field list as a template and repeat it for products, contacts, purchase orders and manufacturing orders.
Will an Odoo export load in as it is? expand_more
No. The free version's import reads a different system's layout, and Odoo names its columns its own way. Matching them is part of the work when Enterprise DNA builds your version, always trialled on a copy first so nothing goes missing.
We only pay for a handful of users. Is it worth moving? expand_more
Maybe not on the subscription alone. The case is strongest when partner days, custom code and the step to Custom outweigh the seats, or when the reports never answer what the owner asks. We will say so plainly on the call if staying put is the better choice.
Odoo also runs our accounts and website. What happens to those? expand_more
This replaces the workshop side: quotes, jobs, stock, purchasing and costing. Your ledger can move to Xero or MYOB, with invoices drafted here and sent through it. If you want something else replaced too, that is a conversation for the call.
Stop paying for every login to your own workshop
Thirty minutes with Sam. We add up what Odoo costs you across users, apps, the plan you need and partner time, look at how your shop really quotes, builds and invoices, and sketch what your own version would be. If it fits, we build it. If not, the free version is yours to run.
Job Shop for Claude Code is free and open source, published by Enterprise DNA.
Done paying for Odoo?
Get your version built