Metafield-Based Product Targeting: Let Your ERP Drive Shopify Discounts

Introduction

Every growing Shopify catalog eventually collides with the same operational wall: the products are governed by one system, while the promotions are governed by another. For enterprise wholesalers, product truth lives in the ERP. Costs, suppliers, categories, contract eligibility, pricing groups: all of it is already classified, already maintained, already correct. Yet most discount tooling asks merchants to rebuild that intelligence by hand, one collection or product tag at a time.

Instead of asking:

"Which products should receive this discount?"

a solutions architect asks:

"What business rule should define this campaign?"

That shift is the entire architecture. This case study designs a wholesale pricing system in which the ERP keeps making the decisions and Discount Prime simply executes them, using metafield-based product targeting.

Merchant Scenario

Consider Atlas Industrial Group, an enterprise wholesale distributor supplying industrial equipment across North America.

Every product in Shopify originates in the ERP: names, inventory, cost, supplier, category, availability, and above all the pricing group that decides how each product may be sold. Only one thing does not live there: promotional rules. Those were rebuilt inside Shopify, by hand, every week.

The Synchronization Problem

The marketing team launches new wholesale campaigns every month, and eligibility changes constantly. Some products qualify for distributor pricing. Others belong to government contracts and can never be promoted. To keep campaigns accurate, employees manually mirror the ERP: collections rebuilt, tags added, products imported, campaigns edited. Hours of work reproduce answers the ERP already holds.

The breaking point arrives during a quarterly promotion, when more than 7,000 products change pricing eligibility at once. The ERP updates every record automatically. Shopify does not. The team spends nearly two full days rebuilding collections, and by the time they finish, the ERP has already changed hundreds of products again.

The business is not struggling with pricing. It is struggling with synchronization.

Business Objectives

Option 1: Manual Collections

Build a Shopify collection per campaign and rebuild it whenever eligibility changes.

Option 2: Tag-Based Targeting

Push a promotional tag from the ERP and target campaigns at that tag.

Option 3: Metafield-Based Targeting

The ERP synchronizes one structured field, pricing_group, with every product. Inside Discount Prime, the wholesale campaign targets products where pricing_group = dealer. That is the entire rule.

Comparison Matrix

The Discount Prime Architecture

The final design keeps one metafield as the bridge and lets each pricing_group value drive its own campaign.

One Metafield, Six Pricing Models

The same field supports every commercial program the ERP already tracks.

Marketing no longer manages products. It manages business logic.

Customer Journey

Walk through a dealer purchase after the redesign.

1. A purchasing manager logs in. Her account carries the dealer customer tag, so the Dealer Wholesale Pricing campaign activates.
2. She opens an industrial fastener kit: list price $148.00, Shopify cost price $96.20, pricing_group = dealer.
3. The campaign applies the dealer tier automatically. No code, no request, no sales rep.
4. She orders 40 units and checks out.

Three weeks later a supplier introduces a new product line. The ERP assigns pricing_group = dealer, the nightly sync completes, and every new product is priced correctly the moment it appears. No campaign edits. No forgotten products.

Measuring Success

Track operational metrics alongside financial ones:

• Hours spent per month on campaign maintenance
• Time from ERP change to storefront eligibility
• Pricing eligibility errors per quarter
• Estimated Profit per campaign in profit analytics
• Margin health distribution (Healthy / Thin Margin / Loss)
• Dealer reorder frequency

The first three should trend toward zero effort. The last three prove the pricing itself stays sound.

Common Mistakes

• ❌ Building collections that exist only to feed discounts.
• ❌ Duplicating ERP business rules inside Shopify.
• ❌ Maintaining promotional eligibility in spreadsheets.
• ❌ Editing product tags by hand after every ERP update.
• ❌ Letting campaign complexity grow with catalog size.

Key Lessons

Atlas did not automate discounts. It automated decision making. The ERP already knew every answer; Discount Prime did not need to replace that intelligence, only to read it. When a campaign is defined by a metafield rule instead of a product list, growth stops creating operational work: the rule for 92,000 products is the same rule for 500,000.

Metafields bridge two worlds that should never merge. Business logic stays inside enterprise systems. Customer pricing stays inside Shopify.

Conclusion

Enterprise commerce is not about managing more products. It is about managing fewer decisions. When promotional logic already exists inside an ERP, rebuilding it inside Shopify creates cost, delay, and error. Metafield-based product targeting lets the ERP remain the single source of truth while Wholesale / B2B Pricing, Bulk Price Update, and conflict detection execute the strategy automatically.

Once the campaign is defined by a business rule rather than a product list, everything else becomes automation.