Skip to content

Why Batch

The tools you run today, on one system.

A register, a booking app, a time clock, an inventory sheet and a marketing tool is five logins, five invoices and five versions of the truth. Batch is one.

What it replaces

One subscription in place of the tools below.

Each tool bolted onto the register has its own login and its own invoice, and their numbers rarely agree. Batch does the same work on one system.

13 separately billed tools become one system: One sign-in per person, One subscription, Shared records.

  • Point of sale
  • Booking app
  • Time clock
  • Purchase orders
  • Accounting software
  • Loyalty app
  • Gift card vendor
  • Email marketing
  • Kiosk software
  • Menu boards
  • Kitchen display
  • Reporting dashboard
  • Multi-location roll-ups
Batch.All in one

One system

  • One sign-in per person
  • One subscription
  • Shared records

The one system

Sales, staff and stock share one record.

When payments, bookings, staff, stock and marketing share one core, the parts stop disagreeing, and nobody spends the first week of the month making them agree.

  • One sign-in per person

    Everyone signs in to the same system, and their role decides what they can open, at one location or at all of them.

  • One subscription

    One subscription for the business instead of a stack of them, each with its own renewal date and support queue.

  • Shared records

    Sales, bookings, stock and hours are recorded once, and both the reports and, on Plus, the general ledger read that same record.

What it replaces

Every tool in the pile has a home in Batch.

Whichever of these the business pays for today, the same work happens inside a Batch module, on the same customers, the same staff and the same books.

Under it

The part you only notice when it is missing.

None of this is a setting somebody has to remember to switch on.

  • Encrypted at the readerThe pad encrypts the card as it is read, before anything is sent.
  • Never the full numberBatch never stores the full card number or the security code.
  • Access by roleOne role per person decides what they can open, at every location they work.
  • Kept separateEach business’s data is kept separate, and the database adds row-level isolation as a second check behind the application.
  • On the recordThe changes that matter are written to an event log that can be read back.
  • One codebaseRestaurant, retail and services share one database, so a fix is one fix.

Ready when you are

Stop paying for the pile. Start on one system.