RestioX Help Center

Create an account and the 14-day free trial starts without a card. If you would rather not do the configuration yourself, the free setup service does it: you send your menu, branding and payment details, and the team builds the ordering site, the QR menu, the delivery zones and the payment connection. That route typically goes live in five to seven days.

No. The setup service migrates the whole menu — descriptions, prices, images and add-ons — together with your coupons, delivery zones and business details from the platform you are leaving. If you would rather build it yourself, the menu is edited in the admin and published to the till, the website, the QR menu and the kiosk in the same action.

There is, and not from an app store. The staff app is a progressive web app: staff open it in the phone browser, sign in, and choose Add to Home Screen, after which it has its own icon and opens full screen. Because it is served from your own installation, an update reaches every handset the next time it is opened.

Permissions are granted per action rather than per job title, and they are enforced on the server, so a device cannot talk its way past them. A sensitive action can be denied outright, or allowed only behind a manager PIN typed at the moment it happens. Cancellations, refunds, voids, discounts and price changes are written to the audit log with the person and the minute.

In your ordinary order list. Uber Eats, Wolt, Bolt Food, Talabat and Grab connect as two-way integrations, so their orders arrive alongside your own, fire the same kitchen tickets, deduct the same stock and land in the same reports, while status changes travel back to the platform as the kitchen works.

Ten online gateways — Stripe, PayPal, Razorpay, Paystack, Flutterwave, Mollie, Xendit, PayFast, Tap and Epay — each enabled per restaurant with your own keys, and each able to run in sandbox before you go live. In-person card terminals sit on a separate provider-agnostic layer, and cash and cash on delivery are always available.

Only where you allow it. Branch scope is applied in the data layer rather than remembered query by query, so orders, staff, inventory, customers and reports return the signed-in user’s branch by default. The all-branches view and cross-site reporting are permissions you attach to specific roles, such as an area manager or the owner.

One named person, for one drawer, for one shift. A register session opens with a declared float, closes with a count entered denomination by denomination, and produces a Z-report recording counted cash, expected cash and the difference. A difference goes to a manager to approve or reopen rather than being quietly absorbed.

Three ways, and all of them are yours to run. Reports export to Excel or PDF. The backup module takes a full database backup on the schedule you set and restores from the same screen. And the REST API reads the same records the till and the kitchen screen use.

There is a documented REST API, and no separate key to buy. You create a staff account for the integration, post its credentials to the login endpoint, and send the bearer token you get back on every request. The token carries its own restaurant and branch context, and the role on that account decides what it may reach. Each installation also generates its own endpoint reference inside the admin.

Use the contact form, the email address or the phone number at the bottom of this page. Response speed follows your plan, and which tier includes priority support is set out on the pricing page. Sending your restaurant name and what you were doing when it went wrong usually saves a whole round of questions.

Yes. Plans move up or down at any time, billing runs monthly or yearly with a discount for paying yearly, and there is no contract to sit out, so you can stop whenever you like. The staff seats, table count, menu-item limit and the modules each tier unlocks are listed in full on the pricing page.