Skip to main content
Long-running and batch operations in MerchantOps run as jobs. A job groups many items into one tracked operation so you can watch it finish, see how much succeeded, and catch what failed — without refreshing individual products. This page explains what a job records and how to monitor it. For the shared vocabulary, see Core concepts.

​
What a job tracks

Imports, enrichment runs, and exports all run as jobs. Each job records its type and its progress as it works through its items:
​
job type
import / enrichment / export
What the job is doing — bringing products in, enriching them, or exporting data out.
​
total
count
How many items the job set out to process.
​
processed
count
How many items have finished so far.
​
failed
count
How many items couldn’t be completed.
​
progress
percentage
How far along the job is, computed from processed against total.
Together these let you tell at a glance whether a job is still running, finished cleanly, or finished with some items needing attention.

​
Monitoring jobs

Track jobs on the Jobs page, which shows each job’s type, status, counts, and progress percentage in real time. You can also read a job’s progress through the API when you’re wiring MerchantOps into your own systems.
1

Start a batch operation

Import or export a set of products, or let enrichment run — each creates a job.
2

Watch progress

The job’s progress percentage climbs as its processed count rises toward total.
3

Review failures

When the job finishes, check the failed count. A non-zero value means some items need a second look.
A completed job with a non-zero failed count has still finished — it just means some items didn’t process and need a second look. Review those items rather than re-running the whole batch.

Data ingestion

How products get into MerchantOps — the imports that create jobs.

How enrichment works

Enrichment runs as a background job over your products.