The migration-or-die framing
Every headless tutorial follows the same script: pick a platform that supports headless commerce, migrate your catalog, rebuild your frontend in Next.js, and enjoy the speed. The script works if you're greenfield. It collapses the moment you're an existing store with five years of SKUs, a marketing team trained on the admin, and orders flowing through integrations nobody fully documented.
The platform-migration framing assumes the storefront and the backend must change together. That's true only because most headless infrastructure was built with that assumption. It is not actually true at the architecture level.
The bridge-layer pattern
You can keep your existing backend — Wix, Shopify, Webflow, whatever — and build a custom React frontend that talks to it through a thin, opinionated bridge. The bridge does three things:
- Normalizes the wildly different shapes of each platform's API into one canonical schema.
- Authenticates + rate-limits at the right layer (tenant-scoped, plan-aware, never exposing platform credentials to the frontend).
- Caches aggressively at the edge so your custom frontend gets sub-100ms responses without you writing cache code.
Once you have the bridge, every store on a supported backend can go headless without migration. The frontend is yours to design, the backend is the team's familiar admin, and the gap between them — the part that's historically taken 80 hours of engineering — is solved infrastructure.
Why it didn't already exist
Three reasons, in order of how often they're the actual blocker:
- Platforms didn't want it to exist. Until ~2023, most platforms' headless APIs were second-class citizens — undocumented, rate-limited, missing fields. The business model rewarded vertical integration.
- The market saw it as a migration problem. Headless was sold as "leave your platform, go composable, become enterprise." That sold consulting hours; it didn't serve the 95% of stores under $1M/year that just wanted performance and design control.
- The infrastructure was hard to write correctly. Field mapping across platforms is genuinely tricky. The normalizer has to handle currency units, variant explosion, soft-deleted records, missing fields, schema drift, and tenant-scoped caching — all without leaking platform-specific details to the frontend.
The architectural bet
Trama is a bet that the bridge-layer pattern is durable. The bet has three legs:
- Platforms open up further, not less. Wix shipped real headless OAuth in 2024. Shopify Storefront APIs keep adding coverage. Webflow rebuilt Ecommerce around its API. The wind is at our back.
- React stays the frontend default. Even if Astro, SolidStart, and Qwik take share, all of them consume the same fetch + cache primitives we expose. The SDK works in any framework that runs JavaScript.
- The 95% of stores keep wanting the design + performance of headless without the migration cost. The pain we solve is structural, not faddish.
What this means for you
If you're reading this with an existing Wix, Shopify, or Webflow store and a half-finished headless plan stalled by the migration cost — you don't need to migrate. Paste your URL on the homepage; Trama renders your products through a Next.js frontend in five seconds. That preview is real, not a mockup. The decision becomes "do I like this frontend?" rather than "can my team survive a three-month platform move?"
We built Trama for the stores the headless tutorials forgot.
See your store headless in 5 seconds.
Paste your URL on the homepage. No signup, no card, no migration.