Bird Pickup & Delivery Adds Shopify Flow Delivery Automation

A florist messaged us in May asking how to automate recurring deliveries for her subscription customers. She had built the perfect Saturday-bouquet box, signed up customers, and then realised she was logging into Shopify every Friday night and manually editing the next delivery date on every recurring order. Twenty subscribers, twenty edits, every week.

Shopify Flow delivery automation with Bird Pickup & Delivery is the practice of automatically updating delivery dates, pickup slots, courier data, and order metafields using Shopify's no-code automation engine. She did not know it existed. One workflow, set up once, and every recurring order arrives in her dashboard with the correct delivery date already attached.

The Flow Automation Map

Three places where Shopify Flow delivery automation with Bird Pickup & Delivery removes manual work for local shops:

1. Subscriptions that update themselves. Once the workflow is built, every recurring order auto-increments to the next delivery date, so weekly or monthly customers do not need a fresh date pick each cycle.
2. Third-party courier sync. Every new or edited order pushes the delivery date, time slot, and address to whichever third-party service handles your last-mile.
3. Order data on invoices and packaging slips. Delivery details written into order metafields so they appear in Order Printer, Liquid email templates, and any external app that reads metafields.

Bird's Shopify Flow integration is now wired into all three. If you run a florist, bakery, butcher shop, or any other local delivery business on Shopify, this is the layer that turns your scheduling app into something that talks to the rest of your stack while you sleep.

What is Shopify Flow, and why should a local shop care?

Shopify Flow is Shopify's no-code automation engine. It listens for events ("an order was placed", "a customer was tagged", "a billing cycle completed") and runs actions in response ("send an email", "add a tag", "update a metafield", "call an external API").

For a national e-commerce brand, Flow saves a developer's salary. For a local shop running pickup and delivery on Shopify, it saves your evening hours. Every manual data export from one app into another, every Friday-night dashboard edit, every WhatsApp message to your delivery driver with the day's addresses, is a candidate for Flow.

Bird Pickup & Delivery is the part of your stack that knows when each order is supposed to be delivered or picked up, by which method, and from which location. The Flow integration turns that knowledge into events the rest of your stack can react to.

The triggers Bird exposes inside Shopify Flow

Once Bird's Flow integration is enabled, six events show up inside the Shopify Flow trigger picker, grouped by order type:

Order type	Trigger events
Delivery orders	Delivery order created, Delivery order updated
Pickup orders	Pickup order created, Pickup order updated
Shipping orders	Shipping order created, Shipping order updated

A "created" trigger fires the moment a customer checks out with that fulfilment method. An "updated" trigger fires when the delivery method, date, time slot, or location attributes change later. That second category is the one most merchants underestimate: customers do call to move their pickup from Tuesday to Wednesday, and your downstream systems need to hear about it.

Inside Flow, all the standard Shopify order fields are available on these triggers (customer, line items, total, shipping address, tags). On top of that, Bird's delivery attributes (date, time slot, method, location) are exposed via order.customAttributes, the same key Shopify uses for cart attributes. If you have a "Delivery Date" custom attribute on the order, your Flow workflow can read it like any other variable. Bird also auto-applies delivery-method order tags at checkout, which means any Flow workflow can branch on "is this a pickup or a delivery" without parsing custom attributes at all.

The action Bird exposes inside Shopify Flow

Bird ships one native Flow action: Increment delivery date. It takes an order, an interval, and a count, and moves the delivery date forward by that amount. It is the engine behind every subscription automation below.

Combined with Shopify's generic Flow actions (send email, add tag, call HTTP webhook, update metafield, send to Slack), one Bird trigger plus one or two Flow actions handles most automations a local shop needs.

Use case 1: Subscriptions that update their own delivery dates

If you sell a weekly bouquet box, a monthly meat box, a fortnightly farm crate, or any other recurring product, this is the highest-value workflow in the whole integration.

Without it, every recurring order ships with the first box's delivery date still attached. That date is in the past by the next cycle, and unless someone fixes it manually, the order sits in the queue with broken information. Multiply across every subscriber and every billing cycle and the queue becomes a maintenance job.

With the Flow workflow, the manual update goes away. The four steps:

1. Your subscription app fires a "billing succeeded" trigger when a customer is billed for the next cycle.
2. Shopify Flow catches the trigger.
3. Bird's Increment Delivery Date action runs on the new order and moves the delivery date forward by exactly the subscription's interval.
4. The customer's next bouquet box lands on the right Saturday without anyone opening Shopify.

Bird works with any subscription app that exposes a Shopify Flow trigger for the billing-success event. That covers Recharge (which has a native Bird integration on top of Flow), Appstle, and most other Shopify-ecosystem subscription apps. The Recharge integration on Bird handles the increment natively; for the others, the same Increment Delivery Date action runs from inside Flow.

If you have ever stayed late on a Sunday updating subscription dates because you forgot to do it on Friday, this is the workflow you build first.

Use case 2: Third-party courier handoff that stays in sync

The second use case is one a bakery owner asked us about recently. He had hired an outside courier service to handle his deliveries. Every time a customer placed a new order, or changed the delivery date or address after the fact, the courier needed the updated information. He was copying details out of Bird's dashboard into the courier's portal by hand. He wanted Flow to do it.

The shape of the workflow:

1. A customer places a new order or edits the delivery date or address on an existing one.
2. Bird's "Delivery order created" or "Delivery order updated" trigger fires inside Shopify Flow.
3. Flow calls the courier's webhook with the order's delivery date, time slot, customer address, and any special instructions stored on the order.
4. The courier's system updates in the format their pipeline expects, without anyone retyping anything.

The same pattern works for any external service: a route planner that needs each day's stops, a kitchen display system that needs to know which delivery orders are due today, a Slack channel that pings the bakery team when a pickup is rescheduled. Anything with an inbound webhook can sit at the end of a Bird trigger.

The "updated" trigger is what makes this workflow durable. A new-orders-only integration is brittle, because every customer-initiated date change becomes a silent error. With the updated trigger wired in, every change in Bird propagates to the courier without anyone retyping anything.

Use case 3: Delivery details on invoices, packaging slips, and emails

The third workflow is quieter, and bakers and butchers tend to discover it after their first peak season. Their Order Printer template prints the customer's billing and shipping address but not the delivery date or pickup time. Their order confirmation email lists the line items but not the slot the customer chose. The data is in Bird; it just is not where their templates can read it.

Order metafields are the standard place to put that data. Once delivery date, time, and method live on the order as metafields, every Liquid template can reach them with a single tag, and every external app that reads metafields (accounting, fulfilment, route planning) gets the information for free.

The workflow:

1. A customer checks out with a delivery method selected.
2. Bird's "Delivery order created" trigger fires inside Shopify Flow.
3. A "Set order metafield" action writes the delivery date, time, and method onto custom order metafields.
4. Order Printer, Liquid email templates, and any metafield-aware app read the data from there. Your packaging slip prints "Delivery: Saturday 9–11 AM" and your accounting export carries the date next to the total.

Bird's help centre has a worked example you can copy for date, then adapt for time and method the same way.

For shops running V2 widgets, some of this data is already attached. For older V1 setups, the Flow workflow is how you get parity without rebuilding your widget.

How to enable Bird's Shopify Flow triggers

The setup is two high-level steps with no code or theme edits required:

1. Toggle the integration on inside Bird Settings.
2. Open the Shopify Flow app in your Shopify admin and use Bird's triggers and the Increment Delivery Date action when building any workflow.

For the full step-by-step walkthrough with screenshots, including which trigger to pick for each use case, see the Shopify Flow Integration Guide on the help centre.

Should I use Bird with Shopify Flow, or build the workflows myself?

Shopify Flow gives every Shopify store a generic event system. Out of the box, it can trigger on an order being created or updated, on a customer being tagged, on a fulfilment being created. What it does not know on its own is whether that order is a delivery, a pickup, or a shipped parcel; which time slot the customer chose; or which location is fulfilling it. It also has no native action to move a delivery date forward by an interval.

A merchant who wants to build the workflows in this article from raw Shopify Flow has three jobs ahead of them.

Detect the fulfilment type. Without Bird's delivery-method triggers, every workflow starts on Shopify's generic "order created" trigger and runs a Condition action that parses tags or attributes to identify delivery vs pickup vs shipping. That logic has to be re-implemented inside every workflow. With Bird's six named triggers, the fulfilment type is already known.

Move the date. There is no native Shopify Flow action that increments a delivery date by an interval. From raw Flow, you have to call the Shopify Admin API as an HTTP action, do the date math, format the new date string, and write it back to the right metafield. With Bird's Increment Delivery Date action, that is a single drag-and-drop step.

Handle the schema. Bird already stores delivery date, time slot, and method on the order in a known shape. Without Bird, the merchant designs that schema themselves and keeps it consistent across every order, every theme, every checkout path. With Bird, the data sits in order.customAttributes for Flow to read every time.

None of this means Shopify Flow alone is the wrong tool. For non-delivery automation like loyalty tagging, fraud rules, or inventory alerts, Flow is exactly the right shape. For local pickup and delivery scheduling, Bird turns those workflows into a few clicks instead of a small engineering project.

Why this matters more for local shops than for national brands

The cliché about Shopify automation is that it is for huge stores with operations teams. The opposite is true. A national brand shipping flat-rate parcels has one fulfilment workflow per warehouse. A local florist running pickup, delivery, and shipping out of one storefront has three. A multi-location bakery has nine. The smaller the shop, the more delivery permutations sit on every order, and the more painful manual data-shuffling becomes.

Most local shops still run that data-shuffling on willpower. They re-type addresses into courier dashboards on a Sunday night. They keep a spreadsheet of subscription delivery dates open in another tab. They write the delivery slot in pen on the packaging slip after Shopify prints it.

The Flow integration handles the data shuffling for you. It treats each delivery and pickup event as a thing other apps can react to, without anyone writing a line of code.

FAQs

Do I need a paid Shopify plan to use Bird with Shopify Flow?

Shopify Flow itself is free across all Shopify plans, so there is no Shopify-side upgrade involved. The gate is on Bird's side: the Shopify Flow integration is included on every paid Bird plan (Essential and above). Free-plan Bird stores need to upgrade before they can enable the integration toggle.

Does the Shopify Flow integration work with subscription apps?

Yes. Bird works with any subscription app that exposes a "billing succeeded" trigger inside Shopify Flow. That covers Recharge, Appstle, and most of the rest of the Shopify subscription ecosystem. Recharge also has a deeper native Bird integration that handles the date increment automatically; for the others, Flow is the bridge.

What is the difference between a "created" and an "updated" Flow trigger?

A "created" trigger fires once, the moment a customer checks out and the order lands in Shopify. An "updated" trigger fires every time the delivery method, date, time slot, or location attribute changes on the order afterwards. If your downstream systems need to stay in sync when customers reschedule, the updated trigger is the one you want.

Can I get the delivery date and time onto my Order Printer packaging slip?

Yes, by routing the data into an order metafield via Flow. Once delivery date, time, and method are stored as metafields, your Order Printer template can read them like any other Liquid variable and print them on the slip. Bird publishes a step-by-step in the help centre.

Will the integration slow my checkout down?

No. Flow runs asynchronously after the order is created or updated, so the customer's checkout is finished before any workflow starts. The shopper sees no delay; the automation happens in the background, typically within seconds of the order event.

What if my external app does not support webhooks?

Then it cannot sit at the end of a Flow workflow directly. The usual workaround is to send the data through a middle layer that does support webhooks, or to export from metafields on a schedule. Most modern Shopify-ecosystem apps support one or the other.

Try the workflow on your own store

If you run a subscription florist, a bakery with weekly pickups, or any local shop with a third-party courier, the workflow that saves the most time on day one is usually the subscription one. Build it first; the other two are straightforward once the pattern is set.

Bird Pickup & Delivery is trusted by 7,000+ Shopify merchants in 60+ countries. The Shopify Flow integration is included on every paid Bird plan, with no extra charge.

Start your 14-day free trial of Bird Pickup & Delivery on the Shopify App Store. No credit card required.