Tags and metafields

When order tagging is on, each verified order gets a risk tag and a set of app metafields. This is how the assessment reaches Shopify Flow, saved views, and your other apps without anyone opening the order.

Tagging applies to orders only. Draft orders are never tagged, because the app does not hold write_draft_orders.

The risk tag

Every verified order carries exactly one tag in this form:

verify-ai:low
verify-ai:medium
verify-ai:high
verify-ai:critical

The band is slugified before it is written, so it survives Shopify's own tag normalisation.

When a re-verification moves an order into a different band, the previous tag is removed and the new one added. An order never carries two verify-ai: tags, which is what lets a saved view filter on one and mean it.

Tagging is a convenience, not part of the verification. If a tag write fails, the verification still succeeds and is still recorded and billed; the failure is logged rather than surfaced as an error on an assessment you already have.

App metafields

The full assessment is written to the $app:verify_ai namespace. Because it is app-reserved, no metafield definition is needed and no other app can write to it.

Key	Shopify type	Contents
`risk_score`	`number_integer`	0 to 100
`risk_level`	`single_line_text_field`	`low`, `medium`, `high`, or `critical`
`verified_at`	`date_time`	When the assessment was written
`result`	`json`	The whole assessment: `riskScore`, `riskLevel`, `riskFactors`, `analysis`, and `recommendations`

Read risk_score and risk_level when you need the band, and result when you need the factors and reasoning. Each entry in result.riskFactors carries a factor, severity, category, and description.

Acting on the tag in Shopify Flow

The most common setup is a Flow workflow that routes high-risk orders to a person. Build it as:

Trigger: order tags added
Condition: order tags contains verify-ai:high or verify-ai:critical
Action: hold the fulfilment, add an order note, send an internal email, or post to Slack

Trigger on tags added rather than on order created. The order is created before the verification finishes, so an order-created workflow would run against an order that has no tag yet.

Keep the destructive steps out of Flow until you have watched the scores for a few weeks. Holding fulfilment is reversible; cancelling and refunding are not, and a false positive costs a real customer.

Saved views

Filter the orders list by tag to give the fulfilment team a queue:

tag:verify-ai:high OR tag:verify-ai:critical

Save it as a view and the queue maintains itself as new orders are scored.

Other apps

Any app that reads order tags sees the risk band without further integration. Third-party fulfilment services, 3PL connectors, and order management tools generally fall into this category.

Turning it off

Order tagging is switchable per store from Settings in the Verify AI dashboard, and requires owner or admin permission. Turning it off stops new writes. Tags already on past orders stay, because removing them would rewrite history on orders that were genuinely assessed.