Solving Delivery Problems

Delivery problems are one of the most common triggers for customer complaints in e-commerce. Whether the recipient was not home, the address is incomplete, or the shipment has been stuck without a status update for days – every disruption in the last mile affects customer satisfaction, return rates, and marketplace ratings. Teams that solve delivery problems systematically, rather than only reacting, reduce support effort and protect delivery reliability as a competitive advantage.

This guide shows how fulfillment teams identify, prioritize, and resolve typical delivery disruptions – from the first tracking exception to final clarification with the carrier and customer.

Why Delivery Problems Are Critical in Fulfillment

Delivery is the last direct touchpoint between brand and customer. A smooth process confirms the purchase decision; a problem immediately creates distrust – regardless of whether the merchant or the carrier is the actual cause.

Typical impacts of unresolved delivery problems:

Increased WISMO inquiries ("Where Is My Order?") in customer service
Negative reviews on marketplaces and social media
Chargebacks and payment disputes for shipments perceived as not delivered
Double shipping costs for replacement deliveries
Strain on the OTIF metric (On Time In Full)

Delivery rate in e-commerce: Typical delivery rate of 95–98% for standard parcel shipping in Germany. Every unresolved exception costs an average of €15–40 including support and reshipment.

The Most Common Delivery Problems at a Glance

Not every tracking delay is a real delivery problem. What matters is whether the shipment jeopardizes the agreed delivery time or whether the customer must take action.

Problem Type

Typical Tracking Signal

Urgency

First Measure

Recipient not available

"Delivery attempt unsuccessful", "Recipient not available"

High – package often only briefly at depot

Inform customer, clarify pickup location or redelivery

Address error

"Address incomplete", "Recipient unknown"

Very high – risk of return to sender

Verify address with customer, contact carrier

Delay without exception event

Last scan exceeds SLA time

Medium to high

Initiate carrier investigation

Package marked delivered, customer denies receipt

"Delivered" with POD, customer reports missing item

Very high – fraud and claims risk

Review proof of delivery, escalate with carrier

Damage upon delivery

No special event, customer report

High

Request photos, start claims process

Return to sender

"Return to sender", "Return initiated"

Critical

Clarify cause, contact customer proactively

Important: Exception events in shipment tracking are early warning systems. Waiting only for "Delivered" means reacting too late. For the basics, see the article on Understanding Tracking Events.

Identifying Delivery Problems: Monitoring and Thresholds

Professional fulfillment does not monitor shipments manually, but rule-based. For this you need clear triggers for when a shipment moves to "delivery problem" status.

Automatic Detection via Tracking Rules

Recommended monitoring rules:

Exception event received – every carrier status from the "exception" category immediately triggers a workflow.
No scan for X days – e.g. more than 48 hours without an update after "Out for delivery".
Delivery window exceeded – promised delivery time per shop or marketplace SLA has passed, status not yet "Delivered".
Delivery attempt without follow-up event – after "Recipient not available" no new scan within 24 hours.

Delivery Problem Detection: Workflow

1

Tracking event incoming

2

Rule engine checks category

3

Exception?

4

Create ticket

5

Notify customer

6

Carrier escalation

Manual Escalation by Customers or Support

Not every problem appears in tracking. Customers often report missing shipments only days after the expected delivery date. Support staff need a standardized review path:

Retrieve tracking number and last event status
Compare delivery address with order data
Request proof of delivery (POD) from carrier if status is "Delivered"
Decision: investigation, redelivery, replacement shipment, or refund

Solving Delivery Problems: Step-by-Step Process

Process Flow: Resolving a Delivery Problem

1

Identify problem

2

Collect data

3

Narrow down cause

4

Contact carrier

5

Inform customer

6

Implement solution

7

Document and evaluate case

Step 1: Secure the Data Situation

Before contacting the carrier or customer, all relevant information must be available:

Tracking number and carrier
Complete recipient address from the order
Timestamps of all tracking events
Package dimensions, weight, and shipping product
Internal order number and marketplace reference if applicable

Step 2: Narrow Down the Cause

The most common causes fall into three categories:

Customer-side factors:

Recipient unavailable or absent
Incorrect or incomplete address entry
Neighbor delivery not accepted or package not collected

Carrier-side factors:

Sorting error or lost shipment in the network
Delay due to capacity bottlenecks (peak season)
Misrouting between parcel hubs

Merchant-side factors:

Wrong label or swapped tracking number
Insufficient packaging with transport damage
Late handover to carrier after cut-off

Address errors are particularly critical because they often lead to automatic return to sender. For preventive measures, see the article Address Errors and Investigation.

Step 3: Carry Out Carrier Escalation Professionally

Carrier investigations only succeed when the request is complete and traceable.

Escalation Level

When to Use

Typical Processing Time

Expected Outcome

Online investigation

No scan for 2–3 business days

1–5 business days

Location clarification or delivery date

Phone escalation

Investigation without result or SLA critical

24–48 hours

Prioritized processing at depot

Damage or loss report

Shipment declared lost

2–6 weeks

Reimbursement per carrier contract

POD request

Customer disputes delivery

1–3 business days

Signature, photo, or drop-off location proof

Details on proof of delivery and its importance in disputes: Proof of Delivery and POD.

Step 4: Customer Communication for Delivery Problems

Transparency defuses frustration. Customers experiencing delivery problems expect not only an apology, but a clear perspective: what happens next, and by when?

Every customer message should include:

Confirmation that the problem is being handled
Current shipment status in plain language (no raw carrier codes)
Concrete action options (book redelivery, pickup, alternative address)
Realistic timeframe for resolution
Direct contact channel for follow-up questions

Warning: Never inform customers with an "in transit" status when tracking already reports an exception. This increases loss of trust and the likelihood of chargebacks.

Detailed strategies for automated and manual customer communication: Customer Notifications.

Decision Matrix: Redelivery, Replacement Shipment, or Refund

Not every delivery problem has the same best solution. The decision depends on shipment value, urgency, and carrier feedback.

Situation

Redelivery

Replacement Shipment

Refund

Unsuccessful delivery attempt, package at depot

Recommended

Not necessary

Only on customer request

Shipment lost (carrier confirmed)

Not possible

If available

Alternative or combined

Damage upon arrival

Not sensible

Standard

For low product value

Package with neighbor, customer cannot find it

After clarification with carrier

After 48h without clarification

Rare

Return to sender already initiated

Not possible

Review after goods receipt

For irreparable loss

Tip: Document every decision with justification in the ticket system. This protects you for marketplace A-to-z guarantees and recurring carrier issues in rate negotiations.

Prevention: Reducing Delivery Problems from the Start

Reactive problem solving is expensive. The highest leverage lies in prevention before and during shipping.

Address Validation Before Shipping

Automatic check of required fields (street, postal code, city, country)
Postal code–city matching via address APIs
Flag uncertain addresses for manual approval
Clarify parcel locker and store addresses before label printing

Choosing the Right Shipping Products

Neighbor delivery only with customer consent
Preferred delivery day and time window for high-value goods
Signature on delivery for suspected fraud or high product value
Pickup at store or parcel locker as active checkout option

Measuring Carrier Performance

Compare 3–4 carriers over 6 months based on delivery rate, average transit time, and exception rate – evaluated separately by region.

KPIs for carrier evaluation:

Delivery rate within the agreed delivery window
Share of exception events per 1,000 shipments
Average investigation duration
Reimbursement rate for loss reports
Customer satisfaction after delivery problems (CSAT)

Checklist: Handling a Delivery Problem

Operational quick checklist for support and fulfillment:

Tracking events fully reviewed (including exception status)
Recipient address compared with order
Customer informed within 4 hours of exception event
Carrier investigation initiated with complete data
Proof of delivery requested if "Delivered" status disputed
Decision documented: redelivery, replacement, or refund
WMS/ERP status updated (partial delivery, cancellation, replacement order)
Claims case created for damage or loss
Carrier performance recorded for monthly reporting
Preventive measure noted for recurring patterns

Escalation with 3PL and Fulfillment Partners

If you outsource fulfillment, you need clear SLA rules for delivery problems. The 3PL partner is often the first point of contact because they manage labels, tracking, and carrier contacts.

You should define contractually:

Maximum response time for delivery exceptions
Responsibility for investigation and carrier communication
Rules for replacement shipment without inquiry up to a defined product value
Reporting obligation for delivery rate and exception rates
Escalation matrix for repeated carrier problems

Claims and Compensation

When a delivery problem can no longer be fixed, the claims phase follows. Here it is important to treat customers fairly while asserting carrier reimbursement claims.

Typical process:

Record customer claim with photos, tracking, and order data
Internal approval based on product value and goodwill policy
Trigger refund or replacement delivery
Submit carrier damage case in parallel
Process return if shipment comes back after all

More on structured handling of customer claims: Claims and Compensation.

FAQ: Frequently Asked Questions About Delivery Problems

What to do when status is "delivered" but not received?

Request proof of delivery (POD) from carrier, ask customer about drop-off location and neighbors, escalate with carrier if proof is missing, and consider replacement shipment per internal goodwill policy.

How long does carrier investigation take?

Online investigations typically take 1–5 business days, loss reports 2–6 weeks. For critical SLAs, plan phone escalation.

Who bears costs for replacement shipment?

For carrier loss or carrier error, usually the merchant upfront, with reimbursement via carrier contract afterward. For customer address errors, cost sharing can be defined contractually.

When is neighbor delivery worthwhile?

With high first-attempt delivery rate and active customer consent. For frequent "package not found" reports, prefer signature on delivery or parcel locker.

How do I document for marketplaces?

Archive tracking history, POD, customer communication, and chosen solution in the ticket system – for A-to-z guarantees and seller performance evidence.