AI AUTOMATION · RELAY MODULES | breadcrumb: Home > Learn > AI automation > Our automation models
How to automate ecommerce operations: 10 Relay Modules and where each stops
To automate ecommerce operations, list the work that repeats, give each kind of data one home and automate in order: rules first, AI drafts second, connections across systems last. A person keeps approving prices outside your limits, large refunds and anything sent to a marketplace. This page gives the steps, the operations worth automating and the ten Relay Modules we build this way.
Quick answer
To automate ecommerce operations safely, take one workflow area at a time, build it in your own accounts and write its limits down. Relay Modules are the fixed-scope builds Ecom Relays makes this way: profit and cash reporting, margin alerts, stock sync, landed cost, account health checks, order-status updates, returns, 3PL invoice checks, catalog data and channel launches. Each has a written spec, a named owner, a log and approval points. Standard builds are $750; advanced $1,500 to $3,500.
This page is part of our free AI automation guide, which follows the path from first automations to governance.
How do you automate ecommerce operations, step by step?
Start with one week of evidence, not a tool. These seven steps work for a one-channel store and for a $10M brand; only the number of systems changes.
- 01List the repeat work.
For one normal week, write down every task done more than twice, how often it happens and how long it takes. Weekly hours = times a week x minutes each / 60. Module 02 has a template.
- 02Score each task.
Daily tasks with a rule you can write in one sentence, that can be undone and that use data you trust go first. Anything that "depends" stays manual for now.
- 03Give each kind of data one home.
Stock, product data, orders, costs and policies each get one system of record that every other tool reads from. Module 03 explains how.
- 04Automate rules first.
Tags, alerts, shipping notifications and scheduled summaries need no AI and are easy to check. Module 04 shows the patterns.
- 05Add AI where the work is language,
such as support replies and listing drafts, with a person reviewing the drafts until they are consistently right.
- 06Connect the systems
once work crosses channels, a 3PL and a helpdesk: one put-away stock number to every channel, tracking back to each order, invoices matched to receipts. Module 06 covers this.
- 07Write the limits and measure.
Every workflow gets a named owner, a log, approval points and one number measured before and four weeks after the change.
If you sell on one channel, steps 1 to 4 are most of the job, and the five automations in the Start guide cover them. Relay Modules are for stores where the work crosses systems.
Which ecommerce operations should you automate?
Most of the daily work in a store can be automated in part. The line that matters is where the automation stops and a person decides.
| Operation | Automate | Keep with a person | Measure |
|---|---|---|---|
| Order processing | Tag orders by value, channel or risk; route to the right warehouse; hold high-risk orders for review | Canceling orders; fraud decisions | Errors per 100 orders |
| Inventory and purchasing | One stock count across channels; reorder alerts; purchase order drafts | Approving every PO and supplier commitment | Stockout days on top SKUs |
| Shipping and fulfillment | Tracking to the customer and the channel; delay notices; label purchase for simple orders | Promises on late or lost orders | Orders shipped on time |
| Customer service | Order-status answers from live tracking; saved replies; ticket routing | Refunds above your limit; exceptions; upset customers | Order-status tickets per 100 orders |
| Returns and chargebacks | Return rules by reason; restock checks; dispute deadlines and evidence packs | Refunds outside policy; which disputes to fight | Disputes won as a share of disputes received |
| Pricing and margin | Margin per SKU after every fee; alerts below a floor; repricing inside a written band | Any price outside the band | SKUs below their margin floor |
| Finance and reporting | Daily numbers summary; payout tracking; 3PL invoice matching | What the numbers mean; what to dispute | Hours a week spent on reports |
| Catalog and listings | Data checks against each channel's rules; draft copy from your product data | Product claims; listing approvals | Listings suppressed or flagged |
| Account health | Daily checks of each marketplace's metrics; document vault; appeal drafts | Writing and submitting appeals and policy replies | Days from warning to action |
Shopify stores can run several of these rules in Shopify Flow, which is free on the Basic, Grow, Advanced and Plus plans and includes triggers such as "Order risk analyzed" and "Product variant inventory quantity changed" (Shopify Help Center, checked Oct 20, 2026). Amazon and Walmart rules usually live in your shipping software, your helpdesk or a connector that uses each marketplace's official API.
If you are buying rather than learning, the Relay Modules service page has the scope, prices and how to start for each module.
Our automation models: the 10 Relay Modules
A Relay Module is one workflow area from the table above, built in your own accounts to a written spec with the limits written in, and you keep it. Here is what each of the ten automates, the guardrail built into it and the decisions that stay with your team.
| Module | What it automates | Guardrail built in | What stays human | How we measure |
|---|---|---|---|---|
| RELAY-01 Profit and Cash Pulse | A daily owner dashboard: margin by SKU and channel after every fee, payouts held and when they land, cash tied up in stock, a 13-week cash forecast | Built only from source data (channel, payout, 3PL and cost records); every number shows its period and source | What the numbers mean and what to do about them | Hours a week spent assembling reports |
| RELAY-02 Margin Guard | Every fee, ad cost, shipping and landed cost per SKU; alerts and pricing-rule suggestions when a SKU falls below its margin floor | Suggests; never sets a live price outside your written band | Approving any price change outside the band; MAP and channel pricing decisions | SKUs below floor, and days below floor |
| RELAY-03 Stock Flow | One inventory truth across Amazon FBA, Walmart WFS, Shopify and the 3PL; reorder points, PO drafts and stockout alerts | Syncs from put-away stock only; stops and asks when systems disagree; buffers per channel | Approving every purchase order; supplier commitments | Stockout days on top SKUs; cancellation rate by channel |
| RELAY-04 Landed Cost Desk | Landed cost per SKU under current tariff rules, price scenarios and paperwork ready for your customs broker | Every tariff input dated and sourced; scenarios, not decisions | Customs filings (your broker); pricing decisions | Landed cost updated within a week of a rule change |
| RELAY-05 Account Health Watch | Daily Amazon and Walmart health checks, policy and pricing-rule checks, a compliance document vault and appeal preparation | Prepares; never submits to a marketplace | Writing, checking and submitting every appeal and policy reply | Days from warning to action (target: same business day) |
| RELAY-06 WISMO Breaker | Proactive shipping and delay updates, AI-assisted helpdesk replies to order-status questions and escalation rules | Answers from your written policy and live tracking only; refunds, exceptions and anything unclear go to a person | Refunds above your limit; promises outside policy; upset customers | Order-status tickets per 100 orders; first response time |
| RELAY-07 Returns Relay | Returns rules, exchange-first flows, restock status, chargeback evidence packs and reason-code reporting | Refunds automatic only below your set amount and inside policy | Refunds above the limit; fraud decisions; policy changes | Return reasons by SKU; chargebacks won and lost |
| RELAY-08 3PL Audit | Monthly invoice checks against orders, ASNs and inventory snapshots, stock reconciliation between 3PL and store and delivery-time monitoring | Flags mismatched lines; never disputes or pays on its own | Deciding what to dispute; supplier and 3PL conversations | Mismatched amount found and credited, per quarter |
| RELAY-09 Catalog Ready | Clean product data and feeds that meet title and pricing rules on each marketplace, in search and for AI shopping assistants | Drafts and checks; claims you cannot document are flagged, not published | Approving listing changes; product claims; brand voice | Attribute completion; listings suppressed or changed, days to fix |
| RELAY-10 Channel Launch | Adding a marketplace for a running brand: account approval support, catalog sync, fulfillment setup (FBA, WFS or 3PL) and launch pricing | Launch buffers on stock; pricing inside your floor | Choosing the channel; approving prices; submitting applications in your name | Cancellations on existing channels during launch; days to first order |
Where automation stops
Let AI do the busywork. Three actions always wait for a person:
- 01Price changes outside the limits you set.
A pricing mistake can sell your stock at a loss in minutes.
- 02Refunds above a set amount.
Small ones can be automatic. Big ones get a second look.
- 03Anything touching account health.
Appeals and policy replies are written and checked by people.
We add three more to every build: account appeals and reinstatement, policy decisions (what your store promises customers) and any situation nobody has written a rule for. Everything else: automate it, log it and review it every week.
Five guardrails sit under every workflow: limits on every action, approval for anything risky, only the access each tool needs, a log of every step and one person who owns the outcome. What your AI says, you said.
What does every module have in common?
-
Built in your accounts.
Every workflow, dashboard, SOP and report stays in your accounts and your name.
-
Written spec and acceptance tests.
You approve the spec before we build and the tests before you pay the second half.
-
A named owner on each side
and a log of every automated action you can read.
-
Approval points written in:
the actions in the guardrail box always wait for a person.
-
Access by role, never by password:
Amazon User Permissions, a limited Walmart role with Admin kept by you, Shopify collaborator access; no bank, payout or legal-entity permissions.
-
No outcome promises.
We commit to the build, the spec and the response standards. We do not promise sales, profit, rankings or approvals.
What do Relay Modules cost?
| Item | Price |
|---|---|
| Standard module (one workflow area, for example WISMO Breaker or Catalog Ready) | $750 |
| Advanced module (multi-system builds, for example Profit and Cash Pulse or Stock Flow; ERP, 3PL or WMS integrations scoped on a call) | $1,500 to $3,500 |
| RELAY-10 Channel Launch | Same as the Store Launch price for that channel, from $999 |
| Module Care (upkeep of modules we built) | Included on any monthly plan; otherwise 10% of the build cost a year |
| Payment | 50% at start, 50% at acceptance |
| Timing | 1 to 4 weeks per module |
| If it fails acceptance | Fixed free for 60 days |
Relay Module fees are fixed and published, never a percentage of sales or ad spend. Stock Flow and Margin Guard are included on Ops Desk Growth ($2,499 a month) and above. Prices exclude sales tax where it applies. Founding offer: 20% off the module build, plus 20% off monthly plans for the first 6 months, for our first 25 clients or until Jan 31, 2027, whichever comes first. Every price is also on Pricing.
How is a module built?
- 01Map the systems of record
for the data the module touches.
- 02Pick the workflow
with the most manual touches and write the rule, the limits and the approval points.
- 03Build with logging and alerts
in your accounts, using the tools in your stack where possible.
- 04Run in shadow mode
(drafts only) and compare with how your team does it today.
- 05Test against the written spec, hand over
the documentation and switch it on with you.
Which module should you start with?
Start where the most money or the most hours leak today. This table maps the symptoms we hear most to the module that addresses them first.
| If this sounds like your store | Start with |
|---|---|
| "We find out about margin problems at month end." | Margin Guard, then Profit and Cash Pulse |
| "We oversell, or run out of our best sellers." | Stock Flow |
| "Half our tickets ask where an order is." | WISMO Breaker |
| "Returns and chargebacks are handled case by case." | Returns Relay |
| "We pay the 3PL bill without checking it." | 3PL Audit |
| "Tariffs changed and we are not sure our prices still work." | Landed Cost Desk |
| "Account health warnings surprise us." | Account Health Watch |
| "Our listings are thin or keep getting flagged." | Catalog Ready |
| "We want to add Amazon or Walmart without breaking Shopify." | Channel Launch |
If more than three rows sound familiar, a single module is usually the wrong first step. The 14-Day Ops Foundation connects your channels and data, sets one stock count across them and writes the order routing rules and SOPs first, so each module after it is built on one source of truth.
What does a module build look like, start to finish?
Here is a WISMO Breaker build, step by step (illustrative example; your timings and figures will differ).
- 01Spec.
We count order-status tickets per 100 orders for two recent weeks, list the channels and the helpdesk, and write down what the replies may say: tracking, the carrier's latest scan, your written delay and lost-parcel policy. Refunds, reships and anything outside policy are written in as hand-offs to your team. You approve the spec before the build starts, and the first 50% is invoiced.
- 02Build.
Tracking updates and delay notices are switched on in each channel; the helpdesk is connected to order data; AI drafts are set to answer order-status questions only from live tracking and your policy.
- 03Shadow mode.
For the first period, AI replies are drafts that your team sends. We compare the drafts with what your team would have written and fix the rule where they differ.
- 04Acceptance.
The tests in the spec are run: the right reply on a delayed order, a hand-off on a refund request, a correct answer on a delivered order. When they pass, you sign off and the second 50% is invoiced.
- 05Measure.
Order-status tickets per 100 orders are counted again with the same method. If the module fails acceptance, we fix it free for 60 days.
The same five steps apply to every module. Only the systems and the hand-offs change.
Should you build it yourself or have it built?
Build it yourself when one person on your team has the time to write, test and check each workflow every week, and the work stays inside one or two systems. Module 04 and Module 06 teach the method. Have it built when the work crosses channels, a 3PL and a helpdesk, or when nobody has the hours to maintain it. A third option is a full-time automation and data analyst from our Dedicated Ops Team, who builds and maintains workflows for your business only, managed by us.
What we will not build
A store that runs itself. AI that sets prices, issues refunds above your limit or writes to a marketplace without a person. Review generation of any kind. Anything that needs your owner password. Software licenses we mark up.
A note on AI claims: the FTC has warned businesses not to exaggerate what their AI can do (FTC business guidance, "Keep your AI claims in check," Feb 27, 2023). We describe each tool from its own documentation, label vendor figures as vendor estimates and never say that AI will produce sales for you. AI here means software that drafts, sorts, checks and alerts. People still own the decisions.
Problems and fixes at this stage
Each module row above is a problem-to-solution pair. The same problems, in owners' own words with the cause and the number to watch, are on the Problems and fixes page.
Talk it through with a real person
Book a free 30-minute session with an ops lead. Bring one workflow you want off your plate, and we will tell you plainly whether to automate it, how and where it should stop. A real person replies within one business hour, 9am to 6pm US Central, Monday to Friday. No pitch deck.
A written report within 48 hours of working read-only access. You keep it whether or not you hire us.
Free
Ask a real expert. Free.
A real person replies within one business hour, 9am to 6pm US Central, Monday to Friday.
Request received.
That did not send.
You can reach an ops lead directly, and nothing you typed is lost.
How much does a Relay Module cost?
$750 for a standard module and $1,500 to $3,500 for an advanced, multi-system module. Channel Launch is priced as a Store Launch for that channel, from $999. Upkeep is included on any monthly plan, or 10% of the build cost a year.
What is Module Care?
Module Care is the upkeep of modules we built: fixing what drifts when a platform changes a rule, updating thresholds and keeping the documentation current. It is included on any monthly plan. Without a monthly plan, it is 10% of the build cost a year. If you prefer to maintain a module yourself, the handover documentation shows how.
Can you build on the tools we already pay for?
Usually, yes. We build with the tools in your stack where possible, subscribed in your name, so nothing depends on our accounts. If a module needs a tool you do not have, we say so in the spec, with its cost, before you approve anything.
Do you use AI in every module?
No. Most of each module is rules: syncs, checks, alerts and reports. AI is used where the work is language or classification, such as drafting order-status replies or checking listing data, always with the limits in the guardrail box. The spec for each module names where AI is used and what it may do, so you see it before you approve the build.
Who owns the modules if we stop working together?
You do. Every module is built in your accounts and documented. You receive a handover pack within 5 business days of the end date, and our access is removed within 24 hours. Nothing we build depends on our own accounts, so the modules keep running after we leave.
Can a module change prices or issue refunds on its own?
Only inside limits you write down: refunds below your set amount and inside policy, prices inside your floor and ceiling. Anything outside those limits waits for a person. Every module's spec lists these limits in writing, and you approve the spec before the build starts.
How long does a module take?
One to four weeks each, depending on the systems involved and how quickly access is granted. Advanced, multi-system builds take longer than standard ones. The written spec states the timing before you approve it, and slow access is the most common cause of delay.
Is this the same as "Amazon automation" stores?
No. Relay Modules automate work inside a store you own and run. We do not sell stores, and we never promise sales or income. Every module is a fixed-scope build with a written spec, in your accounts. Companies that sell a ready-made store with promised monthly profit are a different business, and the FTC has sued several of them. The Business models page explains the difference.
Sources6 sources
- 01help.shopify.comchecked Oct 20, 2026Primary
- 02help.shopify.comchecked Oct 20, 2026Primary
- 03help.shopify.comchecked Oct 20, 2026Primary
- 04help.shopify.comchecked Oct 20, 2026Primary
- 05marketplacelearn.walmart.comchecked Oct 20, 2026Primary
- 06ftc.govchecked Oct 20, 2026Primary
Free and ungated. No sign-up wall. Ecom Relays is not a course or coaching program. We do not sell stores and we never promise income.
Next step
Ask a real expert. Free.
A real person replies within one business hour, 9am to 6pm US Central, Monday to Friday.