Oriental Nippon Development
Back to portfolio
Case studyMaintenance contractor for a fuel-station network

Work Order to Invoice in One Chain for a Fuel-Network Maintenance Contractor

Work orders, spare parts, billing and accounts were four disconnected activities. Now closing a job moves the stock, books the cost and raises the invoice.

Industry
Field Service & Maintenance
Region
Pakistan
Engagement
SES (specialist engineers)

Outcomes

  • Job completion triggers the invoice
  • Field usage drives replenishment
  • Per-job profitability visible

Stack

Odoo Work Orders · Odoo Inventory · Odoo Accounting · Python · PostgreSQL

Written byOriental Nippon Team

A maintenance contractor services sites across a petroleum retail network in Pakistan. Jobs are dispatched, done on site, use parts from stock, and are invoiced. Each of those steps was recorded in a different place.

So the chain from "work done" to "revenue recognised" was manual, slow and leaky, and nobody could see whether a given contract was actually profitable.

The problem

  • Jobs and parts recorded separately. Stock and job costs were reconciled after the fact.
  • Billing lagged the work. Invoice evidence arrived late and incomplete.
  • No purchasing signal. Field consumption never reached purchasing reliably.
  • Accounting assembled by hand. Entries were built from operational records instead of produced by them.
  • No job-level profitability. Contract margin was a guess.
BeforeAfter
Job to invoiceFour disconnected stepsOne record
Parts usedLogged separatelyMoves stock on job completion
ReplenishmentAd hocTriggered by field consumption
ProfitabilityUnknown at job levelMaterial and labour per work order

What we built

  • One operational chain

    Completing a job moves stock, creates timesheet and cost lines, and produces the invoice, all in Odoo.

  • Consumption-driven replenishment

    Parts used in the field raise the purchase signal.

  • Job-level cost visibility

    Material and labour attributed to each work order.

Every work order now carries its own commercial consequences:

Technology and the role it played

TechnologyRole in this project
Odoo Work OrdersDispatch and job completion
Odoo InventoryParts consumption and replenishment
Odoo AccountingInvoices and ledger entries produced by the job
Python and PostgreSQLCustom rules and the shared database

How we delivered it

Like the restaurant chain, this client could not justify an internal systems team, so our SES specialists delivered and now run it on a shared-resource basis.

  1. Map dispatch to cash. With the people who run it.
  2. Foundation. Entities, chart of accounts, stock locations and environments.
  3. Work orders and inventory. Configured to real job types and the parts catalogue.
  4. Billing. Completion and sign-off produce the invoice.
  5. Pilot one region. Through a full billing cycle.
  6. Roll out and run. Crew by crew, then managed operation.
Delivery timelineIndicative total: 10–13 weeks
  1. 01Fit review

    1–2 wks

    Job types, parts catalogue, stock topology

  2. 02Foundation

    2 wks

    Entities, accounts, environments

  3. 03Work orders and inventory

    3–4 wks

    Job types, consumption, stock movement

  4. 04Sales, purchase and billing

    2–3 wks

    Completion to invoice, purchase signals

  5. 05Pilot

    2 wks

    One crew or region through a full cycle

  6. 06Roll-out

    ongoing

    Crew by crew

Risks and how we handled them

RiskHow we handled it
Job types that don't match realityConfigured to real job types and the actual parts catalogue
Billing problems found at month endPilot region ran a full billing cycle
No internal team to run itOngoing managed operation by shared specialists

Outcome

Work now produces its own commercial consequences: stock movement, cost and invoice, without anyone assembling them afterwards.

The contractor got an end-to-end connected operation without building an internal systems function. That is why a shared-resource model was the right fit.

What the client keeps

  • The production system
  • Configuration documentation
  • Job-type and parts configuration
  • Runbooks
  • The reporting layer

Sources and further reading

  1. Field Service, Odoo documentation
  2. Odoo 17 documentation, Odoo
  3. Odoo Community Association, OCA

Facing something similar? This is the kind of work our Enterprise & Digital Transformation team delivers every day. Talk to us about your stack.