Hosted link, embedded widget or API: an integration guide

1. Choose the smallest scope that answers your question

A hosted journey is useful when you want to test interest in the service first. A widget suits an experience inside the store page. Choose an API when your own interface and shopping logic justify engineering work.

2. Prepare your catalogue at variant level

A product name is insufficient when a lipstick comes in many shades. Supply product and variant IDs, category, shade name, color description, image, product URL, market and availability. Color samples need review: a marketing photograph or HEX value does not guarantee an accurate representation.

• Example fields: product_id, variant_id, category, shade_name, image_url, product_url, market, available.
• Agree who approves mappings and how often availability is refreshed.
• Define behavior for discontinued variants and empty recommendation lists.

3. Review technical requirements and data handling

For a widget, check Content Security Policy, embedding restrictions and camera permissions on mobile devices. For an API, plan server authentication, limits, retries and error handling. Before a shopper submits a photo, explain its purpose and deletion process.

4. Define acceptance and measurement

Test successful analysis, poor photos, unavailable cameras, slow networks and no suitable products. The store owner approves placement, catalogue mapping and the shopping handoff. The delivery team documents operation, limitations and how to disable the pilot.