POS SalesManager

How POS SalesManager works

POS SalesManager runs sales, tills and stock for your shops. This is how the application is organised: who signs in, where transactions are processed, where data is kept, which payment services it uses, and how every new version is checked before it goes live.

Swipe the diagram sideways to see all of it.

POS SalesManager architecture diagram Web and mobile users reach the application over HTTPS. It relies on a database and file storage, calls payment and product information services, and receives new versions through a tested delivery pipeline. Users Web browseradministrators · branch supervisorscashiers · sales repsaccountants Mobile appAndroid and iOS · works offlinesales kept on the phonesales · restocking · report web pages · secure session sent when back online app.salesmanager.cm · encrypted HTTPS connectionaccess limited to accounts created by the administrator Application server POS SalesManager application Web interfacemanagement screensinteractive catalogue Mobile APIpersonal access tokenno duplicate sales Access and rightsroles and permissionsper shop and per branch Sales managementsales · till · stock (FIFO method)customer credit · commission · report Modulesorders · expenses · staffrestocking · customer accounts Automatic checksconsistency check every nightcommission closed every month DocumentsPDF receipts and invoicesbarcodes and QR codes Databasesales · stock · tills · accountsbacked up before every update File storageencrypted sessions · logsproduct images · documents External services Mamonipayonline mobile payment PayMeOrange Money · MTN MoMo Real-time notificationsscreens update instantly Emailsending emails Open Food / Beauty Factsproduct details from a barcode scan Releasing new versions Developmentone branch per changetests on a dedicated databasenumbered stable version Code repositoryfull historychanges reviewedidentified versions Automated testson every changedatabase rebuilt from scratchfailure = no release Deploymentpre-production, then livebackup before updatingroll back if needed release of a version
POS SalesManager application partner service checks and release enabled depending on your setup

Day to day

  • Sale at the counter: the cashier records the sale; stock, the till and the daily report update at the same time.
  • Sale without a connection: on mobile, the sale stays on the phone and is sent to the server as soon as the connection returns, with no risk of duplicates.
  • Mobile payment: enabled by the administrator; pending payments can be checked from the till.
  • New product: when an unknown barcode is scanned, the product record is pre-filled from the open Open Food Facts and Open Beauty Facts databases.

Data security

  • Every connection goes over HTTPS.
  • Each user only sees the screens and shops their role allows.
  • Sessions are encrypted; the mobile app keeps its token in the phone's secure storage.
  • No open sign-up: accounts are created by the administrator.

Reliability

  • Every change passes a suite of automated tests before it can be released.
  • A version is installed in pre-production first, then live.
  • The database is backed up before every update, and the previous version can be restored.
  • A consistency check of tills and stock runs every night.