Setting up scheduled inventory and order reports after migration

Moving away from NCR Retail Online changes more than the storefront. Once a business adopts Magento or WooCommerce through an NCR Counterpoint partner, its inventory, orders, customer records and reporting tools may sit across a new collection of systems. Scheduled reports need to be rebuilt rather than assumed to have carried across automatically.

A reliable reporting routine gives Australian retailers a current view of stock availability, unfulfilled orders, refunds, sales by channel and low-stock products. It also reduces the need to export spreadsheets manually each morning, which is especially useful for businesses serving customers across Sydney, Melbourne, Brisbane and regional areas.

The goal is not to generate every possible report. It is to deliver the right information to the right person at a dependable time, using consistent definitions and secure access. A well-planned schedule can support purchasing, warehouse work, customer service, accounting and compliance without creating unnecessary notification noise.

Confirm the new reporting environment

Begin by documenting where each type of data now lives. Magento and WooCommerce may hold online orders, while NCR Counterpoint or another retail management system remains the source for point-of-sale transactions, purchasing and store stock. An integration platform may synchronise the two, but synchronisation does not always mean that reporting fields match perfectly.

Check product identifiers, tax settings, order statuses, warehouse locations and payment classifications before creating a schedule. A product code that differs between the ecommerce platform and the retail system can make available stock appear higher or lower than it really is. The same issue can affect reports for click and collect, transfers and backorders.

Run a short period of manual comparisons. Select several online orders and compare their values, payment states, GST treatment and fulfilment status across both systems. For inventory, compare a group of fast-moving and seasonal products at the warehouse, shop floor and website. These checks establish whether the new reports are ready for operational use.

Decide which reports deserve automation

Inventory reporting should usually begin with available stock, low-stock exceptions, stock received, stock adjustments and products with no recent sales. A separate report for overselling risk can identify products where the website quantity is greater than the quantity that can actually be dispatched. This is important when stock is shared between an online shop and physical stores.

Order reporting commonly includes new orders, unfulfilled orders, cancelled orders, refunds, payment failures and orders awaiting collection. A daily sales report can summarise gross sales, discounts, shipping, GST and net value, while a fulfilment report can focus on what the warehouse must pick and pack. For businesses with multiple locations, include the relevant store, warehouse or dispatch source.

Use reporting to support decisions rather than to reproduce every screen in the platform. A homewares retailer, for example, might find a low-stock report more useful when it includes supplier lead time and incoming purchase orders. Merchants reviewing product presentation can also use home décor examples to group seasonal ranges and monitor their performance without treating every category as equally urgent.

Build dependable data connections

Scheduled reports are only as accurate as the feeds behind them. Confirm how frequently orders, stock changes, refunds and catalogue updates are transferred between Magento or WooCommerce and the retail management system. If stock synchronises every 15 minutes but orders are imported hourly, a fast-selling item may temporarily show an inaccurate quantity.

Record the source of truth for each field. The retail system may control stock on hand, while the ecommerce platform controls product descriptions and online imagery. Payment status may come from the payment gateway, and shipping status may be updated by a carrier or fulfilment application. This mapping helps prevent reports from joining conflicting values.

Australia’s geography makes timing particularly important. A warehouse in Sydney may prepare orders while a customer in Perth is still beginning the day, and daylight saving affects the relationship between eastern states, Queensland and Western Australia. Set schedules against a clearly documented time zone, and check whether the platform uses UTC, Australian Eastern time or the server’s location.

Set useful delivery times and recipients

Choose delivery times around the work that follows the report. A warehouse may need an open-order file before the first picking wave, while the purchasing team may need a stock exception report before suppliers’ order cut-offs. A finance report can arrive after end-of-day payment reconciliation rather than at midnight, when some transactions may still be processing.

Use separate schedules for urgent exceptions and regular summaries. A low-stock alert might run several times per day for high-volume products, whereas a weekly slow-moving inventory report is usually sufficient. Sending every report to every employee encourages people to ignore important messages.

Recipients should receive only the information required for their role. Warehouse staff may need order numbers, product codes, quantities and delivery methods, but not full customer payment details. Managers may need totals and trends, while accountants may need tax and refund information. Apply role-based permissions in both the ecommerce platform and the reporting or email service.

A practical reporting checklist

Before activating scheduled delivery, verify these operational details:

• Confirm the report’s time zone, date range and order-status rules.
• Test stock quantities against physical counts and recent transactions.
• Check GST, discounts, shipping charges and refunds separately.
• Send a sample to each recipient and confirm that file formats open correctly.

Use a second review list after the first week of live reporting:

• Compare scheduled totals with payment gateway and accounting records.
• Check that cancelled and refunded orders are not counted as completed sales.
• Review failed synchronisations, missing products and duplicate order numbers.
• Remove recipients who do not use the report or no longer need access.

Keep a short record of report ownership, data sources, frequency and escalation contacts. This makes the process easier to maintain when staff change or when a new warehouse, store or sales channel is added. It also gives a partner or administrator enough context to troubleshoot an inaccurate result.

Protect customer and business information

Order exports can contain names, addresses, telephone numbers and delivery details, so scheduled reporting must be treated as a privacy process. Australian businesses should handle personal information consistently with the Privacy Act 1988 and their privacy policy. Limit downloads, avoid sending sensitive data in unprotected attachments and remove customer fields that are unnecessary for the recipient.

Security should include unique user accounts, multi-factor authentication, strong administrator controls and regular permission reviews. If a report is delivered through a third-party automation service, check its access scope and retention settings. An application that only needs order totals should not receive unrestricted access to customer profiles or payment information.

The Australian Consumer Law also makes accurate order and product information important. Reports that reveal persistent stock discrepancies, delayed fulfilment or incorrect product descriptions can help a retailer correct problems before they lead to misleading availability claims or avoidable customer complaints. GST reporting should likewise be reconciled with accounting records, particularly around sales, refunds and shipping.

Compare platform options before refining schedules

The best reporting workflow depends on the ecommerce platform, extensions and integration method selected after NCR Retail Online’s discontinuation. Magento can offer extensive catalogue, customer and order-management capabilities for larger or more complex operations. WooCommerce may be more approachable for smaller retailers already using WordPress, although extensions and hosting choices can significantly affect reporting.

Subscription and operating costs should be assessed alongside reporting capability. The subscription comparisons provide useful context for NCR users evaluating platform expenses, but the final decision should also account for integration maintenance, Australian payment services, hosting, security and partner support.

Whichever platform is chosen, test the reports during a realistic trading period. Include weekend orders, split shipments, click-and-collect transactions, refunds and an item that sells out. In Australia, seasonal peaks such as Christmas trading and end-of-financial-year promotions can expose timing or stock problems that are invisible during a quiet week.

Establish a review routine that lasts

After the first month, review whether each scheduled report is accurate, timely and acted upon. Measure practical outcomes such as fewer oversells, faster dispatch, quicker refund reconciliation and less manual spreadsheet work. If a report does not influence a decision, reduce its frequency or retire it.

Schedule a monthly access review and a quarterly data-quality review. Confirm that staff still need their permissions, that report recipients remain current and that integration failures are investigated. Keep copies of the report definitions so a partner can reproduce them after a platform update or a change to the store structure.

A successful post-migration reporting setup is a controlled operating rhythm: trusted data is synchronised, exceptions are visible, and routine summaries arrive before the work they support begins. The key thing to remember is that scheduled reports should reflect the new system’s actual data flow, Australian trading conditions and the specific decisions your retail team must make.