Integrations

Systems we plan to work with

Nothing is connected in this prototype. Every status below is honest: planned, not built.

Works with what you already use, or with paper

Many kitchens run on paper and memory. A photo of the printed order is enough to start, and every connection below is optional. Scan an order

Reading the event order

The event order is where every pull sheet starts. Read it from the system that prints it, so nobody retypes or photographs the BEO.

  • CatereasePlanned

    The event order: menu, guest count, room and times. The pull sheet fills itself, and a change to the order shows up before the crew pulls.

    Direction
    Read only
    To switch on
    An account admin allows an export or API access for Cateroute. What Caterease offers is still to check on its own docs.
  • TripleseatPlanned

    Event orders and room bookings, so the crew sees the right room and the right time on their phone.

    Direction
    Read only
    To switch on
    An account admin allows API access for Cateroute. What Tripleseat offers is still to check on its own docs.
  • CBORDPlanned

    Campus dining and catering orders, for kitchens that run catering through campus dining.

    Direction
    Read only
    To switch on
    Campus dining IT approves access to the catering orders. What CBORD exposes is still to check on its own docs.

Crew, schedule and clock in

Know who works each event without a second list, so leave by times and the crew sheet are right on their own.

  • WorkdayPlanned

    The worker roster: name, worker ID and department, so the crew sheet uses the same names as payroll. Clock in times could go back later, after a pilot.

    Direction
    Read only first, writing hours back later
    To switch on
    A Workday tenant admin registers Cateroute as an API client, with an integration system user that can read worker data. Usually the caterer's IT or HR systems team owns this, and it holds personal data, so it needs a privacy answer first. From our research notes, to verify on Workday's own docs.
  • HumanityPlanned

    The shift schedule: who works which event, start and end. It fills the crew sheet and the Leave by column.

    Direction
    Read only
    To switch on
    A Humanity admin turns on API access for Cateroute. Still to check on Humanity's own docs. It may be the easiest first connection.

Product names belong to their owners. No logos are shown until we have checked each company's press kit.