Restroworks (formerly Posist) and Tuckly

A programme, not a plug

Some POS vendors let any developer create an account and start reading the API the same afternoon. Restroworks is not one of them, and it is better to know that up front. Integrations with Restroworks go through a technology integration programme with defined stages, a sandbox, a dedicated engineer on their side, and a commercial agreement. That is a serious way to run a platform, and it also means a Tuckly connection cannot be switched on quickly.

What Restroworks is

Restroworks is the restaurant technology platform formerly known as Posist. It handles billing, kitchen tickets and reporting for restaurants in India and elsewhere, and it publishes a partner marketplace of connected services. Its own marketplace pages state that orders from Swiggy and Zomato flow directly into the Restroworks system, which is the behaviour a direct-order integration would aim to match.

What a connection would do

For a restaurant on Restroworks, the integration would carry four things between the two systems.

Orders in. A customer places an order on your Tuckly site. Instead of a staff member re-keying it, the order is written into Restroworks so the kitchen ticket and the sales record happen exactly as they do for a marketplace order.

Menu out. Items, variants, modifiers and prices held in Restroworks would be read into Tuckly so the ordering site shows what the POS has, at the POS’s prices.

Availability. An item marked unavailable in Restroworks would hide on the ordering site until it is switched back on.

Status back. When the kitchen accepts an order or marks it ready, Tuckly would show that status so the customer-facing side and any delivery step stay in sync.

Payment reconciliation is not part of the picture. Your payment gateway settles to your bank; Restroworks records the sale. Matching the two remains an accounting job.

How the programme runs

Restroworks publishes its process. An integrator applies, and Restroworks says its partnership team gets in touch within two business days. A discovery and alignment phase follows, where scope and commercial terms are agreed. Then build and test on a sandbox, with a dedicated integration engineer. After that a pilot at live outlets, go-live, and an ongoing governance stage. Restroworks quotes six to ten weeks to go live overall and says most integrations take four to eight weeks from sandbox access to pilot launch.

There is a one-time implementation fee for integrators. Restroworks does not publish the amount, and we are not going to put a number on it here. Any cost that affected what you pay would appear on the pricing page before it applied to you.

What this means if you run Restroworks today

You can take direct orders now. Orders from your site arrive on the Tuckly order screen, and staff enter them into Restroworks the way they would a phone order. The integration would remove that step, nothing more. For a single outlet with a modest number of direct orders, the retyping is a minor cost. For a group with a central menu team and several kitchens, the sync is worth the wait, and the number of outlets asking for it is what moves it up our list.

If that is you, say so through the contact page. Knowing the outlet count and whether marketplace orders already flow into your Restroworks helps us scope it properly.