← back

JUL 2, 2026 · 3 MIN READ

Replacing an entire back office with one Worker

Orders that confirm themselves, a Notion office the client already knows how to use, and a daily report that writes itself.

ZY.John Mark Luder
Automated commerce architecture diagram

Most small stores don't need more people — they need fewer repeated decisions. Every order used to mean the same ritual: check the payment, message the customer, update a spreadsheet, tell the boss. That ritual is exactly what a full-time assistant spends the whole month performing.

Zylux Commerce OS replaces the ritual with one Cloudflare Worker on the edge. The storefront takes the order and the Worker does the rest: it re-prices everything server-side (clients lie, servers don't), decrements stock atomically so overselling is impossible, and writes the order into D1 — the single source of truth.

Then the fan-out begins. The order appears in a Notion office the client already knows how to use. A Discord alert pings the owner with the customer's details and a map pin. When the owner taps Confirm, Ship, Deliver, or Cancel — from the admin terminal or straight from Notion — the customer gets an email automatically, the tracker updates, and the change is logged for the daily report.

At midnight the system files its own report: sales, revenue, confirmations, deliveries, cancellations. Nothing is "reset" — every number is a date-scoped query, so history is free and forever.

The whole thing runs on 66 automated tests and costs next to nothing to operate. The back office didn't get cheaper — it stopped existing.

see the live store ↗ want one? email ↗