ShopFlow

The POS experience connects product selection, sale lines, totals, payment-method records, and inventory movement. Barcode-friendly entry and camera scanning help attendants find products, with manual entry and offline lookup fallbacks where appropriate.

The catalogue and per-shop inventory are distinct. A business can define a product once and record stock for the shops where it is actually held. Product variants, stock movements, and shop context support a more accurate view of what can be sold at a particular location.

Owners and inventory managers can review products, shops, stock, and reports through role-appropriate workflows. Exact money handling preserves financial values across calculations and storage, and the platform supports a defined set of currencies used in its target markets.

ShopFlow includes a client-side sale queue and backend synchronisation workflows for interrupted connectivity. Offline identifiers, sync state, and conflict handling give queued work a defined path back to the server.

Versioned product updates help detect competing changes rather than silently replacing newer information. A cashier can continue supported work through an interruption, then see whether synchronisation succeeds or requires attention. The system treats recovery as part of the workflow, not as an invisible background assumption.

Connect provides public shop pages, product detail, category filtering, and search. Visitors can search by text and city or use a near-me view to discover participating retailers. Public pages are available without a shopper account.

A shop controls its public visibility and description, while individual products also have publication controls. Public stock information follows the shop's settings. A shared catalogue product can appear in multiple shops with each location's own inventory context.

Connect is a discovery and catalogue product. Its value is connecting a customer's search to an actual participating shop and its published offerings.

Operational changes publish queue events that a dedicated worker processes into a public data store. The worker reads fresh source records, applies publication rules, and updates or removes the public projection. Hidden or inactive records do not remain public simply because they were once synchronised.

Sensitive fields such as cost prices and internal customer, sale, and audit records are excluded from the projection. This gives the public site a narrower data contract and allows its search workload to operate separately from internal retail transactions.