Headless commerce lets a Singapore brand rebuild its website, app or WeChat Mini Program storefront while keeping the point-of-sale (POS) system its stores already run on. The storefront and the backend are separated and connected through APIs, so design changes online never require swapping out the till, the stock records or the store routines behind them. Fooyo builds Fooyo Commerce®, an AI-powered storefront platform, and does integration work that plugs into existing POS, CRM and CMS stacks instead of replacing them. This guide therefore focuses on the integration decisions that determine whether a headless project works, not on front-end design.

TL;DR

About the Author: Fooyo is a Singapore-headquartered company, with offices in Chengdu and Tokyo, that builds data platforms, AI products and storefronts for clients across eight countries. Fooyo is trusted by government agencies, enterprises and SMEs across Asia, and its integration work connects new storefronts to the POS, CRM and messaging systems clients already use.

What is headless commerce, and why does it matter if you already have a POS?

Headless commerce is an architecture in which the customer-facing storefront (the “head”) is decoupled from the commerce backend and connected to it through APIs. That decoupling is exactly why it suits brands with a working POS: the backend stays put while the front end changes.

A restaurant shows how this works. The dining room is the storefront, and the kitchen is your POS and inventory system. Orders travel between them on tickets in a fixed format. Because the kitchen only reads tickets, you can redecorate the dining room or open a delivery window without retraining the chefs. APIs are those tickets. As long as every storefront sends orders and reads stock in the agreed format, the POS does not need to know what the front end looks like.

How does headless commerce architecture connect a storefront to a POS?

Building on that decoupling, a headless commerce architecture for a brand that keeps its POS usually has four layers:

Fooyo’s view is that projects succeed or fail in the integration layer, not the storefront. Good POS ecommerce integration starts with a written answer to one question per data type: which system owns it?

Data typeUsually owned byWhat to decide
Stock levelsPOS or ERPSync frequency, and how much buffer stock to hold back online to avoid overselling
Product contentCommerce backend or CMSWhether POS SKUs map one-to-one to online products
Prices and promotionsPOS or ERPWhether online-only promotions are allowed and how they reconcile
OrdersCommerce backend, posted to POSHow online orders appear in store reporting and returns
Customer profilesCRMHow in-store loyalty points show up online

Composable commerce vs headless: which do Singapore brands actually need?

A related but distinct question is how far to take the decoupling. Headless separates front from back. Composable commerce also splits the backend into independent services, such as search, cart and promotions, each of which can come from a different vendor.

ApproachWhat changesBest fitTrade-off
Themed platformFront and back from one vendorStandard storefront needs, small teamDesign limited to templates and extension points
HeadlessCustom front end, one commerce backendBrands wanting design control while keeping a POSYou maintain a front end and an integration layer
ComposableFront end plus individually chosen backend servicesLarge catalogues, many markets, in-house engineersMore vendors, contracts and integration points to monitor

Our position: go headless first, and replace an individual service only when a specific limit appears, such as weak search or complex multi-market pricing. Going fully composable on day one buys flexibility you pay to maintain before you use it.

When is a unified commerce platform a better choice than POS integration?

Stepping back from architecture, headless integration is not always the right call. A unified commerce platform runs online and in-store sales on one shared backend, so stock and customer data live in one place without syncing.

Several vendors offer this model. Shopify Plus has native Shopify POS with unified inventory and a Global ERP Program. commercetools provides InStore, an API-first composable POS sharing the same backend.

What should Singapore brands check on data residency and hosting?

Once the architecture is chosen, the next constraint is where data lives. Singapore’s PDPA does not strictly mandate data localisation if cross-border transfer protections are met.

Ask every vendor which of the two they mean, and which data each AI feature sends where.

How do you roll out headless commerce without disrupting stores?

With ownership, architecture and hosting settled, rollout is mostly about sequencing:

  1. Map the system of record for each data type, using the table above.
  2. Audit the POS API. Check whether it exposes stock, orders and customers, and whether it supports webhooks or only scheduled exports.
  3. Build and test the integration layer before the storefront, using a limited SKU set or one store.
  4. Launch one channel, then add others, such as a WeChat Mini Program, once sync is stable.
  5. Add AI merchandising with human review gates so listings and recommendations are checked before going live.

Timelines depend on the workflow, how open the POS API is, data readiness and client approvals, so they should be scoped per engagement. Fooyo follows this sequence: a 30-minute demo, a scoped pilot, deployment in private cloud or on-premises, then ongoing operation and support.

[QUOTE REQUESTED: one line from Fooyo leadership on why the integration layer should be built and tested before the new storefront goes live]

Frequently Asked Questions

What is headless commerce in simple terms?

A storefront built separately from the commerce backend and connected to it through APIs, so either side can change independently.

Do I need to replace my POS to go headless?

No. If your POS exposes an API or reliable data exports, a headless storefront can read stock from it and post orders to it.

What is a headless commerce platform?

A commerce backend designed to serve catalogue, cart and checkout functions through APIs to any front end, rather than through its own fixed templates.

What is the difference in composable commerce vs headless?

Headless decouples the front end from one backend. Composable also splits that backend into separately chosen services.

Can a WeChat Mini Program share the same backend as my website?

Yes. In a headless setup, a Mini Program is another front end calling the same commerce services and reading the same POS stock.

Does PDPA require my commerce data to stay in Singapore?

Not strictly, if cross-border transfer protections are met.

About Fooyo

Fooyo is a Singapore-headquartered company that builds data platforms, AI agents and production AI products, with offices in Chengdu for development and Tokyo for business partnerships. Its Fooyo Commerce® platform covers product listings, storefront setup, payments and AI merchandising, and its integration services connect to existing POS, CRM, CMS and messaging channels instead of requiring replacement. As a Tencent/WeChat partner, Fooyo also builds WeChat Mini Programs for brands preparing for the China market. Fooyo builds and runs these products with clients, deploying in private cloud or fully on-premises depending on data-residency needs.

If you want a storefront you control without disrupting the POS your stores depend on, start with a short conversation. Book a demo or get in touch with the Fooyo team at https://fooyo.sg/.

References

  1. Google (google.com)
  2. The Business Case For Headless Commerce (webriq.com)
  3. Digital Commerce Platform: Top Features and How To Choose (2026) – Shopify Singapore (shopify.com)