Configure On-Hand and Available Quantity in Magento

Retail inventory becomes difficult to manage when physical stock and sellable stock are treated as the same figure. A store may have ten units on a shelf, yet only seven should be offered online after accounting for reservations, safety stock, damaged goods, or an order waiting for collection.

For businesses moving away from NCR Retail Online, the distinction is especially important. The product was discontinued, so many retailers are transitioning through NCR Counterpoint partners to platforms such as Magento and WooCommerce. The NCR Retail Online site remains a useful reference for understanding the former platform’s retail and inventory context, but Magento requires its own stock rules and integration design.

Why On-Hand and Available Stock Differ

On-hand quantity is the physical count recorded at a warehouse, shop, or stockroom. It usually changes when goods are received, transferred, adjusted, returned, damaged, or removed during a stocktake. In a Magento environment, this figure should represent what the business genuinely has in a source location.

Available quantity is the amount Magento can safely sell. It can be lower than on-hand stock because units may already be reserved for unpaid or processing orders, held for click and collect, allocated to another channel, or protected by a buffer. Treating available inventory as a simple copy of the physical count creates a direct path to overselling.

For an Australian retailer, this matters when inventory is split between a Sydney fulfilment centre, a Melbourne shop, and a regional Queensland location. A product may be physically present in Melbourne but unavailable to a Brisbane customer if the integration does not support the promised delivery window or transfer process.

How Magento Calculates Sellable Quantity

Magento’s Multi-Source Inventory model separates stock from sources. A source is a physical location, while a stock is the sales-facing group that connects one or more sources to a website. The salable quantity shown to customers is calculated from source quantities, reservations, and configured thresholds rather than from a single warehouse number.

A simplified model is:

Salable quantity = source quantity − reservations − safety quantity

The exact result depends on configuration, backorders, stock status, and the algorithms used by the installed Magento version and extensions. Reservations are especially significant because Magento can subtract them when an order is placed and reconcile them when the order is shipped, cancelled, or refunded.

On-hand quantity should therefore come from the ERP, POS, or warehouse count, while available quantity should generally be calculated by Magento or by a carefully designed connector. Do not send the same value into both fields unless the business has confirmed that there are no reservations, buffers, or multi-channel commitments.

Configure Magento Stock Settings

In the Magento admin, review the product’s quantity and stock status under the inventory configuration. Enable stock management where Magento is responsible for controlling availability, then define the out-of-stock threshold, minimum and maximum sale quantities, backorder behaviour, and whether customers can purchase when the calculated quantity reaches zero.

The out-of-stock threshold is useful as a safety buffer. For example, if a shop has 20 mugs on hand and a threshold of two, Magento can treat only 18 as sellable. This protects against picking errors, breakages, late POS updates, and stock that has been put aside for a customer. The right figure depends on sales velocity and how quickly the business can investigate discrepancies.

Product-level settings should align with global configuration. A limited-edition item may require zero backorders, while a supplier-backed product may permit them with a clear dispatch estimate. An Australian business selling during Boxing Day promotions or the end-of-financial-year period should test these rules under unusually high order volume before relying on them.

Map NCR Data to Magento Sources

When migrating from NCR Counterpoint or an NCR-connected retail setup, create a field map before enabling live synchronisation. Identify which source provides physical quantity, which system owns reservations, how returns are posted, and how stock transfers are represented. A product identifier must remain stable across the POS, ERP, Magento catalogue, and any warehouse software.

A practical mapping might send Counterpoint’s physical stock count to Magento source quantity. Magento then manages reservations from web orders, while the connector sends shipment, cancellation, refund, and adjustment events back to the retail system. If Counterpoint also receives in-store sales, those transactions must reduce the relevant Magento source quickly enough to prevent stale availability.

Product data should be tested with realistic catalogue examples. A flatware product with separate finishes or pack sizes must use distinct SKUs, because combining stainless steel and gold-tone variants into one quantity produces misleading availability; a flatware example illustrates why product-level inventory needs careful variant mapping. The same principle applies to donation products, service items, and gift cards, which may need non-standard stock treatment; donation options are a useful example of a catalogue item that should not be handled like a physical unit.

Validate Quantity Rules Before Launch

Run a controlled test using one product, one source, and a small quantity. Record the physical count, place an order, inspect the reservation, cancel the order, and then complete a shipment. The expected available amount should change at each stage without unexpectedly changing the on-hand count.

Use these checks during a staging test:

• Confirm a web order creates the correct reservation.
• Confirm cancellation restores sellable quantity.
• Confirm shipment reduces the source quantity once.
• Confirm a return follows the intended restocking rule.

Then test the edge cases that often expose integration flaws. Include a POS sale, a manual adjustment, a warehouse transfer, a partial shipment, a refund, and an order containing multiple sources. Verify that the customer-facing product page, cart, checkout, admin panel, POS, and ERP eventually show compatible values.

Review these customer-facing outcomes:

• Zero available units should show the intended stock message.
• Safety stock should remain invisible to shoppers.
• Backorders should display a truthful fulfilment estimate.
• Click-and-collect stock should not be promised for delivery accidentally.

Operate Inventory Safely Across Australia

Australian retail operations often combine online orders with shop-floor sales, courier collection, and click and collect. A customer in Perth may see different delivery promises from a customer in Adelaide, while remote Northern Territory or Western Australia addresses can require extra handling time. Magento’s quantity logic should be paired with source-selection and delivery rules so a nominally available unit is actually serviceable.

Separate stock pools when the business needs firm allocation. For example, reserve a defined quantity for a Brisbane showroom, keep marketplace inventory in its own buffer, or prevent online orders from consuming units held for a Saturday event. These rules are more reliable than repeatedly editing product quantities after a sale has occurred.

The storefront also needs accurate merchandising and communication. Content channels can support product discovery, whether a retailer promotes a seasonal collection through an Ubuntu Podcast sponsorship or uses a link in bio page to direct shoppers to several destinations. Those campaigns can increase demand quickly, so inventory thresholds and monitoring should be ready before promotion begins.

Set up alerts for negative salable quantities, failed synchronisations, reservation mismatches, and products whose on-hand count has not changed for an unusual period. Schedule regular cycle counts rather than waiting for an annual stocktake, and give staff a clear process for recording damaged items, customer holds, and stock transferred between stores. The next step is to select one high-volume SKU, document its Counterpoint-to-Magento field mapping, and complete the full order, cancellation, shipment, and return test in staging.