Data structure built around a user’s unique profile, typically built as a core dataset of user preferences that is continually refined by testing and measuring various food options.
For certain users, this can also include health data to measure outcome improvements.
The entity to which a user belongs. (Optional)
Useful for aggregating users into delivery batches for distribution optimization and billing details.
The food suppliers (restaurants, caterers, ghost kitchens, individual chefs, and third party marketplaces) whose offerings are uploaded and automatically structured into Parkday format to optimize around user preferences.
Batching of vendor offerings into multiple options that can be offered in the same setting at the same time.
Features for stylized presentation (visual and text copy) to best capture menu quality and convert orders.
Dishes and ingredients and various tagging structures (cuisine, dietary matches, food type metadata).
Meals are automatically structured and trained against all users when uploaded to Parkday to create recommendation rankings.
To learn more about lower-level Parkday entities and relationships and how to leverage them to improve your client experience, Get in touch