Skip to main content
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.
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.

​
Read the queue

WISEPIM Quality Guard quarantine holding non-compliant products before sync The queue lists every product held for review. Each entry shows:

​
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
One root cause often breaks several rules at once. Fix a single missing field, like an empty EAN, and multiple violations clear together.

​
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.
1

Review the violations

Open the entry. Read the failed rules and conditions so you know what to change.
2

Fix the product data

Go to the product and update the fields that caused the failure. Use bulk editing or AI enrichment for common fixes.
3

Mark as resolved

Back in the queue, click Resolve on the entry. The product exits quarantine and joins your next export.

​
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.
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.
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.
Each entry is logged on its own in the audit trail, so you keep full traceability even when you act on many at once.

​
Status reference

​
Common reasons products land here

Missing EAN/GTIN

The top trigger for marketplace exports. Add or verify the barcode on each affected product.

Description too short

The description falls below the required length. Use AI enrichment to write longer, better copy.

No product images

Most channels reject products with no image. Upload at least one to release it.

Missing translations

A required language is missing. Use AI translation to fill the gaps.

​
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 shows how many products need attention at a glance.

Quality rules

Set up the rules that decide what passes and what gets blocked.

Audit log

Track every resolve and bypass for full accountability.

Bulk editing

Fix many products at once before you release them.

AI enrichment

Generate the missing content that caused the failure.