Zaam (XAM) Commerce
Full commerce OS: Zaam panels, API, Flutter EPOS for Android/iOS/desktop/web, and B2B surfaces — inventory, pricing, tills, and multi-channel orders.
Commerce OS flow
Catalog → price → till/B2B → sync — one commercial brain across channels.
- Catalog SKU truth
- Price Channel rules
- Till Flutter EPOS
- B2B Wholesale buy
- Sync API versions
- Plan Merch AI later
The challenge
Wholesale/retail groups need one commercial brain across back office, till, and B2B buying. Split tools create price disputes, blind inventory, and fragile branch switching on mobile.
Zaam required a serious ERP-class stack — not a thin dashboard — including native-class EPOS on phones and tablets.
Till latency and peripheral flows (card readers, customer display) punish wrapped websites pretending to be POS.
What we built
We built across zaam-api, zaam-panels, Zaam_website, and Flutter epos (Android, iOS, macOS, Windows, web PWA) with POS migrations, staff PINs/roles, barcode flows, and offline-minded till UX.
Brand system (black/white/golden marks) keeps every surface recognizably Zaam.
API migrations (including POS module) were versioned so panels and apps move together.
Platform architecture
Panels, API, Flutter EPOS, and B2B surfaces on one commerce graph.
Zaam panels
Next.js back office for inventory, pricing, and admin.
Zaam API
Versioned Node services including POS migrations.
Flutter EPOS
Native-class tills across mobile, desktop, and PWA.
B2B + brand
Wholesale buying surfaces and multi-mark identity system.
Commerce OS diagram
How panels, API, and EPOS share one catalog brain across channels.
Back office
Selling
Intelligence
Keep AI off the cashier critical path — use it in planning and enrichment.
Design principles
Cashiers need speed; AI belongs in merchandising — never on the till critical path.
One commercial brain
Back office, till, and B2B must share price and stock truth.
Native-class EPOS
Till latency and peripherals demand Flutter, not a wrap.
No chat on the till
Cashiers need speed; AI belongs in merchandising.
Operate like infra
Docs, migrations, and roles ship with the product.
How we approached it
Architecture followed real retail roles: cashiers, sales reps, warehouse, admins — enforced in POS permissions and panel IA.
EPOS was first-class Flutter, not a wrapped website, because till latency and peripheral flows demand it.
API migrations (including POS module) were versioned so panels and apps move together.
Deployment docs and database readmes were part of delivery — Zaam is operated like infrastructure.
We intentionally did not sprinkle chat widgets on the till — speed beats novelty at checkout.
Where AI enters — and where it must not
AI value appears once commerce data is trustworthy: SKUs, variants, channel orders (Amazon/eBay/TikTok/Shopify/POS/B2B) in one schema.
That unlocks assistants for catalog enrichment, pricing anomaly flags, and B2B reorder suggestions.
We intentionally did not sprinkle chat widgets on the till. Cashiers need speed; AI belongs in merchandising and planning loops.
EPOS telemetry (shifts, cash movements, availability) further feeds labour and demand models later.
Technical notes from production
Details that only show up once the season is real.
- Flutter EPOS is first-class across Android/iOS/desktop/web because till latency forbids wrapped websites.
- POS permissions encode real retail roles — cashiers, reps, warehouse, admins.
- API/POS migrations are versioned so panels and apps advance together.
- Deployment docs treat Zaam like infrastructure, not a disposable dashboard.
Delivery & systems
Next.js panels + Node API + Flutter EPOS multi-platform + marketing site brand system.
Documented deployment and inventory module status for rollout discipline.
POS roles, PINs, and barcode flows shipped as first-class till concerns.
Stack
Click a layer — each one maps to a real season responsibility.
Back office
Next.js Panels
Inventory, pricing, and admin operations.
Brand assets from the live product
Primary mark pulled from the Olympiad codebase — shown once, on the surface it was built for.
Outcomes
- Multi-surface Zaam ERP/commerce stack
- Flutter EPOS on mobile & desktop targets
- POS roles, PINs, and till migrations
- Brand-consistent panels and website
- Commerce graph ready for merchandising AI
More work
View all
2025–2026
AI Olympiad
EdTech · AI Competition Platform
AI Olympiad
EdTech · AI Competition Platform
2024–2026
Archit Art Gallery
Commerce · Invoicing · Amazon AI Listings
Archit Art Gallery
Commerce · Invoicing · Amazon AI Listings
2023–2026
QUEST Book
EdTech · AI & STEAM Quiz
QUEST Book
EdTech · AI & STEAM Quiz