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.
Crawl a site
Point MerchantOps at a website, let it discover product pages, then review
the list and import the ones you want. See crawling a site.
The API
Create products programmatically, one at a time or in batches, from your own
systems or the
mo CLI.Recurring imports
Bringing the same catalog in on a cadence — what that actually involves, and
what MerchantOps does and doesn’t do for you.
Which method to use
There is no self-service connector builder — no screen where you register an
upstream system and set a schedule. A recurring import is either your code
calling the API on your own schedule, or a managed feed that MerchantOps
builds and operates for you. See
recurring imports for what each involves.
Crawling a site
When the catalog you want exists as a website rather than a file, a crawl discovers the product pages for you. It is a two-stage flow with a human decision in the middle — MerchantOps never imports a page just because it found it.1
Queue the crawl
In Add Product(s) → Site Crawl, give the site’s URL, a search term used
to filter the URLs discovered (it defaults to
product), and a cap on how
many URLs to discover. The crawl runs in the background as a
Job.2
MerchantOps classifies what it found
Each discovered URL is classified as a product page or not, with a confidence
score and a short reason, so you’re reviewing a judgement rather than a raw
URL dump.
3
Review and select
Open the crawl job’s review screen. Each row shows the page’s title, its
classification, and the confidence behind it; a filter narrows the list to
pages classified as products, and a header checkbox selects everything
that’s still unimported. Pages you’ve already imported are marked, so a
second pass doesn’t duplicate work.
4
Import the selected pages
Create Products turns the selected URLs into products. This is where you
choose the enrichment options — Lakehouse search,
brand-site scraping, content generation — and it starts a separate job
from the crawl, which is the one to watch for import progress.
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.
Recurring imports
The three real paths for importing the same catalog again and again.
The Lakehouse
The shared knowledge base enrichment reads from.
Jobs
Track the progress of any batch import or enrichment run.