Retail Merchant Services Comparison: Test the Same Store Basket

Prepare a neutral comparison brief

Describe the store’s locations, current checkout software, ordinary basket size, monthly activity and online or telephone channels. State what needs improvement: manual tender entry, missing stock records, difficult returns or confusing charges. This gives each provider the same problem to address.

Keep a list of requirements separate from preferences. Barcode scanning and traceable partial returns may be mandatory; a particular device appearance may be optional. Ask every provider to mark what is included, separately priced, dependent on another app or unavailable. An unanswered row is not a confirmed feature.

Normalize the cost categories

Use the same historical period and the same transaction categories for each proposal. Separate transaction charges, recurring software, gateway services, equipment, implementation and optional applications. Identify one-time costs separately from ongoing ones.

Ask the provider to explain assumptions about card mix, transaction channel and volume. An advertised percentage does not establish the full cost of the store’s activity. Treat any estimate as a scenario based on named inputs, then compare the actual first statement with the accepted proposal after implementation.

Demonstrate a complete basket and return

Give each provider the same fictional basket: two units of a barcode item, a product variation and a manager-approved discount. Ask to see item entry, payment, receipt and stock movement. Do the exercise under a cashier role rather than only through an administrator’s demonstration.

Then return one item and inspect the merchandise disposition, refund record and report. Ask what happens when a refund needs approval or the original record cannot be found. The best comparison reveals how the store works on an imperfect day, not only how fast a demonstration sale completes.

Examine the boundaries between products

Ask whether payments, catalog management, online ordering, loyalty and accounting are part of one service or several. Record the named support owner for each. A supplier offering an integration should explain the supported version and what data moves in each direction.

Check export and exit requirements before committing. Ask what the store can export, in what format, and how access to historical transactions works after cancellation. Do not assume that owning a device gives unrestricted access to every associated software record forever.

Use weighted decisions with visible evidence

For a small store, a practical scorecard might give more weight to correct returns and staff usability than to a long list of optional features. Choose the weights before the demonstrations so a striking screen design does not silently change the priorities.

Mark each answer as demonstrated, confirmed in writing or still unresolved. A provider’s promise to investigate should remain an open item. Keep the demonstration references and proposal version. This makes the final decision explainable to the owner and reduces confusion when the implementation team takes over.

Close the gaps before switching

Resolve equipment obligations, cancellation arrangements, data migration and the first trading-day support route in the actual agreements and implementation plan. Ask the appropriate adviser about contractual terms rather than assuming a generic comparison overrides them.

Keep an acceptance checklist with the basket, return, closeout and export checks. Review the first full statement and the first stock adjustment cycle after launch. A sound comparison ends with evidence that the selected arrangement meets the store’s named requirements, without promising universal savings or a perfect provider.

A comparison record with evidence levels

Use columns for requirement, current arrangement, provider A, provider B, evidence and unresolved question. Record exact proposal versions for costs and a demonstration date for workflow answers. A blank row should stay unresolved rather than becoming an assumed yes.

For example, score partial returns using the same basket and employee role in both demonstrations. Ask to locate the original item and payment afterward. If one provider needs another application, add that application’s cost, support owner and export requirements before comparing the total arrangement.

Should the lowest quoted percentage win? Only after the same activity and complete costs are compared alongside the store’s requirements. Is a long feature list evidence of suitability? Ask for the actual needed workflow. Can a verbal assurance settle an agreement question? Have the provider identify the relevant written term and obtain appropriate advice for any contractual decision. Preserve unresolved differences for follow-up before accepting the proposal.