Biion Footwear is a company aiming to bridge the gap of EVA footwear that is elevated in both performance and Design.
This project was done with NFA and Highlighter Studio. NFA built the Webdesigns, Highlighter was responsible for working with the Client for implementing the Web Designs. Biions website previously relied solely on Pagefly pages which had their SEO, as well as current theme in chaos.
FireNet was responsible for working with Highlighter for developing solutions around many of the challanges required for updating the website.
1.)
The main challange FireNet was tasked with was Biions products went over the 100 variant limitation. After a thorough investigation weighing different options, given the usecase, we decided to implement internal product linking. For more information you may see this article here
Collections were redesigned with hidden collections used for linking the products via cannonical links.
Theme customizations were also heavily done on the PDP in order to update the option on hover, showing the customer which color they were thinking of selecting. Once clicked, the colour will take them to the internally linked Product for that colour, allowing them to stay within the 100 variant limitation on Shopify.
.webp)
2.)
With this project, we upgraded their theme to OS2.0 which also allowed them to leverage the new collection filters. They required some custom filters, those were created using metafield definitions allowing Biion to add and remove products from specific shoe types, or Models.
3.) FireNet Designs did multiple theme updates, as well as created Custom sections for Biion to use for specific content copy. The most notable one is the "What makes Biion tick" section.
4.) Lastly for a better UGC experience, NFA had built custom design styling on top of Yotpo Reviews. A Custom section was built in React for aggregating Review data from Yotpo's API, as well as multiple style updates for the Yotpo Review widget. Designs were originally complex requiring a full custom build, however there wasn't enough budget and original scope for this request. After discussing with the client it was agree'd to pull this requirement out and add it in as a 2.1 version.
