Rebuilding NCR admin reports in Google Data Studio

NCR Retail Online was built to connect ecommerce activity with retail inventory, store operations and business management tools. Its administrative reports could bring together orders, products, stock levels and customer activity in one operational view. Since the platform has been discontinued, retailers moving to Magento, WooCommerce or another NCR Counterpoint partner solution may need to recreate those reports elsewhere. Learn more about Everyday 3.html.

Google Data Studio, now known as Looker Studio, is a practical replacement for the visual reporting layer. It can combine ecommerce, point-of-sale and spreadsheet data into dashboards that support Australian retail decisions, including GST reporting, Australian dollar sales, stock transfers between locations and end-of-financial-year analysis.

Understand the old reporting model

Before rebuilding anything, list the reports that staff actually used in the NCR admin dashboard. Typical examples include daily sales, orders by status, best-selling products, inventory exceptions, refunds, customer acquisition and sales by store or channel. Avoid copying every old screen automatically; some reports may have existed because the software made them available, not because they informed a decision.

Export several historical periods if they are still accessible through NCR Counterpoint, Magento, WooCommerce or archived files. A single week can hide important patterns. Include a normal trading period, a promotional period and a quieter period, such as the weeks after Christmas in Melbourne or Sydney.

Document the filters and definitions behind each report. “Revenue” might mean gross order value, value after discounts, value after refunds or GST-inclusive sales. Those differences become significant when a dashboard is used for Australian Business Activity Statement preparation or compared with accounting software.

Map the data before building charts

Create a field dictionary that records the source, format, business meaning and treatment of every important field. Product SKU, order number, store code, fulfilment method, quantity, discount, tax, freight and refund status should each have a clear definition. This prevents a chart from blending incompatible figures from an ecommerce platform and a point-of-sale system.

Use a stable key for every join. SKU is usually suitable for product-level data, while order ID works for order-level data. Store names are less reliable because “Brisbane CBD”, “Brisbane-CBD” and “Brisbane City” may represent the same location. A separate store mapping sheet can standardise names, postcodes, states and reporting groups.

Treat dates carefully. Store the transaction date, dispatch date, refund date and financial period separately where possible. Australian retailers may need calendar-month reporting for management but financial-year reporting from 1 July to 30 June. Converting all timestamps to Australian Eastern, Central or Western time also prevents late-night transactions from appearing on the wrong day.

Set up a dependable reporting layer

Looker Studio works best when it reads from a clean reporting layer rather than directly from several constantly changing applications. Google Sheets can suit a small retailer, while BigQuery or a managed data warehouse is more appropriate for high order volumes, multiple stores and long-term history. Scheduled exports or an integration service should refresh the data on a defined timetable.

Keep raw data separate from transformed data and dashboard data. Raw files preserve the original record, transformed tables standardise fields and dashboard tables contain only the dimensions and metrics needed for analysis. This structure makes it easier to identify whether an error came from the source system, a formula or the visual report.

Controls that protect report quality

Use these checks before a dashboard becomes part of daily operations:

• Reconcile order counts against the ecommerce platform
• Match gross sales and refunds to the accounting system
• Check missing SKUs, store codes and tax values
• Record the refresh date and source for every dataset

Security also needs a deliberate design. Apply least-privilege access to the underlying Sheets, warehouse and Looker Studio report. Customer email addresses, phone numbers and delivery details should rarely appear in a management dashboard. The Australian Privacy Act and the Australian Privacy Principles provide an important baseline for handling personal information, even when the dashboard is used internally.

Connect ecommerce, stock and store data

A useful replacement dashboard normally draws from three layers: ecommerce orders, inventory or product data, and store or point-of-sale transactions. Magento and WooCommerce exports may use different statuses and tax fields, so create a common order-status mapping such as Paid, Processing, Shipped, Completed, Cancelled and Refunded.

Inventory synchronisation deserves special attention. A product can be available online, reserved for an unfulfilled order, held in a store or in transit between locations. Build separate metrics for on-hand stock, available stock, committed stock and reorder risk. Combining them into one “inventory” number can cause unnecessary purchasing or overselling.

For retailers selling homewares, category-level reporting can reveal seasonal demand more clearly than individual product views. A historical category page such as the dining and entertaining range illustrates how product taxonomy can be organised before it is translated into dashboard dimensions. Use a controlled category hierarchy rather than relying on inconsistent product titles.

Recreate calculations and report logic

Calculated fields should be rebuilt from documented definitions, not from the appearance of an old chart. Common metrics include net sales, average order value, gross margin, sell-through rate, return rate and stock cover. Decide whether discounts, shipping, GST and refunds are included in each metric, then apply that choice consistently.

The following structure helps translate common NCR-style report requirements into a modern dashboard model:

For example, net sales could be calculated as item sales minus discounts and refunds, with freight reported separately. If GST is included in source prices, label the metric “GST-inclusive sales”. If the business needs ex-GST figures, divide the relevant taxable amount by 1.1 only when the transaction is subject to the standard GST rate.

Use parameters for controls such as date range, sales channel, store group and category. A manager in Perth may need to isolate Western Australian stock, while a buyer overseeing Sydney and Melbourne stores may want a combined view. Keep the number of controls manageable so the report remains readable on a laptop or tablet.

Design dashboards for retail decisions

Rebuild the report as several focused pages rather than one crowded screen. An executive page can show net sales, orders, average order value, refunds and stock exceptions. A product page can rank SKUs, categories and suppliers. An operations page can focus on fulfilment time, cancelled orders, pickup activity and low-stock locations.

Use scorecards for headline measures, time-series charts for movement and tables for action lists. Conditional formatting can highlight products below a stock threshold or stores with unusual refund activity. Geographic charts may help with state-level performance, but a store table is often more useful when managers need to act on a specific location.

Australian retail calendars should be represented in the dashboard. Add filters for public holiday periods, school holidays, major promotional events and the end of the financial year. A retailer serving customers in Adelaide, Canberra and Brisbane may see very different demand patterns, so a national average can conceal local conditions.

If marketing reports use video or campaign content, source notes can be stored beside performance data. Using YouTube transcripts can help teams classify recurring campaign themes and connect content activity with traffic or sales without manually reviewing every video.

Validate the rebuilt reports

Run the old and new reports side by side for at least several reporting periods. Select a sample of orders and trace each one from the source system through the transformed dataset into the dashboard. Test completed orders, partial refunds, cancelled orders, split shipments, gift cards and products with multiple variants.

Check totals at several levels: daily, weekly, monthly, store, channel and category. A report can match the monthly total while still assigning sales to the wrong store or date. Pay particular attention to GST rounding, Australian time zones, currency formatting and the treatment of shipping income.

Give managers a short data dictionary and a report ownership schedule. Someone should know which person or team maintains product mappings, checks failed refreshes and approves changes to calculated fields. Keep a versioned copy of formulas and source extracts so a changed WooCommerce plugin or Magento extension does not silently alter historical results.

A practical replacement for the former NCR dashboard is therefore a governed reporting system rather than a collection of attractive charts. Build the model around stable keys, explicit GST and refund rules, controlled inventory definitions and Australian trading periods. Then validate every headline number against its source before relying on the dashboard for stock, marketing or financial decisions.