One catering system for every store, from checkout to the door.

Catering ran on rented tools that didn't talk to each other, and none of them belonged to the brand.

• Rented ordering, paid every monthOrders from the brand's own catering site ran on a rented platform, paid as a monthly subscription.
• Direct and ezCater, one blind spotOrders came from their own site and from ezCater. One ezCater listing never reached any store's register, so those sales were missing from the reports.
• No delivery tool of their ownTo let customers see the driver on the way, the chain was pricing yet another delivery app.
• Guest orders that went missingA corporate customer who ordered as a guest couldn't find those orders after creating an account.
• Stores in different statesEvery order has to carry that store's own local sales tax.

One team built every piece, around the registers and the marketplace the stores already use.

• Their own catering site

  Order from phone or desktop, delivery or pickup, pay by card. The account keeps every order, guest ones included.

• Straight into the register

  Card payments run through each store's own POS, here Clover. Orders reach the right kitchen with tax and totals matching the POS.

• One menu to maintain

  The site reads the menu from the stores' POS, so nobody keeps a second copy by hand.

• One dashboard for every store

  Direct and ezCater orders side by side. Approve, assign a driver, follow every delivery on a live map, get every alert in one place.

• A branded driver app

  Live on the App Store. Every item checked before leaving, photo and signature at every drop-off.

• Live tracking

  The customer follows the real driver on a live map. On ezCater orders, the driver's progress goes back to ezCater too.

• The right tax, per store

  Each store charges its own local rate, matched to its POS.

• Monitoring and email updates

  Payments, POS, ezCater and messages watched around the clock. Customers get order and delivery updates by email.

Dashboard screens shown with sample data.

Under the hood, for technical buyers. Clover orders and native payments with duplicate-order protection, ezCater API in both directions (orders in, delivery status out), menu read from the POS catalog, payments, tax and data kept separate per store, iOS driver app with push notifications, proof of delivery and live location, automated tests on phone, tablet and desktop screens, daily off-site backups.

Corporate customers sign in to see upcoming catering, reorder a past order in one click, follow the delivery and keep their receipts and saved addresses, including orders they placed as a guest.

9:41

Real account pages, shown with a sample customer and sample orders.

We also built winfieldcoffee.com, the brand's main website: locations, menus, catering, rewards, the shop and the app. One look from the home page to the checkout.

winfieldcoffee.com

Scrolling preview

9:41

winfieldcoffee.com, desktop and phone.Open the live site ↗

• Every store

  taking catering orders on their own site, with card payment

• On the App Store

  a driver app under the brand's own name

• One team

  from ordering to delivery, built and run together

• Theirs

  flat monthly fee, no per-order fees, and the system becomes theirs

In plain wordsYour catering orders, from your own site or from ezCater, land in your own register, go to the right store and go out with your own drivers on your own app, while the customer watches them arrive. No per-order fees, and the system becomes yours.