Proof / Case study
Freight document reconciliation for a food-service distributor
Freight shipments and their receiving documents brought into a custom tracker in Odoo, with every matched document linked back to its shipment. A stage workflow mirrors the legacy freight stages, and plain-English AI requests produce downloadable reports.
Anonymized by policy. The facts are as delivered.
- Industry
- Food-service distribution
- Service
- Custom Module Development / Document Reconciliation
01
Starting point
The client reconciled freight shipments against receiving documents, and matching had to stay traceable to the source shipment record.
Shipment data needed to flow from operations into a purpose-built tracker where that traceability is built in.
02
Constraints
- Field structure complicated the same picture: the customer PO sat inside a combined field.
- An earlier platform upgrade had collapsed the dedicated office, mobile, and other phone fields into one.
03
Scope
- Custom freight-shipment models built, with shipment data synced in from operations.
- Every matched document linked back to its shipment, so matching stays traceable to the source record.
- A freight stage workflow mirroring the legacy system stages, from pending and booked through in transit, delayed, delivered, and followed.
- A dedicated customer-PO field split out of the previously combined field, with the backlog of old combined records re-split programmatically.
- A per-person generated-documents area, and the dedicated office, mobile, and other phone fields restored.
- Contact-screen editing and the active/inactive toggle fixed.
- Plain-English AI requests that produce a spreadsheet, PDF, Word document, or web page, with long reports running in the background and posting a download link when ready.
04
Approach
Stack
Odoo 路 custom freight-shipment module 路 stage workflow 路 generated documents (spreadsheet, PDF, Word, web)
- 01
Audit
A full pass over the freight shipment lifecycle and the receiving documents reconciled against it, including the field structure that had drifted through an earlier platform upgrade.
- 02
Model & Sync
Custom freight-shipment models built and shipment data synced in from operations, with each matched document linked back to its shipment so matching stays traceable to the source record.
- 03
Configure & Repair
A freight stage workflow mirroring the legacy system stages, from pending and booked through in transit, delayed, delivered, and followed. A dedicated customer-PO field was split out of the previously combined field, and the backlog of old combined records was re-split programmatically. A per-person generated-documents area was added, the dedicated office, mobile, and other phone fields were restored, and contact-screen editing and the active/inactive toggle were fixed.
- 04
AI Reporting
Plain-English requests produce real downloadable deliverables: a spreadsheet, PDF, Word document, or web page. Long reports run in the background and post a download link when ready.
05
Evidence
Freight shipments and their receiving documents now reconcile inside a custom tracker, with every match traceable back to the source shipment record.
The freight stage workflow mirrors the legacy stages, the customer PO lives in its own dedicated field with the old combined backlog re-split programmatically, and each person has a generated-documents area.
AI reporting turns plain-English requests into downloadable deliverables in four formats, with long reports running in the background and posting a download link when ready. The post-upgrade phone-field collapse and the contact-editing and active/inactive toggle faults were fixed as well.
06
Limitations
- The write-up records the deliverables and behavior shipped, and names no quantified business outcome.
Start a project
Have a project like this one?
Tell us what you are building. A senior engineer writes back with a written plan and a fixed quote.
Start a projectFree written plan and a quote. No meeting.