Warnify documentation

Core concepts

A warning rule defines the customer-facing copy, display behavior, placement, targeting, and consent storage behavior for a warning.

A theme app block renders matching rules on the storefront. Warnify includes a product warning block and a cart warning block.

Consent evidence is captured when a shopper accepts a required warning. The accepted rule version is stored so later changes to warning copy do not overwrite historical context.

• Use product pages for item-specific notices before add to cart.
• Use cart pages for final review before checkout.
• Use checkout blocking for warnings that must be accepted before purchase.

Rule targeting

Warnify supports several target types so merchants can match warnings to the catalog structure they already maintain in Shopify.

• Products: apply a rule to all variants of selected products.
• Variants: apply a rule to selected SKUs, sizes, colors, or configurations.
• Collections: apply a rule to every product in selected collections.
• Product tags: apply a rule to products with matching Shopify product tags.

Display types

Display type controls how strongly a warning interrupts the buying flow. The same rule can be styled differently through app settings and theme block settings.

• Inline message: informational notice without required consent.
• Required checkbox: customer must tick a checkbox before continuing.
• Modal confirmation: customer opens and confirms a branded warning modal.

Theme app blocks

Merchants place Warnify blocks in the Shopify theme editor. The blocks can inherit app-level style settings or be customized directly in the theme editor.

• Product warning block: reads product, selected variant, tags, collections, and rule metafields.
• Cart warning block: reads cart items, product tags, collections, and rule metafields.
• Display conditions: customer state, country, discount-code state, shipping requirement, gift cards, subtotal, quantity, line items, and cart weight.

Checkout blocking

Checkout blocking requires a rule with required acknowledgment and block checkout enabled. When accepted, Warnify stores accepted rule details in cart attributes.

The checkout validation function reads required rule metafields and accepted cart attributes. If a required rule is missing, checkout returns a blocking error.

• Use checkout blocking for mandatory warnings and terms.
• Use notice-only warnings when the customer does not need to explicitly consent.
• Keep theme blocks installed so customers can accept warnings before reaching checkout.

Consent logs

Consent logs give merchants a reviewable history of accepted warnings. Logs preserve the rule snapshot used at the time of acceptance.

• Rule name and rule version snapshot.
• Warning title, message, and checkbox label snapshots.
• Accepted status, accepted time, source page, cart token when available, product IDs, variant IDs, and user agent when available.
• CSV or spreadsheet export for offline review.

Recommended testing flow

Use a test product and a test collection before enabling a rule for a live catalog group. Confirm both storefront rendering and checkout validation before relying on a rule in production.

• Create a test rule and target a test product, variant, collection, or tag.
• Add product and cart theme blocks in the active or preview theme.
• Open the storefront product page and accept the warning.
• Add the product to cart and verify cart warning behavior.
• Try checkout before and after acceptance to verify blocking.
• Open consent logs and confirm the acceptance record appears.