Home & Cook is the official E-commerce store for famous household brand names including Tefal, Jamie Oliver, KRUPS, Nespresso, Rowenta and Moulinex. Created 8 years ago, Home & Cook was designed, developed and managed by Dodec for one of our key accounts, GroupeSEB, a leading worldwide manufacturer of small domestic appliances and cookware.

Working closely with GroupeSEB, the team at Dodec continue to provide and grow an effective e-tail solution for Home & Cook, incorporating a forward thinking strategy, intuitive design and user focused ordering process, ultimately ensuring the customer is presented with a seamless online shopping experience.


Case Study

Adaptive and responsive design strategy shows 60% increase in conversion

As mobile and tablet usage continues to grow rapidly, Dodec have focused on effectively bridging the gap between mobile and desktop by employing responsive and adaptive design strategy for Home & Cook.
60%
Increase in mobile & tablet conversion
20%
Increase in unique purchases made on mobile & tablet
Following a significant redevelopment of the new adaptive design, results show a 60% increase in mobile and tablet conversion and a 20% increase in unique purchases made on mobile and tablet compared to the year before. Search optimisation has been improved greatly and the site is now fully SEO friendly.

Through years of growing and developing this E-commerce store, Dodec continue to look after all aspects of Home & Cook ensuring appropriate product positioning, and technology adoption to achieve the most positive customer experience possible.


Sylvia Douglas

Sylvia Douglas

Project Lead Developer

Home & Cook is built based on the ASP .NET MVC framework, using Dodec’s bespoke eCommerce / CMS platform. One major decision here was how to do the mobile version of the site. Do we do a fully responsive website or do we do separate mobile views? Well, we ended up doing a mixture of both, to get the best of both worlds.



The ASP .NET MVC framework is very well suited to separate mobile views. So it was extremely easy to create one layout for desktop views and one layout for mobile views. Why not just do one layout to suit both? It’s too restricting for the design and content. This way you get total freedom to design the desktop exactly how you want without having to think about collapsing it down to a desktop version. And you can have completely different content on each layout.



Then, on a page by page basis, a decision can be made whether to build that page with responsive code, or whether to do a separate view for it. So you minimise repeat code as much as possible for views that are suited to both desktop and mobile, but you can change content and layout completely for views that you really want to customise for the mobile version.