Explore the distinctive B2B features that set BigCommerce apart from Adobe Commerce (and Magento 2).
In this article, we discuss the differences between Adobe Commerce (formerly Magento 2) and BigCommerce in relation to B2B Features. You will see how each system behaves so you can determine which is a better fit for your needs.
One of our favorite questions to ask in B2B-related conversations is, "what is your pricing structure like?" While we did have the answer "there are no price differences" recently, this is quite unusual. The most common that we observe is unique lists of prices. Customers enter into different groupings based on order volume or other criteria. Of course, there are situations in which the final price is calculated, but it's rare (or impossible) that a system could natively accommodate these rules.
Utilizing a feature called Shared Catalogs, this is simply a usability varnish on the existing Tier Price features with one additional feature: you can enable/disable products and categories. You can apply discounts individually or across a group. Prices are changeable by website. These shared catalogs are assigned to companies.
Price Lists offer unique pricing per storefront, and customer group. Within a price list, prices can be entered per enabled currency. Administrators need to import via CSV to mass-assign pricing. Each product can have a discount or have a new price specified (the discount is auto-calculated).
Companies sometimes request a limited set of products, typically with highly negotiated prices. This makes it easier and reduces confusion for repeat buyers.
Shared Catalogs also allow you to exclude specific categories and/or products. Simply check or uncheck the boxes. Just so you know, for every new product you create, you need to manually associate each with shared catalogs.
Each customer group has a mechanism to allow access to specific categories. Once this override is enabled, every new category must be manually enabled in all applicable customer groups.
While we will dive into the unique details of the B2B purchase experience, it would be helpful to start with an overview.
Initialization process
Purchase process, from the buyer's perspective
Initialization process
Purchase process, from a junior buyer's perspective
Not every company has access to special features, such as payment terms, custom price lists, purchase order approvals, etc. B2B companies must be able to automate as much as makes sense for onboarding new customers.
New companies can fill out the below form. No customer accounts are created until an administrator manually approves the company. This form is only customizable by a developer. Individual/customer registration happens on a separate form.
Visitors are given a choice between company and individual registration. Store administrators can add new fields. Store administrators can assign a default price list and payment methods.
Businesses (usually) have a set number of shipment destinations. The ability to store a shared address book will save users time.
This capability does not exist out of the box.
Store administrators can select how addresses are shared and managed.
Some relationships involve specific types of payment and shipping methods.
Store administrators control a list of default payment and shipping methods. This can be overridden for each company.
When a company is created, it is assigned a default list of payment methods. Changing this default list does not affect existing company accounts. Shipping methods are not controlled at the company level.
Some companies require a process to ensure orders meet certain requirements.
Adobe Commerce has rich capabilities for this. Junior buyers can completely configure the order. The final step is to submit the purchase order for approval. Administrators can approve or reject with comments.
Junior buyers cannot make purchases. Instead, they add products to a shopping list. They send the shopping list for approval. The Company administrator adds these products to the cart and places the order.
Low-value orders may be automatically approved, while others may need review by specific parties.
Adobe Commerce has rich capabilities for this. Company administrators can create rules defining when orders require approval. These rules are based on order total, number of SKUs, or shipping amount. Administrators can also define who is capable of approving the order, making a way for tiered approvals.
Junior buyers can only add items to Shopping Lists for approval. There is no native capability for this.
In many cases, B2B extends terms to their customers. Being able to track this in an ecommerce environment reduces customer support inquiries.
Adobe Commerce provides customer reporting around terms. Store administrators can extend a credit limit to buyers (along with the capability to exceed that). There is no definition of time, for example, 30 days. Finance can notate payments which reduces the overall amount owed.
At the time of writing, Invoices are not possible with the new B2B User Portal. BigCommerce has the backend infrastructure, but this still needs to be exposed on the frontend. BigCommerce tracks payment terms. Customers can pay invoices directly on the website. This will be a robust feature when it is made available.
The sales or customer service team needs an easily accessible dashboard to review company status.
Out of all the great features that Adobe Commerce's B2B suite has, this is fairly lacking. While there is a place to edit company details, no additional information is present, like orders or links to individual customer accounts.
The Company Detail allows Store administrators to edit company information—but what details are editable is just as interesting: company users, super admins, shared address book, and uploads (upon registration, visitors can upload files). Additionally, BigCommerce allows you to associate Sales Staff with each company.
B2B often means customization. We first think of price lists, but we shouldn't stop there. How do we collect additional information in the checkout?
This is not a native feature of Adobe Commerce.
The B2B edition allows administrators to add custom fields to the Company, Address, Order, or Invoice forms. These values are reflected in Order Notes in the admin panel.
What if the buyer wishes to request a special price? In fact, some B2B websites only sell through a quoting process—usually to ensure the correct product is chosen for the given application.
Store administrators can enable quoting globally or for specific company accounts. Once products are in the cart, buyers can Request a Quote. Store administrators can configure discounts per item and per-quote discounts. They can set an expiration date, and add new products and comments with files. Every change is verbosely logged. This is designed to allow back-and-forth communication. Buyers can purchase at their convenience.
Buyers can add products to a quote on the product page or in the cart. Buyers can submit the quote at their convenience—including a message and files. Products can be added, quantities changed, prices adjusted, discounts applied and shipping applied. By adjusting the price, the discount percent is calculated. Once the quote is ready, the sales staff can send the quote in a rich email to the buyer (with the quote also attached as a PDF). Changes are tracked in the history, but they aren't detailed.
Some B2B buyers are considered power users, looking for fast ways to navigate the buying process. Quick order allows a buyer to search for or upload products in one form.
Adobe Commerce has an excellent search feature built into the quick order form. Buyers can easily upload a list of products.
The B2B edition has a useful feature in that it shows a list of previously ordered products (along with the date it was ordered). This allows for a quick, ad-hoc reordering process. Beyond this, buyers can search for products or upload a list of products.
Wouldn't it be nice to assign salespeople to specific accounts so they can manage the respective quotes and orders?
There is no native functionality for this.
Once salespeople have accounts for the BigCommerce store, they can then access the B2B Edition app. Store administrators will create each salesperson an account on the B2B Edition and assign them to specific companies.
Having a list of products from which you can consistently order saves time and reduces potentially costly mistakes.
Adobe Commerce calls this feature Requisition Lists. Buyers cannot share these with other team members. However, these lists can be exported.
Shopping lists provide a list of products that can be ordered. If a Junior Buyer creates a list, they must escalate to an administrator. However, these are not technically shareable.