Bug Guide

Welcome offer cannot be dismissed on mobile

A shopper sees the "Take 10% off your first order" offer but cannot dismiss it on a phone.

1. Open the home page in a narrow viewport (or use a mobile device).
2. Refresh the page so the welcome offer and cookie notice are visible.
3. The close (x) button is not visible in the mobile viewport, but is visible on larger screens.
4. Notice that start shopping button may also be overlapped by the cookie notice.
5. This causes users to need to dismiss the cookie notice first before they can interact with the welcome offer.

1. Open or resize the same page to a viewport wider than 768px.
2. Refresh the page.
3. Click the × in the welcome offer.
4. Observe that the offer closes normally.

1. The close (×) control is visible above the cookie notice on all supported mobile widths — not just tappable, but rendered without any part hidden.
2. The "Start shopping" call-to-action is fully visible and fully tappable, with no portion covered by the cookie notice.
3. The cookie notice remains fully visible and functional after the fix.
4. Behavior on viewports wider than 768px is unchanged.

"Charged twice for the same order?"

Getting a wave of complaints from customers saying they placed a single order but were charged twice. A couple of them mentioned they "clicked the button twice because nothing happened the first time." Not sure if that's related — passing it to engineering to look at.

Checkout error message is unhelpful — hurting conversion

When a shopper submits checkout with a missing or invalid field, they get one generic "Please fill in all fields" message with no indication of which field is the problem. Session replays show people re-checking every input in frustration; funnel data shows abandonment spikes at this step. Fixing this should be a straightforward conversion win.

• Each invalid field is called out inline, with a message that names the field and what's expected.
• Valid fields don't get flagged as errors.
• Successful submissions behave exactly as they do today.

International customers can't check out

Sales flagged this — orders from non-US customers aren't going through. Canada, UK, and Japan all seeing it. Would like a triage plan by end of day: whether this is a same-day fix or something that needs a temporary workaround while a proper fix ships.

State/Province selection carries over when the country changes

A shopper changes the selected country in the checkout form, but a previously chosen state or province value silently carries over — so the form submits with a state that doesn't belong to the new country.

1. Add any item to the cart and navigate to the checkout page.
2. Select United States as the country and pick a state (e.g., California).
3. Change the country to a different one (e.g., Germany or United Kingdom).
4. Fill in the remaining fields and submit — or inspect the form data.
5. Observe that the state field still holds the previously chosen value ("CA") even though it makes no sense for the new country.

1. Reload the page and pick a country only once before submitting.
2. Observe that the state value corresponds correctly to the selected country.

1. Changing the country clears any previously selected state/province value.
2. The state field re-renders correctly (select vs. free-text input) based on the new country's regions.
3. The required-field check catches the empty state after a country change instead of allowing a stale value to slip through.
4. No regressions to the initial country selection flow.

"The Add to Cart button is broken on some plants"

Customers keep messaging in convinced the "Add to Cart" button is broken on certain products — they click it and nothing happens. When I look at those products they're actually sold out, but that's not obvious to shoppers. Can we make it more obvious? People shouldn't have to contact us to figure out that a plant is out of stock.

One of the product cards has a missing image

One of the product cards on the plant listing is showing a broken image — the rest of the card looks fine but there's no photo. Looks bad for something a shopper sees first. Low priority relative to the checkout issues, but let's not ship the release with a broken image visible on the homepage.

Clear Cart dialog locks the page

After dismissing the Clear Cart dialog, customers are unable to click anything on the site and are forced to refresh the page to continue shopping.

1. Add an item to the cart to open the cart modal.
2. Click Clear Cart to open the confirmation prompt.
3. Click Keep Items or Clear Cart to close the prompt.
4. If you try to click any product or navigation link on the page, it has no effect.

1. Confirming "Clear Cart" successfully empties all items from the cart.
2. Closing or confirming the dialog leaves the page fully clickable so customers can keep browsing without refreshing.

Same promo code can be applied multiple times

A shopper can apply the same promo code repeatedly and receive the discount more than once, driving the cart total down with each duplicate application.

1. Add at least one product to the cart and navigate to the cart page (/cart).
2. Enter a valid promo code (for example GHC2026 or WELCOME10) and click Apply.
3. The coupon appears in the applied list and the discount is reflected in the total.
4. Without reloading, enter the same promo code again and click Apply.
5. Now, the same coupon is listed again (and the discount total increases).

1. The same promo code cannot be applied more than once per cart session.
2. A second attempt shows clear feedback (e.g., "This promo code is already applied.").
3. discountTotal reflects each distinct coupon at most once.

Cart and checkout totals ignore the sale price

A shopper adds an item marked "On Sale" to their cart. The line-item price in the cart matches the sale price shown on the product card, but the cart Subtotal and Total — and the checkout Order Summary and Place Order button — are calculated from the higher crossed-out price instead of the sale price.

1. In the header, click Sale (or on the shop page, sort by On Sale) and pick any product showing a "Sale" badge with a strikethrough original price.
2. Click Add to Cart. The cart modal opens automatically.
3. In the modal, compare the line-item price against the modal's Total — the total is higher than the line-item price times quantity.
4. Click View Cart & Checkout. On the cart page, the line item shows the sale price, but the Subtotal and Total use the original (pre-sale) price.
5. Click Proceed to Checkout. The Order Summary and the Place Order button both show the inflated total.

1. Add a product without a "Sale" badge to the cart.
2. Observe that the line-item price, the modal total, the cart Subtotal, and the checkout total all agree.

1. Cart-modal total, cart-page Subtotal and Total, and checkout Order Summary all reflect the sale price for items on sale.
2. Per-line item totals in the cart page and checkout Order Summary agree with the summary Subtotal.
3. The Place Order button shows the same total as the Order Summary.
4. Non-sale items (no compare_at_price) are unaffected.
5. A percentage-based promo code applied on top of a sale item discounts against the sale price, not the crossed-out price.

Stale search results

As a shopper types in the header search, earlier suggestions can appear after newer ones, so the list does not always match the current query. Only shows up under network latency.

1. Open the app and, in browser DevTools, enable a throttled network profile such as Fast 3G.
2. In the header search box, quickly type a short query and then extend or replace it — for example type mon and then highlight it to replace it with snake.
3. Repeat with a few different search terms if needed.
4. Observe that the suggestions may display results for an earlier query instead of the text currently in the input.

1. Open the app on a normal network profile or with a stable connection.
2. Type a new query in the header search box.
3. Watch the suggestions update as each character is entered.
4. Observe that the visible suggestions remain consistent with the latest text and do not lag behind the current query.

1. Header-search suggestions always correspond to the text currently in the input, regardless of request order or network latency.
2. Responses from stale (superseded) requests are discarded and never overwrite newer results.
3. Behavior is verified under a throttled network profile (e.g., Fast 3G) with rapid typing.
4. No new console errors or unhandled promise rejections introduced by the fix.