Integrating A WMS With Counterpoint And Your New Ecommerce Site

Replacing NCR Retail Online with a new ecommerce platform is more than a website redesign. It changes the way product data, customer orders, warehouse tasks, payments and fulfilment information move through the business. A warehouse management system (WMS) can provide the control layer that keeps these activities aligned with Counterpoint and the new online shop.

The first task is to define which system owns each piece of information. Counterpoint may remain the source for products, pricing, suppliers and financial records, while the WMS manages bin locations, picking, packing and stock movements. The ecommerce site then presents sellable inventory and captures orders without creating a second, conflicting version of the truth.

This approach is especially important for Australian retailers managing several sales channels, GST-inclusive pricing and deliveries across large distances. Before replacing the former NCR Retail Online platform, document the current workflows and decide how the new integration will handle local requirements such as click and collect, split shipments and regional freight.

Start With Data And Process Mapping

Begin with a catalogue of every data object exchanged between Counterpoint, the WMS and the ecommerce platform. This should include item numbers, barcodes, descriptions, variants, costs, retail prices, tax codes, supplier details, customer records, stock quantities, sales orders, refunds and shipment tracking. Mapping these fields exposes mismatched formats before they become costly errors.

Pay particular attention to item identifiers. A product may have a Counterpoint item number, a supplier SKU, an EAN barcode and an ecommerce product ID. The WMS needs a dependable relationship between these values so that a picker scans the right item and the website reduces the correct inventory. Variant products, kits, multipacks and products sold by weight deserve their own test cases.

Process mapping should also cover exceptions rather than just the ideal order path. Describe what happens when stock is short, a payment is declined, an order is edited, a customer requests a refund or a warehouse cannot find an item. For an Australian operation, include authority-to-leave instructions, PO boxes, remote-area surcharges and deliveries to locations outside Sydney, Melbourne, Brisbane or Perth.

Build A Reliable Inventory Sync

A WMS integration should communicate available-to-sell inventory, rather than simply copying every physical stock figure to the online store. On-hand units may be reserved for wholesale customers, damaged, awaiting quality checks or allocated to an in-store order. The ecommerce quantity should reflect what can genuinely be promised to a shopper.

Set rules for safety stock and channel allocation. A retailer might keep a small buffer for popular lines during a weekend promotion or reserve selected stock for a local shop’s click-and-collect service. These rules are useful during busy periods such as the Christmas rush, Boxing Day sales and end-of-financial-year promotions, when a few minutes of inaccurate stock can create a wave of cancellations.

Choose an integration method that matches operational volume and risk. Application programming interfaces (APIs) are usually preferable for near-real-time updates, while scheduled files may suit smaller businesses or legacy Counterpoint setups. Whichever method is used, record message status, timestamps and error details. A failed stock update should create an alert and a retry process, not disappear silently.

Connect WMS Rules To Counterpoint

Counterpoint and the WMS should have clearly separated responsibilities. Counterpoint can remain responsible for merchandise, pricing, purchasing and sales history, while the WMS controls warehouse locations, replenishment tasks, picking waves, packing stations and dispatch confirmation. The ecommerce platform should receive approved product and availability data rather than becoming an uncontrolled editing point.

Order status needs a shared vocabulary. “Paid”, “released”, “being picked”, “packed”, “dispatched” and “cancelled” should mean the same thing across each system. If Counterpoint uses one status code and the website interprets it differently, customers may receive a dispatch email before the parcel has left the warehouse.

Decide how adjustments travel in both directions. A WMS may report a short pick, stocktake variance or damaged item, while Counterpoint may record a return, credit or manual sale. These events need reconciliation rules and audit trails. A daily comparison of key totals—orders, units sold, stock adjustments and unfulfilled lines—can reveal integration drift before it affects a large number of customers.

Manage Orders, Backorders And Exceptions

The order lifecycle should begin when the ecommerce platform confirms payment and finish when tracking is returned to the customer record. The WMS can then create picking work, group orders by warehouse zone and send packed quantities back to Counterpoint. If a customer buys several items and one is unavailable, the systems must agree whether to hold the complete order, ship available products first or cancel the missing line.

Backorders require a firm customer communication policy. Show an honest estimated date, avoid reserving stock that does not exist and make partial fulfilment rules visible at checkout. The practical guidance in backorder handling advice is useful when customer orders span the period between the old service and the replacement store.

Australian delivery conditions make exception handling particularly important. A parcel sent to a rural address may take longer than one sent across metropolitan Melbourne, while an incorrect postcode can produce an expensive carrier correction. Capture suburb, state and postcode validation at checkout, support Australia Post or StarTrack tracking where appropriate, and ensure the warehouse can see delivery notes without relying on handwritten instructions.

Protect The Customer Journey And Search Visibility

A technically correct integration can still damage sales if customers see inconsistent prices, missing products or confusing delivery promises. Test the complete journey on mobile devices, including product search, variant selection, coupon codes, GST display, account creation, guest checkout, payment, order confirmation and returns. Check that customer service staff can locate the same order in Counterpoint, the WMS and the ecommerce administration area.

Security should be designed into every connection. Use encrypted transport, restricted API credentials, role-based access and logs that show who changed an order or stock figure. Avoid storing payment card data in systems that do not need it, and establish procedures for revoking credentials when staff or suppliers change.

A platform migration also changes URLs, category paths and product addresses. Create redirects from valuable old pages, update canonical tags and submit the new XML sitemap to search engines. The URL migration guidance can help teams reduce broken links and preserve organic traffic while the new store settles.

Checks Before The First Live Order

• Match item IDs, barcodes and product variants across all systems
• Confirm GST, pricing, freight and discount calculations
• Test overselling, partial shipment, cancellation and refund scenarios
• Verify tracking, customer emails and warehouse printouts

Run these tests with realistic Australian addresses and purchase patterns rather than sample data alone. Include a PO box, a regional postcode, a click-and-collect order and a multi-item parcel. Review the results with warehouse staff, customer service and finance so that technical assumptions are checked against daily work.

Signals To Monitor After Launch

• Inventory mismatches and failed synchronisation messages
• Orders stuck between payment, release, picking and dispatch
• Unusual refund, cancellation or backorder rates
• Page errors, broken redirects and declining organic visits

Monitor the integration closely for the first several weeks, especially after promotions or catalogue updates. Reconcile stock and order totals daily at first, then establish a frequency that reflects transaction volume. Keep a rollback plan for disabling a faulty channel without losing orders already accepted by the warehouse.

Operate And Improve After Launch

Going live is the start of operational ownership, not the end of the project. Assign a person or team to review integration alerts, approve data changes and coordinate fixes between the Counterpoint partner, WMS provider and ecommerce developer. Written runbooks should explain how to retry failed messages, perform a stock reconciliation and handle an order that appears in one system but not another.

Warehouse feedback is a valuable source of improvement. If pickers repeatedly search for the same product, the location layout or barcode data may need attention. If customer service receives frequent delivery-date complaints, the availability calculation or carrier estimate may be too optimistic. These observations can guide changes to replenishment, safety stock, packaging and delivery rules.

Keep integrations maintainable by documenting field mappings, API versions, scheduled jobs, credentials, ownership and change history. Test upgrades in a staging environment before applying them to live operations. With clear ownership and regular reconciliation, Counterpoint, the WMS and the new ecommerce site can operate as one dependable retail system, with accurate stock and a practical fulfilment process as the everyday measure of success.