shopify sidekick order-management refunds fulfillment

How to Handle Orders, Refunds & Fulfillment with Shopify Sidekick

Use Sidekick to pull a customer's full order history, process refunds and exchanges with a drafted reply, run bulk order edits safely, and build a native backorder system with Flow and ShopifyQL.

5 min read SidekickSkills View as Markdown

Shopify Sidekick can pull a customer’s entire order history in one query, walk a refund or exchange through to a drafted customer reply, design a repeatable bulk-edit workflow for high order volume, and build a backorder system out of Shopify Flow and ShopifyQL. What it won’t do is send customer emails for you or approve a refund on your behalf — those stay under your hand, deliberately.

Here’s the order of operations that actually works.

Step 1: Get the full customer picture before you reply

The most common support mistake is answering an order question without knowing who you’re talking to. Before touching a refund, ask Sidekick for a complete history on [CUSTOMER EMAIL OR NAME]:

  • Every order they’ve placed — order number, date, total, current fulfillment and payment status
  • Lifetime totals: order count, total spent, average order value
  • A flag on anything unfulfilled, on hold, or carrying an open refund or dispute
  • Tags applied across their orders (VIP, Fraud-Review, Returning-Customer) so you see how they’ve been categorised
  • Existing order notes, so you have prior context before you write a word

Finish the request by asking for a one-line summary you can paste straight into a support ticket or CRM note — something like “5 orders since [DATE], $[TOTAL] lifetime, no open issues, last order delivered [DATE].” That single line changes how you handle the conversation. A first-time buyer with a damaged package and a five-year customer with the same complaint are not the same ticket.

Step 2: Work the order issue and the reply together

Refunds go wrong when the action and the communication are handled separately — the money moves and the customer hears nothing for two days. Run them as one request.

Give Sidekick the situation in plain terms (wrong item received, package damaged, size exchange, refund requested after the return window) plus the order specifics: order number, customer name, order date, products, and total. Then ask for four things:

  1. The action itself — full refund, partial refund of [AMOUNT], exchange, or reshipment. Be explicit; don’t let it choose.
  2. A drafted customer reply that acknowledges the issue with empathy, states what you’re doing, gives a resolution timeline, includes return shipping instructions where relevant, and adds a goodwill gesture (a discount code or free shipping next order) if you decide the situation warrants one.
  3. Any inventory adjustment the resolution implies — a returned item coming back into stock, a reshipment pulling another unit out.
  4. A recurring-issue flag — is this the same complaint you’ve seen before on this product?

That fourth item is the one people skip, and it’s where the real value hides. Three separate “damaged in transit” refunds on the same SKU is a packaging problem, not three unlucky customers.

Step 3: Standardise your bulk order edits

Once volume climbs, the per-order approach breaks down. Ask Sidekick to build you a documented bulk-editing workflow around your actual numbers — store name, average daily order volume, the edits you repeat most, and how many staff touch orders.

A complete workflow covers:

  • Selecting orders with Shopify admin filters — date range, fulfillment status, payment status, or tag
  • Bulk tagging, e.g. tagging every unfulfilled order from the past week as “Priority”
  • Bulk note updates, like adding a warehouse note to all orders shipping from one location
  • Bulk shipping edits when a carrier or rate changes
  • Bulk archiving of orders fulfilled and delivered more than 30 days ago
  • Bulk cancellation for orders flagged as fraud or test orders
  • Shopify Flow automation for the edits you repeat weekly

Two additions make this safe rather than fast-and-scary. First, ask for a pre-and-post checklist your staff follow every time, plus a backup step — export the matching orders before you change them. Second, ask for a tag naming convention so three staff members don’t invent priority, Priority, and PRIORITY in the same week. Bulk operations amplify small inconsistencies into permanent mess.

Step 4: Build a backorder system that stays native

Backorders are where fulfillment quietly falls apart: an order sits at zero inventory, nobody tags it, and when stock lands it ships to whoever shouted loudest instead of whoever waited longest.

Sidekick can build the whole loop inside Shopify:

  • Flow one, on Order created: if the order contains [PRODUCT/SKU] and that variant’s available inventory is 0 at order time, tag the order [BACKORDER TAG] and add a note recording the order date and estimated restock.
  • Flow two, on Product variant inventory quantity changed: when that SKU goes from 0 to a positive number, find all orders tagged [BACKORDER TAG] containing the variant, sort oldest-first, and re-tag them [READY-TO-FULFILL TAG] up to the newly available quantity. Chronological fairness, enforced automatically.
  • A ShopifyQL report showing current backorder count, total revenue on hold, and the creation date of your oldest still-tagged order. Save it as a reusable skill so “how many backorders do we have right now” is a question, not a project.

Keep the scope honest here. This system covers orders, tags, Flow, and reporting. Customer-facing backorder email sequences, a published backorder policy page, and a self-service cancellation portal all sit outside it — they need a Shopify Email or Messaging campaign build, or a dedicated app, and should be scoped as their own piece of work.

What stays yours

Sidekick removes the clicking: pulling histories, drafting replies, structuring the workflow, wiring the Flows. It does not decide whether a customer past the return window deserves an exception, how large a goodwill gesture should be, or when a repeat product complaint becomes a supplier conversation. Those judgment calls are the job. Everything around them is now a prompt.

Frequently asked questions

Can Sidekick issue a refund for me?

You can ask Sidekick to process the refund action on a specific order and draft the customer reply that goes with it, but treat the money movement as the step you confirm personally. Give it the order number, the exact action (full refund, partial refund of a stated amount, exchange, or reshipment), and review what it proposes before anything is committed. A refund is not a step to approve on autopilot.

Does Sidekick send the customer email automatically?

No — it drafts. The order-issue workflow produces a reply that acknowledges the problem, explains the action you’re taking, gives a resolution timeline, and adds return shipping instructions or a goodwill offer if you asked for one. You still read it, edit the tone to match your brand, and send it from your own support tool.

Can Sidekick bulk-edit hundreds of orders at once?

It can build the workflow for bulk edits — filtering orders by date range, fulfillment status, payment status, or tag, then bulk-adding tags, updating notes, adjusting shipping info, archiving old fulfilled orders, or cancelling flagged ones. Ask it for a preview of exactly which orders match your filter and how many, plus a pre-flight checklist, before anything is applied. Export the matching orders first so you have a rollback reference.

Can Sidekick build a backorder system without a third-party app?

Yes, within limits. It can build two Shopify Flows — one that tags an order as a backorder when the variant is at zero inventory, one that re-tags the oldest backorders as ready-to-fulfill when stock returns — plus a ShopifyQL report for live backorder counts and revenue on hold. What it won’t cover natively is customer-facing backorder email sequences, a policy page, or a self-service cancellation portal; those need a campaign build or a dedicated app.

Will Sidekick tell me if a product keeps causing refunds?

Only if you ask. Add a line to your order-issue prompt asking it to flag whether the same issue has come up before with that product, so a pattern shows up as a product problem rather than as a stack of one-off refunds.