Skip to main content

PDQ shipping events in Klaviyo

Every PDQ metric you can trigger a Klaviyo flow on, and what fires each one

PDQ can send 28 shipping and delivery events to Klaviyo. Each one arrives as a metric named PDQ_Shipping_Event_ plus the status, and each can trigger a flow.

Statuses come from the carrier and from PDQ's own order queue, which is why this list goes well beyond what a fulfillment status can tell you. To switch any of them on, see Integrating Klaviyo with PDQ.

A metric only appears in Klaviyo after it has fired once, so a new store will see this list fill in gradually.

Order and fulfillment

  • PDQ_Shipping_Event_ORDER_PLACED — the order came into PDQ.

  • PDQ_Shipping_Event_NEW — the order was fulfilled.

  • PDQ_Shipping_Event_IN_FULFILLMENT — the order is being picked and packed.

  • PDQ_Shipping_Event_BACKORDER — the order is waiting on stock.

  • PDQ_Shipping_Event_GIFT_ORDER — the order was flagged as a gift.

On its way

  • PDQ_Shipping_Event_READY_FOR_CARRIER_PICKUP — labelled and waiting for the carrier.

  • PDQ_Shipping_Event_PICKED_UP — the carrier has the parcel.

  • PDQ_Shipping_Event_IN_TRANSIT — en route to the customer.

  • PDQ_Shipping_Event_OUT_FOR_DELIVERY — on the truck for today's delivery.

  • PDQ_Shipping_Event_WAITING_FOR_PICKUP — waiting at a pickup point or store.

  • PDQ_Shipping_Event_NOT_PICKED_UP — still sitting at the pickup point.

  • PDQ_Shipping_Event_DELIVERED — delivered.

Something went wrong

  • PDQ_Shipping_Event_LATE — past the delivery promise.

  • PDQ_Shipping_Event_STUCK_IN_TRANSIT — moving, then stopped.

  • PDQ_Shipping_Event_NOT_UPDATED — the carrier has gone quiet on this parcel.

  • PDQ_Shipping_Event_ATTEMPTED_DELIVERY — the carrier tried and could not deliver.

  • PDQ_Shipping_Event_FAILED_TO_DELIVER — delivery failed.

  • PDQ_Shipping_Event_DAMAGED — the parcel was damaged.

  • PDQ_Shipping_Event_LOST — the parcel was lost.

  • PDQ_Shipping_Event_REJECTED — the customer refused the parcel.

  • PDQ_Shipping_Event_RETURN_TO_SENDER — the parcel is on its way back to you.

Needs the customer or you to fix something

These fire before the parcel ships, which is the whole point. A flow built on one of these can get the problem fixed while the order is still in your warehouse.

  • PDQ_Shipping_Event_FIX_ADDRESS — the shipping address needs correcting.

  • PDQ_Shipping_Event_FIX_PHONE — the phone number is missing or invalid.

  • PDQ_Shipping_Event_FIX_FRAUD — the order was flagged for a fraud check.

  • PDQ_Shipping_Event_FIX_INVENTORY — an inventory problem is holding the order.

  • PDQ_Shipping_Event_FIX_MEASURES — weight or dimensions are missing or wrong.

Cancellations

  • PDQ_Shipping_Event_PENDING_CANCELLATION — a cancellation has been requested.

  • PDQ_Shipping_Event_CANCELED — the order was cancelled.

Where to start

You don't need all 28. Four recipes cover most of the value:

  • OUT_FOR_DELIVERY — the highest-open-rate email you will ever send. Good place for a review request teaser or a replenishment nudge.

  • LATE — tell the customer before they email you. This is the single biggest lever on WISMO tickets.

  • FIX_ADDRESS — ask the customer to correct the address while the order is still editable.

  • DELIVERED — the natural trigger for reviews, UGC, and the next purchase.

A note on cancellations: if you build a flow on CANCELED, test it against orders that were edited rather than cancelled. Order edits and tax recalculations can look like a cancellation depending on your setup, and you don't want a cancellation email going to someone whose order is on its way.

That's it! If you want help mapping these to your existing flows, reach out to support@prettydamnquick.com.

Did this answer your question?