Automate with Shopify Flow

Orderkraft sends production events to Shopify Flow as triggers. A manufacturing order gets created, started, put on hold, cancelled, or completed, and Flow picks it up and runs whatever you built around it. Tag the order, email the customer, post to Slack, hand off to another app.

That’s how Orderkraft reaches the rest of your stack. No integration to build, nothing to maintain.

Finding the triggers

Install Orderkraft, open Shopify Flow, create a workflow, and the triggers are there under Orderkraft in the trigger picker. There’s nothing to switch on in Orderkraft itself.

Seven of them exist today. The trigger reference covers each one and the data it carries.

Only made-to-order production fires triggers

Every trigger carries a customer’s order with it. Manufacturing orders you create to build stock ahead of time have no order behind them, so they never fire anything. If your workflow stays quiet during testing, that’s the first thing to check: is the manufacturing order you’re testing with actually linked to a sales line?

Triggers only fire when something is listening

Orderkraft only sends an event when a live Flow workflow uses that trigger. Shopify tells Orderkraft which triggers are in use and Orderkraft skips the rest, which keeps it from making calls nobody reads.

Switch a workflow off and the events stop. Switch it back on and they resume from that moment. Nothing gets held in a queue in the meantime, so production that happened while the workflow was off won’t be replayed. If you’re changing a workflow that matters, do it during a quiet hour.

Delivery and retries

Events go out in the background, usually within seconds of the status change. If Shopify is unreachable or rejects the call, Orderkraft keeps retrying every hour for up to a year. A Shopify outage delays your workflow rather than losing the event.

Delivery isn’t ordered, though. A manufacturing order that goes from started to completed in the space of a minute can reach Flow the wrong way round. Read the status off the payload rather than assuming events arrive in sequence.

What merchants build with it

Tagging the Shopify order when production starts is the common first one, so support can answer “where is my order” without opening Orderkraft. After that it’s usually customer notifications, which is where the choice of trigger starts to matter: sales order manufacturing completed sends one message per order, while the per-manufacturing-order triggers send one per item.

The other one worth setting up early is a Slack alert on manufacturing order on hold. Held orders are the ones that quietly rot, and an alert gets someone chasing the missing material the same day.

What’s next

The Flow trigger reference has the exact firing conditions and payload for each trigger.