CHAHUAPOS / BUILDING IN PUBLIC
One shop. Many businesses.
Shared foundations.
Designing a POS around your shop. Start with a primary business and add other businesses without splitting your shop database.
CHAHUAPOS / BUILDING IN PUBLIC
Designing a POS around your shop. Start with a primary business and add other businesses without splitting your shop database.
One foundation, many businesses
One core + Your business
Shared identity and shop foundations
Offerings · Service arrangements · Charging basis
Shop setup and operational readiness
Configuration coverage from the real catalog, not a count of enabled operational engines.
HYBRID BY DESIGN
A restaurant with a cafe, or accommodation with retail, needs shared information while keeping each activity's workflow.
CHAHUAPOS saves multiple activities under one shop, then adds tested capabilities. It does not invent products, prices or transactions.
One configuration foundation for many business models. Selecting a business does not activate an unfinished module.
The app uses real SQLite/OPFS. After online preparation, saved configuration reopens offline. This is not cloud backup.
View progress and open the development app without a card. Membership is not enabled.
WHAT WORKS TODAY
Orders, bills and stock have passed local checks. The public app is still an earlier version, and real payments are not enabled.
Primary and additional businesses, model foundations, private shop text and on-device persistence.
From business models to catalog items, configure your shop in the same app that manages it.
Local checks cover order edits, original bill prices, retry, cancellation and catalog/stock management. This is not publication of that version or real payment activation.
Setup example
From business models to catalog items, configure your shop in the same app that manages it.
The shop's main activity, such as a restaurant, cafe or retail store.
A restaurant with a cafe, or accommodation with retail, sharing the same shop foundations.
Offerings, service arrangements and charging basis, kept specific to each business.
Categories, names, prices and images come from information the shop owner enters in the real app.
What's new
Published work, locally verified changes and ongoing development are clearly separated.
Progress document for this versionChoose a primary business and additional businesses across categories under one shop and local database.
Configure offerings, service arrangements and charging basis, with business-specific choices and private custom text saved on-device. Locally verified sales work is listed separately below.
Primary business, additional businesses, foundations and catalog setup have been checked in Windows Edge. This is not all-OS acceptance or publication of that app version.
Shop isolation, drafts, entered prices and resume passed in an isolated Cloud test environment. Not enabled on the public app; membership and verified PWA transfer remain pending.
The same draft survives an orderly browser restart, prepared-offline reopen and read-timeout recovery. This does not guarantee power-loss, device-loss or uncommitted-input recovery.
Real SQLite and local Edge checks cover order edits, original bill prices, concurrent changes and retry without a duplicate bill or stock movement. This version is not published.
Management catalog and inventory use the same shop as Sales. Real route checks cover entered price changes and counted stock, without a separate data or billing system.
Checked confirmation, reasons, unused returns and consumed/waste disposition. Prepared or served portions cannot use an ordinary stock return. Refunds and complete approval permissions are separate work.
Latest published app build f362a9d36b62af330bf1
Public build checked on 6 November 2026. Locally verified changes have not updated this app version.
The road ahead
One accepted point at a time, without unconfirmed delivery dates.
Kitchen edit/cancel deltas and acknowledgement are in progress. Verified order/stock work is listed separately; reservations, resources, recipes and durable cart recovery retain their own gates.
Next: financial checks and separate order, statement and receipt issuance. Completed service does not establish verified payment.
Membership, verified PWA transfer, cloud sync and real payments are not enabled. Isolated private-setup testing does not activate those capabilities.
Follow the build
See what is available today. Come back to see what has improved.