---
title: "Settings and trigger toggles"
description: "Switch individual triggers on and off across the Settings tabs, understand opt-in triggers versus suppressors, and manage the baseline sync."
canonical: "https://docs.workflow-trigger-extensions.app/settings-and-toggles"
---

# Settings and trigger toggles

The **Settings** page is where you switch individual triggers on and off. It is split
into tabs by resource.

## The tabs

| Tab | Controls |
| --- | --- |
| **Trigger Settings** | Suppressors for the broad `... Update` triggers |
| **Order Triggers** | Order tags, note, attributes, fulfillment, financial status, shipping address |
| **Draft Order Triggers** | Draft order status, line items, tags, note, attributes, email, addresses |
| **Product Variants** | Variant price, SKU, barcode, unit price |
| **Customer Triggers** | Customer tags, note, state, marketing consent, personal data, and B2B contacts |
| **Product Triggers** | Product title, description, handle, type, vendor, status, tags, publications |
| **Polling Triggers** | Blogs, blog posts, pages, discount expiry, order display status, company location tax |
| **Collection Triggers** | Collection handle, title, description |
| **Markets** | Market status |
| **Inventory Triggers** | Stock level, out of stock, back in stock, variant cost |

You can deep-link a tab with `?tab=<slug>`, for example `app/settings?tab=order`.

## Two kinds of control

### Opt-in triggers (most of them)

Field-level triggers are **off by default**. Switching one on also queues a baseline
sync so change detection has something to compare against.

You rarely need to do this by hand: turning on a Shopify Flow workflow that uses the
trigger switches it on and starts the sync automatically.

### Suppressors (the first tab)

The broad triggers - **Order Update**, **Product Update**, **Customer Update**,
**Collection Update**, **Company Update**, and the discount, market, and location
families - are **on by default** once their permission is granted. The first tab lets
you turn them *off*.

> [!TIP]
> These broad triggers are the usual cause of unexpectedly high usage: they fire on every
> edit to the resource. If your workflows only use narrow triggers, suppress the broad
> ones. Suppression happens before the event is counted, so it genuinely reduces quota
> consumption.

## The baseline sync

After enabling a change-detection trigger, the tab shows a loading indicator while the
baseline sync runs. It refreshes automatically. Expect seconds on a small store, and up
to roughly 20 minutes for a catalog above 100,000 items.

If the required permission has not been granted yet, the sync is **deferred** rather
than failed. Grant the permission and it starts on its own.

## Manual re-sync

Each resource tab has a **Sync existing ...** button. Use it if you suspect the baseline
has drifted, for example after a long period with the permission revoked, or after a
large import performed while the trigger was off.