When an Order Goes Wrong, How Fast Should Your 3PL Actually Fix It?

Key takeaways

• Orders go wrong. The question that decides whether you keep the customer isn't whether it went wrong — it's how fast the fix happens, from the customer's side of the clock.
• Response time (how fast your 3PL replies) is not the same as resolution time (how fast the problem is actually solved). Most SLAs cover the first and quietly ignore the second.
• Different problems have different realistic clocks. A pick error should be fixed same-day. A lost package should be resolved within 48 hours. An inventory discrepancy should be flagged before your customer finds it.
• Resolution usually slows down for three reasons: handoffs between people, approval chains for refunds and reships, and missing data at the point of decision.
• The right question to ask isn't "what's your response SLA?" It's "walk me through a specific example of a problem you resolved — who did what, how long did each step take, and how did you communicate it to the brand and the customer?"

Nobody runs a perfect operation. Pick errors happen. Packages get lost. SKUs that your system says are in stock turn out not to be. The question that decides whether you keep that customer isn't whether something went wrong. It's how fast your 3PL moved on the fix — measured from the moment the customer noticed, not from the moment the ticket was opened.

Most 3PLs quote you a response SLA and leave the resolution speed as "we work it until it's done." That's the gap where customer trust gets lost.

What counts as "an order gone wrong"?

Five categories cover most of what you'll ever see:

• Pick errors — wrong item, wrong quantity, wrong variant. The customer gets the box, opens it, and emails you.
• Pack errors — right items, bad protection. Breakage in transit, damage on arrival.
• Lost packages — carrier marks delivered, nothing arrived; or no scans for 72 hours mid-transit.
• Inventory discrepancies — the SKU showed as available, sold at checkout, isn't actually on the shelf. The oversell.
• Delayed fulfillment — the order sat too long before shipping, missed the delivery window the customer was promised.

Each of these has its own realistic clock. Treating them all with one SLA is why resolution feels slow even when response is "fast."

Response time vs. resolution time — which matters more?

Resolution. The response is table stakes.

A 3PL that replies within an hour but takes four days to actually fix the problem has given you nothing useful. In the meantime, your customer has emailed support twice, left a review, and decided whether they're ordering from you again.

The response SLA tells you how fast someone will acknowledge the ticket. The resolution SLA tells you how fast the problem actually goes away. If your 3PL only talks about the first one, that's what they're accountable for.

What's a realistic resolution clock by issue type?

The honest ranges, for a 3PL running a real operation:

• Pick errors: resolution within same business day — reship issued, customer notified, root cause flagged. If a customer emails Monday morning, a replacement should be on its way Monday afternoon.
• Pack errors / in-transit damage: 24 hours — refund or reship, customer notified, carrier chargeback filed, packaging process reviewed.
• Lost packages: 48 hours from carrier confirmation — proof of non-delivery, replacement issued, carrier claim filed. The clock doesn't start when the ticket opens; it starts when the carrier confirms the loss.
• Inventory discrepancies / oversells: ideally resolved before the customer notices — flagged by your 3PL's cycle count, you decide the next move. If the customer gets there first, 24 hours to refund, reship a substitute, or set clear expectations.
• Delayed fulfillment: resolved by shipping the order with expedited service and absorbing the upgrade cost, same day it's flagged. If it's already a day late, upgrade is non-negotiable.

A 3PL that treats all of these as "we'll get to it in 2-3 business days" doesn't have resolution speed; they have a queue.

Where does resolution actually slow down?

Three places, in order:

• Handoffs between people. The ticket goes from tier-1 to tier-2, from CSR to the warehouse, from the warehouse to the carrier liaison, from the liaison back to the CSR. Each handoff adds hours. Each one is a place the ticket can sit on someone's desk for a day because they're on PTO.
• Approval chains for refunds and reships. A good 3PL has refund authority baked into the frontline role, up to a reasonable threshold. A bad one requires a manager to approve every reship, which means every reship waits.
• Missing data at the point of decision. The CSR needs to know: what was ordered, what shipped, what the customer paid, whether this customer has a history, what the correct resolution is. If the CSR has to go hunt for any of that, you've added half a day.

A 3PL that's fast on resolution has fixed all three — short handoff paths, pre-authorized decisions at the frontline, and good data at the point of contact.

What should your 3PL do on the customer side while the fix is in flight?

The resolution clock the customer sees isn't the same as the 3PL's internal clock. A good 3PL closes that gap on your behalf:

• The customer gets a clear acknowledgment the problem is being worked, with a realistic timeline (not "we'll look into it")
• Every 24 hours, there's a status update until it's done
• When the resolution is executed (refund, reship, replacement), the customer is told what was done and when they'll see it
• No customer should ever have to email twice to find out what's happening

If your 3PL doesn't manage the customer-side clock, you're doing it yourself. That's a hidden cost you weren't told about on the sales call.

What to ask about resolution speed before you sign

Four questions cut to the signal:

• What's your average resolution time by issue category — pick errors, lost packages, oversells, delays? Not response time. Resolution.
• Who has the authority to issue a reship or a refund at your frontline? If every one requires escalation, you'll know why resolution is slow.
• Walk me through a specific example of a problem you solved recently — who did what, how long did each step take, how did you communicate it. Vague answers mean no measured process.
• When a customer complains to us before you've told us about the issue, how do we both find out at the same time?

A 3PL running a real operation can answer all four with specifics. A 3PL running a queue tells you about response time and changes the subject.

FAQ

What's a reasonable response time for a shipping error? Under two hours during business hours, under 12 hours for errors flagged outside business hours. Response is the easy half. Resolution is the one that matters.

What should a 3PL do when the customer complains before I know? Flag it to you immediately and start working the resolution in parallel. If your 3PL waits for you to open a ticket on an issue the customer already raised, you've lost two hours of resolution time before anyone was even working on it.

Who owns the refund if the 3PL made the mistake? The 3PL. A good one eats the cost of their own errors as part of the service — reship, refund, carrier chargeback, all absorbed by them. If the contract puts those costs on you, you're paying twice for every mistake.

Can I set custom SLAs with my 3PL? Yes, and you should, especially around resolution. Base-level 3PL SLAs are written to protect the 3PL. If you have specific customer promises (same-day shipping cutoffs, hour-specific delivery windows), negotiate the SLAs to match them before you sign, not after you have a problem.

Watching your 3PL's SLA clock run out while your customer's patience does the same? See how ecommerce fulfillment at Ships A Lot works, or tell us how your 3PL handles mistakes and we'll walk through the resolution process with you before you commit to anything.