Community mailing list archives

community@mail.odoo.com

Re: Odoo ecommerce vs magento

by
Mr James Alfa
- 05/06/2016 12:35:19
Fabien,

thanks very much for the reply.

With respect and in relation to 1) it is conventional on ecommerce sites to have all the pictures in the same area and to all be handled on an equal basis with regard to zoom, gallery and SEO. If you permit Odoo to claim to have multiple product pictures just because it allows you to enter a block of hand built content after the main product content (built by template) then you must also permit every other ecommerce platform to claim the same, and pretty much anything else that can be coded in html, if there exists a "place arbitrary html on product page" extension for that platform (they all have that).

1) On page 8 you assert that odoo enterprise offers multiple pictures per product - can you let us know how this is possible ?

The recommended way (and the reason why we ticked the box in the grid) is just to drag & drop building blocks on the product page.

These two pages have multiple pictures

Magento's approach looks more like (1): you have to hover to get pictures. Whereas Odoo's approach looks more like (2): you have to scroll. Both are good, it's just a different approach to the same problem: Multiple Pictures per product.

Alternatively, if you want to do it the Magento way, there are different ways:
- use the Gallery buidling block (eventually remove the photo to start the HTML content directly)
- variants have a different images in v9
- use a community module (there are several for that purpose on https://odoo.com/apps)

2) On page 9 you state that cart abandonment tracking is available - can you let us know how customer's carts are inspected from the backend of odoo ?

See quotations in the sales team of your shop:
- Quotations: abandoned or current carts
- Sent Quotations: sales confirmed by payment not registered (e.g. wire transfer)

Thanks for clarifying this - I had not seen this before - you should raise the profile of this and provide an example of a server action that adds the ability to email the quotation to the customer to reactivate the cart completion process. Many sales can be rescued with this simple action.

 
3) On page 9 you state that there are customer testimonials are available for odoo enterprise - this is obviously completely distinct from a product review, which relates to a specific product.

This could be implemented in different ways. The main approach is to use the website_customer module for "Customer References", e.g: http://odoo.com/customers

But there are others ways:
- website_partners for resellers
- static HTML pages, using the Testimonial building block
- product reviews


The fact that you are suggesting that there are multiple ways to apparently achieve the result of allowing customers to be asked for service or product feedback and having that feedback that is 1) linked to the customer 2) is reviewable and 3) automatically published to the ecommerce front-end leads one to conclude that there is not a specifically designed and documented module for achieving 1,2 and 3. The website_customer module though described as "publish your customer references" does not appear to relate any testimonials to specific customers or to list testimonials under website admin - so where do testimonials come in on website_customer ?

Thanks again for clarifying further.

regards

James Fox

-- 
Fabien

_______________________________________________
Mailing-List: https://www.odoo.com/groups/community-59
Post to: mailto:community@mail.odoo.com
Unsubscribe: https://www.odoo.com/groups?unsubscribe