This question is not about which open source product is better in terms of community, administration, hardware requirements, more paid or free modules, etc. It includes a real case study and an urgent factual solution:
Which electronic store product to choose to create a clothing store?
I will list in order of importance for this case and explain the most important requirements (taking into account the requirements of the client) and the actual point of analysis, which I now:
- 1) Product Management . In any store it is very important how the products are managed. In a clothing store, it is especially important how custom products are managed (in terms of size and color).
Prestashop has “Combinations” of one specific product (with their own price or photos) and a finished color that changes the photo of the product.
Magento has a “custom product” that is the father of other simple products. There is no flaw in the color swatcher flaw, and the way it shows the price of different children, there are too many IT-oriented ones (for example: yellow + $ 20, absolutely ugly for clothes) None of them allow SPECIAL DISCOUNTS (only special prices) at specific combination or baby product.
Initial winner: Prestashop by just a little (swatcher and ease to use against complex magento products)
Prestashop ,
Magento " ", , . NO/CMS ( )
Initial winner: Prestashop (ease of use and category restriction out-of-the-box)
Prestashop , , , , - . .
Magento . , . , MULTILINGUAL, . ...
Initial Winner: Prestashop (for ease of use and intuitive)
CMS , cms. Magento Joomla ( ), Magento .
Initial Winner: Magento (better CMS and experience in integration, like paid modules)
- -/API, ERP//, Magento ( ...). Java API Magento WS (Magja)
Initial Winner: Magento (More experience in integration, better web services/API)
, , . Magento Prestashop . , : " "
, ( ). , .
: Prestashop 1.5 Beta 2 ( - 1.4.6), Prestashop Magento. Magento, Prestashop (, )
(2): , , . , , . CMS/ERP, .