Guides / Buying · 3 min read
Questions to ask during a merchant software demo.
A useful demonstration follows the work through the system. It should show what happens when the order changes, stock is short, the customer is on account or the goods need to be delivered.
By the OperiQ team
1. Begin with a real working scenario
Do not begin with a long feature list. Give the supplier a fictional but recognisable order: an account customer wants several product lines, one line is short, part of the order is collected and the rest goes to site.
Ask the demonstrator to identify the customer, apply the correct price, check stock, decide how the short line will be sourced and keep the fulfilment choice on the order. This shows whether the system connects the work or simply presents separate screens.
- Can staff find products by description, code or barcode?
- Where is customer-specific pricing shown?
- What does available stock exclude?
- Can one order support collection and delivery decisions?
2. Ask what happens when things change
Most demonstrations show the straightforward route. Merchant work is often defined by the correction: the quantity changes, the customer moves a delivery, the supplier sends a different amount or an invoice needs attention.
Ask the supplier to amend the fictional order after it has progressed. Look for a clear record of what changed, whether the stock and account position remain consistent, and which roles may approve the decision.
For a trade account, test an overdue balance and an account stop. For purchasing, receive a different quantity from the purchase order. For delivery, change the site note and ask where the driver sees it.
3. Check migration, access and evidence
A product demonstration should also explain the move from the current system. Ask which records can be imported, how a test migration is checked and what the merchant must approve before launch. A credible answer will qualify the result according to the source data rather than promising that every field will move.
Ask who can see cost-sensitive or customer information, how permissions are applied and how support access is controlled. Finally, distinguish a genuine product screen from a mock-up and fictional example data from customer evidence.
OperiQ demonstrations use fictional merchant data and the real interface. If a requested workflow is not supported, it should be stated plainly.
See how OperiQ handles this on your own work.
Book a meeting