Price Override

A till may show a different amount from the shelf tag, and staff may need to correct the customer's transaction immediately, which solves that sale but not the underlying data problem. In a fictional example a cashier sees a product scanned at $12 when the valid shelf label says $10, and a manager approves the correction before the store fixes the price file or label.

Shopify documents POS roles and permissions and Square describes item price overrides across locations, which illustrate different controls, but the business must set a policy that fits its operation. Overrides can be manual discounts, corrected prices or special contract terms, and these should be kept distinct in reporting.

A planned promotion should ideally be configured centrally rather than retyped for every sale, as in a fictional case where a retailer applied a weekend 15% promotion through manual overrides because the system was not updated and then loaded the next campaign in advance to reduce errors. Location-specific pricing may also be deliberate, since Square's feature can set variations for locations, so a fictional chain that holds approved local prices for two regions is not producing unauthorised manual overrides, unlike a cashier's one-off exception.

Set permissions by role and amount, so a cashier may handle small corrections while larger exceptions need approval, although too many barriers can delay fair treatment of customers. In a fictional case an employee needed to honour a valid advertised offer but waited ten minutes for manager approval, so the business adjusted the threshold and trained staff on eligible cases.

Capture who changed the price, the original and new amounts, date, item and reason, because audit logs protect employees as well as the business and a bare final price cannot explain the exception. Logs also help interpret patterns fairly: when a fictional shop saw ten overrides on one SKU, the logs showed all were valid shelf-label corrections, so management fixed the label rather than suspecting ten staff members.

Controls also deter misuse, since an employee could underprice goods for an associate or hide a wrong discount, so review unusual patterns fairly and investigate before attributing intent. A fictional owner who noticed repeated late-night overrides checked promotions, returns and customer incidents, and found the pattern might reflect a training issue, not theft.

A price override differs from a refund, because an override changes the sale price before or during the transaction while a refund returns money after a sale, and systems may record them differently. When a fictional buyer discovers an overcharge after leaving, the store follows its adjustment or refund process and does not pretend a later price-file edit changed the old receipt.

Check tax and promotion interactions as well, since changing base price can alter tax or eligibility for other discounts, so test the total on the receipt and not only the line amount, as a fictional store learned when it overrode a clearance item, accidentally stacked another coupon and pushed the final price below policy until the POS team fixed the rule and trained staff. Monitor override frequency, value and reasons by store or product, since a high rate can signal bad master data, misleading labels or excessive discretionary discounts.

A fictional branch with 100 overrides among 10,000 sales has a 1% rate, while another with 30 among 500 has a 6% rate, so raw counts alone make the first look worse and the team compares rates and reasons instead. Customer law matters too, because an internal override policy cannot override consumer rights, and a fictional employee told never to change a till price must follow local rules when a valid advertised offer conflicts with the till; close the loop by updating incorrect labels or price files, documenting the remedy and retesting, because a price override is a controlled exception, not a substitute for accurate pricing, and valid corrections should be easy while misuse stays visible.