Getting started

Plan the move around your restaurant.

Keep your existing system while you prepare and test RestaKit. Switch each workflow when your team is ready.

Getting started

  1. Tell us what you need

    Tell us which tasks and connections matter to your restaurant. We can help with setup or quote for custom work.

  2. Choose hosting and installation

    Use your hosting account and pay the host directly. Early access includes deployment, installation and human testing for up to three locations sharing one menu. Different menus are quoted separately. We help you prepare the hosting access needed for setup.

  3. Prepare menus and data

    Send us your menu, prices, photos and dish options. We set up one supplied menu shared across up to three locations as part of early access. Different menus are quoted separately. Tell us about any data migration or advanced menu work so we can quote it separately.

  4. Test a shift

    Check alongside your existing system:

    • Orders, choices and extras, and kitchen tickets.
    • Bills and the payment setup you have confirmed.
    • Closing figures and exports.
    • Staff permissions and service devices.
    • Backup and recovery procedures.

    RestaKit or your developer can help with these checks and any adjustments before you switch.

  5. Choose ongoing help

    Choose RestaKit, your developer or your own team to manage hosting, access, updates and backups. Keep the installation and operating instructions available. Ongoing services are separate from deployment.

    Hosting your software

    For installation options, see Choose hosting and installation.

    If you manage these yourself, follow the operating instructions. Initial deployment for up to three locations sharing one menu is included with early access. Different menus are quoted separately. Hosting and ongoing services are paid separately.

Use RestaKit on your phone, tablet or computer.

Access your restaurant software through a web browser. Choose a screen that suits the job, from browsing the menu on a phone to managing service on a larger display.

Devices and screens

Use an up-to-date browser and choose a comfortable screen size for each task.

TaskSuitable screen
Guest menus and orderinga smartphone or tablet.
Table menusa tablet with an easy-to-read screen.
Counter ordersa larger tablet or touchscreen.
Kitchen ticketsa screen you can read from your working position.
Menus, stock and reportsa laptop, desktop or larger tablet.

Printers

Receipt and kitchen printers are optional. Printer connections depend on the model and connection type. We can help you choose a setup for your restaurant.

Payments and terminals

Confirm your provider, country and payment workflow. Recording a payment taken elsewhere does not connect or control that terminal.

Connections to other systems

The developer documentation can help your developer build a connection. Each new connection still needs technical checks and development.

Internet access and regional requirements

Menu browsing and ordering need a connection to your restaurant software. Online payments and connected services need internet access. Your payment provider and local rules determine currency, tax and receipt requirements.

Backups and recovery

Choose who backs up and restores your installation. Record what is backed up, where it is stored, how often backups run, how long they are kept and who can access them. Test recovery before service and follow the procedure before changes.

Restoring the previous software version and recovering data may require separate steps. Managed backups are not included by default.

Discuss your setup

Need help choosing equipment?

Tell us which equipment or services you want to connect. We can help with setup or quote for a custom integration.

Tell us what you need help with in the application form.

Website analytics

Allow PostHog to measure page visits and clicks? We do not record sessions or form entries. You can change your choice in Analytics settings.