Build vs. Buy>Discounts & Promotions>Member/tag-based pricing

Build or Buy Member & Tag-Based Pricing on Shopify?

Written by Deploi EditorialReviewed by Martin Dejnicki, Director of SEO & AI SearchUpdated August 2026Pricing verification pending

Member and tag-based pricing lands on CUSTOMIZE: native primitives now cover both halves, so the budget goes to glue, not an app's pricing engine. B2B catalogs have priced company accounts on every paid plan since April 2, 2026, and a discount Function plus theme work prices DTC member tiers for an estimated $8,000–$25,000 (Deploi estimate, illustrative). Buy a pricing app only where the 3-catalog cap on non-Plus plans genuinely binds you.

Your profile — see how the verdict shifts

VerdictCUSTOMIZE (catalogs for B2B, Functions for DTC tiers) · BUY only past the 3-catalog cap
Buy score
4.9
Build score
7.5
Confidence
HighApril 2026 made B2B pricing native on all paid plans and Functions carry the DTC half; the app category's job shrank to edge cases
Reference scenario
$20M–$100M GMV · member/wholesale mix · agency dev bench
As of
August 2026

Decision at a Glance

Your profileVerdictWhy
Under $2M revenueBUYA pricing app delivers member tiers this week; native glue needs dev hands your first budget spends better elsewhere.
$2M – $15MDEPENDSTwo or three trade tiers fit native catalogs today; buy only if no bench exists to wire the Function and theme display.
$15M – $75MCUSTOMIZENative catalogs price companies, a Function prices member tags, the theme shows it — owned glue beats a per-customer app fee.
$75M+CUSTOMIZEContract complexity grows and Plus lifts the 3-catalog cap, removing the last app argument; pricing rules belong in code you version.

What Member/tag-based pricing Actually Drives

OutcomeImpactHow it works
Revenue — directHighMember and trade prices convert the segments that already buy most, and the right price applies at cart and checkout with no codes to remember.
Retention & LTVHighA visible member price is a standing reason to stay a member — pricing quietly does the retention work loyalty banners only claim.
Data & insightMediumTier-keyed pricing data shows margin and uptake per segment, so finance sees exactly what member discounts cost and return.
Operational efficiencyMediumCatalogs and Functions replace spreadsheet price lists and manual quote edits with rules that apply themselves on every order.

Spend ceiling: Member pricing is margin policy, so size spend against the margin at stake: glue in the low five figures is proportionate; a per-customer app fee that scales with your best segments is not.

What buying enables (top apps)

  • + Member tiers live this week, no dev hands required
  • + A bridge past the 3-catalog cap for non-Plus stores with many price lists
  • + Bundled extras — signup gating, wholesale order forms — some stores genuinely want

What building additionally unlocks

  • + Pricing by your exact tags, segments, and metafields — ladders no template anticipates
  • + Logged-in member prices rendered by the theme, not faked with duplicate variants
  • + Zero per-customer fees as the member base grows
  • + Tier-level margin analytics living in your own data

Find Your Verdict in 3 Questions

  1. Is the pricing for companies — wholesale accounts ordering on terms?

    Yes: Your verdict: CUSTOMIZE — native B2B catalogs have carried company pricing on every paid plan since April 2026; start there, not with an app.

    No: Go to question 2.

  2. Do more than three price lists need to exist store-wide on a non-Plus plan?

    Yes: Your verdict: BUY — the 3-catalog cap binds until Plus; a pricing app bridges the gap, so verify its exit path.

    No: Go to question 3.

  3. Do you have dev hands for a discount Function plus theme display?

    Yes: Your verdict: CUSTOMIZE — a Function prices member tags and the theme shows it; no subscription, no workarounds.

    No: Your verdict: BUY — a pricing app this quarter, with a diarized re-decision once a bench exists.

The TCC Scorecard — 12 Dimensions

TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →

DimensionBuyBuildWhy
Cost
Acquisition & implementationA pricing app configures tiers in days; the catalogs-plus-Function glue is an estimated 3–6 week build (Deploi estimate, illustrative).
Recurring feesPricing apps tier by customers or orders and bill forever; native catalogs and a deployed Function carry no subscription.
Maintenance & upgradesVendors patch around platform changes for you; your Function needs occasional redeploys on the ~6-month API cycle.
Switching & exitTag-pricing apps historically encode prices in duplicate variants or draft-order hooks that take real cleanup to unwind; catalog prices and Function config stay portable.
Risk
Vendor riskThe pricing-app category shrank when B2B went native in April 2026; betting margin rules on a shrinking category is real exposure.
Security & compliance surfaceCustomer-specific prices are commercial terms; fewer third parties reading your customer list and margins is the safer default.
Platform-deprecation exposureScripts-era pricing hacks died June 30, 2026; catalogs and discount Functions are the surfaces Shopify builds on now.
Value
Fit to requirementApps ship generic tier templates; a Function reads your tags, segments, and metafields and prices exactly your ladder.
Time to marketDays versus about a month — buy wins a member launch already promised.
Performance & scaleCatalog and Function pricing evaluates natively at cart and checkout; no injected scripts or duplicate-variant hacks weighing on the theme.
Data ownership & AI-readinessOwned member-price logic keys margin and uptake by tier in your own data — analysis a rented engine keeps to itself.
Focus & opportunity costGlue across catalogs, Functions, and theme display is real scope; buy if the bench is booked this quarter.

The App Landscape

AppStatusPricingBest for
Shopify B2B catalogs (native)NativeCompany-based price lists on all paid plans since 2026-04-02; 3-catalog system-wide cap on non-Plus (July 2026 research)Included with your Shopify planWholesale and company-account pricing without an app
Tag/member pricing apps (category)CategoryShortlist; probe for duplicate-variant or draft-order workarounds before trusting one$15–$150/mo bands (illustrative)Member tiers without dev hands, or past the 3-catalog cap
Discount Function + theme displayBuild laneThis page's customize path: segment-aware pricing logic plus logged-in price displayOne-time $8,000–$25,000 (Deploi estimate, illustrative)DTC member tiers priced by your own rules

The Build Path

  • B2B half: native catalogs: Company profiles plus catalogs price wholesale accounts on every paid plan; mind the 3-catalog system-wide cap off Plus when markets already use slots.
  • DTC half: discount Function on tags/segments: A Function reads customer tags, segment membership, or metafields and applies the member price automatically at cart and checkout — no codes.
  • Theme display for members: Logged-in members see their price on product and collection pages through theme logic — the display half apps often fake with duplicate variants.
Effort band
$8,000–$25,000 (Deploi estimate, illustrative); lands in the $10–25K contact-form band, more with heavy theme-display work
Typical timeline
3–6 weeks across the Function, catalog setup, and theme display (Deploi estimate, illustrative)
Maintenance, honestly
~15–20% of build cost per year (Deploi estimate): Function redeploys on the ~6-month API cycle and display checks at theme updates.
What you own — and what you take on
You own: the tier rules, the segment logic, the member-price display, and the margin data. You take on: keeping tags and segments clean — pricing logic is only as good as the customer data feeding it.

3-Year Total Cost of Capability

Buy (app path)Build (custom path)
Year 0 (setup)$200–$1,500$8,000–$25,000
Years 1–3 (recurring)$540–$5,400$4,000–$12,500 (maintenance)
3-year total≈$700–$6,900≈$12,000–$37,500
Illustrative cumulative cost over 36 months$0$6k$13k$19k$26kMo 0Mo 12Mo 24Mo 36Buy (app path)Build (custom path)
Illustrative cumulative cost: the app line stays lower at small member counts. The build's advantage arrives with growth — no per-customer fee on your best segments — and the primitives underneath are included with the plan either way.
  • All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
  • Buy path: mid-tier pricing app held flat; real per-customer tiers climb with the member base.
  • Build path: Function, catalog setup, and theme display; three-year horizon.

What the Sticker Price Hides

On the buy path

  • Legacy tag-pricing apps lean on duplicate-variant and draft-order workarounds that pollute the catalog and take real cleanup to unwind (community-reported pattern)
  • Per-customer and per-order tiers scale with exactly the segments you most want to grow
  • The category shrank when B2B went native in April 2026 — thin vendors consolidate or sunset, taking rule configs with them
  • Tier rules rarely export; switching apps means re-entering the ladder by hand

On the build path

  • Dirty tags produce wrong prices silently — tag governance is part of the build, not an afterthought
  • The 3-catalog cap is system-wide on non-Plus: markets, B2B, and member lists compete for the same three slots
  • Logged-in price display breaks at theme updates without a regression check (community-reported widget pattern)
  • ~15–20% of build cost per year in upkeep (Deploi estimate)

What Merchants Say

Wholesale threads keep relitigating the same trade-off: three native catalogs system-wide off Plus, so stores juggling markets plus member tiers hit the cap fast.
community-reported (2026 research corpus)
The app-era scar tissue: tag-pricing tools that cloned products or hijacked draft orders, then left duplicate-variant wreckage behind at uninstall.
app-store 1–2★ review theme

If You Change Your Mind Later

If you bought and outgrow it

Audit how the app encoded prices before uninstalling: duplicate variants, hidden products, and draft-order hooks all need cleanup, and member expectations outlive the tool (community-reported pattern). Export the tier rules, then rebuild them in catalogs and a Function.

If you built and want out

Catalog prices, customer tags, and Function config are portable Shopify-native state — retiring the glue leaves clean data behind. An app can even take over later; the tags and tiers it needs already exist.

When This Answer Changes

We're watching for:

  • The 3-catalog cap moving on non-Plus plans — check the changelog quarterly; it decides the BUY column's remaining case
  • Native B2B closing its at-scale gaps (500+ company rosters are a community-reported pain)
  • Discount Functions gaining richer segment inputs

Verdict change log:

  • 2026-04-02The wholesale half of member pricing became a platform primitive that day. What's left to pay for is glue — Function logic for DTC tags and theme display for logged-in prices — plus apps for stores the catalog cap genuinely binds.

Common Questions

Can Shopify show different prices to different customers natively?

Yes, in two halves. Company accounts get true price lists through native B2B catalogs, on every paid plan since April 2, 2026, capped at 3 catalogs system-wide off Plus. DTC member tiers run as automatic discounts from a Function reading customer tags or segments, with theme logic showing the member price to logged-in shoppers. Apps remain for stores the cap genuinely binds.

How does tag-based member pricing work without an app?

A discount Function reads the logged-in customer's tags, segment, or metafields and applies the member price automatically at cart and checkout — no codes, no duplicate variants. Theme logic renders the same price on product pages so members see their number before the cart. Budget an estimated $8,000–$25,000 for Function plus display (Deploi estimate, illustrative); Scripts, the old Plus route, stopped executing June 30, 2026.

When is a pricing app still the right call?

A pricing app wins in two cases: no dev hands with a member launch this month, or a non-Plus store needing more than 3 price lists once markets and B2B take their share. Before installing, probe how the app implements pricing — duplicate-variant and draft-order workarounds cost real cleanup at exit (community-reported pattern). Diary a re-decision for when either constraint lifts.

Your Next Steps

If you're going with CUSTOMIZE(matches your selected profile)

  1. Split the requirement: companies to native catalogs, DTC tiers to a discount Function
  2. Count catalog slots first — markets, B2B, and member lists share three off Plus
  3. Define tag and segment governance before writing any pricing logic
  4. Ship the Function, then the theme display; validate margin per tier in month one
  5. Add a theme-update regression check for the logged-in price display

If you're going with BUY

  1. Probe implementation before install: Functions-based beats duplicate-variant workarounds
  2. Price the per-customer tier at your projected member count, not today's
  3. Confirm what exports at exit — tier rules rarely do
  4. Diary a re-decision for when Plus, or a dev bench, arrives

Official Docs & Sources

Official documentation linked for verification — our verdicts and estimates are our own.

Ready to price members on primitives you own?

Catalogs price your companies, a Function prices your tiers, and your theme shows members their number. We wire the three together and leave the margin data with you.

Contact us today

Ecommerce development at Deploi

Verdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Full scoring anchors: see the TCC methodology.

Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.

No affiliate links. No paid placement. We make money building and integrating solutions — not on referral fees.