Setting up Counterpoint reorder alerts that trigger web purchases

A small retailer in Brisbane once told me her only reliable forecast was the look on her regulars' faces. That instinct carried her for years, but it cannot scale alongside a web store. When Counterpoint watches inventory and pings the right person the moment a SKU dips below threshold, the gap between a sold-out shelf and a steady weekend becomes a configuration question rather than a luck question. Done well, the alert fires, drafts a purchase order, and lands inside your ecommerce back end before anyone has walked back from the loading dock.

NCR Retail Online has been retired, leaving Counterpoint operators to bridge their POS to Magento or WooCommerce through their NCR Counterpoint partner. The reorder feature is built into the counterpoint engine and does not need replacement, but the way the alert fans out does. Once a PO payload resolves inside your storefront of choice, the rest of the chain follows cleanly, from cart creation through to despatch.

This walkthrough covers the moving parts: configuring min/max thresholds, defining the alert, mapping its output to a web purchase, and verifying the loop end-to-end. A side-by-side comparison follows, with habits that hold up across small Australian catalogues and growing multi-site operations.

Preparing Counterpoint before any rule goes live

Open the inventory module and confirm every active SKU has a preferred vendor, a unit of measure, and a current cost. Skipping this is the most common reason automated rules misfire later; the alert triggers correctly, but the PO has nowhere to land. Run the standard inventory integrity report and clear duplicates before touching a single threshold.

If the same product sells in-store and online, both records should resolve to one item code in Counterpoint. Otherwise the alert will write against one channel while the other goes empty, and Australian merchants have been caught out by this during Christmas rushes, when one misaligned SKU can quietly erode margin across two revenue streams. Confirm that the operator account has rights to alter reorder rules and create POs; lock-down logins are common in service-based businesses and silently stop the alert from reaching the next stage.

Tuning min and max thresholds to real demand

Counterpoint's reorder logic leans on min and max fields per item, and those numbers should not be guesses. Pull three months of sales history per SKU, average it across a typical week, and add a buffer for volatility. For a Penrith nursery selling seedlings, a threshold of two weeks of cover usually rides out the Saturday rush; for a smaller Adelaide boutique stocking one-off pieces, narrower windows often make more sense than wide buffers.

Lead time matters as much as velocity. If your distributor promises three-day delivery from Sydney, your reorder point sits comfortably below the safety-stock ceiling; if shipping runs from a Melbourne warehouse with five-day turnaround, build that gap into the buffer. Stores tied to seasonal demand such as Australia Day, Melbourne Cup or EOFYS should recalibrate thresholds at the start of each peak window and again at its close. For long-tail items like artisan candles or single-origin tea, dial the min downward, but log those exceptions so they are not forgotten in the next quarterly review.

Building the alert rule and choosing its destination

Inside Counterpoint, open Inventory Controls and select the automated reorder rules panel. Define the rule by item class, vendor, or department, depending on where most of your stock sits. For a moderately complex store, vendor-based rules usually produce the cleanest output, since each supplier carries a consistent PO format. Set the action to generate a draft purchase order and queue it as pending rather than auto-approving, particularly when the PO will land in a Magento or WooCommerce pipeline.

Pick the notification channel your team actually checks. Email remains the default for most small operators around Australia, but SMS or in-app alerts work better when the on-call buyer is on the floor or sorting parcels. Counterpoint can fan alerts to multiple recipients; do so sparingly, otherwise the inbox noise becomes its own reliability problem.

Operators running Counterpoint alongside adjacent hospitality or entertainment venues often extend those integrations further. The same data plumbing that handles a stock refill can route POS events into live gaming workflows. The architectural principles are identical: one source-of-truth event fans out cleanly to multiple downstream services.

Bridging the alert to a triggered web purchase order

Once Counterpoint drafts the purchase order, the next link is the API bridge from your POS to your ecommerce platform. If you are still on a legacy NCR storefront, plan a smooth migration to WooCommerce so the reorder automation lands on a stable REST surface. Most Australian integrators working through NCR Counterpoint partners handle the migration alongside the API rebuild, which keeps the SEO footprint intact while new webhooks come online.

Map the Counterpoint PO payload to the format your web store expects. That typically means translating the SKU, quantity, vendor reference, and expected cost into the equivalent WooCommerce or Magento purchase-order model. Test the full path with a single low-value SKU first, so the loop is proven without risking a surprise auto-order of fifty units of something niche.

On the receiving end, configure your storefront to either auto-approve based on threshold limits or queue the PO for buyer review. The hybrid model, auto-approve under a dollar cap and escalate above it, is popular with multi-site retailers, since it preserves human judgement for high-value stock while letting the system handle commodity items.

Aligning fields and keeping stock in step

Field mapping is where most reorder automations quietly break. Counterpoint thinks in vendor codes and departments; Magento thinks in configurable products and categories; WooCommerce sits somewhere between. Build an explicit mapping document and keep it versioned; even a simple spreadsheet works, as long as every change in one system is mirrored in the other. If you sell everyday drinkware alongside higher-margin gear, treat that category as a separate mapping track, since giftable items often carry seasonal SKUs that turn over faster than the base catalogue.

Set up the inventory sync so it triggers after a PO is generated, not before. Reverse-ordering the sync can cause the storefront to display inflated stock figures for hours while the alert is in flight, which damages trust with online shoppers. Confirm one-way POS-to-web sync is enabled, and that any back-dated stocktakes from a weekend count do not blow away a queue of pending reorders. Make the mapping document easy to find by anyone on the team, including seasonal casuals.

Manual reorders versus automated triggers

The trade-off is rarely a clean win for either side. Manual reorders suit very small catalogues where the buyer knows every line intimately; automated rules suit anything where the SKU count crosses a few hundred or where the same buyer is also fronting up to customers at the register.

Habits worth keeping for steady-state operation

• Run a dry-month audit at the start of each season, comparing actual stockout days against the rule's predictive accuracy, then tune min/max from there.
• Treat vendor reliability as a data point; if a supplier drops below 95% on-time delivery, raise that vendor's threshold by ten percent.
• Keep a single owner for the alert rule, even across multi-site operations, so the configuration does not drift between stores in different states.
• Pair the reorder automation with a lightweight marketing check that uses a reliable keyword discovery tool to spot demand surges before stock dips.
• Re-test the full loop quarterly; even a small Counterpoint update can quietly change a field name and break a webhook without warning.

The single habit that carries the most weight, based on how Australian small merchants tend to operate, is the quarterly loop re-test. Counterpoint updates ship quietly, and a webhook that worked in February can quietly fall over in May. Block fifteen minutes on the calendar once a quarter, fire a test SKU through the alert, and confirm the PO lands correctly inside your web store. Done consistently, the automated reorder loop quietly funds your weekends, your Boxing Day rush, and every campaign in between.