Enforce checks at publish

Requires the Laqi Product Data Checks Pro add-on.

Auditing tells you what is broken now. Enforcement stops the next one.

Under Checks, Pro adds a column where each check can be set to:

• Nothing means the check still reports, but does not interrupt anyone.
• Warn tells the person saving, then lets the save proceed.
• Block refuses the save.

Warn is the default and blocking is opt-in, per check. A rule that blocks everything would lock you out of your own catalogue on the day you install it.

The two editors behave differently, honestly

• The new product editor and the REST API get a real error, so the save genuinely fails and the person sees why.
• The classic editor has no way to refuse a save at that point. The product is kept as a draft instead, and told why.

These are described separately rather than as if they behaved the same, because the difference is visible to whoever hits it.

Imports are never blocked

The WooCommerce CSV importer and programmatic saves are recorded, never refused. A nightly supplier feed that fails stops the business, which is worse than the data problem being enforced against. Those products appear in the findings list like any other.

If the licence lapses

Enforcement stops and the store falls back to the free behaviour: the problem is still found and still reported, it just no longer blocks the publish. Your per-check settings are kept, so renewing restores exactly what you had.