Building a Fallback Plan for Counterpoint Sync Outages

A Counterpoint synchronisation failure can interrupt far more than stock updates. Online orders may continue arriving while the point-of-sale system shows old quantities, staff may lose confidence in availability, and customers can receive conflicting information about delivery or pickup. A practical fallback plan keeps sales moving while protecting inventory accuracy and customer trust.

Australian retailers need to prepare for these interruptions across different trading conditions. A fashion shop in Melbourne, a gift store in Brisbane, and a multi-location retailer in Perth may all rely on the same retail management system, yet face different delivery windows, staffing patterns, and customer expectations. The plan should be simple enough for a busy Saturday and detailed enough for a prolonged outage.

Map The Systems And Failure Points

Start by documenting how information travels between Counterpoint, the ecommerce platform, payment services, shipping tools, email marketing, and staff devices. Record which system is the source of truth for product descriptions, prices, stock levels, customer details, refunds, and fulfilment status. This map reveals what can continue independently and what depends on a successful sync.

Separate a total outage from a delayed or partial connection. A failed integration may stop stock updates while orders still enter the web store. In another incident, inventory may synchronise but price changes or product edits may not. Each condition needs a different response, so define clear symptoms for “pause online sales”, “sell with caution”, and “operate offline”.

NCR Retail Online has been discontinued, and retailers transitioning through NCR Counterpoint partners may use platforms such as Magento or WooCommerce. That makes it important to document the current environment rather than assume an old integration guide still applies. Keep credentials, vendor contacts, plugin versions, and escalation procedures in a restricted but accessible location.

Set Safe Trading Rules

The most important decision is whether the store remains open online. If inventory is unreliable, hide products with low stock, disable click-and-collect, or temporarily switch to a narrower catalogue. A short pause is usually less damaging than accepting orders that cannot be fulfilled, especially for popular products with only one or two units remaining.

Create a buffer for uncertain stock. For example, a retailer might allow online sales only when Counterpoint shows at least three units, reserving the remainder for in-store customers and manual corrections. This approach is useful during busy periods such as Boxing Day, school holidays, or a weekend market event when stock can move quickly.

Set rules for staff transactions as well. They may continue using the POS if sales are recorded locally, but they should avoid manual product creation, price changes, and stock transfers unless a manager approves them. Consistency matters more than speed when records will later need to be reconciled.

Keep Orders And Payments Controlled

If the web store remains active, assign every order a clear status such as “received during outage”. Export or print an order queue at regular intervals, including the customer name, item, quantity, paid amount, delivery method, and contact details. Store copies securely and restrict access to staff who need them.

Do not process a payment twice simply because an order has not appeared in Counterpoint. Check the ecommerce payment gateway before retrying a charge, and record transaction IDs alongside each order. For bank transfer or manual payment arrangements, verify cleared funds before dispatching goods.

Australian businesses should also consider privacy obligations under the Privacy Act 1988 when copying customer information into spreadsheets or temporary systems. Use business devices, limit downloaded data, protect files with access controls, and delete temporary records when reconciliation is complete. The fallback process should preserve payment and customer information without creating a second uncontrolled database.

Communicate Clearly With Customers

Prepare short templates for delayed confirmation, stock verification, dispatch delays, and cancelled orders. Avoid promising same-day delivery or pickup until the inventory position is confirmed. In Australia, shipping expectations can vary sharply between inner Sydney, regional New South Wales, and remote parts of Western Australia, so messages should allow for carrier and distance differences.

Email scheduling can help maintain a measured communication rhythm once service resumes; these email timing practices are useful when sending outage notices, revised dispatch updates, or back-in-stock messages. However, scheduled messages should be paused if they depend on stock data that has not yet been corrected.

Give store teams a single approved explanation. A brief statement such as “our stock systems are being reconciled, and we will confirm availability shortly” is better than different staff inventing technical explanations. Record every promised callback and follow it through, particularly for customers who have travelled to collect an item.

Create Practical Recovery Checklists

A fallback plan works only when people can execute it under pressure. Keep printed instructions near the POS and store a digital copy in a location available during an internet or server incident. Include vendor contacts, opening hours, account numbers, and the authority required to pause the online store.

Immediate outage actions

• Confirm the affected systems and record the start time
• Pause risky products, pickup options, or promotions
• Export open ecommerce orders and check payment status
• Nominate one incident owner and one customer contact

Before restoring normal sales

• Compare physical counts with Counterpoint records
• Confirm the ecommerce catalogue, prices, and stock buffers
• Check that failed orders have not been duplicated
• Approve a controlled restart with a time recorded

Run the checklist during a quiet trading period at least twice a year. Include a simulated sync delay rather than testing only a complete system shutdown. Staff in Adelaide or Canberra may follow the same procedure as a Sydney team, but local delivery cut-offs, roster coverage, and store layouts should be reflected in each location’s version.

Reconcile, Secure And Improve

When synchronisation returns, do not assume that the systems have repaired themselves correctly. Freeze non-essential edits, take an export or backup, and reconcile activity in a defined order: completed sales, refunds, cancellations, stock receipts, transfers, and ecommerce orders. Mark each exception for review instead of silently forcing totals to match.

Review security before reopening every channel. A platform change or emergency integration can alter administrator accounts, extensions, hosting settings, and payment flows. Retailers moving to a replacement ecommerce system should understand PCI compliance requirements, particularly where payment pages, card data, and third-party services are involved.

Hosting resilience also deserves attention. A dependable fallback may still fail if the replacement store has weak backups, limited monitoring, or insufficient capacity during a campaign. Compare hosting options for recovery procedures, support availability, security controls, and Australian customer demand patterns before selecting a long-term platform.

After each incident, measure the duration, number of affected orders, stock discrepancies, refunds, and customer contacts. Identify which manual steps caused delays and update the runbook while the details are fresh. The purpose is not to eliminate every outage, but to reduce confusion and make the next response faster and safer.

A strong fallback plan gives staff permission to slow down in the right places, protects customers from inaccurate promises, and creates a controlled path back to normal operations. The key thing to remember is that when Counterpoint sync fails, continuity depends on clear trading limits, careful records, secure communication, and disciplined reconciliation.