Adobe Commerce development
Storefront design
Performance & SEO
AI & agentic commerce
Release tracker
Magento does not include a point-of-sale (POS) system, so omnichannel retailers choose between three routes: a POS extension that runs on Magento itself, a standalone retail POS integrated with Magento, or a POS that comes with your ERP. Magento-native POS options keep one database for products, customers and stock, which suits retailers with a handful of stores. Standalone and ERP-led POS systems suit larger chains with dedicated store operations, at the cost of an integration to build and maintain. Whatever you pick, judge it on offline mode, inventory sync, payments and hardware before features.
The three main options
| Option | How it works | Fits | Trade-offs |
|---|---|---|---|
| Magento-native POS extension | A POS app (often a web or PWA app on a tablet) that reads and writes directly to Magento: same catalog, customers, prices and MSI stock | Brands with a few to a few dozen stores, where web and store share products and promotions | Depends on Magento's availability and performance; check offline mode carefully; extension must keep up with Magento upgrades |
| Standalone retail POS, integrated | A dedicated retail POS runs the stores; middleware syncs products, stock, customers and orders with Magento | Larger chains, franchise setups, stores with specialist workflows | Two systems of record; integration to build and monitor; promotions may differ between channels |
| ERP-led POS | The POS module of your ERP handles stores; Magento integrates with the ERP | Retailers whose ERP already runs finance, stock and stores | Store features depend on the ERP vendor; Magento integration goes through the ERP |
Adobe previously offered Store Fulfillment for Adobe Commerce for in-store pickup workflows. Adobe's discontinued-products page says it was discontinued in February 2024 and points merchants to partner solutions on the Commerce Marketplace. Magento's own in-store pickup delivery method, configured on MSI sources, remains available.
Examples of POS products marketed for Magento include Magestore (which lists a POS on the Adobe Commerce Marketplace) and ConnectPOS (which offers a Magento POS on its own site), and other vendors list POS modules on the Marketplace too. We have not tested or verified their features and do not rank them here: features, pricing and version support change, so check each vendor's current compatibility with your Magento version against the criteria below.
Selection criteria
| Criterion | What to check | Why it matters |
|---|---|---|
| Offline mode | Can it take card and cash sales with no internet? How are sales queued and synced? What happens to stock and promotions offline? | Store Wi-Fi fails. A POS that stops selling costs more than any feature gap |
| Inventory sync | Does each store map to an MSI source? How fast do store sales update online salable quantity? Can stores see other locations' stock? | Click-and-collect and "available in store" only work with near-real-time stock |
| Payments | Which card terminals and payment providers are supported? Is card data kept out of the POS (for example with point-to-point encryption)? Split tenders, gift cards, refunds to original method? | Payments decide your PCI DSS scope and your fees |
| Hardware | Supported tablets and operating systems, receipt printers, barcode scanners, cash drawers, customer displays | Hardware lists are often narrower than the brochure suggests |
| Customers and loyalty | Same customer account online and in store? Loyalty points earned and redeemed in both? | A unified customer is the main reason to go omnichannel |
| Returns and exchanges | Can online orders be returned in store, and the reverse? Do refunds and stock go back correctly? | Cross-channel returns are where most integrations break |
| Store operations | Staff roles, shift and cash management, end-of-day reports, multi-store and multi-currency | Store managers use these every day |
| Upgrade path | Supported Magento and Adobe Commerce versions; release history; how it behaves on Adobe Commerce as a Cloud Service if you plan to move | An unmaintained POS can block your next upgrade |
Run a pilot in one store for several weeks, including a deliberate offline test and a busy trading day, before rolling out.
Integration patterns
Pattern 1: Magento as the hub
The POS reads and writes Magento directly. Each store is an MSI source; store sales create orders in Magento (often marked with a POS channel), and stock is deducted from the store's source. This is the simplest model because catalog, prices, customers and promotions are shared. Our Magento inventory management guide explains how sources and stocks should be set up for this.
Pattern 2: POS and Magento synced by middleware
The POS owns store transactions and store stock; Magento owns web orders. Middleware syncs:
- Products and prices: from the product master (PIM, ERP or Magento) to both.
- Store stock: POS to Magento, as quantities per store source, every few minutes.
- Customers: matched on email or a loyalty ID, in both directions.
- Click-and-collect orders: Magento to POS, with status back to Magento when collected.
Pattern 3: ERP as the hub
The POS and Magento each integrate with the ERP, which owns stock, finance and often customers. This avoids a direct POS-to-Magento link but means freshness depends on the ERP's sync frequency. Plan it together with your Magento ERP integration.
Loyalty and the unified customer
The business case for omnichannel POS usually rests on knowing the customer in both channels: points earned in store and spent online, purchase history for staff, and one marketing profile. Decide where loyalty balances live and make the POS and Magento read the same balance in real time, or one channel will show stale points. Our guide to ecommerce loyalty programs covers the options on Adobe Commerce.
Payments and compliance
Card-present payments usually run through a payment provider's terminal, so card data goes from the terminal to the provider and does not touch the POS app. That keeps PCI DSS scope smaller. Confirm which terminals and providers the POS supports in each country you trade in, and whether online and in-store payments can use the same provider for unified reporting and refunds. This is general information, not compliance advice; your payment provider and QSA can confirm your scope.
FAQ
Does Adobe Commerce have a built-in POS?
No. Adobe Commerce and Magento Open Source support in-store pickup through MSI sources, but a POS comes from an extension, a standalone POS vendor or your ERP.
Can a web-based POS work offline?
Some can, by caching the catalog and queuing sales locally. Test it: switch off the network during a pilot and check card payments, receipts, stock and the sync afterwards.
Should store stock be visible online?
If you offer click-and-collect or "check store availability", yes, but only when stock syncs quickly. Otherwise use a buffer, such as a per-source safety stock, to avoid selling the last unit twice.
Next step
The POS decision is really an integration decision. Mistri's Magento extension development team builds POS and middleware integrations, and our Adobe Commerce development work covers the MSI, pickup and customer setup that a good omnichannel POS depends on.
Sources
Store Fulfillment for Adobe Commerce, discontinued (Adobe Experience League); In-store delivery (Adobe Experience League); Stocks and sources (Adobe Experience League); PCI Security Standards Council document library; Magestore POS Lite listing (Adobe Commerce Marketplace).
