Headless commerce and PWA (Progressive Web App) are fashionable terms in e-commerce. Agencies are happy to recommend them – often regardless of whether they actually solve the client’s problem. Below is an attempt to answer when headless makes sense and when it is overkill.
What headless means
A traditional Magento store has frontend (what the customer sees) and backend (logic, database) integrated in one system. Headless separates these layers: the Magento backend exposes data through an API, and the frontend is a separate application (React, Vue, Next.js) that consumes it. PWA is a frontend that behaves like a mobile app – works offline, can be “installed” on a phone’s home screen.
When headless is justified
When the store must operate on multiple channels simultaneously (web, mobile app, kiosk, B2B application) and all should draw from the same data source. When the frontend team is large and wants to work independently of the backend. When UX requirements are specific enough that the standard Magento theme is too limiting. When page load time is critical (Next.js with SSR can be faster than traditional Magento rendering).
When headless is overkill
For a typical B2C store up to 50,000 products, headless adds complexity without proportional benefits. A separate frontend is a separate infrastructure, separate deployment, separate stack to maintain. Every change in product data or promotions requires synchronisation between systems. Maintenance budget grows. Time to market is longer.
PWA without headless
PWA Studio – Adobe’s official PWA solution for Magento – does not require full headless. You can implement PWA as an overlay on standard Magento and gain some benefits (offline support, push notifications, better mobile performance) without full layer separation.
If any of the signals described sound familiar, it is worth analysing before the problem grows. I offer a free initial consultation – write to biuro@tews.pl or visit tews.pl.
