Your WhatsApp number, now a real storefront.

A storefront that lives inside the chat.

When a customer messages your shop, Commerce OS replies with a signed shop link — one URL, scoped to that customer, scoped to your catalogue, valid for that session. Tap the link and the storefront opens as a mobile-native PWA — your products, your prices, your promos, your tax. Add to cart, choose pickup or delivery, place the order. They never leave WhatsApp; the order confirmation comes back as a chat message.

This is the surface that WhatsApp's native catalogue cannot be. Meta's built-in shop is a rigid product list edited in Business Manager, with no link to your POS and no concept of stock, promos, or tax. The Commerce OS shop link is the real storefront — same data, same engine, different channel.

Your Retail OS catalogue, exposed.

The products customers browse on WhatsApp are the same product rows your cashier rings against at the till. Prices change in Retail OS, the shop link reflects it on the next page load. Stock runs out, the line hides itself. A promo lights up in the back office, it lights up online too — because the cart engine is the same code path the POS uses, not a fork.

Per-product visibility is yours: flip is_whatsapp_visible and is_shippable on anything you would rather not put online. Kitchen items, modifiers, variable-weight items, and inactive SKUs are auto-excluded so the catalogue stays clean without per-product babysitting.

Customers without a re-onboarding tax.

The customer who walked into your shop yesterday is the same customer who messages you on WhatsApp today. Commerce OS keys off the phone number — one Retail OS customer record, one history, one loyalty balance, whichever channel they arrive on. No separate online-customer table, no duplicate KYC, no “please create an account” friction wall.

For merchants running the Mauritius loyalty pilot, points earned at the till carry over to WhatsApp orders and back. The CRM lead record holds the consent (opt-in, opt-out, channel preference); the customer record holds the commerce. Two roles, one person, one phone — the way it should have always worked.

Orders go where orders go.

A WhatsApp order is an order. It lands in the same orders table as a till sale, tagged channel='whatsapp' so reports stay clean. Your manager sees it in the web console at /dashboard/online-orders. Your cashier sees a notification badge inside the PWA POS. Same row, two surfaces, no double entry.

Restaurants get Kitchen Display System routing the same way an in-store order does — the kitchen does not care which channel sent the ticket. When DeliveryOS lights up later, the dispatch handoff plugs in here too. Until then, fulfilment is yours: pickup at the store, or your own rider going out the door. One order pipe, not two — that is the whole point.

Your WhatsApp Business, your number.

Commerce OS is bring-your-own-number. Each merchant runs the channel on their own WhatsApp Business Account — provisioned via a BSP (we default to 360dialog) or Meta Cloud API direct. The number, the verified business name, the message templates, the Meta Business Manager record all live under your name. Posterita holds API credentials in our vault and acts as the technical integrator.

Two reasons this matters. One: Meta's Commerce Policy forbids a single account fronting transactions for many unrelated businesses, so a shared Posterita number is not an option for a real commerce surface. Two: if you ever leave Posterita, your WhatsApp business identity goes with you. The credentials are ours to hold and yours to take back. No channel lock-in.

Cash-first at launch. Payment rails later.

Commerce OS does not process online payments at launch. Orders are placed online; payment happens at handover — cash on pickup, cash on delivery, or whatever channel you already use. If your Posterita POS already has an online payment rail configured, we expose it as a pay-link option in the checkout. We are not integrating a new payment provider in v1.

Why: payment rails per region are deep work and a known rabbit hole. The Mauritius wedge — MCB Juice and Blink at the till today, MIPS and MAUCAS scoped for online — is on the roadmap. We would rather ship a clean catalogue and order flow first and wire payment rails by region next than ship a half-broken payment integration as a marketing bullet.

Three steps. One conversation.

This is not a self-serve sign-up. WhatsApp Business provisioning, Meta template submission, and vault-stored credentials are operational steps that need a human at our end. We do them once, properly, per merchant.

Questions people actually ask.

WhatsApp commerce, the way merchants actually want it.

Your number. Your catalogue. Your customers. One order pipe, one cart engine, one source of truth — extended to the channel your customers are already on. Honest about payments, honest about onboarding, honest about scope.

The Posterita family

Retail OS runs the till. Agency OS supervises the agents. Legal OS files the company. Mail OS reads the inbox. Account OS holds the identity. DeliveryOS executes the last mile. Commerce OS is the WhatsApp channel into all of it — one operating system for SMEs in the developing world.