Not Every Tracking Update Should Send a Customer Notification

A customer receives several “delivered” messages for one package. The operations team sees repeated updates and proposes discarding every payload with the same status.

That can solve the noise while losing useful information.

FedEx's webhook guide explains that multiple payloads can share a tracking milestone while adding information such as delivery predictions, recipient details, or proof of delivery. A payload should not automatically be treated as a new milestone. FedEx webhook developer guide.

Separate updating the record from notifying the customer

We recommend two explicit decisions. First, determine what information the shipment record should incorporate. Then decide whether the change warrants a customer-facing notification.

Those decisions have different business purposes. The internal record may need a newly available document even when there is no reason to repeat the same delivery message.

Define notification rules around meaningful changes, audience, channel, and any required review. Do not assume a provider's milestone names match the wording your customer needs.

Use a small event test set

Before launch, ask your team to demonstrate:

1. A genuine progression to a new milestone.
2. An unchanged milestone with new supporting information.
3. A repeated delivery of information already handled.
4. A correction or update arriving after another message.

Provider-specific rules must determine how updates are interpreted. Do not rely on arrival order alone unless the provider documents that guarantee.

In each test, inspect both the shipment record and the outbound communication. A quiet inbox does not prove that the underlying record is complete.

Measure the two outcomes separately

Track unnecessary notifications and missing shipment information as separate issues. Assign a review process for failed updates and explain data freshness in the customer portal.

The aim is an accurate record and useful communication, rather than an alert for every technical delivery. Explore shipping integrations or review your update flow with Blinkshift.