A wholesale or field-service business can appear busy while losing control of margin. Sales promises stock that is already reserved. Buyers place urgent orders without seeing future demand. Technicians complete work but parts and labour reach finance late. Returns sit in a corner of the warehouse. Invoices are delayed because the delivery or service record is incomplete.
Odoo can connect CRM, Sales, Purchase, Inventory, Field Service and Accounting in one environment. The value is not simply having the applications together. It is creating a reliable chain from customer promise to physical delivery, completed work and financial result.
For Melbourne businesses distributing products, installing equipment or maintaining customer assets, that chain should be the centre of the ERP design.
Define what the business is promising
A quotation may promise a product, a delivery date, an installation, a maintenance visit or a bundled outcome. The system needs to distinguish each commitment.
Before configuration, classify sales lines as:
- stocked products;
- products purchased for a specific order;
- assembled or manufactured items;
- installation or delivery services;
- scheduled field-service work;
- recurring maintenance or subscription services;
- expenses or materials billed after work.
This classification affects availability, purchasing, task creation, delivery and invoicing.
Make availability understandable to sales
“In stock” can mean several things. The warehouse may physically hold ten units, but eight are reserved and another customer needs five next week. Sales should not rely on a single on-hand number.
The design should make users understand:
- on-hand stock;
- reserved stock;
- forecast availability;
- incoming purchases;
- customer-specific allocation;
- blocked or damaged stock;
- stock at other warehouses or vans.
Odoo’s inventory planning uses forecast quantities and replenishment mechanisms. The official reordering-rule documentation explains how minimum and maximum quantities can trigger purchase or manufacturing actions.
Reordering rules should not be copied across every product. They should reflect demand pattern, supplier lead time, order multiple, carrying cost and service importance.
Use different replenishment strategies for different items
A Melbourne distributor may carry fast-moving local stock, imported products, spare parts and expensive items purchased only after an order. Each group needs a different policy.
| Item type | Possible strategy | Control focus |
|---|---|---|
| Fast-moving stock | Minimum and maximum reordering. | Forecast quality, lead time and safety stock. |
| Imported long-lead item | Planned replenishment with larger review horizon. | Shipping time, supplier reliability and cash tied in stock. |
| Customer-specific item | Replenish against confirmed demand. | Link purchase to customer commitment and deposit. |
| Critical spare part | Service-level based minimum stock. | Cost of downtime versus carrying cost. |
| Slow expensive item | Manual review or make-to-order. | Avoiding obsolete stock. |
Management should review exceptions: emergency purchases, stockouts, excess stock and repeated manual overrides.
Measure suppliers by more than price
Supplier records should capture the information needed to make reliable buying decisions:
- approved products and pricing;
- minimum order and pack size;
- lead time;
- currency;
- freight or landed-cost assumptions;
- actual delivery performance;
- quantity and quality differences;
- return and warranty terms.
A supplier with a lower unit price may create higher total cost through late delivery, poor quality or administrative effort.
Design receiving as a control point
Receiving should confirm what physically arrived, not merely close a purchase order. Depending on the business, the process may include:
- count and condition check;
- serial or lot capture;
- quality hold;
- backorder creation;
- supplier discrepancy;
- put-away location;
- landed-cost information;
- attachment of delivery documentation.
Users need a clear process for partial receipts and unexpected substitutions. Forcing the system to match a perfect purchase order encourages inaccurate confirmations.
Connect field service to inventory
Technicians may carry parts in vans, collect them from the warehouse or order them for a specific job. If material use is recorded later, stock and job profitability become unreliable.
Odoo includes field-service capabilities for tasks, products, worksheets and operational planning. Its official Field Service documentation provides the application overview.
A practical service workflow should define:
- how the service request is created;
- how equipment, customer site and warranty are identified;
- how the technician is assigned;
- which parts are reserved or loaded;
- how travel, labour and materials are recorded;
- how customer acceptance is captured;
- what makes the work billable;
- how follow-up or return visits are handled.
Technicians should not need to become accountants. The mobile workflow should capture the operational facts finance requires.
Separate service completion from invoice readiness
A task may be operationally complete but not ready for invoicing. The customer may need to sign a worksheet, a purchase-order reference may be missing or included warranty work must be separated from chargeable work.
Use explicit states such as:
- work scheduled;
- work in progress;
- technically complete;
- customer acceptance received;
- commercial review required;
- ready to invoice;
- invoiced.
Each state should have an owner and entry criteria. This prevents completed work from remaining invisible to finance.
Build job profitability from source transactions
Profitability should include more than invoice value minus part cost. Depending on the business, it may require:
- product cost;
- freight or landed cost;
- technician labour;
- subcontractor cost;
- travel and accommodation;
- warranty or rework effort;
- discounts and credits;
- unbilled time and material.
If these costs are not captured against the customer, order, project or task, a later dashboard cannot calculate them accurately.
Handle returns as a traceable process
Returns affect customer service, inventory and finance. The system should distinguish:
- customer changed mind;
- incorrect item supplied;
- damage in delivery;
- warranty claim;
- supplier defect;
- repairable item;
- scrap or write-off.
The return should link to the original delivery where possible. The receiving location, inspection, replacement, supplier claim and credit decision should be visible.
Configure Australian GST and BAS with professional validation
GST-registered Australian businesses issue tax invoices, collect GST and report through the business activity statement. The Australian Taxation Office’s GST accounting guidance explains these core responsibilities and the value of accounting software for tax invoices and reporting.
Odoo provides country-specific fiscal localization packages, and Australia is listed among supported localizations in the official fiscal localization documentation.
The company’s accountant or tax adviser should validate:
- chart of accounts;
- GST tax mapping;
- tax invoice content;
- cash or accrual treatment where relevant;
- BAS reporting;
- credit notes and adjustments;
- imports and exports;
- fixed assets and other specific treatments.
Installing a localization does not remove the need for company-specific review.
Consider Peppol eInvoicing as a process improvement
Australian eInvoicing uses the Peppol network to exchange invoice data directly between compatible systems. The government’s eInvoicing guidance distinguishes it from emailing PDF invoices and explains benefits such as fewer errors and more secure exchange.
Before adoption, determine:
- which customers and suppliers are ready;
- which service provider or access point will be used;
- how trading partners are identified;
- how rejected invoices are handled;
- how status is reconciled in accounting;
- how PDF or other channels coexist during transition.
The objective should be a faster, more reliable accounts-payable or accounts-receivable process, not simply a technical connection.
Design warehouses and mobile stock carefully
A field-service business may treat each van as a stock location. This can improve visibility but increases the number of transfers and counts users must maintain.
Use mobile stock control when:
- parts have meaningful value;
- technicians regularly consume or return items;
- stockouts cause service delays;
- warranty or serial traceability matters;
- van replenishment can be managed consistently.
For very low-value consumables, a simpler issue or expense method may be more practical.
Use operational dashboards that lead to action
Useful measures include:
- orders at risk because of stock;
- supplier deliveries overdue;
- inventory below or above policy;
- service tasks awaiting parts;
- technically completed work not ready to invoice;
- returns awaiting inspection;
- stock adjustments by reason;
- job gross margin;
- invoice correction rate;
- receivables by customer and account owner.
Each measure should have a named person expected to act on it.
A phased Melbourne rollout
Phase 1: product, customer and commercial control
Clean master data, configure CRM, quotations, pricing, approvals and customer ownership.
Phase 2: purchase and inventory
Establish warehouses, receiving, replenishment, transfers, deliveries and returns.
Phase 3: field service
Connect requests, tasks, technicians, parts, worksheets, completion and billing readiness.
Phase 4: accounting, GST and eInvoicing
Configure and validate the Australian finance model with qualified advisers and test end-to-end transactions.
Phase 5: profitability and improvement
Build reporting from stable source transactions and address recurring exceptions.
Go-live scenarios to test
- An order when one item is available and another is delayed.
- A customer-specific purchase that is later cancelled.
- A partial supplier delivery.
- A technician using extra parts not originally reserved.
- A job completed without the required customer reference.
- A warranty return that should not be billed.
- A damaged product returned to the supplier.
- A GST adjustment or credit note.
- An eInvoice rejection.
- Month-end reconciliation of inventory, service billing and accounting.
Frequently asked questions
Can Odoo support both wholesale and field service?
Yes. Sales, inventory, purchase, field-service and accounting processes can operate in one environment, but the handoffs and ownership rules must be designed carefully.
Should technician vans be configured as warehouses?
They can be configured as stock locations when material value and traceability justify the transaction effort. Simpler treatment may suit low-value consumables.
Does Odoo automatically guarantee Australian tax compliance?
No. Odoo provides localization capabilities, but the configuration and operating process should be validated for the business by appropriate Australian accounting or tax professionals.
What is the most useful first dashboard?
For many wholesale and service businesses, a combined view of orders at risk, overdue purchasing, tasks awaiting parts and completed work not yet invoiced produces immediate value.
What usually causes poor job-profitability reporting?
Parts, labour, subcontractor cost or credits are not recorded against the same customer order, project or service task. Profitability depends on disciplined source transactions.
An Odoo rollout for a Melbourne wholesale or field-service business should create one reliable story: what was promised, what stock and work were required, what was delivered, what it cost and what was invoiced. When that story is complete, management can grow without losing control of service or margin.
