Bitrix, shop-script, Drupal or some other engine?

Question

CMS

I found several programmers who are ready to implement the project. Each of them offers its own version of the engine (drupal/bitrix/shop-script, etc.). I would like to ask experienced people in the direction of which engine should I look? According to the cms rating, Bitrix wins, but many write that it only has good marketing, but in fact it is no better, only you will overpay and more expensive development. And what is the general difference between all these engines?
The essence of the project (in short):
1. We went to the site, asks to enter an index / address
2. After entering the address or index, available stores are displayed (magnet / pyaterochka / Auchan, etc.), depending on the address, stores may differ and prices too (so as not to go from one end of the city to another)
3. I choose a specific store and proceed to shopping
3.1 I can see various offers from different stores (if I entered the name of the product in the search bar and did not specify a specific store)
4. A basket with friends is available (a basket is created, a link is given to friends -> they join and you jointly make purchases in one basket, under each product the name of the person who added / on the "members" tab you can see who is online or offline in the basket), the order is placed for one person.
5. There are recipes and there is a blog.
Prices in stores should be updated through the admin panel according to the price list in excel format. There should be a function to edit prices for everything at once, for different groups or separately for each product.
Initially, orders must be sent to the courier's e-mail.
In the future, it is worth considering that the engine can be expanded to such functions as:
1. Optimization with an application for couriers so that orders arrive there, and not by mail. In the application, a person scans the barcode of the product and sees if it is one or not;
2. Chat with a courier through the site or a call;
3. Tipping and evaluating the work of couriers in the application;
4. Scalability for a large number of stores in different cities and high attendance.
Here is an example of a site (you must enter 10069 - this is an index): https://www.google.com/express/
Who and what can advise? What is the best engine to choose with a future perspective? Or is it better to choose any engine now, and in the future you will have to completely redo everything and write from scratch (without ready-made engines)?
Thanks in advance!

Answer 1

Do it in php framework. Any listed engine does not provide the required functionality.

Answer 2

If you are not a programmer yourself, then there is no difference what is the difference between the engines, because you still won't be tinkering with the code. The choice of engine is important for who will be the lead developer of the project.
And we must proceed from the fact that any project may turn out to be completely different from the way you envision it. And it may not be perceived by users at all as you expect. Therefore, the creation of the first version is, in fact, testing the idea to what extent it turns out as expected in practice. And we must be prepared that we will have to redo everything more than once. Therefore, it is desirable to create the first version at minimal cost and as quickly as possible.
Hence the advice - listen to the opinion of the developer with whom: a) maximum mutual understanding; b) you can create the first alpha version as quickly as possible; c) the cost of creation will be kept to a minimum.
The first implementation will show how tenacious the idea itself is and whether it is worth digging further.

Answer 3

Judging by the description of the project, it is more important to choose a good programmer and rely on him than to impose a platform advised by people who should not code. If a good programmer chooses a bad platform, then he is a bad programmer - back to the beginning =)
First of all, look at the portfolio for projects similar in functionality / scale. Further - the price tag and just mutual understanding. Avoid bicycles, but do not console yourself with the hope that since it is made on something known, the next programmer will not want to burn everything and write it all over again;)
PS The store part does not seem to fall on ready-made solutions at all, respectively, I would saw it on the framework, and the content part (recipes / blog) can be planted next to the CMS. But the devil is in the details, and your performer should look at the details - just keep in mind that hypothetically, you can split the project into parts and take a more suitable tool for each.

Answer 4

Ruby On Rails

Answer 5

django python