← All case studies

How Union Moved Its Venues Off Checkmate and Put Every Delivery Marketplace Inside Its Own POS

3 → 1Places where venues manage delivery menus
1 monthFrom the first call with Union’s CEO to passed acceptance testing
~13%Of orders failed with Union’s previous integration option, by Union’s own count
WhoUnion is a POS built for high-volume bars, nightclubs and restaurants, used by thousands of venues across the US. Most new Union customers come through payment partners, and Union’s own team handles onboarding, training and menu building for every venue it signs.
WhatUnion’s venues wanted DoorDash, Uber Eats and Grubhub orders in the same POS and KDS they use for every other tab. Union already offered delivery through Checkmate, but that integration only received orders. Menus weren’t truly synced: a venue added an item in Union, and the integrator then synced each item by hand. Items couldn’t be 86’d from the POS, and venues ended up managing delivery in three different places.
WhyUnion wanted delivery to feel like part of Union. With the previous setup, Union sent an email introduction and the integrator onboarded the venue under its own name. Union wanted to own that experience: its look and feel, its onboarding, and self-setup without calls to support. Going direct with each marketplace wasn’t an option either, because new integrations wait in long approval queues. Union chose its next partner on three things: support, reliability and price.
“Because they have to go to like three different places to manage things, it’s become very difficult for them.”
Becky Groffman, Head of Product, Union

Solution

Union replaced its previous integrator with KitchenHub and built marketplace delivery directly into its own product. Venues turn on delivery inside Union, build their menu once in Union and publish it to every marketplace. Orders appear in the Union POS and KDS like any other tab. KitchenHub runs the marketplace connections in the background and maintains them when DoorDash, Uber Eats or Grubhub change their APIs.

01Onboarding owned by UnionWhen Union enables delivery for a venue in its internal admin tool, KitchenHub creates the store and location automatically through the API. Union then sends the venue a link to sign in to DoorDash, Uber Eats and Grubhub on their official pages, so Union never handles a venue’s marketplace passwords. Once credentials are ready and the venue is disconnected from its previous provider, a connection takes about 30 minutes.
02One menu, published from UnionA venue edits its menu in Union and publishes it once: to the POS, the KDS and, through KitchenHub, to every connected marketplace. Business hours set in Union go to the marketplaces through the same API. Venues set delivery markups to offset marketplace fees, and can pause delivery or extend prep time from Union when the kitchen is slammed.
03A support team in Union’s SlackUnion’s support team reports issues straight into a shared Slack channel with KitchenHub. When Union’s venues hit marketplace-specific limits, KitchenHub builds the workaround on its side: for example, menus where the same item appears on several screens with different availability windows, which Uber Eats rejects.

Implementation

  1. DiscoveryUnion’s head of product walked KitchenHub through what wasn’t working with the previous integrator and what Union needed: white label, API-based provisioning, menu control, multi-location support, an SLA and weekend support.
  2. BuildUnion’s engineers built against the KitchenHub API: store and location creation when delivery is turned on, menu publishing, business hours, and order webhooks into the POS and KDS.
  3. Acceptance testingIn one session, KitchenHub and Union’s developer onboarded a test venue end to end: menu push, ASAP and scheduled orders from several marketplaces, order and item notes, business hours sent to the three major marketplaces, and cancellations. Union passed the same day and received production keys.
  4. RolloutThe first live venue started on Uber Eats a few days later. Union then began moving its existing delivery portfolio off the previous integrator while onboarding new venues directly on KitchenHub. For Grubhub, KitchenHub transfers a venue from the old integrator as soon as Union confirms the switch in the shared channel.

Challenges Resolved

Three places to manage deliveryVenues now build the menu once in Union and it goes live on every marketplace.
Items that couldn’t be 86’dAvailability changes in Union reach every marketplace.
Onboarding under someone else’s brandVenues connect marketplaces from a Union link, with Union’s support team guiding them.
Manual re-entry and missed ticketsMarketplace orders land in the POS and KDS like any other tab, with no separate tablets.
Marketplace edge casesKitchenHub handles marketplace-specific limits, such as Uber Eats rejecting overlapping availability windows, without changes on Union’s side.
Switching off the old integratorKitchenHub’s team works with each marketplace to move venues over, so switching doesn’t depend on the venue calling DoorDash or Uber Eats support.
CUSTOMER FEEDBACK
“Our goal here is to get our customers over to you all as quickly as possible.”
Becky Groffman, Head of Product, Union

Gain Confidence in Your Order Aggregation with KitchenHub

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