NDIS equipment supply breaks generic ERP in two specific places: billing that has to satisfy the NDIS rather than just the customer, and rental fleets made of assets that come back rather than stock that gets consumed. Odoo handles both, but not out of the box. This page covers what actually makes NDIS supply different, what has to be configured, and where the limits are.
Why NDIS billing is not ordinary invoicing
In most distribution, an invoice goes to whoever bought the goods. In NDIS supply, who you invoice depends on how the participant's plan is managed, and getting it wrong means the claim is rejected rather than merely late.
- Agency-managed participants have claims submitted to the NDIA directly through the provider portal. You are not invoicing the participant at all.
- Plan-managed participants have a plan manager who receives and pays the invoice. Different recipient, different format expectations, different payment terms.
- Self-managed participants pay you directly and claim it back themselves.
Three payment paths for the same product to three participants. A system that treats the participant as the customer will get two of them wrong.
On top of that sits support item numbering. Every supported item and service has a support item number, and price limits are set by the NDIA's Pricing Arrangements and Price Limits, which are revised periodically. Charging above the limit means the claim fails. Charging below it means you have quietly given away margin.
Assistive technology adds a further layer, with quoting and assessment requirements that vary by the value and complexity of the item.
What this means in practice
The configuration that matters is putting the funding logic in the system rather than in a person.
- Products carry their support item number and funding category, so the correct code appears on the claim automatically
- The participant record carries the plan management type, so the invoice routes to the right party without anyone deciding
- Price limits are held against the product rather than remembered, so a quote cannot be written above them
- Service bookings and plan dates are visible at the point of quoting, so nobody supplies against a plan that has expired or run out of funding
None of that is exotic ERP functionality. It is ordinary configuration applied to a domain that has more rules than most. The reason it goes wrong is that generic implementations do not know the rules exist.
Rental fleets are assets, not stock
This is the second thing generic ERP gets wrong, and it is structural rather than a configuration gap.
Standard inventory assumes stock is consumed when it is sold. A hospital bed, a mobility scooter or a ceiling hoist goes out, comes back, gets serviced, and goes out again, possibly for years. Each unit needs its own identity, not just a quantity on hand.
What that requires:
- Serial-level tracking. Not "twelve beds in stock" but which bed is with which participant, and which is in for repair.
- Service history against the asset. Maintenance, safety checks and repairs recorded against the unit, not the product line. This is what makes an incident defensible.
- Utilisation reporting. A fleet that sits idle is capital doing nothing. You cannot see that without asset-level history.
- Recurring rental billing. Daily, weekly or monthly periods generating claims automatically, against the right funding category.
The awkward part is that a rented item is two things at once: an asset on your balance sheet, and a service being claimed against a participant's plan. In a generic build those two facts live in different modules and never reconcile.
The rest of the operation
Once billing and rentals are right, the remaining pieces are conventional and Odoo covers them natively.
Warehouse. Multi-location and multi-bin, barcode scanning, putaway rules, batch and serial tracking, replenishment rules.
Field service. Job scheduling and dispatch, technician mobile access for checklists, signatures and photos, with completion updating the rental and service records rather than requiring a second entry.
Occupational therapist relationships. OTs drive referrals, and the relationship is with them as much as with the participant. Recording OT interactions and linking them to participant records and orders means context survives staff turnover.
Mobile quoting. Reps quoting from a phone or tablet in the room, with product availability and plan information visible, rather than writing up quotes that evening.
The Ooda Healthcare Suite
We have packaged the NDIS-specific configuration as the Ooda Healthcare Suite, built on Odoo. It covers the funding category and support item structure, the rental module with barcode asset tracking and period-based invoicing, OT and participant relationship tracking, and field service integration.
It exists because we kept building the same configuration for equipment suppliers, and rebuilding it each time was neither fast nor cheap for the client.
What it does not solve
It does not remove the need to know the rules. The system enforces what you configure. If your understanding of a support item category is wrong, the system will apply it wrongly and consistently.
Price limits change. The Pricing Arrangements and Price Limits are revised, and product pricing needs updating when they are. That is a maintenance task, not a set-and-forget.
It is a configuration project, not an install. Anyone offering NDIS compliance working on day one with no configuration budget is describing something that does not exist.
It will not fix a broken product catalogue. If support item numbers are not attached to products at migration, the claiming logic has nothing to work from.
How we work
Ooda Consulting is based in Sydney at Level 6/201 Kent St and works with SMEs across Australia and New Zealand. We have delivered Odoo implementations for NDIS and healthcare equipment suppliers, and Ooda's Odoo developers hold Odoo certification, current to version 19.
See Odoo for Healthcare and Aged Care for the multi-scheme billing and rental configuration, Odoo ERP Implementation for how a build is scoped and staged, or Why do most Odoo and ERP projects blow out? for what goes wrong when it is not.
Frequently asked questions
Can Odoo handle NDIS billing?
Yes, with configuration. Support item numbers and funding categories attach to products, and plan management type attaches to the participant so invoices route to the NDIA, a plan manager or the participant automatically. It is not enabled out of the box and requires deliberate setup.
What is the difference between agency-managed, plan-managed and self-managed for invoicing?
Agency-managed claims go to the NDIA through the provider portal. Plan-managed invoices go to the participant's plan manager. Self-managed participants pay you directly. Same product, three different billing paths, which is why plan management type has to be held on the participant record rather than remembered.
Can Odoo manage an equipment rental fleet?
Yes. Serial-level tracking gives each unit its own identity, service history attaches to the asset rather than the product line, and rental invoicing generates by period. This is the main reason equipment suppliers outgrow generic inventory systems.
Why does generic ERP struggle with NDIS equipment supply?
Two reasons. Standard inventory assumes stock is consumed on sale, which does not describe a rental fleet that returns and is serviced. And ordinary invoicing assumes the customer pays, which is only true for self-managed participants.
Does the system keep up when NDIS price limits change?
Price limits are held against products, so updating them is a maintenance task when the Pricing Arrangements and Price Limits are revised. The system enforces whatever is configured, which is why the update has to be scheduled rather than assumed.
How long does an NDIS equipment supplier implementation take?
It depends on fleet size, how much of the product catalogue already carries support item numbers, and whether field service is in scope. The billing and rental configuration is the substantial part; the warehouse and CRM sides are conventional.
