Recreating NCR’s buy online, pick up in store workflow in WooCommerce

NCR Retail Online has been discontinued, so recreating NCR’s Buy Online, Pick Up in Store workflow in WooCommerce means rebuilding its operating rules rather than reviving retired software. Customers still need to find eligible stock, reserve it, pay securely, choose a collection point and receive a verifiable handover. Behind that journey sit product data, store inventory, order routing, notifications and exception handling.

For an Australian retailer, a practical starting point is WooCommerce as the online sales layer while the POS or ERP remains authoritative for physical stock, tax records and financial reporting. This suits concentrated networks in Sydney, Melbourne and Brisbane, where shoppers can order on a phone during a commute and collect near work or home. It also creates a portable transition path for teams working with NCR Counterpoint partners, whether they select WooCommerce, Magento or another stack.

Define the operating model before choosing plugins

Start with a service blueprint that names the system responsible for product truth, sellable stock, price, tax, customer identity, order status and financial reconciliation. The NCR architecture planning guide offers a useful decision-making pattern: separate sales channels from core records so one store transaction does not create several conflicting versions of the truth.

Where the current POS already records the stock ledger, WooCommerce should request availability rather than become a second stock authority. The order, reservation and collection workflow can live in WooCommerce, supported by an integration layer that exchanges identifiers and status changes. That boundary keeps the reconstruction maintainable if a retailer later changes its POS or ecommerce platform.

Avoid rebuilding every former NCR feature. Record the required behaviours and integration contracts instead: an availability response, a reservation, an order-placed event, a collection event and a cancellation or refund event. Each contract needs an owner, expected response time, retry rule and reconciliation process, making it easier for an NCR Counterpoint partner to support or replace individual components.

Build one accurate store stock pool

Model each physical pickup site as a WooCommerce pickup location with a stable store identifier, trading zone, opening hours, collection counter, service capacity and time zone. Keep stock at SKU-and-variant level and track on-hand, reserved and available-to-promise quantities. A product may be eligible at one store yet unavailable at another, so a single global “in stock” flag cannot support reliable collection promises.

Synchronisation should be event-driven where possible and periodically reconciled regardless. WooCommerce REST API calls can apply accepted stock changes, while webhooks can trigger fulfilment events, but no webhook should be the only control. Include idempotency keys, duplicate-event handling, dead-letter reporting and a daily comparison between WooCommerce reservations and the POS ledger to expose missed or duplicated movements.

The content migration needs the same discipline as inventory. Use the NCR catalogue migration advice to preserve product codes, image references and descriptions while mapping them to clean WooCommerce identifiers. Rewrite supplier text where necessary, add useful alt text, compress images for mobile and keep old NCR URLs in a redirect map. Stable SKU and product identifiers make stock reconciliation and future search-engine migration less error-prone.

Route orders and take payment safely

A pickup selector should match the customer’s suburb or postcode against participating stores, then check both stock and collection capacity before presenting a choice. A standard WooCommerce pickup extension can cover basic location selection, while complex estates need custom logic for reservations, priority stores and alternative branches. If no branch qualifies, the customer should see a clear delivery option or an explanation of why collection is unavailable.

Australian shoppers expect familiar payment choices, including cards, PayPal, Apple Pay, Google Pay and buy-now-pay-later services such as Afterpay. Configure the gateway to support Australian-dollar transactions, successful and failed captures, partial refunds and full cancellation. A prepaid pickup order should not default to cash on collection; where a store accepts an offline exception, it needs a documented reconciliation and receipt process.

Order states should mirror the physical process: awaiting payment, confirmed, reserved, ready for collection, collected, cancelled, expired and refunded. Reservation expiry releases the stock hold and either voids an uncaptured authorisation or follows the gateway’s refund process for captured funds. Where 99shoutbox integrations participate in gift fulfilment, include them in the same cancellation, partial-redemption and refund cases as ordinary card payments.

Design collection communications and staff handover

After payment, send an order confirmation with the store name, address, pickup window, order number and a secure collection code. Email should provide the full receipt; SMS or push messages can carry the practical reminder without exposing unnecessary personal data. If readiness moves forward, send a specific “ready now” notice, and if it slips, offer a revised time rather than leaving the customer to guess.

Legacy entitlement checks can prevent support gaps during transition. Use the archived NCR gifts catalogue as a reference for identifying legacy gift and redemption features, then confirm which behaviours still have commercial meaning. Test these cases with the replacement platform and document who authorises refunds, how unused balances are reported and what a customer sees when a gift card cannot cover an order.

Staff need a compact pick screen, a printed or digital pick list and a handover routine that verifies the order number plus collection code. Masked customer details should be visible at the counter, with the full record available only when policy allows. In dense pickup zones, collection windows must use each store’s local time: Perth and Adelaide sit in different zones from the eastern states, and daylight-saving changes can shift displayed appointments. Local parking, loading-zone and public-transport constraints should shape the promised window as well.

Protect payments, data and Australian obligations

Keep cardholder data inside a PCI DSS-compliant payment flow, preferably through tokenisation or hosted fields, and give store staff no access to full card details. Enforce multi-factor authentication for administrators, least-privilege roles, patching, encrypted backups and access logging. Store pickup reduces the checkout journey but expands the set of people and devices handling an order, making configuration and audit controls essential.

Under the Australian Privacy Act 1988 and applicable state or territory privacy laws, collect only what fulfilment needs and explain the purpose of names, contact details and pickup data. Set retention and deletion rules, support access and correction requests and document a data-breach response. Transactional pickup messages are distinct from marketing, but promotional content added to those messages still needs to comply with the Spam Act 2003 and applicable consent rules.

Australian Consumer Law governs the promise made at checkout. Availability, substitutions, damaged items, cancellation, refunds and collection deadlines must be stated clearly and handled consistently; a customer should not discover a material condition or charge only at the counter. Display prices in Australian dollars, normally including GST, and configure tax treatment around the actual selling entity and where the taxable supply occurs. A billing-address-only tax rule can be wrong for cross-state collection, so tax settings should be reviewed by an Australian tax adviser.

Pilot the service and hand over operations

Pilot one store with representative fast-moving products, low-stock products, oversized items and products requiring age verification. Test simultaneous orders for the last unit, delayed POS updates, expired holds, failed payments, partial refunds, damaged substitutions and customers arriving outside their window. Monitor stock accuracy, reservation release time, order-to-ready time, collection completion, refunds, support contacts and pickup no-shows rather than relying only on conversion.

Training should follow the actual counter workflow, including how to locate stock, confirm a reservation, resolve a mismatch and escalate a refund. A recorded demonstration is easy to share across shifts, while a YouTube transcript guide makes the same material searchable and accessible to staff who cannot watch the full video. Store managers can pair the recording with a scenario test and a one-page decision guide.

After the pilot, reconcile every order, reservation, payment and stock movement, archive the NCR mappings and remove the retired platform from hidden operational dependencies. Preserve product identifiers, approved redirects and historical order access so customers using old links or saved receipts still receive support. The concrete next step is a two-week pilot at one Melbourne store using 20 representative SKUs, two daily pickup windows, one reserved-stock pool and nightly reconciliation, followed by a recorded go/no-go review after the first week.