GlassHouse Docs Support
Reference

Find and fix a connection issue

Start with what you see, then check the relevant connection.

The launcher does not appear

For JavaScript, confirm the target exists, is empty and is connected to the document before calling mountGlassHouse. Import the stylesheet and check that /api/glasshouse/config returns JSON.

For WooCommerce, check that GlassHouse is active and that the page includes the GlassHouse block or shortcode. Clear the site’s page cache after updating.

Chat cannot connect

In WooCommerce, check GlassHouse → Settings for the connection status. For a custom store, check the registered origin and server credential, then inspect the server log for the token exchange.

The service must reach /api/glasshouse/agent-tools without a login page or redirect. Shopper requests need a valid store session, including for guests.

A product is missing

Confirm the product is published, available and in stock. For custom stores, keep the ID and its type consistent between the catalogue, product lookup and page context. Return absolute product and image URLs.

For WooCommerce, review the product’s species match in Prepare Recommendations.

A plant is missing from a layout

Check its reviewed mature width and the growing conditions selected by the shopper. A plant with unknown dimensions cannot be placed by the default layout engine; unknown facts cannot satisfy a requested condition.

A cart change fails

Reload current availability and check minimum quantities and quantity steps. In the adapter, return the design’s applied lines and set success only when all quantities were applied. Check that retries find the previously saved result.

HTTP responses
StatusCheck
401Shopper-session middleware.
403Store origin, JSON content type or callback signature.
409Current stock, selected quantities or a partial cart result.
429Request limits; wait before retrying.
503Server logs and the connected service.

Get help

Email glasshouse@superseeded.ai with your store URL, integration type and the steps that reproduce the issue. Include the failed route and HTTP status if available. Keep credentials and shopper information out of the report.

Tab to a result, then press Enter to open it.