2024 1.1 version Restaurant Interface + Dispatching Improvements #25
Paul-Eraman-CoopCycle
started this conversation in
Large topics to discuss as a group
Replies: 2 comments
-
|
👋 I have no idea about the solution as a whole, but I think it is bad that you have an automated behavior ("non-pro") and then it becomes non automatic for "pro". I think you could have more notifications/sound for "non pro" so you educate them to move tasks to "in preparation". |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
If we are assuming that autoaccepting restaurants sometimes get overwhelmed and ignore delivery times (which is true...) how do we notify the customer? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
The Goal: To make CoopCycle a minimum viable service for restaurants that have a high volume of deliveries (15 + in a single shift)
Having talked with many restaurants and cooperatives, the following problems are common:
Solutions we have found based on discussions with other restaurants, looking at competitors, and talking to cooperatives:
Restaurant App Version 1.1

Orders Dashboard for Dispatch

Admin Panel

Beta Was this translation helpful? Give feedback.
All reactions