Databases
StackOverflow2013
Postsdbo
POPrestashop vs Magento: Real-world e-commerce case - A clothes store
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPrestashop vs Magento: Real-world e-commerce case - A clothes store
    primarykey
    data
    text
    <p><strong>This question is not about which open-source product is better</strong> in terms of community, administration, hardware requirements, more paid or free modules,etc... It involves a real case of study and a urgent actual decision:</p> <p><strong>Which e-shop product to choose to create a clothes store?</strong></p> <p>I will enumerate, in order of importance for this case, and explain the <strong>most important requirements</strong> (as of client requirements) and the actual point of analysis I am now:</p> <ul> <li>1) <strong>Product management</strong>: In any store is very important how the products are managed. In a clothes store in particular is even more important how configurable products (in terms of size and color) are managed. </li> </ul> <p>Prestashop has "Combinations" of one specific product (with their own price or photos) and an out-of-the-box color swatcher that changes product photo.</p> <p>Magento has "Configurable product" that is a father of others simple products. No out-of-the-box color swatcher is a drawback and the way it shows different children products price is too much IT oriented (eg: Yellow +20$, totally ugly for clothes) NONE of them allow SPECIAL DISCOUNT (only special price) on an specific combination or children product.</p> <pre><code> Initial winner: Prestashop by just a little (swatcher and ease to use against complex magento's products) </code></pre> <ul> <li>2) <strong>Client grouping</strong>: Ability to goup clients and apply special prices or abilities to them.</li> </ul> <p>Prestashop has good and easy built-in functions like category discount by group or even category display by group</p> <p>Magento can make discount by group with "Promotion rules", but they are always low-level and not very intuitive, but very powerful. NO category/CMS restriction by group (only with paid modules)</p> <pre><code> Initial winner: Prestashop (ease of use and category restriction out-of-the-box) </code></pre> <ul> <li>3) <strong>Multilingual</strong>:</li> </ul> <p>Prestashop has an easy and well integrated way to translate categories, products, installed modules or themes, all in the admin interface just clicking some flag. Very intuitive.</p> <p>Magento treats multilingual as entire different shops. To add product description or category name in other languages you have to SWITCH SHOP. It allows much more different configuration between different shops, but if you only want MULTILINGUAL, it makes it really harder to maintain. Not that intuitive...</p> <pre><code> Initial Winner: Prestashop (for ease of use and intuitive) </code></pre> <ul> <li>4) <strong>CMS Integration</strong>: (e.g. with Joomla)</li> </ul> <p>Both shops have some basic CMS module to create static pages or content that you can link to your cms. For real integration more modules (normally paid ones) are made between Magento and Joomla because Magento is in the market for a longer time.</p> <pre><code> Initial Winner: Magento (better CMS and experience in integration, like paid modules) </code></pre> <ul> <li>5) <strong>ERP Integration</strong>:</li> </ul> <p>Both shops has some kind of web service/API to allow a complex integration with other ERP's/Databases/Application but Magento's ones are better developed and tested (again more experience through the years...). There is a even Java API to Magento WS (Magja)</p> <pre><code> Initial Winner: Magento (More experience in integration, better web services/API) </code></pre> <p>These are all initial valorations, maybe I'm wrong in some of the cases. I'd love to hear opinions from Magento or Prestashop experts about these topics. Don't forget we are talking about a specific case: <strong>"Clothes shop"</strong></p> <p><strong>No need to answer every point</strong>, just any of them or give another good reason to choose one or another (or even another product). I'll upvote almost anything, and choose the best answer among them.</p> <p><strong>EDIT:</strong> Taking a look at the <strong>Prestashop 1.5 Beta 2</strong> (current stable is 1.4.6) it gives more reasons to choose Prestashop over Magento. It includes some of the good Magento features that weren't available in Prestashop (Like custom cart discount rules)</p> <p><strong>EDIT(2):</strong> Strange that there is no answers nor opinions about any of the points. The decision has to be made soon and <strong>Prestashop is most likely the chosen one</strong>. It will force more work on the CMS/ERP Integration but the other points are a bit more important for the decision.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USPeeHaa
    1. USAleja_Vigo
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POPrestashop vs Magento: Real-world e-commerce case - A clothes store
      1. USAleja_Vigo
      1. VTFavorite
    2. VO
      singulars
      1. POPrestashop vs Magento: Real-world e-commerce case - A clothes store
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POPrestashop vs Magento: Real-world e-commerce case - A clothes store
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI think this SO is not the right forum for such a type of question.
      singulars
      1. POPrestashop vs Magento: Real-world e-commerce case - A clothes store
      1. UShakre
    2. COIn my opinion, if you have an experience with Prestashop, do with it. Do not jump new adventure.
      singulars
      1. POPrestashop vs Magento: Real-world e-commerce case - A clothes store
      1. USOğuz Çelikdemir
    3. CO@hakre could be...
      singulars
      1. POPrestashop vs Magento: Real-world e-commerce case - A clothes store
      1. USAleja_Vigo
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload