Retail operations system

NexusPOS

A retail POS and store-operations system covering touch checkout, barcode workflows, inventory, staff roles, cash shifts, refunds, reconciliation, audit history and native receipt printing.

Product work and architecture overview by Savi Saluwadana.

ElectronPOSInventoryPrismaMongoDBRBAC

What it does

Who it serves
Cashiers, store managers and retail administrators.
Product purpose
Checkout and store operations with an optional Electron desktop shell.
  • Touch checkout, barcode/SKU input, held orders and receipts.
  • Inventory, authenticated staff roles and store settings.
  • Cash shifts, refunds, reconciliation and audit history.

How it works

  1. A cashier builds a basket and applies eligible discounts or loyalty.
  2. Authenticated server routes calculate checkout totals and validate stock.
  3. Prisma persists retail records to MongoDB.
  4. The optional Electron shell provides native receipt printing while the browser supports print fallback.

Architecture

Next.js / React → Prisma → MongoDB + Electron

NexusPOS architectureRetail interface connects to Retail API. Desktop shell connects to Retail interface. Retail API connects to Retail records.Retail interfaceNext.js / ReactDesktop shellElectron / receipt printingRetail APIAuth, stock, checkoutRetail recordsPrisma / MongoDB
Component overview. Arrows show requests and data flow between the main parts of the product.
NexusPOS components and responsibilities
ComponentResponsibility
Next.js + ReactCashier and store-administration interfaces.
Server routesAuthenticated staff actions and server-authoritative checkout.
Prisma + MongoDBProducts, orders and retail operational records.
ElectronOptional native desktop packaging and receipt printing.

Current scope

Electron is an optional desktop shell. The portfolio does not claim a complete offline checkout engine or a tenant-isolated hosted retail service.

Architecture summary reviewed . The repository is private; this page provides a public product summary.