Works with Ruleproof — Rules2Tag presets
Tags that can be read at checkout. Ruleproof — our checkout-rules app — reads customer and product tags to change shipping, payment or whether checkout goes ahead. It is not required: any app that reads tags at checkout can use these, and the tags are yours either way.
Each of these is a ready-made rule you can adopt in one click inside Rules2Tag, then change however you like. Nothing runs until you say so, and every rule can be previewed against your own store first.
These pair with Ruleproof, our checkout-rules app — the two are built to work together, and each is useful on its own. You do not need both: nothing here depends on Ruleproof, so another app or your own process can play the same part.
10 presets in this category
Customers using disposable email
I want to flag customers signing up with throwaway addresses
Tags a customer whose email is on a throwaway domain as fraud-suspected.
Why: A throwaway address is the cheapest signal that a buyer does not mean to be reachable, and it often comes before card testing and chargebacks. Shopify surfaces nothing about it. This app writes the tag and stops there — blocking is a separate job, and Ruleproof's "Block checkout for flagged customers" is the rule that refuses the next attempt.
Together: Ruleproof reads this tag at checkout — remove cash on delivery and express shipping, or stop checkout outright, for the customers this flags.
Customers with automated email patterns
I want to flag signups that look generated rather than typed
Tags a customer whose email looks machine-generated as bot-suspected.
Why: Card testing and bulk signups reuse one mailbox through aliases — name+1@, name+2@ — or bolt digits onto a real-looking name. Both are visible in the address itself, and Shopify cannot filter on either. Tagged as a bot rather than as fraud on purpose: these are usually worth reviewing rather than refusing. This app only writes the tag — pair it with Ruleproof's "Block checkout for flagged customers" if you do want them refused.
Together: Ruleproof reads this tag at checkout — stop checkout, or strip the payment methods fraud favours, for the customers this flags.
VIP customers by lifetime spend
I want to tag my best customers so I can treat them differently
Tags a customer once their all-time spend passes a threshold you choose.
Why: Lifetime spend is the single most requested segment and the hardest to get right: Shopify segments recompute on demand, but a TAG is durable — it drives shipping rules, discounts, and the flows other apps read. This is also where a 60-day view lies outright: a customer who spent thousands last year looks brand new.
Together: Ruleproof reads this tag at checkout — give VIP-tagged customers a free or faster shipping option nobody else sees.
Students (.edu email)
I want to spot students so I can offer a student discount
Tags a customer whose email matches a pattern you choose — \.edu$ for US universities.
Why: Email-domain segmentation is how student and employee pricing is usually verified without a third-party service, and a regex handles the variants (.edu, .ac.uk, a company domain) that an equals-match cannot.
Together: Ruleproof reads this tag at checkout — reserve a student shipping rate or payment method for customers carrying it.
Wholesale (tax-exempt) customers
I want to tag my wholesale accounts
Tags any customer Shopify marks as tax-exempt.
Why: Tax-exempt is the flag wholesale accounts already carry, so this needs no data entry and no list to maintain — and the resulting tag is what checkout rules and pricing apps can read.
Together: Ruleproof reads this tag at checkout — show trade shipping and invoice payment to wholesale customers, and hide them from everyone else.
Email marketing subscribers
I want to tag customers who agreed to marketing email
Tags a customer whose email marketing consent is subscribed.
Why: Consent lives on the customer profile but is not a tag, so it cannot drive the flows and segments that read tags. It also changes, so a manual copy goes stale — and a stale copy is a compliance problem, not a marketing one.
Together: Ruleproof reads this tag at checkout — a subscriber-only shipping perk is one rule away.
Spend tier (bronze / silver / gold)
I want to band my customers into spend tiers, not just one VIP group
Tags a customer whose all-time spend falls BETWEEN two amounts you choose.
Why: One VIP threshold gives you two groups: VIP and everyone else. Tiers let the middle exist, which is where most of a store's revenue actually sits. Run this preset once per tier with different bands and tags — the upper bound is what keeps a gold customer out of the silver tag.
Together: Ruleproof reads tier tags at checkout — each tier can unlock its own shipping or payment options.
Age-restricted products, by product type
I want to flag the products that need an age check at checkout or delivery
Tags every product whose product type is one of the types you list.
Why: Age verification is usually enforced by something OTHER than the product page — a checkout rule, a carrier that requires ID on delivery, a state or postcode restriction. All of those need a durable flag on the product, and product type is how most catalogs already separate this stock. Getting it from a tag means the rule keeps working as you add products.
Together: Ruleproof reads this product tag at checkout — its "Restrict regulated products by region" preset blocks or limits a cart carrying it by shipping destination.
Age-restricted products, by vendor
I want everything from certain suppliers flagged as age-restricted
Tags every product from the vendors you list.
Why: For a lot of stores the restriction follows the SUPPLIER, not the product type — a distillery or vape wholesaler sells nothing that does not need a check. Naming the vendor once means new stock from them arrives already flagged, which is the failure mode a manual tag has: the product added on a busy Friday is the one that ships without the check.
Together: Ruleproof reads this product tag at checkout — its "Restrict regulated products by region" preset blocks or limits a cart carrying it by shipping destination.
Age-restricted products, by title wording
I want to flag age-restricted products that I only recognize by name
Tags every product whose title matches a pattern you supply.
Why: The honest fallback for a catalog that grew organically, where "Wine" is a word in the title rather than a product type. A pattern is less precise than a type and this preset says so: check the dry run before making it live, because a title rule matching "gin" also matches "ginger". Prefer the product-type or vendor version when your catalog supports it.
Together: Ruleproof reads this product tag at checkout — its "Restrict regulated products by region" preset blocks or limits a cart carrying it by shipping destination.