Ecommerce & Marketplace Automation
Shopify and Amazon,running like one business.
Growing brands rarely stall on demand. They stall on operations — the restock maths, the true-profit spreadsheet, the FBA claims nobody has time to file, the support inbox at 11pm. We automate that layer so your team runs the brand instead of reconciling it.
Plugs into the stack you already run
Restock
Sea Salt 200g — 11 days of cover left. Reorder 1,400 units today to land before the gap.
FBA claim
34 units from SHP-8821 never checked in. Claim pack drafted and ready to file.
Buy Box
Lost on 2 ASINs overnight — an unauthorised seller undercut by £1.40.
Ads
Blended ROAS 3.1× on true margin. Two Meta ad sets showing creative fatigue.
Support
84 tickets handled overnight, 6 escalated with full order context attached.
Shopify and Amazon in one operating picture
restock plan and true profit, without a spreadsheet
support cover on email, chat and Amazon messages
to your first automation running live
Sound familiar?
Every brand hits this wall at around £2M.
The systems that got you here — a good spreadsheet, a sharp ops person, and a lot of manual care — stop scaling at exactly the point the numbers get big enough to hurt.
The spreadsheet is the business
One file holds restock maths, margin, and forecasts. One person understands it. It breaks quietly, and you find out at the stockout.
You don't know what you actually made
Shopify says one number, Amazon settlements say another, ad spend sits in three dashboards. True profit by product is a month-end archaeology project.
Amazon quietly keeps your money
Units lost in transit, damaged in the warehouse, mis-measured for fees. Every seller is owed something. Almost nobody files for it.
Bestsellers go out of stock
Velocity changed three weeks ago, but the reorder point didn't. You lose the sale, the rank, and the momentum — then pay for air freight to catch up.
Support eats the team
Where is my order, can I change the address, I want a refund — the same eight questions, all day, across email, chat, and Amazon messages.
Ads are judged on the wrong number
Platform ROAS looks fine. Blended ROAS against real product margin tells a different story, and nobody has time to build that view weekly.
None of this is a people problem. It's a systems problem — and systems are fixable.
The shift
Same team. Very different week.
Nothing here is exotic. It's the ordinary operating rhythm of a brand at your size, moved off people and into systems.
How the week runs today
- Monday morning goes on rebuilding the restock sheet from two exports.
- Profit by product is guessed, or calculated properly once a quarter.
- FBA discrepancies get noticed months later, if at all.
- A lost Buy Box is discovered when sales dip.
- Two people spend their mornings answering WISMO emails.
- Supplier POs and ship dates live in one inbox and one memory.
How it runs once it's automated
- The restock plan is already in Slack at 08:00, with quantities per channel.
- True profit by product and channel lands every Monday, ad spend included.
- Every gap is caught within days and arrives as a ready-to-file claim pack.
- You get an alert the hour it happens, with the undercutting seller named.
- The routine 80% is answered from live order data; your team gets the hard 20%.
- POs go out automatically, replies are read, and delays surface before they bite.
Put a number on it
What is the manual layer costing you a year?
Three sliders. No email gate. Move them to roughly match your business and you'll get a defensible order of magnitude — the same three numbers we'd quantify properly in the audit.
These are industry mid-points, not a forecast for your business. The point isn't the exact figure — it's that the number is never small, and nobody has ever measured it. That's what the audit is for.
Rough annual value on the table
£63,672
Recovered cash and reclaimed payroll capacity, per year
- 801 hrs
- Hours handed back to the team
- £22,422
- Payroll value of those hours
- £37,500
- Revenue recoverable from stockouts
- £3,750
- Sitting in unfiled marketplace claims
At 70% of the manual hours removed — the share a first build usually reaches before judgement calls start.
Not a redundancy plan. It's the capacity you stop spending on reconciliation.
Assumes 3% of revenue lost to fast movers going out of stock, half of it preventable with earlier signals.
Lost and damaged FBA inventory that never gets reimbursed because nobody has time to file within the window.
What's included
Six layers of your operation, taken off people.
Most brands don't need all six. They need the two that are currently costing them the most, built properly.
Inventory & Restock Planning
Sales velocity from both channels, plus stock on hand and inbound POs, turned into a daily reorder and FBA restock plan — with a warning well before anything sells out.
Profit, Payouts & Claims
Shopify revenue, Amazon payouts, and ad spend combined into real profit by product and channel — plus a claim pack for every unit Amazon lost, damaged, or overcharged you for.
Customer Support Automation
An AI front line across email, chat, and Amazon messages: order status, WISMO, returns, and refunds answered from live order data, escalated to a human the moment it matters.
Ads & PPC Automation
Meta, Google, and Amazon Ads pulled into one blended-ROAS view, with rule-based budget moves, creative-fatigue alerts, and scale-or-kill flags on every campaign each morning.
Listing, Pricing & Account Health
Alerts on lost Buy Box, silent listing edits, unauthorised sellers, price gaps between channels, and any policy or account-health warning — each one with a drafted response attached.
Retention & Lifecycle Flows
Back-in-stock, low-stock, and replenishment emails timed to how fast each customer actually gets through the product, plus review requests that land after delivery, not before.
Under the bonnet
This is what one of them actually looks like.
Automation is an easy word to say and a hard thing to trust. So here are three of the twelve, opened up — every step, every system it touches, and the exact point where a human still has to say yes.
Money Amazon owes you, filed before the window closes
- Fires when
- New inventory adjustment or shipment discrepancy appears in Seller Central
- Cadence
- Runs daily, 06:00
- What lands
- A Slack digest of claimable value each morning, and a running log of what's been recovered.
- What it replaces
- A quarterly panic where someone exports four reports and gives up halfway.
Live in 3–5 weeks
- 1
Pull the ledger
Fetches inventory adjustments, shipment receipts and reimbursement reports from the Amazon SP-API since the last run.
- 2
Reconcile shipped vs. received
Matches every shipment line against what Amazon actually checked in, unit by unit, and flags the gaps.
- 3
Filter out the noise
Drops anything already reimbursed, already disputed, or outside the claim window. What's left is genuinely owed.
- 4
Value each claim
Prices the discrepancy at your landed cost, sorts by value, and drafts the case wording with the evidence attached.
- 5
You approve the queue
You approveEvery draft claim lands in one Slack message with the amounts. Approve all, or drop the ones you don't want filed. Nothing is submitted to Amazon without that click.
- 6
File and track
Submits the approved cases, logs case IDs to a sheet, and chases anything still unresolved after 14 days.
The architecture
Nothing gets ripped out. It sits on top.
We don't migrate you to a platform or ask you to adopt new software. We read from the systems you already pay for, do the thinking in between, and push the result to wherever your team already looks.
Reads from
Your accounts, your API keys, read access first
The layer we build
Hosted wherever you want it — your cloud or ours
Orchestration
Scheduled and event-driven workflows in n8n, versioned and documented.
Reasoning
Claude handles the judgement calls — classifying, drafting, summarising.
Rules & guardrails
Your thresholds, your policies, your tone. Explicit, readable, yours to change.
Human checkpoint
Anything touching money or the brand waits for a person to approve it.
Writes to
Where your team already works — no new dashboard to remember
If you already run something that works, we leave it alone. The goal is fewer moving parts, not more.
Week six onward
One Tuesday, with the systems running.
Nothing here needs a person to start it. This is the shape of a normal day once the first two or three automations are live.
- 02:41Automated
A customer in Sydney asks where their order is
Tracking is pulled, the reply is written and sent in eleven seconds. Nobody is awake. Nobody needs to be.
02:41AutomatedA customer in Sydney asks where their order is
Tracking is pulled, the reply is written and sent in eleven seconds. Nobody is awake. Nobody needs to be.
- 06:00Automated
Overnight Amazon adjustments reconciled
Four shipment discrepancies found, priced at £2,180, drafted as claims and queued for your approval.
06:00AutomatedOvernight Amazon adjustments reconciled
Four shipment discrepancies found, priced at £2,180, drafted as claims and queued for your approval.
- 07:00Automated
Stock cover recalculated across both channels
Two SKUs drop under the reorder threshold. Draft POs are prepared against the right supplier lead times.
07:00AutomatedStock cover recalculated across both channels
Two SKUs drop under the reorder threshold. Draft POs are prepared against the right supplier lead times.
- 08:00You
You read one Slack message
The brief: what needs reordering, what Amazon owes you, what ads did, where support landed. Ninety seconds, coffee in hand.
08:00YouYou read one Slack message
The brief: what needs reordering, what Amazon owes you, what ads did, where support landed. Ninety seconds, coffee in hand.
- 08:04You
You approve two things and change one
PO for the 200g goes out as drafted. You cut the second order in half because you know something the data doesn't. That's the whole job now.
08:04YouYou approve two things and change one
PO for the 200g goes out as drafted. You cut the second order in half because you know something the data doesn't. That's the whole job now.
- 11:20Automated
Buy Box lost on your best seller
Alert fires within minutes, not at the end of the week when someone notices the revenue dip.
11:20AutomatedBuy Box lost on your best seller
Alert fires within minutes, not at the end of the week when someone notices the revenue dip.
- 14:00You
Your ops person does actual ops
Supplier negotiation, a new 3PL quote, the packaging change. The work you hired them for, not the reconciliation.
14:00YouYour ops person does actual ops
Supplier negotiation, a new 3PL quote, the packaging change. The work you hired them for, not the reconciliation.
- 17:30Automated
Back-in-stock flow fires itself
The restocked SKU triggers Klaviyo to the waitlist automatically — the same day it lands, not three weeks later.
17:30AutomatedBack-in-stock flow fires itself
The restocked SKU triggers Klaviyo to the waitlist automatically — the same day it lands, not three weeks later.
- 18:00You
You close the laptop
No spreadsheet to update tonight. Tomorrow's brief is already being assembled.
18:00YouYou close the laptop
No spreadsheet to update tonight. Tomorrow's brief is already being assembled.
Blue is a decision only you can make. Everything else already happened.
How we get there
Six weeks from first call to something you actually trust.
No twelve-month transformation programme. We take one workflow, prove it on your own numbers, and only then talk about the next one.
The audit is free and useful on its own. You leave it with a quantified list of what's leaking — whether or not you build anything with us.
- 01Week 0 · free
Ops audit call
Ninety minutes with whoever actually runs the day: you, your ops lead, your Seller Central. We map where the hours and the leaks are, and we're blunt about which ones automation won't fix.
You get:A shortlist of the leaks worth closing, sized honestly
- 02Week 1
Map and prioritise
We put every candidate automation against two axes — money it protects or makes, and effort to build — then pick the one or two that pay back fastest. You approve the order before anything starts.
You get:A prioritised build plan with fixed scope and price
- 03Weeks 2–5
Build the first one
We connect to your real accounts through official APIs, build in the open, and show you working output every few days. You see the actual numbers it produces, not a demo on sample data.
You get:One automation running live on your own data
- 04Weeks 5–6
Prove it on your numbers
We run it alongside your current process and compare. If the restock plan disagrees with your gut, we find out which one was right before you trust it with a purchase order.
You get:A side-by-side that either earns your trust or gets fixed
- 05Ongoing
Expand and hand over
Next automation on the list, same rhythm. Everything runs in your accounts, documented, with the credentials in your name — so keeping us is a choice, not a dependency.
You get:Documentation, ownership, and a system that keeps growing
Ways to start
Three ways in. All of them reversible.
Start with the audit if you're not sure, or straight into a build if you already know what hurts. Nothing here locks you into a year.
Ops Audit
Find out what's actually leaking.
Best for: Brands who know something is wrong but not what to fix first.
- 90-minute working session with your ops team
- Review of Shopify, Seller Central, and ad accounts
- Every leak quantified in hours or pounds
- A prioritised shortlist you can act on with or without us
First Build
One automation, live, proving itself.
Best for: Brands who already know the problem and want it gone this quarter.
- One automation from the build menu, fixed scope and price
- Built on your live accounts, not a sandbox
- Side-by-side validation against your current process
- Documentation and full handover on day one
- 30 days of tuning after go-live
Ops Partner
We run the automation layer.
Best for: Brands building the full system out over a few quarters, without hiring for it.
- A rolling queue of builds, prioritised with you each month
- Monitoring and fixes when Amazon changes something
- Model, prompt, and rule tuning as the catalogue changes
- A monthly ops review with the numbers in front of you
- Cancel with 30 days' notice — everything stays yours
The alternatives
You have three options. Here's the honest comparison.
We're not the right answer for everyone. If your ops genuinely fit in one person's week, hire the person.
| An ops hire | A VA or freelancer | BoringOrca | |
|---|---|---|---|
| Time to useful | 2–3 months to hire and ramp | Fast, but capped at their hours | First automation live in weeks |
| Scales with order volume | No — more orders, more hours | No — you buy more hours | Yes — the work stops being manual |
| Works at 3am and on Boxing Day | No | No | Yes |
| Knowledge stays when people leave | Walks out the door | Walks out the door | Documented, in your accounts |
| Annual cost shape | Salary, NI, pension, holiday | Hourly, grows with volume | Fixed build, optional retainer |
| Judgement on the hard 20% | Strong — that's what people are for | Varies | Escalated to your team, with context |
No hostage-taking
The terms that make this a low-risk yes.
Handing your ops to an outside team is a real decision. These four things are how we make it a reversible one.
It runs in your accounts
Your Shopify, your Seller Central, your ad accounts, your API keys. We build inside your walls — nothing routes through a black box we control.
Fixed scope, fixed price
Every automation is quoted as a defined piece of work before it starts. No hourly meter, no scope creep invoice at the end of the month.
A human signs off what matters
Refunds, goodwill credits, listing changes, purchase orders — anything with money or your brand attached gets drafted by AI and approved by a person.
You can fire us cleanly
Code, workflows, credentials, and documentation are yours from day one. If you take it in-house next year, there is nothing to unpick and nothing to buy back.
Straight from us
Why we only take a few of these at a time.
Most agencies would rather sell you a retainer than a result. We'd rather build two things properly than eight things badly, so we cap how many builds run at once. It means we sometimes say no, and it means the work that does start actually ships.
We also don't think every problem needs AI. Half of what we build is boring plumbing — an API call, a rule, a scheduled job — and that's usually the half that saves the most money. If your problem is genuinely a spreadsheet formula, we'll tell you that on the audit call and you'll have lost ninety minutes.
The reason we ask for that call before quoting anything is simple: we've never seen two brands leak in the same place. Yours will have one thing costing far more than you think, and it's rarely the thing you'd have guessed.
Alee
Founder, BoringOrca
P.S. If you'd rather just see whether we're any good first — ask us on the call to walk through the FBA reconciliation build line by line. We'll show you the actual workflow.
Connects to what you already run
Proof
We've built this for ecommerce before.
Real problems, practical solutions, and measurable outcomes.
Questions we get asked first
What size brand is this actually for?
We build for Shopify and Amazon brands doing roughly £2M+ a year. Below that, the manual version usually still fits in one person's week. Above it, the spreadsheet holding your restock and profit numbers together becomes the single biggest risk in the business — and that's the problem we solve.
Do we have to replace our current tools?
No. We build on top of what you already run — Shopify, Seller Central, your 3PL, Klaviyo, your helpdesk, your ad accounts, and yes, your spreadsheets. Everything connects through official APIs, and your team keeps working in the tools they already know.
How do you stop AI from telling a customer something wrong?
Support agents answer from live order, shipping, and policy data rather than guessing, and every sensitive path — refunds, goodwill credits, anything about a damaged or missing order — routes to a human with a drafted reply. We tune it against your real ticket history before it ever touches a customer, then keep measuring after launch.
Where should we start?
Usually with restock planning or the combined P&L, because those two pay for themselves fastest and everything else builds on the same data. We'll take one workflow end to end, prove it on your numbers, then expand — not a twelve-month programme.
Who owns the automations you build?
You do. The workflows, the code, the credentials, and the documentation are all yours, running in your own accounts. If you ever want to take it in-house or hand it to someone else, there's nothing to unpick.
Let's find out what's actually leaking.Ninety minutes, no pitch. You keep the findings.
Reach out
Tell us about your project.
Whether you're automating a workflow or building something new, tell us what you need. We'll tell you honestly whether and how we can help.
We reply within a day
A real person reads your message and responds within one business day — no automated runaround.
A short discovery call
We dig into your goals and constraints to see if we're a good fit. No commitment, no hard sell.
A clear plan & quote
You get a concrete proposal with scoped milestones and predictable pricing — not a vague estimate.
Prefer email?
alee@boringorca.comFree ops auditNinety minutes. No pitch. You keep the findings.
Shopify + Amazon brands at £2M+Free ops audit for Shopify + Amazon brands at £2M+