Imports

Imports let you bring first-party catalog data into Extralt without crawling your own storefront first.

A run crawls ecommerce pages. An import uploads catalog data you already have. Both produce captures, and captures move through the same Enrich, Extend, and Explore pipeline.

When to use imports

Use imports when you want your own product catalog inside Extralt:

• Seed Extralt with your current product data
• Compare your catalog against open-web competitor observations
• Enrich your own products with the same taxonomy, attributes, and signals as extracted products
• Build Explore views where your catalog is the reference point

Imports are not a separate product model. They are another way to create captures.

Creating an import

Dashboard

Navigate to Extract > Imports > New.

Choose a catalog file, confirm the country and language, then upload it. The import appears in Extract > Imports > List with its current status, success count, error count, and status message.

Supported source files currently include JSON, JSONL, and CSV. The file should contain enough product data to build valid captures: product titles, images, variants or SKUs, prices, currency, and stable product or SKU identifiers where available.

API

The dashboard sends the file to the Extract API. API clients can use the same import endpoint under /v1/extract/imports.

Use the import status endpoint to poll the job, then list captures with the returned import id.

Validation

Imports use the same capture quality gate as crawled data. Extralt does not force incomplete catalog rows into captures.

An import can fail validation when the source data is too sparse or ambiguous, for example:

• no usable product title
• no product image
• no variant or SKU structure
• no positive price
• no currency
• rows that cannot be mapped to stable products
• nested data where products, variants, prices, or stock cannot be joined safely

When validation fails, the import status includes a message explaining what was missing or invalid.

After import

Once an import completes, open Extract > Captures and filter by the import job. Imported captures can then be enriched like captures from a crawl run.

The downstream model is the same: