Retail and checkout

A checkout that refuses a payment on a Saturday costs more than a year of testing.

Checkout is the only place in the store where an anomaly immediately turns into a lost sale — and in queue who sees all.

Make an appointment

The actual surface

It's not a checkout, it's a chain of actors.

A payment transaction involves the cash register software, the payment terminal, the bank acquirer, the loyalty program, private-label payment methods, vouchers and gift cards, and sometimes a third-party promotional system. Each is provided by a different supplier, on its own schedule.

A defect rarely arises within a single building block. It arises at the junction—a discount accepted by the loyalty program but rejected by the register, a receipt that fails to print the correct description, a payment method active in one store and missing in the next. Nobody tests the junctions, because they belong to nobody.

What we are verifying

Three levels, from parameterization to the printed ticket.

Fleet configuration

What every point of sale actually contains, compared to all the others.

  • Active payment methods and their identifiers
  • Discounts, their amounts and descriptions
  • Service fees, taxes, rounding

The checkout journey

The transaction replayed from end to end, in the combinations that actually cause failure.

  • Shared payment, cancellation, refund
  • Combined loyalty and discount
  • Resumption after network incident

Customer proof

The receipt, because it is the only document the customer takes away.

  • Text of the discount actually printed
  • Breakdown of taxes and amounts
  • Consistency with what the cash register recorded

What it finds

On a park compared to itself.

Read-only readings of an entire retail chain's park, without immobilizing a single point of sale.

28
payment methods, no discrepancy between stores
85
comparative discounts, including 3 reviews
3
different labels for the same discount

This last figure is the most instructive: the same discount applied three different labels depending on the point of sale. Same amount, so invisible in the financial statements — but this is the text that gets printed on the customer's receipt, and it's what triggers a complaint. An audit that only looks at amounts misses it.

Frank questions

What we are asked for

Should a store be closed for testing?

No for the parameter comparison, which is done in read-only mode on the configuration interfaces. Yes, occasionally, to replay real transactions with a payment terminal—this is generally done in a pilot store or in a laboratory, outside of opening hours.

Do you work with payment terminals?

We are testing the chain all the way to the terminal and its return to the cash register. Actual bank transactions go through your acquirer's test environments: this is a prerequisite that must be obtained early, as it determines the schedule.

And omnichannel — online ordering, in-store pickup?

It is the same logic, with one more boundary: the order created online must exist in the store, with the correct status and the correct amount. We check both sides and, above all, their junction, which is where things break.

How long for a first result?

Two to three weeks for the first complete comparison of the park, once access is open. The first pass on a park that has never been compared systematically finds something—that is the most profitable part, and the cheapest.

Let's talk about what you can't test yet.

A no-obligation audit of your testing process to find out where you really stand.

Make an appointment
en_USEnglish