Manual Price Overrides in WooCommerce That Survive Sync

NCR Retail Online has been discontinued, so retailers moving through NCR Counterpoint partners need a deliberate pricing model after migration. A catalogue can retain its SKUs, images and descriptions while losing the rules that decided which system controlled retail prices. Without those rules, a manual WooCommerce change may be erased by the next import, while a source-system change may appear in every sales channel.

For teams working out how to set up manual price overrides in WooCommerce without breaking sync, the durable pattern is to separate the imported base price from a temporary adjustment. One calculated effective price should then feed the product page, cart and checkout. This matters in Australia, where consumer prices are commonly displayed GST-inclusive and must reconcile with AUD books, online tax settings and inventory records.

Establish price ownership before changing settings

Choose one authoritative writer for every price field. If NCR Counterpoint or another inventory platform owns the base retail price, its sync should write only that base. WooCommerce should decide whether an approved exception replaces it for a product, variation, store or channel. Keep inventory quantity, cost price and customer-facing price separate, even when an integration currently updates all three.

Before go-live, export product IDs, SKUs, prices and descriptions, then reconcile them against a staging WooCommerce catalogue. NCR’s guide to migrating product records is particularly relevant to carrying images and descriptions into WooCommerce without losing variant context. Preserve each old identifier beside its new WooCommerce ID so later price records can be matched reliably.

Map catalogue and sync boundaries

Create an explicit field map for SKU, stock quantity, cost, regular price, sale price and tax class. If Counterpoint is the base-price source, write that value to a registered custom field rather than WooCommerce’s normal price fields. Exclude the resolved price and override metadata from the importer, then let the WooCommerce pricing service supply the customer price. Australian consumer prices are usually shown with 10% GST included, so the tax configuration and source records must follow the same gross-or-net convention.

Rich content can expose duplicate variants and silent SKU mistakes. Test the mapping with a visually led category: NCR’s page on fine china merchandising provides a useful example of names, imagery and descriptions that should be checked against the migrated catalogue. Confirm that each description, image and barcode belongs to the correct variation before enabling unattended price synchronisation.

Build a durable override layer

Implement the feature as a small owned plugin or integration module rather than a theme snippet. A custom table or properly registered WordPress metadata can store the WooCommerce product or variation ID, store or channel scope, imported base-price snapshot, override amount, start and finish times, status, reason and approving user. Store money as integer cents or another decimal-safe representation, and record whether the adjustment is a fixed amount or a percentage of the current base.

The pricing resolver should use a valid active override when one exists and fall back to the latest imported base price otherwise. Apply that same resolver to storefront requests, WooCommerce REST API responses, carts, checkout calculations and order creation. Expiry times should be stored in UTC and displayed in the relevant Australian store timezone. Repeated synchronisation runs must not extend an expiry date or create duplicate override records.

In the product editor, lock or clearly mark the standard price fields when automatic pricing is enabled. Provide custom controls for the amount, reason, effective period and approval status instead. Define how a manual adjustment interacts with a WooCommerce sale price, coupon and scheduled promotion; otherwise, two valid-looking discounts can produce an unintended final amount. Clear the relevant product and pricing caches after an approved change.

Protect price integrity and administration

Every price calculation path must use the same effective value, including AJAX requests, mobile purchases, restored carts and third-party order channels. After setting an adjustment, run the inventory sync twice and verify that the base price may update while the approved exception remains unchanged. Confirm that stock movements, tax totals, coupon calculations and completed orders still behave correctly. Audit records should capture the previous value, new value, source, user and timestamp; rollback should deactivate the exception rather than erase its history.

Restrict price overrides to trusted roles such as a dedicated pricing manager or shop manager. Validate capabilities, nonces, product scope and numeric values on every request, and escape displayed values. Use prepared database statements or vetted WordPress APIs, restrict access to cost-price metadata and prevent unauthorised customers from calling custom endpoints. Backups should include both WooCommerce product data and the separate override store.

Run overrides as a controlled store process

Give staff a fixed sequence for requesting, approving, applying and expiring a price change. A reason code such as clearance, price-match or event correction makes later audits much easier. Training should demonstrate the distinction between the imported base price and the visible effective price. The same design principle appears in a comparison of guided lesson plans: structured instructions and defined decision points reduce inconsistent handling.

Scope an adjustment carefully when a retailer operates across Australia. A Sydney CBD branch, Melbourne showroom and Brisbane warehouse may share one SKU but have different stock, fulfilment options and local promotions. Store-specific overrides should not accidentally become national prices, and regional click-and-collect rules must not change the online price. Seasonal work around EOFY stocktake, Christmas trading and major sale events benefits from advance approval and automatic expiry rather than open-ended manual edits.

Cover variants, promotions and sales channels

Variable products need variation-level records when the base price differs by size, colour or other option. A parent-level override should apply to all variations only when that behaviour is intentional. Bundles and product add-ons require a defined calculation order so the checkout reflects each component’s current effective price. Save the resolved component prices on the order, because later catalogue changes must not alter an existing customer invoice.

External channels need their own scope and update rules. If campaign timing is triggered by livestreamed product demonstrations, record the event reference and responsible operator with the promotion instead of relying on an informal message. Treat WooCommerce, the point-of-sale system, marketplaces and advertising feeds as separate consumers of the pricing service. Record scheduled promotions as absolute amounts or calculated percentages, define their precedence against manual adjustments, and ensure delayed jobs are idempotent.

A reliable setup lets inventory synchronisation continue without granting it uncontrolled authority over every WooCommerce price field. Product, stock and base-price data can move from the source system while approved exceptions remain attributable, time-limited and visible across the storefront, cart and checkout.

The rule to remember is simple: sync owns the base, WooCommerce owns the approved exception, and every exception remains auditable, temporary and reversible.