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

# Quarantine

> Review products that failed a quality check, fix the data, and release them back to your channels. Resolve issues one by one or in bulk.

Quarantine holds products that failed a quality rule before they reach your store. Here you see what went wrong, fix the data, and release the product. Nothing in quarantine can be exported, synced, or published until you act on it.

<Info>
  Only rules with **Block** severity send a product to quarantine. **Skip** rules quietly leave the product out of the export. **Warn** rules let it through and log a warning.
</Info>

## Read the queue

<img className="block dark:hidden" src="https://mintcdn.com/swiftsyncai/Q3dIqlj_CJMF6Idi/images/marketing-screenshots/quality-guard/quality-guard-quarantine-light-branded.webp?fit=max&auto=format&n=Q3dIqlj_CJMF6Idi&q=85&s=079b730ce58707aa31f078f696e40d31" alt="WISEPIM Quality Guard quarantine holding non-compliant products before sync" width="2400" height="1445" data-path="images/marketing-screenshots/quality-guard/quality-guard-quarantine-light-branded.webp" />

<img className="hidden dark:block" src="https://mintcdn.com/swiftsyncai/Q3dIqlj_CJMF6Idi/images/marketing-screenshots/quality-guard/quality-guard-quarantine-dark-branded.webp?fit=max&auto=format&n=Q3dIqlj_CJMF6Idi&q=85&s=d5d59f1349a5836af149c5baa700eb80" alt="WISEPIM Quality Guard quarantine holding non-compliant products before sync" width="2400" height="1445" data-path="images/marketing-screenshots/quality-guard/quality-guard-quarantine-dark-branded.webp" />

The queue lists every product held for review. Each entry shows:

| Column             | What it tells you                                               |
| ------------------ | --------------------------------------------------------------- |
| **Product**        | Name, SKU, and image, so you can spot it fast                   |
| **Failed rules**   | The quality rules the product broke                             |
| **Severity**       | The severity of each failed rule                                |
| **Triggered by**   | What ran the check: export, sync, publish, manual, or scheduled |
| **Target channel** | The channel the product was headed to when it was flagged       |
| **Quarantined at** | When the product entered quarantine                             |
| **Status**         | Pending, Resolved, or Bypassed                                  |

## See why a product failed

Open an entry to see the exact rules and conditions it broke. Each failed condition shows:

* **Field** that was checked, such as Product Name, EAN/GTIN, or Description
* **Operator** that was applied, such as "is not empty" or "length is at least"
* **Expected value** the rule required
* **Actual value** found in your product data
* **Message** that explains the issue in plain language

<Tip>
  One root cause often breaks several rules at once. Fix a single missing field, like an empty EAN, and multiple violations clear together.
</Tip>

## Resolve a product

Resolve a product once you have fixed the data behind the failure. The product leaves quarantine and passes the check on the next export.

<Steps>
  <Step title="Review the violations">
    Open the entry. Read the failed rules and conditions so you know what to change.
  </Step>

  <Step title="Fix the product data">
    Go to the product and update the fields that caused the failure. Use [bulk editing](/en/essentials/bulk-editing) or [AI enrichment](/en/essentials/enriching-products) for common fixes.
  </Step>

  <Step title="Mark as resolved">
    Back in the queue, click **Resolve** on the entry. The product exits quarantine and joins your next export.
  </Step>
</Steps>

## Bypass a product

Bypass a product when you accept the violation and want to release it anyway. You enter a reason, and WISEPIM records it in the [audit log](/en/quality-guard/audit-log).

<Warning>
  Bypassing overrides your quality rules. Use it only when you understand the trade-off, for example when a product is meant to skip a field that a general rule requires.
</Warning>

When you bypass an entry:

* You enter a reason that explains why the bypass is acceptable.
* The bypass and your reason are saved to the audit trail.
* The product becomes exportable despite the violation.
* Your name is recorded as the person who approved it.

## Work in bulk

Clear many entries at once instead of one by one:

* **Bulk Resolve**: select several entries and resolve them together. Use this after a bulk data fix.
* **Bulk Bypass**: select several entries and bypass them with one shared reason. Use this when a whole group shares an acceptable exception.

<Info>
  Each entry is logged on its own in the audit trail, so you keep full traceability even when you act on many at once.
</Info>

## Status reference

| Status       | Meaning                                                            |
| ------------ | ------------------------------------------------------------------ |
| **Pending**  | Held for review and cannot be exported.                            |
| **Resolved** | Data was fixed and the product was released.                       |
| **Bypassed** | Violation was accepted and the product was released without a fix. |

## Common reasons products land here

<CardGroup cols={2}>
  <Card title="Missing EAN/GTIN" icon="barcode">
    The top trigger for marketplace exports. Add or verify the barcode on each affected product.
  </Card>

  <Card title="Description too short" icon="file-text">
    The description falls below the required length. Use AI enrichment to write longer, better copy.
  </Card>

  <Card title="No product images" icon="image">
    Most channels reject products with no image. Upload at least one to release it.
  </Card>

  <Card title="Missing translations" icon="languages">
    A required language is missing. Use AI translation to fill the gaps.
  </Card>
</CardGroup>

## Keep your queue clean

* **Check it often.** Review the queue daily, or before every export, to avoid surprises.
* **Fix data at the source.** Repair the root cause instead of bypassing again and again. Your compliance rate climbs.
* **Resolve in bulk.** After a bulk data update, bulk-resolve the affected entries to clear the queue fast.
* **Always give a reason.** Write a clear, specific note on every bypass. Your future self and your team will thank you.
* **Watch the count.** The quarantine number on the [Quality Guard dashboard](/en/quality-guard/overview) shows how many products need attention at a glance.

## Related

<CardGroup cols={2}>
  <Card title="Quality rules" icon="shield-check" href="/en/quality-guard/rules">
    Set up the rules that decide what passes and what gets blocked.
  </Card>

  <Card title="Audit log" icon="scroll" href="/en/quality-guard/audit-log">
    Track every resolve and bypass for full accountability.
  </Card>

  <Card title="Bulk editing" icon="table" href="/en/essentials/bulk-editing">
    Fix many products at once before you release them.
  </Card>

  <Card title="AI enrichment" icon="sparkles" href="/en/essentials/enriching-products">
    Generate the missing content that caused the failure.
  </Card>
</CardGroup>
