Skip to content

Which orders are late, canceled or escalated this week?

Join Shopify, Amazon, ShipStation and Gorgias. See which shipments went out late and from where, whether cancellations moved, and which escalations still have no owner.

Open Querri

What you'll need

Querri (Free trial) to join orders, shipments and tickets

Shopify, Amazon, ShipStation and Gorgias: Step 1 says what each adds

Your ship-by and business-hours rules: so late and waiting are measured 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

The weekly report says how many orders shipped. It doesn't say which ones went out late, which warehouse they came from, or which escalations nobody has picked up. Orders are in Shopify and Amazon, ship dates in ShipStation and escalations in Gorgias, so the answer often arrives after customers start writing in.

This playbook lists every shipment past its ship-by date, splits the week's late shipments by warehouse and channel against a usual week, and measures how long escalations wait for an owner in business hours.

How it works:

  • • Connect Shopify, Amazon, ShipStation and Gorgias
  • • List every order past its ship-by date
  • • Split late shipments by channel and warehouse
  • • Measure how long escalations wait for an owner
  • • Build the weekly fulfillment and escalation view

Follow the steps

Open Querri →
1 Step 1:

Connect Shopify, Amazon, ShipStation and Gorgias

Four sources, one project:

  • •

    Shopify: store orders with placed, canceled and fulfilled times.

  • •

    Amazon Seller Central: the All Orders report for orders you ship yourself, with Amazon's promised ship dates.

  • •

    ShipStation: each shipment's warehouse, ship-by date and ship date.

  • •

    Gorgias: escalation tags, and when each ticket was first assigned.

All four connect directly and sync on a schedule. Orders Amazon fulfills never pass through your 3PL, so they are left out of late shipments.

Tip: Pull at least 13 weeks, so this week can be held against a usual week built from the 12 before it.

  • Shopify orders
  • Amazon orders
  • ShipStation shipments
  • Gorgias tickets and events
Querri One project
2 Step 2:

List every order past its ship-by date

Start with every shipment that was due this week:

Prompt

"Which shipments due this week went out late or haven't shipped yet, and how does that compare with a usual week?"

199 of the 5,008 shipments due the week of 2026-10-26 went out late or not at all, against a usual 71.7. 74 had no ship date by Sunday.

List every order past its ship-by date
Ship-by weekLate shipments
2026-10-1292
2026-10-1960
2026-10-26199
Usual week71.7

Late shipments by ship-by week. Usual is the average of the 12 weeks before 2026-10-26.

3 Step 3:

Split late shipments by channel and warehouse

Then see where they came from:

Prompt

"Split this week's late shipments by warehouse and by channel, against their usual weeks."

175 late shipments were assigned to 3PL East, against a usual 46.1: 87.9% of the week's late shipments. 3PL West had 24, close to its usual 25.6.

Split late shipments by channel and warehouse
SplitThis weekUsual week
3PL East (Columbus)17546.1
3PL West (Reno)2425.6
Store orders16256.6
Amazon orders you ship3715.1

Late shipments, week of 2026-10-26, against the usual week. Each split adds up to 199.

4 Step 4:

Measure how long escalations wait for an owner

Check cancellations, then the escalations:

Prompt

"Did cancellations move? And how long did this week's escalations wait for someone to own them, in business hours?"

Cancellations held at 1.39% against 1.37%. The median escalation waited 6.8 business hours for an owner, but 16 of 36 waited more than 10 or still have none.

Measure how long escalations wait for an owner
EscalationsCountBusiness hours
Owner within 10 business hours2010 or less
Owner after more than 10810.2 to 27.0
No owner yet8waiting up to 12.0
All escalations36median 6.8

Escalations tagged the week of 2026-10-26, by business hours to first owner.

5 Step 5:

Build the weekly fulfillment and escalation view

Four numbers for the Monday call, and who does what.

The narrative Querri writes:

Late shipments ran well above a usual week, 175 of the 199 from 3PL East, while cancellations held steady.

What you can create or export:

Build the weekly fulfillment and escalation view
ItemCountNext step
Late shipments from 3PL East175Call 3PL East
Escalations with no owner8Assign an owner
Escalations owned after 10+ hours8Ask for an update

This week's actions, week of 2026-10-26.

Send the Monday call to one warehouse, and give every open escalation a name.

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 a weekly view people trust

Compare with a usual week, not last week

One bad week makes the next look good. Averaging the 12 weeks before gives each warehouse and channel a fair baseline.

Watch time to first owner

Time to resolve hides the wait before anyone picks an escalation up. Measuring to the first assignment shows the ones nobody owns.

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

When a shipment is due, what business hours are, what counts as an owner: 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

"Business hours are Monday to Friday, 8:00 to 18:00 Eastern. Save that as a rule for the Gorgias tickets table."

Or bring the document that already says it

Upload your fulfillment SLA or support escalation 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:

  • Due: the ShipStation ship-by date, two business days after the order
  • Late: shipped after the ship-by date, or not shipped by Sunday
  • Amazon-fulfilled orders are out of scope
  • Escalation: a Gorgias ticket tagged escalated
  • First owner: the first time the ticket is assigned to a person
  • Usual week: the average of the 12 weeks before
Prompt

"Read our fulfillment SLA and propose the rules it states about ship-by dates and business days. 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 on Monday

Monday starts with one warehouse to call and a name on every open escalation. Changing business hours is a sentence.

Frequently asked questions

What counts as a late shipment?
A shipment that left after its ShipStation ship-by date, two business days after the order, or had not shipped by Sunday. 199 of the week's 5,008 were late; 74 had not shipped.
What is a usual week?
The average of the 12 weeks before. For late shipments it was 71.7; for 3PL East alone, 46.1.
Why are Amazon-fulfilled orders left out?
Amazon ships them from its own fulfillment centers, so your warehouse can't be late on them. The 37 Amazon orders here are the ones you ship yourself, on Amazon's promised ship dates.
How are business hours counted?
Monday to Friday, 8:00 to 18:00 Eastern, Curio's rule. An escalation tagged at 17:00 on Friday that gets an owner at 9:00 on Monday waited two business hours.
Why time to first owner and not time to resolve?
Because the risk is an escalation nobody has picked up. This week's median was 6.8 business hours, against 7.1 usually, yet 8 had no owner at all.
Does it say why the warehouse fell behind?
No. It shows where the late shipments came from and how far above usual they are. The call with 3PL East is where the reason comes from.
Did cancellations move?
No. The week's rate was 1.39%, against 1.37% over the 12 weeks before, inside its usual range of 1.15% to 1.49%.
How often should this run?
Every Monday, on a schedule, for the week just ended. A warehouse falling behind shows up in the first week it happens.