Product
Digital voucher system
Part of the commerce platform rather than a separate product: vouchers, the people who issue them and the people who redeem them, kept apart by role.
Status: In active development, as part of the commerce platform.
The problem
A voucher is a promise that money already changed hands. That makes the interesting question not the voucher itself but who is allowed to create one, who can see it, and who can mark it used.
How it works
The system manages products, digital vouchers, customers, vendors, administrators and managers. Each of those is a role, and the separation between them is enforced by role-based access rather than by which screen a person happens to open. A vendor sees their own vouchers; a manager sees the vendors they are responsible for; an administrator configures the products the vouchers are drawn against.
Architecture
Roles enforced at the API
Every voucher operation is checked against the caller's role before it reaches data, so the boundary does not depend on the interface.
Part of the commerce platform
Vouchers share the catalogue, the customers and the wallets rather than duplicating them, which is what keeps balances reconcilable.
Technologies
PHP Laravel MySQL Redis React
Services this uses
SaaS and custom software
Multi-tenant business platforms with per-organisation data isolation, roles and an API shared by every client.
Web applications
React and Next.js front ends against Laravel and Node APIs, including admin panels and RTL interfaces.
Start a project
Write in English, French, Romanian or Arabic. Every message gets a written answer within one business day.
Tell us what you are building.
Write in English, French, Romanian or Arabic. Every message gets a written answer within one business day.