> ## Documentation Index
> Fetch the complete documentation index at: https://docs.merchantops.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Jobs

> How MerchantOps tracks batch operations — import, enrichment, and export — and how to monitor their progress.

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](/getting-started/concepts).

## What a job tracks

Imports, [enrichment](/enrichment/how-it-works) runs, and exports all run as
jobs. Each job records its type and its progress as it works through its items:

<ResponseField name="job type" type="import / enrichment / export">
  What the job is doing — bringing products in, enriching them, or exporting
  data out.
</ResponseField>

<ResponseField name="total" type="count">
  How many items the job set out to process.
</ResponseField>

<ResponseField name="processed" type="count">
  How many items have finished so far.
</ResponseField>

<ResponseField name="failed" type="count">
  How many items couldn't be completed.
</ResponseField>

<ResponseField name="progress" type="percentage">
  How far along the job is, computed from processed against total.
</ResponseField>

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.

<Steps>
  <Step title="Start a batch operation">
    Import or export a set of products, or let enrichment run — each creates a
    job.
  </Step>

  <Step title="Watch progress">
    The job's progress percentage climbs as its `processed` count rises toward
    `total`.
  </Step>

  <Step title="Review failures">
    When the job finishes, check the `failed` count. A non-zero value means some
    items need a second look.
  </Step>
</Steps>

<Tip>
  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.
</Tip>

<CardGroup cols={2}>
  <Card title="Data ingestion" icon="file-import" href="/data-ingestion/overview">
    How products get into MerchantOps — the imports that create jobs.
  </Card>

  <Card title="How enrichment works" icon="wand-magic-sparkles" href="/enrichment/how-it-works">
    Enrichment runs as a background job over your products.
  </Card>
</CardGroup>