Filing Royal Mail lost parcel compensation claims used to take our client 20 minutes each. We built an AI-powered Xero + Linnworks system that does it in seconds + automatically finds unclaimed lost packages. 240 hours saved + hundreds recovered monthly.

Case Study Highlights

Support time per claim: 20 min → ~2 min
Annual time saved: 240 hours
New monthly revenue: Hundreds in previously unclaimed Royal Mail compensation
Fully automated lost-package detection + PO evidence bundling

Filing a reimbursement claim with Royal Mail shouldn’t take 20 minutes. But for one of our clients, that’s exactly how long it took every single time a package went missing.

The support team knew the drill. A customer reports a lost parcel. To file a Royal Mail compensation claim, you need evidence of value: a purchase invoice showing what the item actually cost you to buy or manufacture. Royal Mail bases their lost package compensation on “actual loss”, not the retail price. That means digging up the original purchase order for every item in the shipment. Sounds simple enough until you actually try it.

The Manual Royal Mail Lost Parcel Compensation Claim Nightmare

Here’s what the process looked like:

Find the tracking number for the lost package
Look up the order in Linnworks to see what products were in it
Figure out the SKU or barcode for each product
Go into Xero and start hunting through purchase orders
Open each PO and pray it’s not a scanned photocopy

Step four was where things fell apart. Xero’s search is not built for this. You can’t search inside PDF attachments, and the metadata on purchase orders rarely had the detail the team needed. So they’d scroll through lists of POs, open them one by one, and visually scan the contents looking for a matching SKU or product name. It’s the same kind of pain we saw with a client whose sales team had to leave Tradegecko to manually check warehouse stock before placing every order.

Most POs were proper digital documents, but a decent number were scanned images or photocopies that suppliers had uploaded as PDFs. Those ones had no searchable text at all, so the only way to check them was to open each one and read it.

Multiply that by a dozen lost packages a week and you’ve got a team spending a serious chunk of their time on something that feels like it should be automatic. They brought the problem to us at SaaS Glue.

How We Built the AI-Powered Royal Mail Compensation Claim Automation System

We broke the problem into two parts: making the data searchable, and making the search instant.

The PO processing pipeline pulls every purchase order PDF out of Xero and runs it through an AI parsing layer. Blurry scan of a photocopied invoice? Crooked image of a supplier receipt? Doesn’t matter. The system reads the document, extracts line items, quantities, and prices, then builds a searchable index of every product the client has ever purchased.

Each item gets cross-matched against the Linnworks catalogue. When a PO has a barcode or SKU that matches, the link is straightforward. But plenty of POs don’t include barcodes at all, and suppliers often use their own SKUs that have nothing to do with the client’s. For those cases, the system falls back to AI-powered name matching, comparing product descriptions from the PO against the Linnworks catalogue to find the right item. The end result is the same: a clean link between “this product in an order” and “this is what we paid for it, and here’s the PO to prove it.”

The front end is dead simple. Support enters an order ID, the system pulls every relevant purchase order, bundles them into a zip file, and hands it over. What used to take 20 minutes of tab-hopping now takes about ten seconds.

Automatically Finding Unclaimed Royal Mail Lost Parcels

Once the system was running, something obvious jumped out: a lot of lost packages were never being claimed at all. The support team was only filing reimbursements when a customer complained. But packages go missing whether the customer notices or not, and Royal Mail will pay out either way as long as you file in time.

So we built a lost package tracking pipeline. It monitors Royal Mail tracking statuses across all outbound shipments and flags anything showing signs of being lost: parcels stuck in transit past expected delivery windows, packages with no scan activity for days. When it spots one, it automatically pulls the matching purchase orders from the index.

Every two weeks the system compiles a report of unclaimed lost parcels with the PO evidence already attached. The support team just reviews the list and submits the Royal Mail reimbursement claims in bulk. What used to slip through the cracks now gets caught automatically.

Ensuring Long-Term Stability

A system like this is only useful if you can trust the data. Suppliers change their invoice formats, product names drift, new items get added. If a PO suddenly starts failing to parse or match, we need to know about it before the support team does.

We set up a Grafana dashboard that tracks PO processing in real time: how many are being parsed, how many line items match successfully, and the rate of unmatched lines. We agreed with the client on a 2% failure rate as the acceptable threshold. If the unmatched rate climbs above that, it usually means a supplier changed their invoice layout or started using different product descriptions, and we can catch it early.

Errors and exceptions get logged to Rollbar, so if something breaks we get alerted straight away rather than waiting for someone to notice missing data.

Results: 240 Hours Saved + Recovered Revenue

Here’s the maths. About 16 lost packages a week, each one taking 20 minutes to process. With the new system the lookup takes about 10 seconds and the whole claim, forms included, takes around 2 minutes. That’s roughly 240 hours a year given back to the support team.

On top of that, the client started recovering hundreds of pounds every month in Royal Mail compensation that previously went unclaimed, simply because nobody had the time to file. And the person who used to spend half their afternoon hunting through Xero for purchase orders? They now spend that time on work that actually matters.

The Linnworks and Xero integration runs quietly in the background. New purchase orders get indexed as they come in, so the data is always current. The support team doesn’t think about the pipeline at all, they just use it.

Frequently Asked Questions – Royal Mail Claims Automation

Could this work with accounting software other than Xero?

Yes. The PO parsing doesn’t care where the PDF comes from. We just need API access to pull the documents.

Could this work with an order management system other than Linnworks?

Yes. The system just needs a product catalogue to match against. Whether that’s Shopify, Sellercloud, Veeqo, Brightpearl, or anything else with an API, the approach is the same.

Did you run into problems with the PO data?

The only issue was a batch of very old POs from a supplier the client no longer works with. Those had missing barcodes and inconsistent product names that the system couldn’t map to anything in Linnworks, so we skipped them. Every recent PO from active suppliers parsed and matched without trouble.

How long did this take to build?

The core system (PO parsing, indexing, and the lookup UI) was up and running in a month.

What does it cost?

It depends on the data. Document parsing can be straightforward or it can get messy, and we won’t know which until we see what you’re working with. We start with a short discovery phase to evaluate the complexity, then quote either a fixed fee or an hourly rate depending on the job.

If any of this sounds familiar, lost parcels piling up, support team buried in manual lookups, money going unclaimed because nobody has time to file, drop us a message. At SaaS Glue, we’ll have a look and tell you what we think.

You can also see more of our work or read our manifesto to understand how we approach these problems.

Royal Mail Lost Parcel Compensation Claim Automation: Xero & Linnworks Case Study