The owner asks for a sales report and accounts spends two days on it

We sat with the finance team at a roughly 70-person Abu Dhabi company running Odoo alongside Excel. Four problems came up in the first ten minutes, unprompted, each one costing someone real time every week. None of them needed new software. All four needed the system that was already there to be configured to actually answer the question being asked of it.

Why does the salesman-wise sales report take accounts two days?

Every time the owner asks for a sales report broken down by salesperson, someone in accounts exports data from Odoo into Excel and rebuilds the report from scratch. One to two days of work, for a report that gets asked for again a few weeks later, rebuilt from scratch again.

Odoo ships general sales reporting and a pivot view that can group by salesperson. What it does not ship is the exact report an owner has in their head: specific columns, specific groupings, a layout that matches what they are used to seeing. Getting there usually means either Odoo Studio, which is an Enterprise-only tool for building custom views and PDF reports, or a custom filtered export configured once and reused. Without either, the fallback is the manual rebuild.

The fix is not a new report button someone has to remember to click. It is a report that reads Odoo directly on a schedule and lands in the owner's inbox already formatted the way they expect it, with no export and no rebuild. Once it is configured, it runs the same way every time, whether it is asked for or not.

Why are aged receivables invisible until a payment is keyed in?

Nobody chases an overdue invoice before it is already late, because nobody sees it is overdue until a payment gets entered against it and the gap becomes obvious in hindsight. The ageing picture exists in the invoice data the whole time. It just is not surfaced anywhere the team looks day to day.

An ageing view that updates from invoices, not from payments, closes that gap. It reads open invoices against their due dates continuously, so a bucket like "30 to 60 days overdue" is accurate the moment it crosses the line, not whenever someone happens to reconcile it. The team can chase on day 31 instead of finding out on day 90.

Why does a quotation's validity end without anyone noticing?

A quote gets sent, the customer sits on it, the validity date passes, and the quote is now technically dead, but nobody told the salesperson or the customer. The deal either dies quietly or gets reopened at the old price by mistake.

Odoo's automation rules, built on its scheduled and automated actions, exist for exactly this kind of check: run on a schedule, look for records matching a condition, do something about it. In most Odoo setups we see, nobody has configured that specific rule, so the validity date field sits on the quotation unused. A scheduled job that checks for quotes expiring within seven days and emails the salesperson (or the owner, or both) turns a date field nobody reads into an actual warning.

Why does purchasing price every order from scratch?

The buyer places an order without knowing, at a glance, what was paid to that supplier last time. Odoo does keep that history: it does not overwrite old vendor prices, it keeps them on record against the product and the supplier. The gap is not the data. It is that the last price paid usually does not appear on the purchase order line itself, where the buyer is actually looking when they type in a number.

Surfacing the last price paid directly on the purchase order line, at the moment the buyer is pricing the order, turns a fact that exists somewhere in the system into a fact the buyer actually sees.

Is this an Odoo-specific problem?

No. The same four shapes, the report nobody automated, the ageing view nobody built, the alert nobody configured, the lookup nobody surfaced, show up in Zoho, Tally and QuickBooks setups just as often. The system name changes. The gap between what the software can technically do and what it has actually been configured to do does not.

This is why we describe this kind of work as configuration and integration, not a new software purchase. The business already owns a system capable of answering these questions. Our earlier post on this goes into why "buy something new" is so often the wrong move when the real problem is that what is already there was never wired to talk to itself. Our post on checking whether automation is actually working covers the other half of this: once something is built, how to tell if it is quietly failing.

What does fixing this actually look like?

In each of the four cases, the shape is the same. We watch how the report, the chase, the quote or the order actually gets handled today, by the person who does it. We find where the underlying data already lives in the system. Then we configure a report, a scheduled alert or a lookup that reads that data directly and puts it where the person already looks, an inbox, a screen, a line on a form, instead of a spreadsheet someone rebuilds by hand.

Our operations dashboard work follows the same pattern for businesses that want all of this, the reports, the alerts, the receivables view, the price lookups, in one place the owner can check from their phone rather than four separate fixes inside Odoo. Either way starts with watching the actual process, not guessing at it.