How to Handle Multi-Warehouse Fulfillment with Counterpoint and Magento

Running a retail operation across more than one warehouse has shifted from a luxury to a baseline expectation. With customers in Perth expecting next-day delivery and shoppers in Sydney expecting same-day click-and-collect, the geography of Australia pushes merchants toward distributed inventory. Pairing NCR Counterpoint with Magento creates a practical path: Counterpoint remains the source of truth for stock, pricing, and purchasing, while Magento runs the customer-facing storefront. The trick is making the two systems talk without constant manual reconciliation, and the rules around tax, freight, and regional cut-offs all need to be respected.

For retailers already running Counterpoint in the back office and Magento online, the move to multi-warehouse fulfillment is less about new software and more about configuration discipline. Counterpoint already tracks stock by location; Magento already supports multi-source inventory out of the box. The work sits in between: deciding how locations are mapped, how orders route, and how exceptions are handled when a popular SKU sells out in Sydney but still sits on the shelf in Adelaide.

Setting Up Multiple Locations in Counterpoint

Counterpoint treats each warehouse as a discrete location, and every inventory record carries a quantity per location. The first decision is granularity: do you create one location per physical site, or do you roll stores and warehouses together? Most Australian retailers keep stores and warehouses separate because of different cost bases, different picking labour, and different replenishment cycles. A store in Brisbane's Queen Street Mall behaves very differently from a fulfilment centre in the western Melbourne industrial belt, even if they technically hold the same SKUs.

When locations are correctly defined, the next layer is the transfer process. Counterpoint's inventory transfers move stock between locations and write the movement into the purchasing and valuation history, which keeps the accountant happy at BAS time. Set reorder points per location, not just per SKU, because a single global threshold will either overstock slow-moving regional warehouses or understock the busiest ones. A threshold that works for a low-velocity warehouse in Hobart will starve a high-velocity one in Parramatta.

Finally, audit the user permissions so warehouse staff can only see and adjust stock for their own site. This prevents the classic error of a Brisbane team accidentally writing off Adelaide stock because they had the wrong warehouse selected in the receiving screen.

Mapping Counterpoint Locations to Magento Sources

Once Counterpoint has well-defined locations, those locations need to become Magento sources. In the multi-source inventory framework, each source represents a physical place stock can ship from. The mapping is usually one-to-one: a Counterpoint location called "MEL-DC" becomes a Magento source of the same name. Keeping the names identical saves hours when reconciling sync errors later.

The Magento side also needs stocks (collections of sources) and sales channels mapped to those stocks. A single Australian website can run from a single stock that contains all sources, with Magento picking the optimal source per order using its shipping rules. Alternatively, regional stores can run on separate stocks that only see the local warehouse, which is useful for businesses with differentiated assortments in different states.

Inventory sync between Counterpoint and Magento typically runs through an integration middleware or a direct connector. The flow is straightforward: Counterpoint pushes available-to-promise quantities every few minutes; Magento reads them and deducts on order placement; orders placed in Magento feed back to Counterpoint as sales orders, which then deduct the stock and create pick lists. Choose a tool that records every sync with a timestamp and an identifier so disputes are easy to resolve.

Keeping Stock Levels Honest Across Systems

The most common failure mode is not a system outage but a slow drift. A SKU that is genuinely available in Counterpoint shows as out of stock in Magento because the last sync missed a manual adjustment. The opposite is worse: Magento believes stock is on hand, a customer orders, and the warehouse team cannot fulfil because Counterpoint says zero.

Three habits keep the numbers aligned. First, run the integration on a short interval: every five minutes is the practical floor for most Australian retailers. Second, reconcile at end of day with a scheduled job that highlights variances above a tolerance, say two units or one percent. Third, treat manual stock adjustments as events worth auditing. Every write-off, every count correction, every inter-store transfer should flow to Magento within the sync window rather than at the next batch.

For businesses selling items with strong seasonal swings such as wine, cookware, and gifts around the festive window, staging the sync around promotional drops matters as well. A flash sale on red blends can deplete a Melbourne warehouse in minutes; if the sync is slow, customers will keep ordering stock that is already gone. Many retailers in this category pause the sale after a threshold is hit and let the sync catch up before reopening the offer.

Shipping Rules, GST, and the Last Mile

Australian shipping is unusual in global terms: distances are vast, the population is concentrated, and carrier pricing is post-code driven. Magento's shipping matrix lets you set rules per source, so a Melbourne source can offer local Metro rates that a Brisbane source cannot match. Most retailers with multi-warehouse setups calculate shipping per source at checkout rather than averaging, because customers notice and complain when the rate does not reflect the actual fulfilment point. GST at 10% applies to most domestic goods and is calculated on the order subtotal including shipping in some scenarios. Counterpoint should be the system of record for tax codes, and the integration should push the inclusive or exclusive flag to Magento so that customer-facing prices match invoice prices. If you sell food and wine online, the rules around liquor licensing vary by state, so configure Magento to block checkout for restricted postcodes unless the customer is verified.

Finally, think about the carrier mix. Australia Post remains the default for regional and rural coverage, while private couriers such as Startrack, Toll, and Aramex handle metro density. For bulky items like more/food-wine.html and specialty premium cookware ranges, restricting particular sources to carriers that handle fragile goods makes sense. This kind of carrier-to-source routing sits inside Magento's shipping methods but should be agreed with the warehouse team so they don't book the wrong pickup.

Choosing Your Sync Approach

Different retailers take different paths between Counterpoint and Magento, and the right one depends on order volume, team size, and tolerance for manual work.

A practical starting point is the native connector with documented fallbacks: it ships faster and gives the team time to learn the data model before any customisation begins. Build the custom layer only after the standard flow is stable, because customising on top of an unstable foundation just creates a more complicated unstable foundation.

Watch-outs When Going Live

• Pilot one warehouse and one product line first; resist the urge to flip the switch across the whole catalogue on day one.
• Document the source naming convention before launch, and never rename a source after orders are flowing because it breaks the mapping.
• Train warehouse staff on the order feed from Magento, including how to flag a partial ship so Counterpoint records the correct movement.
• Run a reconciliation report on day one, day seven, and day thirty after launch; variance trends tell you where the integration is leaking.

Quick Wins for Ongoing Operations

• Schedule the sync to run more frequently during promotional windows and less frequently overnight when traffic is low.
• Use Counterpoint's user audit log to identify who made the last manual adjustment when a stock figure looks wrong.
• Review the source-level shipping rules quarterly, because carrier pricing and Metro boundaries change every January.
• Keep a small test-order routine so support staff can place a no-value order end-to-end and confirm the full loop.

Once the integration is live and the reconciliation reports are clean, the next concrete step is to schedule the first quarterly review of source-level shipping rules and carrier contracts before the new-year rate changes take effect in January.