# Import Shopify products from a CSV URL with a workflow

Product imports are rarely just file uploads. A workflow can validate rows, create products, update variants, set inventory, publish channels, and log failures.

Canonical URL: https://blog.jsworkflows.com/articles/import-shopify-products-from-csv-url-workflow/

Category: Operations

Importing products from a CSV file sounds simple until the file has to become a real Shopify catalog.

Creating the product is only one part of the job. A serious import may need to create or update variants, activate inventory at locations, set available quantities, write metafields, publish products to sales channels, load images, validate taxonomy categories, and report every row that could not be processed.

That is why product import is a good example of a workflow, not just a file upload.

## The pain point

Supplier and catalog CSV files rarely match Shopify perfectly.

- Product titles, handles, vendors, product types, and tags may need cleanup.
- Variant rows may need option values and SKU matching.
- Inventory quantities may need to be applied by location.
- Product or variant metafields may need type-safe values.
- Some products may need to be published to specific channels.
- Images may be listed as URLs and need validation.
- Some rows may be new products while others are updates.
- Failed rows need a clear reason so the file can be fixed.

When this is handled manually, the import process becomes a mix of spreadsheet edits, trial uploads, and cleanup work inside Shopify.

## What makes it a complex job

A product import touches several Shopify resources and API operations.

Depending on the store's needs, the workflow may need to work with:

- Products.
- Product variants.
- Variant options.
- Inventory items.
- Inventory levels.
- Locations.
- Product and variant metafields.
- Publications and sales channels.
- Product media or image URLs.
- Taxonomy categories.

That is more than a single create action. It is an orchestration problem.

## How a workflow helps

A JsWorkflows product import can run from a schedule, manual test, or configured CSV URL. The workflow can import the file, process rows in batches, and keep a run history.

A strong workflow can:

1. Validate the CSV URL and required headers.
2. Normalize row values before calling Shopify.
3. Decide whether a row should create a product or update an existing one.
4. Set variants, SKUs, options, tags, status, vendor, and product type.
5. Activate inventory items at the right locations.
6. Set inventory quantities in batches.
7. Set product or variant metafields.
8. Publish products to selected channels.
9. Retry transient API errors and throttled requests.
10. Send or log a summary of created, updated, skipped, and failed rows.

This turns the import from a manual upload into a repeatable operational process.

## Why this shows the value of JsWorkflows

Many automations can be expressed as a simple trigger and action. Product import is different. It needs branching, validation, paging, batching, retries, and multiple Shopify GraphQL requests.

That is where editable workflow code matters.

The merchant-facing setup can stay simple: a CSV URL and selected publications. The technical details can stay in code: batch size, retry limits, lookup strategy, Shopify GraphQL mutations, and error handling.

This split is important. Merchants should configure the business inputs. The workflow should handle the mechanics.

## A practical example

The JsWorkflows product import template is a good example of this pattern. It uses a CSV URL as the source and can coordinate product lookup, product updates, inventory activation, inventory setting, metafield updates, and publication.

The point is not only that the template imports products. The point is that it demonstrates how a workflow can coordinate many Shopify resources safely in one controlled run.

That makes it useful for catalog onboarding, supplier imports, product backfills, and repeatable catalog maintenance jobs.

## What to watch for

Product import workflows should be conservative.

- Require clear identifiers such as handle or SKU.
- Validate required headers before writing data.
- Keep row-level failure messages.
- Avoid updating unrelated products when identifiers are ambiguous.
- Batch Shopify API writes.
- Retry only transient failures, not data validation errors.
- Review logs before increasing automation scope.

These safeguards are what separate a controlled workflow from a risky bulk script.

## When this is a good fit

Use a workflow when the CSV import is repeated, store-specific, or operationally important.

If you only need a one-time basic upload, Shopify's built-in CSV import may be enough. If the import needs mapping rules, inventory logic, metafields, publication control, retries, or detailed reporting, a workflow is the better fit.

The value is not just importing faster. The value is making the import process consistent, reviewable, and easier to improve over time.