Setting up Magento stock alerts around NCR thresholds

Moving from NCR Retail Online to Magento involves more than importing products and customer records. Stock warnings also need to preserve the operating rules that staff relied on when deciding when to reorder, transfer, or pause sales.

A threshold is the quantity at which Magento raises a low-stock warning. It is different from the quantity available for purchase, the safety-stock buffer, or the amount shown as “out of stock” to shoppers. Treating those values as interchangeable can create unnecessary alerts or leave popular items unavailable.

For Australian retailers, the consequences appear quickly. A Sydney fashion store may need extra stock before a weekend event, while a regional Queensland business may face longer supplier lead times. Seasonal demand around Christmas, Boxing Day, and the end of financial year can also make an old NCR warning level unsuitable.

Magento can reproduce the underlying logic, but the migration needs a deliberate mapping exercise. Before changing settings, record the NCR threshold by product or category, identify the stock source behind each figure, and test the resulting alerts with realistic inventory movements.

Audit the NCR rules before migration

Start by exporting the product SKU, current stock, low-stock level, reorder quantity, supplier lead time, and any location-specific notes from the NCR environment or its operational reports. If the same SKU had different thresholds in a shop and warehouse, preserve both values rather than forcing one global number.

Some businesses used an informal rule that was never documented in software. A buyer may have ordered when there were ten units left because a supplier took three weeks to deliver, even though the formal NCR setting was five. Speak with the people who purchase and receive stock, then distinguish system thresholds from staff habits.

NCR Retail Online has been discontinued, so the migration should be treated as a systems change rather than a simple theme or catalogue transfer. The NCR platform information can provide useful background, but the practical source of truth should be the settings and reports captured from the former installation.

Translate thresholds into Magento inventory settings

In Magento 2, the global low-stock value is commonly found under Stores, Configuration, Catalog, Inventory, and Product Stock Options. The “Notify for Quantity Below” value acts as the default warning threshold. A product can usually override that default through its Advanced Inventory settings, which is important when high-value or fast-moving items need different treatment.

Map an NCR threshold of ten units to a Magento warning level of ten only when both platforms measure the same quantity. If NCR excluded reserved units, damaged goods, or stock held for click-and-collect orders, a direct numerical match will be misleading. Document the formula before entering the value.

For example, a retailer might define usable stock as physical stock minus damaged stock minus allocated orders. Magento may calculate salable quantity through its inventory management system, so the relevant comparison could be:

salable quantity = physical quantity - reservations

The threshold should be applied to the figure staff actually use for replenishment, not simply to the number printed on a warehouse shelf label.

Handle multi-source inventory correctly

Magento’s Multi-Source Inventory features separate sources such as a Melbourne store, a Brisbane warehouse, and a third-party fulfilment location. This can improve stock accuracy, but it changes the meaning of a low-stock notification. A product might be low at one location while the total network still has enough units to fulfil online orders.

Decide whether the NCR threshold was global, source-specific, or based on a preferred dispatch location. If a Perth shop had a local minimum of four units for walk-in customers, that reserve should not disappear just because stock exists in Sydney. Source priorities, reservations, and distance-based fulfilment rules need to support the same commercial decision.

A useful migration record includes the SKU, source, physical quantity, reserved quantity, salable quantity, threshold, and next replenishment date. This makes it easier to explain why Magento produced a warning and helps staff identify whether they need to buy, transfer, or simply wait for an inbound delivery.

Account for Australian trading patterns

Australian retail demand is shaped by geography and calendar events. A gift shop in Melbourne may see strong traffic during local festivals, while a coastal Queensland store may need a different forecast during school holidays. Long delivery routes to Western Australia, Tasmania, and remote areas can justify a larger safety buffer than a metro store would use.

GST does not change the number of units needed for a low-stock alert, but tax configuration can affect reports, product imports, and order totals during the same migration. Retailers moving from the old platform can review this WooCommerce tax setup guide for related transition considerations, especially if they are comparing Magento with WooCommerce.

Keep inventory rules separate from Australian pricing and tax rules. A product should trigger a replenishment warning because its available units are low, not because its GST-inclusive price or tax class changed.

Configure the alert delivery process

A warning is useful only when it reaches the person who can act on it. Magento can support low-stock notification emails, but the sender, recipient, schedule, and email transport need checking after installation. Send alerts to a monitored purchasing address rather than an abandoned administrator mailbox.

Many stores prefer a daily digest so staff do not receive a separate message for every SKU. Others need immediate alerts for medicines, replacement parts, or best-selling products. Match the delivery frequency to the cost of running out and the speed at which the supplier can respond.

Magento cron must be running reliably for scheduled processes and notifications. After configuration, inspect logs, confirm the email queue is being processed, and test delivery to Australian business addresses. A warning that exists in the admin panel but never reaches the buyer is a failed control.

Test with real stock movements

Create a staging test using several representative products: one with a global threshold, one with a product-specific override, one held at multiple sources, and one with reservations. Reduce quantities one unit at a time and record the point at which Magento produces the warning.

Test the full trading sequence as well. Place an order, cancel it, create a shipment, receive a partial supplier delivery, and transfer stock between locations. Confirm that the salable quantity and alert status behave as expected after each event. Include backorders if the store permits them, since a backorder policy can alter the practical meaning of “low stock.”

A short screen recording can help train store teams and provide evidence for future audits. When documenting the process, use clear descriptions and searchable labels; guidance on writing a clear video description is relevant when internal tutorials need to be found quickly.

Monitor and refine the rules

After launch, compare Magento warnings with purchase orders, stockouts, excess inventory, and staff overrides for at least one replenishment cycle. If alerts arrive when shelves are still full, the threshold may include stock that cannot be sold or may be set too high for the sales pattern. If products repeatedly sell out before action is taken, the lead-time buffer needs review.

Create a simple monthly report showing warnings raised, orders placed, units sold before replenishment, and days out of stock. Review it by category and location rather than relying on one figure for the entire business. Thresholds for phone accessories, fresh seasonal products, and slow-moving furniture rarely deserve identical treatment.

Keep a change log containing the previous threshold, new threshold, reason, approver, and review date. This protects the business from undocumented adjustments and makes future platform changes easier. The strongest Magento setup is one that reflects purchasing reality, source-level stock, and Australian delivery conditions.

The essential point is that matching NCR thresholds means matching the business rule behind each number. Capture how NCR calculated available stock, reproduce that logic in Magento, test warnings across sources and order states, and review the results against real replenishment decisions.