Implement Variant Metafield as a Discount Type
complete
J
Jordan Aisbett
It would be beneficial if the Regios Discounts app could allow the use of variant metafields as referenced discount values directly in the Apply Discount step/node of the discount creation process. This would enable merchants to dynamically set prices based on metafield values, allowing for greater flexibility and automation in pricing strategies. Currently, with existing limitations, users are forced to rely on static values or complex setups that do not integrate well with their metafield-managed pricing strategies.
If you'd like us to add this feature to our app, please upvote and comment on this thread.
P.S. This feature request was generated via AI, based on the conversation with the customer.
Tobe Osakwe
updated the status to
complete
Great news: In the "Metafield discount" type, you can now define discounts that read their values from product or variant metafields.
Docs: https://regiostech.crisp.help/en/article/discount-value-options-in-regios-discounts-1wd2179/
P.S. One small favor: if you're satisfied with our app, a quick review would mean a lot to us. Takes under a minute: review link. No pressure at all!
Photo Viewer
View photos in a modal
Tobe Osakwe
Merged in a post:
Support for dynamic pricing from variant metafields in the Advanced Logic Builder
M
M.F. Bendix
As a user of the Advanced Logic Builder, I want the ability to dynamically pull prices from variant metafields, specifically using the metafield named 'custom.vip_price'. Currently, the functionality is limited, and the dynamic variable icon is not visible in the 'Apply Discount' node for mapping this metafield. It would be beneficial to allow this feature, enabling users to set prices directly from metafields in the discount logic.
If you'd like us to add this feature to our app, please upvote and comment on this thread.
P.S. This feature request was generated via AI, based on the conversation with the customer.
Tobe Osakwe
Merged in a post:
Apply a dynamic discount per customer
Y
Yann Fressignaud
Hi,
Concerning the 5 discount limit, I have a request : would it be possible for you to apply a dynamic discount based on a customer metafield ?
Indeed, I need to apply in Shopify the numerous contracts discounts I have (27).
Thanks
Raphael
Tobe Osakwe
Merged in a post:
Read discount value (per-SKU price) from a product/variant metafield — pricebook alternative to Price List CSV
M
Matt Lowe
> "the promo is HANDSFREE. i was able to get it to configure by removing anything i had 0 on hand for to lessen my list"
>
> "yes, its different pricing across different skus"
>
> "we have thousands of skus on each of our stores and most of our promotions are 'price pointed' which is just each SKU in the event will have a specific promotional price these could have anywhere from a handful of skus to hundreds (which is where we are running into this limit issue)."
Merchants like Dooney & Bourke / ILoveDooney are running into Shopify's 10KB discount configuration-size limit when they try to use the Price List CSV import for large, price-pointed promotions. Once an event gets into the hundreds of SKUs, the per-SKU price data no longer fits inside the discount config, so the discount cannot be saved.
They need one promo code per event, but splitting into two discounts would require two different codes, and Shopify does not allow two discounts to share a code.
What they want is a way to source the promotional price from a variant or product metafield instead of storing every SKU's price inside the discount configuration. Their Shopify rep suggested something like a variant metafield called
Event Price
and using Regios to read that value when the code is used.A Shopify-native equivalent to the SFCC pricebook workflow would solve this cleanly:
- The merchant stores per-SKU promotional prices in metafields, not in the discount config.
- A single code can drive per-SKU pricing across hundreds or thousands of SKUs.
- Monthly updates become much easier because the merchant can update metafields via Shopify bulk editor, Matrixify, or CSV, without re-importing a massive price list each time.
Desired behavior:
- Add a new discount value source for price/value from a product or variant metafield.
- Let the merchant specify the namespace and key, for example custom.event_price.
- Read the scalar per variant and plug it into the discount template, similar to the existing per-row price list workflow.
- Support code-triggered discounts.
- Items with no metafield value should simply not be discounted.
This would remove the SKU-count ceiling for price-pointed promotions and directly address a recurring support issue for large-catalog merchants.
If you'd like us to add this feature to our app, please upvote and comment on this thread.
P.S. This feature request was generated via AI, based on the conversation with the customer.
Tobe Osakwe
Merged in a post:
Enable discounts based on product metafield values for customer tags
L
Louis Sham
This customer requests the ability to set discounts based on product metafield values. For example, if a customer is tagged with c1, c2, or c3, the discount price should match the product metafield value. This allows for dynamic discounting based on individual product pricing, enhancing customer experience by providing personalized discounts based on membership or special pricing strategies.
If you'd like us to add this feature to our app, please upvote and comment on this thread.
P.S. This feature request was generated via AI, based on the conversation with the customer.
Tobe Osakwe
updated the status to
closed
Seun Oyebode
Customer context — variant metafield as price source
Came in via Crisp on 2026-04-29 (visitor231630). Merchant has variant metafields holding pre-calculated pack prices for quantity tiers — synced from their PIM (I want to believe this is their internal tool) as their single source of truth:
- custom.pack_price_10plus(number_decimal) — applies at qty ≥ 10
- custom.pack_price_20plus— applies at qty ≥ 20
- custom.pack_price_50plus— applies at qty ≥ 50
When a line hits a tier, they need Regios to set that line's unit price to the value in the matching variant metafield. Below qty 10, the standard variant price applies.
They already evaluated and rejected the existing options:
- Volume/tiered/quantity breaks — only takes static prices/percentages, no metafield reference
- Fixed price — static
- Price list — works but requires CSV imports, which breaks their PIM-as-single-source-of-truth model
What they're asking for is essentially the same architecture as the existing
Company metafield (B2B)
discount type, but reading from variant metafields instead of company metafields. The Discount template options we already have (Percentage / Fixed amount / Fixed price) cover the value semantics — Fixed price + variant metafield value would resolve their use case directly.Quantity-tier selection of
which
metafield key to read (e.g. read pack_price_50plus
at qty ≥ 50) would be the second piece, but isn't strictly required for v1 — a merchant with a single per-variant price metafield would already benefit from just the variant metafield discount type alone.Existing Metafield Discounts feature (product/variant metafield as eligibility filter) does
not
solve this — that gates which products qualify
, not what price to apply. Worth noting in case other tickets get misrouted there.Tobe Osakwe
Hi Raphael,
While you can only check one customer metafield per discount in our app, you can potentially use our advanced logic builder to apply different discounts based on which metafield value the customer has.
For example, if all of your contract discounts have the same key, you can chain together 27 "Check if" steps, using the "Then" and "Otherwise" options.
For a video and text tutorial on how to use the advanced logic builder, check here:
Best,
Tobe