Skip to main content

​
What Is the Quarantine?

When a product fails a quality rule with Block severity, it is placed in quarantine. Quarantined products cannot be exported, synced, or published until the underlying data issues are resolved. The Quarantine page is where you review these products, understand what went wrong, and take action.
Only rules with Block severity send products to quarantine. Rules with Skip severity silently exclude the product, and rules with Warn severity let the product through with a logged warning.

​
The Quarantine Queue

The Quarantine Queue shows all products currently held for review. For each entry, you can see:
  • Product name, SKU, and image — Identify the product at a glance
  • Failed rules — Which quality rules the product violated
  • Severity — The severity level of each failed rule
  • Triggered by — What action caused the quality check (export, sync, publish, manual, or scheduled)
  • Target channel — The channel the product was being exported to when it was flagged
  • Quarantined at — When the product entered quarantine
  • Status — Pending, Resolved, or Bypassed

​
Understanding Violations

Each quarantine entry lists the specific rules the product failed, along with the individual conditions within those rules. For every failed condition, you can see:
  • The field that was checked (e.g., Product Name, EAN/GTIN, Description)
  • The operator that was applied (e.g., “is not empty,” “length is at least”)
  • The expected value the rule required
  • The actual value found in your product data
  • A human-readable message explaining the issue
Use the failed condition details to pinpoint exactly what needs to be fixed. Often a single missing field — like an empty EAN — is the root cause, and fixing it resolves multiple rule violations at once.

​
Resolving Quarantined Products

You have two options for handling a quarantined product:

​
Resolve

Resolving means you have fixed the underlying data issue. The product is removed from quarantine and will pass the quality check on the next export attempt.
1

Review the violations

Open the quarantine entry and read through the failed rules and conditions to understand what needs to change.
2

Fix the product data

Navigate to the product and update the fields that caused the failure. You can use bulk editing or AI enrichment for common fixes.
3

Mark as resolved

Return to the Quarantine Queue and click Resolve on the entry. The product exits quarantine and will be included in your next export.

​
Bypass

Bypassing means you are acknowledging the violation but choosing to let the product through anyway. You must provide a reason for the bypass, which is recorded in the audit log.
Bypassing a quarantine entry overrides your quality rules. Use this only when you understand the consequences — for example, when a product is intentionally missing a field that is required by a general rule but not needed for a specific use case.
When you bypass an entry:
  • You must enter a reason explaining why the bypass is acceptable
  • The bypass and your reason are logged in the audit trail
  • The product will be exportable despite the rule violation
  • Your name is recorded as the person who approved the bypass

​
Bulk Actions

For efficiency, you can resolve or bypass multiple quarantine entries at once:
  • Bulk Resolve — Select multiple entries and resolve them all in one action. Use this after a bulk data fix.
  • Bulk Bypass — Select multiple entries and bypass them with a shared reason. Use this when an entire group of products has an acceptable exception.
Bulk actions are logged individually in the audit trail, so you maintain full traceability even when processing many entries at once.

​
Quarantine Statuses

StatusMeaning
PendingThe product is in quarantine and waiting for review. It cannot be exported.
ResolvedThe data issue has been fixed and the product has been released from quarantine.
BypassedThe violation was acknowledged and the product was manually released without fixing the issue.

​
Common Quarantine Scenarios

Missing EAN/GTIN

The most common quarantine trigger for marketplace exports. Add or verify the barcode for each affected product.

Description Too Short

Products with descriptions below the required character count. Use AI enrichment to generate longer, higher-quality descriptions.

No Product Images

Products without any images cannot be exported to most channels. Upload at least one image to resolve.

Missing Translations

Products lacking translations for a required locale. Use the translation feature or AI translation to fill in missing languages.

​
Best Practices

  • Check quarantine regularly — Review the queue daily or before every export run to avoid surprises.
  • Fix data at the source — Rather than bypassing repeatedly, fix the root cause in your product data. This improves your overall compliance rate.
  • Use bulk actions wisely — After a bulk data update, bulk-resolve the affected quarantine entries to clear the queue efficiently.
  • Document bypasses — Always provide a clear, specific reason when bypassing. Your future self (and your team) will thank you.
  • Monitor the dashboard — The quarantine count on the Quality Guard dashboard gives you an at-a-glance indicator of how many products need attention.