A customer buys lipstick in shade A, but the sale records shade B at the same price. The payment is correct, yet stock for shade A has not been deducted, shade B has been deducted incorrectly, and the member's purchase history shows shade B.
A sales transaction connects goods movement, payment, promotions and loyalty benefits. An entry error can affect several records. Corrections should reflect the actual transaction, follow authorized procedures, keep related records consistent and retain the full handling history. For a chain retailer, this is a basic transaction-management capability.
Distinguish entry corrections from returns and exchanges
Start with the nature of the business event. Unconfirmed entries may be edited within the permitted scope; errors in confirmed transactions require controlled adjustment; actual customer returns or exchanges follow after-sales procedures. The transaction facts and related business status determine the route.
| Situation | Handling principle |
|---|---|
| Entry error while the document remains editable | Correct the details and recheck products, promotions and the amount payable before confirmation. |
| Record error in a confirmed transaction | Use a supported correction, reversal or controlled adjustment linked to the original sale, and check related records. |
| Actual customer return or exchange | Handle goods, refunds and benefits through the after-sales process and link them to the original transaction. |
Document status and business effects need separate checks. “Pending approval” describes approval progress, while payment, inventory and benefit records show what has already occurred. Withdrawing an approval request does not itself reverse those effects; the correction must cover the records actually affected.
A new price issued by headquarters is a subsequent pricing-policy change. Confirmed transactions retain their original price. A difference between old and new prices is not, by itself, a sales-entry error.
Link the original sale and reconcile inventory, payment and loyalty
In the lipstick example, payment is correct. The errors concern the item recorded, stock deductions and purchase history. Link the correction to the original sale, define its scope, retain verified correct results and address affected records through the authorized process.
Direct correction, reversal and re-entry, and other controlled adjustments are different document workflows. The brand defines their scope, permissions and approval requirements according to supported system processes. When reversing and re-entering a sale, link the original document, reversing entry and correct document so the changes can be traced.
The customer has not returned the lipstick, so the reason should be recorded as a sales correction. Even if the workflow uses a linked return document and a new sale, the records must accurately reflect where the goods went. Check the following results:
| Area | Expected result in this example |
|---|---|
| Products and inventory | Deduct shade A for the actual sale and restore the incorrect deduction of shade B, avoiding duplicate stock movements. |
| Payment | Retain the correct payment without charging twice. If the process involves refunding and collecting again, verify actual payment outcomes. |
| Loyalty and promotions | Record shade A in purchase history and check points, discounts and gifts under the original transaction rules. |
| Adjustment history | Retain the reason, operator, time and links between the original sale and subsequent documents. |
Equal prices still require promotion and benefit checks: the two shades may qualify for different campaigns. If the incorrect item changed the discount, handle the difference under brand rules. Where a basket-level promotion is affected, check the related items and total amount too.
Completion depends on the actual outcomes across related records. Refunds still processing or member records awaiting correction should retain a progress status and responsible role. The original sale, adjustment basis and execution results form the audit trail, allowing store, finance and loyalty teams to verify the same transaction.
Support controlled adjustments and traceability with PEKON
The PEKON Smart Retail System covers store transactions, promotions, inventory, member-related workflows and operating data. For sales corrections, implementation translates business rules into document workflows, role permissions and record queries, defining the division between system processing and staff checks. Editable details, reversal methods and the scope of linked records depend on the product version and system connections.
Stores initiate handling within their authority; the relevant roles verify stock, payment and benefit outcomes. Subsequent users can refer to the original sale to find the adjustment basis and progress. These arrangements make the process actionable and verifiable and reduce repeated explanations and record searches between teams.
The management requirements are clear: authorized handling, consistent linked records and a traceable adjustment history. Applying them through the retail system supports consistent transaction handling across stores and roles.