Shopify POS in India: What Works and What Does Not

Most Shopify POS material is written from a US perspective, and it describes an experience that does not fully transfer. Shopify's own card readers, its first-party payment processing, and the hardware ecosystem around them are shaped by markets where Shopify Payments has deep support. India is not one of those markets in the same way.

That does not mean Shopify POS is a bad choice here. It means the evaluation is different, and the parts you need to verify are different. This is the local picture, including the gaps.

What genuinely transfers

The core proposition is unaffected by geography, and it is the actual reason to consider Shopify POS.

Retail and online run on one system. One catalogue, one customer record, one inventory pool, one set of reports. A sale in the shop decrements the same stock your website sells from. A customer who bought online and walks in is the same customer, with their history visible.

For a retailer who also sells online, this removes an entire category of daily work — the reconciliation between two systems that each think they are authoritative. That benefit is identical in Mumbai and Manchester, and it is what should drive the decision.

The 2026 releases strengthened this further with mixed fulfilment, letting one order combine ship-to-home and in-store pickup items, and support for running multiple legal entities from a single store rather than one Shopify instance per entity. The second is genuinely useful for Indian groups operating retail and online under different companies, which is a common structure.

Payments: the first thing to verify

This is where the divergence is sharpest.

In markets with full Shopify Payments support, the flow is seamless: Shopify's own reader, Shopify's processing, everything settled and reported in one place. In India, that first-party path is not the default assumption, and retailers typically operate differently.

The common patterns:

A separate card terminal alongside Shopify POS. The customer pays on your existing terminal, the sale is recorded in Shopify POS as the corresponding payment type. This works and is widely done. The cost is that settlement and reconciliation happen in two systems rather than one, which erodes some of the unification benefit.

UPI and QR-based payment, recorded similarly. Given UPI's dominance in Indian retail, this matters more here than any guide written elsewhere will tell you, and how gracefully your setup handles it is worth testing specifically.

Cash, which the 2026 releases improved with a built-in cash ledger handling tracking, reconciliation and reason codes on the device. For cash-heavy Indian retail this is a genuine improvement over informal till management.

Verify, before committing: which processors are supported, what happens to reconciliation when payment is taken outside Shopify, and whether the reporting you need still works when payment data arrives from elsewhere.

GST is the largest gap

Be direct about this one, because it is the most common reason Indian retailers reject Shopify POS after evaluating it.

Shopify calculates tax and can be configured with GST rates. What it does not do natively is produce the full GST-compliant invoice an Indian business needs — correct format, HSN codes, the split between CGST, SGST and IGST presented as required, and a numbering scheme that satisfies filing.

The routes available:

Most retailers land on an integration with the accounting software they already use, because filing happens there regardless. The point to internalise is that this is a requirement to solve during implementation, not a gap discovered afterwards — and it should be part of the cost calculation when comparing Shopify POS against a local POS that handles GST natively.

Hardware, verified locally

Do not order hardware from a compatibility list written for another market.

The questions that matter:

• Is the device sold in India, with support and replacement? A reader with no local supply chain is a single point of failure with a long lead time.
• Does it work with your chosen payment path? Hardware and processing are coupled, and this is where the market difference bites.
• Receipt printer, cash drawer, barcode scanner — these are more standardised and generally less problematic, but confirm the specific models.
• What is the fallback when a device fails? Every counter needs a way to keep trading.

The connectivity item deserves emphasis. Retail locations in India vary enormously in connection quality, and offline behaviour should be tested under realistic conditions rather than trusted from a feature list.

When a local POS is the better answer

An honest comparison needs this section.

If you are a purely offline retailer with no online presence and no plan for one, Indian POS systems built for local billing, GST and hardware will generally serve you better and cost less. The unification benefit — the entire reason to choose Shopify POS — is worth nothing to you.

If you have complex local compliance requirements, sector-specific billing rules, or need deep integration with an Indian accounting or inventory package, a system built for that market is likely to fit better than Shopify plus integrations.

If you are price-sensitive with many small outlets, the per-location Pro pricing compares unfavourably with local systems charging per terminal or flat.

Shopify POS wins when online and offline are both real parts of your business. That is the honest boundary.

The cost model in practice

POS Lite is included with your Shopify plan. POS Pro is charged per location.

The consequence is that the calculation is about footprint, not headcount. Staff are free. Additional tills within one location are free. Each new location is not. A business with one shop and eight staff pays once; a business with four kiosks pays four times regardless of how quiet they are.

Model this against your actual expansion plan, and include the GST solution and any payment integration in the total. Comparing Shopify POS Pro against a local POS on licence fee alone will mislead you in both directions.

Staff, training and the adoption risk

The failure that sinks POS projects in India is rarely technical. It is that the counter staff do not use the system the way it was designed, and the data quality degrades until the reports stop being trusted.

This risk is higher than in markets where staff have usually encountered similar systems before. If your team has been running a till that does one thing well, moving to a system that also manages customers, inventory and omnichannel orders is a genuine change in job description, not a software update.

What reduces the risk:

Configure permissions before launch, not after. Decide which roles can discount, refund, open the drawer and edit inventory. Retrofitting this onto a store where everyone shares a manager login is much harder than setting it up on day one, and shared logins destroy the per-staff attribution that makes the reporting worth having.

Train on the awkward transactions, not the easy ones. Everyone can process a straightforward sale after ten minutes. The training that matters covers returns, exchanges, the online customer walking in, and what to do when the connection drops.

Give it a fallback everyone knows. Staff who are unsure what to do when something fails will invent a workaround, and the workaround becomes permanent. A written, practised fallback prevents a year of unreconcilable entries.

Expect a slower first fortnight and staff it accordingly. A queue forming while someone learns the interface is how a good system acquires a bad reputation internally, and internal resistance is much harder to reverse than a configuration error.

A sensible evaluation sequence

1. Confirm the unification benefit applies to you. If you do not sell online, stop here and evaluate local systems.
2. Solve payments on paper before anything else — processor, hardware, reconciliation.
3. Decide the GST route and cost it.
4. Trial with one location, running your five most common awkward transactions.
5. Test offline behaviour and a device failure.
6. Then decide about rolling out.

Step four matters more than any feature comparison. Write down the transactions your staff currently handle awkwardly — the returns, the exchanges, the customer who bought online — and check each one in a trial. Those are what you are buying a fix for.

For the full platform picture, see POS and operations. GST invoicing specifics and payment methods for Indian stores are covered in the same archive and in checkout and payments.