Hold at Location on FedEx: pickup-point delivery as a checkout conversion feature

The door tag that becomes a refund

A buyer in San Francisco places an order on a DTC home-goods brand’s Shopify store. The package ships FedEx Home Delivery. Three days later, FedEx attempts delivery at the buyer’s apartment. The buyer is at work. A door tag appears. The package returns to the local FedEx facility. The buyer either drives across town to pick it up — annoyed — or asks the seller for a refund because they don’t have time to retrieve it. The merchant absorbs the return-to-shipper cost, the customer-acquisition cost, and the negative review.

This is the failure mode that FedEx Hold at Location (HAL) was built to prevent. The mechanics aren’t complicated — show pickup at checkout, let the buyer choose a convenient FedEx Office, FedEx Ship Center, or partner Walgreens location, route the shipment directly there instead of attempting residential delivery. The carrier capability has been on the FedEx Ship API for years. What’s uneven across the eCommerce ecosystem is whether the integration layer actually exposes HAL as an option at checkout.

This article describes what HAL actually does operationally, where the workflow consistently breaks for the buyer segments that would benefit most, and what the integration layer needs to do for pickup-point delivery to function as the conversion feature it should be.

What HAL actually does

FedEx Hold at Location is the carrier-side capability to route a shipment directly to a chosen FedEx retail location rather than attempting residential delivery. The mechanics:

Buyer selects pickup at checkout from a list of FedEx locations near their delivery address
The shipment manifest carries the HAL location ID — the package routes to that location instead of attempting residential delivery
Buyer receives notification when the package arrives at the location
Buyer picks up at their convenience within the holding window (typically 5–7 days)
Failed-delivery retries don’t happen; the package waits for the buyer rather than the buyer waiting for the package

The supported locations include the FedEx Office retail network (the larger FedEx-owned retail network in the US), FedEx Ship Centers (FedEx’s own ground-handling locations open to retail customers), and partner Walgreens locations across the US footprint. The FedEx Office network alone is one of the broadest pickup-point networks in the US — and largely under-exposed in the eCommerce checkout flow across most multi-carrier shipping apps.

Where the workflow actually breaks — three failure patterns from the merchant base

Three patterns show up consistently across DTC merchants whose buyer demographics would benefit from HAL:

1. HAL not exposed at checkout at all. The most common failure. The merchant’s FedEx integration treats every residential address as a residential delivery destination — it shows residential service tiers (Home Delivery, Ground, Express) and ignores HAL entirely. Buyers who would have selected pickup if offered the option get the default residential delivery and then the failed-delivery follow-up. The fix is exposing HAL alongside residential delivery options at checkout, with location lookup driven by the buyer’s address.

2. HAL exposed but with a broken location-lookup experience. Some integrations technically support HAL but require the buyer to manually enter a FedEx location ID or look up locations on fedex.com in a separate tab. The friction kills adoption — buyers who would have chosen HAL with a clean lookup don’t bother with the multi-step version. The right pattern is location lookup driven from the buyer’s address at checkout, showing a small list of nearby locations with addresses and pickup-window info inline.

3. HAL applied without buyer notification configured. A few integrations route shipments to HAL locations correctly but don’t configure FedEx-side notifications to the buyer when the package arrives at the location. The package sits at the location, the buyer doesn’t know it’s there, the holding window expires, and the package returns to the shipper. The buyer experience is worse than residential delivery — the package was at a convenient location the whole time but the buyer never knew. The fix is configuring the FedEx notification flow as part of the HAL workflow setup.

These three patterns explain why HAL adoption stays low even among merchants whose buyer demographics would benefit substantially from offering pickup at checkout.

The workflow that holds up at scale

The workflow that actually works treats HAL as a first-class checkout option for residential destinations where the buyer demographic suggests it would be welcome (apartment density, urban areas, college campus zip codes, addresses with historical failed-delivery patterns). The buyer sees pickup as an option alongside residential delivery, the location lookup runs from their checkout address, and they can pick a convenient FedEx Office or Walgreens with minimal additional friction.

The shipment builder writes the HAL location ID to the FedEx Ship API call. The label routes the package to the chosen location. FedEx notifies the buyer on arrival. The buyer picks up at their convenience within the holding window.

For the merchant, the checkout exposure is one configuration step at the integration level. The integration handles the per-order location selection, the manifest population, and the notification setup. The fulfillment team handles labels the same way they always have.

Where this sits in the broader checkout conversion picture

Pickup-point delivery has been one of the longer-term trends in last-mile eCommerce. UPS Access Point, USPS PO Box services, Amazon Locker, and a growing set of carrier-aggregator pickup networks all operate in adjacent space. FedEx Hold at Location’s network — anchored by the FedEx Office retail footprint plus FedEx Ship Centers and the Walgreens partnership — is one of the broader US pickup-point networks but is among the less-exposed in the typical Shopify or WooCommerce checkout.

The buyer segments where HAL matters most are well-defined. Apartment dwellers in dense urban areas. Office workers who can pick up near work but won’t be home for residential delivery. College students. Buyers in neighborhoods with porch-piracy concerns who prefer a controlled pickup location. For DTC merchants whose customer mix is meaningfully weighted toward those segments, offering HAL at checkout is one of the more direct conversion improvements available.

What makes the integration-layer gap interesting from a partnership perspective: the FedEx retail and partner-location network has been investing in pickup capacity, and the carrier-side Ship API has supported HAL for years. The constraint on adoption is at the integration layer — most multi-carrier shipping apps don’t expose HAL at all, or expose it in ways that produce low buyer adoption. Closing that gap would benefit FedEx (more shipments routed through the retail network), the merchant (lower failed-delivery cost, better conversion among pickup-preferring buyers), and the buyer (a pickup option that fits their schedule).

Pickup-point checkout workflow automation still feels like one of the under-built capability areas across Shopify and WooCommerce shipping infrastructure for residential DTC.

Happy to connect with anyone on the FedEx Retail / FedEx Office channel side exploring pickup-point checkout workflow automation further.

This article reflects patterns observed across PluginHive’s residential DTC merchant base on FedEx. FedEx Hold at Location program specifics, partner location networks, and holding window policies evolve — verify current FedEx Retail and FedEx Office channel documentation before commercial commitments.