WISMO on Shopify: Why Customers Ask and How to Stop Them Before They Do

WISMO stands for Where Is My Order. It is the most common question in e-commerce customer support, and it is almost entirely preventable. For many Shopify merchants, these tickets are seen as a normal cost of doing business. The cost is absorbed into the operations budget without being tracked explicitly.

However, it is important to calculate how much WISMO actually costs, why it happens, and what a few changes can do to the volume. This article covers the data on WISMO costs, the operational causes, and the specific actions that eliminate most of these inquiries before they are ever submitted.

How much do "Where Is My Order?" questions really cost?

WISMO inquiries account for 50 to 80 percent of all support volume, and each ticket costs between $4 and $12 to resolve. For a store with 1,000 monthly orders, this can add up to over $1,250 in support costs from this single question category alone.

While it feels like a minor support burden, the math says otherwise. ShippyPro's 2026 WISMO guide identifies it as the largest category of support volume. Ringly.io puts the cost per WISMO call at $5 to $6. ReadyCloud cites $4 to $12 per interaction. LateShipment calculates that deflecting 40% of these tickets can save $26,000 per month for a high-volume store.

The downstream costs extend beyond the ticket itself. WISMOlabs notes that 66% of customers may stop buying from a brand after a bad experience. According to DigitalGenius data cited by ReadyCloud, 69.7% of shoppers are less likely to buy again after a delay if they are not kept informed. The retention cost of this anxiety compounds far beyond the individual ticket.

Why do customers keep asking where their order is?

Customers ask because they expect real-time updates, similar to the experience Amazon provides. They are not just checking casually; they are monitoring progress because delivery certainty is now part of the product. Silence from a brand creates uncertainty, which leads directly to support tickets for information that already exists.

Serveretail's WISMO guide identifies this as the root cause. Every e-commerce brand is compared to the standard of real-time updates, accurate delivery windows, and proactive notifications. ShippyPro breaks these inquiries into two categories. True WISMO tickets are requests for information that already exists. Delivery issue tickets involve real problems like lost packages or incorrect addresses.

An estimated 70 to 90% of shipping inquiries are pure WISMO, according to ShippyPro. These are questions that proactive communication could have prevented. The remaining 10 to 30% are genuine delivery exceptions that require support. This distinction is operationally important. The goal is to eliminate the majority of inquiries that are requests for information you already have.

What causes most WISMO inquiries?

Most WISMO tickets are triggered by a lack of communication. This includes long silences after the order confirmation, confusing carrier jargon in tracking updates, and delivery timelines that were too optimistic. A missing self-service tracking option also forces customers to contact support for simple updates.

• Silence after confirmation. The most common trigger is a lack of communication between order confirmation and delivery. LateShipment identifies this as the dominant pattern. When a package takes longer than expected, the customer has no information and contacts support.
• Confusing tracking updates. Customers often cannot interpret carrier jargon like "In transit" or "Departure scan." ShippyPro notes this is a direct WISMO driver, as customers contact support for a translation.
• Unrealistic delivery timelines. Serveretail cites Shopify's research showing customers prefer realistic timelines over optimistic ones that slip. A customer told to expect a package on Tuesday that arrives Thursday will contact support.
• Stalled tracking information. Carrier tracking systems sometimes fail to update for 24 to 48 hours. From the customer's view, their package has stopped moving. ReadyCloud notes that 11% of packages hit a shipping exception, but even without a real delay, tracking gaps create anxiety.
• No self-service option. As Salesforce's WISMO guide describes, when customers cannot look up their order status themselves, they contact an agent. Every ticket that reaches a human could have been prevented with a tracking page.

How can I reduce the number of WISMO questions I get?

The most effective way to reduce WISMO is through proactive communication. This includes sending automated notifications for key delivery milestones and providing a branded tracking page with plain-language updates. Setting realistic delivery estimates at checkout and notifying customers of delays before they notice are also key.

• Automate notifications. The highest-impact change is implementing automated notifications at every milestone: order confirmed, shipped, out for delivery, and delivered. LateShipment reports this can reduce inquiries by up to 75%. ShippyPro cites reduction rates up to 80%.
• Use a branded tracking page. Sending customers to a carrier's site is a common mistake. A branded page on your domain with plain-language status updates reduces ambiguity. Malomo's research shows customers check tracking four to five times per order. AfterShip is a widely used app for this.
• Set realistic delivery estimates. PrettyDamnQuick advises setting accurate timeframes during the ordering process. Use historical data to inform your estimates. Including a specific delivery window in the confirmation email also sets a clear expectation.
• Notify customers about delays first. When a shipment is delayed, the best experience is receiving a message from the merchant before the customer discovers it. Serveretail notes this can prevent thousands of tickets during a single disruption.
• Offer self-service lookup. A chatbot or order status page lets customers find their status without an agent. Salesforce describes how AI chatbots can handle these inquiries in under a minute. Ringly.io notes modern AI agents handle 70 to 73% of WISMO calls without escalation.

For Shopify merchants, Shopify's native notification system sends shipping confirmation emails automatically. The common gap is the lack of updates between shipping and delivery. Adding "out for delivery" and "delivered" notifications closes this gap.

What if the WISMO question is about a real delivery problem?

A small percentage of shipping inquiries are not simple questions but genuine delivery exceptions like lost packages or incorrect addresses. While proactive communication cannot prevent these, you can stop address-related failures before they happen by verifying addresses before the order is sent to fulfillment.

These 10 to 30% of inquiries are real problems that no notification cadence can prevent. The most preventable type of delivery exception is an address-related failure. Shippo data shows 2.1% of all e-commerce parcels carry address issues. For a store with 1,000 orders per month, that is 21 orders that will generate genuine exception tickets.

These tickets are preventable by catching the address issue before fulfillment begins. Tacey operates at that pre-fulfillment layer, evaluating every Shopify order between payment and fulfillment for address quality and order-level issues before the warehouse sees the order. A questionable address is tagged for review, and the customer can fix it on the order status page before it ships. Preventing the delivery failure prevents the exception ticket that follows. Plans start at $29 a month for 750 orders and scale with order volume, with a 14-day free trial.

Frequently asked questions

What percentage of support tickets are WISMO-related?

WISMO inquiries are the largest category of e-commerce support volume. They account for 50 to 80 percent of all tickets, depending on the store and its communication strategy.

What's the difference between a WISMO ticket and a delivery exception?

A true WISMO ticket is a request for information that already exists, like a tracking number. A delivery exception is a ticket about a real problem, such as a lost package, a customs hold, or an incorrect shipping address that requires investigation.

How can a branded tracking page reduce WISMO tickets?

A branded tracking page keeps customers on your site and translates confusing carrier jargon into plain language. This reduces the ambiguity that causes customers to contact support for an explanation of their order's status.

How effective are proactive shipping notifications?

Proactive notifications are highly effective, with brands reporting a reduction in WISMO inquiries by up to 75 or 80 percent. Sending automated updates for key events like "shipped," "out for delivery," and "delivered" answers questions before they are asked.

What is the most common cause of WISMO inquiries?

The most common cause is silence. When a customer receives an order confirmation and then hears nothing until the package is supposed to arrive, any uncertainty or delay will trigger a support ticket.

How many e-commerce packages have address problems?

According to data from Shippo, 2.1% of all e-commerce parcels have address issues. These problems lead to genuine delivery exceptions that are preventable if caught before the order ships.