← All case studies

How OrderCounter Stopped Maintaining Its Own Marketplace Integrations and Turned Delivery into Recurring Revenue

1 weekTo ship the POS-managed menu a merchant asked for
15%Higher marketplace prices one restaurant sets automatically, from a single POS menu
0Marketplace integrations OrderCounter’s team has to maintain for advanced delivery
WhoOrderCounter is a restaurant POS with about 1,500 locations across the US. It sells through deployment partners and payment agents as well as its own sales team, and a dedicated team upsells new products to restaurants already on OrderCounter.
WhatOrderCounter had built its own direct marketplace integrations, but they only went so far. They received an order, printed it in the kitchen and classified the payment. Nothing went back to the marketplaces: no menu sync, no price changes. Restaurants that wanted higher prices on DoorDash and Uber Eats to cover 25–30% commissions had to keep separate menus, and every item was mapped by hand. Building deeper connections directly took a long time: one of OrderCounter’s direct marketplace integrations took almost a year to get across the finish line.
WhyOrderCounter wanted deeper delivery for its merchants without growing an integrations team. As its leadership put it, they weren’t interested in maintaining all these integrations. They also needed a partner that fit how they sell: a product their deployment partners and upsell team could resell, recurring revenue on every location, and commercial terms they could plan around.
“We’re not interested in maintaining all these integrations.”
Thomas Barrineau, OrderCounter

Solution

OrderCounter kept its own basic integration and added KitchenHub as the advanced option. Merchants on the advanced tier get DoorDash, Uber Eats and Grubhub orders in the POS, with the menu and prices managed from OrderCounter. KitchenHub maintains the marketplace connections, and OrderCounter’s teams sell it across their base.

01One menu, with a price per marketplaceMerchants manage one menu in the POS. Price rules set a separate markup per marketplace, for example 20% on DoorDash and 30% on Uber Eats, so no one maintains a second menu. Merchants who prefer the menu they already built on DoorDash can keep it and map it to OrderCounter instead.
02A connection that looks like OrderCounterMerchants connect their marketplaces from a window embedded in OrderCounter, so the setup looks like part of the POS. Once the POS is connected, orders are accepted and sent to the kitchen automatically, and merchants no longer need the DoorDash tablet.
03Delivery as recurring revenueKitchenHub became a SaaS product OrderCounter resells. Its upsell team sells it to existing restaurants, and its sales team can answer the aggregator question on every demo with a yes.
04Features built on requestWhen an OrderCounter merchant needed the menu managed entirely from the POS, KitchenHub shipped it within a week. KitchenHub also raised its limits to handle one of the largest menus on OrderCounter.

Implementation

  1. Launch planningOrderCounter’s leadership and developers mapped how KitchenHub fits next to their own integration: two tiers, markup per marketplace instead of separate menus, and an embedded connection flow.
  2. Commercial termsThe partnership was set up to protect what matters to a reseller: residual income on every location, flexibility to move merchants between tiers, and notice on any change to service terms.
  3. Onboarding the teamKitchenHub walked OrderCounter’s upsell lead through onboarding step by step, then gave the sales team a one-page capability summary and an interactive guide.
  4. Rollout through partnersOrderCounter and its deployment partners onboard merchants location by location, with KitchenHub’s team joining the first connections and handling marketplace-side issues directly with DoorDash, Uber Eats and Grubhub.

Challenges Resolved

Shallow integrationsOrders used to be received and printed, nothing more. Now menus, prices and availability sync from the POS.
Two menus for two price levelsOne POS menu with a markup per marketplace replaced separate marketplace menus.
Item-by-item mappingMerchants can publish the POS menu directly, so most items no longer need mapping.
Integration maintenanceMarketplace API changes and approvals are handled by KitchenHub, not OrderCounter’s developers.
No recurring revenue from deliveryKitchenHub is a product OrderCounter’s teams resell on every location.
Large menusKitchenHub adjusted its limits so even OrderCounter’s biggest menus publish to the marketplaces.
CUSTOMER FEEDBACK
“For the price you’re offering it is a no-brainer.”
Thomas Barrineau, OrderCounter

Gain Confidence in Your Order Aggregation with KitchenHub

Instant access to an interactive demo with no sales calls, account setup, or integration required.