Sync the catalog

virtual.fit resolves storefront products from your synced catalog. Use the management API for continuous server-to-server sync. Use CSV for scheduled or manual imports.

The current contract is schema version 2. Omit schema_version for all new integrations. Send schema_version: 1 only from an existing image-only integration that needs legacy update behavior.

Send management API requests to https://api.virtual.fit.

Choose a sync method

Management API
CSV

Push changes as they happen. This is the best option when your backend knows the current variants, prices, or inventory.

curl --request PUT \
  "https://api.virtual.fit/vfr/manage/sites/$SITE_ID/products/$PRODUCT_ID" \
  --header "Authorization: Bearer $VIRTUAL_FIT_API_KEY" \
  --header "Content-Type: application/json" \
  --data @product.json

Keep the API key on your server. Never include it in storefront JavaScript.

Import a file where each row describes a product-level update or one exact variant. Repeat product_id for each additional variant.

product_id,title,product_image_url,variants_complete,variant_id,option_values_json,variant_available,inventory_quantity,variant_price,currency
dress-10042,Floral Midi Dress,https://cdn.example.com/floral-front.jpg,true,floral-petite-2,"{""color"":""Floral"",""fit"":""Petite"",""size"":""2""}",true,4,79.00,USD

Omitted schema_version also means version 2 in CSV.

Find your site ID

In virtual.fit, open Custom JS → Sync Products and copy the Storefront Site ID from the Storefront Credentials section. The site ID is a UUID used in the site_id path parameter. It is different from the public site key, your workspace ID, and any ID from your commerce platform. For server-side discovery, call the current-site endpoint with your API key and store the returned site.id value for later requests:

curl --request GET \
  "https://api.virtual.fit/vfr/manage/sites/current" \
  --header "Authorization: Bearer $VIRTUAL_FIT_API_KEY"

Start with the smallest useful product

You can send the title and image first. Add variants, stock, prices, options, and size charts later under the same product ID.

{
  "title": "Floral Midi Dress",
  "images": [
    {
      "url": "https://cdn.example.com/floral-front.jpg"
    }
  ]
}

For a new product, include:

A stable product ID in the request URL or product_id CSV column.
title.
At least one public product image.

Omitted fields stay unchanged on later updates. This lets a feed publish the essentials quickly and enrich the product progressively.

Choose a durable product ID

product_id is the permanent identity of the product inside one site. It is case-sensitive and can be a numeric ID, UUID, or URL-safe string.

Prefer an immutable catalog or database ID.
Keep one ID for the product when prices, images, options, or variants change.
Do not derive it from the title, URL, handle, or current variant combination.
Keep it within 255 UTF-8 bytes and URL-encode it in API paths.

A product can begin without variants and gain them later under the same product_id. This does not create a second product or require a migration.

Send products with variants

A product holds shared merchandising data. A variant holds one exact purchasable combination, such as Floral / Petite / 2.

{
  "title": "Floral Midi Dress",
  "handle": "floral-midi-dress",
  "canonical_url": "https://shop.example/products/floral-midi-dress",
  "brand": "Example Fashion",
  "price": {
    "amount": "79.00",
    "currency": "USD"
  },
  "compare_at_price": {
    "amount": "99.00",
    "currency": "USD"
  },
  "images": [
    {
      "external_media_id": "floral-front",
      "url": "https://cdn.example.com/floral-front.jpg",
      "position": 0
    }
  ],
  "options": [
    {
      "key": "color",
      "source_name": "Colour",
      "kind": "visual",
      "presentation_role": "include",
      "position": 0,
      "values": [
        {
          "source_value": "Floral",
          "display_label": "Floral",
          "swatch": {
            "image_url": "https://cdn.example.com/floral-swatch.jpg"
          }
        }
      ]
    },
    {
      "key": "fit",
      "source_name": "Fit",
      "kind": "fit",
      "presentation_role": "exclude",
      "position": 1,
      "values": [
        {
          "source_value": "Petite",
          "display_label": "Petite"
        }
      ]
    },
    {
      "key": "size",
      "source_name": "US Size",
      "kind": "size",
      "presentation_role": "exclude",
      "size_system_code": "us",
      "size_audience_code": "womens",
      "size_category_code": "apparel",
      "position": 2,
      "values": [
        {
          "source_value": "2",
          "display_label": "2"
        }
      ]
    }
  ],
  "variants_complete": true,
  "variants": [
    {
      "source_variant_id": "floral-petite-2",
      "title": "Floral / Petite / 2",
      "sku": "FLORAL-P-2",
      "canonical_url": "https://shop.example/products/floral-midi-dress?variant=floral-petite-2",
      "option_values": {
        "color": "Floral",
        "fit": "Petite",
        "size": "2"
      },
      "available": true,
      "inventory_quantity": 4,
      "inventory_observed_at": "2026-07-25T10:00:00Z",
      "price": {
        "amount": "79.00",
        "currency": "USD"
      },
      "compare_at_price": {
        "amount": "99.00",
        "currency": "USD"
      },
      "media": [
        {
          "external_media_id": "floral-front"
        }
      ]
    }
  ],
  "size_charts": [
    {
      "external_id": "womens-petite",
      "url": "https://shop.example/pages/womens-petite-size-chart",
      "applies_to": {
        "fit": "Petite"
      },
      "size_system_code": "us",
      "size_audience_code": "womens",
      "size_category_code": "apparel"
    }
  ],
  "enabled": true
}

Send only combinations that shoppers can actually select. Option values describe available choices; they do not create a Cartesian product of variants.

Send stock updates

Use the same product upsert endpoint when stock changes. For an existing product, send only the changed variants. You do not need to resend the title, images, prices, or unchanged variants.

Exact variants
Products without variants

Identify each variant by the same source_variant_id used during the initial sync.

curl --request PUT \
  "https://api.virtual.fit/vfr/manage/sites/$SITE_ID/products/dress-10042" \
  --header "Authorization: Bearer $VIRTUAL_FIT_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "variants": [
      {
        "source_variant_id": "floral-petite-2",
        "available": false,
        "inventory_quantity": 0,
        "inventory_observed_at": "2026-08-01T09:30:00Z"
      }
    ]
  }'

Send product-level available when your source has no exact variants. A product-level update cannot include an inventory quantity.

curl --request PUT \
  "https://api.virtual.fit/vfr/manage/sites/$SITE_ID/products/dress-10042" \
  --header "Authorization: Bearer $VIRTUAL_FIT_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{
    "available": false
  }'

If the product gains variants later, send stock on each exact variant. Variant availability takes precedence over product-level availability.

For exact variants:

Send available: true when the variant can be purchased and false when it is sold out.
Send inventory_quantity when your source provides an exact count. Quantity alone does not set available.
Send inventory_observed_at as the RFC 3339 time when your source reported the stock. If you omit it, virtual.fit uses the request time.
Keep the timestamp from the source. An older observation does not replace newer stock for the same variant.
Omit variants_complete from a targeted stock update. Set it to true only when the request contains the complete authoritative variant list.
Refresh stock regularly. virtual.fit treats stale inventory as unknown instead of claiming that a variant is in stock.

enabled controls whether the product can use the fitting room. It is not a stock field. Keep enabled unchanged when only inventory changes. For an existing product, omitting it from an upsert preserves the current state; use the dedicated enable-state endpoint when changing availability by itself.

Field reference

Fields are ordered by how commonly a new integration needs them. Auto-detected when omitted means virtual.fit derives the value from the supplied variants, option names, swatches, or media.

Product fields

string

required

Stable product ID in the request URL. Keep it unchanged when variants, prices, inventory, or media change.

string

required

Shopper-facing product name. Required when creating a product.

object[]

required

Shared product media. A new product needs at least one public image. See the image object reference.

Show image fields

string

required

Public HTTP or HTTPS image URL.

string

Stable media ID from your source. Use it to reference this image from variant media.

string

Source alt text.

string

Source-defined role. Prefer front, back, or side for those views. featured, primary, and gallery are also accepted.

number

default:"0"

Zero-based display order.

number

Optional source width in pixels.

number

Optional source height in pixels.

string

Required for most Custom JavaScript storefronts. Send the stable storefront slug when the site resolves product URLs by handle. You may omit it only when URL resolution uses product_id.

string

Public canonical product URL. Must use HTTP or HTTPS.

boolean

default:"true"

Whether the product is enabled in the fitting room. This is separate from upstream sale availability.

boolean

Current source-reported sale availability when it is known. Omit or send null when unknown. Usually derived from exact variants or synced from the source; variant availability is more precise when variants exist.

number

Current overall customer rating on a 0–5 scale. Omit when the source does not expose an aggregate rating.

number

Number of customer reviews included in the current overall rating. Must be zero or greater.

object

Product-level selling price. A variant price overrides it for that variant. Expand for the exact object shape.

Show money fields

string

required

Decimal amount as a string, such as "79.00".

string

required

Three-letter ISO 4217 currency code, such as USD or EUR.

object

Product-level original or pre-sale price. Uses the same amount and currency shape as price.

object[]

Exact purchasable combinations. An empty array is valid. Expand for variant identity, selections, inventory, pricing, and media fields, or open the variant object reference.

Show variant fields

string

Stable source ID for this exact combination. Required unless option_values uniquely identifies the variant.

string

Shopper-facing variant label, such as Floral / Petite / 2.

string

Merchant SKU.

string

Public URL that opens this exact variant. When omitted, recommendations use the product canonical_url.

object

Exact option key-to-value selection, for example {"color":"Floral","fit":"Petite","size":"2"}. Keys and values must match declared options when options is supplied.

boolean

Whether this exact variant can currently be purchased. Omit or send null when unknown.

number

Known inventory quantity. Omit when the source does not expose it.

string

RFC 3339 timestamp for the inventory observation.

string

Unmodified inventory policy from the source system.

string

Stable source inventory-item ID.

object

Variant selling price. Uses amount as a decimal string and currency as a three-letter ISO 4217 code.

object

Variant original or pre-sale price. Uses the same shape as variants[].price.

string

Public primary image for this variant.

object[]

Variant-specific media. Reference a shared image by external_media_id, or provide a public url.

Show variant media fields

string

ID of an item in product images.

string

Public HTTP or HTTPS URL when the media is not already in product images.

string

Source-defined role such as primary, front, or back.

number

default:"0"

Zero-based display order.

boolean

default:"false"

When true, the supplied variant list is authoritative. Omitted variants become inactive. Send true with variants: [] for a genuinely variantless product.

object[]

Choice axes, labels, swatches, and size metadata. Auto-detected when omitted: virtual.fit derives the minimum option structure from variants[].option_values. Send options when you have source labels, ordering, swatches, or explicit size metadata. See the option object reference.

Show option and swatch fields

string

required

Stable machine key such as color, fit, or size. Variant option_values must use the same key.

string

Merchant label such as Colour or US Size. Auto-detected when omitted: defaults to key.

string

Auto-detected when omitted. Accepted values:

visual — color, pattern, print, wash, or finish.
style — another choice that changes the visible garment shape or design.
size — numeric, alpha, or shoe size.
fit — petite, regular, tall, body type, or fit family.
length — length or inseam.
width — footwear or garment width.
other — a source-specific choice that does not match the above.

string

default:"auto"

Accepted values:

auto — infer visual identity from the option kind, swatches, and variant media.
include — always treat the option as changing the visible product.
exclude — never split visual identity on this option.

number

default:"0"

Option display order.

string

Normalized system for a sizing option. Use one of:

Geographic systems: us, eu, uk, au, jp, cn, kr.
International letters: intl_alpha.
Measurements: inch, cm, mondopoint.
Special cases: brand_specific, one_size, unknown.

string

Who the sizing is designed for. Use womens, mens, unisex, kids, youth, baby, or unknown.

string

What kind of sizing the values describe. Use apparel, footwear, denim, bra, hosiery, accessories, or unknown.

string

Original source label when it does not map cleanly to a normalized size system.

object[]

required

Declared values for this option.

string

required

Exact value used by variant option_values.

string

Shopper-facing label. Auto-detected when omitted: defaults to source_value.

string

Optional normalized value when the source value is unusual.

number

default:"0"

Value display order.

object

Optional color, multi-color, or image swatch. Image swatches support patterns and textures.

Show swatch fields

string

Primary CSS color value.

string[]

Ordered CSS color values for a multi-color swatch.

string

Public HTTP or HTTPS swatch image for a pattern or texture.

string

Optional source CSS value when a color or image is insufficient.

string

Accessible swatch label. Defaults to the option value label.

object[]

Product-wide or option-scoped size chart references. Stored now for future size-aware recommendations; they do not change today’s visual recommendation ranking. See the size-chart reference.

Show size chart fields

string

Stable chart ID from the source.

string

Public HTTP or HTTPS size chart page or asset. A URL alone is valid and allows a later enrichment step to add structured data.

object

Optional structured chart data when the source already provides it.

object

Option key-to-value selector, for example {"fit":"Petite"}. Omit when the chart applies to the whole product.

string

BCP 47 locale such as en-US or de-DE.

string

Normalized size system. Uses the same accepted values as options[].size_system_code.

string

Sizing audience. Uses the same accepted values as options[].size_audience_code.

string

Sizing category. Uses the same accepted values as options[].size_category_code.

object[]

Optional measured garment dimensions by size. Use canonical dimension names such as bust, chest, waist, hips, shoulder_width, sleeve_length, total_length, inseam, front_rise, back_rise, thigh, or leg_opening. Use cm or in.

Show garment measurement fields

string

required

Canonical dimension name.

number

required

Non-negative measured value.

string

required

cm or in. virtual.fit normalizes length internally.

string

Source size this measurement describes, such as Petite / 4.

string

Short source label such as merchant.

number

Optional confidence from 0 to 1.

object[]

Optional product-page model or mannequin fit facts. Send the worn size and any source-reported body measurements. These fields can improve future size recommendations and remain optional.

string

Brand or designer name.

string

Merchant-facing product type. Usually populated automatically when the source exposes it.

string

Optional plain-text product description. Useful enrichment, but not required for fitting-room product matching.

string

Optional product-specific try-on guidance.

string

Optional concise garment naming override used to describe the item during try-on. Auto-detected when omitted.

boolean

Whether the product still exists and is active in the source catalog. Send false for archived or removed products.

string

Optional unmodified status from the source system, such as ACTIVE, ARCHIVED, or DRAFT. It is preserved for diagnostics and is not a normalized enum.

string

RFC 3339 timestamp for the source record. Usually populated automatically.

number

default:"2"

Omit for the current contract. The only accepted explicit values are 1 for a legacy image-only request and 2 for the current contract.

object

Optional ordering and idempotency metadata for multi-worker progressive syncs.

Show progressive ingest fields

Use ingest only when several workers may update one product or events may arrive out of order.

string

required

Unique event ID. Reusing it with a different payload is rejected.

string

required

ID shared by events from one sync run.

number

required

Positive sequence number within the run.

string

required

Stable name for the worker or feed.

string

required

RFC 3339 time when the source was observed.

string[]

Fields represented by this event.

string[]

Collections complete in this event. Accepted values are images, options, variants, and size_charts. A completed variants collection also requires variants_complete: true.

Variant and media behavior

A product may have no variants. Send variants_complete: true with variants: [].
If variants appear later, keep the same product ID and send the new variant list.
Size-only variants normally share product media.
Color, pattern, material, and style variants can reference distinct media.
Shared media is stored and prepared once even when several variants reference it.
A swatch image represents the selector. Variant media represents the garment used for display and try-on.

virtual.fit recommends at most one result per product. A result may identify the best exact variant or the best visual choice within the product. When fresh inventory is known, exact variant results must be available. When availability is unknown, virtual.fit does not claim that a variant is in stock.

Visual choices

You do not create presentation IDs. virtual.fit derives visual choices from option meaning, swatches, and variant media. Use:

presentation_role: "include" when an option changes the visible garment.
presentation_role: "exclude" for size, fit, length, and other non-visual choices.
presentation_role: "auto" when virtual.fit should infer the behavior.

If variant media clearly changes with an option such as color, virtual.fit can infer that the option is visual. Explicit roles remain useful when source media is incomplete or ambiguous.

Size charts

Use one chart without applies_to when it applies to every variant. Use a selector when petite, regular, tall, or another option value uses a different chart. A chart may contain:

A public url.
Extracted structured content.
Both a URL and structured content.

If you omit size metadata, virtual.fit preserves the source size values but does not guess their geographic system, audience, or category. These three fields are independent: for example, us + womens + footwear is different from us + youth + footwear. Petite, regular, and tall remain option values such as fit, and applies_to selects the chart for each fit. Reusing the same chart URL or stable external_id across products allows virtual.fit to share the stored chart document while keeping each product’s applies_to selector.

Optional review evidence

You do not need to send reviews. virtual.fit can collect public review evidence when it prepares a product. If your backend already receives complete review records, you can sync them after creating the product. The optional review endpoint accepts each review’s stars, full text, purchased variant, customer photos or videos, and source-reported measurements or fit votes. virtual.fit analyzes review text asynchronously, so review enrichment never blocks the product from becoming ready. Use a stable source review ID whenever one exists. Send each review as its complete current record so removing media or structured evidence is unambiguous. See Sync product reviews. The storefront can request the compact fit summary for fast product display and load full paginated reviews only when the shopper asks to inspect the evidence.

Partial updates and clearing data

For an existing product:

An omitted field stays unchanged.
An explicit null clears a supported field or collection.
variants_complete: true makes the supplied variant list authoritative.
A plain partial variant update does not remove omitted variants.

You may clear handle, preview_image_url, brand, description, product_type, prices, availability, rating, review count, custom instructions, images, options, variants, size charts, garment measurements, or model observations.

{
  "description": null,
  "size_charts": null,
  "garment_measurements": null
}

Clearing options removes your supplied labels and swatches. If active variants remain, virtual.fit retains the minimum option structure required to describe them.

Order updates from multiple workers

Add ingest metadata when several workers may update one product or when events may arrive out of order. The event and sequence fields make the complete update idempotent and ordered.

{
  "variants": [
    {
      "source_variant_id": "floral-petite-2",
      "available": false,
      "inventory_quantity": 0,
      "inventory_observed_at": "2026-07-25T11:00:00Z"
    }
  ],
  "ingest": {
    "event_id": "inventory-4281",
    "run_id": "catalog-sync-2026-07-25",
    "sequence": 12,
    "producer": "inventory-sync",
    "observed_at": "2026-07-25T11:00:00Z",
    "observed_fields": ["variants"]
  }
}

Delete catalog data

Use DELETE when the product should be removed from the synced catalog. This permanently removes the synced product record and its managed product images:

curl --request DELETE \
  "https://api.virtual.fit/vfr/manage/sites/$SITE_ID/products/dress-10042" \
  --header "Authorization: Bearer $VIRTUAL_FIT_API_KEY"

The canonical catalog retains a deletion tombstone so a stale source snapshot cannot serve the product again. Syncing the same product ID later creates it again and clears the tombstone.

Use the enable-state endpoint when you only want to hide a product temporarily or preserve its diagnostic history. Deletion removes the synced record and managed images.

To keep the product and its images while removing it from the fitting room, set its enabled state:

curl --request PUT \
  "https://api.virtual.fit/vfr/manage/sites/$SITE_ID/products/dress-10042/enabled" \
  --header "Authorization: Bearer $VIRTUAL_FIT_API_KEY" \
  --header "Content-Type: application/json" \
  --data '{"enabled":false}'

Send {"enabled":true} to re-enable it. Disabled products remain in the product count, but do not consume enabled-product slots. Delete one variant:

curl --request DELETE \
  "https://api.virtual.fit/vfr/manage/sites/$SITE_ID/products/dress-10042/variants/floral-petite-2" \
  --header "Authorization: Bearer $VIRTUAL_FIT_API_KEY"

The variant path accepts the stable source variant ID used during sync.

CSV format

Each CSV upload is a synchronous import of at most 1,000 rows. Split larger catalogs into multiple files. Product and variant upserts are idempotent, so it is safe to retry a file; if an infrastructure failure occurs after processing starts, rows already saved remain saved.

Current contract
Delete rows
Legacy v1

Omit schema_version; version 2 is the default. Repeat the product ID on each variant row. Blank product-level cells on later rows inherit the first row for that product.

product_id,title,handle,canonical_url,product_image_url,rating,review_count,options_json,variants_complete,variant_id,variant_canonical_url,option_values_json,variant_image_url,variant_available,inventory_quantity,inventory_observed_at,variant_price,variant_compare_at_price,currency,size_chart_url
dress-10042,Floral Midi Dress,floral-midi-dress,https://shop.example/products/floral-midi-dress,https://cdn.example.com/floral-front.jpg,4.7,128,"[{""key"":""color"",""source_name"":""Colour"",""kind"":""visual"",""presentation_role"":""include"",""values"":[{""source_value"":""Floral"",""display_label"":""Floral"",""swatch"":{""image_url"":""https://cdn.example.com/floral-swatch.jpg""}}]}]",true,floral-petite-2,https://shop.example/products/floral-midi-dress?variant=floral-petite-2,"{""color"":""Floral"",""fit"":""Petite"",""size"":""2""}",https://cdn.example.com/floral-front.jpg,true,4,2026-07-25T10:00:00Z,79.00,99.00,USD,https://shop.example/pages/size-chart

Include operation.

operation=delete with an empty variant_id deletes the product.
operation=delete with product_id and variant_id deletes that variant.

operation,product_id,variant_id,title,product_image_url
delete,dress-10042,floral-petite-2,,

Existing image-only importers can set schema_version to 1. Version 1 supports product identity, titles, handles, enabled state, preview images, prompt fields, and product image URLs.

schema_version,product_id,title,handle,product_image_url,enabled
1,dress-10042,Floral Midi Dress,floral-midi-dress,https://cdn.example.com/floral-front.jpg,true

Version 1 does not accept variants, options, prices, inventory, size charts, or delete rows. If those fields are present, the import explains which fields require the current contract.

Legacy JSON compatibility

Use an explicit legacy version only while an existing image-only integration is being migrated:

{
  "schema_version": 1,
  "title": "Floral Midi Dress",
  "handle": "floral-midi-dress",
  "product_image_url": "https://cdn.example.com/floral-front.jpg",
  "enabled": true
}

Do not add current fields to a version 1 request. If virtual.fit detects fields such as options, variants, prices, inventory, or size charts, it returns a message that lists the incompatible fields and tells you to omit schema_version.

Image requirements

Image URLs must be reachable without shopper cookies, expiring browser sessions, or IP-bound authorization. Use stable HTTPS CDN URLs and clear, high-resolution JPEG, PNG, or WebP images up to 64 MB. Avoid short-lived signed URLs unless they remain available during preparation and later refreshes. Prefer images that show the complete sold product on a model or mannequin. When available, send front, back, and side views. These views provide a more useful fit reference than a flat lay or isolated ghost image and generally produce more accurate try-on results. Flat-lay, ghost, and product-only images are still accepted. virtual.fit automatically analyzes, deduplicates, and selects the strongest prepared views without modifying the originals. When a photo contains several garments, also include a view where the sold item is unambiguous.

Input limits

Limits are intentionally generous enough for large catalogs while preventing a single malformed request from consuming unbounded memory or database space. Limits apply equally to JSON and CSV values.

Input	Limit
JSON product body	4 MiB
CSV file	32 MiB and 1,000 rows per synchronous import
Product IDs, handles, variant IDs, SKUs, labels	255 UTF-8 bytes each
Product title	500 UTF-8 bytes
Description	64 KiB
Custom instructions	4 KiB
URL	8 KiB
Images per product	500
Options per product	20
Values per option	1,000
Variants per product	5,000
Media references per variant	100
Size-chart references per product	50
Structured size-chart content	256 KiB each
Garment measurements per product	250
Model observations per product	50

A request that exceeds a byte or collection limit returns 413 with the field that must be reduced. Invalid values within the limits return 400.

Common sync failures

Failure	Fix
Missing values on a new product	Include a title and at least one product image.
A version 1 request contains current fields	Remove `schema_version` to use the current contract, or remove the listed unsupported fields.
Image preparation never completes	Confirm the URL is public, stable, no larger than 64 MB, and returns an image content type.
A variant is rejected	Declare matching option keys and values, or send the variant without conflicting option definitions.
A variant disappears unexpectedly	Use `variants_complete: true` only when the supplied list is authoritative.
URL matching finds no product	Keep the product ID and handle aligned with your configured URL resolution.

Never call the management API from browser JavaScript. Its API key can modify catalog data and must remain server-side.

Get started

Shopify

Custom JavaScript

Recommendations

Operate

API reference

Choose a sync method

Find your site ID

Start with the smallest useful product

Choose a durable product ID

Send products with variants

Send stock updates

Field reference

Variant and media behavior

Visual choices

Size charts

Optional review evidence

Partial updates and clearing data

Order updates from multiple workers

Delete catalog data

CSV format

Legacy JSON compatibility

Image requirements

Input limits

Common sync failures

​Choose a sync method

​Find your site ID

​Start with the smallest useful product

​Choose a durable product ID

​Send products with variants

​Send stock updates

​Field reference

​Variant and media behavior

​Visual choices

​Size charts

​Optional review evidence

​Partial updates and clearing data

​Order updates from multiple workers

​Delete catalog data

​CSV format

​Legacy JSON compatibility

​Image requirements

​Input limits

​Common sync failures

Choose a sync method

Find your site ID

Start with the smallest useful product

Choose a durable product ID

Send products with variants

Send stock updates

Field reference

Variant and media behavior

Visual choices

Size charts

Optional review evidence

Partial updates and clearing data

Order updates from multiple workers

Delete catalog data

CSV format

Legacy JSON compatibility

Image requirements

Input limits

Common sync failures