Gula

One tablet. Three platforms. Zero order chaos.

Built for Indonesian restaurant chains. Consolidated GrabFood, GoFood, and ShopeeFood into a single screen. Acquired by Runchise.

See case study

The problem

Sound familiar?

  • Staff managing Grab, GoFood, and Shopee on three separate tablets - missing orders in the rush?

  • Marking an item out of stock means logging into each platform separately, one after another?

  • Closing the store for the night means tapping through every platform before anyone can leave?

Short answer

Gula was a B2B food tech platform built for the Indonesian market that consolidated orders from GrabFood, GoFood, and ShopeeFood onto a single tablet screen. Restaurants with multiple kitchens or brands could mark items unavailable across all three platforms in one click, close every platform with one tap, and manage all orders from a single device and printer. It served Domino's, KFC, and Flash Coffee, and was later acquired by Runchise.

Indonesian food delivery runs on three separate ecosystems: GrabFood, GoFood, and ShopeeFood. For a chain running multiple kitchens or brands, that means a different tablet per platform, separate logins, and three separate chances for an order to fall through. When bread runs out, you update it on three apps. When you close for the night, you tap through three apps. When a Grab order comes in while staff are handling a GoFood rush, it gets missed.

Gula was built to eliminate that. One tablet. One printer. Every order from every platform in one unified feed. Read the full case study.

What Gula changed for Indonesian restaurant operators

The problem was not the platforms. It was managing three separate systems as if they were one business.

Before Gula
  • Three tablets, three apps, three loginsGrab, GoFood, and Shopee each needed their own device. Staff switched between screens constantly. Orders fell through when attention was split.
  • Item unavailability updated three timesMarking bread as out of stock meant opening each app separately and updating the menu one platform at a time. One missed update meant orders still coming in for an item you couldn't fulfil.
  • Store close required tapping through every platformEnd of service meant three separate close actions. A rushed close left one platform open, and orders kept coming in after the kitchen shut down.
  • Multi-brand kitchens had no single viewChains running several brands from one kitchen had no way to see all orders in one place. Staff managed by juggling devices.
After Gula
  • One tablet handles all three platformsEvery incoming order from Grab, GoFood, and Shopee lands in one feed. One device. One printer. Staff see everything in a single view.
  • One click propagates availability to every platformMark bread unavailable once. Gula pushes the update to GrabFood, GoFood, and ShopeeFood simultaneously. No more partial updates, no more unfulfillable orders.
  • One tap closes the store everywhereSingle action. All platforms closed. No risk of orders arriving after the kitchen shuts down.
  • Multiple brands and kitchens managed from one screenChains running several brands from a shared kitchen managed all of them through one interface. Brand-specific menus, unified order management.
In practice

Flash Coffee ran several brands from the same kitchen. Before Gula, closing one brand on a single platform while keeping another live required different staff on different tablets. After Gula, one person managed all brands and all platforms from a single screen. What was a three-person coordination task became a one-person, one-device workflow.

Where Gula made the biggest difference

Every feature traced back to the same constraint: restaurant operators in Indonesia needed to run three platforms as one business.

  • 01

    Unified order feed across all platforms

    GrabFood, GoFood, and ShopeeFood orders appeared in one feed, sorted by time. Staff did not need to check which platform an order came from - they just worked the queue.
  • 02

    Cross-platform availability in one click

    Any menu item could be toggled unavailable across all three platforms simultaneously. One action. Three platforms updated. No missed orders for items you cannot fulfil.
  • 03

    Platform-wide store open and close

    Open or close the store on every connected platform with a single tap. Useful for unplanned closures, peak-hour pauses, and end-of-day shutdown.
  • 04

    Multi-kitchen and multi-brand support

    Chains running several brands from a shared kitchen assigned orders to the right kitchen without confusion. Each brand had its own menu configuration; all shared the same operator dashboard.
  • 05

    Single tablet and printer workflow

    All orders printed to one printer regardless of source platform. Kitchen staff worked from printed tickets without needing to know which aggregator generated the order.
  • 06

    Real-time sync across GrabFood, GoFood, ShopeeFood

    Menu changes, availability updates, and store status changes pushed to all connected platforms in real time. No manual sync required.

Why restaurant chains in Indonesia chose Gula

Three platforms, one operator, one device. That was the promise. Here is how it held up in practice.

  • 01

    Enterprise-ready from launch

    Domino's, KFC, and Flash Coffee built their multi-platform operations on Gula. Pizza Hut and Tanamera ran active trials. The platform was designed to handle the order volume and menu complexity of established chains, not just independent restaurants.
  • 02

    Inventory management that actually propagates

    Most workarounds required staff to update each platform manually. Gula treated cross-platform availability as a first-class feature, not an afterthought. One change hit all three platforms simultaneously.
  • 03

    Multi-brand, multi-kitchen native

    Chains running several brands from shared infrastructure were the primary design target. The platform handled brand-level menu isolation and kitchen-level order routing without custom configuration per site.
  • 04

    Backed and later acquired

    Gula was funded by East Ventures and later acquired by Runchise. RaftLabs was a product partner on the build. The acquisition validated the platform's fit with where Indonesian food tech was heading.

Gula was acquired by Runchise. RaftLabs was one of the product partners on the build alongside the founding team. If you are building a multi-platform aggregation layer, a restaurant operations tool, or a food tech product for Southeast Asian markets, the architecture and lessons from this build are directly applicable. The case study covers the technical decisions and go-to-market execution in detail.

What clients say

Most clients stay.
Some say so on camera.

Three-year average engagement. Founders and operators describing the work in their own words. No marketing varnish.

Testimonial 1 of 16: Charles E.

Charles E.

Entrepreneur at Aggie Technologies

USA flagUSA

All of the sprints were completed on schedule and on budget. We highly recommend RaftLabs!

200+
engaging content modules
5000+
daily active users

01 / 16

Common questions

Gula was acquired by Runchise and is no longer operated by RaftLabs. If you are looking to build something similar - a multi-platform order aggregator for food delivery or another vertical - we have built this and can scope a comparable product for your market.
GrabFood, GoFood, and ShopeeFood - the three dominant food delivery platforms in Indonesia. The architecture was designed to add further platforms without structural changes.
Yes. The core pattern - consolidating orders from multiple third-party aggregators into one operator dashboard with cross-platform inventory and store management - applies to any market where restaurants list on more than one delivery platform. Tell us the platforms and the market; we'll scope the integration layer.
A kitchen running three brands - say, a burger brand, a chicken brand, and a drinks brand, each with separate listings on GrabFood and GoFood - had all six storefronts managed from one Gula dashboard. Each brand had its own menu configuration, but orders from all storefronts came into a shared queue routed to the right kitchen station.
Onboarding a new chain typically took one to two weeks: menu mapping, platform credential setup, printer configuration, and staff training. Multi-location rollouts scaled linearly from there.

Want to build something like Gula?

Tell us what's not working in your business. We'll find the real problem and tell you exactly what it would take to fix it.

  • Scope and cost agreed before work starts. No surprises. No obligation.
  • Working prototype within 3 weeks of kickoff.
  • Pay by milestone. You see progress before each invoice.
  • 60-day post-launch warranty. Bug fixes, UI tweaks, and deployment support. No retainer.
  • All conversations are NDA-protected.