Notification Triggers

TrackLogy fires notifications based on trigger events — named events that correspond to shipment status transitions. You can enable or disable each trigger independently for email and SMS.

All Triggers

`shipment.created`

Fires when: A new shipment is registered in TrackLogy (manually or via API).

Use this for: Letting customers know their order has been shipped and providing the tracking number upfront.

Default: Enabled for email, disabled for SMS.

`shipment.in_transit`

Fires when: The carrier has picked up the package and it is moving through the network.

Mapped from statuses: pre_transit, in_transit, info_received, available_for_pickup

Use this for: Reassuring customers their package is on the way after it leaves the warehouse.

Default: Enabled for email, disabled for SMS.

`shipment.out_for_delivery`

Fires when: The package is on the delivery vehicle and scheduled for delivery today.

Mapped from statuses: out_for_delivery

Use this for: Alerting customers to be home or available to receive their package.

Default: Enabled for email, disabled for SMS.

`shipment.delivered`

Fires when: The carrier confirms the package has been delivered.

Mapped from statuses: delivered

Use this for: Confirming delivery, encouraging reviews, or upselling follow-up products.

Default: Enabled for email, disabled for SMS.

`shipment.exception`

Fires when: A delivery issue is detected — failed delivery attempt, wrong address, customs hold, etc.

Mapped from statuses: exception, failure, failed, on_hold

Use this for: Proactively informing customers of delivery problems so they can take action before contacting support.

Default: Enabled for email, disabled for SMS.

`shipment.returned`

Fires when: The package is being returned to the sender.

Mapped from statuses: return_to_sender, returned

Use this for: Notifying customers that their package could not be delivered and is returning.

Default: Enabled for email, disabled for SMS.

Configuring Triggers

Via the Dashboard

Go to Dashboard → Notifications. Each trigger is shown with toggle switches for Email and SMS channels.

Via the API

# Get current settings
curl https://api.tracklogy.com/v1/notifications/settings \
  -H "Authorization: Bearer YOUR_API_KEY"
 
# Update settings
curl -X PUT https://api.tracklogy.com/v1/notifications/settings \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "channels": {
      "email": true,
      "sms": true
    },
    "triggers": {
      "shipment.created":          { "email": true,  "sms": false },
      "shipment.in_transit":       { "email": true,  "sms": true  },
      "shipment.out_for_delivery": { "email": true,  "sms": true  },
      "shipment.delivered":        { "email": true,  "sms": true  },
      "shipment.exception":        { "email": true,  "sms": true  },
      "shipment.returned":         { "email": true,  "sms": false }
    }
  }'

The channels object is a master switch. If email: false, no emails will be sent regardless of individual trigger settings. Use it to temporarily pause all notifications for a channel.

Settings Scope

Trigger settings are scoped to your workspace (owner account). They apply to all stores in your workspace except for:

WooCommerce stores (always excluded from TrackLogy notifications)
Stores that have specific statuses disabled in their own email settings

SMS Notifications Overview