Fixed quote after a free call

Shopify order status and returns automation for supplement brands

"Where is my order" is usually the biggest single ticket type for a supplement brand. We build a workflow that sends proactive shipping updates from ShipStation or AfterShip, answers order-status questions instantly with live tracking, alerts customers before they notice a delay, and routes returns and damaged or leaking deliveries with photos and lot numbers so quality can spot batch problems. A typical build costs $1,000 to $2,500 and takes about three to four weeks.

The problem

Why WISMO tickets swamp supplement support teams

Customers on a subscription expect the next pack before they run out, and when tracking stalls they write in, often more than once. Agents copy tracking numbers from Shopify into a carrier site and paste the answer back, all day.

Returns and damage claims hide quality signals. A crushed tub or a broken seal reported through three channels never reaches the person who would notice that the same lot keeps coming back, and some supplement returns cannot be resold at all.

What we build

What our Shopify order status automation includes

Proactive shipping updates

Shipped, out for delivery and delivered messages from carrier tracking events, branded and consistent.

Instant WISMO answers

Order-status questions by chat or email answered with live tracking and an honest estimate.

Delay alerts

Shipments with no scan for a set time trigger a message to the customer and a task for the team.

Returns and damage intake

A form that collects photos, order number and lot number, applies your return policy and creates the return or replacement for approval.

Batch signal to quality

Damage and complaint reports grouped by lot so the quality lead sees patterns early.

Weekly fulfilment report

Late shipments, carrier performance, return reasons and replacements by product.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Shipment event

    ShipStation or AfterShip reports a tracking update or a stalled shipment.

  2. 02 Automated

    Customer updated

    The customer gets a proactive update or delay notice.

  3. 03 Automated

    Questions answered

    Order-status questions get live tracking instantly; returns go through the intake form.

  4. 04 Team review

    Team approves returns

    Support approves replacements, refunds and carrier claims.

  5. 05 Regulatory lead or founder decides

    Quality decisions

    The quality lead decides on any batch investigation; possible adverse events go to the adverse event process.

How it behaves

How order updates and returns behave

What each person sees and what runs in the background, including what happens when something goes wrong.

What the customer sees

  • Shipped, out for delivery and delivered updates without asking
  • A heads-up if a parcel is delayed
  • A simple form for returns or damaged items

What the team sees

  • Fewer order-status tickets
  • Returns and claims ready to approve with photos
  • Damage reports grouped by lot

What the automation does

  • Listens to tracking events and order changes
  • Answers order-status questions with live data
  • Applies the return policy and routes every case

Edge cases and fallbacks

Tracking number missing
The order goes to the team instead of sending a broken link.
Parcel marked delivered but customer says it is not
Routed to support for a carrier claim or replacement decision.
Return mentions a reaction
Routed to the adverse event process first.
Carrier tracking feed outage
Messages pause and the team is alerted rather than sending stale status.

Architecture

Order status and returns automation at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
ShipStation Tracking events Shopify Orders n8n workflow Status and rules Updates Email and SMS Returns intake Photos, lot no. Support team Approvals Quality lead Batch patterns
  • Input
  • Logic and services
  • Output
  • People

How it flows

  1. 1 Orders from Shopify and tracking events from ShipStation or AfterShip feed the workflow.
  2. 2 Customers get proactive updates and delay notices; order-status questions are answered with live tracking.
  3. 3 Returns and damage reports come through an intake form with photos and lot numbers, for support to approve.
  4. 4 Reports are grouped by lot so the quality lead can spot batch problems early.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Order status (WISMO) & returns automation project plan

Typical time to launch: about 3 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Fulfilment setup, carriers, current WISMO volume, return policy and quality process.

  2. 02

    Design

    2 to 3 days

    Message set, delay thresholds, return rules, intake form and reports.

  3. 03

    Build

    About 1 week

    Tracking events, messages, WISMO answers, returns intake and lot grouping.

  4. 04

    Shadow run

    About 1 week

    Messages go to an internal list while real shipments are tracked.

  5. 05

    Launch

    1 to 2 days

    Switch on and train support on approvals.

  6. 06

    Support

    Ongoing

    Peak-season tuning, new carriers and policy changes.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Shopify Admin API and webhooks ShipStation API v2 tracking webhooks AfterShip Tracking API Loop Returns API Klaviyo or Twilio for messages

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Fulfilment map, message set, return rules and thresholds.

    $200 – $350

  • Build

    Tracking events, WISMO answers, delay alerts and returns intake.

    $500 – $1,100

  • Integrations

    Shopify, shipping, returns and messaging.

    $150 – $400

  • Testing and shadow run

    Internal-list run against live shipments.

    $100 – $250

  • Launch and training

    Support training and run book.

    $50 – $100

  • Total project estimate

    $1,000 – $2,200

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. ShipStation, AfterShip, Loop Returns and messaging are billed to you directly.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Shipping and returns apps: Your ShipStation, AfterShip or Loop Returns plans.
  • Messaging: Your Klaviyo plan, or Twilio at about $0.0083 per US message segment plus carrier fees (Twilio's published US pricing).
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: fair review and complaint handling

The FTC's rule on reviews bans suppressing negative reviews through threats or intimidation, so damage complaints are resolved on their merits and never tied to review removal.

Source: www.ftc.gov

US: complaints that may be adverse events

Returns and complaints that mention a reaction are routed to the adverse event process, since serious reports must reach FDA within 15 business days.

Source: www.fda.gov

UK: service messages vs marketing

Shipping updates are service messages; any promotional content added to them needs consent or the soft opt-in under PECR.

Source: www.legislation.gov.uk

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Order status (WISMO) & returns automation questions, answered.

WISMO stands for "where is my order", the most common ecommerce support question. Proactive updates and instant answers with live tracking cut those tickets without making customers wait for an agent.

Shopify's order status page shows tracking well. We add proactive messages, delay alerts before customers notice, instant answers in chat and email, and returns intake with lot numbers, which the status page alone does not cover.

ShipStation through its API v2 and tracking webhooks, AfterShip through its Tracking API, and Loop Returns through its API, plus your Shopify store.

So the quality lead can see whether damage or complaints cluster in one batch. It is a simple way to spot a packaging or supplier problem early.

That is a policy and quality decision for your team. Our workflow applies the return policy you set and routes each case for approval.

WISMO tickets per hundred orders, share of shipments with a delay alert, average resolution time for returns, replacements by product and damage reports by lot.

Free 20-minute call

Want this for your health & supplement brand?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call