Magento POS systems and store data in 2026
Connect counter sales to a Magento catalogue without conflicting stock. Compare POS connection methods, order visibility and cross-channel returns.
- Published
- Last updated
A Magento POS system connects counter sales to your Magento catalogue through a third-party extension or an external point of sale (POS) integration. Choose the connection by who controls stock and how sales reach the website when a till loses its connection.
Magento-based tills suit retailers who want Commerce to hold their sales records. An external POS suits a retailer keeping an established store system, provided its connector carries orders and returns as well as quantities.
What a Magento POS connection provides
Magento Open Source and Adobe Commerce need an added POS product for counter selling. A vendor’s description of its POS as Magento-native means it integrates with Magento. It does not make that product an included Adobe till.
The till is the screen staff use to scan products and complete a sale. A payment terminal authorises card payments. The integration moves product and transaction data between the till and Commerce. A successful card payment alone does not prove that website stock changed.
This guide covers Magento 2 and the extension-based Adobe Commerce deployment model. Adobe Commerce as a Cloud Service has a different API and extension model. A Magento 2 module’s compatibility statement does not establish support for that service.
Compare the other platform POS systems when your decision also includes changing the online platform.
Map products, locations and stock authority
Give each shared field one system that controls changes, then define where those changes go. A typical Magento-led setup uses the following map.
| Shared data | System controlling changes | Direction and matching rule |
|---|---|---|
| Products and variants | Magento catalogue | Send each sellable variant’s SKU to the till. Keep its parent product association. |
| Prices and discounts | Magento pricing rules | Send the right website, customer group and currency context to POS. Record any authorised counter discount on the order. |
| Tax | Store tax configuration | Apply the configured tax treatment to each sale and preserve the charged amount on the receipt. |
| Physical quantities | Magento source inventory, or the existing inventory system | Assign one writer for each location. Map the POS outlet to its source code. |
| Orders and refunds | Commerce sales records, with linked POS references | Send counter orders into Commerce. Keep the receipt, order and credit memo identifiers connected. |
A stock keeping unit (SKU) identifies a sellable item. A navy shirt in medium needs its own variant identifier. Deducting stock from the shirt’s parent record leaves the selected size’s availability wrong.
Adobe’s inventory API documentation distinguishes physical sources from stocks that supply website sales channels. Website availability uses salable quantity, which also accounts for reservations. A till’s physical count and the website’s available quantity can therefore differ legitimately.
When a website order is submitted, Commerce reserves its quantity. Shipment then deducts the physical source quantity and clears the corresponding reservation. Route counter sales through the supported POS order process so a separate stock adjustment does not deduct the same sale twice.
During an outage, a till has an older view of stock. Two disconnected tills can sell the same last unit before either reports its sale. Use separate outlet allocations or a stock buffer where that risk exists. Define how the integration flags a rejected order instead of silently replacing the latest quantity with an older count.
Evaluate connection methods and running costs
Choose a Magento extension when Commerce owns the catalogue and sales records. Use a connector when an existing POS remains the store’s main system. Custom application programming interface (API) work suits a data flow that supported products cannot carry.
| Connection | Objects and permissions | Failure recovery and maintenance |
|---|---|---|
| Magento POS extension | Catalogue, outlet stock, customers, orders and credit memos. Give cashiers outlet-specific access. | Use the product’s offline order queue. Retest the module after Magento and payment changes. |
| External POS with connector | Map variant SKUs, locations, price context, orders and refunds. Grant only the required Commerce API resources. | Retain failed events and retry with a stable transaction identifier. Monitor both products’ version changes. |
| Custom API integration | Build and authorise each required catalogue, inventory and sales operation. Customer access needs its own permissions. | Own retry logic, duplicate prevention and reconciliation. Budget for ongoing development and monitoring. |
Adobe’s authentication guidance separates integration access from customer access. A shopping assistant’s ability to read product stock does not justify permission to read every customer’s orders.
Magestore for a Magento-led retail operation
Magestore is the best fit here for a retailer keeping catalogue and counter operations within Magento. Its Magento POS page lists direct synchronisation and Magento 2.4.9 compatibility. Magestore also sells a separate Adobe Commerce POS product. Select the edition-specific product for the store being connected.
Magestore documents offline selling and an online-purchase, in-store-return workflow. Local checkout data supports sales during disconnection. Website availability catches up after those sales reach Commerce, so an offline till cannot guarantee a current website count.
Magestore names Australian retail customers on its product page. Its commercial model includes subscriptions and one-time purchasing, with pricing requested for the chosen package. Include implementation and payment integration in the total, alongside any hardware and ongoing support.
Webkul for a module-led implementation with developer support
Webkul Point of Sale is the best fit here for a retailer wanting a Magento module and a development team to manage it. Its listing covers Magento 2.4.x, source-based outlet inventory and offline orders. The Adobe Marketplace listing identifies it as a third-party extension.
Webkul documents automatic order synchronisation after connectivity returns. Its changelog includes order returns and credit memos. The setup must carry the original order reference through the refund and reconcile the correct source quantity.
Webkul’s web POS supports multiple currencies. Australian deployment still needs an Australian payment arrangement and the store’s goods and services tax configuration. Its listing prices the module separately from optional installation and support. An extension purchase alone does not establish an Australian terminal connection.
For either option, compare the complete cost over the same operating period. Include software, additional registers or outlets, integration work, hardware, payment fees and upgrade support. Run the Australian tax and payment scenarios below against the exact package before buying hardware.
A Magento QuickBooks POS integration is a different question from sending accounting entries to QuickBooks. Intuit discontinued QuickBooks Desktop Point of Sale and its connected services in 2023. For a new setup, choose supported POS software first and treat accounting export as a separate data flow.
Keep online shopping answers consistent with counter sales
A counter sale must reach the website’s stock calculation before a shopping assistant can use its new availability. The sequence runs from the POS order to Commerce inventory, then to the catalogue connection the assistant reads. Each delayed step extends the period when an online answer can use the previous count.
For example, suppose the last medium navy shirt sells in-store. After the POS sale is accepted and processed, the website must stop presenting that variant as available. An assistant using an earlier product feed still needs its next stock update. Immediate POS synchronisation does not make a scheduled feed immediate.
Keep availability and order support separate. A receipt must identify the original Commerce order or map to it reliably. A shared email address alone is insufficient authority to disclose order details. Match the customer’s authenticated access or approved order-verification process before displaying a counter purchase online.
A return also has separate financial and inventory decisions. Adobe’s refund API guidance distinguishes refund operations by the original payment method. Return sellable goods to the mapped stock location only after inspection. A damaged shirt can receive a refund while remaining unavailable for resale.
This shared order history is part of omnichannel commerce: the customer can move between counter and website without losing the purchase record.
Validate a sale, a return and a failed sync
Validate the complete sale-to-availability path in a test environment before connecting live outlets. Use a test payment method and a dedicated stock location. The following hypothetical records define expected outcomes, not measured product results.
- Map one configurable shirt and its navy-medium variant to the test outlet. Start with five sellable units and no other reservations. Record its SKU, source code, price and tax treatment.
- Sell one navy-medium shirt at the counter. Expect one linked order and receipt with the intended price and tax. After processing completes, expect four available units and no change to another size.
- Return that shirt through the opposite channel. Find the original order and create the appropriate credit memo. If it is returned to sellable stock, expect five units. For damaged stock, expect four available units despite the refund.
- Disconnect the till after its product data loads and place one permitted offline sale. Expect the order to remain queued locally. After reconnecting, expect one Commerce order and one stock reduction, even if the sync request retries.
- Repeat with a website sale occurring before the offline sale reaches Commerce. Expect the agreed allocation or oversell-handling rule to apply. Record any unresolved order for staff review.
- Refresh the website and its assistant’s stock source. Expect the same variant availability after the configured update completes. Try order-status access with the purchasing customer and an unrelated customer. The unrelated customer must receive no private order details.
Reconcile the receipt against the order, refund and inventory movements before adding the next outlet. Release the connection when retries preserve one sale, returns reach the intended location and online answers follow the reconciled stock.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.