01
Begin with customer context
Before a line is priced, the system should make clear whether the sale is cash or account, which customer is being served and what commercial terms apply. A price shown without that context may be technically valid but commercially wrong.
The same context should remain visible when quantities change or another product is added. Staff should not have to remember which price source was used.
02
Make exceptions deliberate
There will be legitimate occasions when an authorised person changes a price. The important controls are visibility, permission and traceability. A changed price should not become an invisible new normal for another customer.
During a software review, ask who may change a line price, what they can see before doing so and how the final invoice reflects the agreed transaction.
- Customer and account identified
- Price basis visible
- Quantity and unit confirmed
- Exception authority understood
- Final invoice matches the sale
03
Connect pricing to the account
For an account sale, pricing is only one part of the decision. The team may also need to understand terms, account status and whether the order is being quoted, supplied or invoiced. Keeping these records connected reduces rekeying and makes later questions easier to answer.
A useful system should support the commercial conversation without exposing information to roles that do not need it.