Skip to main content
Before you can enrich, price, or publish a product, it has to exist in your catalog. This page covers the ways product data gets into MerchantOps and points you to the details for each. For the vocabulary used here — product, variant, attribute, Job, enrichment — see Core concepts. Everything you ingest lands as products scoped to your organization, validated against a product type. Batch imports and enrichment create a Job you can monitor for progress and per-row errors.

Ways to add products

In the dashboard

Create a product by hand, filling in its name, brand, product type, and attributes. Best for one-off additions and corrections.

Paste a product URL

Point MerchantOps at a product page and it creates the product, then enriches it from that page and the brand site.

Upload a CSV

Bring in many products at once from a spreadsheet export. Columns map to product fields and attributes; the batch runs as a tracked Job.

Import connectors

Scheduled, automated feeds — for example a nightly file drop over SFTP — that keep your catalog in sync with a partner or ERP system.

The API

Create products programmatically, one at a time or in batches, from your own systems or the mo CLI.

Which method to use

You want to…Use
Add or fix a single productThe dashboard
Enrich from a known product pagePaste a product URL
Load a batch from a spreadsheetCSV upload
Keep a catalog continuously in syncImport connectors
Wire ingestion into your own systemsThe API
There is also a shared Lakehouse — a knowledge base of product, technology, and document data that enrichment draws on. It is not a way to add products to your catalog directly; it is a source enrichment consults to fill them in.

What happens after ingestion

However a product arrives, the flow is the same:
1

The product is created and validated

MerchantOps checks it against its product type and initializes its attributes.
2

Enrichment runs, if requested

You can ask for enrichment at ingestion time — searching the Lakehouse, scraping the brand site, and generating missing content. See How enrichment works.
3

Progress is tracked as a Job

Batch imports and enrichment create a Job with live counts of processed, succeeded, and failed items, plus per-row error detail.

Uploading products

Column mapping, batch imports, and how uploads become products.

Import connectors

Scheduled feeds that import a partner or ERP catalog automatically.

The Lakehouse

The shared knowledge base enrichment reads from.

Jobs

Track the progress of any batch import or enrichment run.