Products and Stock
Hyvä POS is on the App Store
The free app is out for iPhone, iPad and Mac: install it from the App Store, connect your Magento store and sell. PRO, the Magento module with a license per terminal, follows shortly. News and pricing are at hyva.io/pos.
The catalog on the register is your Magento catalog, live: no imports and no separate product database. The app reads products, categories, prices and stock straight from Magento's REST API, and it only writes back when the cashier changes something: a stock adjustment, not a product edit.
Browsing and Search
Search by name or SKU, browse the category tree, and filter by status, type, visibility or category. Matching products appear from the local catalog cache first, while the authoritative Magento results load in the background and replace them.
Opening a product shows images, description, custom attributes, tier prices and stock per source. Offline, browsing and search keep working against the cached catalog (see Offline Product Cache).
Barcode Scanning
- Bluetooth scanners in HID mode work out of the box.
- MFi scanners (Socket Mobile and similar) connect natively.
- The device camera scans barcodes too, so a register works without a hardware scanner.
A scan resolves against the local SKU cache, SKU first and then the barcode attribute, so the line lands in the cart without waiting for the network. Live price and stock refresh right after. Hardware options are on the barcode scanners page.
Product Types at the Register
- Simple products add straight to the cart.
- Configurable products open an option picker (size, color, and so on); the resolved variant is what is sold and what deducts stock.
- Grouped products open a list of their children, each with its own quantity stepper; every selected child becomes its own cart line, like on the storefront.
- Bundle products open the bundle picker with required and optional selections and quantities.
How Bundles Reach Magento
Magento's order API cannot reproduce the bundle-parent-with-child-lines structure a storefront order has. That is a platform limitation, not a POS one. So when a POS sale contains a bundle, the app writes the Magento order with one line per component simple. The charged bundle price, tax and discount are distributed across the components to the cent, so the lines sum to the amount the customer paid, and every component deducts its own stock and ships correctly.
The receipt shows the bundle as one line at its bundle price; only the Magento order record carries the flattened components.
Price Display and Tax Mode
Prices on the register can show Excluding Tax, Including Tax, or Both. This only changes what the cashier sees. Tax itself is always calculated from Magento's tax rules and rates, which sync to the device, so the register's totals match the webshop's.
Set the display mode under Settings → Pricing & Tax: Display Product Prices in Catalog for the product grid, and separate Display Prices and Display Subtotal pickers for the cart. Mirror your store's Stores → Configuration → Sales → Tax display settings so both channels present prices the same way. On PRO, a Sync from Magento button pulls these values, and the admin can lock them from global settings: a locked setting shows a lock and a Magento badge on the register and cannot be edited there.
Stock at the Register
Every product's stock is one tap away. With Multi-Source Inventory, quantities show per source; without MSI, the register shows the single Magento stock figure. The numbers are Magento's on-hand source quantities, read live from the inventory API. Whether the register works with sources is the Use Multi-Source Inventory setting under Settings → Inventory (on PRO from Stores → Configuration → Hyvä POS → Terminal Defaults → Stock, lockable). With it off, or on a store without Magento Inventory, the register reads the single stock figure and the source features stay off; see inventory sources and stocks.
Which shelf the register sells from is Settings → Inventory → Shipment Source. Every stock check then runs against that source specifically, not an aggregate across sources. Automatically fulfil take-now items, under Stock on the same page, is whether the register ships the goods a customer takes at the counter right after the order, so the order completes and the shelf moves; off, the order waits for a shipment made in Magento. It follows that switch alone: whether the stock registration module is ready plays no part in it (see the stock registration module). On PRO, terminals bound to a location inherit the source from the location, so every register in a shop is configured identically.
Stock Management opens on the full product list. A search, a category or a scan narrows it, and clearing them brings the full list back.
Cashiers can also change stock, and each save writes straight to Magento's inventory:
- Take in a delivery by scanning it in; see below.
- Set quantities directly, per source, including for the children of configurable products.
- Review recent changes in the on-device adjustment history (who, when and why, exportable as CSV) and roll back a mistake.
If your store keeps stock in more than one place, read inventory sources and stocks first. Which source the register sells from, and which one a delivery lands in, are separate settings.
The Stock Registration Module
The register places its orders through Magento's order API, which saves an order without the stock side a checkout order gets: the website's salable quantity does not move when the register sells, and after the register's shipment the website offers goods that have left the shop. Two open-source Magento modules from Hyvä close that gap, hyva-themes/magento2-inventory-order-reservation on every store and its companion hyva-themes/magento2-inventory-order-reservation-msi on a store with Magento Inventory. The stock registration module describes what they do and how they install.
The register asks the store for the module when it connects, on every sync and on Check for Magento Updates, and shows the answer as a row under Settings → Inventory: Ready, Installed, not ready (with the module's own sentence), Installed, not verified, or Not installed. On a store that does not read Ready, the register asks the merchant once, before any money moves, to acknowledge selling without stock registration; the setup checklist carries the row with the composer line until the store reports the module. The counter shipment follows Automatically fulfil take-now items alone, never readiness. PRO brings the module as a dependency from module 1.6.0. The stock registration module has the states and what each one does to a sale.
Receiving a Delivery
A box of t-shirts arrives at the shop: twelve of them, in four sizes.
- Open Stock Management and turn on Auto-increase stock on scan (on a phone-sized screen, Auto-increase stock under the search field).
- Pick the Source the delivery is landing in. On a single-source store there is nothing to choose. On a split setup this is the difference between the shop shelf and the warehouse, so check it before the first scan: the picker defaults to the first source, not necessarily yours.
- Scan the first shirt. The register resolves the barcode, adds one unit to that source, saves it to Magento immediately, and confirms on screen.
- Keep scanning. Two of the same size means scanning it twice. There is no quantity to type and no Save to remember.
Because each scan saves on its own, you can stop at any point and the units already scanned are in Magento. Nothing is held in a draft.
Configurable products resolve to the child that owns the barcode, so scanning a medium adds to the medium and not to the parent. Parents hold no stock of their own in Magento's inventory.
Every scan lands in the adjustment history with the cashier's name, so a miscount is traceable and reversible.
Low Stock
Stock checks run in the background after a line is added, never blocking the scan. Cart lines show a Low Stock badge when the selling source is at or below the threshold, which defaults to 10 units; on PRO the threshold comes from Terminal Defaults → Stock → Default Low Stock Threshold in Magento, with an override per location, and syncs to every register. Product screens flag stock slightly above the product's own minimum quantity, so the warning arrives before the last unit sells.
The Low stock chip at the start of the Stock tab's filter bar lists the products at or below the same threshold and takes the category and the search with it. On a store with Multi-Source Inventory it reads the location's source; without it, Magento's own low-stock list.
Selling Through a Shortage
Before payment, the register compares every line against the on-hand quantity at its source and lists any shortfalls. What happens next depends on the tier.
Free. The register refuses the sale while a line is short, whatever the setting below reads, and the cart row's Resolve menu offers no Sell anyway. Without the Hyvä POS module nothing on the store can ship a short line: Magento Inventory refuses the deduction, and the sale would stay unshipped. The register checks the line against the stock your website sells from: with Multi-Source Inventory, the salable quantity of the website's stock, the same figure the web shop shows, as fresh as the store's stock index. A register with a shipment source set under Settings → Inventory needs that source to carry the line as well, since the website figure does not say which source holds it. A product Magento sells on backorder is still handed over from stock: the register's shipment is immediate, so a line the figure cannot cover is refused even where the web shop would take the order on backorder. When the website's stock cannot be read, the line shows no figure and the Pay tap stops with Stock could not be checked and a Retry; one entry under Reports → Errors shows why, and the connection test's Inventory (website stock) row names the resource the integration needs. The register sells offline on its own terms; a failed check is not the same thing. The selling source is the module's.
PRO. The policy is yours, under Settings → Inventory → Insufficient stock (its own section, whatever Automatically fulfil take-now items is set to; from module 1.6.0 also set in Magento under Terminal Defaults → Stock → Insufficient Stock, per location, and lockable):
- Warn but allow (default): badges inform, checkout proceeds. The short lines go through as sold past the stock check.
- Confirm at checkout: one dialog lists the short lines; Continue Anyway sells them the same way.
- Hard-block: the sale waits until the lines are covered.
From module 1.6.0, the Insufficient stock row and the Automatically fulfil take-now items row under Settings → Inventory each say where their value comes from: the store's setting, the POS location or this terminal. A row Magento locks shows a lock and cannot be changed on the register. A value changed in Magento reaches the register on the next sync or on Check for Magento Updates.
When the customer is holding the item, the cashier can also resolve with Sell anyway on the line (available when Magento allows backorders). Either way the sale completes at negative stock: the module ships the line, takes the source below zero, writes the shortage on the order as a status comment ("Stock discrepancy, sold past the stock check at the register: …") and the register files a Sold from negative stock row under Reports → Sync Issues, so the manager can correct the source once the shelves have been counted. A shortage the register never saw, because the shelf emptied after the line was added, ships the same way and is written on the order as stock drift. A sku the selling source does not carry at all is assigned to that source at the handed-over quantity below zero, with the comment stating it; assigning its stock to the source is the correction.
With the stock registration module ready, the store places Magento Inventory's reservation for a register order the way the web shop does, so the salable quantity your web shop sells from follows every register sale, on both tiers. Without it an order placed through the API carries no such reservation, which is Magento's own behaviour for API orders, and the register asks the merchant to acknowledge that before it sells; bin/magento inventory:reservation:list-inconsistencies and inventory:reservation:create-compensations are Magento's tools to true the figures up afterwards.
Offline Product Cache
The register keeps a slim copy of the catalog on the device: SKU, name, price, tax class, barcode, categories and thumbnail per product, encrypted at rest. It powers instant scanning, instant search suggestions, and full browsing when the connection drops.
Configure it under Settings → Data & Sync: the Offline Catalog Cache toggle, a Sync Interval picker, and a Last synced timestamp so the cashier can see how fresh the copy is. Fast Product Lookup keeps the index in memory for faster scans. One consequence: a product added to the catalog after the last sync is not scannable until the next sync completes.
Barcode Labels
With a label-capable printer connected, print barcode labels for products straight from the product screen. Which product attribute holds the barcode is set per label printer under Settings → Barcode Labels (the default attribute code is barcode).
PRO
PRO adds per-line source selection at checkout (sell this one from the warehouse in the back), stock transfers between sources with an audit trail, stock-discrepancy reporting in the Reports tab, and customer-specific pricing from contracts or an ERP.