Your Carrier Data Feed: What It Is and How to Use It

A carrier data feed is the automated flow of shipping data from FedEx, UPS, DHL or Canada Post into your own systems: invoice detail, tracking events, rate quotes and address validation results. Instead of somebody downloading a PDF invoice every Tuesday and squinting at it, the charge-level records land in a database where you can query them. That single change is what separates shippers who know their real cost per package from shippers who find out at quarter end. If you audit invoices, forecast freight spend or reconcile against your WMS, the feed is the foundation. Everything else is reporting on top of it.

The four feeds that actually matter

Shippers tend to lump all carrier data together. It’s cleaner to think of four separate feeds, because they arrive at different times, in different formats, and they answer different questions.

The invoice feed is the money feed. Tracking tells you a package was late. The invoice tells you what you were charged for it, and whether you were charged twice.

Why the invoice feed is where refunds live

Carrier billing files are dense. A single domestic ground shipment can carry a dozen charge lines once you add fuel, residential delivery, delivery area surcharge, extended area, address correction, additional handling and peak. Multiply that across 40,000 packages a month and manual review stops being a plan.

With a clean feed you can run the checks that consistently produce credits:

• Duplicate billing. The same tracking number invoiced across two cycles. Rare per shipment, meaningful at volume.
• Late delivery against the service commitment. Where a money-back guarantee applies, the feed gives you the commit time and the actual delivery scan in the same row. Note that guarantee terms have changed repeatedly since 2020 and vary by carrier, service and country, so confirm what your agreement covers.
• Dimensional weight errors. Billed weight higher than the cartons you actually ship. If your WMS carton data is in the same warehouse as your invoice feed, this becomes a two-table join.
• Address correction charges on addresses that were valid at the time of label creation.
• Residential surcharges applied to commercial delivery points.
• Missed discounts and incentive tiers that didn’t apply because a service code or account number was wrong on the label.
• Voided labels still billed. Labels created, never tendered, invoiced anyway.

None of these are exotic. They’re the ordinary noise of high-volume parcel billing, and they typically run somewhere in the low single digits as a percentage of total spend. On $2M in annual parcel spend, one or two percent is $20,000 to $40,000 you already paid for and can get back. We go into the specific charge types on what we audit.

Getting the feed set up without an IT project

You don’t need EDI on day one. Order of operations we’d suggest:

1. Turn on the electronic invoice file

FedEx Billing Online, UPS Billing Center and DHL MyBill all offer a downloadable electronic invoice in CSV or XML with the same charge-level detail as EDI 210. Canada Post provides electronic billing detail through its business account tools. Ask your rep to enable it and to include all account numbers under the parent, including third-party and freight-collect accounts. Missing accounts is the most common gap we see.

2. Get the field dictionary

Every carrier publishes a layout document mapping column positions to charge descriptions and codes. Get it. Charge descriptions change wording between versions, and a report that keys off text strings instead of charge codes will silently break.

3. Load, don’t look

Push the file into a table, not a spreadsheet. One row per charge line, keyed on tracking number plus invoice number plus charge code. Keep the raw file. When a carrier disputes a claim, the original file is your evidence.

4. Join to your own data

Your order management or WMS records hold the piece that carrier data lacks: what was actually in the box, what it weighed on your scale, what the customer paid for shipping. That join is where the interesting variances show up. Billed weight versus scale weight. Zone billed versus zone implied by the destination ZIP.

5. Automate the file pull

Once the manual download gets annoying, move to SFTP drops or EDI 210. That’s usually a conversation with your carrier’s technical support team and takes a few weeks.

If you’d rather not build this, that’s essentially what we do. Read how it works for the mechanics of connecting your accounts, and pricing is contingency-based, so it comes out of recovered credits.

Timing is the whole game

Here’s the part that gets missed. Dispute windows on parcel invoices are short, and they vary by carrier and by claim type. Some are measured in a couple of weeks from the invoice date. A feed that lands weekly and gets audited within days lets you file inside the window. A quarterly manual review does not.

That’s why we treat cadence as a service level, not a preference. Invoice drops on a Tuesday, audit runs Wednesday, claims filed by Friday. Miss the cycle and the credit is gone regardless of whether you were right.

What good looks like after six months

Shippers running a real feed can answer these in under a minute: cost per package by service and zone, accessorial spend as a percentage of base rate, top ten ZIPs generating address corrections, share of packages billed on dim weight versus actual, and the exact dollar value of credits recovered last quarter. That’s not a dashboard flex. Those five numbers are what you take into a carrier rate negotiation, and they’re the difference between asking for a better discount and proving which discount you need.

Start by pulling one month of electronic invoice detail and counting the charge lines. Most teams are surprised by how many there are. If you want a second set of eyes on it, start a free audit, or browse more on the blog.

FAQ

What is a carrier data feed?

It’s an automated flow of shipping data from a carrier into your systems, usually invoice detail, tracking events and rate quotes. Invoice feeds arrive as EDI 210 files, CSV or XML on a scheduled drop, while tracking and rating feeds are typically real-time API calls.

Do I need EDI to audit my FedEx or UPS invoices?

No. Most shippers start with the electronic invoice file (CSV or XML) they can download from their carrier billing portal, which carries the same charge-level detail as EDI 210. EDI is worth setting up once you’re processing enough volume that manual downloads become a chore.

How far back can a data feed help me recover refunds?

That depends on the carrier’s dispute window, which is often short (roughly 15 days from the invoice date for some claim types) and varies by carrier, agreement and country. A feed matters because it flags billing errors inside that window instead of months later, so pull historical invoices for benchmarking but expect recovery to be limited to recent cycles.