What to Do with Deleted Products That Still Exist in Counterpoint’s Records

Removing an item from a selling screen does not always erase its history from NCR Counterpoint. A product may disappear from the catalogue while its SKU, stock movements, invoices, purchase orders, and sales reports remain in the database. That behaviour is usually useful rather than faulty: retailers need reliable records for audits, returns, financial reporting, and customer service.

The practical task is to separate products that should no longer be sold from records that must be retained. Australian retailers also need to consider GST reporting, Australian Consumer Law obligations, supplier warranties, and end-of-financial-year records. A careful cleanup process can keep the Counterpoint database manageable without damaging historical information or breaking links with an online store.

Why Deleted Products Remain in Counterpoint

Counterpoint generally treats product deletion and transaction history as separate concerns. If a stock item has appeared on a receipt or invoice, permanently removing it could leave old transactions without a recognisable description, price, tax treatment, or item reference. The system may therefore retain the product record even when staff can no longer select it for a new sale.

This is especially common with discontinued lines, seasonal goods, duplicate SKUs, and products that have been replaced by a new supplier code. A deleted or hidden item can still appear in sales history, inventory valuation, purchase reports, customer returns, and database searches. Its continued presence does not necessarily mean it is available for sale or included in current stock.

Before changing anything, confirm whether “deleted” means removed from the website, marked inactive in Counterpoint, excluded from a store location, or genuinely deleted from the item file. Those statuses have different consequences for reporting and synchronisation.

Check Its Operational And Financial History

Start by searching the item number, barcode, product description, and any alternate supplier code. Review recent sales, on-hand quantities, committed stock, lay-bys, purchase orders, transfers, and open customer orders. An item that looks obsolete may still be attached to stock sitting in a Brisbane warehouse, a Melbourne shop floor, or a regional store awaiting transfer.

Check financial records as well. In Australia, GST-inclusive ticket prices and tax codes need to remain consistent with the records used for Business Activity Statements and reconciliation. Review the item’s sales history around EOFY, especially if the product was sold during a different pricing period or under a promotional tax treatment. Do not remove a record simply because its current stock figure is zero.

Returns and warranty claims deserve particular attention. Under the Australian Consumer Law, a customer may return or seek a remedy for goods after the product has stopped being sold. Keeping the original item description, receipt reference, and transaction history makes it easier for staff to handle a claim accurately.

Make The Product Unavailable Without Destroying History

For most discontinued products, the safest approach is to make the item inactive, non-sellable, or unavailable for replenishment, depending on the controls available in your Counterpoint setup. Remove it from current website listings, tills, catalogue searches, and purchasing workflows while preserving the underlying record.

Before applying the status, confirm that the item has no remaining saleable quantity, open order, transfer, or reservation. If a small amount remains, decide whether it should be sold through, transferred to another branch, written off, or returned to the supplier. A Sydney gift shop might handle a discontinued range differently from a rural hardware retailer that still needs to sell the last units to a nearby community.

Record the reason for the change in an internal note or product-management log. Useful details include the date, staff member, supplier decision, replacement SKU, remaining quantity, and whether the online listing was removed. This creates an audit trail and prevents another team member from reactivating an obsolete item by mistake.

Clean Up Duplicate And Orphaned Records Carefully

Some lingering products are not genuine historical items. They may be duplicate records created during a catalogue import, a barcode change, or a failed ecommerce synchronisation. Compare descriptions, supplier codes, barcodes, cost prices, tax settings, images, and category assignments before deciding which record is authoritative.

An orphaned record may have no current stock but still be connected to a web listing, price level, promotion, customer order, or reporting group. A bulk deletion can therefore create broken links or misleading totals. Export a backup or obtain a verified database backup before attempting any large-scale change, and test the process on a copy where possible.

Category structure is worth reviewing at the same time. For example, a homewares retailer might separate flatware, serving pieces, and entertaining accessories rather than leaving discontinued lines mixed into a general catalogue. A customer-facing example of a flatware collection shows how a distinct product group can remain useful even when individual SKUs are retired.

Keep Online And Storefront Data Aligned

A product removed from an ecommerce site may still be active in Counterpoint, and the reverse can also happen. Compare the item status, available quantity, price, images, and category across the point-of-sale database, website, marketplace feeds, and any integration middleware. Pay attention to products with zero stock, backorders, or a “hide when unavailable” rule.

Run a controlled synchronisation after changing the record and inspect the results rather than assuming the feed worked. Check the website from a customer’s perspective, search the SKU, and confirm that an old product cannot be added to a cart. If the product is still visible, identify whether the source is Counterpoint, a cached feed, a manually maintained page, or a separate marketplace listing.

This matters for Australian shoppers who may expect prices in Australian dollars, GST treatment to be clear, and delivery availability to reflect their state or postcode. A discontinued item that remains visible can produce overselling, incorrect freight expectations, or prevent a customer in Perth, Adelaide, or Hobart from completing a legitimate purchase.

Build A Repeatable Records Policy

Create clear rules for active, discontinued, inactive, archived, and replacement products. Decide who can change each status, what checks are required, and how long historical records must remain accessible. Include procedures for seasonal merchandise, supplier range changes, recalled products, changed barcodes, and products sold through multiple locations.

A simple monthly or quarterly exception report can identify items that have had no sales for a defined period, carry no stock, have no open orders, and are not linked to active promotions. That report should support review, not automatic deletion. A product with no sales for twelve months may still be needed for a warranty, a repeat order, or an audit.

Document the relationship between old and replacement SKUs. If a retailer changes from one coffee machine model to another, staff should be able to see which item replaced the old one without rewriting historical receipts. A broader dining-and-entertaining category can also help teams organise current merchandise consistently; examples such as entertaining products illustrate how related ranges can be grouped for navigation and reporting.

When Specialist Review Is Sensible

Get help from an experienced Counterpoint partner when records are duplicated across companies, stores, or databases; when historical transactions appear damaged; or when the ecommerce integration keeps recreating deleted items. Specialist review is also sensible before a major migration, especially if the business is moving from a discontinued retail platform arrangement to Magento, WooCommerce, or another supported system.

Prepare a list of affected SKUs, screenshots of their current status, recent transaction examples, stock locations, and the desired outcome. Include details about GST, price levels, supplier links, and online channels. A partner can then distinguish a harmless historical record from an item that is still feeding stock or pricing to a live sales channel. General migration references, including platform transition information, may offer background, but your own Counterpoint configuration should remain the basis for any technical decision.

The goal is controlled retirement rather than an empty database. Preserve records needed for sales history, tax documentation, customer remedies, and management reporting, while removing obsolete products from everyday workflows. That balance keeps the catalogue clean and protects the evidence your business may need later.

Begin with a backup and an export of every affected SKU, then review each item for stock, open orders, returns, tax history, and online connections before changing its status.