eCommerce Website

Thank you for your suggestions!
Please take a read of our Canny Etiquette before creating a post.
Apple Pay Express and Click & Collect Services
We've had customer reports where a shopper selects Click & Collect, but when completing checkout using ApplePay Express at the top of the checkout, the order defaults to home delivery instead. What's happening: • If the customer uses ApplePay Express at the top of the checkout, the system bypasses or overrides the selected delivery method. • The order defaults to standard delivery to the billing/home address. • If ApplePay is selected at the end of the checkout process, the chosen delivery method (Click & Collect/DPD Pick Up) is respected and works as expected. So technically, the functionality does work - but only if ApplePay is triggered at the end of the journey. Why this is a problem: From a UX and customer journey perspective, this is highly misleading: • Customers reasonably assume their delivery choice is locked in once selected • Express checkout appears visually equal to (or preferred over) standard checkout, but behaves differently • There is no warning or indication that ApplePay Express will ignore the delivery selection This results in: • Orders sent to the wrong fulfilment route • Customer confusion and loss of trust • Additional CS workload and manual corrections In short, the checkout allows customers to make a 'valid' selection that is silently discarded. Suggested improvements: Respect delivery selection for Express Checkout Disable Express Checkout when non-delivery options are selected Clear UX messaging (display a warning) Reorder or visually seperate Express Checkout - The current layout strongly encourages Express Checkout before fulfilment is truly 'finalised'
2
Ensure CSS updates are force-refreshed for returning visitors (cache busting)
We regularly invest in design and development updates that modify the main CSS. However, returning visitors can sometimes see a broken or malformed layout due to cached CSS files in their browser. This is a long-standing issue across the web and one many experienced developers will recognise. From customer feedback and internal staff comments, this has already caused confusion, with users assuming the website is broken. Critically, we cannot rely on customers to hard refresh their browser, clear cache, or open the site in incognito mode. Most users will not do this and may simply leave the site without reporting the issue. As a business paying for design and development time, we expect visual updates to be visible immediately to both new and returning visitors. Problem Browsers cache CSS aggressively. When core styles change, returning visitors may still load old CSS against updated HTML. This can result in broken layouts, spacing issues, missing styles, or incorrect formatting. Customers may lose trust and abandon the site without contacting us. Proposal Implement automatic CSS cache busting, using one of the following standard approaches: Append a version number to CSS files (for example: style.css?v=1.2.3). Automatically increment the CSS version whenever changes are deployed. Alternatively, generate new stylesheet filenames for updated CSS bundles. Ensure this applies to both custom client CSS and platform level styles. This ensures browsers always fetch the latest stylesheet without requiring any action from the customer. Why this matters Prevents customers seeing a broken or outdated layout. Protects conversion rates and brand trust. Ensures paid design updates are visible immediately. Aligns with long-established web development best practice. Reference Explanation of CSS versioning and cache busting: https://developer.mozilla.org/en-US/docs/Web/HTTP/Guides/Caching#cache_busting This should be a relatively small technical change but would have a disproportionately positive impact on user experience and reliability across all browsers and devices.
4
Load More