TryHair for WooCommerce

WooCommerce · independent cloud integration

Install, connect and enable.

TryHair runs as a WooCommerce connector plus an authenticated cloud image service. Internet access is required.

The current ZIP is a development review build, not a Marketplace-approved release. Install on staging first. Paid purchases remain disabled.

1. Check the environment

The plugin declares WordPress 6.5+, PHP 7.4+ and WooCommerce as a dependency. The recorded compatibility run used WordPress 7.1.3, WooCommerce 11.2.1 and PHP 8.3. Full supported-version certification and QIT review remain pending. Use supported, security-maintained PHP on your host.

A publicly reachable HTTPS WordPress site is required for self-service verification. Localhost cannot receive a new anonymous Free allowance. Ensure outbound HTTPS access and that the fixed WordPress connection-proof REST route can be reached by our service.

2. Install the connector

  1. Download the 0.7.4 review ZIP.
  2. In WordPress, open Plugins → Add New Plugin → Upload Plugin.
  3. Install and activate it with WooCommerce active.
  4. Open WooCommerce → TryHair and review the connection disclosure.
  5. Click Connect TryHair. The plugin verifies site control and stores service credentials on the server; you do not need an AI API key.

3. Enable a product

  1. Edit a published wig product in WooCommerce.
  2. Enable TryHair in the product settings and save.
  3. Use a clear supported image of the wig. For variations, assign an independent image when available; otherwise the main product image is used.
  4. Open the storefront product page and check the Try On dialog.

4. Test with authorized sample images

Choose a clear front-facing photo with one visible face, and a suitable wig image. Generate once and verify the result and download control. Tests that genuinely generate an image consume successful allowance; refreshing the dashboard does not.

5. Understand the usage dashboard

Disconnecting or moving a store

Disconnect store revokes its service connection and preserves the allowance identity and usage history. Disabling or removing the plugin stops its storefront integration; it is not an automatic request to delete anti-abuse or accounting records. Contact support before moving domains or cloning an installation.

Compatibility boundaries

Development checks covered classic galleries on Storefront and Twenty Twenty-Five, native product gallery/add-to-cart blocks, simple and variation products, and narrow browser viewports. Other commercial themes, gallery extensions, real-device Safari/Android behavior and a full QIT matrix still need review.

Troubleshooting and contact →