Skip to main content
Update a variant’s cart message or ship date and Bloom applies it to every open pre-order for that variant. With Klaviyo connected, Bloom also sends an event so you can email each affected customer.

​
What Bloom updates

When you save a new ship date, cart message, or both, Bloom finds every unfulfilled pre-order with that variant. A cart message change:
  • Appends an Updates: line to the order note in Shopify admin, with a timestamp.
  • Updates the Bloom: Pre-order Order Status block (if added) - customers see the new message with a Last updated tag.
  • Writes the order metafield bloom.preorder_message_history with per-variant history.
Either change sends a Pre-order Ship Date Updated event to Klaviyo. A date-only change sends the event only - the order note, order status message and history metafield stay as they are. Changes propagate within a minute or two.

​
Notify customers with Klaviyo

We recommend this route. With Klaviyo connected, each save sends one Pre-order Ship Date Updated event per affected order to the customer’s Klaviyo profile. It covers orders placed through Bloom’s pre-order purchase option, the pre-order line property, and Fast Bundle pre-order components.
  1. In Klaviyo, go to Flows and click Create flow, then Build your own.
  2. Select Metric as the trigger, then Pre-order Ship Date Updated.
  3. Optional: add a Trigger split on ship_date_changed or message_changed to send different copy for each.
  4. Add an Email and build it with the event properties:
  5. Set the flow to Live.
The metric shows in Klaviyo once Bloom sends its first event. Change the ship date on a variant with a test pre-order to create it.
Bloom doesn’t send the event when Klaviyo isn’t connected, the order has no email (phone-only customers get nothing), or the save fails. Re-saving the same date or clearing the date doesn’t count as a change. Market ship date overrides aren’t supported yet.

​
Event properties

  • event_handle - always preorder_ship_date_updated.
  • order_id, order_name, order_number
  • product_title, variant_title, variant_id
  • previous_message, new_message - the cart message before and after. A date-only change repeats the current message in both.
  • previous_ship_date, new_ship_date - YYYY-MM-DD. A message-only change repeats the stored date in both. Omitted when no date is set.
  • ship_date_changed, message_changed - true for whichever changed.
  • changed_at - ISO timestamp of the save.

​
Notify customers via Shopify Flow

Use this if you don’t use Klaviyo. Bloom doesn’t ship its own Shopify Flow connector, but it updates the order via Shopify’s API, so you can build a Flow workflow off the change. Flow only sees cart message changes - a date-only change doesn’t update the order.
This setup isn’t end-to-end tested by us yet. Run it in a dev store before turning it on for customers.
  1. In Shopify admin, open Apps → Shopify Flow → Create workflow.
  2. Trigger: an order-update trigger (e.g. Order edited or Order updated, depending on what’s available in your store).
  3. Condition: Order tags contain Pre-order.
  4. Action: send an email or use your preferred connector. The bloom.preorder_message_history metafield lives on the order resource, so reference it via Liquid in the action body - e.g. {{ order.metafields.bloom.preorder_message_history }}. Flow’s dedicated metafield action doesn’t expose order metafields directly.
  5. Turn the workflow on.
Shopify Flow fires on every order update. The Pre-order tag condition keeps it focused on the right orders.

​
Tips

  • Update one variant at a time when only one product has shifted.
  • Keep cart messages explicit - they’re quoted verbatim. Ships 12 August travels further than Slight delay.
  • Use the order note for internal notes too - anything outside Bloom’s ▼▼ Pre-order [Bloom] ▼▼ markers stays put across updates.