Short write‑ups of problems we hit running a real commerce operation and what we changed in the code because of them. No product announcements; just the reasoning.
For as long as the storefront has rendered on the server, a page missing from the cache cost about a second, and we kept blaming the size of the page. It was a translation helper. Every translated word left a small reactive effect behind in the rendering process, nothing ever cleaned it up, and every page drawn in a different language re-ran all of them. How a cost that grew with uptime gave it away, a heap diff full of translation keys, the twenty-line fix, and what changed once a cache miss cost 36 ms instead of 1.2 s.
A label sheet is designed in a browser and printed by mPDF — two renderers that share no code and must agree to the millimetre. Where they disagreed, what happened when a barcode library quietly accepted an invalid EAN13 and encoded a different number than the digits printed under it, why the PDF thumbnails are rendered on the client, and the one Blade character that cost an afternoon.
Our pickers and packers work on cheap tablets with a Bluetooth scanner, on the same web application the office uses — same URL, same codebase, no app store. How a browser tells a barcode from a person typing, what the server does with a scan (match → location → pick, in one round‑trip), and why "it feels like an app" is a design discipline, not a framework.
Every storefront page is rendered once on the server — so crawlers and slow phones get full HTML — and once more in the browser, where it becomes an app. How Inertia server‑side rendering runs here (a Bun process under a supervisor, health‑checked on every deploy), what a 418 KB props payload taught us about where the second actually goes, the silent client‑side‑rendering incident, and the three levers we keep on the list.
Why a trading company wrote its own CMS instead of bolting a shop onto a page builder, and how two front‑end engineers turned "we need a product page" into seventy‑odd web blocks, a workshop that edits the live site, snapshots you can publish and roll back, and a storefront that knows its own catalogue.