Syncing Counterpoint purchase orders with an online storefront

A reliable connection between Counterpoint and an ecommerce website keeps purchasing, stock control and online sales working from the same information. When a buyer raises a purchase order in Counterpoint, the relevant product, supplier, quantity and expected arrival details should flow into the retail workflow without forcing staff to re-key data in several systems.

For Australian retailers, the goal is rarely a simple “send everything online” setup. A shop in Brisbane may sell from the same stock pool as its website, while a business in regional New South Wales may need to allow for supplier delays, freight zones and warehouse transfers. The right process makes purchase orders useful without showing unavailable or unreceived stock to customers.

Establish what Counterpoint should send

Start by defining the source of truth for each data type. Counterpoint should generally remain responsible for supplier records, purchase order status, product identifiers, cost prices and receiving activity. The online storefront should manage web descriptions, search settings, customer-facing images and merchandising. Inventory quantities need a clearly agreed owner or synchronisation rule.

A purchase order itself does not usually mean that stock is available for sale. If a retailer orders 50 units from a supplier, the website should not automatically advertise all 50 unless the business has deliberately enabled pre-orders or expected-stock sales. A safer sequence is to create the order in Counterpoint, transmit its details where required, receive the goods, and then publish the updated available quantity after the stock has been checked.

Map the fields before configuring an integration. Product codes, barcodes, variants, supplier references, unit costs, tax settings, locations and expected delivery dates must match between systems. A mismatch between an SKU in Counterpoint and a configurable product in Magento or WooCommerce can create duplicate listings, incorrect quantities or an order that cannot be allocated properly.

Prepare products, suppliers and locations

Clean master data is the foundation of a dependable purchase order feed. Remove duplicate SKUs, standardise barcode formats and decide how products with multiple colours, sizes or pack quantities will be represented. A product sold as a single item online but purchased as a carton from a supplier needs a conversion rule that staff can understand.

Location settings deserve particular care. A retailer with stores in Melbourne, Perth and an online fulfilment warehouse may need separate stock pools, transfer rules and click-and-collect availability. A small operator in Hobart may use one location, but still needs to distinguish stock on hand, damaged goods, committed stock and stock awaiting receipt.

Supplier data should include usable lead times rather than vague notes such as “usually quick”. Record order cut-off times, minimum quantities, shipping arrangements and whether the supplier sends partial deliveries. These details help purchasing staff judge whether a low-stock alert should create a purchase order immediately or wait until the next buying cycle.

Build the purchase order workflow

A practical workflow begins when Counterpoint identifies a replenishment requirement. Staff review the suggested quantity, check open purchase orders and confirm the supplier. After approval, the purchase order receives a stable reference number and moves to a status such as submitted, acknowledged, partially received or complete.

The integration can then pass selected information to the ecommerce platform or an intermediary service. Depending on the system design, that may include expected quantities, incoming dates and warehouse allocations rather than the entire internal document. The storefront can use this information to support back-in-stock notices or pre-order messages, while keeping unreceived units out of normal availability.

When goods arrive, staff should receive them against the original Counterpoint purchase order. A partial delivery of 20 units from an order for 50 should increase stock by 20, leave 30 outstanding and preserve the original audit trail. The online inventory update should happen after counting, barcode checking and location assignment, not merely when a supplier marks an item as dispatched.

Handle Australian tax, freight and fulfilment

Australian ecommerce operations need consistent treatment of GST, prices and invoices. Product and order data should distinguish GST-inclusive customer pricing from supplier costs and tax-exclusive purchasing values. The exact configuration depends on the retailer’s accounting setup, but the key principle is that a purchase order sync must not alter the tax logic used for customer checkout or financial reporting.

Freight can also affect whether an item is genuinely available. A supplier in Sydney may deliver quickly to a Melbourne warehouse, while stock travelling to Darwin, rural Queensland or a remote Western Australian town may take considerably longer. Use realistic lead-time windows and avoid promising an arrival date based only on a purchase order acknowledgement.

Australian businesses often combine shipping with click and collect, local delivery or Australia Post services. The inventory design should show whether incoming stock is intended for general online fulfilment, a particular shop or a customer reservation. During busy periods such as Christmas, Boxing Day promotions or end-of-financial-year sales, a temporary purchasing surge can otherwise make incoming stock appear more certain than it is.

Monitor errors, security and stock changes

A sync process needs visible error handling. Record when a purchase order was created, transmitted, accepted, rejected or changed. Alerts should identify failed product mapping, invalid supplier codes, duplicate document numbers and quantity differences. A silent failure is particularly risky because staff may believe that goods are protected by a purchase order when the storefront is using old stock data.

Access should be limited according to staff responsibilities. Buyers may create and approve purchase orders, warehouse staff may receive goods, and ecommerce staff may edit descriptions without changing cost or supplier data. Secure credentials, encrypted connections and regular password rotation are basic controls. Retailers reviewing network exposure can also read about public IP risks when assessing the wider security environment around connected systems.

Keep a reconciliation routine alongside the automated feed. Compare Counterpoint stock on hand with the storefront quantity at set intervals, investigate large variances and document manual adjustments. A weekly review may suit a low-volume retailer, while a busy fashion or electronics operation may require daily checks or near-real-time updates.

Plan the move beyond NCR Retail Online

NCR Retail Online was discontinued, so retailers using a legacy connection need to treat platform migration as part of the purchasing project. Magento and WooCommerce are common alternatives available through NCR Counterpoint partners, but the choice should follow the business’s catalogue size, fulfilment model, integrations and internal technical capacity.

Before switching, document how purchase orders currently move through the business. Capture field mappings, inventory rules, store locations, customer reservations, tax settings and exception procedures. Export test data and run parallel checks where possible. A migration should prove that an approved purchase order, a partial receipt and a stock correction all produce the expected result on the new storefront.

The change may also affect picking, dispatch, refunds and customer notifications. Retailers can review guidance on fulfilment changes before moving to Magento, especially if warehouse staff will use different statuses or screens. Historical records should be retained according to business and accounting requirements; archiving historical orders can help preserve evidence without keeping an obsolete storefront operational.

A sensible implementation starts with a small group of products and one location. Test purchase order creation, supplier acknowledgement, partial receipt, stock availability and customer ordering before expanding to every category. Include staff from buying, the shop floor, warehouse operations and finance so that the final process reflects what actually happens during a busy trading day.

The essential principle is simple: a purchase order represents planned supply, while received and verified inventory represents stock that can normally be sold. When Counterpoint, the storefront and the warehouse follow that distinction, Australian retailers can reduce overselling, improve replenishment decisions and give customers clearer information. The reader should remember that accurate field mapping, controlled receiving and regular reconciliation matter more than a fast connection that merely moves data.