JournalGuide
Guide / RC JOURNAL

How should a small online shop handle a delayed order?

Give late orders an owner, a clear customer update, and a resolution path that matches the order record.

Illustration of a packed parcel and dispatch note, with a dotted route through a delivery truck to a home

A customer ordered a gift from your shop. The delivery date has passed. Your checkout says the order was fulfilled, but the tracking link shows no recent movement. What should your website and your team do now?

Treat a late order as an open customer issue, not a completed checkout. Identify which stage is late, send a useful update before the customer has to chase you, give them a way to reach a person, and record the next action until the order is delivered or otherwise resolved. An automated tracking email can help, but it cannot decide what your shop owes the customer.

The problem is common enough to deserve a process. In Statistics Canada’s 2018 Canadian Internet Use Survey analysis, 37.7% of Canadian online shoppers reported delivery that was slower than indicated after completing an online order. The survey covered people aged 15 and older in the provinces. It is an older, national, self-reported measure across many sellers and kinds of orders; it does not measure your shop’s performance or prove that a particular message will prevent complaints.

Find out which promise is at risk

Start with the order as the customer saw it: product, selected delivery method, address, estimated arrival or pickup date, and the confirmation message. Compare that record with the actual state of the item. Is it waiting for stock, being packed, labelled but not handed to the carrier, in transit, at a pickup point, or apparently delivered? Each state calls for a different response.

Do not let a “fulfilled” flag on the commerce platform stand in for evidence that the parcel arrived. Check what that flag means in your own system: it may record a shop action rather than delivery to the customer. Your customer-facing status should use words that match the event you can verify. “We created a shipping label” is different from “the carrier has the parcel.”

If you use Canada Post, its delivery-standard guidance defines transit from deposit with the carrier, subject to cut-off times and business days. It is not a measure of the time your shop needs to prepare the order, and most standards are estimates. Add your own processing time when judging whether the customer-facing estimate was realistic. For a pickup order, check the shop’s readiness message and pickup hours instead of looking for a carrier scan.

Make one person responsible for the next update

Choose a simple trigger: the promised date has passed, the shop knows it cannot meet it, or a carrier exception appears. The team member who sees the trigger should assign the order to a named owner and set a follow-up point in the order system. A shared inbox is fine if the task has a clear owner. A status page with no one watching it is not a response plan.

The owner should check the stock and packing record, carrier tracking, and any message already sent. Canada Post’s tracking documentation describes exception updates for interruptions such as address or transportation problems. These events are useful evidence, but they do not explain every delay. Its tracking help also notes that a parcel may have no new public scan for several days. Avoid telling a customer that an unscanned parcel is lost, or that it is definitely moving, until you have checked.

If the expected date has passed and tracking gives no answer, use the carrier’s investigation route when appropriate. Keep the customer informed about what you have actually done. The merchant should still handle the customer’s order question; sending only a tracking link makes the buyer do the shop’s support work.

Write the update the customer needs

A useful delay message identifies the order, the last confirmed event, what is uncertain, what the shop is doing next, and how the customer can reply. For example:

Your parcel has not arrived by the estimate shown at checkout. Our record shows that it was handed to the carrier, but the latest tracking update does not confirm a delivery date. We are checking the shipment and will contact you again when we have a verified update. Please reply to this message if the address has changed or the order is time-sensitive.

That is an illustrative template, not a script to send unchanged. If the item is still on your shelf, say so and explain the next step your team can actually take. If you have a reliable revised date, state whether it is an estimate or a commitment. If you do not, do not invent one to make the message sound reassuring. Give the customer a monitored reply path and make sure someone can see it outside ordinary shop hours if that is what your public support promise implies.

Keep the wording consistent across email, text, account page, and staff replies. A message saying “on its way” while the account page says “delivered” creates a new problem. Use plain status labels, not internal codes. If a system sends automatic delivery notifications, decide who can correct them and how a human will follow up when the event is wrong.

Give the customer a real resolution path

The right outcome depends on the facts and the terms of the sale. A delayed gift, an unavailable replacement, and a parcel marked delivered but not received are different cases. Let the customer know whom to contact, what information to provide, what your shop will investigate, and when the next update will come. Do not promise a refund, replacement, or carrier claim before checking the order and the applicable rules.

For Québec consumer sales, the Office de la protection du consommateur explains that late delivery and missing parcels can give buyers recourse, and that the merchant has responsibilities when delivery was part of the contract. The available remedy depends on the transaction and circumstances. Have the owner or an appropriate adviser review the shop’s policy and specific cases; a carrier delay does not automatically end the merchant’s role.

If the business serves customers in French and English, check both versions of the delay message and support route. A French checkout followed by an English-only exception notice can leave the buyer unsure what to do. The operational facts should be the same in each language, with a fluent person reviewing any policy or remedy wording.

Test the process with an order already on the books

Pick a recent order and reconstruct the path without exposing customer details in a test environment. Can a staff member find the promise that was displayed, the current stock or shipment state, the last customer message, and the person responsible for the next action? Can a customer open the tracking link on a phone and reply without hunting for a support address? Does the order record change when the issue is resolved?

Begin with a manual checklist if volume is low. Add automated alerts only when the team agrees what each event means, who reviews exceptions, and what must wait for human judgement. Measure your own late-order cases and response times before buying a new support system; a faster automatic email is not the same as a resolved order. Our checkout testing guide covers the order handoff before launch, while the delivery and returns guide covers what shoppers need to see before committing.

When the order page, notifications and staff workflow disagree, a website partner can help map the states and test the customer path. Discuss a clearer website with Red Comet; the shop remains responsible for its fulfilment promises and customer decisions.

Sources

WHAT COMES NEXT

Have a project in mind?

Explore what we make and how we can help shape your next idea.

Explore our services