DERequest a demo

Integrations

Restaurant connections with clear setup requirements.

Payments, bookings, accounting and printing have different requirements. The overview separates existing workflows from the devices, settings and import processes to check for your specific business.

Request a demoContact

Connections: scope and requirements

This overview describes existing workflows. It does not grant compatibility for every provider or device; the specific combination is reviewed during setup.

AreaDocumented workflowCheck before use
Payment terminalPayment transaction and payment-status feedback at the POS.Review the specific terminal model, payment service, network connection and handling of uncertain responses.
ReservationsEmbed a booking page on your website; organise reservations and table allocation.Agree embedding, areas, capacities, time slots and required guest information for your operation.
Accounting / DATEVPrepare an EXTF CSV posting batch, run preflight checks and create the handover file.Agree the period, recipient details and account mappings. Test the recipient’s specific import with a sample file.
Printing and preparation stationsAssign orders to the relevant work areas and output routes.Define devices, connections, paper formats and print destinations. Test the workflow with the actual devices.

Integration principle

Purpose first, interface second.

Compatibility, scope and regulatory requirements must be reviewed for every specific combination.

Payments & checkout

Payment methods, devices and operational payment workflows are aligned to the configuration.

Read article

Accounting & export

Data handovers and export requirements are reviewed for the specific use case.

Read article

Guests & reservations

Existing booking and guest structures are considered in process planning.

Read article

Print & peripherals

Workstations, printers and handover points are considered along the workflow.

Read article

Team & identity

Roles, access and staff processes need a clear, secure framework.

Read article

Analysis & control

Reporting and data handovers should support decisions, not create new spreadsheets.

Read article

Before setup

These questions get us to the right decision faster.

  • Which systems and devices are already in use?
  • Which data needs to go where?
  • Which roles, permissions and privacy needs apply?
bonzumoReporting & closing
In focus01
Today↗
Status●
Active work12:45Team handoverliveReport ready✓

A payment at the table, a booking through your website and records for accounting all connect your venue with other devices or services. Clear handovers help your team work with related transactions. Bonzumo includes integration functions built around practical hospitality tasks, with the relevant setup assessed for your business.

A payment terminal connection is available in the system. Before use, the device, payment service and configuration need to be checked against your workflow. Start with the situations you actually handle: counter sales, payment at a table, separate bills or a transaction that prompts a question from the guest or your team.

An embedded booking page can bring reservations into your own website. Guests gain a place to book while you organise reservation work in the system. Preparation includes discussing dining areas, capacities, booking times and the information you need to welcome guests. That connects the online booking point with the work at reception.

A DATEV booking batch export is available for accounting preparation. Required settings and mappings depend on your operation and the intended accounting process. Online gift card purchases also have a payment connection. Each connection needs the relevant service accounts and configuration to support the agreed workflow.

For a useful conversation, bring a short overview of your current devices and services. Explain where information is entered twice or where details are lost during a handover. You can then work through the required process and check the appropriate connection. Request a demo around these transitions to assess the practical benefit in the context of your own business.

Explore this topic

Guide overview: Connect payments and checkout in a restaurant: understand every amount and payment status: Payment starts before a guest reaches for a card; Plan voucher redemption and the remaining payment together; Use your own payment cases in a demoConnect payments and checkout in a restaurant: understand every amount and payment statusFrom the table bill to a card terminal, plan payment around your service and verify the devices and providers that fit your actual setup.Guide overview: Prepare restaurant accounting and exports: from daily closing to a traceable handover: Accounting begins during service; Agree accounts and revenue categories with a specialist; Run a trial with the accountant who receives the dataOrganise your restaurant accounting handover clearlyAgree the period, supporting documents, responsibilities and recipient of your accounting records. A clear handover makes questions and unresolved transactions visible.Guide overview: Connect guest and reservation workflows: from online request to the right restaurant table: A guest request is more than a calendar entry; Keep changes and cancellations visible; Ask for a demo of a complete guest journeyConnect guest and reservation workflows: from online request to the right restaurant tableA reservation book helps when reception, floor plan, and service understand the same guest request. Plan the workflow before relying on an external connection.Guide overview: Set up restaurant printers and peripherals around the way your team works: Print routes start with the actual workflow; Pass on special requests and courses clearly; Assess the right print route in a demoSet up restaurant printers and peripherals around the way your team worksFrom kitchen tickets to bar output, plan print routes around real workstations and check equipment, responsibility and interruptions in your venue.Guide overview: Staff identity and access in hospitality: clear roles for every work area: A team needs clear identities instead of shared logins; Several workstations need one shared standard; A demo with real roles makes the benefit visibleStaff identity and access in hospitality: clear roles for every work areaPersonal logins, understandable permissions and careful handovers help your team work while keeping sensitive responsibilities clear.Guide overview: Restaurant analysis and control: understand your data and ask better questions: The most useful metric starts with a question; Connect reporting questions with stock and staffing; Turn numbers into one testable decisionRestaurant analysis and control: understand your data and ask better questionsUse reports, closing data and export preparation for practical decisions, with clear periods, responsibility and traceable transactions.

Next step

Let us review your existing system landscape.

Request a demo