| Industry | Timber and wood products, import and export |
| Location | Johannesburg |
| Size | 40-50 employees |
| Odoo version | 19, on Odoo.sh |
| Modules | Accounting, Sales, Purchasing, Studio, and custom development |
Invoices, packing lists, and customs declarations were built from scratch with no standard templates, and each shipment took three to four hours. The company also ran four bank accounts across different currencies, and staff copied the right banking details onto each invoice by hand. If they got it wrong, the client sent the invoice back. Payment then slipped by days, sometimes weeks.
Stock codes, weights and dimensions were looked up fresh for every order. A wrong customs declaration meant a one- to three-day hold at the border. Once an email went out, nobody could trace what had been sent. Management had no live view of the export pipeline, so cash flow forecasting was mostly educated guessing, and the operations team was stretched thin.
The brief was to make Odoo the single home for every trade document and retire the Word and Excel files entirely.
What we built
We delivered four custom templates for the sales order, purchase order, invoice and commercial invoice, using Odoo Studio and QWeb.
The bank selection is now a dropdown. Pick the account, and the bank name, branch code, account number, SWIFT code and currency fill themselves in. The commercial invoice can be generated from a sales order or a delivery order, and its totals come from what was actually delivered, not what was ordered. That matters for partial shipments, which used to mean manual maths. An email template attaches the invoice and updates the order status in one step.
The hard parts
The delivered-quantity logic was the trickiest. It had to filter delivery moves and match them to the right sale order lines, and we only got it right by sitting with the client’s operations team and learning how they really handle partial shipments.
The other risk was replacing Odoo’s standard PDF layouts without breaking the modules that depend on them. We used template inheritance with XPath positioning instead of overwriting the standard templates. It’s slower to build. It also means future Odoo upgrades won’t turn into a rescue mission, and we’d make that trade every time.
The process was phased: discovery, build, testing, then deployment with training and post-go-live support. Each module was tested against real client data before we moved to the next one.
What changed
Staff now select a bank account, click a button, and get a professional commercial invoice in seconds. Partial shipments calculate themselves from delivery records. Management can see at a glance which orders have had commercial invoices sent, and clients get accurate documents the first time.
The system was built so the business can take on roughly three times its current order volume without adding admin staff. The team spends its time growing the business instead of correcting paperwork.