Retail & F&B SaaS
Tindra POS & Inventory
A multi-tenant SaaS platform built to centralize POS, inventory, purchasing, subscriptions, and operational workflows for retail and food and beverage merchants.
Context
Business / Industry Context
Tindra is a cloud-based POS and inventory platform for Philippine retail and food and beverage businesses. It supports day-to-day merchant operations while providing a separate platform administration layer for managing merchants, subscriptions, plans, and system-level settings.
Problem
Retail and F&B businesses often manage sales, inventory, purchasing, suppliers, receiving, and reporting through disconnected tools or manual processes. Tindra needed a centralized platform where merchants could run daily operations while maintaining clear separation between merchant data, user roles, financial transactions, and platform-level administration.
Goals
- Provide a cloud-based POS and inventory system for retail and F&B merchants.
- Support multiple merchants through secure tenant-isolated architecture.
- Connect POS transactions with inventory movements and operational records.
- Centralize purchasing, suppliers, purchase orders, receiving, and stock replenishment.
- Support merchant subscriptions, plans, payments, and platform administration.
- Provide operational reporting and auditability across key workflows.
Users / Roles
- Platform administrators
- Merchant owners
- Cashiers
Core Workflows
- Retail POS checkout and payment recording
- Dine-in and take-out order management
- Product, category, unit, and stock management
- Stock adjustments, low-stock monitoring, and movement tracking
- Supplier and purchase-order management
- Low-stock purchasing and buy-list workflows
- Goods receiving and automatic stock updates
- Merchant subscription and payment management
- Sales, inventory, purchasing, and operational reporting
- Void, refund, and audit workflows
Solution
Built a production-oriented multi-tenant SaaS platform connecting POS, F&B ordering, inventory, procurement, subscriptions, reporting, and platform administration within one operational system. Sales, receiving, stock adjustments, voids, and refunds are handled through controlled transactional workflows so inventory and operational records remain consistent as merchants perform daily activities.
Key Modules
- POS and transaction management
- F&B tables and order management
- Products, categories, units, and inventory
- Stock adjustments and movement history
- Suppliers and procurement
- Purchase orders and goods receiving
- Buy lists and low-stock purchasing
- Merchant subscriptions and payments
- User and permission management
- Platform administration
- Reports and audit logs
Technical details
Architecture & Technology
- Multi-tenant Next.js SaaS architecture with merchant-level data isolation.
- Supabase and PostgreSQL backend with database-enforced access controls.
- Role-based access for Platform Admin, Owner, and Cashier workflows.
- Append-only operational events for critical sales and inventory transactions.
- Atomic and idempotent transaction handling for checkout, receiving, voids, refunds, and stock updates.
- Automated testing for application behavior, permissions, and tenant isolation.
- Modular architecture separating platform administration, merchant operations, POS, procurement, reporting, and billing.
Technology
Result / Impact
- Centralized POS, inventory, purchasing, receiving, subscriptions, and reporting in one platform.
- Connected sales and procurement activity directly with inventory movements.
- Established a secure SaaS foundation capable of supporting multiple independent merchants and users.
- Reduced fragmentation between cashier operations, stock management, purchasing, and merchant administration.
- Created a structured purchasing workflow from low-stock identification through purchase orders and goods receiving.
- Improved operational traceability through transaction history, stock movement records, and audit logs.
What I Learned / Design Decisions
- Designed critical sales and inventory operations around atomic transaction handling because POS, receiving, void, and refund actions directly affect stock and financial records.
- Enforced merchant isolation at the database level rather than relying only on application-level access checks.
- Separated platform administration from merchant operations so subscriptions, merchants, and platform settings remain distinct from day-to-day business workflows.
- Added a practical purchasing flow that connects low-stock products, buy lists, purchase orders, goods receiving, and inventory updates.
- Kept Retail and F&B workflows on a shared transactional foundation while adding table and order-status workflows where F&B operations require them.
- Used audit and operational event records to improve traceability for sensitive inventory and transaction changes.
Need a system like this?
I build custom operational systems for inventory, purchasing, sales, logistics, deliveries, and reporting workflows.
Discuss Your System