Replicating NCR’s Order Splitting by Warehouse Location in Magento

NCR Retail Online helped retailers connect ecommerce orders with store inventory and business systems, including workflows that could divide a customer’s basket according to stock held at different locations. With the platform discontinued, retailers moving from NCR Counterpoint integrations need to recreate that behaviour in Magento without losing inventory accuracy or fulfilment visibility.

The goal is simple for the shopper: place one order, pay once and receive the products through the most sensible delivery arrangement. Behind the scenes, Magento may need to create separate fulfilment lines, assign stock from multiple sources and communicate each decision to warehouse, store and accounting systems.

Australian retailers have particular reasons to get this right. A customer in Melbourne may expect a fast shipment from a Victorian store, while a buyer in Perth may need stock dispatched from a Western Australian location to avoid excessive freight time and cost. GST-inclusive prices, regional delivery zones, click and collect and Australia Post cut-off times all affect the design.

Why Warehouse-Based Order Splitting Matters

A single catalogue can represent stock held in a central distribution centre, retail shops, showrooms and third-party warehouses. Treating these quantities as one pool can produce overselling, delayed dispatches or an order that appears available online but cannot be completed from the selected location.

Warehouse splitting gives each source a defined role. Magento can reserve a dining set from a Brisbane store, a matching accessory from a Sydney warehouse and a backordered item from a supplier, while keeping the customer’s order together at the payment level. The operational system then receives separate fulfilment instructions.

This approach is especially useful for Australian businesses that serve both metropolitan and regional customers. A retailer with locations in Sydney, Melbourne, Adelaide and Perth may use local stock for click and collect, while routing remote orders from a national distribution centre with better packing capacity.

Build a Reliable Source-of-Stock Model

Magento’s Multi-Source Inventory framework provides the foundation. Each warehouse, store or virtual stock location should be created as a source with a clear code, address, contact details, dispatch calendar and available product quantities. Source priority can then reflect the business’s preferred fulfilment sequence.

A useful model distinguishes physical stock from sellable stock. Physical units may include items already reserved, damaged goods, display stock or products awaiting transfer. The quantity exposed to Magento should be calculated after those exclusions, with safety buffers for fast-moving items. This is critical during Boxing Day promotions and end-of-financial-year sales, when Australian inventory can change quickly.

Product data should also indicate whether an item is eligible for split fulfilment. Large furniture, hazardous goods, personalised products and chilled items may require a single-source rule. For example, a fragile crystal range may need special packaging and a dedicated dispatch location; a retailer can organise such products in a crystal collection while maintaining stricter allocation rules.

Design the Magento Allocation Logic

Magento can use source selection algorithms to recommend where order lines should be fulfilled. A distance-based method may favour the nearest source, while a priority-based method can direct orders to a central warehouse first and reserve shop stock for local customers. The correct option depends on freight contracts, store workload and promised delivery dates.

For an NCR-style workflow, allocation should happen at line level rather than treating the basket as an indivisible unit. Each product line can be evaluated against available quantities, source priority, delivery postcode and collection preference. If one source holds the full quantity, the system creates one shipment; if stock is distributed, it creates multiple shipments or fulfilment groups under the same order.

Rules should account for Australia’s geography. A location that looks close by road may still create a costly shipment across state borders, while stock in Perth may be the logical choice for a Western Australian customer. Delivery zones can be represented through postcode ranges, state rules or carrier-rate services, with exceptions for remote areas and islands.

Connect Magento With Counterpoint and Operations

A migration should preserve the integration boundary between ecommerce and the retail management system. Magento needs dependable updates for stock, price, product status, order creation, cancellations, refunds and shipment tracking. Counterpoint or its replacement system should receive the correct source assignment rather than a generic order with no fulfilment detail.

APIs are usually the preferred method for this exchange because they support structured, repeatable updates and clearer error handling. Retailers replacing NCR Retail Online can review inventory API syncing as a useful reference for thinking about stock movements, polling intervals and reconciliation between systems.

The integration should be idempotent: sending the same order or stock update twice must not create duplicate shipments or subtract inventory repeatedly. Every message needs an external identifier, timestamp, source code and processing status. Failed messages should enter a retry queue and alert staff before the discrepancy affects customers.

Present Split Orders Clearly to Shoppers

Order splitting is an internal process, but the customer experience must remain understandable. During checkout, Magento should show the expected delivery method, estimated timing and any separate shipping charges before payment. If a basket will arrive in two parcels, that information should be visible in the confirmation email and account area.

Retailers may choose to consolidate several fulfilment groups into one customer-facing shipment when stock can be transferred first. That can reduce confusion but may delay dispatch. Another option is to send available items immediately and mark the remaining lines with their own status. The decision should reflect the retailer’s delivery promise and carrier agreements.

For Australian shoppers, delivery messaging should accommodate metro and regional variation. A customer in inner Sydney may receive a next-business-day estimate, while a rural Queensland postcode may need a broader window. Click and collect should show the specific store, collection readiness time and identification requirements, rather than presenting every source as an interchangeable warehouse.

The product catalogue also needs consistent categorisation and fulfilment attributes. A broader home range can include flags for oversized delivery, store collection, fragile handling and source restrictions, allowing checkout rules to operate from dependable product data rather than manual exceptions.

Secure, Test and Monitor the Migration

Before launch, create test orders that cover single-source baskets, split baskets, partial availability, cancellations, refunds and failed carrier updates. Test stock held in stores and distribution centres separately, then repeat the scenarios with simultaneous orders for the same unit. The purpose is to confirm that reservations occur before allocation races create overselling.

Security must cover Magento administration, integration credentials, webhooks and staff access to fulfilment data. Use least-privilege accounts, multifactor authentication, encrypted transport and audit logs. Personal data should be handled according to Australian privacy obligations, with payment information kept within the approved payment provider rather than copied into operational notes. Even basic device and account protections matter; teams can consult screen passcode guidance when reviewing access practices, while ensuring that any security procedure is legally and operationally appropriate.

After launch, monitor allocation failures, negative stock, delayed acknowledgements, cancelled lines and orders that remain unshipped past their promised date. Reconcile Magento quantities with each source system at scheduled intervals, especially after promotions, stocktakes and store transfers. A dashboard showing source-level availability and fulfilment age will reveal problems faster than customer complaints.

A practical replacement for NCR’s warehouse order splitting should be documented as a set of business rules, source records, integration events and customer-facing statuses. Start by listing every Counterpoint location, assigning each a Magento source code, and then run one controlled split-order test from checkout through dispatch and stock reconciliation.