Skip to main content

Every order on one rail.

Keep the payment processor, register and delivery apps you already use. Their orders land in the same RestCall queue as your phone, QR and online orders.

Illustrative orders from marketplaces and your own channels on one rail.

What connects, and which way it works.

Each connection is labelled with what it does today. Planned ones say so.

  • Marketplaces

    Their orders come in to you

    Marketplace tickets sit on the same rail as phone, QR, online and counter orders, so the kitchen works one queue.

    • DoorDash

      Marketplace orders land in the same queue as every other channel.

      Available
    • Uber Eats

      Marketplace orders land in the same queue as every other channel.

      Available
    • Grubhub

      Marketplace orders land in the same queue as every other channel.

      Available
  • Couriers

    Your orders go out with them

    You keep the order and the guest; they carry the bag. Delivery status comes back onto the same order.

    • DoorDash Drive

      Hand a delivery run to DoorDash couriers without giving up the order.

      Available
    • Uber Direct

      Hand a delivery run to Uber couriers without giving up the order.

      Available
  • Payments

    Money settles to your account

    Payments go to your own merchant account. We never hold the money, and card numbers never reach our servers.

    • Stripe

      Online payments and in-person Stripe Terminal, settling to your own account.

      Available
    • Stax

      Card processing through your existing Stax merchant account.

      Available
    • Finix

      Planned payment connection.

      Coming next
  • Point of sale

    Works alongside your till

    Happy with the register you have? Keep it, and let RestCall run the channels that feed it.

    • Clover

      Connected restaurant POS workflows.

      Available
    • Square

      Planned POS connection.

      Coming next
    • Toast

      Planned POS connection.

      Coming next
    • SkyTab

      Planned POS connection.

      Coming next

A connection should remove a job, not add one.

These connections write into the same order, menu and guest the rest of RestCall reads, so there is nothing to match up at the end of the night.

  • One menu, so a price change reaches every channel at once
  • One order queue, whichever channel the order came from
  • One guest record, instead of history split across apps
  • Every connection labelled available or coming next
  • Running your own drivers instead? See Pickup & Delivery

See it on your menu

See RestCall on your menu.

Book a demo and we’ll walk you through how RestCall would take phone orders for your restaurant.

Book a platform demo Explore the platform