We run online stores, and we write the software we run them on.
We sell online to customers in a number of countries.
Most of our working day happens in Commerce Workbench, an operations system we built for ourselves.
Workbench9:00 AM, team chat
Morning brief, Tuesday
- Store A: 14 orders yesterday, $2,310. Up 6% on the week before.
- Store B: Merchant Center flagged the account. The appeal checklist is ready for review.
- UK checkout: 17 people started last week, 1 paid. Shipping rates need a look.
- Yesterday's 3 approved product fixes were written to the store. Google has confirmed 2 of them.
- 2 new ad suggestions are waiting for approval.
Commerce Workbench
We started building it because the numbers we needed each morning lived in a dozen places: the store admin, Google Ads, Merchant Center, Analytics, Search Console. The workbench reads all of them for every store we run, keeps a running list of what is broken, and lets an AI assistant draft the fix. Nothing changes until one of us approves it.
What it reads, and why
| Source | What we use it for |
|---|---|
| Shopify, SHOPLINE and other store platforms | Products, orders, refunds and stock, in each store's own currency and time zone |
| Google Merchant Center | Which products Google won't show and why, account-level warnings, and custom labels for shopping campaigns |
| Google Ads | Spend, search terms that cost money without selling anything, campaigns that stopped serving |
| Google Analytics 4 | Where visitors come from and where they leave between the product page and payment |
| Google Search Console and Bing Webmaster Tools | What people search for, which pages rank, and pages that drop out of the index |
| Boards and pins |
How a change gets made
- A ticket opens. For example, Google stops showing a product because its main image is too small.
- Someone drafts the fix. Either an AI assistant (we use Claude) or one of us, with the evidence attached.
- A reviewer decides. Approved changes are written to the store or to Merchant Center; rejected ones go back with a note.
- The source confirms it. The ticket closes when Google or the store reports the fix, not when someone says it is done.
Ground rules
- It reads by default. Write access is turned on per store, per job.
- Every change has a named approver and stays in the audit log.
- Store and advertising credentials are encrypted and stay on our servers.
- When data is missing it says so. A gap is never shown as a zero.
It runs our own stores today. If you sell online and want to compare notes, write to us at admin@everevive.com.