Customer Notifications for Pickup Point Deliveries
Clear, timely, and informative communication is critical for a successful pickup point customer experience. Unlike home delivery, customers need specific information to know when, where, and how to collect their order.
Effective notifications serve several important purposes:
- Manage expectations — inform customers about the process and what to expect at each stage.
- Drive action — prompt customers to collect their parcel within the designated timeframe.
- Provide essential details — give customers everything they need for a smooth collection, including location, opening hours, and any collection requirements such as ID or codes.
- Reduce customer support — proactively answer common questions and minimize "Where is my order?" (WISMO) inquiries related to pickup.
- Build trust and confidence — a clear communication flow makes customers feel secure and informed about this delivery method.
- Prevent failed collections — reminders help ensure parcels are collected before the holding period expires, avoiding unnecessary returns.
This guide outlines the key notification touchpoints, required content, and the different approaches to managing these communications.
Notification Responsibility: Carrier vs. Retailer-Managed
A key consideration is who sends pickup-specific notifications to your customers. There are generally two models:
Carrier-Managed Notifications
The shipping carrier automatically sends standard notifications directly to the customer — using contact details such as email or SMS provided in the manifest data — when certain tracking events occur. This typically covers the "Ready for Collection" message and, in some cases, reminders.
Many carriers offer this as a default service, but you should confirm with each carrier whether it is enabled by default, what the notifications include, and whether they can be suppressed if you choose to send your own.
- Pros — requires minimal setup effort from the retailer; leverages the carrier's existing notification infrastructure.
- Cons — less control over branding, messaging content, and timing; notifications use generic carrier templates; may not cover all desired touchpoints such as exception handling.
Retailer-Managed Notifications
The retailer takes full responsibility for triggering and sending all pickup-related notifications using their own communication systems — email marketing platforms, SMS providers, OMS workflow tools, and so on. This requires monitoring carrier tracking events.
- Pros — full control over branding, content, tone of voice, timing, and number of reminders; ability to integrate seamlessly with other brand communications; can include additional content such as upselling or loyalty messaging.
- Cons — requires technical setup to ingest carrier tracking events via API or webhooks and build the logic to trigger specific messages based on those events; requires content creation and ongoing maintenance.
Determining Your Approach
- Check with your carriers — confirm whether each carrier provides customer notifications by default, what those notifications include, and whether they can be suppressed if you choose to send your own.
- Evaluate your needs — decide whether the standard carrier notifications are sufficient or whether you require greater control over branding and content.
- Configure accordingly — if using carrier notifications, ensure they are enabled and that you are passing the necessary customer contact details correctly in your manifest data. If managing your own, ensure carrier notifications are suppressed where possible to avoid duplicate messages, and begin the technical setup for tracking event ingestion and notification triggering.
Key Pickup Notification Touchpoints
Standard order confirmation and shipment confirmation emails remain essential, but several pickup-specific communications are also required:
- "Ready for Collection" notification — (most critical) informs the customer their parcel has arrived at the chosen pickup point and is available for collection.
- Collection reminder(s) — sent if the parcel has not been collected after a set period (e.g., 3 days, 5 days) to prompt the customer before the collection window expires. You may configure one or multiple reminders depending on your carrier's holding period.
- Return initiated (uncollected) — informs the customer the collection window has expired and the parcel is being returned to you. Sets expectations about refunds and next steps.
- Delivery exception — notifies the customer if an unexpected issue occurs, such as a parcel being misrouted, damaged, or a pickup point being temporarily closed. Provides information and directs the customer on next steps.
Essential Content for Each Notification
When crafting retailer-managed notifications — or evaluating carrier-provided ones — ensure each message contains clear and actionable information.
"Ready for Collection"
| Requirement | Detail |
|---|---|
| Clear subject line | e.g., "Your order [Order #] is ready for collection!" |
| Confirmation | State clearly that the order is ready. |
| Who / What | Customer name, order number, retailer name. |
| Where | Full pickup point name and address. A link to a map is optional but recommended. |
| When | Pickup point opening hours. State clearly how many days the customer has to collect (e.g., "Please collect within 7 days"). |
| How (collection requirements) | State exactly what the customer needs to bring. This varies by carrier — for example, some require photo ID, others provide a barcode or QR code via email or SMS. |
| Tracking link | Optional. Link to detailed tracking. |
| Customer service link | Optional. Link to your help or contact page. |
| Branding | Use your brand logos and styling if sending the notification yourself. |
Collection Reminder(s)
| Requirement | Detail |
|---|---|
| Clear subject line | e.g., "Reminder: Collect your order [Order #] soon!" |
| Urgency | Gently remind the customer the collection window is closing (e.g., "Just a reminder your order is waiting for collection until [Date]"). |
| Key info recap | Briefly reiterate: order number, pickup point name and address, opening hours, collection requirements, and collection deadline (e.g., "Collect by end of day on [Date]"). |
| Consequences | Briefly state what happens if the parcel is not collected (e.g., "Uncollected orders will be returned, and a refund processed"). |
| Tracking / support links | Optional. Link to detailed tracking or your customer service page. |
Return Initiated (Uncollected)
| Requirement | Detail |
|---|---|
| Clear subject line | e.g., "Your order [Order #] is being returned" |
| Explanation | State clearly that the order was not collected within the timeframe and is now being returned. |
| Next steps | Explain the process (e.g., "A refund will be automatically processed once the return is received at our warehouse. Please allow X days."). |
| Charges (if applicable) | Clearly state if any return shipping fees will be deducted from the refund, as per your policy. |
| Customer service link | For questions. |
Delivery Exception
| Requirement | Detail |
|---|---|
| Clear subject line | e.g., "Important Update Regarding Your Order [Order #]" |
| Explanation | Clearly and concisely explain the issue (e.g., "There has been a delay delivering your order to the pickup point," "The chosen pickup point is temporarily unavailable," "Your parcel was damaged in transit"). |
| Resolution / next steps | Provide clear instructions on what happens next or what the customer should do. Examples: "We have redirected your parcel to [New Location Name/Address]. You will receive a new 'Ready for Collection' notification soon." / "Please contact our Customer Service team at [Phone/Link] to arrange redelivery or a refund." / "Tracking has been updated with the latest information: [Tracking Link]." |
| Apology | Express apology for the inconvenience. |
| Customer service link | Essential for exception handling. |
Implementing Retailer-Managed Notifications: Using Tracking Events
If you manage your own notifications, you will need to trigger them based on real-time shipment status updates from the carrier.
Step 1: Access Tracking Data
You need a reliable method to receive tracking event updates for your shipments. Common approaches include:
- Carrier tracking APIs — programmatically query the carrier's API for tracking status using your tracking numbers.
- Carrier webhooks — subscribe to the carrier's webhook service, which pushes status updates to your system automatically when events occur. This is generally preferred for real-time updates.
- Third-party tracking platforms — platforms such as AfterShip or ShipStation aggregate tracking data across carriers and may offer webhook or API access.
Step 2: Identify Trigger Events
Work with each carrier's documentation or technical support to identify the specific tracking event codes or status descriptions that correspond to key pickup milestones. The exact codes vary by carrier, but common mappings are:
| Carrier Event | Notification to Trigger |
|---|---|
| "Delivered to Pickup Point" / "Ready for Collection" / "Available for Pickup" | "Ready for Collection" notification |
| "Return to Sender Initiated" (from pickup point after hold time expires) | "Return Initiated (Uncollected)" notification |
| "Exception" / "Alert" / "Delivery Attempt Failed" (if relevant to pickup) | "Delivery Exception" notification (may require internal review before sending) |
Note: Event code naming conventions differ between carriers. Always refer to your carrier's specific API or EDI documentation to confirm the correct event codes for your integration.
Step 3: Implement Reminder Logic
- When the "Ready for Collection" event is received, store the timestamp.
- Set up scheduled tasks (e.g., daily checks) to identify orders that are ready but uncollected for a defined number of days.
- Trigger the "Collection Reminder" notification based on your desired schedule (e.g., after 3 days, then again after 5 days).
- Before sending each reminder, check whether the parcel has already been collected to avoid sending unnecessary messages.
Step 4: Integrate with Your Communication Tools
Connect your tracking event monitoring system to your email service provider (ESP), SMS gateway, or notification platform to send correctly formatted messages to the customer.
Example Notifications
The images below show example notification templates for reference. If sending your own notifications, ensure they align with your brand guidelines and tone of voice.
FAQs
How do I know if my carrier sends notifications automatically?
Contact your carrier account manager or consult the carrier's technical documentation to confirm whether customer notifications are sent by default for pickup point deliveries, what those notifications include, and whether they can be suppressed. Requirements and default behaviors vary between carriers and service types.
Can I use both carrier-managed and retailer-managed notifications?
This is generally not recommended, as it can result in duplicate messages being sent to the customer. If you choose to manage your own notifications, confirm with your carrier whether their default notifications can be suppressed. If suppression is not possible, coordinate the timing and content carefully to avoid confusion.
What customer contact details do I need to pass to the carrier for carrier-managed notifications?
Most carriers require at minimum a customer email address to send notifications. Some also support SMS and require a mobile phone number. These details must be included in your manifest or shipment request data. Refer to your carrier's manifesting documentation for the specific fields and format required.
How long do customers typically have to collect their parcel?
Collection windows vary by carrier and service type. As a general guide, most carriers hold parcels for 7 days, though some offer longer periods. Always confirm the exact holding period with your carrier and communicate it clearly in your "Ready for Collection" notification. The collection deadline should also be reiterated in any reminder messages.
What collection requirements should I communicate to customers?
Collection requirements vary by carrier. Some carriers require the customer to present a photo ID (such as a passport or driving licence). Others provide a barcode or QR code via email or SMS that is scanned at the pickup point. Check with each carrier you use to confirm the exact requirements, and ensure these are clearly stated in your "Ready for Collection" notification.
What happens if a customer does not collect their parcel?
If a parcel is not collected within the carrier's holding period, it will be returned to the sender. You should communicate this clearly in your collection reminder notifications, including the collection deadline and what will happen if the parcel is not collected (e.g., automatic return and refund processing). Your specific refund and returns policy will determine the exact next steps to communicate.
Where can I find carrier-specific tracking event codes?
Tracking event codes are documented in each carrier's API or EDI reference documentation. Contact your carrier account manager or technical support representative for guidance on the specific event codes that correspond to pickup point milestones such as "Ready for Collection" and "Return to Sender Initiated." For carrier-specific documentation available in the HubBox Console, refer to the relevant carrier integration guides.