Managing closed and cancelled orders during data migration

Retailers who have relied on NCR Retail Online for years are now planning their move to platforms such as Magento or WooCommerce, and the moment of cutover tends to expose a long list of small but important details. One of the most overlooked areas is what happens to orders that were closed, cancelled, or partially refunded before the migration begins. These records are not glamorous, but they sit at the intersection of finance, customer service, and compliance, and mishandling them can cause weeks of cleanup after the new site goes live.

The transition is more pressing for Australian retailers because the local tax year, consumer law, and reporting calendars all run on their own rhythm. Orders placed at 11pm AEDT in Sydney, or after a Boxing Day sale in Melbourne, carry implications for GST, refund obligations, and EOFY reporting that do not exist in the same form elsewhere. Knowing how these orders travel from the old database to the new one determines whether the books balance on 1 July.

This guide walks through the practical steps for handling closed and cancelled orders during a data migration, from the pre-migration audit through to the scheduled reporting that keeps the archive useful long after launch.

Why closed and cancelled orders need special treatment

A cancelled sale is not just an empty row in the database. It usually contains the original transaction, the reversal, and sometimes a partial refund, all linked to a customer who remembers the interaction. When a migration runs without a clear plan for these records, the new platform can show a sale that never completed, lose the link between the original order and its reversal, or drop the metadata that finance relies on for reconciliation.

For Australian retailers, the stakes are higher because the Australian Taxation Office expects GST collected and refunded to be traceable through every system that touches the register. If a cancelled order loses its GST line during migration, the new system will show a mismatch between sales totals and the BAS statement at the end of the quarter. The same applies to consumer guarantees under the Australian Consumer Law, where a cancelled order may still trigger a refund obligation that has to be visible in the customer record.

Audit your order history before the cutover

Before any data is moved, run an audit on the closed and cancelled order history inside NCR Retail Online. Filter the order list for the last two financial years, which is the window most Australian retailers use for active reporting even though tax records must be kept for at least five years under ATO rules. Export the list as CSV and look for patterns: are there clusters of cancellations around product launches, supplier delays, or seasonal promotions like the Black Friday weekend in November or the post-Christmas rush in early January. Patterns like these will shape how the archive is structured in the new platform.

Pay particular attention to orders that are marked as closed but still have an open balance, and to cancelled orders that were never refunded because the customer was paid out in store credit. These edge cases are the ones that disappear during a careless migration, and they are also the ones a customer will ask about six months later. Specialty stock such as the craft beer ranges covered in the beer retail resources page often reveals cancellation clusters tied to expiry dates or supplier substitutions, and those patterns deserve their own tag in the new system so they remain searchable later.

Tax and refund records that must travel with the data

The Australian GST framework treats a cancelled order as a tax adjustment, not simply as a deleted sale. The original 10 per cent GST charged on the invoice has to be matched to the GST refunded on the cancellation, and the difference flows back into the BAS for the period in which the cancellation occurred. When the order record moves from NCR Retail Online to the new platform, every one of these fields has to come along: the original GST amount, the refund date, the reason code, and the staff member who processed the reversal.

Local timing matters here. AEST is the default timezone for most NCR Counterpoint partners, but cross-border suppliers in New Zealand or Asia sometimes record refunds in UTC. Confirm that the migration script applies a consistent timezone to every historical record, otherwise the BAS line for June will not reconcile with the bank statement that closed on 30 June at midnight AEST. Sydney-based finance teams in particular tend to spot this kind of discrepancy first, since they are usually the ones preparing the EOFY package for the auditor.

Mapping status fields between legacy and new systems

The new platform will not speak the same status language as NCR Retail Online. Magento, for example, uses a different state machine for orders, and WooCommerce extensions each have their own conventions. A clean migration starts with a mapping table that defines what "Closed" in the legacy system becomes in the new one, what "Cancelled" becomes, and whether partially refunded orders are stored as a separate status or kept as a flag on the parent record.

Before the cutover, test the mapping against a small batch of orders that includes a fully closed sale, a fully cancelled sale, a partially refunded sale, and an order that was cancelled but where the stock was returned to inventory. Run the test migration, then open each order in the new system and confirm that the financial totals, the status, and the linked documents such as credit memos have all arrived correctly. If you would like a quick visual walkthrough of how the export files look in practice, the guide on creating walkthrough videos shows a useful method for recording the process for the team.

Reconciling cancelled sales after the migration

Once the cutover has happened and the new store is live, run a reconciliation pass within the first 48 hours. Pull a list of all orders marked as cancelled or closed in the new platform, compare the count and total value against the same list exported from NCR Retail Online before the migration, and flag any discrepancies for review. This is also the right moment to schedule the ongoing reports that will keep the archive honest.

For retailers moving to Magento, the post-migration period is also when the value of real-time inventory visibility becomes obvious, because cancelled orders that were never properly returned to stock can distort reorder points for fast-moving lines such as seasonal fashion, limited-edition giftware, and perishable grocery ranges. A short delay in catching these distortions can mean missed restocks across Sydney, Brisbane, and Perth warehouses within the same week.

Keeping the order archive searchable for future audits

The migration is the moment to decide how closed and cancelled records will be searched in the new system. Most teams underestimate this step and end up with thousands of historical orders that are technically present but practically invisible. Configure a saved filter for "closed or cancelled" orders, tag them with the originating financial year, and make sure that customer service staff in Brisbane, Perth, and regional hubs can all reach the archive through the same search panel.

The long-term payoff shows up at the next EOFY, when finance needs to answer a question about a refund issued three years ago. With a well-structured archive, that lookup takes seconds; with a sloppy archive, it takes days. Set up the right scheduled reporting from day one and the archive will pay for itself the first time the auditor asks for a sample of cancelled transactions. The scheduled reports after migration guide walks through the configuration step by step.

Block out a 90-minute session in the calendar this week, run the pre-migration audit on the last two financial years of closed and cancelled orders, and tag every record that carries a refund or stock return before the cutover date is set.