Stores & orders

How to handle "where is my order" emails in a small store: answer from the order, act on it, stay until delivered

A tracking link answers the question a store expects. The email asks a different one: what is happening to my parcel, and what will you do about it. Here are the base rates, the five states behind the question, and the reply each one deserves.

Short answer

Handle a "where is my order" (WISMO) email by reading the order and the latest carrier event, saying plainly which of five states the parcel is in, doing the one action your rules allow for that state, and keeping the thread open until the parcel is delivered or the owner has replied. WISMO was 18% of incoming requests in Gorgias's 2023 data; for a 1,000-order-a-month store that is roughly 40 to 150 emails a month and about $6k to $22k a year of handling.

18%

of incoming support requests were WISMO

Gorgias platform data, 2023

19–46

support tickets per 100 orders, by vertical

Gorgias Ecom Lab, March 2026

30%

of email handoffs from AI were abandoned

Gorgias Ecom Lab, Oct 2025 to Apr 2026 data

The most common email in a small store's inbox is also the one most often answered with the wrong thing. "Where is my order" (WISMO) made up 18% of incoming requests in Gorgias's 2023 platform data, and Gorgias priced a human-handled ticket at about $12.18 to $12.40.1 For a store shipping 1,000 orders a month, that is roughly 40 to 150 WISMO emails a month and about $6,000 to $22,000 a year of handling. The usual reply is a tracking link. The better reply reads the order and the last carrier event, names the state the parcel is in, does the one thing your rules allow for that state, and keeps the thread open until the parcel arrives.

What does WISMO mean, and how many of these emails should a small store expect?#

WISMO is a customer contact asking about the status of an order already paid for. It is the largest single category in most store inboxes, and owners say so in public: a thread in r/ecommerce with 130+ comments (September 2026) asked, "Is it all just the typical 'Where is my order?'"6 A thread in r/dropship (30+ comments, November 2025) asked how other stores were "actually handling" it.7

The base rate for total volume is firmer than the base rate for WISMO's share. Gorgias's Ecom Lab measured 19 to 46 support tickets per 100 orders in March 2026, depending on vertical: about 20 for food and beverage, 22 for apparel and 46 for electronics.23 The 18% WISMO share is from 2023, and no 2024 to 2026 primary figure was found for this piece. Vendor pages that claim 30% to 40% were not verified and are not used here.

WISMO volume and handling cost, worked from published rates
StoreTickets per monthWISMO per month (18%)Handling at $12.18Per year
Apparel, 300 orders/month66 (22 per 100)~12~$146~$1,750
Apparel, 1,000 orders/month220~40~$487~$5,850
Electronics, 1,000 orders/month460 (46 per 100)~83~$1,010~$12,100
Gorgias's own worked example, 1,000 orders/monthn/a150~$1,860~$22,300

Sources: tickets per 100 orders, Gorgias Ecom Lab, March 2026; WISMO share and cost per ticket, Gorgias, 2023. The rows combine a 2026 volume rate with a 2023 share, so treat them as a range, not a forecast. For a solo owner the "cost" is your own time.

The tracking link fails because it answers a general question while the customer is asking a personal one. The page shows carrier events; the customer wants to know what those events mean for their parcel and what the store will do. That gap is widest exactly where the tracking page is least helpful.

Gorgias's own 2023 automation guide shows the boundary. Its WISMO rules fire when an order has a tracking number or is not yet fulfilled, and the guide says delivery delays and lost packages still need a human.1 Those are the emails that arrive with the most heat. The tracking-number case is the easy one; the delayed, stuck and missing parcels make up the expensive tail.

The consequence of silence is not only a second email. On Hacker News in April 2026, a commenter explained why stores send so many shipping emails: without them, customers file "credit card disputes and BBB complaints" and blast support "over a two day shipping delay."5 The per-dispute fee was not verified for this piece, but the direction is clear: an unanswered WISMO email can turn into a dispute. The companion piece on the 48 hours after "order confirmed" looks at why status pages and email drips both miss this.

The five WISMO states and the honest reply for each#

Every WISMO email maps to one of five parcel states, and each state has one true sentence, one allowed action and one owner decision. The table is the core of this guide. Fill in the "allowed action" column with your own policy before anyone, person or assistant, answers from it.

The five WISMO states: honest reply, allowed action, owner decision Copy this into your support doc and replace the bracketed parts with your policy.
StateWhat is trueHonest reply saysAllowed without the ownerGoes to the owner
1. Not yet shippedPaid, not packed or not labelledWhen it will ship, per your stated dispatch timeConfirm the dispatch window; note any change requestAny delay beyond your stated window
2. Label created, no carrier scanPacked and labelled; carrier has not scanned itDate the label was made; that the carrier has not scanned it yet; when you will check againCheck again after [X] business days and write backNo scan after [Y] business days
3. In transit, normalScans moving; within the carrier's estimateLast scan, place and date; expected windowSend the tracking link with that summaryNothing, unless the window passes
4. Carrier exception or delayScans stopped, returned, or marked exceptionWhat the exception says, in plain words; what you are doingContact the carrier or open an inquiry per your processReship, refund or claim decision
5. Delivered, not receivedCarrier shows delivered; customer has nothingDelivery time and any location detail; a few checks (neighbours, mailroom)Ask for the checks; set a time to follow upReship, refund or claim decision

States 4 and 5 involve money, so the reply tells the customer who decides and by when. Never promise a reship or refund in an automatic reply unless your written policy already does.

The table also shows where the volume can be cut without risk. States 1 and 3 can be answered from the order and the carrier page alone; state 2 needs a scheduled re-check; states 4 and 5 need a decision. If a store's WISMO mix is mostly 1 and 3, the problem is speed. If it is mostly 4 and 5, the problem is carrier choice or packaging, and no reply template fixes it.

Why should a WISMO thread stay open until the parcel arrives?#

A WISMO thread should stay open until delivery because the customer's question is not answered until the parcel is in their hands. A reply that closes the ticket on "here is your tracking" leaves the store waiting for the second, angrier email. The rule is simple: the thread closes when the carrier shows delivered and the customer has not reported a problem, or when the owner has replied to a state 4 or 5 decision.

Illustration
Customer · Sun 21:12Ordered last Tuesday, tracking hasn't changed in three days. Where is it?
Assistant · Sun 21:13Your order was packed and a shipping label was created on Wednesday. The carrier hasn't scanned it yet, which is why tracking hasn't moved. I'll check again on Tuesday morning and write to you either way. If it still hasn't been scanned by then, the owner will decide on next steps and reply by Tuesday 17:00.
State 2. Re-check due Tue 09:00. Owner decision if no scan.

Handoffs are where open threads usually die. Gorgias found that when AI support handed a ticket to a human, 30% of email handoffs and 42% of contact-form handoffs were abandoned, and one-third of all handed-off tickets never received a human reply.4 Email is also slow by default: Gorgias puts the median email first response at 12+ hours.8 A state 4 or 5 email that waits that long has had time to become a dispute.

What should the owner see when a WISMO email needs a decision?#

The owner should see the decision, not the thread: which state, what the carrier shows, what the customer was told, and what your policy allows. A short record like the one below lets a one-person store decide on a phone in under a minute.

Example receipt

Asked
"Says delivered Friday, nothing here." Order placed 12 days ago.
Rule
State 5, delivered not received: ask for checks, owner decides reship or refund.
Sources
Order record; carrier page showing delivered Fri 14:02; returns and lost-parcel policy.
Sent
From support@ (store address). Customer told the owner will reply by Mon 17:00.

The receipt shows what was used, which matters when the customer later disputes the charge. A record of the carrier event, the policy and the time of each reply is the evidence a store needs.

Leading indicators: is your WISMO load improving or getting worse?#

WISMO volume is a lagging indicator of fulfilment and carrier quality, so the useful signals sit upstream. If a store tracks the measures below monthly, it can see a carrier or packing problem before the inbox fills.

  • WISMO emails per 100 orders. Compare against your own baseline; the 18% share applied to 19 to 46 tickets per 100 orders gives about 3 to 8 as a rough reference.
  • Share of orders in state 2 for more than two business days. A rise points to a hand-off problem between packing and the carrier.
  • State 4 and 5 counts by carrier. If one carrier produces most exceptions, the fix is commercial, not a template.
  • Median time to first reply on WISMO, and share of threads closed only after delivery. These measure the inbox, not the parcel.
  • Disputes and chargebacks that mention delivery. The most expensive and the most delayed signal.

The figures in this guide expire when Gorgias or another platform publishes a 2024 to 2026 WISMO share. If that share differs from 18% by more than five points, rework the volume table first. The five-state table does not expire; carriers change their wording, not the states.

Where Valet fits#

Valet is an AI assistant for written inquiries: you forward support@ or orders@ to it, and replies go out from your own address once the domain is verified. It answers only from the facts you give it, such as dispatch times, carrier rules and your lost-parcel policy, and never invents a refund or a promise. Reships, refunds and claims are money decisions, so they go to you with one-tap replies, and the customer is told when you will reply. Each email moves through the Valet Inquiry States with a next step and a time, and every reply carries a Valet receipt. Valet could measure what share of WISMO threads close without the owner; it has no such figure yet. To see how your own order emails are handled today, start with the free lead check.

Questions people ask

What does WISMO mean in ecommerce?

WISMO stands for "where is my order": a customer contact asking about the status of an order they have already paid for. Gorgias reported in 2023 that WISMO made up 18% of incoming requests on its platform.

What should I say when a customer asks where their order is?

Say which state the parcel is in (not yet shipped, label created but not scanned, in transit, carrier exception, or delivered), give the date of the last carrier event, say what you will do next and when you will write again. Avoid sending only the tracking link.

Why do customers keep asking where their order is when they have tracking?

Because the tracking page shows events, not explanations. A customer whose parcel has shown "label created" for three days, or "delivered" when nothing arrived, is asking what that means for them and what you will do.

When should a WISMO email go to the store owner?

When the answer involves money or a judgement: a reship, a refund, a carrier claim, a delivered-but-missing parcel, or an angry customer. The customer should be told who will reply and by when.

How many WISMO emails should a small store expect?

Gorgias's March 2026 data shows 19 to 46 support tickets per 100 orders depending on vertical, and its 2023 data put WISMO at 18% of requests. A 1,000-order apparel store would see roughly 40 a month on those figures; Gorgias's own worked example used 150.

Sources

Confidence: H primary source checked · M credible secondary or reported · L vendor claim or single report. Reddit and forum items are quoted from public threads and summarised, not endorsed.

  1. Automate WISMO requests · Gorgias · 2023-11-13 M
  2. Stop benchmarking against the average · Gorgias Ecom Lab · 2026-04-01 H
  3. Ticket volume · Gorgias · 2026-05-22 H
  4. The cheapest ticket is the one a human never touches · Gorgias Ecom Lab · 2026 H
  5. Comment by pembrook on "One item purchased, ten emails" · Hacker News · 2026-04-08 H
  6. "E-commerce owner with lots of support emails" (130+ comments; Google snippet) · Reddit, r/ecommerce · c. 2026-09 M
  7. "How are you all actually handling the 'Where Is My Order?' [question]" (30+ comments; Google snippet) · Reddit, r/dropship · c. 2025-11 M
  8. Customer service benchmarks · Gorgias · 2026-05-15 H

How to cite this page

Cite this page

Valet, "How to handle 'where is my order' emails in a small store", valet.team, October 2026.

Review cycle: semi volatile. Last checked 1 October 2026. Spot an error? Tell us and we'll fix it and note the change.