How to Build a B2B Wholesale Marketplace Like Faire

Faire charges 25% commission on every new retailer order. On a $500 opening order, that's $125 going to a third-party platform. Multiply that across a $10M/year wholesale operation and you're handing $1.5M-$2.5M to a platform you don't control, can't customize, and can't exit without losing your retailer relationships.

That's why industry associations, buying groups, and vertical-specific operators build their own wholesale marketplace. The economics are strong. The technology is proven. The hard part is knowing what you're actually building.

According to Statista's 2024 B2B ecommerce report, global B2B ecommerce revenue surpassed $20 trillion in 2024 and is growing at roughly 18% per year. Wholesale marketplaces represent the fastest-growing segment within that number as distributors replace phone and fax ordering with digital platforms.

Who builds this (and why)

Faire dominates independent retail, but it doesn't own every vertical and it doesn't serve every use case.

Industry associations build a branded wholesale platform for their member brands. The Gift and Home Association, the Specialty Food Association, and dozens of vertical trade groups represent thousands of brands who all sell to the same pool of retailers. A branded platform keeps those transactions inside the association's own platform. Member brands pay lower commission than Faire. Retailers get curated access. The association earns revenue.

Distributors use wholesale platforms to replace phone orders and paper catalogs. A specialty food distributor with 200 brands and 1,000 retail accounts is still processing orders by fax and email. A wholesale portal cuts order processing time and gives brands visibility into sell-through.

Buying groups, like independent pharmacy co-ops or natural food cooperatives, aggregate purchasing power. A wholesale portal lets member retailers access negotiated pricing and consolidated ordering.

Vertical operators build niche marketplaces for categories Faire doesn't curate well: sustainable and ethical brands only, American-made products only, cannabis wholesale, artisan ceramics. The vertical focus is the product.

Brands that sell through distributors build direct wholesale portals to bypass the intermediary entirely. A brand paying 40% to a distributor can offer retailers 30% margin and keep 10% for themselves.

The business case is the same across all of them: capture the commission, control the relationship, own the data.

B2B is not B2C with a discount code

The biggest mistake teams make is treating a wholesale marketplace like a B2C store with lower prices. The structural differences run deep.

A B2C store sells one unit to any customer with a credit card. A wholesale marketplace sells to verified trade buyers in case quantities, on payment terms, at tiered prices that change based on order volume.

Minimum order quantities (MOQs) mean a retailer can't buy 3 units of a candle. They must buy a case of 12, or meet a $300 minimum order. Your cart logic must enforce this. Your UX must communicate it clearly before checkout.

Wholesale pricing tiers are not simply "half of retail." A brand might offer $8.50/unit for orders up to $500, $7.75/unit for $500-$2,000, and $7.00/unit above $2,000. These tiers can vary by product category, by retailer type, and by relationship status. The pricing engine is non-trivial.

Net payment terms mean a retailer orders $2,000 of goods today and pays in 30 or 60 days. This is standard in wholesale. Without it, many retailers won't buy. With it, you're either carrying credit risk or partnering with someone who will.

Trade account approval means not everyone can buy. Consumers cannot create accounts and place wholesale orders. The platform must verify that each buyer is a legitimate retail business.

Catalog visibility controls mean some products are wholesale-only. A brand might list their full consumer range on Shopify and restrict their wholesale line to approved retailers on your platform. Your catalog system needs to support that.

None of this exists in Shopify Plus, WooCommerce, or standard marketplace frameworks. It requires custom logic throughout.

The brand portal: where supply comes from

Brands are your supply. The brand portal must make it easy for brands to list, manage, and sell.

A brand creates an account and fills in their business details: company name, tax ID, shipping origin, lead times. Then they build their catalog. Each product listing includes the wholesale price, the MSRP (the price they recommend retailers charge consumers), the case pack size (must be ordered in multiples of 12 units, for example), the minimum order quantity, and available inventory. Brands upload product photos, spec sheets, and any retailer-facing marketing materials.

Brands manage their own catalog. When inventory runs out, the listing goes dark. When a new season launches, brands upload the new collection. Your brand portal is a lightweight PIM (product information management) system.

Brands also control order management. When a retailer places an order that includes their products, the brand receives notification, confirms they can fulfill it, and ships. Order statuses flow back to the retailer. Tracking numbers are attached. Brands see their earnings minus platform commission in a simple dashboard.

One critical feature: per-retailer access controls. Some brands want to control which retailers can see and buy their line. A prestige cookware brand might not want dollar stores purchasing their product. Your portal must let brands individually approve or block retailers from their catalog.

Retailer discovery and vetting

Anyone can browse product categories on a consumer marketplace. A wholesale marketplace is different: retailers apply to buy.

The application collects the business name, address, business license number or tax ID, and a link to the retailer's store or e-commerce site. The goal is to confirm this is a real retail business, not a consumer trying to buy wholesale.

For most platforms, manual review works at early stage. Someone reviews applications daily and approves or rejects. At scale, you integrate an automated business verification service (Middesk, Ekata) that confirms business registration and reduces fraud.

Approved retailers get access to the full catalog. Rejected applicants get a clear message and a path to reapply if their situation changes.

Inside the approved retailer experience, discovery works through product search and brand pages. A retailer searches for "beeswax candles" and sees all matching SKUs across brands, sorted by relevance, price, and lead time. They browse a brand's page and see their full wholesale catalog. Featured brand placement is a monetization option: brands pay for promoted positions in search results and category pages.

Product catalog and search

A wholesale marketplace catalog is different from a consumer store. Products have wholesale prices, MSRP, MOQs, case pack sizes, lead times, and country of origin. Retailers filter on all of them.

Algolia is the right tool for search at this scale. Indexing happens automatically when brands update products. Search results are instant. Faceted filters (category, price range, MOQ, country of origin, lead time, brand) work without page reloads. Typo tolerance handles "ceramics" and "ceramicss" equally.

Full-text search alone isn't enough. Retailers also browse by category hierarchy: Home > Kitchen > Cookware > Cast Iron. Your category taxonomy needs to be defined upfront and maintained. Brands assign their products to categories. Retailers navigate from broad to specific.

Order flow: the hard part

A retailer adds items from three brands to their cart. Each item has an MOQ. The cart validates that the retailer meets MOQ for each item. If they fall short, the cart shows a warning: "Add 4 more units of this item to meet the minimum." The retailer adjusts and proceeds.

At checkout, the retailer selects a payment method: credit card (Stripe) or Net terms. If they select Net terms and have an approved credit line, the order goes through and the platform pays the brands. The BNPL provider bills the retailer in 30 or 60 days.

The payment collection is one transaction to the platform. Behind it, the order splits into separate orders by brand. Brand A receives their line items and ships them. Brand B receives theirs. Brand C receives theirs. The retailer tracks all three shipments from a single order detail page.

Stripe Connect handles the financial routing. Each brand has a Stripe Connect account linked to your platform account. When the retailer's payment clears, the platform distributes brand payouts automatically, minus commission (15% on repeat orders, 25% on new retailer first orders in a Faire model, or whatever commission structure you choose). Payouts settle to brand bank accounts on a schedule you control.

Net terms financing

Net terms are not optional. They're why retailers choose wholesale over retail buying. A retailer who can pay in 60 days can place larger orders, manage cash flow, and reduce risk on new brand relationships. Resolve's 2023 B2B Payments Report found that 67% of independent retailers said Net terms availability was the primary factor in choosing a wholesale supplier over a competitor.

"Net terms in B2B wholesale aren't a courtesy. They're the reason a retailer can take a chance on a new brand. Remove them and you cut the addressable market in half." -- Resolve CEO Justin Straight, speaking at B2B Online Chicago 2023.

Building your own credit underwriting is expensive and regulated. The right approach is a B2B BNPL integration.

Resolve, Balance, and Behalf all offer API-based Net terms products. Here's how the integration works: when a retailer creates an account, they can apply for a Net terms credit line. The BNPL provider runs a business credit check (using the retailer's tax ID and business data). They assign a credit limit, say $5,000. The retailer can place orders up to that limit on Net terms.

At checkout, the retailer selects Net terms. The BNPL API confirms the order is within the credit limit and approves it. The BNPL provider pays your platform (same-day or next-day ACH). Your platform pays brands via Stripe Connect. The BNPL provider collects from the retailer in 30 or 60 days. Your platform carries zero credit risk.

The BNPL provider charges a fee (typically 2-4% of the transaction). You can absorb this in your commission or pass it to the retailer as a Net terms fee.

Returns and claims

Faire built a "risk-free ordering" policy for first orders: retailers can return unsold goods from new brands. This shifts inventory risk to Faire (and the brand) and makes it dramatically easier for retailers to try new brands.

Your return policy is a competitive decision, not a technical one. You can offer similar risk-free ordering for first brand orders. You can require brands to opt in. You can cap the return window (30 days from delivery) or limit it by category (perishables excluded).

The technical side is straightforward: claims are filed on the order, the platform reviews them, and approved claims trigger a return label generation and a credit memo. Credits reduce the next order's payment total or issue a refund. Tracking returns by brand and reason gives you data to manage brand quality over time.

Tech stack

React handles both the brand portal and the retailer buyer portal. Two separate frontends with a shared design system. Node.js handles the API layer: catalog management, order processing, account management, and payment routing. PostgreSQL is the primary database, handling orders, accounts, catalog data, and Net terms credit limits.

Algolia powers product search. The catalog is indexed automatically when brands update products. Search is instant with faceted filters. AWS S3 stores product images and spec sheets.

Stripe handles payment collection and Stripe Connect routes brand payouts. A B2B BNPL API (Resolve or Balance) handles Net terms underwriting and payment.

Timeline and cost

A full wholesale marketplace with brand portal, retailer portal, catalog search, order management, Net terms integration, and Stripe Connect payout routing takes 16-20 weeks and costs $160K-$240K.

The first four weeks cover architecture decisions, database schema, brand portal scaffolding, and retailer account management. Weeks five through ten build catalog management, product search, and the MOQ-aware cart. Weeks eleven through fourteen add checkout (Stripe + Net terms BNPL), order routing per brand, and payout automation. Weeks fifteen through twenty cover the brand order notification system, shipping tracking, returns, and admin tools for platform operators.

A proof-of-concept for a single category with 20-30 brands and no Net terms costs $80K-$120K in 10-12 weeks. That's enough to validate demand before committing to the full build.

Where builds break

Most wholesale marketplace failures are not technical. They're product and go-to-market failures. RaftLabs has built two-sided B2B platforms and the pattern is consistent: the technical architecture holds up. The marketplace dies for one of four avoidable commercial reasons.

The first is launching without enough brands. A marketplace with 10 brands is not a marketplace. Retailers open an account, see limited selection, and leave. The minimum viable catalog is category-dependent. For gifts and home, 50-100 brands is a floor. Get brand commitments before you build.

The second is launching without a Net terms option. Retailers expect it. Without it, they'll use your catalog to discover brands and place orders directly. You lose the commission and the transaction data.

The third is underestimating the brand portal. Brands need to be able to manage their catalog without calling support. If adding a product takes 20 minutes or requires help, brand supply quality degrades over time and new brands don't onboard.

The fourth is shipping without clear MOQ communication. Retailers add items, reach checkout, and discover they can't complete the order because they're short on a minimum. They abandon. Cart abandonment in wholesale is a UX problem, not a buyer problem.

None of these are hard to fix at the design stage. They're expensive to fix after launch.