Card terminals in Reinbek, Germany

Choose the payment point around the queue

A fixed counter gives staff a consistent place to complete sales, but it can become a bottleneck when collection customers and new orders arrive together. Taking payment at a table may reduce counter traffic, while moving the task of identifying the correct bill to the staff member carrying the terminal.

Mobile use suits workflows where customers do not approach a fixed checkout, but device handover, charging and coverage become operational decisions. Software partners should map one busy shift with the merchant before proposing hardware: where does the sale begin, who requests payment, and who confirms it is complete?

Verify connectivity where payments actually happen

Do not assume that a connection working beside the till will work equally well throughout the premises. Identify proposed payment locations, including tables, collection points and any outdoor service areas. Ask the team which connection methods the proposed device supports and what happens if connectivity is interrupted.

The trade-off is practical: a fixed position may be easier to power and supervise, while a moving terminal gives staff more flexibility but introduces coverage and battery checks. Test the agreed configuration in realistic locations. A successful check means staff can see a clear payment outcome and match it to the sale, not merely that the terminal connects.

Give staff a clear rule for uncertain payments

During a rush, an unclear result is more disruptive than a straightforward decline. Decide which available record staff should consult, who may investigate and what the customer should be told while the outcome is checked. Do not treat a delayed software screen as proof that payment failed.

NeroConnect is for connecting software/POS providers and their merchants to payment services. Partners should confirm supported devices and integration options with the team before promising a connected workflow. Where staff must enter amounts separately, include an explicit amount check and sale-reference check in training.

• Identify the sale and the payment attempt without starting another charge.
• Check the available payment status using the agreed process.
• Escalate unresolved outcomes through the confirmed support route before deciding whether to retry.

Hypothetical example: collection orders meet table service

Imagine a software partner helping a Reinbek café that handles collection orders alongside seated customers. At lunchtime, one employee serves the collection counter while another takes payments at tables. If both share one terminal, customers may wait while staff search for the device, even when order entry is quick.

The partner compares a shared counter arrangement with separate payment points, subject to device availability and commercial terms. In a rehearsal, staff process a collection order while another customer pays at a table, then practise an uncertain result. The success check is observable: every sale has an identifiable outcome, staff know who owns each enquiry, and nobody retries merely to clear the queue.

Separate payment confirmation from settlement

A confirmed customer payment and funds reaching the merchant are different checkpoints. Before choosing a service, ask about settlement timing, reporting, applicable deductions and how refunds or adjustments appear. Confirm the arrangements for the merchant’s German business rather than assuming terms used in another market apply.

Also separate software costs from payment costs. With an eligible NeroPay card terminal, NeroPOS, NeroWeb and NeroBooking software can be included without an additional software subscription charge. Terminal costs, payment processing charges, eligibility and applicable terms still apply. Existing software partners should confirm compatibility rather than assume they must replace their merchant software.