Cloud POS for Multi-Branch Retail
Budget: $250 – $750 USD
I operate several retail outlets and need a cloud-based POS platform that lets each branch run on its own register while remaining part of one central database. Stock must move seamlessly between branches, and I should be able to compare performance in real time from a single dashboard.
Core workflow
• Sales: fast, barcode-driven checkout with discounts, taxes and multiple payment methods.
• Purchases: a dedicated purchase module that stores supplier invoices, sets reminder dates and alerts me when an order is due.
• Reporting: instant P&L, overall sales, product-level sales, plus an automated end-of-day report that lands in my inbox without manual intervention.
• Inventory: live counts per branch, low-stock alerts and one-click transfers to another location.
Access requirements
• Front end must be responsive for both desktop (Windows & macOS) and smartphones; staff commonly switch between the two.
• No local servers – everything cloud hosted so I can add more than three branches without new hardware.
What I will provide
I currently use a basic system; I’ll share its code and workflows at project kick-off to give you a clear starting point and shorten the discovery phase.
Acceptance criteria
1. All sales, inventory and EOD data reconcile across branches after simulated heavy traffic.
2. Automated end-of-day reports arrive by email/SMS within five minutes of store close.
3. Purchase reminders trigger on the set dates and display in the back-office dashboard.
4. The same user account logs in from both a Windows desktop and an iPhone with full functionality.
Hand-off items
• Source code and database schema
• Admin and cashier user guides (PDF)
• Deployment script or container image
• Two weeks of post-launch support for tweaks and bug fixes
If this matches your expertise in modern web stacks (Laravel, Django, Node, Firebase, etc.), let’s discuss milestones and timelines—once in place, I can finally keep every branch on the same page without nightly spreadsheets.
Core workflow
• Sales: fast, barcode-driven checkout with discounts, taxes and multiple payment methods.
• Purchases: a dedicated purchase module that stores supplier invoices, sets reminder dates and alerts me when an order is due.
• Reporting: instant P&L, overall sales, product-level sales, plus an automated end-of-day report that lands in my inbox without manual intervention.
• Inventory: live counts per branch, low-stock alerts and one-click transfers to another location.
Access requirements
• Front end must be responsive for both desktop (Windows & macOS) and smartphones; staff commonly switch between the two.
• No local servers – everything cloud hosted so I can add more than three branches without new hardware.
What I will provide
I currently use a basic system; I’ll share its code and workflows at project kick-off to give you a clear starting point and shorten the discovery phase.
Acceptance criteria
1. All sales, inventory and EOD data reconcile across branches after simulated heavy traffic.
2. Automated end-of-day reports arrive by email/SMS within five minutes of store close.
3. Purchase reminders trigger on the set dates and display in the back-office dashboard.
4. The same user account logs in from both a Windows desktop and an iPhone with full functionality.
Hand-off items
• Source code and database schema
• Admin and cashier user guides (PDF)
• Deployment script or container image
• Two weeks of post-launch support for tweaks and bug fixes
If this matches your expertise in modern web stacks (Laravel, Django, Node, Firebase, etc.), let’s discuss milestones and timelines—once in place, I can finally keep every branch on the same page without nightly spreadsheets.
Related categories:
PHP
Software Architecture
MySQL
HTML
Web Development
Cloud
Database Management
API Development