fb-image

Explore More Across Our Network

Linnworks Reporting: When Standard Reports Are Not Enough

Linnworks Reporting: When Standard Reports Are Not Enough

Linnworks holds almost everything you need to know about your business: orders, channels, stock, locations, suppliers and despatch. The standard dashboards and reports answer the everyday questions well. How many orders came in today? What sold last week? Which items are low on stock?

The trouble starts when the questions get more specific. Which sub-source is most profitable once fees and postage are taken off? Which warehouse should hold more of a fast-moving SKU? Which products have missing dimensions that are causing the wrong shipping service to be chosen? Standard reports rarely answer these directly, so teams fill the gap with exports and spreadsheets.

This post explains how to tell when standard reporting has stopped being enough, what that costs, and what a better setup looks like.

Signs standard reports are no longer enough

1. Someone rebuilds the same spreadsheet every week

If a team member exports data every Monday, pastes it into a template and fixes the formulas, the report exists, just not in Linnworks. That is time spent every week on a job a scheduled report could do.

2. The answer needs data from several places

Questions such as “sales by sub-source, by location, with current stock” combine order, channel and inventory data. When a standard report covers only one of these, people end up joining exports by hand, which is slow and easy to get wrong.

3. Different teams get different numbers

Operations, finance and purchasing each build their own version of “sales last month”, with different date filters or treatment of refunds and cancellations. Meetings then turn into arguments about whose figure is right.

4. You can see sales, but not margin

Revenue by channel is easy to find. Margin after purchase cost, channel fees and postage usually is not. Without it, a channel can look successful while quietly losing money on certain products.

5. Stock decisions are made on gut feel

Reordering and transfers between locations need sales velocity, stock on hand and stock due in, side by side. If buyers piece this together themselves, decisions arrive late and are inconsistent.

6. Data problems are found by customers, not reports

Missing weights and dimensions, items without a bin rack, or listings not linked to the right SKU often only come to light when an order goes wrong. Simple exception reports can catch these before they cause a problem.

What it costs

  • Time: hours each week spent exporting, merging and checking spreadsheets, usually by experienced people whose time is better spent elsewhere.
  • Cost: over-ordering slow lines, under-ordering fast ones, and continuing to sell products or channels that make little or no margin.
  • Risk: decisions based on a spreadsheet with a broken formula or an out-of-date export, and reports that stop when the one person who builds them is away.

A practical example

Imagine a seller with stock in two locations, selling on Amazon, eBay and their own website. Every Monday, the operations manager spends most of the morning building a report that shows last week’s sales by channel and sub-source, alongside current stock in each location. This is an illustration, but it is a common pattern.

The process involves three exports, a lookup between them and a manual tidy-up of SKUs that don’t match. Twice in a quarter, a filter left on from the week before means the figures are wrong, and a transfer between locations is made on bad data.

Replacing this with a single custom report means:

  • the data comes straight from Linnworks in one query, with no manual joining;
  • sales, stock by location and days of cover appear in one table;
  • the report is scheduled to arrive before the Monday meeting; and
  • everyone uses the same definitions, so the numbers match.

The manager’s Monday morning goes back to acting on the numbers instead of building them. The exact saving depends on how many reports you run and how complex they are.

What a better reporting setup looks like

  1. Start with the decision, not the data. Write down the question the report must answer and who acts on it.
  2. Agree definitions. Decide once how to treat refunds, cancellations, dates and costs, so every report uses the same rules.
  3. Check the data first. Missing costs, weights or SKU links will make any report wrong. Fix the gaps or report on them.
  4. Build it once, properly. Custom SQL queries can combine order, channel and stock data that standard reports keep separate.
  5. Test against known figures. Compare the new report with a week you have already checked by hand before relying on it.
  6. Schedule and deliver it. Have reports run automatically and arrive where people already work.
  7. Keep a short list of exception reports. Missing data, unlinked listings and stock errors are cheaper to catch in a report than in a complaint.

Examples of reports we have built include sales by sub-source channel, channel inventory by location, inventory sales analysis by category and SKUs with an invalid bin rack. Our Linnworks reporting and SQL services page explains how we approach custom reports.

When standard reports are still the right choice

Custom reporting isn’t always needed. If a standard report answers the question and nobody has to rework it, keep using it. Custom reports earn their place when a report is run often, combines several types of data, or drives decisions about stock, pricing or channels. If your reporting problem is really a manual process problem, our posts on Linnworks processes worth automating and Linnworks rules that have become too complicated may help.

Not sure where your reporting gaps are?

We offer a free, no-obligation 30-minute Linnworks Efficiency Review. We look at how you report on sales, stock and channels today and point out where time is going on spreadsheets that a report could replace, before any work is discussed.

Book your free Linnworks Efficiency Review

To see everything we do for Linnworks users, from reporting and macros to integrations and support, visit our Linnworks services page.

Table of Contents

Get Started With Us
Get Started With Us
Scroll to Top