Customize Branded Notification Flows

Customize Branded Notification Flows

Premium Tracking notifications are powered by AfterShip and allow you to customize shipment communications using structured Notification Flows.

Notification Flows organize tracking statuses, apply logic conditions, and control when and how customers receive shipping updates.

This guide covers:

• How to navigate to Notification Flows

• Creating a new flow

• Saving existing notifications as templates

• Editing flow content and logic

• Trigger configuration

• Optional enhancements

• Best practices

• Save and enable requirements

• System behavior and boundaries

Follow the guide below or watch this informative video on how to brand notifications.

What Are Notification Flows?

Notification Flows are shipment-level communication automations triggered by carrier tracking updates.

Flows allow you to:

• Group multiple tracking statuses into a structured workflow

• Add logic splits (carrier, engagement, random)

• Apply time delays

• Send Email, SMS, Internal Email, or Internal SMS

• Control re-trigger frequency

Flows execute per shipment, not per order.

How to Access Notification Flows

There are two ways to access ACP Premium Tracking.

Both are located under the Shipments tile.

Option 1

1. Click Shipments

2. Select Shipment History

3. Click the Premium Tracking button (top left)

4. Navigate to Notifications → Flows

Option 2

1. Click Shipments

2. Select Tracking Events

3. Navigate to Notifications → Flows

Do not remove webhooks unless directed by Wineshipping.

Creating a New Flow

1. Navigate to Notifications → Flows

2. Click Create Flow (top right)

3. Select the tracking status (example: In Transit, Delivered)

4. Configure trigger logic

5. Add actions (Email, SMS, etc.)

6. Save

7. Enable

A flow must be Saved and Enabled to activate.

Using Saved Templates (Optional but Recommended)

If you previously customized a notification:

1. Open the existing notification

2. Save the email as a Template

3. Create a new Flow

4. Attach the saved Template to the flow

5. Disable or delete the old notification

This method allows faster flow creation and prevents duplicate messaging.

Most brands have already transitioned to flows, so this step is typically only needed when upgrading legacy notifications.

Editing Flow Content

Each Email action contains:

• Email Name (internal reference)

• Subject Line

• Sender Information

• Reply-To Email

• Branding toggle

• Email body editor (Drag-and-Drop recommended)

Three editing methods:

• Easy Editor

• Drag-and-Drop Editor (recommended)

• HTML Editor

Templates must be saved before attaching to flows.

Understanding Triggers and Logic

Flows execute based on carrier tracking updates.

Trigger Types - Logic

• Trigger Split

  

  • Splits the flow based on shipment data.

    • Example:
      Custom field → dc_carrier is any of:

      • TMC-GRND

      • TMX-GRND

      • TMX-HOME

  • Exact value matching is required.

  • Even an invisible space will prevent the flow from triggering.

• Conditional Split

  • Splits based on customer behavior.

    • Example:
      Interacted with email → Did not click

  • Often used to trigger follow-up SMS.

• Random Split

  • Used for marketing testing or experimental messaging.

• How Trigger Split Paths Work

  • After creating a Trigger Split, the flow will divide into two paths:

    • Yes → Shipments that meet the trigger condition
      Example: Temperature Control carrier codes (TMC-GRND, TMX-GRND, etc.)

    • No → Shipments that do not meet the trigger condition
      Example: All other carrier services

    Both paths must contain an action in order for communication to send.

Timing Controls

• Time Delay

  • Delays sending actions to avoid simultaneous notifications.
    Common setting: 20 minutes.

• Trigger Status Unchanged

  • Prevents re-trigger if status updates repeatedly within a short window.

• Trigger Frequency

  • Determines how often a shipment may re-enter the flow.

  • Recommended:
    Shipments can re-trigger after 1 day.

  • If disabled, shipments will not re-trigger.

Optional Enhancements

SMS Notifications

• May incur additional charges

• Messages longer than 160 characters may split

• Should be reviewed for compliance and clarity

Internal Notifications

• Send Internal Email

• Send Internal SMS (contact service@wineshipping.com before enabling)

Internal notifications trigger per shipment.

Best Practices

We recommend:

• Including 21+ signature requirement language

• Explaining the unsubscribe impact clearly

• Including redirect tracking links

• Clarifying shipping method (Temperature Control, Ice Packs, etc.)

• Disabling legacy notifications before enabling new flows

• Pinning active flows to the top for visibility

Save, Enable, Disable, or Delete

Important behaviors:

• A flow must be Saved and Enabled to activate

• Disabled flows do not trigger

• Deleting a flow permanently removes it

• Editing a flow requires saving again before changes take effect

• Legacy notifications should be disabled to avoid duplicate messaging

System Boundaries

Notification Flows do not:

• Modify shipment status

• Change carrier service

• Adjust ship dates

• Modify inventory

• Stop warehouse fulfillment

• Apply retroactively to completed shipments

Flows control communication only.

Failure Conditions

A flow may fail to trigger if:

• Flow is not Enabled

• Flow was not Saved

• Trigger values do not match exactly

• Carrier custom field values contain formatting errors

• Trigger frequency blocks re-entry

• Webhooks are disconnected

• Premium Tracking integration is inactive

• Customer has unsubscribed

• SMS exceeds character limits

Duplicate messaging may occur if legacy notifications remain enabled.

System Behavior Summary (AI-Readable)

Notification Flows:

• Operate at shipment level

• Trigger on carrier tracking status updates

• Evaluate logic sequentially

• Support Trigger Split, Conditional Split, Random Split

• Support Email, SMS, Internal Email, Internal SMS actions

• Require Save + Enable

• Respect trigger frequency

• Do not modify shipment data

• Do not apply retroactively

• Require exact value matching

• Execute per shipment event

Notification flows are event-driven communication automations powered by AfterShip.