Every e-commerce project we've seen puts most of its budget into the storefront: the theme, the checkout flow, the product pages. That's the part customers see, so it's the part that gets attention. Meanwhile, someone on the team is manually re-keying orders into a fulfillment system, checking inventory across two platforms by hand, and reconciling refunds in a spreadsheet at the end of the month. That back office is where the hours actually go once the store is live.
The recurring pattern
- Orders live in the storefront platform, fulfillment runs on a separate 3PL system, and nothing keeps them in sync automatically.
- Inventory drifts between channels: what's shown as in stock online isn't what's actually on the shelf.
- Refunds and returns get processed manually in the payment processor and never reflected back in inventory or accounting.
- Multi-channel sellers duplicate the same product data by hand across every marketplace they sell on.
None of this is glamorous work, which is exactly why it stays manual for so long. It's not a hard technical problem, it's a boring one, and boring problems get deprioritized until someone counts the actual hours a team spends on them each week.
Where to start
Inventory sync is almost always the highest-leverage first move, because it's the one that causes visible customer-facing damage when it's wrong: overselling something that's actually out of stock. After that, order-to-fulfillment automation removes the most manual re-keying per order. Refund reconciliation is lower volume but high annoyance, usually worth doing third.
It compounds
Unlike a lot of automation work, e-commerce back-office fixes compound with growth instead of just saving a fixed number of hours. A manual process that costs two hours a week at current volume costs twenty at ten times the volume. Automating it early means growth doesn't come with a proportional headcount cost attached.
Related reading
Approval workflows in Google Forms and Sheets, without an add-on
A request comes in, the right person approves it with one click, nobody has to chase, and there is a record. You can build that inside Google Workspace with a Form, a Sheet and Apps Script. Here is the design, and the five things that break once real volume arrives.
Google Form → Apps Script → Approver → Decision → Sheet
AI shopping agents can now buy from your store. Is your data ready?
In September Shopify switched checkout on for AI shopping agents. An agent does not see your homepage; it reads your product data and believes it. Here is what changed, where stores lose the sale, and the four checks to run before your first agent order.
Buyer asks → Agent → Product data → Checkout → Buyer approves → Your fulfilment
What changed in Google Workspace this September, and what it means for your automations
Workspace Studio flows can now run your own Apps Script steps and call webhooks, Sheets doubled its cell limit to 20 million, Apps Script data regions went GA, and Gemini connects to QuickBooks, HubSpot and Salesforce. A working read of 4 announcements.
Studio flows → Sheets → Apps Script → Gemini
Continues · Got a workflow like this?