Odoo for a Propane Delivery Business: Routes, Accounting and Support

Real client project, name withheld. Delivered at Master Software Solutions; my role is set out below. The client's name and identifying details are left out.

A residential and commercial propane supplier in the United States already used Odoo, but routes were planned by hand, accounting lived in QuickBooks, and only one former employee understood the setup.

• Industry: Energy distribution: propane delivery
• Location: United States
• Platform: Odoo
• Odoo support
• Accounting migration
• Route planning

The problem

The company delivers propane for generators, cooking, pool and water heaters, outdoor living and forklifts. Three problems overlapped. The one person who understood the Odoo setup had left without documenting it. Accounting ran separately in QuickBooks and had to be reconciled by hand. And delivery routes were planned informally, wasting fuel and driver time.

The existing process

Operations in Odoo, accounting in QuickBooks, and routes planned from experience each day. With no Odoo knowledge left in the business, nobody could safely change or maintain the system.

Business requirements

• Understand and document the existing Odoo setup.
• One system for operations and accounting.
• Optimised delivery routes planned inside Odoo.
• A long-term partner for Odoo support and development.

My role

I delivered this project at Master Software Solutions as consultant, tech lead, project manager and delivery manager: reviewing and documenting the existing setup, designing the move of accounting from QuickBooks and the route-planning rollout, leading the MSS developers, and owning delivery and the ongoing support. The route-planning module is an MSS product.

The solution

First, understand what was already there: the existing Odoo configuration was audited and documented so it could be supported safely. Accounting then moved into Odoo: the chart of accounts was mapped, historical financial data migrated, taxes configured, and invoicing tied to delivery orders, so a completed delivery produces its invoice. Route optimisation was added inside Odoo, so dispatch plans routes from the day's delivery orders instead of from memory.

Key decisions

• Document before changing anything. With the only expert gone, the first job was to make the existing system understood.
• Move accounting into Odoo rather than keep reconciling with QuickBooks, so there is one set of numbers.
• Tie invoicing to delivery orders. In a delivery business, the delivery is the event that should trigger the bill.
• Set up ongoing support rather than a one-off project, so knowledge never again sits with one person.

Odoo modules used

• Inventory and delivery
• Accounting
• Invoicing
• Route optimisation

Integrations

• A route optimisation module added to Odoo for delivery planning.
• QuickBooks: chart of accounts and historical financial data migrated into Odoo.

Implementation

Audit and documentation of the existing setup; chart of accounts mapping and historical data migration from QuickBooks; tax configuration; training on Odoo accounting workflows; then route optimisation. The work continues as an ongoing support and development partnership.

Challenges

• Working out an undocumented configuration built by someone who had left.
• Migrating accounting history without disrupting daily deliveries and billing.

Results

• One platform for operations and finance, with no QuickBooks reconciliation.
• Dispatch streamlined, with routes planned in Odoo to cut mileage and fit more stops into each route.
• Invoices generated from completed deliveries.
• A documented system with ongoing support, so the business no longer depends on one person.