Skip to main content

Shopify Flow Automation for Bulk & Multi-Recipient Orders

Use Send To Many's four Shopify Flow triggers, its Add order line item action, and standard order triggers to fulfill parent orders, add items to recipient orders, send delivery digests, copy PO numbers, route recipient orders, and sync Sends to external systems.

Send To Many includes Shopify Flow triggers and an action that let you build automations directly in Flow, with no webhooks or custom code required. You can also use Flow's standard order triggers, since every recipient order we generate is a regular Shopify order.

Send To Many's Flow Triggers​

Four triggers are available in the Shopify Flow trigger picker under Send To Many. Each one passes a set of fields you can use in your Flow conditions and actions.

Send Created​

Fires when a new Send is created. Use it to notify your team that a new bulk order is in progress, log the event to an external system, or kick off preparation workflows.

Fields available:

  • Send ID: the Send To Many Send ID
  • Send name: the name the merchant gave the Send
  • Send preset name: which Send preset was used (e.g., "Corporate Gifting")
  • Send source: manual, inquiry, or storefront
  • Customer ID: the Shopify customer's legacy numeric ID
  • Customer name: the customer's display name
  • Assigned user email: the team member assigned to the Send (if any)

Send Completed​

Fires when a Send has finished generating recipient orders. A completed Send can still have orders that failed to create, so check Number of orders failed before treating the Send as fully processed. Use it to notify the gifter, trigger post-generation workflows, or update a CRM.

Fields available: all 7 fields from Send Created, plus:

  • Number of orders created: count of successfully generated recipient orders
  • Number of orders failed: count of orders that failed (e.g., inventory issues)
  • Number of import rows: total non-excluded rows in the Send

Send Fulfillment Status Changed​

Fires once a day, in the morning, for every Send whose recipient orders had shipment status changes in the previous 24 hours. It carries counts, not recipient details: how many orders and shipments are delivered, in transit, delayed, failed, and so on, plus a summary of what changed. This is the trigger behind the delivery digest.

Fields available:

  • Customer: a Shopify customer reference for the gifter, so Flow can use their email and other customer fields
  • Send ID, Send name, Send preset name, Send source, Assigned user email: same as Send Created
  • Parent order ID and Parent order name: the gifter's order, when there is one
  • Order counts: total orders, orders with status changes, orders with all shipments delivered, orders with shipments in progress, orders with no shipments, and orders fulfilled, partially fulfilled, and unfulfilled
  • Shipment counts: total shipments, and a count for each carrier status (delivered, in transit, confirmed, out for delivery, delayed, failed delivery, attempted delivery, returning to sender, ready for pickup, and unknown)
  • Overall fulfillment status: one value for the Send as a whole. It reads has_delivery_issues whenever any shipment is delayed, failed, attempted, or returning to sender.
  • Changed statuses summary and Current statuses summary: readable text summaries for emails and messages

The trigger only runs for your store once an active workflow uses it, and it only fires for Sends that are Finished. The full field reference and the inclusion rules are in the delivery digest tutorial.

Aggregate Draft Order Completed​

Fires when the aggregate draft order (the gifter's invoice) is paid, or marked as complete with payment due later. Use it to sync payment data to an external system, send a receipt confirmation, or trigger downstream workflows.

Fields available:

  • Order: a Shopify order reference for the order created when the draft was completed. Flow can use it to reach the full order object.
  • Send ID, Send name, Send preset name, Send source, Customer ID, Customer name, Assigned user email: same as Send Created
  • Aggregate draft order name: the Shopify draft order name (e.g., #D1234)

Getting Started with Flow Triggers​

Flow triggers work automatically. To use them:

  1. Open Shopify Flow from your Shopify admin.
  2. Create a new workflow.
  3. In the trigger picker, search for "Send To Many" or browse the app triggers.
  4. Select the trigger you want: Send created, Send completed, Send fulfillment status changed, or Aggregate draft order completed.
  5. Add your conditions and actions as you would with any Flow workflow.

No configuration is needed in Send To Many itself. The triggers register automatically when you install or update the app.

Let Sidekick build it

Shopify's Sidekick assistant is good at building these workflows. Describe what you want in plain language, for example "when a fulfillment is created on an order tagged Send to Many, find the order with the same Send tag and the Send to Many aggregate tag and mark it fulfilled", and review the result before turning it on.

Send To Many's Flow Action: Add Order Line Item​

The Add order line item (Send to Many) action adds a product to an existing order. Use it to add something to every recipient order in a Send, such as packaging, a printed insert, a catalog, or a free sample, without editing each order by hand. It shows up in the Flow action picker under Send To Many.

The action uses Shopify's order editing, so the item is added the same way as if you'd clicked Edit on the order: it appears on the order, reserves inventory, and is fulfilled with the rest of the order.

FieldWhat it does
OrderThe order to add the item to. Comes from the workflow, so use a trigger or step that provides an order.
Product variantThe variant to add, as a variant GID (gid://shopify/ProductVariant/123) or a numeric variant ID.
QuantityHow many to add. Must be 1 or more.
Allow duplicate variantsOff: if the variant is already on the order, nothing is added. On: the quantity is added even if the variant is already there.
Email order updates to customerSends the order's customer Shopify's order edit email, including any payment request. Leave it off unless you want the customer told about the change.
Order timeline noteOptional note for your staff, shown on the order timeline.

Balances from added items​

The item is added at its normal catalog price. Adding a product with a price above $0 leaves a balance owing on that order, because the order total goes up after it was paid. That's true whether recipient orders were created with calculated or $0 order revenue.

You have three ways to handle it:

  • Use a $0 product. For inserts and packaging you don't charge for, create the item as a $0 product or variant. No balance is created.
  • Mark the order as paid in the same workflow. Add Shopify's Mark order as paid action after the Send To Many action. It marks the order that triggered the workflow as paid, so it works when the workflow starts from that order, for example with Order created. It doesn't capture any payment.
  • Resolve it manually. Open the order in Shopify admin and settle the balance there, for example by marking it as paid.

Example: add an insert to every recipient order​

  1. Trigger: Order created.
  2. Condition: the order tags include Send to Many # and don't include Send to Many aggregate, so only recipient orders match. Add a condition on a Send preset tag if you only want some Sends.
  3. Action: Add order line item (Send to Many) with your insert's variant ID and a quantity of 1.
  4. If the insert has a price, add Mark order as paid.

Shopify Flow workflow with an Order created trigger, a condition matching Send To Many recipient order tags, the Send To Many Add order line item action, and Mark order as paid

tip

The action works on any order in your store, not only orders created by Send To Many. Keep the tag condition in place so it only edits the orders you mean to change.

Example Automations​

Delivery digest emails​

Send gifters one daily shipping update per Send instead of an email for every shipment. The Send fulfillment status changed trigger passes the day's counts to your email platform, and the email links to the Sends page in the customer account, where every recipient and tracking number already lives.

The workflow is the trigger, an optional condition on Send source or Send preset name, and a Klaviyo Track an event action (or a Send HTTP request action for other platforms). The step-by-step build, including the Klaviyo flow and email template, is in Set Up Delivery Digest Emails with Shopify Flow and Klaviyo.

Shopify Flow workflow for the Send To Many delivery digest with the Send fulfillment status changed trigger connected to the Klaviyo Track an Event action

Delivery problems to your team​

The same trigger can alert your team instead of, or as well as, the gifter. Add a condition where Overall fulfillment status equals has_delivery_issues, then send an internal email or post to a Slack or Teams channel with Send HTTP request. Include Send name, Assigned user email, and Changed statuses summary so whoever picks it up knows which Send and what happened.

Notify your team when a Send is created​

Use Send created with a Send internal email action, or an HTTP request to a Slack channel, so your fulfillment team can prepare inventory. Add a condition on Send source to alert only on storefront checkout Sends, which arrive without anyone on your team having seen them.

Tag the gifter after a Send completes​

Use Send completed to add a tag such as bulk-gifter to the customer record for segmentation in your email platform. The trigger passes Customer ID, which Flow can use to look up the customer.

Sync to external systems​

When a Send completes, or when its invoice is paid, push the Send details to your ERP, CRM, or a spreadsheet with Flow's Send HTTP request or Add row to Google Sheets actions. The Aggregate draft order completed trigger includes the paid order itself, which makes it the right starting point for revenue and reconciliation workflows. See Send To Many and your ERP for how the parent and recipient orders fit together.

Triggering Flows on recipient orders

You can also trigger Flows on the individual recipient orders Send To Many creates. Use Flow's standard Order created trigger and filter on the tags Send To Many adds to your orders (either the default tags or the tags you configure on your Send preset or checkout settings).

Order-Based Flow Patterns​

Since every recipient order is a standard Shopify order, your existing order-based Flow workflows fire normally. You can also build Send To Many-specific workflows using the tags and attributes on each order.

Identifying Send To Many orders in Flow​

Use these filters to target Send To Many orders specifically:

  • Order tags: every order in a Send carries a Send to Many #<Send ID> tag. The parent (aggregate) order also carries Send to Many aggregate. Add your own tags in your Send preset settings or checkout settings.
  • Payment gateway: "Send to Many"
  • Sales channel: "Send to Many"

The Send ID tag is what links a recipient order to its parent and siblings. In a Get order data action, a query such as tag:'Send to Many #1234' returns every order in the Send, and adding AND tag:'Send to Many aggregate' narrows it to the parent.

Fulfilling the parent order​

Parent orders don't ship, so left alone they sit unfulfilled in your queue and, if you capture payment on fulfillment, they never capture. A Flow can fulfill them for you. Pick the timing that matches your accounting rules:

  • Immediately. Trigger on Order created, check that the order tags include Send to Many aggregate, and mark its fulfillment orders as fulfilled. The simplest option, and the right one when the parent order only needs to stay out of the fulfillment queue.
  • When the first recipient order ships. Trigger on Fulfillment created, check that the fulfilled order is a Send To Many recipient order (tagged Send to Many # but not Send to Many aggregate), use Get order data to find the parent order with the same Send tag, and mark it fulfilled. Use this when you capture on fulfillment and want to capture as soon as the gifts start shipping.
  • When all recipient orders have shipped. The same as above, with one more step: before fulfilling the parent, Get order data for every order with the Send tag and check that all of them are fulfilled. This is the pattern in the screenshot below, and it aligns with revenue recognition rules that wait for delivery of the goods.

Shopify Flow workflow that fulfills the Send To Many parent order once all recipient orders in the Send are fulfilled

If you'd rather hold than fulfill, the same conditions work with a Hold fulfillment order action. See managing aggregate orders for how parent orders behave in Shopify.

Copying details from recipient orders to the parent​

Details captured per recipient, such as a PO number, cost center, or department, live on the recipient orders as order attributes or metafields. The parent order doesn't get them automatically, which matters when your ERP or your customer's accounts payable team reads the parent. A Flow can copy them: trigger on Order created, check for the Send to Many aggregate tag, use Get order data to fetch one recipient order with the same Send tag, and write the value to the parent with Add order note, Update order metafield, or Add order tags.

Tag-based routing​

Use configurable order tags to route recipient orders to fulfillment workflows. Tag all orders in a Send with marketplace-send and let Flow assign them to a specific fulfillment location, or route them to a 3PL by tag. Dynamic tag variables (Send ID, row number, custom fields) let the same workflow adapt to each Send without manual configuration.

Routing by shipping method​

Recipient orders carry the shipping rate the gifter chose, or the rate your preset assigned. Use a condition on the shipping line title to map rate names to carriers, service levels, or fulfillment locations, which is useful when a shipping method name on the storefront needs to become an internal code for your warehouse or drop-ship partner.

Shopify's newer Flow actions​

Because recipient orders are regular Shopify orders, newer Flow actions apply to them too. Shopify's Buy shipping label action, for example, can buy labels for every recipient order in a Send as the orders come in, filtered by tag or product.

Still have a question?

Ask Manny, the Send To Many bot, about “Shopify Flow Automation for Bulk & Multi-Recipient Orders” or anything else in the docs.