How to automate customer updates during custom-order production

Automation is useful when the same thing should happen every time. It is harmful when you pretend a custom shop has no judgment.

A made-to-order workflow has a few honest, repeatable moments: the order moved to a status that should notify the customer, an order has sat in a production step longer than you intended, Shopify marked it fulfilled, a missing Ship by date can be copied from a Shopify field you already trust.

It does not have a Zapier-style engine that talks to every other app you use. Inside Orderflow, you can write custom status rules (if the product title contains a phrase, set a starting status — or if an order stays in a status for two days, move it) in addition to the built-in Shopify rules.

What is worth automating

Status emails. If Proof Sent should always tell the customer, that should not depend on someone remembering to hit send.

Customer actions. Approving a proof, requesting changes, or submitting requested information can move the order to the next status you configured. That is still a rule you chose, not a surprise.

Repeatable product routing. If every order whose product title contains a phrase should start at the same status, a custom rule can set that.

Orders that sit too long. Artwork does not always finish on the day you hoped. Without a rule, someone has to notice the order is still in Working on Art, change the status, and write the customer. If that delay should always get the same next status and the same update, that is a rule — not a judgment call each time.

Shopify fulfillment → your completed step. If “fulfilled in Shopify” always means “we are done in the production queue,” one rule can move the Orderflow status. If fulfillment sometimes means a partial shipment, think before you turn that on.

Ship by dates from Shopify. Only if you already store a real need-by date in additional details, line-item properties, or Shopify’s own ship-by date on the order.

What not to automate by wishful thinking

• Zapier-style connections to every other tool
• Promising a tracking email before you have tracking
• Auto-completing an order because any tracking number appeared
• Emailing the customer for optional photo uploads they may never send

When a production step runs long

Shopify fulfillment status does not tell you that artwork has been sitting for two days. That lives in your production statuses.

A useful pattern:

1. Keep the order in a working status such as Working on Art.
2. If it is still there after the time you chose, move it to a status that means “this is late” — Proof Overdue, for example.
3. If that next status is set to email the customer, they get the update you already wrote. You do not have to find the order and send it by hand.

The customer hears that you are behind and still on it. You stay at the machine. The shop does not wait for someone to remember to check a list.

Stay rules are checked about once an hour. They skip cancelled and already fulfilled orders. Proof Review and Form emails still need a proof or form, so a stay rule does not send those.

Using Orstrax Orderflow

Orderflow automations include built-in Shopify rules (off until you enable them) and custom rules you write:

• Fill a missing Ship by date from Shopify additional details, line-item properties, or the ship-by date on the Shopify order
• Optionally set a missing Ship by date a chosen number of days after the order date
• Move the order to a status you choose when Shopify marks it fulfilled
• Custom if/then rules that set a status when the order matches product title, SKU, tags, and similar fields — only while it is still on your first status. If that next status emails the customer, the email goes out
• Custom rules that move an order after it has stayed in one status for a set number of hours or days. If that next status emails the customer, the email goes out

Status Actions are separate. They cover Proof Review, Request Information, and Collect Info—including moving the order after the customer responds, when you configured that outcome.

Status customer emails and proof or information-request mail are configured on the status and templates, not in a general automation builder.

Existing users: Using automations.