Last‑Mile Logistics: Boosting Customer Satisfaction

Last-mile logistics is the customer-facing delivery segment in which a parcel moves through the carrier’s local network to the recipient’s selected destination. Customers may experience checkout, fulfillment and delivery as one journey, although different parties control each stage.

Research shows that the last-mile experience influences how customers evaluate online shopping. A correct warehouse operation can still be followed by dissatisfaction if the delivery promise, tracking or exception response is unclear. Improvement therefore means offering a feasible service, recording each custody event and communicating verified information—not promising maximum speed. Vakulenko et al. — Online retail experience and customer satisfaction

What Is Last-Mile Logistics?

Definitions vary with network design. Lim, Jin and Srai connect last-mile logistics with city logistics, home delivery and B2C distribution and show that delivery models have different network configurations. Lim, Jin and Srai — Consumer-driven e-commerce Boysen, Fedtke and Schwerdfeger describe the movement from an urban starting point, such as a local depot, to the customer’s preferred destination through combinations of vehicles, facilities and handover methods. Last-mile delivery concepts

For an e-commerce parcel, separate:

1. Commercial order: The seller establishes the purchase and delivery terms.
2. Warehouse fulfillment: Inventory is picked, checked, packed, labeled and made ready.
3. Carrier handoff and network: Custody transfers and the parcel enters carrier transport.
4. Final delivery: The carrier attempts delivery to the selected destination.

The boundary between line-haul, local distribution and last mile depends on the carrier. Define it through events. A shipping label can exist while the parcel remains in the warehouse. For the preceding stages, see our order fulfillment process guide.

Who Is Responsible for Each Last-Mile Event?

Customer satisfaction is an end-to-end outcome, but control is divided. Connect each stage to an owner and evidence:

1. Order and commercial promise — brand or seller: Approved order, method and terms.
2. Picking, packing and labeling — Memnun Depo: Task records, parcel-content link, label and ready time.
3. Service and collection plan — client and carrier: Service code, booking or collection response.
4. Physical handoff — warehouse–carrier interface: Manifest, loading scan, handover list or agreed proof.
5. First scan, network and delivery — carrier: Original events, times and available POD.
6. Support, claims and return authorization — brand or seller: Case, notification and decision records. Return transport belongs to the carrier; Memnun Depo records return receipt and inspection when contracted.

The contract should identify the system of record and escalation owner. Memnun Depo controls preparation and the physical transfer it performs, not the carrier’s pickup timing, route, first scan or final delivery.

What Is the Difference Between Dispatch and Delivery Promises?

Use separate clocks for ready for dispatch, physical handoff, first carrier acceptance and delivery. At Memnun Depo, a processable order has valid data, available inventory and defined packing and carrier rules. Once it enters the system, the warehouse commitment is to make it ready within 12 hours. Carrier collection timing and final delivery are not part of that promise.

Google Merchant Center’s official model also separates handling time from transit time and treats cutoffs and operating days as configurable inputs. It illustrates why dispatch and delivery estimates should not share one timestamp; it does not define an SLA for Memnun Depo or a carrier. Google Merchant Center — Calculate shipping speeds

The customer promise should follow:

order approval → warehouse preparation → collection → carrier transit → delivery attempt

Memnun Depo stages and transfers the parcel when collection occurs, but the carrier controls whether and when it arrives. There is no public fixed cutoff: schedules and service calendars are client- and carrier-specific. Most importantly:

label created ≠ pickup booked ≠ parcel handed over ≠ first carrier scan ≠ delivered

How Should a Carrier and Service Be Selected?

Select the service—not only the carrier name—against:

• Destination coverage, parcel dimensions, weight and product restrictions
• Delivery method, collection plan and operating calendar
• Tracking events, exception codes and POD availability
• Redelivery, pickup-point, return and claim rules
• Integration readiness, label controls and total cost
• Historical performance for comparable routes and parcel profiles

Segment scorecards by service and region; a national average may hide local differences. Several carriers may add coverage but also multiply mappings, labels, invoices and exception procedures.

Route planning, vehicle allocation and delivery sequencing belong to the carrier. Memnun Depo can apply agreed selection rules and produce the label, but does not optimize the carrier’s route. See our integration capabilities.

How Do Packaging and Labels Affect Delivery?

Packing rules should reflect dimensions, weight, fragility, carrier limits, required protection, documents and multi-parcel relationships. A transport-ready carton need not be repacked if it meets the agreed rules.

Before dispatch, verify that:

1. The current label is on the correct parcel.
2. Recipient, address, carrier and service data are complete.
3. Tracking is linked to the parcel and split-shipment relationships are correct.
4. The barcode is readable and old or canceled labels cannot be used.
5. Actual weight, dimensions and agreed pre-seal evidence are recorded where required.

The GS1 Logistic Label uses an SSCC to identify a logistics unit and connect physical movement with electronic messages. An SSCC is not a carrier tracking number, and not every B2C parcel requires one. GS1 Logistic Label Guideline

Label creation proves only that shipment data were generated—not that handoff occurred.

How Should Address and Contact Data Be Controlled?

Required fields should follow the destination and carrier service. The UPU’s S42 approach defines common address components and country-specific formatting templates. UPU Addressing Solutions and S42

Check country, postal code, locality, administrative area, street, building or unit, recipient, required contact data and carrier field rules. Preserve the original entry and record the source of any material normalization. Validation improves structure; it cannot prove recipient presence or building access.

Addresses and telephone numbers are personal data. Limit transmission and access to the defined process and apply appropriate security and retention controls. Türkiye’s Personal Data Protection Authority requires technical and administrative measures against unlawful processing or access and for safeguarding personal data. KVKK — Data-security obligations

Why Are Carrier Handoff and the First Scan Separate?

Record four distinct events: label created, pickup booked, parcel handed over and first carrier scan. DHL Express documentation illustrates the boundary: creating a shipment or booking collection is not acceptance for carriage; acceptance follows handover or pickup under its terms. Other carriers have their own models. DHL Express MyDHL API

Handoff evidence may be a loading scan, manifest, reconciled handover list, signature or another agreed record. The first scan may occur later at a branch or facility. Measure the gap: the warehouse record shows when custody ended, while the carrier event shows when acceptance was published.

A missing first scan is an investigation trigger, not automatic proof of loss. Check handoff evidence, parcel counts, carrier response and later events.

How Should Tracking, ETAs and Customer Communication Work?

Tracking information normally originates in the carrier’s system. An OMS, WMS, marketplace or customer portal may retrieve and display it, but displaying a carrier event is not the same as creating or controlling that event.

A status dictionary should preserve the distinction between:

• Label created
• Ready for dispatch
• Handed over to carrier
• Accepted by carrier
• In transit
• At a delivery facility
• Out for delivery
• Delivered
• Delivery exception
• Returning to sender
• Returned

Carrier codes should be stored in their original form and mapped to customer-friendly text separately. The record should retain both the carrier event time and the time the connected system received it. This makes it possible to distinguish a transport delay from an API, webhook or polling delay.

An ETA is an estimate based on the information and model available at a particular time. It should be displayed with its source and last-update time and should not be rewritten as a guarantee. Carrier APIs also differ by product and region. For example, DHL’s official tracking documentation shows that status history, estimated dates or time windows and delivery details vary by API, service and access right. DHL Parcel DE Shipment Tracking API

Customer notifications should be triggered by verified events and contain an appropriate next action:

• Carrier accepted: Tracking is active.
• Out for delivery: Follow the carrier’s supported delivery options.
• Exception: Explain the known reason without inventing a cause and identify the next step.
• Delivered: Report the carrier outcome and provide a support path.
• Returning: Explain why the forward-delivery flow has ended and what happens next.

Research on unattended home delivery shows that delivery experience is multidimensional rather than reducible to speed alone. Customer perceptions can involve cognitive, emotional, behavioral, physical and social responses. Olsson, Hellström and Vakulenko — Customer experience dimensions in last-mile delivery

Memnun Depo does not guarantee real-time carrier updates, ETA accuracy, route visibility or POD availability. Where a carrier integration exists, the system can forward the data supplied by that carrier under the applicable technical and service conditions. For event mapping, retries and reconciliation controls, see our e-commerce integration guide.

Which Delivery Options Should Be Offered?

A delivery option is useful only if the selected carrier service can execute it and the connected systems can transmit it correctly. Possible models include:

• Attended home or workplace delivery
• A carrier-defined delivery time window
• Unattended delivery under the required permission and access rules
• Pickup from a carrier branch or service point
• Parcel-locker delivery
• Delivery to an authorized alternate recipient or location
• A supported rescheduling or redirection option after dispatch

Last-mile research covers many combinations of vehicles, facilities and handover methods; none is automatically best for every destination or customer. Boysen, Fedtke and Schwerdfeger — Last-mile delivery concepts

Out-of-home delivery can consolidate parcels at pickup points or lockers, but its performance depends on network density, location, capacity, customer acceptance, travel behavior and routing. A recent review emphasizes that out-of-home delivery is a family of network-design and operating decisions rather than one uniform solution. Janinhoff et al. — Out-of-home delivery in last-mile logistics

Research on mobile parcel lockers likewise models recipient travel distance and home availability when comparing mixed delivery networks. This illustrates why a locker should not be described as universally cheaper, faster or lower-emission without scenario-specific evidence. Peppel, Spinler and Winkenbach — Integrating mobile parcel lockers

Before offering an option, define:

• Eligible destinations, products and parcel sizes
• Carrier service code and label requirements
• Capacity or availability checks
• Price and commercial terms
• Identity, access and notification requirements
• Holding period and uncollected-parcel rule
• Redirection and exception behavior
• Which party answers the customer if the option fails

Memnun Depo should not be presented as operating lockers, delivery vehicles or scheduled delivery routes unless that service is expressly included in the client-specific arrangement.

How Should Failed Deliveries and Exceptions Be Managed?

A failed delivery attempt is an operational event, not a complete root cause. The initial carrier status should be retained, then mapped into a controlled reason taxonomy.

Possible cause groups include:

• Order or address data: Missing unit details, incorrect postal information or an unusable contact field
• Recipient or destination: Recipient unavailable, access restricted, refusal or pickup not completed
• Warehouse preparation: Wrong label, unreadable barcode, damaged packaging before handoff or incorrect service assignment
• Handoff boundary: Parcel shown as ready but not transferred, count mismatch or missing first scan
• Carrier network: Capacity issue, misrouting, network delay, vehicle problem or unsuccessful attempt
• External condition: Weather, security, regulatory restriction or another event outside normal control
• Unknown: Evidence is not yet sufficient; investigation remains open

For every exception, record:

• Parcel and tracking identifiers
• Original carrier code and description
• Event time and system-receipt time
• Current owner
• Customer impact
• Next action and due point
• Communication sent
• Resolution status and final cause

Research on attended home delivery under uncertain customer availability demonstrates that delivery-attempt planning involves a trade-off between customer availability, repeated visits and route cost. The findings apply to the studied model and data; they do not establish a universal failure rate or a single best redelivery policy. Özarık et al. — Last-mile deliveries under stochastic customer availability

The next step after an unsuccessful attempt depends on the carrier service: another attempt, recipient contact, delivery to a pickup point, address clarification, return to sender or another defined action. Customer communication should reflect the carrier’s actual response rather than promising a redelivery that has not been scheduled.

Exception statuses must not be overwritten merely to make a dashboard appear complete. Resolution means that the parcel has reached a supported outcome and that the reason and owner are recorded.

How Should Loss, Damage, POD and Claims Be Managed?

Loss, damage and delivery disputes require different evidence:

• Possible loss: The parcel has no expected movement or cannot be located after investigation.
• Visible damage: The parcel or contents show physical damage at a documented stage.
• Delivered-but-not-received dispute: The carrier reports delivery, but the recipient disputes receipt.
• Wrong or incomplete contents: The parcel arrived, but its contents do not match the order.
• POD dispute: The available proof does not resolve who received the parcel or where it was left.

The evidence pack may include:

• Order, shipment, parcel and tracking identifiers
• Item and quantity records
• Label version
• Parcel weight and dimensions
• Packing or pre-seal evidence where agreed
• Handoff manifest or loading record
• Full carrier event history
• Available proof of delivery
• Customer statement and photographs
• Support correspondence
• Dates relevant to the carrier’s claim procedure

POD can mean a signature, recipient name, location, photograph or another service-specific record. A “delivered” status does not prove that every type of POD exists. The DHL Express MyDHL API, for example, includes an electronic POD operation, but availability and content remain specific to that carrier product and access arrangement. DHL Express MyDHL API

Claim deadlines, evidence, compensation limits and liability rules come from the applicable carrier contract and law. They should be recorded in the service matrix rather than assumed. Memnun Depo can provide warehouse preparation and handoff evidence within its scope; it cannot guarantee the carrier’s claim decision or compensation.

Root cause and financial recovery should remain separate. A claim may be rejected even when an operational problem occurred, and an accepted claim does not by itself prove which preventive action is needed.

Where Does Last-Mile Delivery End and Returns Begin?

An unsuccessful forward-delivery parcel may enter a return-to-sender flow under the carrier’s rules. A customer may also request a return after successful delivery. Both move goods backward, but they begin with different events and may follow different commercial decisions.

A controlled reverse flow separates:

1. Return request or carrier return event
2. Authorization by the brand, seller or sales channel
3. Return transport and tracking
4. Physical receipt at the warehouse
5. Match to the original order and item
6. Quarantine and inspection
7. Condition finding
8. Brand-approved disposition
9. Inventory and financial updates

The warehouse’s receipt of a returned parcel is not automatically approval of a refund. Memnun Depo can receive, match, inspect and process a return according to agreed operating rules, while the brand or authorized sales channel retains the commercial decision unless the contract expressly states otherwise.

Return pickup, reverse transport and carrier events remain carrier activities. For receiving, inspection, quarantine, disposition and reconciliation controls, see our reverse logistics and returns management guide.

How Should Cost, Speed and Environmental Impact Be Balanced?

Last-mile decisions should compare the complete service design, not one headline rate. Relevant cost components may include:

• Warehouse preparation and packaging
• Label and integration transactions
• Carrier pickup and transport charge
• Fuel, remote-area, dimensional or peak surcharges
• Failed delivery and redelivery
• Pickup-point or locker fees
• Return-to-sender and customer returns
• Support and exception handling
• Loss, damage and claim administration

Speed should also be separated into warehouse preparation, time waiting for collection, carrier transit and time to successful delivery. Accelerating one segment may not improve the end-to-end result if another segment becomes the constraint.

Environmental comparisons require the same discipline. Home delivery, pickup points and lockers can produce different carrier routes, consolidation levels and customer trips. The outcome depends on parcel density, vehicle type, failed attempts, distance to the collection point and how the customer travels. An out-of-home option should not be labeled “green” solely because several parcels share one stop.

ISO 14083:2023 establishes a common methodology for quantifying and reporting greenhouse-gas emissions from passenger and freight transport-chain operations. It can provide a consistent accounting boundary, but citing the standard does not mean that Memnun Depo or a carrier has completed an ISO 14083 assessment. ISO 14083:2023

A practical comparison should state:

• Transport-chain boundary
• Included and excluded activities
• Shipment-allocation method
• Primary and estimated data
• Vehicle and energy assumptions
• Failed attempts and returns
• Customer travel where relevant
• Reporting period and uncertainty

There is no universal last-mile cost share, ideal delivery speed or emissions-saving percentage that applies to every operation. For the wider warehouse, packaging, transport and returns context, see our sustainable fulfillment guide.

Which Last-Mile KPIs Should Be Measured?

Every KPI needs a start event, end event, denominator, exclusions, time zone, owner and source system. Start with:

• Warehouse: Ready within 12 hours; right-first-time parcel preparation; parcels ready before the client-specific planned collection.
• Handoff boundary: Handoffs with required evidence; time from physical handoff to first carrier scan; handed-over parcels still awaiting that scan, grouped by age.
• Carrier: Collection adherence; on-time delivery against the defined promise; first-attempt success; exception rate by original carrier reason.
• Integration: Time between carrier event occurrence and visibility in the connected customer system.
• Claims and customer experience: Loss or damage reports, submitted versus accepted claims, resolution time and delivery-related customer contacts.

For example, ready within 12 hours is processable orders made ready within 12 hours divided by all processable orders in the cohort. First-attempt success is parcels delivered on the first recorded carrier attempt divided by parcels with at least one recorded attempt. Reported loss or damage and accepted claims must remain separate measures.

The original customer promise should be preserved. If the carrier later revises an ETA, performance against the original promise and communication of the revised estimate are different measurements.

Averages alone can hide a small group of severely delayed parcels. Report distributions, percentiles, oldest open cases and cause groups where useful. Compare like with like by carrier, service, destination, parcel profile and period.

No universal target should be copied from another business without validating the order profile, carrier contract and data definitions.

How Should Data Be Reconciled and Root Causes Found?

Last-mile visibility depends on joining several identifiers correctly:

customer order → fulfillment order → shipment → parcel → label version → tracking number → carrier event → delivery or return record

One order may contain several parcels, and one parcel may have more than one label record if a label was canceled and replaced. Historical identifiers should remain traceable instead of being overwritten.

A reliable event record should retain:

• Source system and original event code
• Order, parcel and tracking identifiers
• Event occurrence time and time zone
• System-ingestion time
• Raw carrier payload or retrievable reference where appropriate
• Mapped business status
• Mapping version
• Manual intervention, user and reason
• Notification triggered from the event

Event-driven updates should be supported by scheduled reconciliation. Common mismatch checks include:

• Label created, but no ready-for-dispatch record
• Ready parcel, but no physical handoff
• Handoff recorded, but no first carrier scan
• Carrier scan received, but not written back to the sales channel
• Carrier reports delivered, while the OMS remains in transit
• Exception exists, but no owner or customer communication is recorded
• Return tracking exists, but no expected-return record was created
• Returned parcel received, but not matched to an order or client

Root causes should be grouped by the stage that created them:

• Sales channel or customer data
• Integration or status mapping
• Inventory or warehouse operation
• Label and parcel association
• Handoff boundary
• Carrier collection or network
• Recipient or destination
• External condition
• Unknown pending investigation

The corrective action must address the cause, not just close the case. Examples include a new address rule, service-mapping correction, label-control change, manifest reconciliation, carrier escalation or revised customer instruction.

Access to address, contact and POD data should follow role-based controls and the applicable data-security policy. For integration architecture, idempotency, retries and audit trails, see our e-commerce integration guide.

What Does Memnun Depo Control in the Last-Mile Flow?

Memnun Depo’s verified operating boundary can be stated as follows:

• A processable order has valid order data, available inventory and defined packing and carrier rules.
• Once that order enters the system, Memnun Depo picks, checks, packs where required, labels and makes it ready for dispatch within 12 hours.
• A transport-ready boxed product can be labeled and prepared without unnecessary repacking when it meets the agreed rules.
• The parcel, order, carrier label and tracking identifier are linked in the warehouse record.
• Parcels are staged according to the agreed carrier flow.
• When the carrier collection occurs, Memnun Depo controls the correct physical transfer at the warehouse interface and records the agreed handoff evidence.
• Domestic fulfillment and shipping workflows are supported across Türkiye.
• Returns received at the warehouse can be processed under the client’s agreed authorization, inspection and disposition rules.

The following are outside Memnun Depo’s performance promise:

• Whether and exactly when the carrier arrives for pickup
• The carrier’s vehicle, route and delivery sequence
• The time or location of the first carrier acceptance scan
• Carrier-network transit and delays
• Real-time tracking-event availability
• ETA accuracy
• Out-for-delivery timing
• Successful final delivery
• The content or availability of POD
• Redelivery, pickup-point and return-to-sender decisions made under the carrier service
• Carrier claim approval or compensation

Memnun Depo does not publish a generic fixed order or carrier cutoff through this article. Any cutoff, collection calendar or service window must be defined for the specific client and carrier arrangement.

Most importantly:

label creation ≠ physical handoff ≠ first carrier scan

The 12-hour commitment concerns warehouse preparation of a processable order and readiness for dispatch. It is not a 12-hour carrier pickup, transit or final-delivery guarantee.

You can review the current fulfillment services, explore integration capabilities or contact us to define a workflow and responsibility matrix for your operation.

Frequently Asked Questions About Last-Mile Logistics

Does last-mile delivery begin when a shipping label is printed?

No. Printing a label creates shipment data. The operational last mile begins according to the carrier-network boundary defined for the service, and physical carrier custody begins only when the parcel is handed over and accepted.

Does “ready within 12 hours” mean delivery to the customer within 12 hours?

No. It means that a processable order is picked, checked, packed where required, labeled and made ready for dispatch within the warehouse. Carrier collection and final delivery are separate processes.

Does a pickup booking prove that the carrier has the parcel?

No. A booking is a request or plan. Physical handoff and the carrier’s first acceptance scan are separate events requiring their own evidence.

Who controls the delivery ETA?

The carrier produces the carrier-network ETA under its service and data model. Connected systems may display that estimate, but Memnun Depo does not guarantee its accuracy or treat it as a fixed delivery promise.

Can Memnun Depo guarantee real-time tracking?

No. Tracking frequency and availability depend on carrier events, APIs and connected-system processing. Event time and system-receipt time should be measured separately.

Can a validated address still result in failed delivery?

Yes. Validation can improve address structure and carrier compatibility, but it cannot guarantee recipient availability, building access or successful carrier execution.

Are parcel lockers always cheaper or more sustainable than home delivery?

No. The outcome depends on network design, locker location and capacity, carrier routing, parcel density and customer travel. Each scenario needs its own cost and emissions analysis.

Who handles an unsuccessful delivery attempt?

The carrier executes the action permitted by its service, such as another attempt, pickup-point delivery or return to sender. The brand or seller normally coordinates customer support. Memnun Depo can provide warehouse and handoff evidence for the investigation.

Is a delivered status the same as signed proof of delivery?

No. POD content varies by carrier and service. A delivered event may or may not include a signature, name, photograph or location record.

Is a return-to-sender parcel the same as a customer return?

No. Return to sender follows an unsuccessful forward-delivery flow. A customer return normally begins with a separate request or authorization after delivery. Both should have distinct statuses and evidence.

What is the most important last-mile KPI?

There is no single universal KPI. Warehouse readiness, handoff evidence, first-scan gap, on-time delivery, first-attempt success, exceptions, tracking latency and customer contacts answer different questions and should be measured together.

Sources and Further Reading

• Lim, S. F. W. T., Jin, X. and Srai, J. S. (2018). Consumer-driven e-commerce: A literature review, design framework, and research agenda on last-mile logistics models.
• Boysen, N., Fedtke, S. and Schwerdfeger, S. (2021). Last-mile delivery concepts: A survey from an operational research perspective.
• Vakulenko, Y., Shams, P., Hellström, D. and Hjort, K. (2019). Online retail experience and customer satisfaction: The mediating role of last mile delivery.
• Olsson, J., Hellström, D. and Vakulenko, Y. (2023). Customer experience dimensions in last-mile delivery: An empirical study on unattended home delivery.
• Universal Postal Union. Addressing Solutions and the S42 international addressing standard.
• Google Merchant Center. Calculate shipping speeds.
• GS1. GS1 Logistic Label Guideline.
• DHL Express. MyDHL API official documentation.
• DHL. DHL Parcel DE Shipment Tracking API official documentation.
• Janinhoff, L., Klein, R., Sailer, D. and Schoppa, J. M. (2024). Out-of-home delivery in last-mile logistics: A review.
• Peppel, M., Spinler, S. and Winkenbach, M. (2024). Integrating mobile parcel lockers into last-mile delivery networks: An operational design for home delivery, stationary, and mobile parcel lockers.
• Özarık, S. S., Lurkin, V., Veelenturf, L. P., Van Woensel, T. and Laporte, G. (2023). An Adaptive Large Neighborhood Search heuristic for last-mile deliveries under stochastic customer availability and multiple visits.
• International Organization for Standardization. ISO 14083:2023 — Quantification and reporting of greenhouse-gas emissions arising from transport-chain operations.
• Personal Data Protection Authority of Türkiye. Data-security obligations under the Personal Data Protection Law.

This article provides general information on operations and process design. Carrier services, APIs, legal requirements and contractual responsibilities may change, so each implementation should be validated against current carrier documentation, applicable law and the client-specific agreement.