Integrations.
Connects to what you already run.
Part 16 of 17 · 1 min 5 s
Transcript
What the narration says, word for word (translated from the Spanish voice-over).
In this video: how it connects to what you already have running.
Batuta doesn't try to replace your time and attendance system or your payroll. It connects to them, with your own credentials, and each one keeps doing its job. With time and attendance connected, publishing a week sends the plan across on its own, and the real attendance comes back into your reports. Here you can see the date of the last push and the last sync.
The same with HR, to import your staff with their contracts instead of typing them in, and with the point of sale, which is what turns labour cost into a percentage of sales. Every connection is tested before you rely on it. And if one fails, it never blocks publishing: the week publishes anyway and the error is flagged.
Want to see this with your own venue's shifts and staff? Write to us at usebatuta.com.
Recorded on a demo restaurant: invented names, no real person's data. There is no pilot running yet, so you will not see customer results here.