Splitting the configuration into steps also helps to handle compatibility, allowing for incompatible items to not be displayed within the next step. This example is also well-optimised for mobile devices, which is a common weakness of builders in a lot of cases. In this example, there are five very clear steps (as well as tooltips to help explain the steps) and then a clear add to cart that is activated once each option has been selected. This example from Interior Define is a great example of a multi-stepped approach that remains straightforward throughout. I think this makes things far clearer for the user and also helps to break up the process and keep things optimized for mobile etc. How should the front-end UX be approached?įrom my perspective, I think multi-dimensional builders should be split out into steps, with a very clear journey and clear endpoint to the user. Smart Pixel, ThreeKit or Cylindo) that would handle the front-end side and require either individual products be created in the back-end or products are combined dynamically. ![]() The alternative approach would be to use bundling, a configurable product (in a platform like Magento) or variants (in a platform like Shopify), but you’re likely to be far more restricted from a technical perspective and, in the case of configurable products in Magento, you’ll be fighting against performance. By using a technology like Vue or React, data manipulation can be more dynamic, meaning you’re not limited by the catalog capabilities of your eCommerce platform (particularly useful if you’re working with a platform like Shopify). Over the last year or two, it’s become very common to go beyond native product configuration and extend what the templating language of the core platform can do. How should a highly configurable product or customised product be structured? a car or a sofa) or even just configurable product sets or bundles. trainers on NIKE ID), a fully built / modular item (e.g. These are notoriously hard to position online, as there are generally lots of options, several steps, variable compatibility and then often additional complexity around pricing and availability.Įxamples of product builders could include a personalised product (e.g. So, I would say a product builder is essentially an advanced configurable product (although not always structured that way from a back-end perspective) with a number is customisable aspects or components. custom vs standard product types vs third party solutions) and then also look at really good examples, in each of these areas. ![]() In this article, I’m going to provide recommendations on approaching the UX side (including on mobile, which is critically important), talk about different routes (e.g. Product customisation, building or personalisation and generally more advanced configuration has become a big trend over the last few years – and getting the design and UX right is critically important, as it’s not simple and often requires a number of steps and aspects. ![]() These types of products can also be very engaging and generally a really nice user experience vs purchasing items separately. Over the last few months, we’ve been working with a number of eCommerce clients on creating, simplifying and optimising product builders and product configuration processes – with this being a key part of their business and an opportunity to drive improvement in conversion rates and AOV, most notably.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |