Emergency situation

In case of emergencies or breakdowns, you can send an SMS to our emergency hotline

On-call phone (SMS only)

+45 29 70 15 95

Send an SMS with the following information:

  • Your name and webshop
  • Description of the problem
  • Your callback phone number

Notes: This service is only for critical situations where your webshop is down or has serious problems. For regular support, please use our normal support channels.

Headless commerce

Headless commerce is an e-commerce architecture where the frontend (what the customer sees) and backend (product data, orders, payment) are separated and communicate via APIs. This gives complete freedom in design.

What is headless commerce?

In a traditional e-commerce platform, the frontend and backend are closely integrated: the platform controls both the visual aspects (HTML, CSS, templates) and the functional aspects (products, shopping cart, payment). In headless commerce, the two layers are separate. The backend delivers data via APIs, and the frontend can be built using any technology—React, Vue.js, Next.js, a mobile app, or even a physical kiosk.

Traditional vs. Headless

  • Traditional (monolithic): Backend and frontend in a single system. Easier to get started, faster setup, but limited flexibility in design and performance.
  • Headless: The backend provides data via APIs. The frontend is built separately. Full design freedom, but requires more development work and technical knowledge.

Advantages of headless commerce

  • Design freedom: No template limitations. You can create exactly the experience you want.
  • Performance: Frontends built with modern JavaScript frameworks can be extremely fast (static site generation, edge rendering).
  • Omnichannel: The same backend delivers data to the online store, mobile app, POS, IoT devices, etc.
  • Flexible tech stack: The frontend team can use the latest technologies independently of the backend.
  • Scalability: The frontend and backend can be scaled independently.

Disadvantages of headless commerce

  • Development complexity: You must build and maintain a separate frontend, which requires skilled developers.
  • Higher costs: More development time and ongoing maintenance compared to a traditional platform.
  • No out-of-the-box frontend: You start from scratch with design and functionality.
  • Division of responsibility: Errors in the frontend and backend must be debugged across two systems.

When does headless make sense?

Headless commerce is relevant when:

  • You have a dedicated development team that can build and maintain a custom frontend.
  • You have specific performance requirements that a traditional platform cannot meet.
  • You need to deliver a consistent experience across multiple channels (web, app, kiosk).
  • You have a unique design that cannot be implemented on a template-based platform.

For most small and medium-sized online stores, a traditional platform like Shoporama—which offers flexible themes and strong performance—is the most cost-effective solution.

API-Driven E-commerce

Whether you choose a fully headless solution or a traditional platform, API access is valuable. With a REST API, you can build integrations, automate processes, and retrieve data for third-party systems. Shoporama offers a REST API that provides access to products, orders, customers, and more—giving you the ability to build headless or hybrid solutions if the need arises.

We know online marketing in Shoporama

We've been working with online marketing ourselves for decades. As the only shop system in the country, we have spoken multiple times at conferences such as Marketingcamp, SEOday, Shopcamp, Digital Marketing, E-commerce Manager, Ecommerce Day, Web Analytics Wednesday and many more.

See the full dictionary