Building a Reliable Fulfilment Workflow Beyond NCR Retail Online

When NCR Retail Online was discontinued, retailers using its connected ecommerce, inventory and business management features had to rethink how online orders moved from checkout to dispatch. The replacement does not need to copy the old platform feature for feature. It needs to preserve stock accuracy, clear staff responsibilities and dependable communication with customers.

For an Australian retailer, fulfilment is shaped by local conditions as much as by software. A store in Melbourne may ship daily from a central stockroom, while a retailer in regional Queensland may need to account for longer carrier routes, weather disruptions and limited collection windows. GST-inclusive pricing, Australia Post services, click and collect and public holiday trading calendars also need to fit into the workflow.

A practical substitution workflow separates the essential activities from the retired product: product data, stock control, order capture, payment, picking, packing, dispatch and returns. Magento, WooCommerce or another ecommerce platform can handle the customer-facing layer, while NCR Counterpoint partners may help connect retail records and operational systems during the transition.

Map the fulfilment process before choosing software

Start by documenting the route of a typical order. Record what happens from the moment a customer places an order through payment approval, stock allocation, picking, packing, shipping notification and delivery. Include exceptions such as a partial shipment, a cancelled line, an oversold item, a failed payment or a customer choosing click and collect.

This process map will expose where NCR Retail Online previously automated work. For example, inventory synchronisation may have reduced the risk of selling the last item in a Brisbane shop through the website at the same time it was sold in person. If that synchronisation disappears, the replacement workflow needs a defined stock update interval, an inventory buffer or a manual exception queue.

Separate the workflow into three layers: the ecommerce storefront, the system of record for stock and products, and the fulfilment tools used by staff. One platform may cover several layers, but naming the responsibilities prevents confusion. A low-cost WooCommerce installation can still produce reliable results when stock ownership and order status rules are explicit.

Prepare product and inventory data for migration

Product data is often the least visible source of fulfilment errors. Create a clean catalogue containing SKUs, barcodes, variant relationships, dimensions, weights, tax treatment, supplier references, images and available quantities. Use one stable SKU for every sellable variation, such as size and colour, rather than relying on a product title that staff may edit later.

Historical exports can help, but they should be treated as source material rather than a perfect database. Retailers transferring variant information can use this CSV variant transfer guide to understand how exported fields may be structured before importing them into a new catalogue. Test several products with multiple options, bundles and discontinued variations before attempting a full upload.

Stock availability should be defined operationally. “Available” might mean physically on the shelf, sellable after reserving online orders, or accessible at another store. For Australian businesses with locations in Sydney, Adelaide and Perth, a shared stock pool may create unrealistic delivery promises. Consider location-level stock, safety quantities and a rule that prevents the final unit from being sold online until a staff member verifies it.

Inventory checks to schedule

• Compare online stock with a physical count for priority products
• Review oversold, reserved and damaged units each trading day
• Reconcile stock after transfers between stores or warehouses
• Audit discontinued, hidden and seasonal products before promotions

Connect orders to picking, packing and dispatch

The order status model should be simple enough for casual staff to follow. A useful sequence is paid, ready to pick, picked, packed, dispatched, delivered or exception. Avoid treating “processing” as a catch-all status because it hides whether an order is waiting for stock, payment review or a carrier label.

At the picking stage, produce a clear pick list grouped by location or fulfilment method. A Melbourne showroom handling local collection may need a separate collection shelf, while a warehouse in Western Australia may need orders consolidated before the afternoon carrier cut-off. Barcode scanning is valuable, but a printed checklist and a second-person verification step can provide a workable fallback during internet or device outages.

Packing rules should capture the details that affect freight cost and customer expectations. Record the parcel dimensions, weight, tracking number and carrier service. Australia Post, Sendle, Aramex and other carriers may offer different coverage, collection arrangements and delivery estimates, so the checkout promise should use realistic service zones rather than a single national estimate.

For click and collect, send a message only after the item is physically located and checked. Staff should verify the order number and customer name at handover, with a documented process for an authorised person collecting on someone else’s behalf. This is especially important during busy periods such as Boxing Day sales, when queues and duplicate collection emails can quickly create disputes.

Build controls for customer service and exceptions

A substitution workflow is tested most seriously by exceptions. Define what staff should do when an item cannot be found, a customer orders two units but only one is available, or a payment remains authorised without being captured. The action may be a refund, a replacement product, a delayed dispatch or a request for customer approval, but it should not depend on an individual employee’s memory.

Keep an exception queue outside ordinary order processing. Give every case an owner, a due date and a short reason code. Useful categories include stock discrepancy, address problem, payment review, carrier delay, damaged goods and customer change request. This creates a manageable workload for a small team and gives managers evidence about recurring problems.

Customer communications should be timed to real events. An order confirmation means the purchase was received; it should not imply that stock has been packed. A dispatch message should include the carrier and tracking details only after the parcel has been handed over. For Australian customers, clear wording around delivery to parcel lockers, PO Boxes, remote areas and apartment buildings can prevent avoidable support contacts.

Returns need the same structure as outbound orders. Record the return request, approval, received condition, refund decision and inventory outcome. Products returned to saleable stock should not be made available again until they have been inspected. Gift purchases also deserve a defined path: retailers can review gift shopping options when shaping gift-related catalogue and fulfilment content, especially around gift cards, seasonal products and recipient-friendly returns.

Exception rules worth documenting

• Missing stock: pause fulfilment and verify nearby locations
• Damaged goods: photograph, quarantine and assign a replacement decision
• Address errors: hold the parcel until the customer confirms details
• Carrier delays: record the scan history before promising a new date

Measure performance and protect the handover

Choose a small group of fulfilment metrics that staff can act on. Order accuracy, time from payment to pick, time from pick to dispatch, stock discrepancy rate and refund turnaround are more useful than a large dashboard filled with passive statistics. Track click-and-collect readiness separately from shipped orders because the service promise is different.

Security controls should cover account access, payment information and exported files. Use role-based permissions so casual staff can pick and pack without changing product prices or refunding orders. Enable multi-factor authentication where available, review connected applications and store CSV exports in a restricted location. Never place full payment card details in spreadsheets or email attachments.

Run a staged handover instead of switching every process on a single day. Pilot the new workflow with a limited product range or one store, compare stock and order outcomes, then expand. Schedule testing around Australian trading realities: do not use a quiet Tuesday alone as proof that the process will handle a Saturday rush in Sydney or a pre-Christmas promotion.

Keep a written fallback procedure. It should explain how to accept an order if the storefront is unavailable, how to reserve stock, how to record a manual payment exception and how to notify customers. A controlled spreadsheet may be suitable for a short outage, provided it has an owner, version control and a reconciliation step once systems recover.

Put ownership and review into daily operations

Technology will not maintain an accurate fulfilment workflow without assigned responsibility. The ecommerce owner can manage catalogue and checkout settings, the inventory lead can approve stock adjustments, and the dispatch lead can control carrier handover. Smaller businesses may combine these roles, but the duties still need to be named.

Create a daily rhythm around the order queue. At opening, staff review payments, stock exceptions and urgent collections. Before the carrier cut-off, they check packed orders and tracking details. At close, they reconcile dispatched orders, unresolved discrepancies and returns received. This routine suits businesses in Australia where a late carrier collection or public holiday can shift the next available delivery day.

Review the workflow after promotions, range changes and carrier changes. If customers repeatedly receive an “in stock” message for items that cannot be found, adjust the stock buffer or counting process rather than simply apologising. If dispatch is consistently late, inspect pick-list design, staff coverage and cut-off promises before adding another integration.

The immediate next step is to document one complete order journey, including a stockout and a click-and-collect order, then assign an owner to every action before selecting or configuring the replacement platform.