Turning a check off

A store that does not carry barcodes is not a store with three thousand problems. Checks is where a store says which rules apply to it — and the interesting part is not the switch, it is what happens to everything already found.

Nothing is resolved, because nobody fixed anything

The obvious way to build this is the wrong one. If turning a check off closed its findings, every one of them would land in Proof as a change somebody made — thousands of receipts for work that never happened. And if the findings were simply left open, they would sit on the list forever, asking for work no check will ever look at again.

So a finding whose check goes off does neither. It goes quiet: a state of its own that keeps the evidence, the revision and the history, and credits nobody. It leaves the open counts, the lanes, Today and the alerts, and it never appears in Proof.

Turning a check off moves its open findings into a quiet state rather than resolving them; approved and applied cases carry on to their receipt; turning the check back on lets the next catalog check decide which findings are still true. WHEN THE CHECK GOES OFF Open findings and their drafts Quiet not fixed · credits nobody Approved · applying already promised Seen through receipt in Proof, as ever WHEN IT COMES BACK ON A full catalog check runs still true → open again, same case gone → closed, crediting nobody dismissed by a person → stays dismissed One decision, one receipt, one re-read of the catalog.
The switch is the small part. What it does to work already in flight is the whole design.

Choose requirements for this store

The full-description minimum, requiring an assigned brand, and requiring that brand in the title are off by default. Enable them in Checks for the selected store. A minimum needs a positive character count; the same value is used in scanning and draft review. Changing the number shows its expected impact before saving and starts a full scan.

Work already in progress gets a recorded outcome

A change already sent to the store still needs its result checked. A proposal waiting to be sent is checked against the current policy first. Changing a rule can make that proposal stale; it never authorizes a different catalog value. Completed writes retain their receipts, while a rule change alone counts no repair.

Nothing new of a turned-off check is written down in the meantime.

Turning it back on does not un-do anything

Restoring quiet findings wholesale would be a lie. Some of their products no longer exist; some were fixed while nobody was watching. So turning a check back on restores nothing directly — it starts a full catalog check, and that decides:

  • Still there — the finding is open again, the same case with the same history, in the same revision unless the product itself moved.
  • Gone — the finding closes crediting nobody. It is not counted as a fix, and Proof does not report one.

A dismissal is a different thing, and it survives

Turning a check off is a rule about the whole store. Dismissing one finding is a person saying this particular product does not have this problem. The two never overrule each other: a finding you dismissed stays dismissed through a check going off and coming back, and only a change to the product itself brings it up again.

What it costs, before you decide

Saving the list is one decision: however many switches you moved, they arrive together, leave one receipt with your name and the door you came through, and start one catalog check rather than one per switch. Before you save, the confirmation counts what it will move — how many findings go quiet, across how many checks, how many drafts go with them, and how many cases are already on their way to your store and will be seen through regardless.

Not connected yet? The scan is free.

Create an account, connect your WooCommerce store and what this article describes runs on your real products.

No card required. The free plan never writes to WooCommerce.