top of page
< Back

ReusePass Program Design

TIMELINE: START HERE


Action items: After reading this page, here are the action items that need to be completed:

  • Determine program design and settings


DETERMINE THE SERVICE DESIGN

  • We need the following information about your dining operations:

    • Locations information and order flow

      • Dining locations offering reusables

      • Number of cashiers/location

      • Power (outlets) and wifi availability

      • The daily to-go volume/location

      • How do people order at these locations: in-person, mobile ordering, kiosk, lockers, robots, etc.

      • How do people pick up at these locations: unsupervised pickup shelf, supervised pickup shelf, lockers, robots, etc.

    • Scanning Operations & Washing

      • Dishrooms where reusable containers will be washed

      • Scan-in operations: RFID or Manual Scan-In

        • RFID is Topanga.io’s passive scan-in technology

    • Integrations

      • Order integrations

        • Grubhub mobile ordering

        • Starship mobile ordering & kiosk ordering

      • Charging integrations

        • Grubhub automatic charging


DETERMINE PROGRAM SETTINGS

  • We need the following information about your reusables program:

    • Mandatory vs. Optional:

      • Optional ReusePass (dishes, single-use, reusables)

        • If you are still offering single-use, will there be a single use upcharge and what amount will the surcharge be? We recommend $2.50

      • Optional ReusePass (single-use, reusables)

        • If you are still offering single-use, will there be a single use upcharge and what amount will the surcharge be? We recommend $2.50

      • Optional ReusePass (dishes, reusables)

      • Mandatory ReusePass (every order in a reusable container)

    • Sign up flow, the information you will capture from users during sign up. Topanga.io requires phone number for all sign ups. Below are the added fields you can add to the sign up flow besides phone number:

      • Single Sign On (SSO) — how we authenticate users are who they say they are. This is recommended if you plan on charging late fees. This will require collaboration with your IT team.

        • If you are utilizing SSO during sign up flow then you can disregard the other sign up flow options.

      • If you are not utilizing SSO during sign up, here are the fields you can capture (you can choose more than one):

        • Email — email is always collected optionally during the sign up flow but we can make it mandatory

          • We will need the email format in order to authenticate

        • Student ID — This is recommended if you plan on charging late fees

          • We will need the length of this id number in order to authenticate

    • Late fee charging — will you charge a fee for late containers, and what will the charge amount be.

      • If you are not utilizing integrated charging (i.e. Grubhub automatic charging) you will need someone to process these fees. Topanga.io does not process fees.

bottom of page