A wholesale jewelry storefront on Magento (now sold as Adobe Commerce) comes down to two jobs: switch on and configure the B2B features that control who sees which prices, and feed the store clean, structured jewelry data so those prices and products stay accurate. The first job is a matter of settings. The second is where most jewelry projects slow down, and it is where we at JewelCloud put our effort: structured, standardized product data delivered to your store, so your team is not rebuilding attributes by hand.
This guide walks through the setup in the order you would do it, for retailers, brands, manufacturers and diamond dealers who want a trade-ready catalog.
TL;DR
- Shared catalogs, company accounts and negotiable quotes require the Adobe Commerce B2B extension, so confirm your edition and PHP version before anything else.
- Setting Enable Company to Yes turns on Shared Catalog, B2B Quotes and the B2B default payment and shipping methods in one move.
- Decide early where the authoritative price lives (your ERP or Commerce), because shared-catalog pricing overrides customer group pricing.
- Jewelry needs category-specific attributes (metal, purity, carat, certificate) and a feed that syncs inventory, or wholesale buyers see stale stock.
- A structured product feed from JewelCloud supplies the jewelry data layer so your Magento B2B rules have accurate products to work on.
Table of Contents
- What you need before you start
- Step 1: Turn on the B2B features
- Step 2: Build company accounts and buyer roles
- Step 3: Shared catalogs and wholesale pricing
- Step 4: Quotes, payment terms and approvals
- Step 5: Model jewelry products correctly
- Step 6: Connect supplier catalogs and live inventory
- Step 7: Test, secure and maintain
- Do you need a custom build?
- Our perspective
- Start with the data layer
- FAQ
- Sources
What you need before you start
B2B on Magento is not part of a bare install. Adobe’s catalog documentation states that shared catalogs, which let you give different companies curated assortments and custom pricing, require Adobe Commerce B2B licensing along with company accounts and Shared Catalog configuration.
Technically, the B2B extension is installed with Composer after Adobe Commerce itself. Version 1.5.0 requires PHP 8.1, 8.2 or 8.3. Ask your developer or host to confirm the PHP version in staging first, not on the live store.
Adobe’s pricing page lists company accounts, purchase approvals, quoting, requisition lists and payment on credit among the B2B operations of Adobe Commerce, with support for very large SKU counts and localized storefronts from one instance. For a jeweler with a deep catalog plus trade customers, that breadth is the reason to choose this platform.
Before you build, write down four decisions:
- Who your trade buyers are (independent retailers, designers, other dealers) and how you will approve them.
- Which products each group may see.
- How each group is priced.
- How they pay: card, invoice terms or a credit limit.
Every later setting follows from those answers.
Step 1: Turn on the B2B features
In the Admin, go to Stores > Settings > Configuration > General > B2B Features. Adobe’s documentation says setting Enable Company to Yes automatically enables Shared Catalog, B2B Quotes and the B2B default payment and shipping methods.
The same page recommends enabling direct product price assigning for Shared Catalogs when you manage many of them. If you plan one catalog per customer tier, or one per large account, turn that on from the start. Switching a catalog-heavy store over later is harder than starting with it.
Step 2: Build company accounts and buyer roles
The company account is the center of Magento B2B. Per Adobe’s B2B introduction, a company admin builds divisions, subdivisions and users with different roles and permissions that control ordering, quoting, purchasing and credit access. As the seller, you configure payment methods, pricing levels, quotes and requisition lists for each company.
The B2B REST API documentation describes the Company as the entity every other B2B feature depends on. Create your account structure before pricing or quotes, or you will rework them.
A workable jewelry pattern looks like this:
- Company admin: the store owner or purchasing manager at the retailer. Controls users and can approve spending.
- Buyers: staff who can build carts and request quotes, with order limits set by role.
- View-only users: a bookkeeper or merchandiser who needs to see orders and invoices but not place them.
If you want to vet who gets wholesale access, keep new company accounts pending until you have checked a resale certificate or trade reference. Decide that policy now so your team applies it consistently.
Step 3: Shared catalogs and wholesale pricing
A shared catalog is a curated set of products with its own pricing, assigned to one or more companies. In jewelry this is how you show a boutique your fashion line while a large chain sees your full bridal range and diamond inventory.
Pricing has a firm order of priority. Adobe’s advanced pricing documentation says tier and group pricing apply to simple, virtual, downloadable and bundle products, and that with B2B shared catalogs, custom shared-catalog pricing takes priority over customer group pricing. If you used customer groups for wholesale before, expect shared-catalog prices to win once a company is assigned.
A simple worked example: a gold chain lists at $480 retail. Your Preferred Retailer shared catalog carries a custom price for that SKU. A retailer assigned to that catalog sees the shared-catalog price even if their customer group also has a discount. Test that priority on a sample account before you load thousands of items.
The bigger question is where the authoritative price lives. A wholesale-portal guide on Adobe Commerce B2B advises deciding whether the ERP or Commerce is the source of truth before development, and planning ERP integration early, since availability, credit limits, payment terms, tax and order status can depend on ERP data. For metal-priced jewelry, where cost moves with the market, settle this early.
Step 4: Quotes, payment terms and approvals
Wholesale jewelry buyers rarely pay list price for large orders. Negotiable Quotes handle that. Adobe’s quote documentation explains that buyers and sellers can add items, change quantities and request or apply discounts until both agree. A quote can start from an authorized buyer’s cart or from a sales rep in the Admin, and the Admin Quotes grid keeps the communication history.
For payment terms, Payment on Account is the usual choice. According to Adobe’s B2B configuration guide, it is an offline method letting companies buy up to the credit limit set in their profile. You can enable it globally or per company. Know these details:
- New orders default to a Pending status.
- It is not supported for orders with multiple shipping addresses, which matters for chains shipping to several stores.
- Order approval works when you enable Enable Purchase Orders at the website level and in the company profile.
Set credit limits per company based on your own terms, and keep high-value diamond accounts on a separate approval rule from everyday findings buyers.
Step 5: Model jewelry products correctly
This is where generic setups fail. Rings, loose diamonds, gold chains and gemstone jewelry each need different fields. A ring needs metal, purity, stone details, ring size and often a certificate reference. A chain needs length, clasp and weight. Loose diamonds need carat, cut, color, clarity, dimensions and the grading report.

A practical rule: define mandatory fields per product category, and treat variants (ring size, chain length) separately from product-level attributes (metal type, stone, certificate). Run each record through the same routine: collect, validate, enrich, approve, publish, then watch for sync errors.
Then build filters shoppers and buyers actually use. If your attribute values are inconsistent, such as “14K”, “14kt” and “14 karat” as three separate values, faceted filters break and buyers cannot find product. Our guide on GIA-aligned Magento jewelry attributes shows how to keep that vocabulary consistent without remapping thousands of items, and our wholesale Magento jewelry catalog guide covers FTC-compliant and GIA-ready product pages.
Step 6: Connect supplier catalogs and live inventory
A wholesale store lives or dies on stock accuracy. If a buyer orders a piece your supplier sold out yesterday, you have a service problem and sometimes a lost account.
For ERP and inventory connections, Magento’s merchant documentation recommends a prebuilt connector, an integration platform or a direct API, validated in staging first. It suggests OAuth with least-privilege scopes, careful field mapping, and sync cadences of one or two catalog updates a day (or on change), hourly prices if needed, and inventory every 5 to 10 minutes.
Use that cadence as a starting point and adjust to how fast your suppliers change. If you source from several vendors, one shared SKU can be oversold; a master catalog approach prevents it, as we explain in our guide to multi-supplier jewelry inventory.
Our JewelCloud Product Feed delivers structured, standardized jewelry product data and inventory syncing from participating designers, manufacturers and diamond dealers, so you can expand your assortment without carrying physical stock. We also provide apps and plugins for Magento, among other platforms. For supplier field matching, see how to map supplier catalog data into shoppable sets, and for stones in particular, gemstone catalog management.

Diamond search and ring builders
Loose diamonds and bridal are where B2B buyers expect search by shape, carat, color, clarity and price, and a way to pair a stone with a setting. Our DiamondLink and RingBuilder tools are built for these jobs, and they sit on top of the same structured data, so your search results and product pages agree.
Step 7: Test, secure and maintain
Before launch, run a checklist in staging:
- Create two test companies in different shared catalogs and confirm each sees only its own products and prices.
- Place an order with Payment on Account and check the credit limit decreases.
- Start a negotiable quote from a buyer cart and complete it from the Admin.
- Change a supplier price and stock level and watch how long the store takes to reflect it.
- Check that every product page shows its required fields for its category.
B2B features also depend on background processing. Adobe’s install guide lists MySQL message-queue consumers behind them, including sharedCatalogUpdatePrice and sharedCatalogUpdateCategoryPermissions for Shared Catalogs, negotiableQuotePriceUpdate and quoteItemCleaner for Quotes, and inventoryQtyCounter for deferred stock updates, each started with bin/magento queue:consumers:start. If shared-catalog prices appear to lag, check that these consumers are running before you suspect the data.
After launch, treat the catalog as a living thing. Review sync error logs weekly, retire discontinued styles, and re-check pricing rules whenever you add a new customer tier.
Do you need a custom build?
Some retailers want the B2B logic and a polished storefront delivered together. Our Web Design for Jewelers service covers custom jewelry websites, and diamond dealers can look at websites for diamond suppliers. If you are comparing platforms first, our Shopify B2B jewelry setup guide shows the same job on a different system.
Our perspective
Most Magento B2B projects we hear about start with the settings and run into trouble with the data. Company accounts, shared catalogs and quotes are well documented and predictable. Jewelry attributes, certificates, stone details and changing supplier inventory are not, and they decide whether a wholesale buyer trusts your site.
That is why we built JewelCloud around structured, standardized, jewelry-specific product data. When the feed is accurate and consistent, your shared catalogs fill with products that already carry the right metal, stone and certificate fields, and your team spends its time on pricing strategy and customer relationships instead of spreadsheets.
Our advice: configure B2B features once, carefully, and let a purpose-built data layer keep the catalog current.
Anthony
Start with the data layer
If you are planning a Magento B2B jewelry store, begin with the product data. Our JewelCloud Product Feed gives your store structured jewelry product data from participating suppliers, with inventory syncing, ready for your shared catalogs.

Suppliers who want retailers to see their line can join through our vendor membership; the Silver plan is $1,500 per month. Visit JewelCloud to see which option fits.
FAQ
Do I need Adobe Commerce, or is open-source Magento enough for B2B?
Shared catalogs and company accounts require Adobe Commerce B2B licensing, according to Adobe’s catalog documentation. Confirm the edition and PHP version with your developer before you plan the build.
What is the first setting to change?
Set Enable Company to Yes under Stores > Settings > Configuration > General > B2B Features. That also enables Shared Catalog, B2B Quotes and the default B2B payment and shipping methods.
Which price does a wholesale buyer see?
If the buyer’s company is assigned to a shared catalog with custom pricing, that price takes priority over customer group pricing. Test this with a sample account before loading your full catalog.
How often should inventory sync?
Magento’s merchant documentation suggests inventory every 5 to 10 minutes, prices hourly if needed, and catalog data once or twice a day. Adjust to how quickly your suppliers change stock.
Sources
- Catalog Management Guide, Adobe Commerce
- Install the Adobe Commerce B2B extension
- Adobe Commerce Product Pricing
- Enable B2B features, Adobe Commerce
- Introduction to Adobe Commerce B2B
- B2B integrations, Adobe Developer
- Advanced pricing, Adobe Commerce
- Negotiable Quotes, Adobe Commerce
- How to Integrate with ERP Systems, Magento 2 Merchant Documentation
- Adobe Commerce B2B Features for Wholesale Portals

