SeeOnWall for WooCommerce

SeeOnWall adds a “See on your wall” button to your poster/art product pages. Shoppers take (or upload) a photo of their own wall, or pick a stock room scene, and instantly see the poster placed at true physical scale — reducing purchase hesitation and returns.

Requires WooCommerce (8.0+) to be installed and active — SeeOnWall is a WooCommerce extension, not a standalone plugin.

How it works

1. Install and activate SeeOnWall.
2. Go to WooCommerce → SeeOnWall and click Connect to SeeOnWall. No account signup, no API key to copy — the plugin proves it controls your store’s domain and a free account is provisioned automatically.
3. A “See on your wall” button appears on your product pages automatically, sized from your product’s Dimensions (WooCommerce → Product data → Shipping).
4. Upgrade to a paid plan any time from the SeeOnWall settings page for higher usage limits, session sharing, and white-labelling — billed by SeeOnWall directly (Polar.sh), not through WooCommerce.

External service: SeeOnWall

This plugin is the client for SeeOnWall, a hosted software-as-a-service that renders the wall previews. The plugin does not do the visualization itself — it connects your store to the SeeOnWall service at https://seeonwall.com and loads the service’s viewer on your product pages. It is not usable without this service, which is operated by the plugin author.

What is sent, and when:

• On connect / reconnect (one-time, triggered by you clicking Connect): your store’s URL and the connecting WordPress admin’s email address. In return the plugin receives a store token used to authenticate later requests. The admin email is used only for account notifications (e.g. usage-limit alerts) and billing — it is never shown to shoppers or used for marketing.
• On product pages (for connected stores): a small JavaScript viewer is loaded from https://seeonwall.com/seeonwall.js, and the product’s image URL and physical dimensions are passed to it so the shopper can preview the poster. This is loaded from SeeOnWall (not bundled) because the preview is a live hosted service, kept current server-side.
• The plugin itself sends no shopper data. It only injects the button and passes the product image URL and dimensions. Shoppers, however, interact directly with the SeeOnWall service once they open the preview — see below.

What SeeOnWall does with shopper data (not the plugin, but the service it loads):

• A shopper who picks a room-scene template uploads nothing at all. No photo is created.
• A shopper who uploads or takes a photo of their own wall has that photo stored in an EU Cloudflare R2 bucket and analysed by Google Vertex AI (via Google’s EU Data Boundary endpoint, pinned to europe-west1) to detect the wall corners. The photo stays inside the EU for its whole lifetime, is never used to train models, and is deleted automatically when the session expires after 7 days.
• Shoppers never create an account. Cloudflare Turnstile is used for bot protection on upload.
• A notice stating the above is shown to the shopper inside the viewer, before they upload.

Service terms, privacy policy and sub-processors:

• Terms of Use: https://seeonwall.com/terms
• Privacy Policy: https://seeonwall.com/privacy
• Sub-processor list: https://seeonwall.com/subprocessors

Reporting illegal content

If content hosted by SeeOnWall is unlawful — for example a poster image used without the rights holder’s permission — you can report it to abuse@seeonwall.com. The notice-and-action procedure under Article 16 of the EU Digital Services Act, including what a notice must contain and how it is handled, is described at https://seeonwall.com/report

Source Code

The admin settings page is a small React + TypeScript app. The plugin ships only its compiled, minified output (assets/js/settings.js, assets/css/settings.css). The complete, human-readable source those files are built from is included in this plugin under the src/ directory, together with build instructions (src/README.md). Build tooling: Node.js + Vite (npm install && npm run build). React and ReactDOM are not bundled — they resolve at runtime to the copies WordPress ships (the react / react-dom script handles).