An ecommerce operations studio
Checking orders and inventory. Copying numbers between tools. Reconciling payouts, refunds and fees. Answering the same support questions. We connect the routine work spread across Shopify, Amazon, advertising, support and finance so your team stops checking normal operations by hand: the routine runs on its own, and only the exceptions, failures and decisions that need a person reach you.
Book an Ecommerce Teardown See the operations workflow01
Seven jobs that repeat, and one person they all wait on.
One day6:00 AM
A typical day0decisions waiting on you
Support tickets
Forty tickets. Thirty five of them are the same four questions.
02
A reference workflow that reviews orders, spend and inventory on a schedule, and speaks only when a decision is yours.
The campaign has been delivering to nobody since Tuesday. You find out on Friday.
A reference architecture for an ecommerce team on Amazon and Shopify. On a schedule it reviews orders, inventory, spend and listings, separates a real problem from a reporting artifact, and speaks only when a person has to choose. Shown with synthetic data, not a live client account.
An integration that fails surfaces as an alert, not as silence.
Four sample outputs from the architecture, set as field reports.
Session data gap: all three SKUs showing n/a sessions. This clears as Amazon traffic reporting catches up, typically 24 to 48h post-listing activation. Not alarming yet; flag if still n/a tomorrow.
Two accessory SKUs show n/a days of runway because units sold is zero. This is a data gap, not confirmation of healthy stock.
Delivery check today is the single most important operational task.
A creative is queued for sign-off. Approve, or reject.
Nothing publishes until someone answers. Raised three times, and it has been waiting fifteen days.
Amazon's ad reporting is not a source of truth. Spend and sales figures get revised after the fact, attribution is dated to the ad click rather than the purchase, and the console deletes granular daily data after 60 to 90 days depending on the report.
When an account's numbers quietly stop updating, nothing errors. Every report still returns a figure — the same figure — and it can go unnoticed until someone looks. Weeks of recommendations can be made on data that has stopped moving.
So the architecture stores its own copy of the data on each run and says out loud when the numbers disagree with themselves.
Option B (benefit) balances brand voice with benefit-forward hooks. Default recommendation.
Option A (feature) leads with tangible product attributes. Strongest fit where features rank higher in conversion.
The system does not just produce options. It says which one, and why, per channel.
03
Reconciliation. Entirely rules, which is why it goes first.
A month of settlement lines, and your accountant is waiting on you to classify them.
Marketplace tax reporting is a monthly reconciliation nobody wants and everybody has to do. It is also entirely rules, which is what makes it the first thing worth handing over.
Recurring manual reconciliation every month, off the founder's desk and off the bookkeeper's invoice.
04
Your hours, your rate. The current cost of the manual work — not a saving.
The routine runs without you. The decisions still come to you.
Put in the hours your team spends on these now. This estimates what that manual work costs you today — nothing more. The teardown is where we work out which steps can actually be automated, and how much of the workload could realistically change.
05
An agent with no stated limits is a liability. These are the limits.
Nothing ships without you. That stays true, on purpose.
Four rungs. Everything we build sits on one of them, and you decide which.
Reads the account and says nothing unless something is worth saying. The daily memo lives here.
Names the option it would take and why, per channel, and waits. It does not act on its own recommendation.
Builds the thing and holds it. Creative is rendered, copy is written, the queue fills up. Nothing is published.
Only after a person answers. Approve or reject, by name, on the specific item. There is no rung above this one.
You do. The workflows, the prompts and the account configuration are yours, and they leave with you.
On your infrastructure and your accounts wherever the platform allows it, so nothing depends on us staying in the room.
An integration that fails surfaces as an alert, not as silence. The system is built to stop and say so rather than continue on stale data.
Documented, and walked through with whoever will hold it. If your team can't run it without us, it isn't finished.
Good fit
Not a fit
06
Three ways in. Fixed price, scoped before anyone starts.
One workflow you already know is costing time, scoped, built, and handed back running. The clear first step.
Live in 1 to 2 weeks after scope, access and data are ready
From$1,500
Operations run and maintained over time: a setup engagement, then a scoped monthly for monitoring, fixes and iteration.
Setup + scoped monthly
Larger, multi-system builds, scoped only after a pilot or teardown shows what is worth it. Not an off-the-shelf package.
Scoped after diagnosis
Fixed price, scoped up front. No retainer to start.
If your bottleneck isn’t one of these, the teardown still applies. Most builds start as something not on this page.
07
The same product, argued to a different person, on a different channel.
One product carries a dozen arguments. Making each by hand is where the queue backs up.
Creative is a queue in the operating layer like any other, and it backs up like any other. A batch is not a hundred versions of one ad: it is the same product argued to a different person, on a different channel, for a different reason.
We build a creative production system around the product, the brand and the audience. It generates, checks its own work against the real product, regenerates what fails, and keeps only what holds up: static and video, product shots and lifestyle scenes, across multiple hooks and angles. A person approves the final assets before anything ships.
Built as our own internal infrastructure, for repeatable, controlled production. Not a generator you point at a product and hope.
08
A studio of one who ships, not a roster you are assigned from.
A note from Shah
Every system on this page started as something I was doing by hand for a client, badly, at the wrong hour. The agent exists because I wanted the evening back. It turned out the founder wanted theirs back more.
You are not buying a platform, and you are not being assigned an account manager. Whoever scopes your build is the person who builds it, and the person who answers when it escalates.
Book an Ecommerce TeardownShah DurranFounder
How I work
A client asked for a deliverable I took the money for and then could not build the way it needed to be built. I credited it back rather than shipping something that would have technically satisfied the brief.
Another wanted to buy a tool I would have been paid to integrate. It would not have earned back what it cost them at their volume, so I said so, and we did not buy it.
When a client's numbers and my own database disagreed, I went and checked against the live platform instead of defending my figures. Mine were the ones that were stale.
None of those were good for the invoice. All three are why the same people keep coming back.
A free ecommerce teardown is one call. We map what is worth automating first, and what it would take. If nothing is worth it, we say so.