Native Delivery: System Requirements

System Requirements

Online Ordering

Transaction fees, ability to negotiate Consistency with menu mapping Stand up website and apps

POS

Tablet consolidation Some level integration for all software components

For example, delivery management could go to directly to POS or to POS via Online

Ordering Platform Single source of truth

Delivery Management

Ability to throttle orders, ultimately understanding what your capacity is. Designate a pickup area Consider a second make line Lighted car signs Real-time status updates for customers - apps, SMS Staff management Tip management

Loyalty

Big: Earn burn, and collect/utilize rewards Small: Direct communications, customer identity (SMS blasts, email lists)

Guest Communications & Feedback

Feedback on Order

Direct to brand: Not via Yelp or Google, will foster better communication with customers.

Timeliness: Real-time, or next day depending on sentiment and how the organization wants to respond. Collateral on Direct Ordering

Consider cost per acquisition, transition customers from marketplace to websites and direct restaurants apps. Offer discounts for direct orders.

Security (coverage across all platforms)

Network Security (Overarching) Privacy Compliance for your Vendors (CCPA, GDPR, LPGA, ADA) Wi-Fi, WAPs: Enough power, cellular failover for uptime. Ability to operate offline. This is critical with off-premise technology. SIEM and Network for work from home/corporate monitoring: Threat detection and response PCI: Make sure vendors have certs, increase oversight with more orders going online into cloud-based solutions.