Real-Time Magento Inventory With Counterpoint

A Magento store can present accurate stock levels only when its product catalogue, retail locations, orders and fulfilment rules agree with the system that actually records sales. For many independent retailers, that system is Counterpoint, where point-of-sale transactions, purchase receipts, transfers and stock adjustments are maintained throughout the day. Connecting Magento to Counterpoint therefore requires more than displaying a quantity beside a product. It requires a dependable inventory workflow.

The practical objective is to make Counterpoint the inventory source while Magento handles online merchandising, checkout and customer accounts. A connector, integration service or NCR Counterpoint partner can synchronise stock between the platforms, preserve order status, and prevent overselling when a customer buys online while another customer is paying in-store. This approach is especially useful for Australian retailers operating across Sydney, Melbourne, Brisbane or regional locations with different fulfilment capabilities.

Define The Inventory Source

Start by deciding which application owns each type of information. Counterpoint should generally remain authoritative for on-hand quantities, receiving, stock transfers, adjustments and store-level availability. Magento can own product descriptions, search settings, images, promotions and online customer data, while order information is passed back to Counterpoint for fulfilment and retail reporting.

This division prevents conflicting edits. If staff change stock figures directly in Magento while a point-of-sale transaction is being processed in Counterpoint, the next synchronisation may overwrite the manual change. Any emergency correction should be made in Counterpoint or through an approved adjustment process, with an audit trail explaining why the quantity changed.

Before configuration, document every stock location. A retailer might have a Melbourne shop, a warehouse in western Sydney and a Brisbane outlet, while a smaller business may have one shop and a separate back room. Give each location a stable identifier and decide whether it can sell online stock, fulfil click and collect, or only support local sales.

Map Products And Locations

Accurate synchronisation depends on reliable product keys. Match the Magento SKU to the Counterpoint item number rather than relying on product names, barcodes or descriptions. Names can change for merchandising reasons, and a single product may have several variants, such as a 500 ml bottle in different colours or a shirt in multiple sizes.

Review kits, packs, matrix items and products sold by weight before importing them. Counterpoint may represent a boxed set differently from Magento, while Magento configurable products use a parent product with child SKUs. Each sellable child item needs a clear relationship to its Counterpoint record so that a sale of a particular size or colour reduces the correct stock count.

Catalogue preparation also matters for Australian shoppers. Use Australian spelling, metric measurements and prices in Australian dollars, and check that delivery regions and postcode rules match the courier services you actually use. A drinkware range, for example, should distinguish individual tumblers from cartons or gift sets; a carefully structured drinkware catalogue can illustrate why variant and pack-level mapping must be precise.

Configure Magento Inventory Sources

Magento’s Multi-Source Inventory, commonly called MSI, allows products to be assigned to sources and salable quantities to be calculated for the website. Create a Magento source for each Counterpoint location that can contribute to online orders. Use consistent codes, names and time-zone settings so the integration can match records without relying on approximate text.

The connector should bring across on-hand values, reserved quantities and, where appropriate, stock status. Magento’s salable quantity is not always the same as Counterpoint’s physical count. An unpaid checkout, an order awaiting dispatch or a quantity held for click and collect may be reserved in Magento even though the item remains physically present in a store.

Choose an allocation policy that reflects operations. A retailer may prioritise the nearest store to reduce delivery time, send orders from a central warehouse, or use a location only after local click-and-collect demand has been protected. In Australia, delivery distances between Perth, Adelaide and eastern-state fulfilment centres can make a simple “nearest location” rule unsuitable, so test allocation using real shipping zones and carrier cut-off times.

Select A Synchronisation Method

Real-time inventory counts usually rely on event-driven updates, scheduled polling or a combination of both. An event-driven connection sends a change when Counterpoint records a sale, receipt or adjustment. Polling checks for changes at regular intervals, such as every minute or five minutes. If Counterpoint or the connector cannot provide webhooks, frequent polling can still deliver near-real-time availability, provided the volume is manageable.

Use different schedules for different data. Stock changes should move quickly, while product descriptions, images and category assignments can synchronise less often. Orders should be sent to Counterpoint as soon as payment is accepted, with an acknowledgement returned to Magento. A failed message must be queued for retry rather than discarded, and retries should be idempotent so that one order cannot be imported twice.

Define the behaviour for unavailable data. If the Counterpoint service, integration queue or network connection stops responding, Magento should show a conservative quantity or temporarily disable sales for affected items. Selling the last unit during an outage may create an expensive customer service issue, particularly for a regional Australian customer who has paid for express delivery to a remote area.

Handle Orders, Reservations And Adjustments

Inventory accuracy depends on the complete transaction cycle, not just a stock feed. When an order is placed, Magento should reserve the relevant quantity according to its configured sales channel. Once payment, fulfilment and dispatch milestones are confirmed, the connector should communicate the appropriate status to Counterpoint and release or adjust reservations according to the agreed workflow.

Set rules for cancellations, refunds, exchanges and partial shipments. A cancelled order may return stock to the available pool, while a damaged return should go into a quarantine location rather than immediately becoming sellable. Store transfers also need attention: stock should not appear available at both the sending and receiving locations while it is in transit.

Retail teams need a controlled process for cycle counts and shrinkage. If staff find a discrepancy during a stocktake, they should adjust the source record in Counterpoint, record the reason and allow the integration to publish the new number. Magento should not be used to hide a discrepancy, and a scheduled reconciliation should compare Counterpoint on-hand totals with Magento source and salable quantities.

The transition away from discontinued NCR Retail Online also makes documentation important. A retailer moving content and customer-facing material to a new platform can use guidance on migrating blog content while separately validating that product, order and inventory data have been mapped rather than merely copied.

Secure, Test And Monitor The Connection

Use dedicated integration credentials with only the permissions required for catalogue, inventory and order operations. Protect API keys and passwords in a secure secret store, encrypt traffic, restrict administrative access and retain logs without exposing customer payment details. Magento should use supported security patches, and the connector should record request identifiers so failed updates can be traced across both systems.

Build a test matrix before switching on live sales. Test a purchase from each website channel, an in-store sale, a refund, a transfer, a receiving event, a manual adjustment, a cancelled order, a partial shipment and a simultaneous sale of the final unit. Include products with multiple variants, backorders, bundles and stock held for click and collect.

Compare results at source level and product level. A successful API response does not prove that the right SKU changed. Check that the Counterpoint quantity, Magento source quantity and customer-visible salable quantity agree after each scenario. Watch for negative stock, duplicate orders, stuck queues, unusual quantity jumps and repeated authentication errors.

After launch, schedule daily reconciliation and a regular operational review. Set alerts for failed synchronisations and define who responds during trading hours. Australian retailers should also test public holiday schedules, local pickup cut-offs and peak periods such as Boxing Day, when store traffic and online demand can change rapidly. The final production step is to run one controlled sale of a mapped item, verify the deduction in Counterpoint and Magento, and then release the full catalogue.