The Klaviyo & Malomo Integration gives users powerful ways to trigger personalized emails based on their order's shipment status. The following events are available to trigger emails:

MALOMO METRICS

With an active Malomo integration in your Klaviyo account, these metrics become available for Flows:

METRIC

DESCRIPTION

Malomo: ShopifyOrderCreated

Shopify records a new order placed by a customer.

Malomo: ShipmentCreated

Shopify records a new shipment on an order and that shipment registers in the Malomo platform.

Malomo: ShipmentUpdateReceived

The carrier registers a new shipment status with Malomo.

Malomo: OrderIssueCreated

Malomo identifies a problem with an order or shipment.

SHIPMENT STATUSES

With an active Malomo integration in your Klaviyo account, these statuses become available as Flow Triggers in the Malomo: ShipmentUpdateReceived metric:

METRIC

DESCRIPTION

pre_transit 

A shipping label was created but the carrier has not yet taken possession of the shipment.

in_transit 

The shipment is in the carrier’s possession and is en route to its destination.

out_for_delivery

The shipment is currently on its last mile and is en route to the destination address.

delivered

The local delivery vehicle has reported the package was delivered.

return_to_sender

The shipment was not successfully delivered and is en route back to sender.

cancelled 

The delivery has been cancelled typically by either the seller or recipient.

available_for_pickup 

The shipment is available for pickup from the carrier’s facility such as a post office.

failure 

The shipment could not be delivered.

error 

An unknown delivery error occurred.

unknown

The carrier doesn’t know the current status of the shipment.

PROBLEM TYPES

With an active Malomo integration in your Klaviyo account, these problem types become available as Flow Triggers in the Malomo: OrderIssueCreated metric:

METRIC

DESCRIPTION

FulfillmentStalled

An order that has been created but has not been fulfilled in the specified time frame.*

ShipmentStalled

An order that has been fulfilled or is in transit and has not received a scan update in the specified time frame. *

ShipmentDeliveryAttempted

This event is created based on the carrier status of “failure”, meaning the shipment could not be delivered.**

ShipmentReturnToSender

This event is created based on the carrier status of “return_to_sender”, meaning the shipment could not be delivered and is en route back to the sender.**

*For FulfillmentStalled and ShipmentStalled, the default stalled timeframe is set to 72 hours with Saturdays and Sundays excluded. You may change this in the configuration panel at any time. Please note that the change is not retroactive, and will apply only to new orders placed after updating your settings. 

** In Klaviyo, the ShipmentDeliveryAttemped and ShipmentReturnToSender serves the same purpose as the Malomo: ShipmentUpdateReceived metric paired with the “failure” or "return_to_sender" status. Enabling this problem type will not overwrite any flows based on the existing event.

Important Notes for Problem Orders:

  • At this point, the “Stalled” flag is not a real-time status. It is added to an order once the stalled criteria are met, and is not removed. 

  • Unless you exclude Saturdays and/or Sundays from the Stalled logic, you will notice a spike in Stalled orders created on Sundays and Mondays, as most carriers are not scanning packages throughout the weekend. 

  • Due to the point above, we recommend that you take some time to understand the effects of your chosen configurations before building any customer-facing automations.