The value of a delivery notification is reduced uncertainty. Confirmed, dispatched, out for delivery, delayed, and delivered states change what a customer should do. A store or logistics system can send a stable shipment event to Bartago, which can trigger concise SMS or email, a secure tracking link, and an exception workflow. Events may arrive late, duplicated, or out of order, so a state machine and authoritative timestamps are essential.
Define the shipment event schema
Stable ID, state, and event time
Keep the shipment or order reference opaque. Send state, occurrence time, expected window, and a safe tracking URL server to server. Mask phone and address values in webhook logs.
Message only when the customer can act
Not every scan deserves a notification
An out-for-delivery message can request availability or provide a safe instruction; an internal hub scan usually cannot. For a delay, provide an honest new window and support path.
- Authoritative state
- Out-of-order guard
- Secure tracking URL
- Quiet-hours policy
- Exception escalation
Stop after final delivery
Final state and feedback
A delivered event should cancel pending updates. Keep proof or sensitive detail away from a public URL. Send brief feedback later when useful and keep any marketing offer under separate consent.
Practical checklist
- Stable shipment ID
- Event ordering
- Message-worthy states
- Secure URL
- Support fallback
- Final-state stop
Key takeaway
Delivery automation is not more notifications; it is the necessary notification from an authoritative state.
Final thoughts
Send duplicate and out-of-order events for a test shipment. Confirm the customer never receives an older state and that final delivery cancels pending jobs.
Verify consent, provider or carrier policy, and current applicable requirements before launching a campaign.
Start with 100 free automation credits →Common questions
Should every tracking event send an SMS?
No. Notify when the state changes customer action or expectation.
How should out-of-order events be handled?
Use occurrence time and allowed state transitions to ignore a stale update.
Sources and editorial note
Last editorial review: August 1, 2026. Product behavior may change with releases; check current documentation.