Scan and review findings

Scan lifecycle

A scan is scoped to the authenticated Shopify store. It reads the fields required by the enabled detectors, creates a review result and records the run status. The app should show running, completed, blocked or failed states rather than treating an incomplete run as a clean result.

Read an issue

Each issue explains the signal that caused it, the affected field or records and the action that can be proposed. Values shown in the review surface are masked where full customer data is not needed for the decision.

Use the issue detail to check:

• why the finding was created;
• whether the proposed correction is within the documented scope;
• what the before-and-after preview contains; and
• whether the action should be approved, dismissed or left for later.

Approve deliberately

Do not approve a correction just because two values look similar. Confirm the store context, the affected records and the intended result. If the preview is incomplete or the action fails, keep the issue in review and contact support rather than repeating a broad write.

The app records the approved action in its audit history. It does not silently retry a failed customer change as a different action.