How to Mirror Daily Sales Totals Between Counterpoint and Ecommerce

Running a retail business in Australia usually means juggling a busy shopfront in Sydney or Melbourne with an online store that ships parcels to Perth, Cairns, and everywhere in between. When the till rings at 5pm, every dollar of takings should land in the same report whether the customer bought in-store or paid through the website, and a tidy end-of-day summary keeps stock counts honest and tax time straightforward.

Getting those daily totals to agree across Counterpoint and your ecommerce platform used to flow naturally through NCR Retail Online. With that product now discontinued, retailers are rebuilding the bridge using partner-led migrations to Magento and WooCommerce. The mechanics of the daily sync remain the same regardless of the new home: define what counts as a sale, push it on a schedule, and reconcile the totals before the team arrives the next morning.

Why Daily Reconciliation Matters Down Here

Australian retailers work under a 10% Goods and Services Tax on most domestic sales, and the Australian Taxation Office expects clean records that reconcile bank deposits with reported turnover. If your Counterpoint ledger says one thing and the ecommerce backend says another at the end of June for EOFY, the accountant will not be your favourite person. Daily reconciliation shortens the feedback loop and makes the financial year-end far less painful.

Beyond compliance, customers notice when stock counts drift. A Sydney shopper who clicks "in stock" on a pair of sneakers only to be told the warehouse is empty loses trust quickly, and bad word travels fast on local buy-and-sell groups. Boxing Day queues in Melbourne's CBD are legendary, and a missed sale there because the website thought the floor was bare is the kind of mistake that costs far more than the original margin.

The Data Points That Must Travel Together

Every transaction that moves between Counterpoint and the ecommerce platform carries the same payload: a unique order identifier, the SKU, the quantity sold, the unit price including GST, any promotional discount, the shipping charge paid to Australia Post or a courier, and the net amount deposited into the merchant account. Leave any of those fields blank and the totals will not match at the end of the day.

Payment surcharges and buy-now-pay-later fees add another layer. Australians love Afterpay, and many shoppers will abandon cart if it is missing, but the surcharge that Afterpay withholds needs to be reflected in the daily summary so the bank reconciliation stays honest. Category-level reporting matters just as much, especially for high-volume lines like wine and spirits where the buying team watches margin closely and any drift between the till and the website quickly shows up in the category P&L.

Preparing Counterpoint for a Clean Daily Export

Counterpoint holds the master record for most Australian retailers, so the export has to be pristine before it leaves the building. Confirm that the workstation is running a supported version of NCR Counterpoint with database access enabled, and audit the SKU file so that the SKUs used online match the SKUs used on the back office exactly. A single mismatch — like a hidden space in "WINE-GIFT-01" — will silently drop a line from the daily summary.

Time zones are another trap. Australia spans AEST, AEDT, ACST, and AWST, and daylight saving ends on the first Sunday of April in the southern states while Queensland stays put year-round. Lock the export schedule to Australian Eastern time so the report always runs at midnight Sydney time regardless of where the server sits. The shop in Adelaide will get its numbers labelled consistently, and no one has to ask why Tuesday looks short.

Configuring the Receiving Platform

On the other side of the bridge sits the new ecommerce platform. Whether the choice has landed on WooCommerce for a smaller boutique in Brisbane or Magento for a multi-store operator with warehouses in every state, the receiving end needs the same three things: a secure REST API connection, a webhook that triggers on completed orders, and a clear status mapping that says what an online order looks like once it has been imported into Counterpoint.

Field mapping is where most of the friction lives. Counterpoint speaks in departmental hierarchies that ecommerce platforms do not always understand, so a gift pack sold under the drinkware category on the website may need to land in a department that handles glassware in the back office. Build a mapping document before the first sync runs, and the team will spend less time untangling mismatched categories later.

Scheduling the Daily Sync Window

Pick a sync time that respects the trading rhythm of an Australian retail business. Most shops close around 6pm, and the ecommerce orders placed between 6pm and midnight AEDT are usually the largest batch of the day. Running the reconciliation at 1am gives the platform half an hour to settle, the payment gateway time to clear, and the Counterpoint server a quiet moment to compile the report before staff log in for brekkie.

Run the job every day, including weekends and public holidays. Australia Day, ANZAC Day, and Easter long weekends all produce unusual sales patterns, and skipping the sync because it is a public holiday creates a Monday morning that nobody wants. The script should run on Australian time, send a summary email to the store manager at 7am, and raise an alert if the variance between Counterpoint and the ecommerce platform exceeds a sensible dollar threshold.

Troubleshooting the Discrepancies That Will Appear

Even with everything wired up correctly, there will be days when the totals do not match. The usual suspects are rounding — Australian GST is calculated per line and can produce a one-cent variance on large baskets — and timing, where an order placed at 11:59pm AEST lands on the wrong side of the sync window. Build a tolerance into the reconciliation report so that a 30-cent discrepancy does not generate a panic email every morning.

Refunds are trickier still. A customer who returns a bottle of red online at 10pm and a customer who walks into the Melbourne showroom to return the same SKU at 11am the next morning both need to appear in the daily summary, but they often travel through different paths. Map the refund order status carefully and review the weekly reconciliation to catch any patterns before they build up into a meaningful gap.

Rebuilding on a New Platform After Discontinuation

With NCR Retail Online now discontinued, the long-term home for most retailers is either Magento or WooCommerce, and the partner that handles the transition takes responsibility for rebuilding the daily sync from scratch. Data migration covers customer records, product catalogues, and historical sales, but the ongoing pipeline is what keeps the lights on once the project is signed off. Spend time on setting up discount and coupon systems on your new platform before the launch, because promotional pricing that drifts between the two systems is one of the fastest ways to lose margin on a busy trading day.

Pick a partner who has done the work before and who understands the Australian retail calendar. EOFY, Boxing Day, and the lead-up to Christmas each bring their own traffic spikes, and a sync that breaks on the busiest day of the year is not much of a sync at all.

The trick is a locked schedule, a quick variance check each morning, and treating the report as the only version of the truth. With those habits in place, the daily sales summary will tell the same story whether someone reads it in Counterpoint or on the ecommerce dashboard — which is the only outcome the accountant, the buying team, and the warehouse manager will all accept.