What ecom tasks are worth automating (and what each costs to build)

Most "should we automate this" conversations run backwards. They start with what's annoying. They should start with what's expensive — and annoyance and expense are correlated far more weakly than anyone wants to admit.

This is the list I wish clients had before our first call: the ecommerce workflows where automation reliably pays back, what each costs to build properly, and — since a price list without the losing rows is just marketing — the ones where I'll tell you to keep doing it by hand.

One rule before the list. The math is always the same: hours per week × people × loaded hourly cost × 52, plus errors per month × cost per error × 12. That's the annual price of the manual workflow. If it doesn't clear the build cost inside a year or so, don't build. You can run your own numbers in two minutes with the ROI calculator — it will happily tell you not to hire me.

Worth automating, almost always

1. Inventory and order sync between systems

The classic: Shopify on one side, an ERP / 3PL / marketplace on the other, and a human in the middle re-typing or re-uploading CSVs. This is usually the most expensive workflow in the building because its errors compound — an oversell isn't a typo, it's a refund, a support thread, and a little reputational dent, multiplied by every channel.

The tell that it's time: anyone on your team saying the words "I do the stock reconciliation on Mondays."

Build cost, done properly: $8k–$25k depending on how hostile the second system is (modern REST API vs. an SFTP drop of fixed-width files vs. NetSuite). Pays back fastest of anything on this list — the typical mid-size store is burning $30k–$80k/yr here between labor and error costs.

2. Order routing and fulfillment handoffs

Splitting orders across warehouses, flagging fraud-scored orders for review, pushing the rest straight to the 3PL, handling address corrections before they become tickets. Rules a human applies from memory, forty times a day, with a miss rate that scales with how tired they are.

Build: $6k–$15k. The win is less the hours than the latency — orders that ship the same hour instead of the next morning quietly move your review scores.

3. Returns processing

Label generation, restock decisions, refund issuance under policy, customer notification. Every step is a lookup plus a rule. Merchants staff this like it's judgment work; ninety percent of it isn't. Automate the ninety, route the judgment calls to a human queue.

Build: $8k–$18k. Worth it above roughly 200 returns/month; below that, a tight manual process with a good macro set is honestly fine.

4. Finance reconciliation and month-end close

Matching processor payouts to orders to bank deposits, chasing the gaps, producing the spreadsheet your accountant actually wants. The 36-hour close case study on this site started as "two people, nine days, every month." That's not a workflow, that's a seasonal migration.

Build: $10k–$30k. The number that matters isn't the hours — it's that reconciled-to-the-cent books let you catch processor errors (they happen more than you'd think) while the dispute window is still open.

5. Price and competitor monitoring

Scraping competitor prices, stock status, and catalog changes into something your pricing decisions can actually use. Buying a SaaS for this works until your category or sites aren't covered; then you're in custom territory.

Build: $5k–$15k for a monitoring pipeline with real anti-bot handling and alerting. The build-vs-buy line: if an off-the-shelf tool covers your exact sites and fields, buy it. The moment you're exporting its CSVs to fix them in a spreadsheet, you've already decided to build — you're just paying twice during the transition.

6. Support deflection with actual resolution

Not a chatbot that apologizes in brand voice — an agent wired into your order system that can do things: track, modify addresses pre-shipment, trigger the returns flow, escalate with full context attached. The support automation case resolved 60% of tickets end-to-end, which is the only number that matters in this category.

Build: $12k–$40k depending on how many systems the agent needs write-access to and how much guardrailing your policies require. Worth it above ~1,500 tickets/month; below that, hire a good part-timer and revisit next year.

Worth automating, sometimes

7. Lead and wholesale-account enrichment

If you have a B2B/wholesale arm: enriching applications, scoring them, routing the good ones to a human with context. Pays when volume is real (hundreds/month). Below that, the enrichment engine pattern is overkill — a Zapier chain gets you 80% of it.

8. Catalog operations

Bulk product uploads, image processing, attribute normalization across channels. Hugely valuable for catalogs in the tens of thousands of SKUs; pointless below a thousand. The middle is genuinely case-by-case — this one's worth a diagnosis call rather than a rule of thumb.

9. Reporting pipelines

If decisions wait on someone assembling numbers every Monday, automate the assembly. But be honest about whether anyone acts on the report — automating a dashboard nobody reads just makes the ignoring more efficient.

Not worth automating (keep doing these by hand)

Anything you do less than weekly. The maintenance cost of automation is real and permanent; a monthly 2-hour task costs 24 hours a year, which will never pay back a build. Write a checklist instead.

Workflows still changing shape. If you've redesigned the process twice this quarter, automating it now means paying to rebuild in three months. Automation is for workflows that have stopped moving.

Judgment you'd want to keep even at scale. Supplier negotiations, make-or-break customer saves, anything where the 2% edge cases carry 80% of the value. Automate the paperwork around these, never the call itself.

How to read the price ranges

Every range above assumes built-properly: idempotent, monitored, alerting when the upstream API changes, documented, and owned by you — not a tangle of no-code triggers that dies silently on a Tuesday. That's what the $8k–40k on this site's FAQ buys. If a quote comes in dramatically under these ranges, you're usually buying the demo, not the system; the difference surfaces in month three.

And the honest benchmark stands: if the workflow doesn't waste at least the build cost per year, don't build. Run your numbers — the calculator does the arithmetic and gives you the verdict either way. If your number's big, you know where to find me.