By Janson, Founder of ASG · Revised October 22, 2026
Real photograph from the ASG-provided media collection. This scene does not establish the status of any individual order. An order can be marked fulfilled in Shopify while its tracking page still offers little useful information. For a seller shipping from China, the immediate job is to establish what happened, explain what is known, and give the customer a dependable next step. A reassuring message is useful only when its facts are sound.
This guide connects shipping records, Shopify settings, customer messages and measurement. It uses five communication windows as a practical checklist. They are an editorial framework, not measured causes of most WISMO contacts, and sending updates does not guarantee that customers will stop asking.
Quick Answer
WISMO means “where is my order?” To handle it, separate the order date, verified physical handover, tracking events and delivery record. Build estimates from comparable orders, explain only the events you can verify, and assign an owner and next update time when information is missing. Measure customer contacts against the same order cohort before judging whether a change helped.
See Section 7 for US shipment-delay handling.
Contents
Use five windows to organize the investigation Keep physical events and system events separate Build a delivery estimate you can reproduce Check what Shopify actually displays Read USPS statuses without guessing Send messages supported by evidence Handle US shipment delays under the correct rule Investigate delivered but not received Give your supplier or agent a specific investigation Measure WISMO with a consistent order cohort Frequently asked questions Where ASG fits
1. Use Five Windows to Organize the Investigation
WISMO is a customer’s request for order whereabouts or progress. For this guide’s reporting method, it includes a customer asking about preparation, tracking or non-receipt. An automated tracking-page visit is not an inbound support contact. Define these boundaries before collecting numbers.
The following windows help a support team decide which evidence to request. They can overlap, and some orders skip them. A customer may first contact you during local delivery even though an earlier inventory problem caused the delay. Record the contact stage separately from the confirmed underlying cause.
Communication window
Evidence to check
Action for the seller
Communication window Before verified carrier handover Evidence to check Inventory status, packing record and dated carrier receipt Action for the seller Establish whether preparation or handover is still pending; name the person investigating.
Communication window Partner handover or an unclear transfer Evidence to check Partner reference, receiving carrier and acceptance evidence Action for the seller Identify which organization should confirm the transfer.
Communication window A gap between international tracking events Evidence to check Last verified event, event source and partner response Action for the seller Explain the last known fact; investigate without inventing a current location.
Communication window Destination delivery Evidence to check Destination carrier events and its current estimate Action for the seller Follow the applicable carrier process and communicate any supported change.
Communication window Delivery recorded, receipt disputed Evidence to check Address, delivery record and the customer’s account Action for the seller Open a non-receipt investigation; retain the relevant evidence.
One historical seller post illustrates the question, without establishing its prevalence:
Most customers are fine with it but quite a few start reaching out after about a week asking where their order is.
— u/Powerful-Annual6060, r/dropship, March 7, 2026
This is one person’s reported experience. It does not identify a particular physical handover stage or establish when customers on your routes will contact you.
Proactive communication and handoff diagnosis already appear in other WISMO guidance, including YourGPT and WISMOlabs . The contribution here is a connected workflow for Shopify sellers shipping from China: distinguish the evidence, check platform eligibility, apply the US shipment rule where relevant, and measure outcomes consistently.
2. Keep Physical Events and System Events Separate
Create a small event ledger for each parcel. Preserve the original timestamp, timezone, source and parcel identifier; normalize copies to UTC for calculations. For split shipments, keep parcel records under the same order. Do not overwrite the original tracking number when a destination number becomes available.
Event
What to record
What it does not establish
Event Order placed What to record Checkout timestamp and promised terms What it does not establish That inventory was available or dispatched
Event Physical carrier handover What to record Dated receipt or other verified evidence of possession What it does not establish That a public tracking event appeared immediately
Event First tracking event What to record Exact event text, timestamp and source What it does not establish Physical movement, if the event only describes a label or electronic pre-advice
Event First physical acceptance scan What to record Carrier-confirmed acceptance event, where available What it does not establish The exact earlier handover time if scanning was delayed
Event Destination-carrier acceptance What to record Evidence from the receiving carrier What it does not establish That earlier partners never held the parcel
Event Delivery recorded What to record Carrier event and any supporting delivery evidence What it does not establish That a disputed receipt has been resolved
Shopify’s Fulfilled status is a separate system event. Its individual fulfillment guide allows tracking to be added during fulfillment or afterward, and buying a label in Shopify can mark an order fulfilled. That status alone does not establish physical carrier possession.
Illustrative. These records are not a mandatory sequence, and the diagram is not ASG operating data. Use order to verified handover for a physical dispatch interval. If you only have tracking data, call the metric order to first recorded tracking event , then classify the event. Label it as a proxy; do not rename it dispatch time. Missing scans mean missing scan evidence, not proof that nothing moved. Conversely, a generated tracking number is not evidence that the carrier received a parcel.
These distinctions also make escalation more useful. Ask for the missing receipt or acceptance event, rather than asking a partner to repeat a general assurance that the order has shipped.
3. Build a Delivery Estimate You Can Reproduce
How long does shipping from China take? Your customer needs an estimate for the selected product, service and destination, counted from the stated starting point. A supplier’s transit quote may start at carrier acceptance and omit preparation. Do not present it as the complete checkout-to-delivery interval without checking its definition.
For an order-level delivery measure, define completion as the delivery of all parcels required for that order. Also retain parcel-level intervals for diagnosis. State whether partial deliveries, replacements and cancelled items are included; changing those rules changes the number.
For a straightforward starting model:
Select orders placed within a specified date range, with comparable origin, destination, service, product constraints and stock conditions.
Record the snapshot date and each order’s outcome: completed delivery, still open, lost, cancelled or another documented resolution.
Calculate elapsed checkout-to-complete-delivery time in calendar days using normalized timestamps. Keep a separate operational calendar for business-day commitments and holidays.
Show the sample size, delivery completion rate and unresolved outcomes beside any percentile. Compare recent periods before deciding whether the sample describes current operations.
A percentile calculated only from delivered orders describes that subset. Dropping slower open orders can make performance look better. Do not use a delivered-only percentile as an all-order promise. If unresolved orders materially affect the estimate, wait for a mature cohort or use an explicitly documented method for censored outcomes; report when the full-cohort percentile cannot yet be established. Lost or cancelled orders need their own outcome counts, not invented delivery dates.
A worked P90 example
Illustrative arithmetic, not ASG performance or a recommended sample size. Suppose all ten orders in a small cohort completed delivery. Their sorted checkout-to-delivery durations, measured as elapsed 24-hour days, are:
8, 9, 10, 10, 11, 12, 13, 14, 16, 20
Using the nearest-rank method, the P90 rank is ceil(0.90 × 10) = 9. The ninth value is 16 days : nine of these ten observations are at or below it. Other quantile conventions can return different values, so record the method. Ten orders illustrate the calculation; they do not establish a dependable future service level.
Illustrative. Nearest-rank P90 for the ten completed orders in the example above. For a date conversion using that example, an order placed at 12:00 UTC on November 1, 2026 , plus 16 elapsed calendar days, reaches 12:00 UTC on November 17, 2026 . This is a calculated point, not a guaranteed arrival or a complete customer-facing range. There is no business-day cutoff in this illustrative elapsed-time calculation. If you instead quote business days, define the origin timezone, cutoff, excluded weekdays and holiday calendar before producing dates.
Do not add the P90 preparation time to the P90 transport time and call the sum the end-to-end P90. Stage percentiles need not occur on the same orders. Calculate the total interval directly; use the stage intervals to locate operational problems.
Before publishing a range, document how both endpoints were selected, the eligible orders, its review date and known exclusions. Explain stock-dependent preparation separately where needed. An honest wider estimate is useful only if customers can understand its start point and what happens when it is missed.
4. Check What Shopify Actually Displays
Do not assume a delivery-date feature covers a route merely because the store uses Shopify. Separate the estimate in your shipping policy from the date that the customer’s actual checkout and order status page display.
Shopify’s automated delivery dates require eligible stores, inventory, origins, destinations and predicted timeframes. China is not in the current eligible-origin list. Orders must also stay within the supported region combinations. A China-to-US parcel therefore does not qualify for this feature under those published conditions. A qualifying US warehouse order is a different case; store registration alone does not determine eligibility.
Manual delivery dates combine configured fulfillment and transit time, but availability depends on the origin and shipping-rate type. Third-party app rates are excluded; mixed eligible and ineligible rates can also prevent display. The guide defines business days as Monday through Friday and a noon cutoff in the shipping origin’s local timezone, with calendar treatment described in its calculation rules. Check your exact configuration against the current availability table instead of assuming a China-origin rate qualifies.
If the native feature does not fit, use clear product-page, shipping-policy and confirmation copy, or evaluate an app against the same evidence requirements. Do not promise that an app will repair missing carrier events. Keep the estimate wording consistent wherever the customer sees it.
There is a reason to make estimates visible, without claiming a guaranteed conversion lift. Narvar’s November 2025 release reports that 73% said estimated delivery dates influenced purchase decisions. Its report combines platform data with an August 2025 survey of 3,461 US online shoppers. This is reported consumer preference, not a causal test of your store or a China-route benchmark.
The Shopify order status page has another dependency: a fulfilled order can remain Confirmed until carrier information reports transit. Supported carriers provide status updates and mapping; unsupported carriers instead provide a link to their tracking site without the same status display or live map updates. Multiple fulfillments receive separate sections.
For Shopify order tracking , check the carrier as well as the number. Shopify can misidentify an ambiguous format. Select the correct carrier, or use Other with a complete tracking URL where appropriate. An app should transmit carrier and URL information with the number so that identification does not rely on guessing.
As an implementation check, inspect a representative order from each active service, including a split order if you use them. Open its customer-facing link, verify the parcel it resolves to, compare the displayed estimate with the checkout promise, and inspect the messages actually sent. Record the date and results. This article describes that check; it does not report a completed Shopify admin test.
Illustrative. Check written estimates against the customer-facing display of an actual order. For detailed field mapping across suppliers, use ASG’s multi-supplier Shopify tracking guide .
Further reading: Shopify order routing across two locations .
5. Read USPS Statuses Without Guessing
If a customer sees In Transit to Next Facility , inspect the full USPS event history and its timestamps before interpreting it. A status phrase is not live geolocation or proof that a parcel cannot be lost. China origin alone does not establish its current country, facility or custodian.
Use USPS’s own status explanations for these distinctions:
Status or event family
Supported interpretation
Status or event family Label information awaiting USPS Supported interpretation Electronic label information does not establish that USPS received the parcel.
Status or event family Partner event with USPS Awaiting Item Supported interpretation USPS has not taken possession; ask the shipper about the partner transfer. This says nothing conclusive about an earlier origin-carrier handover.
Status or event family In Transit Supported interpretation USPS describes processing or transport toward the delivery office. Events can repeat. The wording does not establish a precise current location or exclude loss.
Status or event family Awaiting Delivery Scan Supported interpretation USPS did not record delivery by 9 p.m. local time on the out-for-delivery date and anticipates the next business day. If more than one full postal business day passes without delivery, its guidance is to submit a service request.
There is no universal rule in this guide that one to three days without a scan is normal. Set an investigation trigger using the actual service’s evidence and published procedures. A quiet period, a missed customer estimate and a missed legal shipment deadline are different triggers; one must not postpone action required by another.
Keep both the carrier’s event time and the time your system received it. A late data feed can otherwise look like slow transport. When information conflicts, say which source you are checking and when the customer will hear from you again.
Illustrative. Recorded details and evidence limits. 6. Send Messages Supported by Evidence
Another historical seller described a coordination problem:
It is like your Shopify store, your supplier’s tracking, and your customer’s emails are all in different buildings.
— u/Material_Vast_9851, r/dropship, November 3, 2025
The quotation describes that author’s experience; it is not evidence that every seller has the same failure or that a particular message schedule fixes it.
Shopify’s notification documentation distinguishes the triggers. Order creation produces the order confirmation; fulfillment triggers shipping confirmation, subject to the relevant sending option. Adding or changing tracking on an already fulfilled order can send a shipping update. Out-for-delivery and delivered notices depend on corresponding carrier or fulfillment-app events and notification settings. These events are not interchangeable with the first physical scan. Shop-app notifications also have separate controls, so do not assume every customer message is editable or suppressible in the store.
Use the following as illustrative message patterns , not ready-made assertions. Replace every bracketed field with verified information. If a fact is unavailable, remove it or explicitly say it is being checked.
Situation
Evidence required
Example customer message
Situation Order accepted Evidence required Order record and the estimate shown at purchase Example customer message “We received order [number]. Your estimated delivery range is [dates], counted from [starting point]. You can check updates at [link].”
Situation Handover not verified Evidence required The absence of confirmation in your records; an assigned investigator Example customer message “We are checking the carrier handover with [partner]. We do not yet have confirmation of receipt. [Team] will update you by [date, time and timezone].”
Situation Carrier acceptance verified Evidence required Identified carrier’s acceptance record Example customer message “[Carrier] recorded receipt on [date]. The latest available event is [plain-language fact]. Track this parcel at [link].”
Situation No newer verified event Evidence required Latest checked record and a follow-up task Example customer message “The latest event we can verify is [event] on [date]. We are checking for newer information and will update you by [deadline], even if the investigation is still open.”
Situation Customer delivery estimate missed Evidence required Original estimate and confirmed investigation status Example customer message “Your order has passed the estimated range. We are checking [specific issue]. [Supported revised estimate, if available.] Your next update is due [deadline]; contact us here about the available resolution.”
Illustrative. Templates must be completed from the actual order record; they do not promise delivery or a reduction in support contacts. Assign every exception an owner. Use a daily exception list as a starting workflow, but let the relevant deadline determine urgency.
Before adding automation, map which system sends each message and its trigger. Check for duplicates, stale estimates and conflicting parcel links. Where you control custom automations, stop routine reassurance when an exception needs an individual response. Test whether customers can reply and whether that reply reaches the responsible team. Evaluate contact rates and resolution quality after the change; message volume alone is not success.
Contact ASG to discuss your fulfillment requirements
This workflow gives a seller and its sourcing or fulfillment partner a shared set of questions. If you are evaluating ASG, bring the destination, product constraints, order pattern and examples of the records you need. Confirm service scope, evidence availability and responsibility for exceptions before relying on a particular process.
7. Handle US Shipment Delays Under the Correct Rule
This section concerns the US FTC Mail, Internet, or Telephone Order Merchandise Rule. It is not a worldwide shipping policy. Confirm whether the transaction falls within its scope and check other applicable consumer law separately.
Section 435.1 treats shipment as physical transfer into a carrier’s possession. A properly completed order includes the necessary payment or authorization and information needed to process and ship it, with additional rules for dishonored payments and credit qualification. A Shopify status or label creation cannot substitute for the physical event.
The FTC business guide explains the basic deadline: have a reasonable basis for the advertised shipment time. Without a clear, conspicuous shipment time, the usual default allows 30 days, starting when the seller receives an order meeting the rule’s completion requirements. A specific exception allows 50 days for an order accompanied by the customer’s application for the seller’s credit, when no shipment time was stated. These are shipment deadlines, not a universal guarantee of delivery within 30 days.
Section 435.2 : notify promptly once lateness is known, by the shipment deadline; offer delay or cancellation with prompt refund. Give a supported date; otherwise explain the delay and uncertain duration. Provide seller-paid response means.
First extension ≤30 days beyond the original deadline: expressly explain silence means consent unless rejection arrives before shipment and the revised date.Longer/indefinite first extension: explain automatic cancellation unless, within 30 days after the original deadline, shipment occurs without prior cancellation or specific consent arrives.Renewed notice: promptly, by the effective revised deadline, give a supported new date or say no date can be given and why. State explicitly: still unshipped and no specific further consent received by that deadline means automatic cancellation and prompt refund. Only a later date the buyer expressly accepts replaces that deadline. Prior express consent to an unanticipated indefinite extension beyond the first revised date under (b)(1)(iv) is excepted.Indefinite consent: expressly explain continuing cancellation by notice before actual shipment, starting after the original deadline for an indefinite first extension, or the effective revised deadline for a further indefinite extension.
Refund timing also matters. Under §435.1 , many required refund actions have a seven-working-day deadline after the refund right arises; a seller-as-creditor account adjustment has a one-billing-cycle rule. If the original payment method cannot be used, the rule provides a cash/check/money-order fallback within seven working days after discovering that inability. Refund the amount paid for unshipped merchandise using the prescribed form and timing for that payment arrangement.
Section 435.3 lists limited exceptions, including certain subscription deliveries after the initial shipment, seeds and growing plants, cash-on-delivery orders, and specified negative-option plans. Other applicable protections can remain relevant.
Keep the original promise, handover evidence, notices, customer responses and refund record together. After actual shipment, investigate delivery separately; shipment deadlines concern dispatch.
8. Investigate Delivered but Not Received
Treat a non-receipt report as an open investigation. Compare the purchased delivery address with the carrier record; ask about a reception desk, household member or secure delivery location without treating those possibilities as established facts. Give the customer an owner and the next action.
Preserve a concise case record: order and parcel identifiers, the customer-facing promise, handover and tracking evidence, delivery date and address evidence, correspondence, investigation reference and the resolution. Limit access to personal information and retain it under your applicable policy. A screenshot should preserve context and timestamps, not merely the word delivered.
Illustrative. Organize the investigation materials named above; no actual customer case is shown. Shopify’s delivery-photo guidance applies when a carrier supplies a photo for a fulfillment whose carrier status is delivered. Not every delivery has one. Shopify can display these photos with the order for a maximum of 90 days . This does not mean every carrier deletes all evidence on day 90. For Shopify Payments, photos from some carriers can enter a chargeback response automatically. Check what is actually present in the case.
For a non-receipt dispute, Shopify’s chargeback guidance recommends contacting the customer and submitting evidence relevant to the dispute. Its examples include fulfillment timing, billing information and shipping/tracking information. The issuing bank determines the outcome; Shopify does not. A tracking status or photo is evidence to assess, not a guarantee of winning.
Separate customer resolution, carrier compensation and payment-dispute deadlines in your case log. One open process should not cause the team to miss another deadline. Do not promise a refund, replacement or dispute result that the responsible team has not authorized under the applicable policy and law.
9. Give Your Supplier or Agent a Specific Investigation
A useful escalation asks for evidence that distinguishes preparation, handover, transport and reporting. Start with the affected parcel identifiers and the last verified facts, then ask:
Was the item available, and when was it ready for collection?
Which carrier physically received it, and what record supports that date?
Is the first tracking event a label record, partner event or physical acceptance scan?
Which destination carrier and parcel reference apply, and has acceptance been confirmed?
Is there a documented service exception or a data-feed issue?
Who owns the investigation, and when will they provide evidence or a progress update?
Illustrative. These questions request evidence; they do not assert that a shipment event occurred. If a partner cannot supply a handover timestamp, leave that field unknown. Compare order-to-first-event time as a disclosed proxy and track the missing-data rate separately. Do not rank two suppliers on “dispatch speed” if one provides actual receipts and the other only generates labels quickly.
Compare like with like: stocked and sourced-to-order products, services, destinations, seasons and product restrictions can differ. An apparent supplier effect may reflect that mix. Start with one defined group and one observable change, such as correcting the carrier mapping, before attributing a lower contact rate to a broader operational improvement.
For the detailed handover and tracking-data investigation, see why tracking updates become a fulfillment bottleneck . This article uses that distinction to connect the evidence with customer communication and measurement rather than repeating the complete troubleshooting guide.
10. Measure WISMO With a Consistent Order Cohort
Start with an order cohort: all eligible customer orders placed during a stated period. Decide exclusions before looking at outcomes, for example test orders. Keep unfulfilled orders in the denominator; customers can ask about them too. Include all relevant support channels and match each contact to an order ID.
Choose a fixed observation window after each order is placed. The following example uses 30 elapsed calendar days per order as a measurement choice, not an industry standard or a legal deadline. A cohort is ready for this comparison only after every included order has had the same opportunity to generate contacts.
Order-level WISMO rate = unique cohort orders with at least one qualifying inbound WISMO contact during their observation window ÷ all eligible orders in that same cohort × 100.
For an illustrative cohort placed during August 1–31, 2026 UTC, include contacts from each order’s placement timestamp up to, but not including, that timestamp plus 30 days. Use a snapshot at or after October 1, 2026, 00:00 UTC so every August order has a full window. These dates demonstrate the method; they are not a completed ASG measurement.
Illustrative cohort record
Value
Interpretation
Illustrative cohort record Eligible orders placed in the cohort period Value 100 Interpretation Denominator, including unfulfilled orders
Illustrative cohort record Unique orders with qualifying contacts within their own windows Value 12 Interpretation Numerator, deduplicated across channels
Illustrative cohort record Qualifying inbound messages about those orders Value 19 Interpretation Workload measure, not the numerator above
Illustrative cohort record Orders not dispatched at their observation-window end Value 6 Interpretation Remain in the denominator; overlap with the 12 is unspecified
Illustrative cohort record Order-level WISMO rate Value 12% Interpretation 12 ÷ 100 × 100
Illustrative. The six unshipped orders are included among the 100; their overlap with contacted orders is not supplied. No ASG operating results are represented. Count a split order once for this order-level rate, even if two parcels prompt messages. Count repeat messages separately in the workload measure. Exclude outbound notifications and tracking-page views. If your definition includes inbound questions answered by a bot, count them consistently rather than dropping them after automation launches. Report unmatched contacts separately until they can be assigned. With no eligible orders, the rate is undefined, not zero.
Tag one primary stage at the first qualifying contact to produce mutually exclusive stage counts. Base it on the latest verified event; if the evidence cannot distinguish overlapping windows, use an unknown category. Record subsequent stages and confirmed causes in separate fields. This prevents one contacted order from being counted as three unique orders and prevents the contact timestamp from being mistaken for the cause of delay.
Ship24’s discussion of WISMO statistics highlights why headline percentages need traceable definitions. Use your documented cohort, channels and observation window rather than importing a percentage from a different measurement. This guide does not use Ship24 as a substitute source for Narvar’s survey.
For before-and-after comparisons, hold the cohort definition and observation window constant and show the raw numerator and denominator. Separate destinations and services where practical; track delivery completion, unresolved cases and customer resolution alongside contact rate. A lower rate can reflect fewer accessible support channels or a different order mix. It does not, by itself, prove that messages prevented contacts or that a supplier improved.
Frequently Asked Questions
Can I use a supplier’s transit estimate as my checkout estimate?
Only after checking its starting event, included stages, destination, service and time units. If it starts at carrier acceptance, it omits earlier preparation. Build or validate a checkout-to-delivery estimate and disclose the conditions. Do not label a sum of stage percentiles as the end-to-end P90.
What if I cannot verify when a carrier received the parcel?
Record handover as unknown and ask for supporting evidence. You can measure order-to-first-tracking-event time as a clearly named proxy, but classify the event first. An electronic label record and a physical acceptance scan are different observations.
How often should I send a no-update message?
Use a cadence your team can honor, informed by the service, customer promise and investigation deadline. Give a concrete next-update time even when there is no new scan. Test the cadence against consistently measured outcomes. No universal day count in this guide replaces an applicable shipment-delay notice or carrier procedure.
Does fewer WISMO messages mean the shipping problem is solved?
No. Compare unique contacted orders, total messages, delivery outcomes and unresolved cases using the same cohort rules. Customers may stop contacting you for reasons unrelated to delivery quality. Treat the result as a signal to investigate, not proof of a particular cause.
About the Author
Janson is ASG’s founder. This guide covers order communication, shipping evidence and fulfillment investigation for Shopify sellers.
Sources and Reading Notes
Official sources are linked beside the claims they support. Shopify and USPS documentation describe their respective systems; the FTC and eCFR links concern the US rule within its scope. Narvar’s cited release describes its own research. The two dated Reddit quotations are historical individual statements, not representative evidence. Competitor and ASG links provide context and further reading, not independent proof of ASG performance.
Public documentation was checked on October 22, 2026 for the cited eCFR sections and FTC business guide, Shopify features, USPS statuses and the Narvar release. Historical quotations and other research also use source material collected on October 21. The Reddit wording was checked against saved source records; direct live access was unavailable during this revision.
The links support the specific statements beside them, not endorsements of ASG or guarantees of results. This guide paraphrases the linked guidance and includes two short, attributed historical quotations. The diagrams are original illustrations. The real photograph comes from the ASG-provided media collection; it does not identify the location or status of an individual order.
ASG Data Note
The five windows are an editorial investigation framework. Numerical examples, message patterns and diagrams are illustrative; they are not ASG shipment measurements, customer case studies or service guarantees. No Shopify backend or live notification test was performed for this guide. Any proposed ASG service, route, delivery estimate or exception process should be confirmed for the seller’s situation.
