Executive Summary
You can't see how product returns affect your margin for weeks. This means you're making buying and marketing decisions with incomplete information.
You end up ordering more of the products that are often returned, which hurts your net margin and ties up cash in stock you know will come back.
The fix isn't a faster report. It's a change in your data structure to bring sales and returns information together for each transaction. This shifts you from slow, batched updates to a much clearer, almost immediate view of your profitability.
The problem: Making decisions with out-of-date information
It's a familiar scene: the Monday morning trade meeting. You're looking at the sales dashboard and a certain SKU is performing very well. Revenue is up, conversion looks good. The natural reaction is to order more stock and promote it.
But then, a few weeks later, the month-end accounts arrive. The margin on that same SKU has fallen through the floor. What looked like a winner was actually a product with a high return rate, but you only found this out after the money was spent on new stock.
This isn't anyone's fault. It's usually a problem with the underlying system. You've probably invested in a modern data stack, hired good people, and have perfectly decent dashboards. The issue is that if the underlying process is flawed, automating it just means you get the wrong answer, faster.
Why sales and returns data are out of sync
In my experience, the root cause is nearly always in the data architecture. Your e-commerce platform, like Shopify, or your point-of-sale system gives you sales data almost instantly. It's clean and easy to put on a dashboard.
Your returns data, however, tends to live somewhere else. It's often in a Warehouse Management System (WMS) or an ERP, and it's usually processed in batches, perhaps overnight or even weekly. These systems are built for accounting, not for quick commercial decisions. The result is that you have two different sets of data, running on two different schedules.
I've seen this pattern with most high-volume retailers I've worked with. They have a very clear picture of their revenue, but their view of profit is fuzzy and only comes into focus at the end of the month. The problem isn't the dashboard; it's that the sales and returns data aren't properly connected. This delay, or data latency, makes it very difficult to get a true picture of SKU profitability.
The fix: Unifying sales and returns for each transaction
The solution isn't to buy a new piece of software. It's about changing how your data is structured, which is less glamorous than building a new dashboard, but much more important.
What we do is build a unified data model. In this model, a return isn't a separate event. It's just an update to the status of the original order line. This changes things quite fundamentally: instead of two separate streams of data, you get one complete story for every transaction.
In my experience, this is the most reliable way to create a Single Source of Truth that works for both the finance team's audit and the commercial team's daily needs.
This is often an organisational challenge, not a technical one
To be clear, making this change isn't always straightforward. It usually requires getting people from Operations, Finance, and your data team to agree on a new way of working. It means acknowledging that the current system has its limits, and it might bring some uncomfortable facts about product performance to light.
What you're doing is removing the ambiguity. Once the data is unified, it's harder to blame delays or differences between systems. The numbers are simply the numbers. This level of clarity can make some people uncomfortable, so it's sensible to expect a bit of resistance.
The result: Moving from reactive to proactive decisions
Once this new data structure is in place, the weekly trade meeting feels quite different. You're no longer just looking at what happened last month. You can see the net margin impact of last week's sales, this week.
You can spot a product with a high return rate in a few days, rather than waiting weeks. This lets you pause marketing spend, change your re-ordering, and talk to the product team about any quality issues. It's the difference between having lots of data but not much insight, and having proper operational visibility. You get to run the business looking at the road ahead, instead of just looking in the rear-view mirror.