Lifecycle Tags

Lifecycle tagging records the full journey of an order’s WhatsApp conversation on the order itself — from waiting to be messaged, through sent / delivered / read, to the customer’s response and the support conversation that follows.

Unlike the single flow tag you configure, lifecycle tags are managed automatically and move through stages: at each step WhatPro replaces the previous lifecycle tag so the order always shows exactly one current state — never an accumulating pile of “sent / delivered / read”.

Lifecycle order tagging is a Growth and Plus feature.

Which flows use lifecycle tags

Lifecycle tagging applies to the order-confirmation and order-change flows, because those flows always run when an order already exists:

• Cash-on-delivery confirmation
• Bank deposit confirmation
• Manual payment confirmation
• Paid order confirmation
• Order edit updates

The chat open / chat closed stages additionally come from the Team Inbox, when an agent’s conversation is tied back to one of these orders.

The lifecycle stages

A lifecycle order moves through these stages. Each new stage tag replaces the previous one.

Stage	When it is applied
Awaiting send	The flow has a delay, and the order is waiting for its message to go out.
Send success	The WhatsApp message was sent.
Send error	The message could not be sent.
Delivered	WhatsApp confirmed the message was delivered.
Read	The customer opened the message.
Customer response	The customer tapped a quick-reply button or replied.
Chat open	A Team Inbox conversation about the order is opened.
Chat closed	That conversation is marked closed.

The customer’s response always wins over an earlier delivery stage — if a customer replies, the order reflects their action rather than “delivered” or “read”.

Awaiting send

If a confirmation flow has a delay configured, WhatPro tags the order as awaiting its message during the delay window. This lets you spot orders that have been picked up by a flow but not yet messaged. The tag is cleared automatically once the message is sent (or once the order is cancelled before the delayed message would go out).

Chat open and chat closed

When an agent works a Team Inbox conversation that maps to one of the lifecycle orders, WhatPro tags that order as chat open. When the conversation is later marked closed, the chat-open tag is replaced with chat closed.

• The chat-open tag is applied once per conversation.
• The chat-closed tag lands on the same order the chat-open tag pinned, even if a newer confirmation message went out for that customer in the meantime.
• This linking is best-effort: it relies on matching the conversation’s customer to a recent confirmation order. If no order can be matched, no tag is applied.

The Team Inbox is a Plus feature, so the chat open / chat closed stages are only produced on Plus.

Per-flow naming

Lifecycle tags are prefixed so you can tell which flow produced them. Cash on delivery, paid order, bank deposit, and order edit each use a fixed prefix; manual payment uses the payment method name you configured on the flow. The generic stage label (without a prefix) is used as a fallback.

For the exact prefix and stage strings, see the Tag reference.

Behavior and reliability

• Replace, not accumulate. Each transition removes the order’s previous lifecycle tag(s) before adding the new one, so the order carries a single current state.
• Best-effort. Tagging never blocks a WhatsApp message. If Shopify is briefly unavailable WhatPro retries; persistent failures are logged.
• Idempotent. Re-applying or removing a tag the order does not have is a no-op, so lifecycle transitions never create duplicates.

Using lifecycle tags in Shopify

Lifecycle tags are ordinary Shopify order tags, so you can:

• Filter the Orders list to, for example, every order awaiting its confirmation message, or every order whose customer has replied.
• Build dashboards or automations around a specific stage.
• Audit an order’s WhatsApp outcome at a glance from the order page.