The Task

We refined WhyBuy's identity so it looks the same wherever customers meet it. That meant a new colour palette, tighter typography and a set of visual motifs, written up in brand guidelines.

The same system now runs through the website theme, social posts, ads and seasonal campaign graphics, so a customer who clicks an ad lands on a site that looks like the ad.

We simplified the header and rebuilt the menu around how people look for hire items: by type of job or occasion as well as by product. The menu runs on smart collections driven by product data, so new products appear in the right place without manual sorting.

A "How it works" section explains booking, delivery slots and collection in three steps. Callouts handle common questions, such as where you can collect if you live outside the M25, with a sign-up for updates when delivery expands.

Product pages now show related items picked from a collection set on each product, so someone hiring a pressure washer also sees the other commonly hired garden maintenance products, and the outdoor party equipment for when the patio has been cleaned.

WhyBuy wanted to sell kits, such as a party bundle or a moving bundle, as one booking. The site's add to basket came from Booqable's booking widget, which was built for one product per page, so a bundle had nowhere to sit.

We set up each bundle as a product in both Booqable and Shopify, and updated the product template so the widget books several items together for the same dates, keeping inventory correct. The bundle price sits above the list of what's included, so customers see the cost before they scroll.

Selling hire bundles when every item has its own booking Read Now

On product cards across the homepage and collections, we hid the contents slider so bundles read cleanly next to single items. Bundles have their own menu, image template and icon, and appear in related products, collections and Google Ads. We cover the approach in selling hire bundles when every item has its own booking.

A hire price has more parts than a retail price: a minimum hire period, the price for that first period, and a rate for each extra day. On WhyBuy's site those prices were set or referenced in three places. The price on tiles came from Booqable, the extra-day pricing table from a Shopify metafield, and the pricing shown in search listings from the meta description. On a lot of products, the three did not match.

We mapped every field the product page needed, where its data came from, and the length limits and defaults for each. The new product template is built from those structured fields, showing the first-period price and extra-day rate together, with specifications and customer reviews alongside.

Keeping hire prices consistent from search result to basket Read Now

We then designed a new product listing process and trained WhyBuy's in-house team to use it. Every new product is listed with its booking price, pricing table, meta title and description set from the same figures, so pricing is consistent from the day it goes live. More on this in keeping hire prices consistent from search result to basket.

WhyBuy's booking checkout runs on a Booqable subdomain, separate from the Shopify store. A customer's cookie choice had to carry from one to the other. If it didn't, tracking broke between browsing and booking, and ad and affiliate platforms lost the sale.

The original consent setup caused two more problems. Its script clashed with Klaviyo, and its settings icon sat over the basket button on mobile and desktop.

Cookie consent when your checkout lives on another domain Read Now

We set up one consent policy covering the main domain and the booking subdomain, moved the icon away from the basket and tested it against the Klaviyo and Booqable scripts before switching it back on. We then updated GA4, affiliate, Google Ads and social ads tracking so bookings were tracked from first click to checkout. Read how in cookie consent when your checkout lives on another domain.

With tracking in place across Shopify and Booqable, we could see where customers dropped out between landing and booking, and fix those points one at a time.

Ads are grouped by what people hire for, such as garden, cleaning, and party and events, with each campaign sending traffic to a matching collection or landing page. Seasonal pages, such as Christmas, get homepage and menu space while they run. Email sign-up sections and Klaviyo flows bring back visitors who don't book on their first visit.

WhyBuy now has one brand across its site, ads and social, and a store where Shopify and Booqable work as one system. Bundles book like single items, new products go live with consistent pricing, and bookings are tracked through to checkout.

Running hire or bookings through Shopify? We connect Shopify with booking platforms so pricing, checkout and tracking work as one. Tell us about your project.