From the team
Long-form writing on how VoidPOS is built, why decisions are made the way they are, and what we are thinking about next.
How VoidPOS structures its data layer to support unlimited branches under one account, while guaranteeing that no branch ever sees another's data.
Software priced in USD for a US market is unaffordable for most of the world. Here is the exact tiering we use and the philosophy behind it.
A 6-digit PIN sounds simple. Making it secure — with industry-standard hashing, lockout logic, cross-branch uniqueness checks, and server-side enforcement — is the interesting part.
A receipt is often the last thing a customer sees before they leave. Here is how VoidPOS generates branded, print-ready receipts from browser HTML.
Data-layer security rules are your last line of defense. Here is how VoidPOS structures them to enforce ownership, branch isolation, and plan limits — independent of application code.