Skip to main content

Integrations

Integration patterns for product data.

With Youzu, you do not need a pre-built connector: send products as real-time JSON or a hosted CSV, JSON or XML file, or call the API. Hosted CSV, JSON or XML files, JSON through the API, dashboard upload and web components are available now, the Merchant API is available on request, and Shopify and WooCommerce connectors are in progress.

Start with the data path you can verify.

What we confirm first

  1. Where the product record lives today.
  2. Which destination has to accept the decision.
  3. Who owns review and which rules apply.
  4. What happens to a record we cannot resolve.

A platform is listed as available only when its route is documented and verified.

Find your route

How your data gets in, and where results go.

2 choices compose one route. Availability follows the bands below.

Where does your product data live?

Where should results go?

Your data

Hosted file import or dashboard upload

Available: documented and usable today; plan, quota and tenant enablement can still apply

Give Youzu a public URL to a CSV, JSON or XML file, or upload a file in the dashboard. Products are processed in the background; each shows its processing status.

Your results

Back into my systems

Read processed products, variants, offers, moderation state and processing status through the API with filters. Applying results to a destination is scoped per integration, with a field map and a review gate agreed first.

What your team does: Tracks submitted products and reads results through the API.

Read as text

Where does your product data live?

  • Files (CSV, JSON or XML). Hosted file import or dashboard upload: Available Give Youzu a public URL to a CSV, JSON or XML file, or upload a file in the dashboard. Products are processed in the background; each shows its processing status.
  • A system that can call an API. JSON through the API: Available Send products as JSON, up to 5 MiB per request, and send a changed product again at any time with the same SKU.
  • A PIM or ERP. File or API export from your PIM or ERP: Available Export a file or send records through the API. No pre-built PIM or ERP connector is listed; your PIM and ERP stay authoritative for their own data.
  • A seller listing form. Merchant API from your server: On request Your server sends the seller's draft and receives suggestions, image-check findings and mismatch warnings. Access depends on your plan, a ready catalog and a monthly request quota.
  • A Shopify, WooCommerce or commercetools store. File or API today; connectors: In progress The WooCommerce plugin, the Shopify integration and the commercetools integration are in progress. Today you integrate by API or file.

Where should results go?

  • Back into my systems. Read processed products, variants, offers, moderation state and processing status through the API with filters. Applying results to a destination is scoped per integration, with a field map and a review gate agreed first.
  • Into my listing form. Your application shows the suggestions and decides what to apply. Merchant calls never create, update or publish products.
  • Onto my storefront. Web components load from a script tag, or your server calls the feature APIs for photo search, Swap, Magic Background and 2D to 3D. Your storefront owns navigation, availability and the next shopper action.

From your data, through Youzu, to your systems.

How product data gets in, what handles it, and where the results stay yours.

Choose a part of the map to highlight its path; arrow keys move between parts.

Ways in

You do not need a pre-built connector: send files or call the API.

Youzu

Your systems

The map as text

  1. Ways in

    1. JSON through the API. Product data can be sent as real-time JSON (up to 5 MiB per request).
    2. Files or an upload. Product data can be sent as a hosted CSV, JSON or XML file URL, or uploaded manually in the dashboard.
  2. Youzu

    1. REST API. A documented REST API (v1 and v2) with an API reference and an OpenAPI description.
    2. Web components. Web components (search lens, Lens, Swap, Magic Background, 3D lens) load from a script tag.
  3. Your systems

    1. PIM, ERP, search, storefront. Youzu works alongside your existing PIM, ERP, search and storefront; those systems stay authoritative for their own data.
    2. Replace or keep your PIM. Youzu can replace your PIM: products, variants and seller offers live in Youzu as structured, reviewable records, or Youzu works alongside the PIM you keep.
    3. Your server. Keep the API key on your server; browser and feature calls use short-lived (5-minute) single-use tokens.
Read as text

3 columns: the ways product data gets in, the parts of Youzu, and your systems. Choosing a part highlights the parts it connects to; the list under the map gives each part's note.

See it with your products

What is available

Availability by status.

Today you integrate by API or file. Ask us about an integration.

Ask about an integration

Input, output, your system

What moves in each path.

Integration paths: what you send, what Youzu returns and what your system does
PathYou sendYouzu returnsYour system doesIf something fails
Hosted file importA public URL to a CSV, JSON or XML file (the file must be reachable at that URL)An accepted request, then per-product processing status and processed recordsTracks submitted products and reads results through the APIInspect each product's status; re-send changed records.
JSON through the APIProducts as JSON, up to 5 MiB per requestThe sameSends changes again with the same SKURe-send the failed request; accepted is not finished.
Dashboard uploadA file uploaded by an operatorProcessed records in the dashboard and through the APIOperators review; your systems read results through the APIUpload a corrected file.
Merchant APIThe seller's draft (name, brand, images, category if known) from your serverSuggestions, image-check findings and mismatch warningsShows the suggestions, lets the seller choose, saves and publishesKeep the seller's edits, say in the form what is missing and let the seller continue.
Feature APIs and web componentsA shopper's image, a room photo or a product photoMatches, a room photo with a swapped item, a new background or a 3D modelYour storefront owns navigation and the next shopper actionKeep the shopper's image and a link to the product; offer a retry; request a new token for each protected call.

Agreed per engagement

Scoped with you.

Each is written down with you before it starts.

  • Later batches and changed products.

    Send the next file URL or re-send changed records at any time; the same SKU identifies a later version of an offer.

  • Scheduled batches with review routing.

    Agreed per engagement: review rules, a named reviewer and what happens to a record that cannot be resolved are written down first.

  • Applying results to a destination.

    Agreed per engagement, with a named destination, a field map and a review gate. Prepared records are available through the API either way.

Implementation sequence

Verified route, then scope, then data.

Step 1 of 4

Source, destination, transport and volume band are written down before any record moves.

Step 2 of 4

Review rules, review owners and what counts as an accepted result are set by your team.

Step 3 of 4

A representative slice of difficult records, inspectable end to end.

Step 4 of 4

Evaluations expand to more workflows once the results are reviewed.

Questions buyers ask

No. You can send hosted CSV, JSON or XML files, upload a file in the dashboard, or send JSON through the API, and you can read processed products back through the API. A connector for a specific platform would be a convenience, not a requirement.

Youzu can replace your PIM, not your ERP. Products, variants and seller offers live in Youzu as structured, reviewable records, so you can run your catalog there instead of in a separate PIM, or keep your PIM and run Youzu alongside it. Your ERP, search and storefront stay authoritative for their own data, and processed records can be read back through the API. You do not need a pre-built connector: you send files or call the API.

Not yet. A WooCommerce plugin and a Shopify integration are in progress. Today you integrate by API or file, which works without a connector. Each entry on this page that is not yet available has a Notify me link that opens the contact form with that platform prefilled.

Ingestion is asynchronous: an accepted request does not mean enrichment, indexing or deduplication has finished. Each product shows its processing status, and you read that status through the API. Poll product processing status through the API to see when a product is ready.

Prepared records are available through the API, and your application decides what to apply. Applying results to a destination is scoped per integration, with a field map and a review gate agreed first. Merchant API calls never create, update or publish products.

Not listed? Tell us the system you use.

You do not need a pre-built connector: send files or call the API.

Discuss your catalog

Next step

See it with your products.

Bring a sample of your catalog, your listing flow or your shopping idea. We will show you what the results look like on your data.