Multi-warehouse fulfillment from Counterpoint to Magento

Multi-warehouse fulfilment gives Australian retailers a way to sell from stock held near customers across several branches. A Magento store can present one broad catalogue while Counterpoint remains the operational source for products and stock. The design must decide which location serves each order, what inventory can be promised, and what shoppers see when stock is moving quickly.

Because NCR Retail Online has been discontinued, retailers moving through an NCR Counterpoint partner need a replacement architecture. For a Magento route, the storefront can handle ecommerce while the partner’s connector carries catalogue, price, stock and order events between systems. Clear ownership for each data flow prevents the storefront and back office from disagreeing about availability.

Australian networks often span a metropolitan DC in Sydney or Melbourne, a larger fulfilment centre in Brisbane and smaller stockholding points in regional centres. Distance affects delivery speed and freight cost, while weather and carrier capacity can disrupt even a well-stocked network. Fulfilment rules should balance proximity, parcel efficiency, stock age and the promise date shown at checkout.

Local realities also shape the setup: prices normally include 10% GST, tax invoices need ABN details, and buyers expect Australian Post and courier options for metro and rural deliveries. Selling through eBay or Catch adds another reconciliation loop. Customer messages can use plain, friendly Australian language and a reassuring “no worries” without weakening exception handling.

Design the stock and order-routing model

Start with a warehouse and SKU map that names the source system for every sellable item. Match Magento product IDs to stable Counterpoint SKUs, including variants, kits and bundle components; never rely on product names alone. Record each location, its trading role and whether it can pick, pack and dispatch parcel orders. This becomes the reference against which stock and fulfilment events are reconciled.

For retailers sharing stock between online and store sales, use the POS as part of the same stock picture rather than another disconnected feed. NCR’s POS connection guide explains the general connection pattern, while the migration design should add online reservations, sale-or-return rules and a process for stores that pick ecommerce orders.

Set allocation rules before enabling express checkout. Magento can route an order to the closest eligible warehouse, but the chosen rule should also respect stock age, promised dispatch time, carrier cut-offs and minimum order value. Reserve stock when payment is confirmed, release it on cancellation, and specify whether an order may be split. Controlled splitting reduces wasted freight, while sensible exceptions prevent an order from remaining unshipped.

Connect Counterpoint and Magento safely

Use a supported API or partner-built connector instead of editing either database directly. Magento needs catalogue attributes, tax classes, images, warehouse visibility and current available-to-promise quantities. Where Magento supports Multi Source Inventory, model each fulfilment centre as a source; otherwise reproduce that visibility through the connector. Product content should include handling attributes, as NCR’s crystal collection illustrates how fragility and gift presentation can disappear in a basic SKU import.

The order flow should move in a clear sequence: Magento creates the order, Counterpoint validates and reserves stock, the selected warehouse picks and packs, and shipment and tracking references return to Magento. Make every event idempotent so a repeated webhook does not reserve or invoice twice. Log acknowledgements, failures and retries, and expose order status to staff.

Security controls must cover credentials, personal data and payment boundaries. Store secrets outside source control, allow only required API permissions, encrypt traffic and redact customer details from logs. Define a retry limit and escalation path for stale stock or unacknowledged orders. During launch, compare event totals by hour; a matching order count is not enough if quantities differ.

Configure Australian delivery and tax

Configure Magento checkout around Australian tax and invoicing rules. Show GST-inclusive prices to consumers, capture ABN details when a business invoice is requested, and ensure tax treatment passed from Counterpoint agrees with the catalogue. Different state and territory GST registration can affect a seller’s obligations, so tax setup needs accounting review rather than a blanket default.

Delivery configuration should support Australian Post alongside suitable courier services, with rates based on destination postcode, parcel dimensions, weight and handling zones. Show realistic delivery windows, particularly for rural and remote addresses where surcharges and longer transit times apply. Test the carrier connection, print labels and capture tracking events. A cheap shipping threshold should not encourage slow, oversized choices.

Marketplace channels such as eBay and Catch can use the same stock pool, but each order needs a clear owner and shared event trail. Confirm whether the warehouse prints marketplace labels, handles returns or accepts a fulfilment fee, then prevent duplicate fulfilment. Customer-service templates can use natural Australian wording—“all sorted” or “no worries”—while preserving precise delivery dates, refund rights and tracking details.

Test the complete fulfillment journey

A migration is ready only when store teams and warehouse staff complete user acceptance testing with realistic products, prices and stock levels. The user acceptance testing guidance explains why business participation matters; for this project, Counterpoint staff should exercise allocation, pick lists, substitutions, cancellations and returns, while Magento staff verify what customers and support agents see.

The regression set should cover a normal multi-warehouse order, an oversell attempt, simultaneous sales in two channels, partial reservation, split dispatch, damaged stock, failed carrier booking, return-to-store and a payment refund. Force a delayed stock feed and then restore it. Each test should record the expected quantity, status, notification and accounting treatment, with defects assigned to a named owner rather than parked in a shared mailbox.

Measure results against agreed thresholds for inventory drift, order latency, pick accuracy, dispatch time and failed connections. Run a representative peak-volume test, such as a sale event or a Melbourne-to-Brisbane promotion, to expose carrier and warehouse bottlenecks. Obtain sign-off from operations, finance, customer service and the integration partner. A signed test record should state what was tested, what remained excluded and who approved the residual risk.

Control day-to-day warehouse operations

Live trading turns architecture into a daily operating rhythm. Reconcile Counterpoint stock against Magento availability, investigate orders stuck after reservation, and monitor cancellations that suggest overselling. Publish a simple exception queue with age, value and owner. Stock-ageing reports should identify lines trapped at a distant branch when another location could fulfil them profitably.

Use these operating controls:

• Reconcile available, reserved and on-hand quantities for every active SKU before and after each dispatch cycle.
• Review priority exceptions at the start of each trading day, with aged oversells and split orders escalated first.
• Audit SKU-to-warehouse mappings and carrier service availability whenever a branch, product or parcel rule changes.
• Track on-time dispatch, cancellation rate, inventory drift and fulfilment cost by location each week.

These controls give buyers and warehouse teams the same view of the operation. Establish a shared definition for available, reserved and damaged stock, assign responsibility for every exception, and review the figures at one regular operations meeting rather than through disconnected spreadsheets.

Treat storefront domain administration as part of continuity, because accurate stock is no help when customers cannot reach checkout. The Gandi domain recovery reference outlines what to do after an expiry, including ownership and renewal checks. Record renewal dates, administrator contacts and recovery access in the same runbook used for warehouse outages, then test that a responsible person can retrieve the account under pressure.

Shift to controlled live trading

Shift to live trading in controlled cohorts rather than switching every SKU and warehouse at once. Begin with a limited product range and two locations, run parallel reporting for a short period, and keep a documented fallback for order acceptance and fulfilment. Customers should see realistic stock and dispatch estimates from the first cohort, while staff receive one escalation channel for edge cases.

After each cohort, compare order value, cancellation rate, picking accuracy, delivery performance and support contacts against the previous process. Resolve mapping and pricing differences before adding more stock. Decommission obsolete feeds only when reconciliation is clean and required audit records are retained. The NCR Counterpoint partner should document remaining dependencies, while internal owners keep control of customer policy, tax decisions and warehouse priorities.

The next concrete step is to produce a one-page cutover map naming the integration owner, the two test warehouses, the first live SKU cohort, its go-live date and the fallback contact.