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

POS system requirements for retail: comparing six operating models

Six retail POS operating models compared on offline resilience, stock control, payments, integration and support, with guidance on when each fits.

E
EncryptTechBD · 0 comments
Colleagues laughing during a meeting at a table
Photo: Direct Media / StockSnap

A POS shortlist usually starts with features and ends with a demonstration. The more useful comparison is by operating model, because the model determines what happens when the internet drops, how stock stays accurate across branches, who owns the data and how much support you will need after the vendor's trainer leaves. Two systems with similar feature lists can behave very differently on a Friday evening.

This comparison is for a retailer in Bangladesh choosing between an on-premise system, a cloud product, an ecommerce add-on, an ERP module, a custom build or a managed retail suite. It focuses on the operating consequences rather than the sales demo.

ModelBest fitOffline behaviourStock modelIntegrationMain risk
On-premise standaloneSingle store, stable assortmentStrongLocalLimitedHardware failure, little remote support
Cloud POS with offline modeGrowing single or multi-storeGood if designedCentralGoodOffline gaps, connectivity
Ecommerce platform add-onD2C brand with physical pickupVariesShared with onlineStrong within platformChannel rules, add-on limits
ERP-integrated POSMulti-branch with finance integrationDeployment-dependentCentral ERPStrongImplementation weight
Custom POSUnusual workflow or pricingDesignedDesignedDesignedBuild and maintain
Managed retail suiteChain with standard processesVendor-dependentCentralBroadContract lock-in

On-premise standalone POS

The database and application run in the store. Billing keeps working when the internet fails, which matters in locations with unstable connectivity. Stock is local unless a separate sync process exists, so multi-branch visibility is weak. Hardware failure can stop trading, and remote support depends on someone being able to reach the machine. Fit it to a single store with a stable assortment and an on-site person who can restart the system.

Cloud POS with an offline mode

The application runs in the cloud and the till caches enough data to keep billing during an outage. This is the most common choice for a growing retailer, but the quality of the offline mode varies. Ask what can be sold offline, how stock is reconciled when the connection returns, and what happens to a payment taken offline. Test a full day without connectivity before signing.

Ecommerce platform POS add-on

If the business already sells on an ecommerce platform, its POS add-on can share products, stock and customers with the website. This reduces duplicate entry and is useful for pickup, pop-up shops and a single brand store. The limits appear when the retail workflow differs from the online one: returns, exchanges, credit sales, weighed goods and multi-branch transfers may need workarounds.

ERP-integrated POS

The POS becomes a front end to the ERP, so sales, stock, purchasing and accounting share one ledger. This is attractive for a multi-branch retailer with an existing ERP and a finance team that needs daily consolidation. The cost is implementation weight: master data, tax rules, user roles and store configuration all need careful setup. A weak ERP implementation becomes a weak POS.

Custom POS

A custom build fits a workflow that no product covers, such as a specialised pricing model, a service counter or a repair workflow. It gives control over the interface and the data model. It also creates a product to maintain: updates, payment changes, hardware compatibility and support. Choose it when the workflow is a genuine differentiator, not because the demo of a standard product was imperfect.

Managed retail suite

A managed suite bundles POS, stock, purchasing and reporting with vendor support. It suits a chain that wants one throat to choke and standard processes across branches. The trade-off is dependency: migration, data export and per-module pricing need to be agreed before signing. Ask what happens when a branch closes, a new module is needed or the vendor changes ownership.

Criteria that matter more than features

  • Offline billing: what still works without internet, and how the sync is reconciled.
  • Stock accuracy: locations, transfers, counts and adjustment reasons.
  • Payments: cash, cards, mobile financial services and split tender, with a reconciliation report.
  • Returns and exchanges: linked to the original receipt, with a reason code.
  • Purchasing: suppliers, purchase orders, goods received and landed cost.
  • Reporting: daily sales, margin, stock ageing and branch comparison.
  • Data export: can you take products, customers and transactions with you?
  • Support: local presence, response terms and spare parts.

Bangladesh-specific questions

Ask how the system behaves during a power cut, whether it can print a Bangla receipt, how mobile financial service payments are reconciled, and who provides on-site support outside Dhaka. Check barcode quality on local packaging and confirm that the hardware can be repaired locally. A cloud-only system with no offline mode is a risk in any location where connectivity is not guaranteed.

Choose each model when

  • On-premise: one store, unreliable connectivity and a capable on-site operator.
  • Cloud with offline: a growing retailer that needs central stock and remote visibility.
  • Ecommerce add-on: the online store is the primary channel and retail is secondary.
  • ERP-integrated: finance and stock already run on an ERP and consolidation matters.
  • Custom: the selling workflow is genuinely different and you can maintain software.
  • Managed suite: a chain wants standard processes and a single support contract.

A decision path

Document the selling model, rank the three failure modes that would hurt most, and shortlist two operating models rather than six products. Run a pilot in one store for a full stock cycle. Compare the evidence, not the demo: closing reports, stock variance, payment reconciliation and the time to train a new cashier. Agree data export and exit terms before signing.

Red flags

No offline plan, no stock adjustment reasons, no payment reconciliation, no data export, per-terminal fees that punish growth and support available only by chat. A POS that cannot explain yesterday's cash is not ready for a busy shop.

We build retail and order systems under Commerce Systems. The pricing page explains how implementation and support are scoped. For the full requirements list behind this comparison, read POS system requirements for retail: a buying 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