Shopify back office automation: orders, refunds, stock, books

Shopify back office automation means letting software handle the repeat work behind the storefront: tagging orders, handling refunds, watching stock and getting sales into the accounting system. The short answer: use Shopify Flow for rules that live inside Shopify, use Make or Zapier to move data to other apps, and build a custom app only when those become fragile or costly.

This guide covers the common back-office flows, which tool fits each one, what to watch out for, and when a custom app is worth building.

Start with the process, not the tool

Before you build anything, write down how the task works today. Who does it, what triggers it, what the rules are and what goes wrong. If a task is done three different ways by three people, pick one way first. Our guides on process mapping and what to automate first cover this step.

For Shopify stores, the best first candidates are usually tasks that are frequent, rule-based and hit money: order-to-accounting sync, refund handling, and low-stock alerts.

The tool options

You have three levels of tooling. Use the lightest one that does the job.

Shopify Flow

Shopify Flow is a free app on the Basic, Grow, Advanced and Plus plans. Workflows are built from triggers, conditions and actions. Usage limits depend on your plan and follow Shopify’s API rate limits. The Send HTTP request action is available on Grow, Advanced and Plus, and tasks from custom partner apps are Plus only (see the Flow limitations page).

Triggers that matter for back office work include (see the trigger reference):

• Order created, Order paid, Order fulfilled and Order canceled
• Refund created
• Product variant inventory quantity changed, Product variant out of stock and Product variant back in stock
• Scheduled time, for jobs that run on a timer

Useful actions in the action reference include Send internal email, Add order tags, Cancel order, Mark order as paid, Hold fulfillment order, Run code and Send HTTP request.

Two actions go beyond the built-in list:

• Send HTTP request calls an outside service. Flow waits up to 30 seconds for a reply. For some error codes you choose whether it retries for up to 24 hours, fails the run or ignores the error.
• Send Admin API request sends a GraphQL mutation to your store, for changes that have no action of their own. It does not support queries, asynchronous mutations or some app-specific mutations. The staff member who turns the workflow on needs permission for the data it changes.

As of 12 November 2026, the action list has no action to issue a refund or to adjust inventory. Whether a mutation for either can be sent through Send Admin API request depends on the rules above, so test it in a development store before you design around it. Check the current lists first, because Shopify adds actions often.

Make and Zapier

Make and Zapier connect Shopify to other apps. Both can start a run when something happens in your store.

• Zapier lists triggers such as New Order, New Paid Order, New Refund and Updated Inventory, and actions such as Create Order, Update Inventory Quantity, Mark Order as Paid and Create Fulfillment (see the Zapier Shopify page). It has a New Refund trigger but no action to create a refund.
• Make lists triggers such as Watch orders and Watch products, modules to get, create and update orders, an Adjust an inventory level module, and a Make a GraphQL API call module (see Make’s Shopify app page). It lists no refund module.

How they charge differs. Zapier counts tasks: a task is a successfully completed action, and triggers and built-in tools such as Filter do not count. Its free plan includes 100 tasks a month. Make counts credits: most module actions use one credit, and its free plan includes 1,000 credits a month. A flow that updates several line items can use many tasks or credits per order, so multiply by your daily volume before you choose a plan.

Check each tool’s current Shopify modules and limits before you commit, as both change often.

Which tool for which job

Flow 1: Orders

What people want: route orders by rule, flag risky ones, and keep the warehouse and finance informed.

Common rules:

1. When an order is created, add a tag based on shipping country, shipping method or total.
2. Tag orders that contain a pre-order or a custom item, so the team handles them differently.
3. Review orders that Shopify marks as risky before they ship. Flow has an Order risk analyzed trigger for this. It fires once Shopify’s own fraud analysis is finished, so it does not run the moment an order is created, and it covers Shopify’s assessments only, not third-party ones.
4. Send an internal email when an order needs a manual step, such as a large order or a missing phone number.

Pick the trigger that matches the moment you need. Check the trigger reference for exactly when each one fires, and use Order paid for anything that should only happen on a paid order.

Start with tags and notifications. They are low risk and make the daily queue easier to read. Keep the actual shipping decision with a person until the rules have run correctly for a few weeks.

Flow 2: Refunds and returns

Refunds move money, so design them carefully.

Facts from Shopify’s refund documentation that affect automation:

• A refund started from the admin cannot be canceled or reversed.
• The Restock items option is selected by default for items with tracked inventory.
• You can refund to the original payment method, store credit, or both, but some methods cannot be refunded to the original source.

Because of this, a safe pattern is to automate the work around the refund, not the refund itself:

1. A customer asks for a refund. A form or the helpdesk creates a ticket with the order number and reason.
2. A rule checks the order against your policy (age, product type, amount) and adds a tag such as “refund-eligible” or “needs review”.
3. A person approves in one click.
4. After the refund, the Refund created trigger starts a flow that logs the amount and reason to your finance sheet, tags the order and notifies the customer.

That gives you speed, a trail and a human check. If you want full automation later, start with small amounts only and add a daily report of everything refunded.

Flow 3: Stock and inventory

What people want: know before something runs out, and keep systems in agreement.

Typical flows:

• When a variant goes out of stock or its quantity drops, send an alert or create a purchase task. Flow has triggers for quantity changed, out of stock and back in stock.
• When a supplier sends a stock file, update quantities through an integration, not by hand.
• When a product is back in stock, notify the team or republish it.

Pitfalls to design for:

• Two systems, two truths. If stock also lives in a warehouse system or marketplace, pick one master and push changes one way.
• Timing. Updates that arrive late can oversell an item. Decide how often to sync and what happens if a sync fails.
• Bundles and variants. Rules that work for single products often break for bundles. Test with the messiest product you sell.

Flow 4: Invoices and accounting sync

What people want: every sale, refund, fee and payout shows up correctly in the books without re-typing.

Options:

• An accounting connector app from the Shopify App Store, if its rules fit your tax, currency and fee setup.
• Make or Zapier, when you need control over how orders become invoices or journals.
• A custom integration, when you have complex tax rules, several markets or special invoice formats.

Decide these points before you build:

1. What is the unit? One invoice per order, or one summary per day or payout? Daily or per-payout summaries are often easier to match to bank deposits.
2. How do refunds appear? Usually as credit notes against the original sale, with the same tax treatment. Confirm this with your accountant.
3. Where do fees go? Payment fees and shipping costs need their own accounts.
4. What about tax and currency? Test with an EU order, a UK order and a US order if you sell in all three.
5. Who reviews exceptions? Some orders will fail to sync. Someone must see the list.

Always run the first few weeks with an accountant reviewing the output.

Pitfalls that catch most teams

• No error handling. A failed run that nobody sees is worse than manual work. Send failures to an email or chat channel.
• Duplicates. If a trigger fires twice, you can create two invoices or two shipments. Check for an existing record before you create one.
• Hidden limits. Plans have caps on runs, tasks or operations. Check them against your order volume, including peak days.
• Permissions. Connectors need access to orders and customer data. Give each the minimum it needs and remove old ones.
• Changing rules. If a shipping rule or tax rule changes, the automation must change too. Document each flow and name an owner. See how to write an SOP for a format.
• Testing on live orders. Use a development store or test orders where possible, and start with read-only or notify-only steps.

When a custom app is worth it

Off-the-shelf tools handle most small stores. Consider a custom app or internal tool when:

• the same flow touches Shopify and two or more other systems,
• the rules are complex enough that you keep working around the connector,
• you need a screen for the team, such as an exceptions queue or an approval page,
• run costs on connector tools grow faster than the value they give,
• or you need something Flow and the connectors do not offer, such as checkout customization.

Check this against your volume and the hours spent on workarounds. If a connector flow does the job, keep it. A custom build earns its cost when it replaces several fragile steps with one maintained system.

Our Shopify service covers custom apps and integrations, and our automation and software service covers wider back-office tooling.

Common questions

Is Shopify Flow free? Yes. It is a free app on the Basic, Grow, Advanced and Plus plans. Some actions, such as Send HTTP request, need Grow or higher.

Can Shopify Flow issue refunds? The action list has no refund action. You can react to a refund with the Refund created trigger. Refunds started in the admin cannot be reversed, so keep a person approving them.

Zapier or Make for Shopify? Both can read orders and update stock. Compare your daily order volume with each tool’s task or credit pricing, and pilot one flow in each if the choice is close.

Can a store be fully automated? The repeat, rule-based work can be. Decisions about money, exceptions and key customers should keep a human check.

Key takeaways

• Write down the process and its rules before you pick a tool.
• Shopify Flow is free on Basic, Grow, Advanced and Plus plans and suits rules that live in Shopify. Some actions need a higher plan.
• Make and Zapier suit moving data between Shopify and other apps.
• Automate around refunds, not the refund itself, because refunds cannot be reversed.
• Pick one master for stock and decide how invoices and refunds map to your books.
• Add error alerts, duplicate checks and an owner to every flow.
• Build a custom app only when connectors become fragile or costly.

If you want help deciding which of these flows to set up first, we offer a free audit.