01 / 04T+0s
Customer places order on Shopify
Shopify checkout completes; the storefront fires an `order.created` webhook to Good Ol' Studio's event bus. Inventory is decremented atomically.
Index
04Live· 2025· Operations Engineering
Exploring software for small-batch operations
Good Ol' Studio
The operational backbone of a real bakery — managing orders, dispatch, finance, and marketing through a single integrated dashboard that replaced four separate tools, with Shopify, Uber Direct, and Klaviyo coordinating automatically on every incoming order.
0 → 1
Tools replaced
Daily
Used in production
Event-driven
Integration pipeline
Live
Production status
01Key Insight
WHY EVENT-DRIVEN BEATS POLLING
The naive way to integrate Shopify + Uber Direct + Klaviyo is a cron that polls each system and reconciles state. That's fragile — every system has different rate limits, different consistency guarantees, different downtime windows. Good Ol' Studio is event-driven instead: Shopify webhooks fire `order.created`, a single handler fans out to Uber dispatch, Klaviyo triggers, and the local ledger. Three systems coordinate from one event, with retries and dead-letter handling built into the bus.
02The Problem
Why this exists.
Small-batch operations get squeezed between off-the-shelf tools that don't quite fit. A bakery selling on Shopify also runs Uber Direct for same-day delivery, Klaviyo for marketing, and a separate spreadsheet for finance. Every new order means switching contexts four times — confirm in Shopify, dispatch in Uber, trigger a follow-up in Klaviyo, log it for the books. The work isn't hard; the coordination is.
Generic ops tools don't help: they're built for venture-backed e-commerce with full ops teams, not a working kitchen with one operator. The constraint is real: limited daily inventory, tight delivery windows, repeat-customer email cadence. Every minute the operator spends in admin software is a minute they're not baking.
03The Approach
How it works.
Good Ol' Studio is one dashboard that absorbs the four tools the bakery used to live in. Orders land via Shopify webhook. Same-day deliveries get dispatched through the Uber Direct API. Marketing flows fire into Klaviyo on order events. Finance reconciliation runs against the underlying ledger. The operator sees one screen instead of four — and the systems coordinate on their own.
The architecture is event-driven from the start. A single `order.created` event from Shopify fans out to a dispatch handler, an inventory decrement, a Klaviyo trigger, and a ledger entry. No human glue between the systems. When something breaks (a delivery fails, a webhook retries), the dashboard surfaces it as a typed exception that the operator can resolve in one click.
04OPERATIONS FLOW
One order, three systems, zero handoffs.
02 / 04T+1s
Klaviyo confirmation flow triggers
The same event fans into Klaviyo — confirmation email goes out, customer enters the post-purchase flow. The bakery's email cadence runs without anyone touching Klaviyo.
03 / 04T+2 hr
Uber Direct dispatch on fulfillment
When the kitchen marks an order ready, the dashboard requests an Uber Direct courier with the correct pickup window. The customer gets a tracking link automatically.
04 / 04EOD
Ledger reconciles to bank deposit
End of day, the unified ledger reports match Shopify revenue, Uber dispatch costs, and the bank deposit — no CSV exports, no manual reconciliation.
05Features
What it does.
01 / 04Orders
Shopify webhook listener
The dashboard subscribes to Shopify's order webhooks and treats `order.created` as the canonical event. Inventory, dispatch, and marketing all key off this single source of truth — no polling, no reconciliation drift, no spreadsheets that go stale.
02 / 04Dispatch
Uber Direct integration
Same-day deliveries auto-dispatch to Uber Direct as soon as the order is fulfilled in the kitchen. The dashboard shows live courier status, estimated arrival, and exception handling for failed deliveries — all from inside the same screen the operator already lives in.
03 / 04Marketing
Klaviyo event triggers
Order events automatically fire into Klaviyo flows: confirmation, delivery in progress, post-purchase, win-back. The operator never opens Klaviyo — they configure flows once, and order activity drives the email cadence forever after.
04 / 04Finance
Single ledger, automatic reconciliation
Every order writes to a unified ledger that doubles as the bakery's daily reconciliation source. End-of-day numbers match Shopify, Uber, and the bank deposit without a single CSV export — because the dashboard owns the source-of-truth event stream.
06Impact
What it produced.
USED BY GOOD OL' COOKIE
DailyIn daily production at a real working bakery. The operator runs the kitchen from this dashboard — not as a side experiment, but as the system of record.
TOOLS REPLACED
0 → 1Replaced the four-app dance of Shopify admin, courier ops, Klaviyo console, and a finance spreadsheet with one dashboard tied to a single event bus.
COORDINATE AUTOMATICALLY
Three systemsEvery order coordinates Shopify, Uber Direct, and Klaviyo without human glue. Webhooks fan out, retries are typed, dead-letters surface as exceptions in the UI.
← Back to Index
© 2026