Skip to content

What do damaged, lost and late deliveries cost in refunds and reships?

Join ShipStation, the carrier file, Gorgias and Shopify. See which deliveries went wrong, the refunds and replacements on those orders, and where the damage comes from.

Open Querri

What you'll need

Querri (Free trial) to tie exceptions to refunds and reships

ShipStation, a carrier file, Gorgias and Shopify: Step 1 says what each adds

Your exception and cost rules: so every exception is counted and priced the same way

Free resources

Start your free trial here →

Sample data sets

Synthetic data for Curio Supply, a made-up home goods brand. Not real customer, retailer or marketplace data.

Need help?

If you have any questions, you can request a demo or email our team.

Before we begin

Refunds and reships show up in Shopify as part of doing business. Nobody adds up which came from a damaged box, a lost parcel or a late delivery, so the cost never gets a cause. The shipment is in ShipStation, the delivery in the carrier's file, the damage report in Gorgias and the refund in Shopify.

This playbook flags every late, lost or damaged delivery on the month's store shipments, ties refunds and reships to them, and finds the warehouse, carrier service and product the damage concentrates in.

How it works:

  • • Connect ShipStation, Gorgias and Shopify; upload the carrier file
  • • Flag every late, lost or damaged delivery
  • • Tie refunds and reships to those orders
  • • Find the warehouse, carrier and SKU behind the cost
  • • Build the monthly delivery exception view

Follow the steps

Open Querri →
1 Step 1:

Connect ShipStation, Gorgias and Shopify; upload the carrier file

Four sources, one project:

  • •

    ShipStation: shipments by warehouse, carrier and service.

  • •

    Carrier delivery file (upload): the delivered date and late or lost status for each tracking number.

  • •

    Gorgias: tickets tagged damaged, which is how damage is known.

  • •

    Shopify: refunds and reship orders, each reship linked to its original order.

ShipStation, Gorgias and Shopify connect directly and sync on a schedule. The carrier file comes in as an upload; upload next month's over the old one and every view rebuilds.

Tip: Pull six months before the month you're reviewing, so this month's damage can be compared with a usual month.

  • ShipStation shipments
  • Carrier deliveries
  • Gorgias tickets
  • Shopify orders
Querri One project
2 Step 2:

Flag every late, lost or damaged delivery

Start by flagging what went wrong, once per order:

Prompt

"Of the store orders we shipped in October, which were delivered late, lost, or reported damaged?"

793 of the 18,190 store orders shipped in October had a recorded exception: 437 late, 310 damaged and 46 lost. These are recorded exceptions on October shipments, as of the export.

Flag every late, lost or damaged delivery
ExceptionOrders
Late437
Damaged310
Lost46
All exceptions793

Store orders shipped in October 2026, by exception. Each order counted once: damaged, then lost, then late.

3 Step 3:

Tie refunds and reships to those orders

Then tie each exception to its refunds and reships:

Prompt

"What refunds and reships are on those exception orders? Leave out refunds on orders with no exception."

The 793 orders carry $30,386.63 in refunds and replacement value: $17,137.63 refunded and $13,249.00 reshipped. Damaged orders account for 79.5% of it.

Tie refunds and reships to those orders
ExceptionOrdersRefunds plus replacement value
Damaged310$24,151.89
Lost46$5,015.12
Late437$1,219.62
All exceptions793$30,386.63

Refunds and replacement value (reships at selling price) on October 2026 exception orders.

4 Step 4:

Find the warehouse, carrier and SKU behind the cost

Find where the damage concentrates:

Prompt

"Where does the damage come from: which warehouse, which carrier service, which product?"

3PL East had 264 damaged orders in October, against about 124 a month before. The Curio Stoneware Dinner Set, 16 piece, was in 106 of the 310 damaged orders; 99 shipped from East.

Find the warehouse, carrier and SKU behind the cost
Carrier serviceOctoberApril to September
UPS 2nd Day Air25.09.8
FedEx Home Delivery20.612.0
UPS Ground20.412.9
USPS Ground Advantage7.96.9

Damaged deliveries per 1,000 shipments by carrier service, October 2026 against April to September 2026.

5 Step 5:

Build the monthly delivery exception view

Four numbers for the monthly review, and where to start.

The narrative Querri writes:

Damage was 310 of October's 793 exceptions but 79.5% of the refunds and replacement value on them, and one dinner set was in a third of the damaged orders.

What you can create or export:

Build the monthly delivery exception view
ItemOrdersNext step
Damaged orders containing the dinner set106Review the packaging
Damaged orders from 3PL East264Review with 3PL East
Lost parcels46Check carrier claims

Where to start, October 2026 exceptions.

Take one product and one warehouse to the packaging conversation, with a dollar figure attached.

Try it on your own data
Querri for ecommerce customer experience See how Querri helps CX teams see which orders turn into tickets, and whether it's the warehouse, the carrier or the product. See Querri for customer experience

See Querri for the whole brand

Tips for an exception review people trust

Count by dollars as well as orders

The most common exception is not always the costly one. Late deliveries were most of the count here and the smallest share of refunds and replacements.

Keep other refunds apart

Refunds on orders with no recorded exception may be ordinary returns or exceptions nobody logged. Mixing them in would make every month look like a damage problem.

Teach Querri your rules once. Every answer after that follows them.

What counts as an exception, which refunds and reships count against it, how refunds with no exception are handled: say each rule once and Querri applies it to every question on that data.

Show me how

Say it in chat

Settle a rule in conversation and the Librarian records it as a fact under Facts & Rules, attached to the table it governs. Every later question on that data applies it, whoever asks, and every view built afterwards carries it.

Prompt

"The cost of a delivery exception is refunds on the order plus the selling price of any reship of it. Save that as a rule for the Shopify orders table."

Or bring the document that already says it

Upload your returns and service recovery policy like any other file. Querri files a From a document card in the Inbox with the statements it found, each with its page and exact words; tick the ones to keep and they become facts. The rules this playbook depends on:

  • Exception: late, lost or damaged, one per order
  • Order of precedence: damaged, then lost, then late
  • Damaged: a Gorgias ticket tagged damaged, matched to the order
  • Reship: a $0 order tagged reship, linked to the original order
  • Cost: refunds plus replacement merchandise value at selling price
  • Refunds on orders with no exception are returns, left out
Prompt

"Read our service recovery policy and propose the rules it states about reships and refunds. I'll review them in the Inbox."

Where the rules reach

A rule is attached to the data, not to one person's chat, so it follows the data everywhere:

  • • Every question asked in chat, by anyone on the customer experience team
  • • Every view the Librarian builds on that data
  • • Every step of a project, including the code it writes
  • • Dashboards and scheduled runs, each time they refresh
  • • Claude and ChatGPT, when they ask Querri

You stay in control

Every rule is listed under Facts & Rules next to the data it governs, where you can edit or remove it. Rules from a document wait for your tick in the Inbox, and a Worth remembering card is how Querri offers one it noticed itself. Workspaces and roles decide who can change what. Company-wide rules go in Settings → Customize; the Library is where the rest lives.

The payoff in the review

The review starts with one product, one warehouse and a dollar figure. Changing how a reship is valued is a sentence.

Frequently asked questions

What does the cost include?
Refunds on orders with a delivery exception plus the selling price of any replacement shipped for them. It measures refunds and replacements on those orders, not the full cost to the business: no product cost, shipping or labor. Not every refund on an exception order was caused by the exception.
Why leave out returns?
This page measures refunds and replacements on orders with a recorded exception. Refunds on orders with no recorded exception, 263 orders and $21,066.70 in October, are counted separately and left out. They may be ordinary returns or exceptions nobody recorded.
How is damage known?
From Gorgias tickets tagged damaged, matched to the order by the order field (219), the subject line (54) or the customer's email (37). Damage nobody reported isn't counted.
Are late deliveries complete?
The figures are recorded exceptions on October shipments, as of the export. The carrier file runs through 2026-10-30, so a parcel shipped late in the month may not show as late yet.
Why is damage's share 79.5%?
Damaged orders account for $24,151.89 of the $30,386.63 in refunds and replacement value on exception orders. The share uses the same measure as the total.
Does the dinner set cause the damage?
The data shows it was in 106 of the 310 damaged orders, 99 of them from 3PL East. Orders hold several items, so it shows where damage concentrates, not why items broke.
How is this different from Orders to tickets?
Orders to tickets starts from support tickets and found product category didn't matter. This page starts from refunds and replacements, and damage concentrates in one product.
How often should this run?
Monthly, once the carrier file for the month is in. A warehouse or product with rising damage shows up in the first month it happens.