OperiQ

Guides / Counter · 3 min read

Keep the customer and the price together.

Trade pricing becomes difficult when the reason for a price is separated from the sale. The counter needs a clear customer context, an agreed basis and a visible route for exceptions.

By the OperiQ team

Merchant staff serving at a counter computer

1. 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.

2. 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

3. 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.

See how OperiQ handles this on your own work.

Book a meeting

Keep reading

Builders’ merchant EPOS explainedRead more →OperiQ trade accountsRead more →Builders’ merchant softwareRead more →

Use the product before deciding.

A private workspace with example merchant data. No card required.