ESU EatsPartnership proposal01 / 16

A Mercial partnership proposal

Campus dining, delivered.

ESU Eats brings ordering, campus payments, restaurant operations, and last-mile delivery into one university-specific experience.

ESU EatsPartnership proposal02 / 16

The campus opportunity

A short distance can still be a real barrier.

Classes, weather, mobility needs, work, athletics, and peak dining lines make campus food access less convenient than it looks on a map.

Demand is concentrated into narrow class-change windows
Students leave campus systems when convenience is missing
Traditional delivery platforms are not designed around campus access or meal-plan value

11:50Class ends

12:05Peak line

12:30Next class

19 min walk→

ESU EatsPartnership proposal03 / 16

The proposal

One trusted layer for the entire order.

A standalone ESU-branded service that can connect identity, eligible payment methods, dining locations, fulfillment, and approved handoff points.

Built specifically for ESU
Designed around campus rules and operations
Structured to become a reusable Mercial campus platform

IDENTITYDININGDELIVERYPAYMENT

Mercialcampus layer

ESU EatsPartnership proposal04 / 16

Student experience

From sign-in to handoff, without the guesswork.

Students discover what is available, customize an order, select an approved destination, pay, and follow clear progress through delivery.

Campus-specific menus and availability
Transparent fees and payment choice
Live fulfillment milestones and pickup instructions

01Sign in

02Choose

03Pay

04Track

05Receive

ESU EatsPartnership proposal05 / 16

Trusted onboarding

University identity becomes the front door.

A proposed ESU SSO handoff would verify affiliation through the university login experience, then create the appropriate student, worker, or administrative profile.

No ESU password collected by Mercial
Role-aware access for students and delivery workers
Exact SSO protocol and claims confirmed during IT discovery

Continue with ESU

Affiliation verifiedStudent · active✓

ESU EatsPartnership proposal06 / 16

Campus payments

Let students pay the way campus life already works.

ESU Eats is designed to support conventional digital payment and, with approval, eligible Dining Dollars or eDollars through the campus-card ecosystem.

Clear balance and eligibility before checkout
One receipt across food, delivery, and service charges
Payment routing and settlement defined with ESU and its vendors

Sources: ESU eCard: Deposit Funds

ESU eCardDining Dollars•••• 2481

Digital paymentVisa •••• 2048Ready

ESU EatsPartnership proposal07 / 16

ESU-specific marketplace

The campus menu, in one place.

The prototype already represents nine ESU dining concepts, with a controlled onboarding path for additional campus-approved nearby restaurants.

9ESU dining concepts represented in the prototype

Menus, hours, availability, and service zones
Dining-operated locations first
Additional restaurants only through campus-approved commercial and operational rules

Sources: ESU Dining

B+FCenter CourtChick-fil-ADansburyGreens 2 GoStarbucksTopio'sWarrior MarketWarrior Wraps

ESU EatsPartnership proposal08 / 16

Restaurant workflow

Orders arrive ready to make—and ready to move.

A restaurant-facing queue turns a student order into a timed, verified handoff without forcing staff to manage delivery logistics manually.

Accept and confirm prep time
Prepare, seal, label, and stage
Scan or code-match the assigned courier at pickup

01Accept

02Prepare

03Seal

04Stage

05Verify

ESU EatsPartnership proposal09 / 16

Student-worker delivery

A campus workforce with a purpose-built shift experience.

Eligible student workers can receive assignments, verify pickup, navigate to approved handoff points, and document completion from a dedicated delivery view.

Availability and shift controls
Safe routes and clear escalation
Earnings, performance, and incident records

RC✓

Next deliveryCenter Court → KempPickup verified

ESU EatsPartnership proposal10 / 16

A future delivery option

One dispatch layer. Human or autonomous fulfillment.

After a successful operational pilot, ESU could evaluate Starship Technologies or another approved robotics partner for suitable routes and delivery windows.

60+university campuses reported by Starship

Potential capacity during peak demand
Weather, accessibility, and route suitability review
Separate procurement, safety, mapping, and partner approval required

Sources: Starship: University Campuses

••

Potential phase 2

ESU EatsPartnership proposal11 / 16

Connected operations

A clean handoff between every system and every person.

Mercial coordinates the experience while approved systems remain authoritative for identity, funds, menu data, order acceptance, and settlement.

Identity and eligibility
Menu, POS, and payment connectors
Dispatch, tracking, notifications, and reporting

Mercial

ESU identityCampus cardDining / POSDispatchReporting

ESU EatsPartnership proposal12 / 16

Governance by design

Launch only when the operating rules are clear.

The partnership defines data ownership, access, accessibility, support, incident response, refunds, and reporting before live transactions begin.

Least-privilege data access and auditable roles
Accessible student and worker journeys
Shared service levels, escalation paths, and operational ownership

✓Ready to launch

PrivacyAccessSupportSafety

ESU EatsPartnership proposal13 / 16

Phased launch

Prove the operation before expanding the promise.

Move from stakeholder discovery to integration, controlled testing, and a limited pilot—with readiness gates at every transition.

01 · Requirements, policy, security, and commercial discovery
02 · Connector and operating-workflow validation
03 · Closed test with selected locations and handoff zones
04 · Measured pilot, review, and expansion decision

1Discover

2Integrate

3Test

4Pilot

ESU EatsPartnership proposal14 / 16

Shared success measures

A pilot should earn the right to scale.

ESU and Mercial agree on the baseline, targets, review cadence, and stop/go thresholds before opening the service.

Adoption and repeat ordering
Acceptance, accuracy, and on-time completion
Student and restaurant satisfaction
Safety, support, refund, and incident rates

Adoption↗

On time94%

Accuracy98%

Incidents↓

ESU EatsPartnership proposal15 / 16

Commercial structure

A partnership built to fund implementation and reward adoption.

The proposed model combines a paid integration and launch engagement, a recurring platform license, and usage-based service revenue.

Implementation fee · discovery, configuration, connectors, and launch
Platform license · software, support, administration, and reporting
Order economics · agreed service and delivery charges tied to usage

01ImplementDiscovery + connectors

02LicensePlatform + support

03UseOrder economics

ESU EatsPartnership proposal16 / 16

The partnership ask

Let’s define the paid ESU Eats pilot together.

Confirm mutual interest, name the working team, complete technical and commercial discovery, and convert the result into a paid pilot SOW and platform agreement.

Designate ESU and Mercial stakeholders
Authorize scoped discovery with dining, IT, campus card, procurement, and legal
Agree pilot requirements, commercial terms, and launch gates

Open partnership brief

+

Shared discoveryPaid pilot agreement