Pre-Launch E2E QA Report

The mega menu header font is displayed in light grey, resulting in poor visibility against the background.

Dropdown arrows are not properly aligned with the corresponding menu text.

When hovering over a single menu item, all submenu items turn black rather than isolating the hovered one.

Moving between categories snaps instantly with no smoothing. A 100–150ms delay should be introduced to prevent flicker on fast mouse movements.

The currently open mega menu provides no hover effect, making it difficult to identify the active selection.

Actual: The CTA button is placed too close to banner edges on mobile. In French (FR), the longer translated text overflows the button container, breaking the UI.

Expected: CTA button has consistent safe-area padding on all viewports. Translated text is accommodated without overflow in all supported locales (EN, FR, ES). Hero banner should use responsive image format (e.g. <picture> tag) to serve correctly sized assets for mobile vs desktop.

Actual: The header navigation uses inconsistent font sizes across different menu items. The brand logo does not display a hover/focus effect, making it feel non-interactive despite being a clickable link.

Expected: Consistent font styling applied to all navigation items in the header. Logo should display a subtle hover state (e.g. opacity shift or underline) to communicate interactivity. The layout for header links should ensure uniform typographic scale.

Actual: Navigation arrows on the Dragons Collections carousel require two clicks before the carousel advances. Collection images are oversized, creating excessive white space between carousel items.

Expected: Single click advances the carousel immediately. Collection images sized proportionally to maintain a balanced, visually consistent rhythm across all carousel slides.

Actual: The text block does not align with image gallery edges. Category links overflow in FR locale. "View All" CTA is hidden on mobile viewports. Category links within this section open in the same tab, navigating the user away from the homepage without preserving their browsing context.

Expected: Text aligned to gallery edges. Locale-safe link labels with no overflow in any supported language. "View All" visible and tappable on all screen sizes. Category links within the "Loved by Little Dreamers" section should open in a new tab so the user can explore categories without losing their homepage position.

Actual: Section heading size is inconsistent with the rest of the site. Left column content is right-aligned while right column content is left-aligned - layout feels unbalanced. Section numbers render as superscript rather than inline text.

Expected: Heading size matches site-wide typographic scale. Content alignment follows consistent column logic (e.g. left-aligned across both columns). Section numbers styled as inline body text.

Actual: Press/media logos in the "As Seen In" section are not linked to the corresponding publications or press articles. The section heading size does not match the typographic scale used across the rest of the website.

Expected: Each media logo links to the corresponding press article or publication in a new tab. Section heading size matches the site-wide typographic scale.

Actual: The newsletter subscription confirmation message appears inside a darker blue box that is visually disconnected from the soft-blue footer background. The "Thanks for subscribing!" message renders in a very large, bold font competing with the footer heading.

Expected: Confirmation message styled consistently with the footer component. Copy uses an appropriate font size and weight that complements the footer design without overpowering the primary heading.

Actual: The "Create a Trade Account" link resolves dynamically to the current page URL instead of a fixed trade registration destination. Clicking it from any page navigates to that same page.

Expected: Link navigates to a fixed trade account registration page. B2B customers should have a clear, functional path to sign up regardless of which page they are on.

Actual: On mobile, promotional homepage banner elements render as stacked static images, adding excessive page height and requiring heavy scrolling to view all promotions.

Expected: Promotional banners should be redesigned into a clean, horizontally swipeable carousel component with clear pagination or touch indicators on mobile to save vertical space and improve interaction.

Actual: On Android Chrome and iOS Safari, the automated marquee/scrolling animation in the footer moves at an excessively high speed, cutting links off mid-display and creating jarring visual jitter.

Expected: Animation velocity reduced to a smooth, non-disruptive speed. All content remains readable as it scrolls. Speed should pass baseline accessibility motion guidelines (WCAG 2.3.3).

Actual: A large empty white space appears between the navigation header and the start of the product grid on several collection pages (e.g. /products/latest).

Expected: Consistent, intentional spacing between header and product grid across all collection pages - no excessive blank area above the grid.

Actual: The category/collection description text is constrained to an overly narrow container, causing excessive line breaks. An expand/chevron arrow is displayed even when there is no additional content to reveal.

Expected: Description text uses a balanced readable width. Expand control is only shown when content is actually truncated and there is more to reveal.

Actual: When the final row contains only one product, the card stretches to fill the entire row width, making it disproportionately large compared to all other cards in the grid.

Expected: Cards in the last row maintain the same fixed column width as all other rows. Cards should never exceed normal grid column width regardless of row count.

Actual: The hover/secondary image on product cards does not fully overlay the default image - parts of the original image remain visible during the hover transition.

Expected: Hover image completely and cleanly replaces the default image. The transition is smooth with no image bleed-through at any point during the animation.

Actual: The final row of search results shows only 2 of 3 possible product cards, leaving an empty third cell. The third product only appears after clicking "Load More", creating an artificial and confusing pagination cutoff.

Expected: Product grid fills each row to full capacity before triggering Load More. All available products within the current page limit are shown. Load More loads the next full batch of results.

Actual: Product card image dimensions vary across different collection pages on mobile - some cards appear portrait, others square. This creates a visually inconsistent and unprofessional grid layout on mobile viewports.

Expected: A consistent card aspect ratio enforced globally via CSS across all collection and search result grids on all viewports. Recommend a fixed aspect-ratio property (e.g. 4/5 portrait) on all product card image containers.

Actual: When a sort option is selected (e.g. "Price: Low to High", "Newest First"), the product grid does not update to reflect the selected order. The sort selection appears to either not fire or fire incorrectly.

Expected: Selecting a sort option immediately re-orders the product grid to reflect the chosen sort criteria. The selected sort label is highlighted/active in the UI. Sort persists on pagination/Load More.

Actual: When a combination of filters is applied that returns zero matching products, the product grid area is left completely blank. There is no feedback message informing the user that no products match their criteria.

Expected: A clear "No results found" message with a suggestion to clear filters or broaden the search. Should include a "Clear All Filters" action link inline to encourage re-engagement.

Actual: Several internal links to collection/category pages use /products/[handle] format (e.g. /products/beds, /products/chairs). On Shopify, /products/ is the product detail page namespace. Collection listing pages use /collections/[handle].

Expected: All internal links pointing to collection/category listing pages should use /collections/[handle] format. Click-test all 20+ nav dropdown and on-page category links to verify they load the correct collection grid and not a 404 or incorrect product page.

The gallery displays only the plus (+) icon; the minus (–) icon is missing, so the zoom state is unclear.

The Previous arrow remains active when the first item is reached. The Next arrow remains active when the last item is reached. Both should be disabled at their respective limits.

The "Flannel" accordion is expanded but shows an X icon, while nested options like "Navy Blue" show a + icon – inconsistent iconography implying the wrong hierarchy.

Reaching a fabric description requires clicking through Materials & Care → Flannel → Sand – three levels for content that should be flattened into tabs with a simple colour list.

Expand/collapse behaviour has a noticeable pause before fully closing.

Navigation arrows are missing for browsing related products. The section becomes disproportionately large when few related products are available.

Actual: The configurable product displayed in the mini cart does not always match the selected configuration. Reproduced: add Girafe Pouf (Chenille White) to cart - mini cart may show a different variant. Add Little One Chair (Jersey Orange Astre) - same mismatch occurs.

Expected: The mini cart should correctly display the exact selected configuration (size, colour, or variant) of the added product at all times.

Actual: The scrollbar is positioned very close to the product content, making the UI feel cramped and visually unbalanced. Content and scrollbar overlap in the available space.

Expected: Adequate spacing maintained between the scrollbar and content to improve readability and visual clarity.

Actual: The product title and product image in the mini cart are not clickable and do not redirect to the corresponding product detail page.

Expected: The product title and product image should be clickable and redirect users to the respective product detail page in the same or new tab.

Actual: No validation or error message is displayed when the user increases the quantity beyond the available stock. Users can add quantities that exceed inventory without any feedback.

Expected: An accurate stock/inventory message should be displayed when the requested quantity exceeds the available stock. Quantity input should cap at the available limit or display an inline error.

Actual: The "Continue to Checkout" button in the mini cart does not display its hover state correctly. When hovered, the transition is incomplete, resulting in the hover effect being only partially visible - the animation does not complete its cycle.

Expected: When hovered, the "Continue to Checkout" button transition should complete fully and consistently. The hover state should match the button styling system used across the rest of the site.

Actual: After successful registration, the user is not redirected to the account section. The page remains on the registration screen with no confirmation or next-step indication.

Expected: User should be redirected to their account dashboard, or shown a clear confirmation message with account activation instructions and a next-step CTA.

Actual: The account activation email link redirects to the default Shopify OTP/login page instead of directly activating the account and logging the user in.

Expected: The activation link should activate the account, sign the user in automatically, and redirect to the account dashboard - without a secondary login step or loop.

Actual: After completing login, navigating to the homepage and then back to the account page redirects the user back to the login page. Session state appears to drop during navigation.

Expected: Authenticated users remain logged in across all navigation. Session should persist until explicit logout or token expiry.

Actual: The forgot password flow is not functioning - users cannot receive a reset email or successfully reset their password. Password recovery is completely broken.

Expected: Entering a registered email address triggers a password reset email. The reset link sets a new password and logs the user in without a loop.

Actual: When logged in and navigating to the order history section, past orders are either not displayed or the section is blank. Pagination controls (if present) do not function correctly.

Expected: All past orders are listed chronologically with order number, date, status, and item count. Each order is expandable to show line items, shipping address, and tracking information.

Actual: Addresses saved in the account address book do not auto-populate the shipping address fields at checkout for logged-in users. The address book section itself may also show blank or incomplete address records.

Expected: Saved addresses are displayed in the account address book. At checkout, the default address pre-fills the shipping form. Users can select from saved addresses via a dropdown.

Actual: Products added to the Lovelist/Wishlist do not persist after the user logs out and logs back in. The Lovelist appears empty on subsequent sessions even when items were saved.

Expected: Lovelist items persist across sessions when the user is logged in. Items saved to the list are retrievable on any device when the same account is used.

Actual: The "Buy Now" button behaviour is inconsistent across product types. On some PDPs it bypasses the cart and goes directly to checkout; on others it adds to cart instead. The button state (enabled/disabled) does not always reflect variant selection status.

Expected: "Buy Now" consistently skips the cart and navigates directly to checkout with the selected variant pre-loaded. The button should be disabled until a complete variant selection is made.

Actual: When scrolling stops between sections, timeline content overlaps and is difficult to read. The timeline does not snap to the nearest story.

Expected: Content should snap smoothly, with only one story fully visible at a time.

Actual: The Discover button displays no hover effect, inconsistent with other interactive buttons on the site.

Expected: Hover effect consistent with other buttons across the website.

Actual: Some text renders at an excessively large size. The "Crafted For Imagination" carousel has no navigation arrows. Images are oversized. Navigation arrows on bespoke bed pages remain active at the first/last item.

Expected: Appropriate typography sizing; carousel navigation arrows; arrows disabled at limits; proportionally sized images.

Actual: The "Contact Us" header and the blue contact block are pulled to the left column, leaving an empty void across the right side of the viewport.

Expected: Content should be consistently aligned throughout the layout.

Actual: Placeholder keys faqs.title and faqs.expandAll visible. Page styling appears incomplete. Spacing is uneven throughout.

Expected: Correct production styling; placeholder keys replaced with intended copy; consistent spacing.

Pages affected: Shipping & Delivery, Returns, Terms & Conditions, Privacy Policy.

Actual: A large amount of empty white space appears above the page title before the main content begins.

Expected: Consistent top spacing across all legal pages.

Actual: After selecting French (FR) or Spanish (ES) from the header language switcher, a large portion of the website content remains displayed in English. Navigation trees, static blocks, button labels, headings, forms, and homepage banners fail to translate. This creates a mixed-language experience on every page.

Expected: Selecting FR or ES from the header language switcher must successfully translate all supported frontend elements, including navigation trees, static blocks, button labels, headings, forms, and core copy. The storefront must maintain a consistent, fully localised experience per language view without rendering mixed-language content strings on the same page layout.

Actual: The header contains: nav items (Nursery, Kids Room, Playroom, Bespoke Beds, Accessories & Essentials), EN language, Search, Account, and Cart icons. No direct "Contact" link is visible in the header. Contact is only reachable via the footer or by navigating manually to /contact.

Expected: For a luxury bespoke furniture brand where customer service is paramount, a "Contact" or "Concierge" link in the header navigation or utility bar is strongly recommended. This is a key trust signal and conversion support element for high-value purchase decisions.

Actual: On mobile devices, tapping images triggers a hover/overlay effect. Buttons and links display a desktop hover effect (colour change, underline, shadow) on tap. These desktop-style hover states linger momentarily after the tap, creating a confusing and visually inconsistent experience on touch devices.

Expected: Hover effects should be removed from buttons, links, and images on mobile devices. Buttons should only display appropriate touch states (e.g. :active or :focus, if required) without applying desktop hover styles. Use @media (hover: hover) CSS media query to scope hover styles to pointer devices only.

Actual: The test product is visible on the live site at dragonsofwaltonstreet.com/product/test. Non-production content is accessible to real customers.

Expected: All test products, test content, placeholder data, and any other non-production elements should be removed or disabled so they are not visible to customers on the live website before public launch.

Actual: The first click on any product card triggers the hover/secondary image swap only - it does not navigate to the Product Detail Page. A second click is required to actually follow the product link. This breaks standard e-commerce card behaviour and is confusing, especially on mobile touch devices.

Expected: A single click on a product card should immediately navigate to the corresponding PDP. The hover/secondary image swap should not intercept the click event or prevent navigation.

Actual: Product card sizes vary significantly across different search result views and collection grids. Some cards appear significantly larger or smaller than adjacent cards, creating a broken, unprofessional grid layout. The CSS constraints for card max-height or grid-template-columns appear inconsistent across page templates.

Expected: Product card dimensions must remain consistent across all search result views and collection grids. A fixed aspect-ratio and consistent column template should be enforced via CSS globally. Suggest a luxury approach: consistent portrait cards (e.g. 4/5 ratio) with uniform padding.

Actual: The final visible row of search results shows only 2 of 3 possible product cards before "Load More" is triggered, leaving an empty third cell visible. The missing third card only appears after clicking Load More, creating an artificial and confusing pagination cutoff.

Expected: The product grid fills each row to full capacity before triggering Load More. All available products within the current page limit are shown. The Load More button only loads the next batch of results beyond the current page capacity - not products that belong to the current page.

Actual: When a search query returns zero results, the product grid area is left completely blank. There is no feedback message, no "did you mean" suggestion, and no alternative action for the user to take.

Expected: A clear "No results found for [query]" message should be displayed, with: (1) a suggestion to clear filters or broaden the search, (2) a "Clear All Filters" / "Start Over" action link, and (3) optionally a recommendation module showing trending or popular products to re-engage the user.

Actual: The Load More button label and behaviour are inconsistent across search and collection pages. In some views it loads a single additional product rather than the next full batch, making pagination feel broken and unpredictable.

Expected: A consistent, clearly labelled pagination control ("Load more", "Show next", or "View more") that reliably loads the next full batch of results. The button should display the number of remaining results (e.g. "Load more (12 remaining)") where possible. Infinite scroll should be considered as an alternative for a luxury e-commerce experience.

Actual: The text insertion cursor (caret) is misaligned within the filter search input field. When clicking into the filter's search box, the cursor renders at an incorrect vertical position - either too high or too low relative to the input baseline - making it feel broken and unpolished.

Expected: The text cursor should be vertically centred within the filter input field. The input should use standard line-height and padding values to ensure correct cursor placement across all browsers.

Actual: The selected filter count displays in a very small font size and is not aligned with the surrounding text. The count badge appears disconnected from the filter label it belongs to.

Expected: Appropriate font size for visibility, aligned with the filter label text. The count badge should be styled consistently with the design system.

Actual: The Clear Filters section shifts position and stays highlighted with a black background after filters are applied - inconsistent layout before and after filtering.

Expected: Filter drawer layout remains consistent. Clear Filters does not shift position or display inconsistent styling before or after filter application.

Actual: After selecting and then deselecting filters without closing the drawer, the filter state becomes locked. Some filter options remain greyed out or blocked, and the product grid does not update until the page is refreshed or the Apply button is explicitly clicked. This "refresh logic block" creates a frustrating experience for users trying to iterate on their filter selection.

Expected: Filter state should update reactively without requiring a page refresh. Deselecting a filter should immediately re-enable all relevant options and update the product grid in real time.

Actual: When conflicting filters are selected then one is removed without closing the drawer, other options remain greyed out and cannot be selected until Apply is clicked.

Expected: Filter availability updates dynamically. Options become selectable immediately after conflicting filters are removed.

Actual: The colour Blue is entirely absent from filter options despite blue products existing in the catalogue. Applying the Pink filter returns only one product when multiple pink-tagged products should be visible. This is a data-level issue - the product metafields or tags used to power colour filtering are either missing, misspelled, or not assigned to the relevant products.

Expected: All colour options represented in the product catalogue must appear in the colour filter. Applying a colour filter must return all products correctly tagged with that colour. A full audit of product colour tags/metafields is required to fix the data at source.

Actual: A scrollbar renders inside the filter drawer even when content doesn't require scrolling. URL: /products/beds

Expected: Scrollbar only shown when content exceeds the available viewport height. Use overflow-y: auto (not scroll) to ensure the scrollbar only appears when necessary.

Actual: On the filter & sort drawer, the modal close icon (X) in the upper right corner is partially covered by or overlapping with the container's vertical scrollbar, making it very difficult to click.

Expected: The close icon must be entirely clear of the scrollbar bounding box - correct right-side margin or explicit z-index/positioning required.

Actual: On iOS Safari & Android Chrome, scrolling upward inside the open filter drawer drags the entire menu down/up, hiding content and exposing a blank area underneath. Background page scrolling is not locked.

Expected: Background page scrolling must be locked while the filter drawer is active. The modal container should remain stable during internal scrolling. Use overscroll-behavior: contain on the drawer container.

Actual: On mobile (iOS Safari & Android Chrome), tapping the filter drawer close icon (X) displays a native browser blue outline/focus border that disrupts the premium custom styling of the storefront.

Expected: Custom focus styling should be applied, suppressing the native browser focus ring on this element while maintaining accessibility for keyboard users.

Current: When interacting with the main navigation header (e.g. "Nursery", "Kids Room"), clicking the top-level items does not load a category overview page. The label text is non-interactive on desktop, so users who click the parent item rather than a sub-item reach a dead end with no content loaded.

Requested: The top-level menu paths should be linked to their corresponding Shopify collection overview pages so users can click through seamlessly to the full category listing. Sub-items should also be shown as individual linked items that reveal on parent hover/click. URL example: clicking "Nursery" should navigate to /collections/nursery.

Current: On mobile views, promotional homepage banner elements are rendering as stacked static images, adding excessive page height and requiring heavy scrolling to reach any content below the hero area. The desktop-oriented layout does not adapt appropriately for portrait/narrow viewports.

Requested: Redesign the homepage banner section into a clean, horizontally swipeable carousel component with clear pagination dots or touch/swipe indicators. This will save vertical screen space and significantly improve mobile interaction patterns. The carousel must support native touch gestures (swipe left/right) and must not block other page interactions.

Current: When scrolling the homepage on a mobile viewport, the hero section scroll animation or video continues to loop and play after the user has scrolled past the hero content. The animation lingers in the background, competing with subsequent page sections and consuming unnecessary GPU/battery resources on iOS Safari and Android Chrome.

Requested: The hero animation/video should pause or stop when it leaves the visible viewport. Use an IntersectionObserver to detect when the hero is off-screen and pause the animation/video programmatically. On iOS Safari, also ensure the video has playsinline and muted attributes to prevent autoplay restrictions from interfering.

Current: When accessing the site on mobile viewports (reproducible across Android Chrome and iOS Safari), the automated marquee/scrolling animation within the footer moves up and down at an excessively high speed. The animation rate causes links to be cut off mid-character and creates jarring visual jitter that is unacceptable for a premium luxury brand. The speed is inconsistent between desktop (acceptable) and mobile (too fast to read). Evidence: ScreenRecording_07-02-2026 16-45-38_1.MP4.

Requested: Reduce the footer animation velocity significantly to a smooth, non-disruptive reading speed - slow enough for users to read all links without jitter. The animation must also respect the user's prefers-reduced-motion media query (pause when true) and should pause when the footer is not in the active viewport to save CPU/GPU resources.

Current: When active collections are refined via the Filter & Sort sidebar, the applied parameters are completely hidden on the main product grid section. Users have no visual indicator of which filters are active without re-opening the drawer. The "Clear All" action is also not visible on the grid page, creating confusion for users trying to reset their browsing context.

Requested: Introduce an active filter chip region directly beneath the collection title (e.g. "Latest Nursery"). This row will display the currently active filters as individual dismissible chips, each with an "X" clear target to remove that individual filter. A global "Clear All" action link must sit alongside. Applies to both PLP collection pages and the Search results page. All filter colour values (Blue, Pink, etc.) must return correct product counts from the data layer.

Current: The Lovelist/Wishlist feature is referenced in the account section and product cards but does not function for logged-in users. Items added to the Lovelist are not persisted and the feature appears partially scaffolded. There is no standalone Lovelist page and no account integration.

Requested: Implement a fully functional Lovelist/Wishlist feature that: (1) allows logged-in users to save products from PDP and PLP cards via a heart/save icon, (2) persists the list across sessions and devices tied to the user's account, (3) is accessible from within the account dashboard section (not as a separate standalone page - it must be integrated into the account navigation), and (4) supports "move to cart" and "remove" actions from the list view. The Lovelist must only be available to logged-in users - guest users should be prompted to create an account or log in.

Current: Navigating to /cart or clicking "Continue to checkout" from the mini cart takes users directly to the Shopify-hosted checkout (/checkouts/...), which uses the default Shopify checkout UI. There is no branded intermediate cart review page. Users have no opportunity to review their full basket, apply a discount code, or confirm item details before entering the checkout flow.

Requested: Implement a dedicated branded /cart page that sits between the mini cart and the Shopify checkout. This page should display: (1) product image, title, variant, and quantity stepper per line item, (2) remove/edit actions per line item, (3) an order summary panel with subtotal, discount code field, and estimated shipping, and (4) a prominent branded "Proceed to Checkout" CTA (black background, white text matching the brand button system).

Current: Pagination is inconsistently implemented across collection and search result pages. Some pages use a "Load More" button that loads only one additional product at a time. Others have no pagination at all. This should also be represented in the sitemap.

Requested: Implement consistent, accessible pagination across all collection and search pages. Options: (1) a "Load More" button that deterministically loads the next full page of results each time it is clicked, or (2) infinite scroll with a scroll-triggered loader and a fallback button. The selected approach must be clean, predictable, and documented. It must be consistent across all listing page types. Add the pagination pattern to the sitemap. Acceptance criteria: the next/load-more button must function correctly on every page load without requiring a page refresh to reset state.

Current - three issues identified:

1. No edit option: There is no edit option or icon present on mini cart line items. Users cannot modify a product's configuration (size, colour, fabric) after adding it to the cart without removing and re-adding the item entirely.
2. Dated native quantity dropdown: Quantity is controlled via a native browser <select> dropdown element (displaying as "Qty: 1 ▼"). Users must open a dropdown to change quantity. This feels dated and out of place for a premium luxury brand experience - a custom +/- stepper is the expected pattern.
3. Checkout button shows total inline: The "Continue to checkout" button at the bottom of the mini cart displays the total price inline within the button label itself (e.g. "Continue to checkout $18,313.00"). There is no separate subtotal/summary row above the button showing item count and order total before the user commits to checkout.

Requested: (1) Add a pencil/edit icon per line item that links back to the PDP with the current variant pre-selected. (2) Replace the native <select> with a custom branded +/- quantity stepper component. (3) Add a dedicated subtotal row above the checkout CTA showing item count and order total separately, and remove the price from within the button label itself.

Current: The final "Pay now" call-to-action at the checkout payment step renders in Shopify's native default blue colour (#3B1BDB or similar). The brand uses a distinct black background (#222222) with white text for all primary action buttons across the entire storefront (e.g. "Add to basket", "Create account", "Sign in"). The blue Pay Now button looks completely unstyled and detached from the brand design system. This is a pre-launch blocker for brand consistency. Also filed as DWSC-44.

Requested: Update the "Pay now" button to match the primary theme button design - black background (#222222 or #1B1B1B) with white text. This can be achieved via the Shopify Checkout Editor (available on all plans) or the Checkout Branding API (Plus). Acceptance criteria: the Pay Now CTA must look native to the brand and match the main button styling across all checkout steps and all tested devices.

Current - two issues:

1. Breadcrumb missing on all collection, PLP, and PDP pages: All mentioned pages (e.g. /collections/cot-beds-cribs) show no breadcrumb trail (e.g. Home > Nursery > Cot Beds & Cribs). Users have no visual indicator of where they are in the site hierarchy and no quick way to navigate back up the category tree. Note: PDP does show a partial breadcrumb ("Furniture / Cot Beds & Cribs") but it is inconsistent with what collection and PLP pages show. Breadcrumbs also benefit SEO via structured data markup (BreadcrumbList schema).
2. No "Quick add to basket" hover action on product cards: Hovering over a product card reveals only a very subtle image zoom effect. There is no "Quick add" or "Add to basket" CTA revealed on hover. Users must click through to the full PDP to add an item to the basket, adding unnecessary friction for users who already know what they want.

Requested: (1) Implement consistent breadcrumb navigation across all collection, PLP, and PDP pages using Shopify's breadcrumb liquid object and include BreadcrumbList JSON-LD structured data for SEO. (2) Add a "Quick add to basket" CTA on product card hover - this should reveal an "Add to basket" button (or a variant selector if the product has variants) without requiring the user to navigate to the PDP.

Current: The checkout framework currently lacks installment-based payment methods. For targeted high-conversion demographic sectors - particularly the UAE market where the brand has significant audience exposure - flexible installment payment options are a standard consumer expectation. The absence of BNPL options is likely to reduce conversion rates for high-value basket orders.

Requested: Integrate "Buy Now, Pay Later" (BNPL) installment payment services into the checkout flow. Priority services for the UAE market are Tabby and Tamara, both of which are very popular and widely expected by UAE consumers. Both services offer Shopify-compatible integrations. Additionally, evaluate wider BNPL options (e.g. Klarna, Clearpay) for the UK market. BNPL options should also be surfaced on the PDP near the price/CTA to reduce price anxiety before users reach checkout.

Actual: There are no estimated delivery times or date ranges shown anywhere throughout the shipping configuration or payment selection steps. Customers are forced to select shipping rates blindly without any visibility into when their high-value luxury items will arrive, which drastically reduces transactional transparency.

Expected: Clear estimated delivery timeframes or delivery window ranges must be explicitly displayed alongside each available shipping tier method (e.g. "Standard Delivery - arrives 5-7 business days", "Express - arrives 2-3 business days"). This is critical for a luxury goods brand selling high-consideration products.

Actual: The final "Pay now" action button renders in Shopify's native default blue colour (#3B1BDB or similar). The brand uses a distinct black background (#222222) with white text styling across the entire storefront for primary action buttons (e.g. "Add to basket", "Create account", "Sign in"). The blue button looks completely unstyled and detached from brand guidelines.

Expected: The "Pay now" button styling must match the primary theme design. Update the button to use a black background (#222222 or #1B1B1B) with white text via the Shopify Checkout Editor or custom theme configuration settings. This is achievable without Shopify Plus by using the checkout.liquid or Checkout Branding API.