01
What the counter needs to see
An account customer may have an agreed credit limit, but the working decision depends on more than one number. Staff need to know the current balance, the value of the proposed sale, whether invoices are overdue and whether the account has been placed on stop.
That information is most useful beside the sale, before goods are promised. Moving it to a separate report makes the counter slower and increases the chance that somebody relies on an old figure or an informal message.
- Current balance and available headroom
- Overdue invoices and agreed terms
- Active account-stop status
- The effect of the proposed order
02
Separate a warning from an account stop
A warning asks the user to review the situation. An account stop prevents further credit sales until the status changes. Those two states should not look or behave alike.
Merchants should decide who can change terms, adjust a limit or release an account stop. The system should then apply that permission consistently rather than relying on whoever happens to be serving the customer.
03
Make exceptions visible and accountable
Sometimes an authorised person may permit a sale that takes an account beyond its normal position. That exception should be deliberate, linked to the sale and available for later review. It should not silently alter the customer’s permanent limit.
During a software demonstration, ask the supplier to show an account close to its limit, an overdue invoice, an account on stop and an authorised exception. Then ask which roles may act and where the decision appears afterwards.
OperiQ keeps account position and sales context connected in the merchant workspace. The exact credit policy remains the merchant’s decision.