Recreating NCR’s order approval workflow in WooCommerce

NCR Retail Online has been discontinued, pushing retailers toward alternatives such as Magento and WooCommerce through NCR Counterpoint partners. Recreating NCR’s order approval workflow for B2B customers in WooCommerce is less about cloning every screen than preserving the controls around trade accounts, pricing, credit and purchasing authority. Buyers need to build an order, lodge it for review and receive an authorised decision without calling sales for routine purchases.

Australian B2B buyers expect prices in Australian dollars, GST treated correctly and a clear record when a manager changes a basket. A Sydney procurement officer may ask a Melbourne colleague to “send it through”, while an approver may require a cost centre, project code or written reason for a price override. Those requests become system requirements when an order crosses stores, warehouses and approval teams.

The target flow is simple: a buyer creates a cart, the system checks account and catalogue rules, an authorised approver reviews it, and approved orders proceed to payment or release. A rejected order should return to an editable draft. Every transition needs a timestamp, actor, previous status, reason where relevant and an exportable audit trail.

WooCommerce does not include this full approval chain in standard checkout, so the safest approach is usually a focused extension or custom plugin rather than theme edits. Teams should document legacy behaviour, test edge cases and protect search visibility while catalogue URLs move. NCR’s transition planning guidance offers a practical starting point for retaining organic rankings during platform changes.

Map the legacy approval journey

Begin by listing the states the old system could produce, such as draft, pending approval, changes requested, approved, awaiting payment and processing. Give each state one owner and define what can happen next. A status label alone is insufficient; approval should also record whether the buyer changed quantity, price, delivery date or funding details after submission.

Write down the people involved: sales representative, buyer, cost-centre manager, finance approver, warehouse operator and administrator. Some requests may need one approval, while larger orders may require two. Australian organisations often combine commercial authority with budget authority, so the replacement should let a company approve by role, account, spend threshold or cost centre rather than by named user alone.

Catalogue, customer and order fields also need mapping. Capture account number, ABN, purchase-order number, project code, GST treatment, delivery location and any credit terms carried from NCR. Keep legacy identifiers in order metadata so finance can reconcile old transactions, but make the new system—not the discontinued platform—the source for future reporting.

Define roles, limits and account rules

Approval rules should combine a baseline with exceptions. A buyer may submit up to a set dollar value, while higher values, new products or discounted lines need a manager. Rules can vary by trading account, warehouse, cost centre, product category, delivery state and the difference between quoted and current pricing. Store the version of each rule with the decision for later audit.

Separate who requests approval from who grants it. A sales representative can help assemble the order but should not approve their own discount, and an administrator should not quietly bypass the threshold. Use least-privilege WordPress roles, WooCommerce capabilities and multi-factor authentication for approvers. Notifications should identify the exact order and the action required without exposing another account’s pricing.

Geography matters in Australia. An order leaving a Melbourne warehouse for regional Victoria may have different freight terms from stock moving between Sydney and Brisbane, while remote delivery to Western Australia or the Northern Territory can alter margin and lead time. Include freight, installation and disposal charges in the approval view rather than revealing them after approval.

Build the workflow inside WooCommerce

A practical build uses custom order statuses such as pending-approval, changes-requested and approved-awaiting-payment, supported by a controlled order endpoint or an established B2B plugin. Store approval metadata through WooCommerce’s order APIs, not direct database writes, and use HPOS-compatible order storage. This keeps records readable when the storage model, hosting provider or plugin set changes.

Within the plugin, create the order without taking payment, validate the buyer, account and cart, then lock editable commercial fields. An approver can approve, reject with a reason or request changes. Payment and fulfilment hooks should run only after a valid approval token or status transition. REST API calls and webhooks should be authenticated, idempotent and logged so a repeated request cannot create duplicate release orders.

Imports from old documents need care. NCR account statements or purchase orders may arrive as password-protected scans; PDF decryption before OCR explains why protected files must be unlocked before text recognition. Keep imported values as proposals until an approver verifies them against the live account, and retain both the source document reference and the corrected field values for reconciliation.

Shape the B2B ordering experience

The customer journey should separate drafting from commitment. Let an authenticated trade buyer see negotiated prices and available credit, add a purchase order and internal note, then submit the order for approval. Do not expose an approval action to an anonymous shopper or to the buyer who created it when policy requires an independent decision. A clear status label and expected response time reduce chasing.

Product rules should follow the risk of the purchase. Standard catalogue items may use account-based limits, while made-to-order furniture needs a quote or manager review. The legacy furniture catalogue illustrates the sort of range where size, finish and delivery can alter cost. Validate those options before submission, but preserve a line-level record of any later change.

Use plain Australian business language: “Awaiting approval”, “Changes requested” and “Approved for processing” are easier to scan than internal codes. Show who owns the next action, when it was submitted and why it was returned. Buyers should receive one consolidated update rather than an email for every field, while approvers should receive a daily digest for low-priority requests.

Protect approvals, payments and records

Treat approval data as sensitive commercial information. Use HTTPS, secure hosting, unique administrator accounts, MFA for finance users and regular WooCommerce, WordPress and plugin updates. Sanitise notes and imported documents, apply file-type checks and keep audit events outside the customer’s editing permissions. A compromised approver account is a direct route to unauthorised credit or discount, not merely a website security problem.

An approval must not override pricing, tax, credit or payment controls. Recheck the approved subtotal, 10% GST where applicable, freight, account credit limit and available stock before payment or release. Australian invoices should carry the correct ABN and GST treatment, while purchase-order systems should prevent the same order being invoiced twice. These checks belong in a server-side service because browser-submitted totals cannot be trusted.

Privacy and retention rules apply to account contacts, buying habits and approval comments. Under the Privacy Act, collect only what the workflow needs, publish a clear privacy notice, restrict exports and set a sensible retention period. Log access to sensitive orders, test account removal and preserve the minimum evidence required for tax, fraud and contractual disputes.

Compare implementation approaches

There are three practical routes. The choice depends on approval complexity, transaction volume, internal skills and how much legacy behaviour must remain.

Plugin configuration suits predictable thresholds and familiar roles, but check compatibility with HPOS, tax, subscriptions and the chosen theme. A bespoke plugin fits unusual account structures or several legacy stores, provided someone owns its security and documentation. Manual email approval can bridge a short migration, yet it leaves reconciliation and duplicate-release risk with staff. For retailers managing several brands or branches, NCR’s multi-store management after NCR discusses the transition issues that a single catalogue must resolve.

Move from legacy to controlled operation

Roll out in stages. First recreate status rules, then pilot with a small group of buyers and approvers in one store, including rejections, price changes and partial fulfilment. Compare approval time, errors and credit exposure with NCR, then expand to more locations. Keep a read-only archive of legacy orders and document the cutover date, support contacts and rollback process before taking the new workflow live.

The next concrete step is to open a clean WooCommerce sandbox and configure one pending-approval order with a buyer, an approver and one rejected revision.