Shopify Flow recipes for furniture stores

The buyer opens Shopify to look for orders needing attention. The showroom manager checks whether the last floor-model chair sold. Someone else keeps a list of unfulfilled orders that need a follow-up. These are useful candidates for automation because the question and the next action can be stated plainly.

Shopify Flow is a free app on Basic, Grow, Advanced, and Plus. Send HTTP Request requires Grow or higher, and tasks from custom partner apps require Plus, according to Shopify’s Flow overview. Start with a narrow internal task, then test that the workflow makes the right record easier to find.

Tag special-order products when an order is created

Recipe: Order created → at least one catalog line’s product has your special-order tag → Add order tags with a reporting label.

This works when the product tag already expresses a reliable catalog classification. The order tag makes the sale easier to find; it does not decide whether the vendor should start building.

Use a distinctive label, such as “special-order-review,” and define what staff should do with that group of orders. Test an ordinary stock order, a special-order line, and an order mixing both.

If the line is a custom item without the expected product record, the product-tag condition needs a separate treatment. Do not assume every descriptive order line has a catalog product behind it.

The trigger and action names come from Shopify’s trigger reference and action reference. Those references are also where to check the exact data each step receives.

Alert the buyer about a large accepted sale

Recipe: Order paid → order total exceeds the store’s chosen threshold and the order matches the purchasing category → Send internal email.

Choose Order created instead if the buyer needs to review orders before full payment. The trigger should match the store’s release process, not whichever event is easiest to remember.

For an illustrative threshold of $5,000, test orders below, at, and above the boundary. State whether the condition uses a total including tax and delivery, and use the correct currency field for the store.

The email should identify the order and the reason for review. “Order needs purchasing review” is more useful than “Big order!” A high value is a prompt to look, not evidence that the specification is approved.

Keep the notification internal. A purchasing alert should not also tell the customer that production has started.

Flag a floor-model quantity that needs attention

Recipe: Product variant inventory quantity changed → the product is marked as a floor model and the chosen quantity falls below the store’s threshold → Send internal email.

Shopify’s inventory-change trigger responds to changes from orders, manual adjustments, and apps. That means a receipt or correction can also start the workflow.

Use the previous and current values to detect crossing the threshold rather than sending an alert on every change below it. If the job concerns one showroom, inspect the appropriate location inventory rather than treating a store-wide total as that showroom’s count.

The action is a review alert. It does not move inventory or remove the display piece from the floor.

Ask the receiving or showroom owner to confirm what happened. A floor-model chair can disappear from the count while remaining quite visibly under a cushion.

Tag approved trade customers when they place an order

Recipe: Order created → the order has a customer already carrying the store’s reviewed trade-approval label and lacks the reporting label → Add customer tags with that reporting label.

Use this when the reporting group should identify approved trade buyers who have placed an order. It does not label every newly approved contact immediately.

Keep the reporting label distinct from the approval label. The tag should not grant a tax exemption or prove that a resale certificate is valid; it identifies a reporting group after a person has completed the approval process.

Avoid a customer-tag feedback loop. Shopify’s Customer tags added documentation explicitly warns against combining that trigger with Add customer tags in the same workflow. Starting from Order created avoids that trigger/action pairing.

Test an approved buyer, an ordinary customer, an order without a customer, and a buyer already carrying the reporting label. Only the first case needs a new tag.

Review stale unfulfilled orders on a schedule

Recipe: Scheduled time → Get order data for open orders older than the chosen age with work still unfulfilled → notify the desk about records needing review.

Shopify provides the Scheduled time trigger and Get order data action. A scheduled workflow needs that data step because the clock does not supply an order by itself. Get order data returns at most 100 records, so partition larger backlogs into bounded groups and verify the coverage instead of treating the first result set as every waiting order.

Say the review threshold is thirty days in this example. Exclude canceled orders and distinguish partial fulfillment from a wholly unfulfilled order. Decide whether the desk wants a digest or separate messages, and prevent the same unresolved item from becoming a fresh-looking alert every morning.

An old unfulfilled order is not automatically late. A made-to-order sofa may be progressing exactly as agreed. The notification should ask for review against the promised window, not declare a breach or send an apology automatically.

Test without changing live orders first

Shopify’s Winter ’26 release includes workflow testing without impacting real store data, a vertical editor, and the ability to cancel runs.

Use the test mode to inspect which conditions pass and which actions would run. Include a sample that should be excluded, not only the order you expect to match.

Then review repeat behavior. If a tag already exists, a quantity changes again, or a scheduled run sees yesterday’s order, what happens? Repeated internal email can become its own sorting task.

Name each workflow after its purpose, give it an owner, and review it on a regular schedule. A useful monthly check asks whether the rule still matches the store’s process and whether anyone reads its output.

Do not assume Flow sees OrderPilot’s internal stages

Flow reacts to the Shopify data and events its triggers or integrations expose. An OrderPilot production stage is not automatically a native Flow trigger.

Order tags set in OrderPilot sync with Shopify, but Flow has no native Order tags added trigger. A tag arriving later does not retrigger Order created. Use a scheduled data check or another documented event when a rule needs to inspect later-arriving tags.

The order tags and filters guide explains how staff can use those labels. Keep “the tag is visible” separate from “this event starts a workflow.”

For the broader distinction, read Shopify order statuses versus working stages.

Use OrderPilot connections for its own order events

OrderPilot’s status map has connections for signing, payment, PO sends, receiving, and delivery, with conditions governing the move. Use those events when the decision depends on the custom sale’s actual progress.

For example, a PO-sent connection can move the order to the appropriate vendor-sent stage when its purchasing conditions are met. A partial send should not be mistaken for every vendor having the order. Draft maps can be tested against an order and published with version history. The connection guide and testing guide explain those controls. Configured status emails can then tell the customer what changed. Enabled status SMS uses fixed templates; email provides the richer tailored message. Assign each notification to one workflow so two systems do not send competing updates.

Put each job beside the facts it needs

Begin with the recipe that removes a real repetitive check from the desk. Use the made-to-order Shopify guide to place it within the full order process, then test before the team relies on it.

Sources

1. Shopify Flow — Shopify Help Center.
2. Triggers in Shopify Flow — Shopify Help Center.
3. Actions in Shopify Flow — Shopify Help Center.
4. Product variant inventory quantity changed — Shopify Help Center.
5. Customer tags added — Shopify Help Center.
6. Scheduled time — Shopify Help Center.
7. Get order data — Shopify Help Center.
8. Winter ’26 Editions — Shopify, Winter ’26.