Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
User experience (UX) is a major consideration for e-commerce firms in an ever-increasing competitive environment. While you may be focusing on personalizing the purchasing experience for your customers and minimizing the number of actions they need to take to complete a purchase, you should remember that UX also depends on the post-purchase experience you provide for your customers.
According to a recent study by consumer marketing firm Narvar, how your customers perceive their post-purchase experience can make the difference between a one-time customer and a loyal one that keeps returning to your site to make a purchase. Narvar surveyed more than 1,000 customers who purchased something online during the past 12 months and found that 49% worried about their package being damaged in transit and 42% thought that their package would not be delivered within the promised timeframe.
The study found that on-time delivery was a crucial factor in developing a positive UX leading to long-term customer relationships. About 60% of the respondents to the survey stated they were more likely to make a purchase from an e-commerce firm that provided a definite date for delivering their purchase, while 72% said that receiving an item on the promised delivery date was the number-one reason for making future purchases from that retailer.
Narvar found that the second most important factor in building long-term relationships with customers was to simplify the returns process, with 70% of the respondents stating that an easy exchange or return process would make them more likely to become repeat customers.
The study also noted the impact that Amazon has had on other e-commerce firms, as consumers are now holding them to the higher standard that Amazon created. The “Amazon effect,” which allowed the company to expand its market share by offering fast, free shipping and easy returns, no longer applies to just Amazon. Consumers now expect other e-commerce firms to provide the same level of customer service and are more likely to remain loyal to firms that do.
Narvar found that age was a factor in determining how customers preferred post-delivery interaction with e-commerce firms. Customers between the ages of 18 and 29 preferred email communication but were more receptive than older customers to receiving communications by Facebook Messenger, the retailer’s app and SMS/texts.
When asked what post-purchase information would make them more satisfied with the retailer, 61% said that a thank you message mattered the most. Other factors mentioned were personalized recommendations, examples of how other customers were using the product and recommendations on how to use the product. Customers under the age of 30 were more interested in seeing how others were using the product (37%) than those who were aged 30 or older (21%).
While devoting resources to personalizing consumer experience does improve UX, the study made it clear that e-commerce firms can benefit most by devoting more resources to basics of post-purchase UX: ensuring that products arrive on time and undamaged, making returns easy, and thanking their customers for making a purchase.
StatusCake Team
Share this
More from StatusCake
Designing Alerts for Action
3 min read In the first two posts of this series, we explored how alert noise emerges from design decisions, and why notification lists fail to create accountability when responsibility is unclear. There’s a deeper issue underneath both of those problems. Many alerting systems are designed without being clear about the outcome they’re meant to produce. When teams
James Barnes
February 18, 2026
A Notification List Is Not a Team
3 min read In the previous post, we looked at how alert noise is rarely accidental. It’s usually the result of sensible decisions layered over time, until responsibility becomes diffuse and response slows. One of the most persistent assumptions behind this pattern is simple. If enough people are notified, someone will take responsibility. After more than fourteen years
James Barnes
February 11, 2026
Alert Noise Isn’t an Accident — It’s a Design Decision
3 min read In a previous post, The Incident Checklist: Reducing Cognitive Load When It Matters Most, we explored how incidents stop being purely technical problems and become human ones. These are moments where decision-making under pressure and cognitive load matter more than perfect root cause analysis. When systems don’t support people clearly in those moments, teams compensate.
James Barnes
February 4, 2026
The Incident Checklist: Reducing Cognitive Load When It Matters Most
4 min read In the previous post, we looked at what happens after detection; when incidents stop being purely technical problems and become human ones, with cognitive load as the real constraint. This post assumes that context. The question here is simpler and more practical. What actually helps teams think clearly and act well once things are already
James Barnes
January 28, 2026
When Things Go Wrong, Systems Should Help Humans — Not Fight Them
3 min read In the previous post, we explored how AI accelerates delivery and compresses the time between change and user impact. As velocity increases, knowing that something has gone wrong before users do becomes a critical capability. But detection is only the beginning. Once alerts fire and dashboards light up, humans still have to interpret what’s happening,
James Barnes
January 21, 2026
When AI Speeds Up Change, Knowing First Becomes the Constraint
5 min read In a recent post, I argued that AI doesn’t fix weak engineering processes; rather it amplifies them. Strong review practices, clear ownership, and solid fundamentals still matter just as much when code is AI-assisted as when it’s not. That post sparked a follow-up question in the comments that’s worth sitting with: With AI speeding things
James Barnes
January 14, 2026