Overrides

With overrides you can deliberately exempt individual products from enforcement — for example legacy stock or special cases that intentionally do not satisfy a rule.

How overrides behave

• A product with an active override is not restricted in its visibility in enforce mode, even if it has blocker violations.
• Overrides apply globally or to a specific sales channel. A global override (salesChannelId = null) applies to all channels.
• Every override requires a justification comment — this ensures traceability.
• Creating and removing overrides is recorded in the audit log (override_enabled / override_disabled).

Managing overrides (API)

Overrides are managed via the API. The endpoints are protected by the quality_gate.override permission.

Enable an override

POST /api/_action/quality-gate/override/enable
{
  "productId": "018d1234567890abcdef1234567890ab",
  "salesChannelId": null,
  "comment": "Approved by management – legacy product"
}

Disable an override

POST /api/_action/quality-gate/override/disable
{
  "productId": "018d1234567890abcdef1234567890ab",
  "salesChannelId": null,
  "comment": "Override no longer needed"
}

Query the status of an override

GET /api/_action/quality-gate/override/status/{productId}?salesChannelId={id}

The salesChannelId parameter is optional. If omitted or set to null, the override applies globally.