Webito Anniversary Sale: 15% off all plans!Get Discount →
Headless

Headless architecture, without the headless project

A fast storefront you can restyle visually today, and an API to replace it with your own front end the day that becomes worth doing.

Webito separates the commerce backend from the storefront that renders it, which is what makes it headless: but it also ships the storefront, so going headless does not mean commissioning a front-end build first. You start with server-rendered themes controlled by design tokens you edit visually, and if you later want a bespoke front end, you build against the same storefront API the bundled themes use, keeping catalogue, tax, orders and B2B logic on the platform.

What Webito does

  • Server-rendered storefront included: no front-end build required to launch


  • Design-token theming for colour, type, radius and spacing, edited visually


  • Page composer and blog with taxonomies, translatable per locale


  • Per-page metadata, canonical URLs and structured data emitted by the storefront


  • Documented storefront API and webhooks for a custom front end


  • Custom domain mapping with certificates issued and renewed automatically

The usual headless trade-off

Classic headless platforms give you an API and a blank page: nothing renders until someone builds a front end, and every content change afterwards routes through a developer. Traditional platforms give you a storefront you cannot meaningfully escape. Webito's position is to ship both sides: a real storefront out of the box, and an API that makes replacing it a normal project rather than a migration.

Design tokens, not theme code

Restyling is done through tokens: colour, typography, radius, spacing: edited visually and applied consistently across every page the theme renders. That covers the majority of what merchants actually want to change without touching templates, and it keeps the result coherent rather than a collage of one-off CSS overrides.

Pages and content, without a second CMS

Landing pages, editorial content and a blog with taxonomies are part of the store rather than a bolted-on system with its own login. Pages are composed from blocks, content is translatable across your active locales, and everything is rendered server-side so it is indexable: with per-page metadata, canonical URLs and structured data emitted by the storefront.

When you do go custom

The storefront API and webhooks are documented and are the same interface the bundled themes consume, so a custom front end is not a privileged integration path with different behaviour. You keep tax determination, order processing, B2B pricing and invoicing on the platform, and own only the layer you actually wanted to own.

This page explains how the platform behaves. It is not tax advice: your registrations, filings and thresholds remain your responsibility, and your accountant should confirm your specific position.

Related capabilities

Your store, live and selling in minutes

Add your products, configure your catalog, and launch a sophisticated storefront. Webito bypasses the fragmented plugin ecosystem by delivering a completely cohesive commerce infrastructure—combining advanced inventory tracking, tax-compliant checkout pipelines, and deeply integrated regional shipping configurations—all operational from day one.

Every order, every payment method, one pipeline

Track the entire lifecycle of a transaction from the initial customer checkout through to final fulfillment and invoicing. Webito provides a singular, authoritative pipeline that governs payment capture, warehouse dispatch, electronic invoicing, and structured refund processing without data fragmentation.

A store that looks like your brand, not a template

Control your brand's aesthetic presentation through a cohesive design-token architecture rather than relying on unstructured, fragile drag-and-drop mechanics. By configuring core visual parameters centrally, you ensure rigorous design consistency across every single page.

Accept every payment method your customers expect

Process transactions through a unified checkout pipeline that natively accommodates both immediate B2C card payments and complex B2B deferred invoicing. Gateway integrations operate as deeply embedded plugins, ensuring absolute tax and accounting consistency.

Built to rank | SEO built into every page

Attain maximum organic search visibility natively, circumventing the need for unstable third-party SEO plugins. Every storefront URL is strictly server-rendered, injecting precise metadata and Schema.org structured data directly into the initial HTML response.

EU VAT compliance, decided inside the order

Destination rates, tax categories, reverse charge and VAT number validation | resolved when the order is placed, not reconciled afterwards.

Know exactly where you stand against the €10,000 threshold

A running total of your cross-border consumer sales, broken down by destination, so the OSS threshold never arrives as a surprise.

Structured e-invoices, not PDFs with an invoice number

EN 16931 semantics and Peppol BIS Billing 3.0 output generated from the order, with the routing identifiers your buyers' systems need.

Wholesale buyers and retail shoppers, one catalogue

Company accounts, negotiated pricing, quote requests and net terms | without maintaining a second store or a parallel product list.

Sell across Europe without a currency surprise at checkout

Deliberate prices per currency, destination-aware tax and shipping, and the local payment methods European buyers expect.

Questions

Common questions

A fast storefront you can restyle visually today, and an API to replace it with your own front end the day that becomes worth doing.

Yes, by architecture: the admin backend and the storefront are separate services communicating over an API. The difference from most headless platforms is that Webito ships a production storefront as well, so you can launch without a front-end project and still swap it later.

No, for the things merchants usually want. Colours, typography, corner radius, spacing and page composition are edited in the dashboard through design tokens and the page composer. A developer is needed only if you want a front end that the themes cannot express.

Yes. The storefront API and webhooks are documented, and are the same interface the bundled themes use. You keep catalogue, tax determination, orders, invoicing and B2B pricing on the platform and render whatever you like on top.

Pages are server-rendered rather than client-hydrated shells, and the storefront emits per-page metadata, canonical URLs and product structured data. Combined with your own domain and automatic certificates, that covers the technical baseline; content and links are still your job.

Test it against your own numbers

Open a free store, load a few products and run an order to the country you are unsure about.