UrbanPiper and Tuckly

Middleware, explained for a restaurant

Think of UrbanPiper as a switchboard. Orders come in from many channels and go out to one POS. A restaurant that takes orders from three marketplaces and has a POS that cannot talk to any of them can connect everything to UrbanPiper Hub instead, and the orders arrive in the POS as if they had been typed there. That is the problem UrbanPiper solves, and it is why it sits in this directory under middleware rather than POS.

UrbanPiper’s site lists a wider product range than Hub. Meraki is a branded ordering website and app product. Prime is UrbanPiper’s own POS. Orderline AI handles phone orders. The company says it is trusted by more than 40,000 restaurants globally, and its site offers versions for India, the UAE, Saudi Arabia, the UK, the US, Canada, Australia, Mexico and Egypt, among others.

Where Tuckly would fit

UrbanPiper’s API documentation describes two kinds of partner. Downstream partners are POS, ERP, till and billing systems: they receive orders, menus are pushed to them, they send fulfilment status back, and they can turn items and stores on and off. Upstream partners are the ordering channels. The documentation describes endpoints that an upstream partner’s backend consumes to send orders in, with a sandbox for testing and a certification step before go-live.

A Tuckly connection would be upstream. An order placed on your site would be sent into UrbanPiper, which would forward it to your POS through whichever downstream connection you already have. Menu and availability would travel in the opposite direction so the ordering site reflects what the POS knows.

The upstream partners UrbanPiper documents include DotPe, Gupshup, ChatFood, Deliveroo, DoorDash, Careem and Dunzo. Tuckly is not on that list today.

The part we cannot tell you

UrbanPiper does not publish commercial terms for upstream partners. Access is arranged by contacting UrbanPiper’s product team, and the documentation points to email and a shared Slack channel rather than a sign-up form. We do not know what it would cost, and we would rather leave that blank than invent a figure.

There is also an obvious tension to name. Meraki is UrbanPiper’s own direct-ordering product, marketed as commission-free, with pricing that UrbanPiper says depends on the scale of your business and your order volume. A platform that sells its own ordering site has a reasonable commercial interest in how it treats competing ordering sites. That does not mean a connection is impossible, since UrbanPiper already lists competing ordering tools as upstream partners, but it is a factor.

What the connection would and would not do

It would move orders and menu data. It would not touch payment settlement, which stays between your gateway and your bank. It would not add delivery: a direct order that needs a rider still goes through Porter, your own staff or pickup on the Tuckly side.

It would also add a dependency. Every order would pass through three systems instead of two. When all of them are up, nobody notices. When the middle one is not, orders can stall between the site and the kitchen. That is a general property of middleware rather than a criticism of UrbanPiper, and it is worth weighing against the convenience.

A practical suggestion

If your POS has its own route, check that page first. For Petpooja, Toast, Square, Clover and Lightspeed, a direct connection is usually simpler than going through a switchboard, and the status of each is on its own page in the integrations directory. If your POS is only reachable through UrbanPiper, or you already run Hub for your marketplace orders and want direct orders to join the same flow, tell us through the contact page. Demand is what decides which connections get built.