A POS system is usually bought at the counter and judged in the back office. The real test is whether the stock count matches the shelf, whether the day's cash reconciles and whether the system still works when the internet drops during a busy evening.
This guide is for a retailer in Bangladesh moving from a cash drawer and a spreadsheet, or replacing a POS that no longer fits. It sets out the requirements to define before you shortlist vendors, a scorecard for comparing them and the questions that reveal the real cost.
Start with the operating model
Write down how the business actually sells before looking at software:
- Stores and counters: one outlet, several branches, a warehouse counter or pop-up sales.
- Channels: walk-in, phone orders, WhatsApp, Facebook, a website or a delivery partner.
- Products: simple SKUs, variants such as size and colour, weighed goods, bundles or serialised items.
- Payments: cash, cards, mobile financial services, split payments and credit sales.
- Fulfilment: takeaway, home delivery, pickup, exchange or repair.
- Staff: cashiers, supervisors, stock staff and owners who need different levels of access.
- Tax and reporting: what the accountant needs at month-end, and what the tax authority requires.
Resolve disagreements about returns before the demo; software makes an undefined process faster, not clearer.
Functional requirements
Selling and payments
- Fast barcode scanning and keyboard entry for items without a barcode.
- Price lookup, discounts, promotions and supervisor approval for overrides.
- Split payments across cash, card and mobile financial services.
- Returns and exchanges linked to the original receipt, with a reason code.
- Receipt printing in Bengali and English, plus an electronic receipt option.
- Cash drawer opening, closing and shift handover.
Inventory
- Stock by store and location, with transfers between branches.
- Purchase orders, goods received notes and supplier returns.
- Stock counts and adjustment reasons, not just an editable quantity.
- Batch or expiry tracking if the product requires it.
Customers and credit
- Customer profiles, phone lookup and purchase history.
- Credit limits, due dates and statement generation for account customers.
- Consent and retention rules for personal data.
Reporting and control
- Daily sales by store, cashier, product and payment method.
- Gross margin, stock value and shrinkage reports.
- Audit log of price changes, voids, refunds and permission overrides.
- Export to CSV or API access for the accountant and BI team.
Technical requirements
- Offline-first operation: the till must keep selling when the connection fails and sync when it returns.
- Conflict handling: a clear rule for what happens when two stores sell the same item while offline.
- Hardware compatibility: receipt printers, barcode scanners, cash drawers, weighing scales and card terminals.
- Network design: a business-grade router, a backup connection and a supported local setup.
- Integrations: ecommerce, accounting, payment providers, delivery partners and payroll.
- API and webhooks: documented, versioned and supported, not an afterthought.
- Data ownership: full export of transactions, customers and stock at any time.
- Backup and recovery: cloud backup, restore testing and a stated recovery objective.
Security and payment compliance
Card payments can bring the POS into the scope of the PCI DSS framework. Ask how the payment flow is designed: whether card data ever touches the POS, whether the terminal uses point-to-point encryption or tokenisation, and which party is responsible for each control. Confirm the scope with your acquirer rather than relying on a vendor's marketing page.
Staff access should be role-based, with individual logins, strong administrator authentication and an audit trail for voids, refunds and price changes. Encrypt data in transit and at rest, expire sessions on lost devices, and define how customer data is retained and deleted. For an ecommerce integration, review the API credentials and permissions.
Vendor scorecard
Score each shortlisted vendor from 1 to 5 against weighted criteria. Adjust the weights; the point is to make trade-offs explicit.
- Fit to the operating model (25): stores, variants, returns, credit sales and payments.
- Offline reliability (15): demonstrated during a pilot, not just described.
- Payment and compliance design (15): clear scope, tokenisation and reconciliation.
- Integrations and data export (15): ecommerce, accounting and BI access.
- Support and local presence (10): language, hours, escalation and on-site capability.
- Security and administration (10): roles, audit, encryption and access review.
- Total cost over three years (10): licence, hardware, payments, implementation and support.
Pricing questions
POS pricing is rarely one number. Ask for a three-year total cost model with these lines:
- Licence per store, per terminal or per user, and the minimum commitment.
- Payment processing fees and who bears them.
- Hardware purchase or lease, including printers, scanners and terminals.
- Implementation, data migration, configuration and training.
- Support tier, response time and the cost of after-hours help.
- Custom reports, integrations and API access.
- Exit, data export and early termination.
Do not accept a per-terminal price without the payment and support lines. The cheapest licence can be the most expensive system once the transaction fees and integration work are included.
Run a pilot
- Choose one representative store, not the quietest one.
- Run in parallel with the current process for two to four weeks, including a weekend and a stock count.
- Measure queue time, stock accuracy, sync failures, refund handling and closing time.
- Ask cashiers to log every workaround in a shared sheet.
- Test an internet outage, a card terminal failure and a return without a receipt.
- Review the vendor's support response against the agreed service level.
A pilot should produce configuration changes and a rollout decision, not just a yes.
Plan the exit before you sign
Contracts end, vendors change direction and businesses grow. Confirm that you can export all transactions, customer records, stock and configurations in a usable format. Clarify who owns the hardware, whether the payment provider is separate from the POS, how much notice is required and what migration support is included. A system that cannot be left is a system that cannot be negotiated with.
Bangladesh-specific checks
Confirm Bengali receipt support, the tax configuration your accountant needs, and the payment methods customers use. Test the system on the mobile networks and devices in the store, not the vendor's demo Wi-Fi. Check multi-branch and warehouse support, and that help is available during trading hours. If orders arrive through Facebook or WhatsApp, confirm how they enter the POS and who reconciles them.
Metrics after rollout
Track billing time per sale, queue length at peak, stock accuracy, shrinkage, sync failure rate, refunds without receipt, closing time, support tickets per store and the share of sales by payment method. Review the numbers monthly with the store manager and accountant.
Where this fits in our work
If you need a POS that fits a multi-channel retail operation, or an integration between the till and the systems behind it, start with Operations Systems and review the engagement options on our pricing page. For the stock side of the same decision, read the inventory synchronisation cost guide.
Sources
- PCI Security Standards Council, accessed 17 November 2026.
- NIST SP 800-63B, Digital Identity Guidelines, accessed 17 November 2026.
- Shopify Help Center, "Sell in person", accessed 17 November 2026.
- Microsoft Learn, "Online and offline point of sale (POS) operations", accessed 17 November 2026.
- GS1, "Barcodes", accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.