Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Industry Playbooks 5 min read

Technology operations for retail businesses: a buying guide

A buying guide for retail technology in Bangladesh: operating model, requirements, vendor scorecard, pricing questions, pilot design and exit terms.

E
EncryptTechBD · 0 comments
Industrial building
Photo: Leeroy / StockSnap

Retail technology buying goes wrong when the demo becomes the requirements document. A point-of-sale system that looks fast on a clean counter can fail when the internet drops, a cashier gives a discount, a customer returns one item from a three-item bundle, or the owner wants yesterday's sales by branch before nine in the morning.

This buying guide is for a Bangladesh retailer with one or more outlets, a warehouse, an ecommerce store or a wholesale counter. It covers the operating model, requirements, vendor scoring, pricing questions, a pilot and the exit terms that protect the business.

Start with the operating model

Write down how the business actually runs before looking at software. The list should cover outlets and warehouses, sales channels, payment methods, delivery, returns, purchasing, stock transfers, staff roles, peak seasons and the reports the owner uses to make decisions.

Be specific about payments. A Bangladesh retailer may accept cash, cards, mobile financial services, bank transfer and credit. Each method needs a reconciliation path. A system that records the sale but cannot match the settlement creates work for the accounts team every day.

Requirements checklist

Must have

  • Offline billing with a safe sync when the connection returns.
  • Barcode scanning, product variants and price lookup.
  • Discount rules, price overrides and approval limits.
  • Returns, exchanges, refunds and warranty tracking.
  • Cash drawer, shift and end-of-day reconciliation.
  • Card and mobile financial service reconciliation.
  • Stock by location, transfers, purchase orders and stock counts.
  • Roles, permissions and an audit trail for sensitive actions.
  • Receipt printing and a daily sales report by outlet and user.
  • Data export in a usable format.

Useful, but not essential on day one

  • Loyalty, CRM and customer segmentation.
  • Ecommerce and marketplace integration.
  • Courier and delivery tracking.
  • Accounting integration.
  • Demand forecasting and automatic replenishment.
  • Gift cards, bundles and promotions.
  • Multi-currency or wholesale price lists.

Bangladesh-specific checks

  • Does the receipt print in Bangla and English?
  • How does the system behave during load-shedding or a broadband outage?
  • Can it reconcile bKash, Nagad, Rocket and card settlements separately?
  • Does local support exist, and what is the response time?
  • Can the owner see all branches without asking each manager for a report?

Build the shortlist

Shortlist three vendors that serve retailers of a similar size and complexity. Ask each for a demo using your own product data, your own discount rules and a return scenario. A demo on the vendor's sample data hides the integration work.

A vendor scorecard

Weight the criteria before the demos, then score each vendor from one to five with evidence. A weighted list keeps the conversation honest when one demo is more polished than the others.

  1. Fit with the operating model (25%): outlets, channels, payments, returns and stock rules.
  2. Integration and data (20%): ecommerce, accounting, courier, payment and reporting.
  3. Usability and speed (15%): cashier steps, offline behaviour and peak-hour performance.
  4. Support and local presence (15%): implementation, training, response and escalation.
  5. Security and controls (10%): access, audit, payment data and breach process.
  6. Commercials (10%): total cost over three years, not the first invoice.
  7. Exit and portability (5%): export, hardware reuse and termination assistance.

Pricing questions

  • Is the price per outlet, per user, per device or per transaction?
  • What is included in implementation, and what is billed as customisation?
  • Are scanners, printers, cash drawers and payment terminals included?
  • What do training, support and upgrades cost after year one?
  • Are payment gateway, SMS and messaging fees separate?
  • What happens when we add a branch or double transaction volume?
  • What is the notice period, and what does exit assistance include?

Ask for a three-year total cost with the assumptions written down. A low monthly fee with expensive customisation and weak support is not cheap.

Run a pilot

Pilot one outlet for 30 to 60 days. Run it in parallel with the current process for the first two weeks. Test a normal day, a peak day, a stock count, a return, a discount override and a connectivity failure. Reconcile cash and mobile financial services daily. Ask cashiers what slowed them down; their answer is more useful than a feature checklist.

Train cashiers on the new return, discount and offline flows, and update the incentive scheme if it rewards behaviour the system now blocks. A system that makes a cashier's day harder will be worked around within a week.

Define the success criteria before the pilot starts: transaction time, reconciliation variance, stock accuracy, downtime and staff adoption. If the pilot fails, stop. A failed pilot is cheaper than a failed rollout.

Integration and data ownership

Decide which system owns the product, price and stock record. Two systems that both claim ownership will drift. Use APIs or scheduled files with monitoring, and define what happens when a sync fails. Keep a reconciliation report that compares stock, sales and payments across systems.

The retailer should own the data. Confirm that product, customer, order and payment records can be exported in a standard format, and that the vendor will assist with a migration if the relationship ends.

Board questions before signing

  • Which decision will this system improve, and how will we measure it?
  • What happens on the busiest day of the year?
  • Who is accountable for stock accuracy and cash reconciliation?
  • What is the cost of the system over three years, including support and change?
  • How do we exit, and what do we keep?
  • What evidence from the pilot justifies the rollout?

Where this fits in our work

If you need help selecting or integrating retail systems, start with Operations. The pricing page explains scope. For the omnichannel view, read the omnichannel retail operations guide.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes