Shipping Complaints in Reviews: How to Answer Never Arrived and Took Forever

Shipping complaints are a different problem than product complaints

A review about a defective product is telling you something about the product. A review about a late or lost shipment is telling you something about the delivery experience, which for most ecommerce stores is handled by a third party — a carrier, a fulfillment partner, sometimes customs. You didn't make the decision that delayed the package, but your name is the one on the review.

That distinction matters for how you respond. Getting defensive about something you didn't directly cause reads just as badly as getting defensive about something you did. The response has to acknowledge the experience the customer actually had, regardless of who's technically at fault.

It also matters for how you track the problem. A store that only looks at review text after the fact has no way to tell, at a glance, how many of this month's one-star reviews are actually about shipping rather than the product itself. Tailwind's Orders product is built to flag delivery complaints by order — tying each review back to the specific order and its delivery status, so a pattern of shipping complaints shows up as a shipping problem instead of getting lumped in with product-quality reviews and misread as something wrong with the item.

Template replies for the most common shipping complaints

These are starting points, not scripts to paste verbatim. Fill in the specifics — order details, what actually happened, what you're doing about it — before posting.

"Never arrived"

We're sorry — a package that never shows up is frustrating, and we understand why you're upset. We'd like to make this right. Please reach out to us at [support email] with your order number so we can look into what happened with the carrier and get a replacement or refund moving right away.

Keep this one short. The customer doesn't need an explanation of carrier logistics in a public reply — they need to know you're taking it seriously and that there's a clear next step. Save the details for the private follow-up.

"Took way too long"

We know waiting that long for an order isn't the experience we want you to have. We're sorry for the delay. We're looking into what happened on this specific shipment, and we'd like to discuss options directly — please email us at [support email] with your order number.

If the delay was unusually long compared to your normal fulfillment time, it's worth saying so briefly — "this is well outside our typical delivery window" signals to other readers that this wasn't the usual experience, without sounding like an excuse.

"Arrived damaged in transit"

We're sorry to hear your order arrived damaged — that's not the condition we pack and ship things in, and we want to fix it. Please email us at [support email] with a photo of the damage and your order number, and we'll get a replacement sent out.

Asking for a photo isn't about doubting the customer — it's genuinely useful if you need to file a claim with the carrier, and most customers understand that when it's framed as part of fixing the problem rather than as a hurdle before you'll help.

This complaint is also worth watching for patterns. One review about a box arriving crushed is a shipping incident. Several reviews about the same product arriving crushed or broken, over a short window, usually points to a packaging problem — not enough padding for that specific item's weight or shape — rather than a string of unlucky carrier handling. A furniture or glassware seller who starts seeing a run of "arrived damaged" reviews on one SKU specifically should treat that as a packaging review, not just a batch of bad luck to apologize for one at a time.

"Tracking never updated"

We're sorry the tracking left you in the dark about where your order was — that's a bad experience even when the package does eventually arrive. Please reach out to us at [support email] with your order number so we can check with the carrier and get you a real update.

This complaint is specifically about information, not the delay itself. A customer who knows their package is five days behind schedule is usually less upset than one who has no idea where it is. Acknowledging that distinction in the reply shows you understand what actually frustrated them.

What all four templates have in common

• They acknowledge the specific complaint, not a generic "sorry for the inconvenience."
• They move the detailed resolution to a private channel — email or a direct message — rather than negotiating a refund in the public review thread.
• They don't argue about whose fault the delay was. Even when it's clearly a carrier issue, the public reply isn't the place to make that case.
• They include a concrete next step the customer can act on immediately.

For more on the general structure of replying to a negative review — tone, timing, what to avoid — see Tailwind's guide to responding to negative product reviews.

The proactive side: tell customers before they have to ask

Most "never arrived" and "took forever" reviews share a root cause: the customer found out about the delay by waiting and wondering, not by being told. A shipment confirmed delayed — stuck at a carrier hub, held in customs, missed its scanned checkpoint — is information you often have before the customer does. Sending it to them changes the experience even though it doesn't speed up the package.

Most carriers and fulfillment platforms expose this as an exception or delay status on the shipment, not just a raw tracking scan — the signal exists before the package is late enough for the customer to start wondering on their own. A store that waits for the customer to reach out first has already lost the chance to get ahead of the complaint; a store that watches for that exception status and sends the update automatically turns the same delay into a non-event for most customers, even though the delivery date hasn't changed at all.

A proactive delay notification works because it replaces uncertainty with information: "Your order is running behind schedule — here's the latest tracking update and a new estimated delivery date" lands very differently than silence followed by a late package. The customer still isn't happy about the delay, but they're not also managing the anxiety of not knowing what's going on.

This has to be sent to every customer whose shipment is actually delayed, the same way, regardless of anything about the order or the customer. The point of connecting delivery status to individual orders is to surface which orders are running late so you can act on the information — not to decide who hears about a delay based on how likely they seem to leave a bad review.

What this is not

Be explicit with your team about this boundary: a proactive shipping notification is not, and must never become, a way to talk an unhappy customer out of leaving a public review. If a customer is already frustrated and reaches out before writing a review, the honest response is to solve the actual problem — refund, replacement, real information about where the package is — not to offer something in exchange for silence, and not to ask them to hold off on posting a review while you "look into it." Both of those cross from customer service into review suppression, which damages trust in your reviews generally and isn't something Tailwind's tools are built to support.

The same principle applies to who gets the delay notification in the first place. Every customer with a confirmed delayed shipment gets told, full stop — not just the ones who seem calm, and not skipping the ones who seem likely to be upset. Filtering notifications by predicted reaction is the same mistake as filtering review requests by predicted sentiment: it turns a transparency tool into a selective one, and customers who find out they were treated differently lose more trust than the ones who got bad news on time.

Where this fits into your broader review response process

Shipping complaints are common enough in ecommerce that they deserve their own set of ready replies, separate from product-quality complaints, because the fix and the tone are different. But they're still part of the same review stream, and the same discipline applies: respond promptly, acknowledge the specific issue, move resolution to a private channel, and never treat the review itself as the thing to manage instead of the underlying problem.

Tailwind's pricing is $5 a month per tool, or $50 a month for the Full plan covering every tool including Orders — with the first month free, no credit card, and no contract, so you can see whether connecting delivery status to your review workflow actually cuts down on this category of complaint before committing to anything.