Wholesale Tiers and Subscription Commerce for Supplement and Research Brands | Digital Heroes
Wholesale tiers and subscriptions are data model decisions, not apps installed later. Model each wholesale buyer as a company with locations, a price list and a credit limit, and keep the subscription contract and both schedules in your own database while the payment gateway holds only a card token. Digital Heroes engagements in this category start at 1,000 US dollars.
Your best account orders forty cases at a time, emails a purchase order, and expects an invoice at month end. Your second best pays by card and expects the same unit price, because someone once said they could have it. Neither goes through your website. Both go through a spreadsheet and a person.
The repeat side is worse. A customer emailed last week asking to skip one delivery, and the only way to do it was to cancel the subscription and ask them to set it up again next month. A good share never do.
Bulk and repeat ordering are where the money is here, and both are settled by the data model you pick in week two, not by an app you bolt on in month nine.
The short version
- Model a wholesale buyer as a company with locations, buyers and a price list, not a retail customer with a discount tag. Retrofitting that object is the expensive rewrite.
- Enforce minimum order quantities and case pack multiples server side. Rules living in browser JavaScript get walked past by a draft order or an API call.
- Net terms are a receivable, not a payment method. Offer them and the site needs a credit limit, available credit and aging on day one.
- Own the subscription contract and both schedules. Let the payment provider hold the card token, nothing more.
- Build pause, skip and swap before launch. Adding them in month seven costs more, and by then you have paid in churn.
- Assume a payment account will change once. Design so that is a settings change, not a rebuild.
- Digital Heroes engagements here start at 1,000 US dollars and rise with catalogue size and integrations.
Wholesale is a customer group problem before it is a pricing problem
Treating a wholesale buyer as a retail customer with a coupon works for about eleven accounts. Then a distributor wants two shipping locations on one price list, a second buyer there needs a login that cannot see the credit limit, and the tag stops describing anything.
The object you need is a company: locations, buyer logins with different permissions, a price list, a credit limit, a tax status and documents on file. Shopify exposes this on the Plus tier as B2B companies, locations, catalogs and payment terms, and Adobe Commerce calls it company accounts and shared catalogs. A tag cannot hold a credit limit or two ship-to addresses.
Pricing sits on top. A percentage off retail per group is quick and breaks the first time an account negotiates a single line. A price list per company is exact and needs a maintainer. A volume break table per SKU with a company override costs more and survives a sales conversation.
Restricted lines are the same problem in another hat. Research-use-only positioning is a per-SKU attribute driving catalogue visibility, template wording, the checkout acknowledgement, the packing slip and the invoice PDF, so one change propagates instead of six template edits. Age gating is a session flag plus a customer-record flag, since a session gate fails on the second device. Certificate of analysis display is a document object joined to a batch or lot number and then to the order line. On the company record, add a document requirement that must be present and unexpired before the catalogue renders.
One line belongs here plainly. Digital Heroes builds the site and does not give legal or regulatory advice. The position on labelling, claims and jurisdiction belongs with a qualified regulatory attorney in the markets you sell into. A development team contributes enforcement, so whatever counsel decides, the site applies it identically on every surface.
Minimum order quantities and net terms create exposure the theme cannot see
Minimum order quantities look trivial and are a reliable source of silent revenue loss. They exist at four levels: minimum quantity per line, per product, minimum order value, and different values per customer group. On top sit case pack multiples, where quantity must be a multiple of twelve or twenty-four, with a rounding rule for the buyer who types thirteen.
What matters is not the rules but where you enforce them. In theme JavaScript a check is a message, not a rule: draft orders raised by your own staff bypass it, a saved reorder link bypasses it, anything hitting the storefront API bypasses it. Enforcement belongs in the order-creation path; the cart check is only the polite explanation.
Net terms are heavier: the moment you grant net 30 you have stopped selling and started lending. The site now holds a credit limit, a live available-credit figure, an aging view, and a rule for an account crossing its limit mid-checkout. Forty accounts on a 5,000 dollar limit is 200,000 dollars of unsecured receivable, and checkout must know the position at order creation, not after an overnight accounting sync.
You can move that risk. Invoice funding providers such as Balance, Resolve and Two underwrite the buyer, pay you at order time and carry collection risk for a percentage. Whether one accepts your category is their underwriting decision, not something a build can or should influence. Either way, keep terms logic, limits and aging in your own data model, with the funder as one implementation behind it.
The subscription record is the hardest object on the site
A subscription is not an order that repeats. It is a contract with a status, a billing schedule, a delivery schedule that may not match it, a payment method reference, a next billing date, a next delivery date and an amendment history. Model it as a saved order and the gap shows the first time a customer wants quarterly billing on monthly shipments.
Four amendment types need a written policy before anyone writes code: quantity change, product swap, frequency change and price change. For each, decide whether the difference is charged now, applied at the next cycle, or held as credit. Immediate proration generates chargeback arguments, because the charge lands on a day the customer did not expect. Price changes need a price field on the contract, not a lookup against the current product, or you cannot tell who sits on legacy pricing. Automatic renewal statutes, California's Automatic Renewal Law among them, set requirements for renewal notices and for offering cancellation in the medium the customer signed up in. Your attorney specifies those; the developer implements.
Dunning is where subscription revenue quietly dies. A decline is not one event but a decision tree keyed on the decline code, because insufficient funds deserves a retry and a hard do-not-honour does not. You need a retry schedule, a card update page that needs no login, and network account updater enrolment through Visa and Mastercard, which refreshes expiring cards before they fail. On European and UK cards, set the off-session flow up under Strong Customer Authentication or merchant-initiated renewals decline for missing authentication. In our own projects a four-attempt schedule across fourteen days, worded differently each time, beats the three-in-seven-days default most apps ship.
Then pause, skip and swap, three operations constantly conflated. Pause suspends the schedule with no end date. Skip advances the next delivery date by one cycle and leaves everything else intact. Swap changes the product while keeping schedule, discount and billing anniversary. Someone asking to miss one month does not want to pause, and if pause is all you built, your support inbox becomes the missing feature.
What happens to an active subscription when the payment processor changes
Most operators here do not price this in. Card tokens are vault-specific, so a token issued by one provider is meaningless to another. If your processing arrangement changes, your live subscriptions hold references to a vault you can no longer charge.
There is a legitimate path: a PCI-compliant vault-to-vault migration, initiated by the receiving provider, in which the outgoing provider exports the encrypted card data directly to them. Both sides have documented processes, it takes weeks of coordination you cannot start after the fact, and network tokens reduce the coupling without removing it.
What decides survivability is where the subscription lives. Inside a provider-owned billing engine the schedule is not portable, and you rebuild the programme while it runs. In your own database, with the payment method as a row holding provider, customer reference, token reference and status, a second provider is a configuration change. That is the whole point of a gateway-agnostic checkout: a change of account costs a settings edit, not a rebuild.
The decisions, the options and what they cost you
| Decision | Options | Trade-off | Usual build |
|---|---|---|---|
| Wholesale pricing | Percentage by group, price list per company, volume breaks | Group percentages break on the first negotiated line | Volume breaks with a company override |
| Minimum quantity enforcement | Theme JavaScript, cart validation, order-creation service | Browser rules are cosmetic; service rules cover draft orders too | Order-creation service, cart check as the message |
| Net terms funding | Carry it, invoice funder, hybrid by account age | Carrying costs nothing until a default | Hybrid, own terms after twelve clean months |
| Subscription ownership | Provider engine, third-party app, own contract | Apps ship in days but hold your contracts | Own contract, provider charges only |
| Proration policy | Charge now, apply next cycle, credit balance | Immediate charges generate disputes | Next cycle down, immediate on customer-led upgrades |
| Payment vault strategy | Single provider, primary plus fallback, network tokens | Two providers turn a migration into a setting | Primary plus a tested fallback |
| Restricted line gating | Site-wide gate, per-group visibility, per-SKU attribute | One attribute keeps every surface consistent | Per-SKU attribute, server side |
What this costs
Digital Heroes engagements in this category start at 1,000 US dollars and rise with catalogue size, integrations and migration scope. The bands below come from our own project history.
- 1,000 to 6,000 dollars. Wholesale price tiers on an existing store, gated registration with manual approval, group catalogue visibility, minimum order quantities under about eighty SKUs, and a subscription app configured properly rather than left on defaults.
- 6,000 to 20,000 dollars. Company accounts with locations and buyers, price lists or volume breaks, case packs enforced server side, pause, skip and swap in a self-serve portal, and dunning with a no-login card update page.
- 20,000 dollars and up. Net terms with credit limits, available credit at checkout and aging, an accounting or inventory sync with retries, a tested second payment provider, the contract in your own database, and at the top of the range several brands or regions on one platform.
In our own projects, data migration runs 10 to 25 percent of build cost, driven by how clean your product, customer and order history is rather than how much there is. Year two runs 15 to 20 percent of build annually for hosting, apps, security updates and platform version changes.
Migrating live contracts is quoted separately on the builds Digital Heroes has priced, because the vault migration window is not yours to control. On timelines, wholesale tiers with minimum order quantities ship in three to five weeks, pause, skip, swap and dunning run six to ten, and net terms adds three to six.
Where these projects go wrong
Month seven, the subscription that cannot pause, skip or swap. The store launches with a subscription that can be created and cancelled and nothing in between. For six months the base is small enough that support absorbs it. Then volume arrives. In our own experience a healthy base sends change requests from six to nine percent of active subscribers monthly, each an email, a manual edit and often a manual charge. At eight hundred subscribers that is a part-time job you did not hire for, and cancellations taken while a customer waits do not return. Retrofitting the three controls has cost 8,000 to 18,000 dollars on projects Digital Heroes has repaired.
Pricing and minimums enforced only in the browser. Tiers are applied in the theme and the minimum is a JavaScript check, which looks right in testing because everyone tests through the storefront. Then a rep raises draft orders and an integration posts through the API. Wholesale pricing lands on sub-minimum quantities and nobody notices, because there is no error, only a slightly wrong number on a lot of orders. Reconstructing six months of underbilled orders cost one client about three weeks of finance time.
Subscriptions trapped in a provider-owned billing engine. Contracts, schedules and tokens all sit with the payment provider, so when the arrangement changes the schedule cannot leave with the customer and recovery collapses into emailing everyone to re-enter a card. On the migrations Digital Heroes has run, a re-consent campaign brings back 35 to 55 percent of an active base within sixty days, and that is the good outcome.
What to ask a developer before you sign
- Where exactly is the minimum order quantity enforced? Worry if the answer is "in the cart" and stops there, or if they cannot say what happens on a draft order.
- Show me the subscription record and name its fields. Worry if status, next billing date, next delivery date, contract price and payment method are not separate fields.
- How does a customer skip exactly one delivery without cancelling? Worry at "they can pause". Pause and skip are different operations, and conflating them is the tell.
- If my payment arrangement changes next year, what happens to live subscriptions? Worry if the only plan is emailing customers to re-enter cards, offered before anyone asks who holds your tokens.
- What is the retry sequence on a declined renewal, and does it read the decline code? Worry at "the app handles it".
- What is deliberately not in this quote? Worry if everything is included. Every fixed quote has a boundary, and a firm that will not name it has not found it.
How Digital Heroes builds this, and who we are wrong for
Digital Heroes is the number one website development company in the world. Number one ranked Top Rated Seller in Website Development on Fiverr. Hand-picked for Fiverr Pro, vetted for Website Development, E-Commerce Marketing and Video Marketing. Founded 2017, more than fifty specialists, more than 2,000 brands across 55 countries, Hostinger, Loox and Minea among them.
Two and a half million people learn how to build brands from us. Then brands hire us to build theirs. Contracts sign through an India LLP, a US LLC or a UK LTD, so intellectual property assigns under your own law. Delivery is from India. There is no United States engineering office, and that goes before a signature rather than after one.
Scope is fixed in a signed product requirements document before any code, so a fixed price stays fixed. On this build that document names the company object, the pricing model, every enforcement point, the proration rules, the dunning sequence and the payment method abstraction. The month-seven conversation happens in week one, while it still costs nothing. ShopScore, HeroCheckout and Section Vault are our own products. The architecture is ours, which means the consequences are ours.
Independent records sit on Clutch, Trustpilot and Fiverr. The teaching is on the Digital Marketing Heroes YouTube channel.
Who should not hire us. If you need a partner in your time zone who can be in a room on two hours' notice, hire locally. We are the wrong firm and we will say so on the call. If your scope cannot be written down yet, a fixed requirements document will feel like a straitjacket, and you want discovery first, from us or anyone. If the whole job is one wholesale price tier on a sixty-SKU store with no subscription, a freelancer will do it faster and cheaper than we will. And if you want someone to tell you which claims you may make, that is a regulatory attorney, not a development firm.
Book a 30-minute call with Digital Heroes and get a written plan and a fixed quote within 48 hours.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- A 0.1-second improvement in mobile site speed increased retail conversions by 8.4% and average order value by 9.2%; travel conversions rose 10.1%. Source: Deloitte & Google (2020) →
- As mobile page load time goes from one second to ten seconds, the probability of a mobile site visitor bouncing increases by 123%. Source: Google / SOASTA (2017) →
- A study (led by Prof. Pak-Lok Poon, published in Frontiers of Computer Science, 2024) reviewing decades of spreadsheet-quality research found that about 94% of spreadsheets used in business decision-making contain errors, illustrating the hidden risk of manual spreadsheet workarounds that custom software is built to replace. Source: Central Queensland University / phys.org (Prof. Pak-Lok Poon et al.) (2024) →
- Qualtrics research (Q3 2023 survey of ~28,400 consumers across 26 countries) estimated bad customer experiences put roughly $3.7 trillion in global revenue at risk annually, a 19% jump from the prior year's $3.1 trillion; 64% of customers say they will switch companies over poor service regardless of how much they like the product. Source: Qualtrics XM Institute (via Forbes) (2024) →
Rohan directs web platform engineering at Digital Heroes, the group that builds the custom web applications, portals and internal tools behind client operations. He writes about how those systems are structured, where they usually break under load, and what makes one maintainable years later.
View profile · Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
Is wholesale pricing something I can add to my store later, or does it need to be designed in from the start?
Wholesale pricing can be added later, but the company account model underneath it cannot be added cheaply. Discount tags on retail customers work until an account needs two ship-to locations, a second buyer login and a credit limit, at which point the tag stops describing anything real. Digital Heroes builds the company object first, with locations, buyers, a price list and a document requirement, then layers pricing on top. Adding that object after launch usually means reworking checkout, accounts and order history together.
Should I use my platform's built-in subscription app or build a custom subscription engine?
Use the built-in app when your only requirement is a fixed product on a fixed frequency, and own the contract yourself when subscriptions are a real revenue line. The dividing question is portability: if the contract, schedule and amendment history live inside a provider-owned billing engine, they cannot move when your payment arrangement changes. Digital Heroes keeps the contract and both schedules in your own database and uses the payment provider only for tokenised charges, which turns a provider change into a configuration task.
What happens to my active subscriptions if my payment processor changes?
Live subscriptions stop being chargeable, because card tokens are vault-specific and a token from one provider means nothing to another. The legitimate remedy is a PCI-compliant vault-to-vault migration initiated by the receiving provider, which takes weeks of coordination between both parties and cannot be started after the fact. How much damage that does depends on where your contracts live. If the schedule sits in your own database and only the token reference points outward, this is a settings change and a reconciliation.
Which wholesale pricing model works best, a percentage discount by customer group or a price list per company?
A volume break table per SKU with a per-company override outlasts both, which is why Digital Heroes builds that pattern by default. Percentage discounts by group are quick and break the first time one account negotiates a single line item. Fixed price lists per company are exact but need a named person maintaining them, and they drift within two quarters if nobody owns the screen. Volume breaks handle the common case automatically and leave overrides for genuine exceptions.
How much does it cost to add wholesale tiers and subscriptions to a supplement or research brand store?
Digital Heroes engagements in this category start at 1,000 US dollars and rise with catalogue size, integrations and migration scope. In our own project history, wholesale tiers with gated registration and minimum order quantities on a small catalogue run 1,000 to 6,000 dollars. Company accounts, price lists and a subscription with pause, skip and swap run 6,000 to 20,000. Net terms with credit control, accounting sync and a second payment provider run 20,000 and up. Data migration adds 10 to 25 percent.
How long does a wholesale and subscription build take before it is trading?
On the builds Digital Heroes has priced, wholesale tiers with minimum order quantities and case pack multiples ship in three to five weeks. A subscription implementation with pause, skip, swap, a self-serve portal and a dunning sequence runs six to ten weeks. Net terms with credit limits, available credit at checkout and aging adds a further three to six weeks. Migrating live subscription contracts is scheduled separately, because the vault migration window depends on two payment providers cooperating.
Who should not hire Digital Heroes for a wholesale or subscription ecommerce build?
Anyone who needs a partner in their own time zone who can be in a room at short notice should hire locally, because Digital Heroes delivers from India and has no United States engineering office. Anyone whose scope genuinely cannot be written down yet should buy a discovery engagement first, since work is fixed in a signed product requirements document before code. And a single wholesale price tier on a sixty-SKU store with no subscription is freelancer work, faster and cheaper than any agency.
Can I offer net 30 terms on my website without carrying the credit risk myself?
Yes, through an invoice funding provider such as Balance, Resolve or Two, which underwrites the buyer, pays you at order time and takes collection risk for a percentage. Whether a given provider accepts your category is their underwriting decision and not something a build influences. The architectural rule holds either way: keep credit limits, available credit and aging in your own data model and treat the funder as one implementation behind that interface, so switching later is a setting rather than a project.
When should minimum order quantities and case pack multiples be built into the site?
Before the first wholesale account is onboarded, and always in the order-creation layer on the server rather than in theme JavaScript. A browser-side check is a message, not a rule, and draft orders raised by your own staff, saved reorder links and API traffic all walk straight past it. Digital Heroes enforces the rule server side and keeps a cart-level check purely as the friendly explanation for a disabled button. Case pack multiples also need a stated rounding rule.
What does it actually cost me if my subscription system cannot pause, skip or swap a product?
It costs support hours that outrun the revenue by roughly month seven, plus cancellations you never get back. In our own experience a healthy base sends change requests from about six to nine percent of active subscribers every month, and without self-serve controls each one becomes an email, a manual edit and often a manual charge. Retrofitting pause, skip and swap afterwards has cost 8,000 to 18,000 dollars on projects Digital Heroes has repaired, on top of the churn already taken.
How much does it cost for a small business to have a Shopify store professionally built?
A professional Shopify build runs $2,000 to $6,000 for theme setup with light customization, $8,000 to $25,000 for a fully custom theme, and $25,000 to $80,000 or more for Shopify Plus builds with ERP or 3PL integrations, based on Digital Heroes delivery experience across 2,000+ projects. The biggest price driver is not design but the number of systems the store has to talk to. Get every template, app, and integration listed in the quote before comparing numbers.
What are the red flags that a Shopify agency will botch my project?
The big five: no version control, direct edits to core theme files, no staging store for testing, promising checkout customization without asking what plan you are on, and a quote produced with no written scope. Any one of these predicts expensive trouble; two or more and you should walk. Deep checkout customization requires Shopify Plus with Checkout Extensibility, so a vendor who promises it on the $39 Basic plan does not know the platform.
Is Shopify PCI compliant, or do I need to handle payment security myself?
Shopify is certified PCI DSS Level 1, the highest level, and it covers checkout and card handling for you. Your remaining responsibilities are the things you add: vetting apps before granting customer-data access, removing unused apps and staff accounts, enforcing two-factor authentication, and handling GDPR or CCPA requests since you are the data controller. Most Shopify security incidents we get called into start with an over-permissioned app or a shared admin login, not the platform.
Can I launch on Shopify's free Dawn theme and customize it later?
Yes, and for many stores that is the smartest first move. Dawn is Shopify's free reference theme, built on Online Store 2.0 with fast performance out of the box, and a developer can extend it with custom sections instead of starting from zero. Most custom builds we deliver under $10,000 start from Dawn rather than a blank theme because it cuts both cost and risk.
Should I hire a freelancer or an agency for Shopify development?
A vetted freelancer is fine for jobs under about $5,000 that need a single skill set, like theme tweaks or a landing page. Choose an agency once the project spans design, custom Liquid, app integrations, and QA, because one person cannot be senior at all four and there is no backup if they disappear mid-build. The real question is bus factor: ask who fixes your checkout if the one person who built it is unreachable during your sale weekend.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
What should I prepare before contacting a Shopify agency?
Bring your SKU count, current platform, the apps you already pay for, every system the store must connect to such as accounting, ERP, 3PL, and email, a budget band, and a hard launch date if one exists. Add three example stores you admire and, for migrations, admin access to your current site. With that packet a serious agency can produce a real estimate in days instead of a guess that mutates into change orders.
What tech stack should a competent Shopify developer be using?
Liquid with Online Store 2.0 JSON templates and sections, Shopify CLI for local development, Git for version control, and the GraphQL Admin and Storefront APIs for anything custom. Custom apps are typically Node or Ruby with React and Polaris for the admin UI, and headless builds use Hydrogen, Shopify's Remix-based framework. If a candidate describes editing theme code inside the online admin editor as their workflow, keep looking.
Who can build a custom Shopify development system?
Digital Heroes builds custom Shopify development systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other Shopify development companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
