How to Measure Post-Purchase Experience: 7 Metrics every Ecommerce Store Should Track
To measure post-purchase experience, track the full journey from order confirmation to delivery and the customer’s next action. The most useful scorecard combines delivery reliability, customer effort, support demand, satisfaction, and repeat behavior rather than relying on a single survey score. For most ecommerce teams, seven practical metrics are delivery-promise accuracy, on-time delivery rate, delivery exception rate, WISMO contact rate, tracking engagement, post-delivery satisfaction, and repeat purchase rate.
These metrics help a store identify whether a poor experience comes from an unrealistic promise, a carrier or fulfillment problem, unclear communication, or a product and service issue. The objective is not simply to collect more data. It is to connect each measure to an operational decision.
What post-purchase experience measurement should include
The post-purchase experience starts after checkout, but it is shaped by decisions made before the order is placed. A delivery estimate shown on the product page creates an expectation. The order confirmation creates another communication point. Shipment visibility, exception handling, delivery, returns, refunds, and the customer’s next purchase complete the picture.
A useful measurement system should therefore answer four questions:
- Did the store deliver when it said it would?
- Did the customer receive clear and timely information?
- How much effort did the customer need to spend to get help?
- Did the experience support satisfaction and future purchasing?
Measure each metric by order, shipment, customer, and time period where possible. Segment results by carrier, destination, service level, product category, warehouse, and promised delivery window. An overall average can conceal a serious problem in one region or shipping method.
1. Delivery-promise accuracy
What it measures: how often an order arrives within the delivery window promised to the customer.
Basic formula: orders delivered within the promised window ÷ orders with a valid delivery promise × 100.
This is often more meaningful than measuring transit speed alone. A three-day delivery that arrives on the fifth day may create more dissatisfaction than a five-day delivery that arrives on the fourth day. The metric evaluates the gap between the customer’s expectation and the actual outcome.
Define the rule before reporting it. For example, decide whether delivery on the final promised date counts as on time, how weekends and public holidays are treated, and whether the clock starts at checkout, payment authorization, or carrier acceptance. Exclude canceled orders and orders with incomplete delivery data, but report the exclusion rate separately.
Use the result to review checkout promises, processing-time assumptions, inventory allocation, and carrier service selection. If on-time performance is high but promise accuracy is low, the problem may be an overly conservative or inconsistent delivery estimate rather than transportation performance.
2. On-time delivery rate
What it measures: the percentage of shipments delivered by the agreed or operational due date.
Basic formula: shipments delivered on or before the due date ÷ shipments with a confirmed delivery date × 100.
This metric is related to promise accuracy but should not replace it. A store may calculate an internal due date from its fulfillment rules, while the customer sees a different promise at checkout. Comparing both measures shows whether the issue is inside the warehouse, in transportation, or in the way the date is presented.
Track the median and distribution of delivery delay as well as the percentage delivered on time. A rate can remain stable while a small group of orders experiences very long delays. Report late shipments by one-day, two-to-three-day, and longer delays if the order volume supports useful segmentation.
Do not compare carriers without controlling for service level, destination, package type, and difficult delivery periods. A carrier handling remote or international shipments may appear worse in a raw comparison because the shipment mix is different.
3. Delivery exception rate
What it measures: how frequently shipments encounter an event that threatens normal delivery, such as an address issue, customs delay, failed attempt, damage report, or extended lack of movement.
Basic formula: shipments with at least one defined exception ÷ shipments in transit or completed during the period × 100.
The exact event list depends on the carrier data available to the store. Write the list down and keep it stable enough to compare periods. It can be useful to distinguish preventable exceptions, such as incomplete addresses, from events that require carrier or customer intervention.
Pair the rate with resolution time: the time from the first exception scan to a successful delivery, replacement, refund, or other resolution. A low exception rate does not necessarily indicate a good experience if unresolved cases remain open for a long time.
This metric is particularly useful for cross-border ecommerce, where customs documentation, destination-country rules, and handoffs between logistics providers can affect the customer journey. Avoid attributing every exception to a carrier before reviewing the order data and the specific event description.
4. WISMO contact rate
WISMO means “Where is my order?” The WISMO contact rate measures how often customers contact support because they cannot find, interpret, or trust shipment information.
Basic formula: support conversations classified as order-location or delivery-status requests ÷ delivered or in-transit orders × 100.
Use a consistent classification across email, chat, phone, social messages, and contact forms. If your support system cannot identify WISMO conversations reliably, begin with a sample-based audit and create a tagging rule. Track both the rate and the share of support contacts that are WISMO-related.
A high result can indicate late deliveries, missing tracking events, confusing status language, an inaccessible tracking page, or a notification gap. It is not proof that the carrier is at fault. Compare WISMO contacts with delivery-promise accuracy and exception rate to find the likely cause.
A store can use this metric to prioritize clearer order emails, a visible tracking link, proactive exception messages, and better customer-service macros. The target should not be zero contacts. Some customers will need help with address changes, returns, or unusual delivery circumstances.
5. Tracking engagement and status visibility
What it measures: whether customers can access and use shipment information after an order ships.
Possible measures include the percentage of customers who open a shipping notification, click the tracking link, visit the order-status page, or receive a meaningful status update before delivery. Choose events that your analytics setup can record consistently. Do not treat a click as proof that the customer understood the status or had a positive experience.
A useful dashboard separates:
- Notification delivery and open rate
- Tracking-link click-through rate
- Tracking-page visits per shipment
- Shipments with no visible update for a defined period
- Customers who contacted support after visiting the tracking page
Interpret repeated tracking visits carefully. They may show strong engagement, but they may also signal uncertainty or a stalled shipment. Combine engagement data with WISMO contacts, exceptions, and delivery outcomes. For stores using a third-party tracking service, verify which events are available and whether the data can be connected to an order or customer record.
For Shopify merchants and other direct-to-consumer sellers, 17TRACK’s Shopify app is one example of a product positioned around order tracking and post-purchase shipment visibility. Its suitability should be checked against the store’s carriers, notification requirements, analytics needs, and data workflow rather than assumed from the product category alone.
6. Post-delivery customer satisfaction
What it measures: the customer’s reported satisfaction after the delivery or support interaction.
A short CSAT survey can ask customers to rate the experience on a defined scale after delivery. The score should be calculated using a documented rule, such as the percentage selecting the top two options on a five-point scale. The exact scale and threshold matter, so do not compare results across surveys that use different questions or scoring rules.
Ask about a specific experience instead of using a vague question. Examples include “How satisfied were you with the delivery of this order?” or “How easy was it to find your shipment status?” Include an optional comment field, but do not make a long survey part of the delivery flow.
CSAT is most useful when linked to operational facts such as delivery timing, carrier, destination, and whether an exception occurred. Survey response bias is a limitation: customers who answer may not represent all buyers. Report response volume and response rate alongside the score.
NPS can be used as a broader relationship measure, but it should not substitute for delivery-specific feedback. Bain describes the standard NPS question as a 0-to-10 likelihood-to-recommend question, with responses grouped into detractors, passives, and promoters. Use that method consistently if you choose NPS; do not label a different satisfaction question as NPS.
7. Repeat purchase rate
What it measures: the percentage of customers who place another order within a defined observation window.
Basic formula: customers from a defined first-order cohort who place at least one additional order during the observation window ÷ customers in that cohort × 100.
Set the cohort and time window before reporting the metric. A replenishment product may have a naturally shorter repurchase cycle than a furniture or seasonal product. Compare like-for-like cohorts, and avoid judging a recent cohort before it has had enough time to repurchase.
Repeat purchase is an outcome metric, not a pure measure of delivery quality. Product satisfaction, price, promotions, assortment, seasonality, and marketing can all affect it. Use it with delivery and customer-feedback metrics. If repeat purchase falls while delivery performance worsens, the post-purchase journey may be contributing to the decline. That relationship still requires further testing.
Track return and refund behavior as a supporting diagnostic. A return may reflect product fit, product quality, buyer expectations, or delivery damage, so it should not automatically be treated as a logistics failure. Segment returns by reason and compare them with delivery exceptions and customer comments.
How to build a practical post-purchase dashboard
Start with one owner for the dashboard and named owners for each action. Operations may own delivery and exception metrics, customer support may own WISMO, marketing or customer experience teams may own surveys, and ecommerce leadership may monitor repeat purchase. Shared visibility matters, but unclear ownership makes metrics passive reporting.
- Define the event and denominator. Specify what counts as an order, shipment, delivered order, support contact, response, and repeat customer.
- Set a baseline. Use a stable historical period, then document unusual conditions such as carrier disruptions or major promotions.
- Segment before acting. Review carrier, region, service, warehouse, product, and customer cohort. Avoid changing a carrier based only on an unadjusted average.
- Connect leading and lagging indicators. Tracking clicks and exception alerts are earlier signals; CSAT and repeat purchase usually appear later.
- Choose thresholds that trigger action. For example, a rise in exception rate can trigger a carrier review, while a rise in WISMO can trigger a notification or tracking-page audit.
- Review data quality. Check missing tracking numbers, duplicate shipments, inconsistent time zones, canceled orders, and late-arriving carrier events.
A weekly operational review can focus on promise accuracy, on-time delivery, exceptions, and WISMO. A monthly or quarterly review can examine satisfaction, repeat purchase, return reasons, and longer-term trends. The cadence should match how quickly the team can investigate and correct problems.
What a good measurement system should reveal
The value of these seven metrics comes from their relationships. Low promise accuracy with acceptable carrier performance suggests a checkout-estimate problem. High exception rates with high WISMO contacts point toward proactive intervention. Strong tracking engagement with poor satisfaction may indicate that customers are checking often because shipments are delayed. Good delivery performance with weak repeat purchase may shift attention to product quality, returns, price, or customer support.
Use the dashboard to form a specific hypothesis, test one operational change, and compare the affected cohort with a suitable baseline. That approach is more reliable than chasing a universal benchmark or optimizing one score in isolation.
FAQ
Which post-purchase metric should a small ecommerce store track first?
Start with delivery-promise accuracy and WISMO contact rate if order and support data are available. Together, they show whether customers receive what they were promised and whether they need to ask for information. Add exception rate when shipment events are reliable.
Is on-time delivery rate the same as customer satisfaction?
No. On-time delivery is an operational outcome, while satisfaction is a customer-reported opinion. A shipment can arrive on time but still create dissatisfaction because of poor communication, damage, or an inconvenient delivery experience.
How often should a store measure post-purchase experience?
Monitor operational metrics continuously or weekly when order volume supports it. Review survey and repeat-purchase metrics less frequently because they need enough responses and time to form meaningful cohorts.
Should I use NPS or CSAT after delivery?
Use CSAT for a specific delivery or support interaction and NPS for a broader relationship question. They answer different questions and should not be treated as interchangeable.
How can I tell whether a carrier is causing a poor experience?
Compare carriers using the same service level, destination mix, product type, and measurement rules. Review promise accuracy, on-time delivery, exceptions, WISMO, and customer feedback together. A raw carrier average is not enough for a fair conclusion.
