Description: Live tracking of Carrier when "Order Status" in "?"

During "Order Info"
Fired after Carrier "En Route" ?

[...]

Same as: Live Tracking

Description: For tracking/overview of entire fleet on map via Admin Panel.
Optional: Additionally, tracking "Active" orders of all couriers delivering for that a merchant.

combo with options: All, Confirm, Start Proccesing, Start Allocation, Allocated, Start Packaging, Packaged, Given to Carrier.

Allow seeing which carrier took a certain order from Merchant App.
This lets you know which carrier is delivering a certain order.
For example, if you have to contact him.

fields suggested: i.e. current date, number, customer name, delivery address, telephone number

Mark a product as temporarily unavailable either if it is an infinite stock product (very necessary in that case if the restaurant ran out of one ingredient) or a finite stock product because of whatever reason.

Basically, this task is about Adding something like "Active / Not Active" boolean flag (switch in UI) and make sure everywhere in UI and on the server we use that flag when decide to show / not show the specific product (e.g. server returns to mobile app only products with flag set to true).

Of course in both Admin UI and in Merchant App it should be possible to set Active / Not Active for any selected product

Cut down on fraud orders.

The time estimate to be configurable by the Merchant/Admin

I’d be an improvement to put a default price from the catalog and if the merchant wants to change it upon creation then he can.

It may need the definition of a MSRP upon creating the product in the catalog.

I need Openstreetmap.org Integration in Ever Platform.

Dashboard shows well only on big screens. Please, make it more responsive.

Allow the customer's order to have comments written before submission. Comments could be seen by the merchant (i.e.: remove onions from my menu) and the carrier (i.e.: watch out the dog when ringing the doorbell)

We can put small (tiny!) button above "Undo" / "Pay with Card" with the text "Leave Notes" (color like grey or something that not stand out too much)

Same changes we should do on full page view:

Click on such Button "Leave Notes" will show a tiny popup with 2 choices:
[Note to Merchant]
[Note to Carrier]

Click "Note to Merchant" above, will show another popup with "Note to Merchant" title and 3 lines input for "Note" and buttons "Submit" and "Cancel". The same should be done for "Note to Carrier". Of course, click again on "Note to Merchant" or "Note to Carrier" should show a popup with a previously entered note and allow it to edit it and submit again.

Notes should be added to order record in Merchant Tablet app, to Carrier app page where delivery information displayed and of course in Admin UI for selected Order.

Upon creating a new product for a Store, when adding it only allows quantities above 0, but not zero. For menus that are prepared on the fly one restaurant may want to have unlimited stock available so it is not possible to break stock for one product on the system.

Ability to add voucher <via Admin, Merchant>

• with a Type <Fixed/Percentage?>,
• with a Discount of ,
• Expiry/Creation date,
• with a "Status", such as "Active/Inactive"

Use Twilio number to middle man calls.
This would also imply VoIP capabilities?

Call Masking would be used to mask any number input in the system to middle man calls routed via Twilio to outbound numbers.

See ever-co/ever-demand#806 for more details

A solution could be to move email or phone to the store info section.

Should be standard payment gateway for transactions based on its popularity and coverage.

Allow adding location details to the customer making a purchase from the shop.
For example: Blue door, hall at the bottom, knock on the door, dangerous dog, etc.
This makes it easier for the deliveryman to deliver merchandise.

Basically we need to add multi-line input (e.g. 3 lines max) where customer can add "Location Notes" when he registers address (in mobile shop app, in the web shop, show it in Admin, in Merchant app for order, in Carrier app for delivery, etc)

Note: it is different from #36 because here we talk about the registration page (customer address), not about the order page! I.e. it's the ability to add some notes for customer address which is important in this ticket, but #36 talks about the ability to add some notes only to specific order!

Hello, so far so good. I was wondering when will you be adding the core files that actually make up the app itself, including web panels and more.

Feature: Nolt integration #2 by Ruslan Konviser

In the Admin module, the feature is to turn on or off states that the order transits. The current pipeline is ok for a large kitchen where tasks are all split up, but for a small restaurant with a simpler pipeline some states do not add up, making it cumbersome.

This feature is about the ability of the merchant/admin to create a basic product and within the product allow the creation of properties to it with configurable limitations to it. And also for the customer (Shop Mobile (Web) ) to allow to select the product and purchase selecting those properties.

An example of this would be to select pizza as the product and a 2nd menu opening enabling to select the taste, say pepperoni, Italian, 4 cheese, etc.

Another example to illustrate the need could be to select a "kebab" and within the product have... say 2 options that can be selected: (1) no onions, (2) no cheese, or maybe both.

Another example is if asked an ice cream as a dessert, selecting ice cream and then enabling to select 2 flavors at most within maybe 10 flavors.

2 hierarchy product creation can now be avoided by creating in the main menu all product combinations, which can be really a lot (between 40 and 100) in some cases so this possibility has reached a natural limitation.

I hope I have managed to illustrate the need without any screenshots.

Push Notifications via Mobile and Web

Description: User will receive live status updates for each order in real time from <x>

x: Courier, Merchant, via Admin, etc.

[...]

This feature is about addresses that can not be mapped to the correct location in the map by Google Geolocation API.

Mobile Shop:

After entering the Address

(watch here that the door number is fiction, this place does not have such field in the real address)

Google does not find it and takes us somewhere else:

Before starting the order, a Maps screen could be added to verify or correct the location found by Google.

Web Shop:

Analogous feature.

Not showed correctly the pin:

Admin:

This is upon creating the Restaurant location.

In this example shows properly the City but the location in the street is still flawed.

You can change this starting to play with coordinates:

But it is too cumbersome to play with coordinates. It would be better to be able to move the "pin" manually.

Cash could also be a SELECTABLE payment option. Some restaurant in more dangerous neighbourhoods don’t want to handle cash neither their deilvery service.

If cash appears as a selectable payment option then the restaurant has to select at least one payment option between: Strype, PayPal, Cash.

Use a scroll or
Drive them elsewhere (Preferred option)

Upon creating a product Tackeaway is better if it si clicked (unless for restaurants only with delivery) because otherwise it could induce an error to the Restaurant Administrator to leave this bock clear by accident (loosing sales)

One on one chat implementation that would allow dialog in a unified "Support" system between Merchants and Couriers, Customers and Admin, any other relation? during an Status* order.

Status*: Active, Pending, Cancelled (with a time limitation) for example.

Review the modules and status from where the order can be cancelled:

1-The customer cancels the order from the Shop App
2-The carrier cancels the order from the Carrier App
3-The merchant App

Still to look at which status to allow in each place.

Ability to view critical logs such as SMS, email delivery failures and more via Admin Panel.

Show in the order if it is for delivery or takeaway

This could be implemented with a Shopping Cart

To avoid for a customer to order when the restaurant is not open (or in other cases, like there is no delivery available, or the restaurants just doesn't want to sell through the app), the shopping service should be opened and closed manually.

Carriers should be able to pick multiple orders for several customers at the same time.

Note: this is advanced feature and in most cases we don't want that because it will slow down deliveries (but of course will make them more cost efficient).

So such feature should be enabled only for orders from the same warehouse / merchant to customers who located very close to each other.

Make a list of orders delivered per day, with the total collected in cash

When taking the order, when you show the delivery address, you should be able to show the route to Origin-Destination (trade - customer's house)

How is this currently implemented?

Internationalization? Currencies? Languages?

For example MI/KM conversion per country, Miles to Kilometers.

When clicking in some places appears code. Please, make it optional to show it.

There could be currency issues to resolve.

If it is multi-country, the country should then be displayed in the Store list as another column.

There could be a summary somewhere ideally:

Or counting:

Currently, it is allowed to order for delivery from a restaurant within 50km (products are shown).

This feature is about improving this by using the delivery zones from restaurants (feature already existing) for delivery mode.

In the admin module, when deleting multiple merchants
Or in the admin module, when deleting multiple carriers

This feature is about making it optional from the Admin, to show the icon for the "in-store" mode in the Mobile Shop.

This is a usability feature when the owner of the app has only one Store and don't want to support in-store mode or if the marketplace owner doesn't want to support in-store mode for all stores.

This feature asks to be able to order the products the customer sees upon entering the shop app or the shop web, for each restaurant.

In its current state, how is countries, cities, regions/area defined?
How is the radius of a given area for delivery defined?

Allow to create user profiles that allow filtering information in the Merchant App, in order to facilitate the management of the order in each area. For example, assign Order States to Roles, and then assign Users to those Roles. This functionality should be configurable from the Admin.

In the Admin module, when adding a product to a warehouse options of Price, Quantity and Delivery, Takeaway or both are to be selected.

After addition, those properties remain hidden and cannot be viewed from the product listings of the restaurant

Neither they can be edited from the Admin module.

This feature is about showing the Price, Quantity and Delivery/Takeaway properties in the product listings of the restaurant and to be able to edit them, either from the product listing or from a new product configuration screen of the restaurant.

When confirming an order estimate a delivery time that reaches the client's app.

That ticket is more complex than it sounds because we need to support the following:

0. The global setting of delivery time (could be we already have it, not sure). It's read from .env file (on the server or in the mobile shop, not sure) and used to display delivery time for all products from all merchants.

1. Per merchant setting of delivery time (could be we already have it, not sure). That will be used as default value when we display delivery time estimate for products in the mobile shop app

2. Per product setting of delivery time (think we don't have this yet). So if it set, in the mobile shop app we show that value instead of value defined for whole merchant (i.e. this value overrides the default for the merchant)

3. In the merchant app or in Admin UI, when the merchant confirms an order it should be possible to set (change the default value) Delivery time, which will be used to display delivery time estimate to Customer in the mobile shop.

4. The carrier should be able to manually adjust the delivery time estimate (to be done later at separate ticket)