You bought a POS system off the shelf. It worked fine when you had one location and a simple product catalogue. Now you have multiple branches, complex pricing rules, and your staff spends half their time working around the system instead of working in it.
This is the POS ceiling. Every business that grows beyond a certain complexity hits it. The off-the-shelf system assumes your business works like every other business. When yours does not, you start building workarounds. Manual calculations. Side spreadsheets. Paper processes to supplement the digital system.
I built a custom point-of-sale system for a recycling company that processes 5,000+ transactions daily across 7 branches with 350 employees. Here is what I learned about when custom POS makes sense and what it actually involves.
Signs Your POS System Is Holding You Back
Your pricing does not fit in the system. Your business prices by weight, by volume, by quality grade, by customer relationship, or by some combination that changes daily. Your POS has a "price" field and a "discount" button. Everything else is a workaround.
You have multi-branch problems. Inventory across multiple locations does not sync in real time. Transfers between branches require manual paperwork. Reporting across all branches requires exporting data and combining it in a spreadsheet.
Your transactions are not standard retail. You are not scanning a barcode and printing a receipt. Your transactions involve weighing, grading, splitting, combining, or processing items. The transaction flow your business uses does not match any template your POS provides.
Cash management is complex. Your business handles significant cash volumes. You need cash-in, cash-out, float management, supplier payments from the till, and end-of-day reconciliation that your POS does not support.
Reporting is inadequate. You need to answer questions your POS cannot: "What is our margin per product per branch per week?" "Which supplier gives us the best quality-to-price ratio?" "How much did each cashier process today?" You end up exporting to Excel to get these answers.
You have outgrown the vendor's support. Your needs are outside the vendor's roadmap. You have requested features that "will be added in a future update" for two years. Support tickets go unanswered because your use case is too niche for a product serving thousands of generic customers.
Why Off-the-Shelf POS Systems Have Limits
POS software is built for the most common use cases. Retail stores selling products at fixed prices to walk-in customers. Restaurants with menu items and table management. Service businesses with appointment-based billing.
If your business operates differently, you are using a tool designed for someone else. And no amount of configuration, plugins, or workarounds will change its fundamental architecture.
The core limitations:
Fixed transaction models. Most POS systems assume: customer selects items, system calculates total, customer pays. If your transaction involves weighing, grading, multi-step pricing, approval workflows, or split processing, the system fights you.
Rigid data models. The POS defines what a "product" is, what an "order" is, and what a "customer" is. When your business has its own definitions (a "load" instead of an order, a "supplier" who is also a customer, a "material" that is not a product), you spend all your time mapping your reality into someone else's categories.
Integration walls. Off-the-shelf POS systems integrate with a short list of accounting and e-commerce tools. If your business runs on Sage Pastel, uses a custom ERP, or needs data flowing into an operational dashboard, you are stuck with CSV exports.
What a Custom POS Looks Like
A custom POS is a web application built for your specific transaction flow, your specific data model, and your specific operational requirements.
It runs in a browser. No special hardware required (beyond a computer, a scale if you weigh things, and a receipt printer if you print receipts). New terminals are a browser tab, not a R15,000 POS device.
It does exactly what your business needs. The transaction flow matches how your business actually operates. The fields are your fields. The pricing logic is your pricing logic. The reports answer your actual questions.
It scales across branches. Multiple locations use the same system. Data is centralized. Inventory, pricing, and reporting work across the entire operation in real time.
It integrates with your other systems. Accounting. ERP. Banking. Reporting dashboards. The POS is not an island. It is part of your operational stack.
What It Costs and How Long It Takes
Custom POS development is a significant investment. Here are honest ranges.
A focused, single-location POS with basic transaction processing, inventory, and reporting: R100,000 to R250,000. Timeline: 6 to 12 weeks.
A multi-branch POS with complex pricing, cash management, supplier payments, user permissions, and operational reporting: R300,000 to R800,000. Timeline: 3 to 6 months.
A full operational platform where the POS is one module alongside inventory management, supplier management, employee management, and financial reporting: R500,000 to R1,200,000+. Timeline: 6 to 12 months (often built in phases).
The cost comparison is not "custom POS vs. off-the-shelf POS license." It is "custom POS vs. the ongoing cost of workarounds, errors, manual processes, and the opportunities you cannot pursue because your systems cannot support them."
The Recycle POS Story
I built a custom POS for a recycling company. The business buys recyclable materials (paper, plastic, metal, glass) from suppliers, processes them, and sells to manufacturers. Seven branches. 350 employees. 5,000+ transactions processed daily.
No off-the-shelf POS could handle their transaction model. Every transaction involves weighing material, grading it for quality, pricing it based on material type and quality grade (prices that change weekly based on commodity markets), and paying the supplier in cash on the spot.
The system handles:
- Point-of-sale transactions with weighing integration
- Dynamic pricing by material, grade, and branch
- Cash management (float, supplier payments, end-of-day reconciliation)
- Multi-branch inventory tracking
- Supplier account management
- Operational reporting across all branches
- User permissions (cashiers, branch managers, head office)
This was not a quick project. It was built iteratively, starting with the core transaction flow and expanding module by module as the business identified what they needed next.
Before You Build: Questions to Answer
If you are considering a custom POS, work through these questions first.
Can you describe your transaction flow in detail? Not "we sell stuff." The exact steps, the decision points, the exceptions, the edge cases. If you cannot describe it, a developer cannot build it.
What reporting do you need? Not "everything." The specific questions you need answers to, daily, weekly, and monthly. These drive the data model.
How many locations and users? This affects architecture, hosting, and cost.
What do you integrate with? Accounting, banking, scales, printers, barcode scanners. Each integration is a piece of the puzzle.
What is your budget and timeline? Be honest about both. A good developer will tell you what is achievable within your constraints and suggest a phased approach if the full vision exceeds the budget.
The Short Version
Off-the-shelf POS systems work for standard retail. When your business has complex pricing, non-standard transactions, multi-branch operations, or specific operational requirements, a custom POS becomes the better investment.
It costs more upfront. It saves more long-term. And unlike a subscription to software that almost does what you need, it actually does what you need.
If your POS system is fighting you instead of helping you, let us talk about what a purpose-built system looks like.