Taking a Shopify Wholesale Storefront From $10k to $1M in a Year: What Actually Mattered

PravadaBeautyLabs.com, the wholesale storefront I launched for Pravada in Fort Myers, did about $10k in its first month and more than $1M in its first year. It ran on Shopify, with a catalog built on metafields, variant logic, and faceted collections, and a job-shop ERP wired in behind it so an order could reach production and labeling without a spreadsheet in the middle.

The revenue line is what people ask about. The useful part is which decisions carried it, which were decoration, and what I would do differently now that Shopify has moved its B2B tooling to every plan. I was Pravada's Director of Marketing & Technology from October 2020 to August 2025, so this is first-hand. Where I do not have a defensible number, I say so.

Context

Pravada is a Fort Myers manufacturer, as my own About page puts it, with two Shopify storefronts, and the domain names say what each is for: PravadaPrivateLabel.com for private-label buyers and PravadaBeautyLabs.com for wholesale beauty. I rebuilt the first with a custom Liquid theme and a section-based, responsive UX, and I designed, built, and launched the second. The wholesale site is the subject here.

A wholesale storefront has a different job from a retail one. The buyer is a business, ordering in quantity, usually on repeat, and they want to place the order at 11 p.m. without emailing a rep. The catalog is large, and the product data has to be right, because a wrong quantity on a case order costs more than on a single unit. And every order has to reach the floor, where someone makes it, labels it, and ships it; the storefront is worth little if that step still runs through a spreadsheet.

Native B2B on Shopify, meaning company accounts, price catalogs, and payment terms built into the platform, was a Plus feature for that whole window and did not exist at all for the early part of it: Shopify's April 2026 announcement says the features were "refined on Shopify Plus over nearly four years" before extending them to every plan, which puts their start around 2022. Every wholesale build in that window faced the same fork: pay for Plus, or solve access and pricing another way. I have no source for which route Pravada took at each stage, so I will not reconstruct it. What I can document is what shipped.

Approach

Six decisions, in rough order.

1. Sections, not one monolithic template. The theme work on my record is the PravadaPrivateLabel.com rebuild, a custom Liquid theme with a section-based, responsive UX; the wholesale site is on record only as a Shopify design-and-build, so I claim nothing more for it. The lesson holds on either site. In Shopify's theme architecture as documented in September 2026, a template is a JSON file that lists sections and their order, with limits of 25 sections per template and 50 blocks per section, and only JSON templates get section customization in the theme editor. Build the theme as sections and a product or collection page can be recomposed without a developer. The shape of a template, with illustrative section names:

{
  "sections": {
    "main": { "type": "main-product" },
    "wholesale-details": { "type": "wholesale-details" }
  },
  "order": ["main", "wholesale-details"]
}

I authored the product detail page components myself, because a wholesale buyer needs different answers on that page than a retail shopper: what changes between variants, and how many units they are committing to.

2. A catalog on metafields, variant logic, and faceted collections. Metafields are typed, validated custom fields on products, variants, customers, and other owners, readable in Liquid and the Storefront API and filterable once a definition exists. That is what turned a large catalog into something a buyer could work through alone: the attributes that matter for wholesale live on the product as data, the collections filter on them, and variant logic handles what differs within a line.

3. An ERP, so orders could ship. Operations ran on spreadsheets. I moved them to shopVOX, a cloud shop-management system built for sign, print, and custom-manufacturing shops, integrated Shopify with it, and standardized labeling on Zebra printers and GS1 barcodes. The storefront got the credit, but the ERP is why the revenue could be fulfilled. That rollout is its own case study. One caution: as of September 2026, shopVOX lists no native Shopify connector, so the bridge from a Shopify order to a shopVOX sales order runs through Zapier, as shopVOX's own how-to describes. Choose the ERP with the connector in mind.

4. Pricing models and reporting. I designed the pricing models and the financial reporting: unit economics, margin dashboards, and channel performance. A wholesale storefront makes it easy to sell at a loss without noticing, because a volume price set once keeps applying. The dashboards existed so a price change could be checked against margin.

5. A CRM with lead routing. Wholesale is still a sales motion. Over those years I implemented and managed HubSpot, Zoho, and Pipedrive with pipeline automation and lead routing, so a new inquiry landed with a person instead of in a shared inbox. A storefront is good at the tenth order. A CRM is what gets you the first one. The CRM playbook is the how.

6. Technical SEO and measurement. Structured data, Core Web Vitals work, and GA4 with Tag Manager, so a buyer searching for a supplier could find the site and the channel reports in point four had real numbers behind them. The GA4 setup guide covers the events worth defining before launch.

What changed

The only figures I will put in a table are the ones on the record.

	Before	After
Wholesale storefront	None	PravadaBeautyLabs.com on Shopify
Wholesale revenue	About $10k in month one	More than $1M in year one
Operations	Spreadsheets	shopVOX ERP, integrated with Shopify
Labeling	Unstandardized	Zebra printers, GS1 barcodes
Reporting	Not on the record	Unit economics, margin dashboards, channel performance

No conversion rate, order count, or average order value appears here, because I do not have a sourced figure I would defend in print. What I can add is my own ranking, from having been in the building, of what mattered. It is judgment, not measurement.

Lever	My call	Why
A storefront that takes orders around the clock	The precondition	Nothing below works without it.
Catalog structure: metafields, facets, variants	Carried the catalog	A buyer finds the SKU instead of calling to ask.
ERP integration and labeling	Let orders scale	It created no orders. It kept them shippable.
Pricing models and margin dashboards	Protected the margin	Revenue is easy to grow at a loss.
CRM lead routing	Brought new accounts	Reorders come from the site. First orders come from a person.
Technical SEO	Compounds slowly	Not a month-one lever.
Visual polish beyond clarity	Decoration	Structure mattered. The tenth round of styling did not.

What I would do differently

Start on native B2B. This is the big one, and it postdates the work. On 2026-04-02 Shopify extended core B2B to Basic, Grow, and Advanced at no extra cost: company profiles, up to three catalogs with tailored pricing, volume discounts and quantity rules, vaulted cards, and payment terms. For a manufacturer with a few price tiers, three catalogs is enough to launch.

As of September 2026, the plans are Basic at $39 a month ($29 annual), Grow at $105 ($79), Advanced at $399 ($299), and Plus from $2,300 a month on a three-year term. Then, the advice was "Plus, or a workaround." In 2026 it is "start on Grow and move up when the catalog count forces you."

Build sections as theme blocks. Theme blocks, in a theme's /blocks folder, are reusable across sections and can nest; section blocks are scoped to one section. Shopify's free Horizon theme is built on nested theme blocks, and its 4.2.0 release is dated 2026-09-18. I would still write custom components for a wholesale product page, but as blocks, so a collection page could reuse them.

Pick the ERP for its connector first. shopVOX was the right system for a shop that also runs an in-house print operation, and its PRO plan has API access. But if the storefront is the center of the business, the ERP's Shopify story is the first question. As of September 2026, Katana connects natively in both directions, orders in and stock levels out; Fishbowl has a plugin on its Advanced tier; NetSuite, Dynamics 365 Business Central, Brightpearl, Acumatica, and Infor M3 have certified connectors. A Zapier bridge works, and it is one more thing to break.

Write the metafield schema before the first product. As of September 2026, app-declared definitions are capped at 128 per owner type and 25 changes per deploy, so a catalog that grows by accident ends up with three fields that mean the same thing. Decide what a buyer filters on, name it once, and define it as filterable from the start.

Stack

• Shopify for both storefronts: a custom Liquid theme with a section-based UX on the Private Label rebuild; metafields, variant logic, and faceted collections on the catalog.
• shopVOX as the job-shop ERP, integrated with Shopify. As listed on shopvox.com in September 2026: Express $109 a month plus $29 per user; PRO $249 plus $49 per user, with API access.
• GS1 US for barcodes. As listed by GS1 US in September 2026, a single GTIN is $30 with no renewal, and a company prefix for 10 items is $250 with a $50 annual renewal. Every size, color, or pack-count variation needs its own GTIN.
• Zebra thermal printers driven by ZPL.
• HubSpot, Zoho, Pipedrive for pipeline automation and lead routing.
• GA4 and Google Tag Manager for measurement; structured data and Core Web Vitals on the storefront.

WBX Creative builds Shopify stores at $2,000 to $15,000 and up, as published on the pricing page in September 2026. The theme and catalog side is creative work; the ERP, CRM, and measurement wiring is technical. My background is on the bio page.