What is custom software and integration work?
Custom software is an application written for one business’s way of working. Integration is the work of linking systems so that an order, a payment or a stock count enters once and shows up everywhere it should. Most operations teams need both.
Restrologic builds them for restaurants, delivery companies, logistics teams and other businesses where mistakes in data cost money every day.
What we build
Our custom work falls into four groups.
- Marketplace integrations. Swiggy and Zomato connected to your POS, so orders arrive at the kitchen without a tablet on the counter.
- Payment and accounting links. Card-machine payments at the POS, payment gateways, and exports into accounting tools and ERPs.
- Internal tools. Admin panels, approval flows, roster tools, dashboards and report builders that replace spreadsheets and chat threads.
- Operations engines. Routing, allocation and tracking logic for fleets, riders and trucks.
How does the Swiggy and Zomato integration work?
A direct marketplace integration connects the aggregator’s order and menu systems to your POS through their partner interfaces. The order reaches the kitchen, the menu stays in step, and the outlet’s status is controlled from one place.
In the Restrologic POS suite, the online-order desk, called Link, does the following.
- Accepts orders automatically, so a busy kitchen does not miss them.
- Syncs the menu to the marketplace.
- Switches items and whole stores on and off, for example when stock runs out or an outlet closes early.
- Brings ratings and complaints into the same screen as the orders.
- Records aggregator-collected tax correctly, including CGST, SGST and aggregator liability for GST.
The old way is to run each aggregator’s tablet and retype or reconcile later. The table shows the difference.
| Task | Tablet per aggregator | Direct integration |
|---|---|---|
| Order entry | Staff retype or run parallel screens | Order flows into the POS and KOT |
| Menu change | Edit on each portal | Change once, sync to each |
| Item out of stock | Switch off on each tablet | One action, applied to each channel |
| Reporting | Merge exports by hand | One report across dine-in and delivery |
We built this on the same platform that runs about 300 live outlets, so the connectors have run at real volume. Read about the restaurant industry work for the wider picture.
What other integrations do we build?
Payments and ERPs are the next most common requests. The pattern is the same each time.
- Find the source of truth for each piece of data: order, customer, stock, ledger.
- Map the fields between systems and decide what happens when they disagree.
- Build the connector with a log of every message, so a missing order can be traced in minutes.
- Alert a named person when a sync fails, instead of failing quietly.
- Reconcile daily, so differences are caught while they are small.
Exception handling is the real work. The happy path is easy to demo. The value is in what happens when a payment is half-completed or a menu item does not exist on the other side.
What proof do you have?
Inside restaurants, the POS suite is the proof. It carries direct Swiggy and Zomato integration, card-machine payments, e-bill, a call-centre phone-order flow and receipt printing, across about 300 live outlets.
Outside restaurants, the Zippee delivery platform shows the other side of custom work: a Go backend with live rider tracking, geofences that mark arrival, OTPs for delivery and pickup, partial deliveries and photo proof of delivery.
Our team’s wider experience, none of it a case study, includes:
- Route optimisation where zones are sized to one truck’s daily capacity. A job with 16,000 stops dropped from about 3 hours to about 4 minutes.
- Employee transport operations: rosters, vehicle allocation, driver assignment and tracking links.
- A truckload freight marketplace with vendor bidding, GPS trip tracking and proof of delivery.
- A fleet telematics reporting engine with scheduled exports.
- Case and records management for a public-sector organisation.
- A multi-vendor proxy routing SaaS with usage billing.
Who is this for?
- Restaurant brands running more than one marketplace and more than one outlet.
- Delivery, fleet and logistics firms that need tracking and proof of delivery.
- Operations teams held together by spreadsheets and WhatsApp groups.
- Businesses with a good system that lacks one connection, such as POS to ERP.
If you are building a product to sell to many customers, see SaaS and product development.
How does an engagement run?
- Audit. We look at your current stack, the data each system holds and where people retype it. You get a short written scope.
- Design. We agree the data flow, the failure rules and who is alerted.
- Build. We deliver connectors and screens in small releases that you can test on real data.
- Go live. We roll out outlet by outlet or team by team, and watch the logs closely in the first days.
- Support. We stay on call for partner changes and new requests.
Next step
Send us a list of the systems you use and the manual step that annoys you most. Contact Deepak and we will tell you what can be connected and what needs a rebuild.