Headless
Commerce Lexicon

A procurement and architectural model in which the D2C brand owns 100% of its application source code and deploys to its own cloud infrastructure (Vercel, AWS, or similar) rather than renting a proprietary SaaS environment.

• How it differs from Shopify Plus

  Shopify Plus is a monthly licence, listed from ₹1,75,000/month on Shopify's India pricing page (checked 31 Oct 2026), plus a 0.2% fee on each transaction when the store uses a third-party payment provider instead of Shopify Payments. Card-processing fees are charged by every processor on every platform, so they are not a Shopify-specific cost. In a Zero Platform Fee architecture, the brand pays only for the compute it consumes; there is no software licence because the brand owns the codebase.

  Source: Shopify Plus pricing
• Financial impact (illustrative)

  Arithmetic, not a forecast: 36 months of the entry Plus licence is ₹63,00,000 (₹1,75,000 × 36). A brand processing ₹10 crore a year through a third-party gateway adds ₹6,00,000 in 0.2% fees over the same period. Subtract your own hosting and maintenance bill to get the net, and change the inputs to match your store in the cost comparison.

  Run your numbers
• Technical requirements

  Requires a composable headless architecture built on a framework like Next.js, a decoupled CMS, and a direct payment processor integration (Stripe, Razorpay).

A term we use to describe a bespoke, fully composable Next.js codebase that functions as the complete digital infrastructure layer for a D2C brand. An AOS replaces monolithic platforms (Shopify, Magento, BigCommerce) with a custom orchestration layer handling rendering, API middleware, edge delivery, and build pipelines.

• Core Components

  React Server Components, Edge Middleware, Incremental Static Regeneration (ISR), decoupled headless CMS, and direct payment processor integration.

An architectural pattern where the frontend presentation layer is decoupled from the backend commerce engine. Unlike monolithic platforms where the storefront, cart, and CMS are tightly coupled, headless commerce allows brands to build custom storefronts using frameworks like Next.js while consuming commerce APIs for inventory, checkout, and customer management.

A deployment strategy where static and server-rendered content is distributed across a global edge network (Vercel's Edge Network, Cloudflare Workers) such that HTML responses are served from the data center closest to the end user. Panarch Digital's targets are a global Time to First Byte (TTFB) under 150ms and a mobile Largest Contentful Paint (LCP) under 0.8 seconds; these are ceilings, and this site's own measured figures sit below them.

• Measured, not claimed

  The current lab and field numbers for panarchdigital.com, with date and method, are published on the performance baseline.

  Performance baseline

The layered caching strategy in a Next.js App Router stack that keeps responses instant without sacrificing freshness. Prerendered HTML and React Server Component payloads are served from cache, the Data Cache memoizes fetches across requests, and Incremental Static Regeneration (ISR) re-renders pages in the background on a revalidation interval: the server-side mechanics behind the Sub-Second Stack.

• The layers

  Full Route Cache + RSC Payload Cache (prerendered output), the Data Cache (deduplicated, persisted fetches), and ISR with time- or tag-based revalidation, tuned per route via revalidate and cache tags.

• Why it matters

  Caching at the server and edge removes origin round-trips for the majority of requests, holding Core Web Vitals green even during traffic spikes, without serving stale data to logged-in users.