Case Study

Case Study: E-commerce Brand Order & Support Automation

We built a connected set of automations for a direct-to-consumer brand selling on its own Shopify store and one marketplace: a customer profile and lifecycle flows in the CRM, WISMO replies from live tracking, returns checked against each market's rules, order exception and reorder alerts, and payout reconciliation into the accounting system. The support team now spends its time on real problems, and the founder sees margin by channel without waiting for month end.

Business type
Direct-to-consumer brand selling in the US, UK and EU
Team involved
Founder, operations manager, two support agents, bookkeeper
Systems connected
Shopify, a marketplace seller account, help desk, tracking platform, 3PL, Klaviyo, accounting software, n8n
Delivery
Scrum, 1-week sprints, about 8 weeks to full launch

The challenge

Where the practice started

Where-is-my-order questions filled most of the support inbox, and agents checked carrier sites one ticket at a time. During sales they fell days behind.

Returns were decided by whoever picked up the ticket, so the same request could get different answers, and customers in different countries were treated the same even though their rights differed.

Order problems were spotted in a morning scan or after a complaint, stock was reordered from a spreadsheet, and marketing emails reached customers who had open complaints.

Payouts from three providers were reconciled by hand at month end, so nobody knew true margin by channel until weeks later.

Goals

What the project had to change

  • Routine order status questions answered accurately without an agent.
  • Every return decided by the same written rules, with each market's rights respected.
  • Order problems and low stock found before customers notice.
  • Marketing flows that pause while a customer has an open issue.
  • Payouts reconciled continuously, with only mismatches left for the bookkeeper.

What we built

What we built, as one connected system.

01

Customer profile and lifecycle flows

We joined Shopify orders, help desk tickets and Klaviyo engagement into one profile, rebuilt the post-purchase and win-back flows around real purchase intervals, and paused marketing whenever a ticket was open.

Service details
02

WISMO replies

Tickets are matched to orders, tracking is read from the tracking platform, normal transit gets an automatic reply, and delayed or stuck parcels go to agents with the history attached.

Service details
03

Returns rules by market

Return requests are checked against the brand's policy and the market rules it approved for the US, UK and EU; eligible returns get a label and faulty items go to an agent.

Service details
04

Order exceptions and reordering

New orders are checked for address, payment and stock problems, 3PL dispatch timing is watched, and the buyer gets a daily reorder email with draft purchase orders.

Service details
05

Payout reconciliation

Payouts from Shopify Payments, PayPal and the marketplace are matched to orders and fees, draft entries go to the accounting system and mismatches go to the bookkeeper.

Service details

Architecture

How the brand's workflows connect

Shopify store Orders, stock Help desk Tickets Payments Payouts, fees n8n Five workflows AI and rules Intent, policies Klaviyo profile Segments, flows Tracking and 3PL Scans, dispatch Support and ops Queues, approvals Founder Refunds, POs Accounts Entries, reports
  • Input
  • Logic and services
  • AI step
  • Data
  • People

How it flows

  1. 1 Orders, tickets and payouts feed one n8n instance.
  2. 2 Five workflows update the customer profile, read tracking and 3PL status, and apply intent detection and the brand's rules.
  3. 3 Support and ops work clear queues; the founder approves refunds outside policy and purchase orders.
  4. 4 Reconciled entries reach the accounting system and every step is logged.

How it behaves

How the system behaves day to day

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

What customers see

  • A quick, accurate answer about their order
  • A delay notice before they need to chase
  • A clear returns decision and label
  • No discount emails while a complaint is open

What the team sees

  • A smaller support queue with facts already gathered
  • One exceptions board and one reorder email
  • A mismatch queue instead of month-end spreadsheets

What the automation does

  • Matches, checks, replies and prepares on schedule
  • Applies the brand's rules per market and per customer
  • Logs every action and alerts the ops manager on failures

Edge cases and fallbacks

Parcel shows delivered but customer disagrees
Always routed to an agent; never answered automatically.
Return just outside the window
Sent to an agent for a goodwill decision.
3PL stock disagrees with the store
Flagged for a stock check; nothing is adjusted automatically.
Chargeback appears in a later payout
Linked to the original order and held on the mismatch queue.
Store, help desk or n8n outage
Tickets fall back to the normal queue, nothing is refunded or posted from partial data, and the ops manager is alerted.

Integrations

What we connected

All integrations

Shopify

Store platform

Orders, products, inventory, fulfillments, returns and payouts.

Shopify Admin GraphQL API and webhooks, with only the access scopes each workflow needs.

Amazon Seller Central

Marketplace

Listings, orders and settlement reports.

Amazon Selling Partner API (Listings Items, Orders, Reports, Notifications), where your seller account grants access.

Klaviyo

Email and SMS marketing

Customer profiles, events and lifecycle flows.

Klaviyo REST API (profiles and events).

Gorgias

Help desk

WISMO replies, AI drafts, hand-offs and support-aware suppression.

Gorgias REST API.

AfterShip

Shipment tracking

Tracking events for WISMO replies and delay detection.

AfterShip Tracking API and webhooks.

ShipStation

Shipping

Orders, shipments, labels and dispatch status.

ShipStation API V1 (available on certain plans) and webhooks.

Xero

Accounting

Draft entries, bank transactions and purchase orders.

Xero Accounting API.

n8n

Automation platform

Runs every workflow, self-hosted or on n8n Cloud.

Your own n8n instance; we hand over every workflow.

How we delivered it

Week by week, one workflow at a time.

Each workflow went live on its own after a shadow run and a sprint demo, so the team got used to one change before the next.

Delivery timeline

Typical time to launch: about 8 weeks, then support

  1. 01

    Discovery

    Week 1

    We sat with support and ops, grouped a month of tickets, mapped returns and reorder steps, and agreed market rules and data flows with the founder.

  2. 02

    Design and access

    Week 2

    Reply templates and returns rules approved, segment definitions, entry structure agreed with the bookkeeper, API access and scopes granted.

  3. 03

    Sprint 1: WISMO

    Week 3

    Built WISMO replies and ran them as internal notes while agents compared; demo and sign-off.

  4. 04

    Sprint 2: returns

    Week 4

    WISMO went live for normal transit. Built the returns rules and label flow in suggest-only mode.

  5. 05

    Sprint 3: exceptions and stock

    Week 5

    Returns went live for change of mind. Built the exceptions board and reorder email.

  6. 06

    Sprint 4: CRM

    Week 6

    The board went live. Built the customer profile, suppression rules and rebuilt flows.

  7. 07

    Sprint 5: reconciliation

    Week 7

    Flows went live. Built payout matching and reconciled the previous month in parallel.

  8. 08

    UAT and handover

    Week 8

    The team ran acceptance testing on every workflow, then we switched everything on, handed over run books and trained the team.

  9. 09

    Support

    Ongoing

    Weekly check-ins during stabilisation and a peak-season review, then monthly care.

Who does what

What the team does, and what automation does.

Automation does

  • Answers routine order status questions from live tracking
  • Checks return requests against each market's rules and issues labels
  • Flags order exceptions and late shipments
  • Builds reorder suggestions and draft purchase orders
  • Pauses marketing for customers with open tickets
  • Matches payouts to orders and drafts accounting entries

The team does

  • Handle delayed, lost and disputed parcels
  • Decide faulty-goods returns and inspect returned items
  • Resolve exceptions with the 3PL and customers
  • Approve reconciliation entries and work the mismatch queue

Founder or ops lead decides

  • Approves refunds and goodwill outside policy
  • Approves purchase orders and supplier choices
  • Sets returns policy per market with legal input
  • Decides discounts and VIP treatment

Compliance handled

Privacy, consent and safety, built in.

Shipping delays in the US

Delay notices offer the choice to accept the delay or cancel, as the FTC Mail Order Rule requires, in wording the founder approved.

Source: www.ftc.gov

Returns in the EU and UK

Withdrawal windows of 14 days from delivery are encoded per market, with excluded items handled by an agent.

Source: europa.eu

Email marketing consent

Flows reach only subscribed customers, with unsubscribes honoured across tools well inside CAN-SPAM's 10 business days.

Source: www.ftc.gov

Bulk sender requirements

The sending domain has SPF, DKIM and DMARC and marketing mail carries one-click unsubscribe, as Gmail requires of bulk senders.

Source: support.google.com

Processor contracts

Every vendor handling customer data is under a processor agreement for UK and EU customers.

Source: gdpr-info.eu

No automated money decisions outside rules

Refunds outside policy, write-offs and fraud holds are always decided by a person.

Outcomes

What changed for the practice

  • Routine where-is-my-order questions are answered in minutes from live tracking, day or night.
  • Every return is decided by the same written rules, with each market's rights applied.
  • Order problems and low stock now surface in the morning list instead of in complaints.
  • Customers with open issues no longer receive marketing emails.
  • Payouts reconcile as they land, and the bookkeeper only handles mismatches.

What we track

The measures the practice watches.

WISMO automation

Share of order status tickets answered without an agent, and reopen rate.

Returns speed

Time from return request to refund, and returns handled without an agent.

Exceptions caught early

Exceptions found before a customer complaint, and orders shipped after the promised date.

Stock health

Stock-out days on top SKUs and purchase order approval time.

Retention

Repeat purchase rate and time to second order by first-order channel.

Close speed

Days to close the month and unresolved payout mismatches.

Cost estimate

What a project like this costs

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

    Ticket analysis, rules per market, data flows and the backlog.

    $1,000 – $2,000

  • WISMO module

    Order matching, tracking rules and replies.

    $700 – $1,700

  • Returns module

    Eligibility rules, labels and refund preparation.

    $800 – $2,000

  • Exceptions and reorder module

    Order checks, 3PL watch, reorder model and draft POs.

    $800 – $2,000

  • Reconciliation module

    Payout matching, entries and margin report.

    $500 – $1,300

  • CRM module

    Profile sync, segments, suppression and flows.

    $700 – $1,600

  • Integrations

    Store, marketplace, help desk, tracking, 3PL and accounting.

    $200 – $400

  • Testing, UAT and launch

    QA, acceptance testing, launch and training.

    $300 – $1,500

  • Total project estimate

    $5,000 – $12,500

Optional monthly care after launch is quoted with your proposal. Typical range for a project of this scope: five workflows at our fixed per-workflow range. Every brand gets its own fixed quote after a free call.

Monthly running costs you pay directly

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

  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • Help desk, Klaviyo and tracking platform: Each vendor's own plan.
  • Accounting software: The brand's existing QuickBooks Online or Xero plan.
  • AI usage: Pay-per-use model fees for intent detection, usually small relative to ticket volume.

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

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.

Free 20-minute call

Want this built for your e-commerce 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