How to choose a CMS for a B2B online store: company and contract
To understand how to choose a CMS for a B2B online store, start not with a module catalogue, but with who buys the goods: a person, a company or a division under a specific contract. The platform must retain these relationships and pass them to the business accounting system without manual guesswork. Only then should you compare built-in features, customisations and the full cost of launching.
Consider a hypothetical situation: a purchasing agent orders goods for a network of service centres. One centre receives the delivery, another legal entity pays, and the contract with the parent company determines the product range. If these relationships are stored in an order comment, the manager remains a translator between the website and accounting.
What to document before comparing CMS platforms
Describe the buyer as a set of related objects: contact, company, contract, payer and delivery location. Determine which can change independently and which must always remain linked. This is the initial data model: a clear outline of what the store needs to know about the transaction.
Take anonymised examples of current sales: “this employee buys for this company under this contract”. The commercial director confirms the business meaning, accounting confirms the payer, and the person responsible for the ERP, the enterprise's business accounting system, confirms the identifiers.
A person's user account is not the same as the buying company. A person may change jobs while the company retains its contract and purchasing history. A separate company record lets you change the contact without rewriting commercial relationships or moving orders between personal profiles.
- Can one contact represent several companies, and how do they select the buyer?
- Does the company have several contracts, and what rule determines which one applies?
- Are the payer, recipient and delivery address different?
- Where are the permitted product range and payment terms stored?
- Which identifiers link these objects to the ERP?
Why a group discount cannot replace a contract
A contract defines the sales context, while a discount changes only some of its terms. A group price list may suffice for straightforward wholesale sales; several agreements with different payers require a more explicit relationship.
A hypothetical distributor sells to a network under a main contract and to an individual service centre under a separate agreement. There is one purchasing agent, but the orders have different payers and permitted product ranges. A “wholesale customer” label does not explain which agreement to apply. You need a choice or an unambiguous rule that produces the same result in the catalogue, cart and ERP document.
A price list and a contract are different entities, even if they currently have a one-to-one relationship. A price list can change without a new contract, and a contract may stipulate terms not reflected in a product's price. So the specification should describe not the discount formula, but how the agreement is determined, where its terms come from and when it takes effect. An archived order must remain understandable after the next change to company details.
The CMS can store the agreement's identifier, status and parameters while the original document remains in another system.
What models do off-the-shelf solutions offer?
Compare platforms by how closely their buyer model matches your structure, not by the number of B2B items in a presentation. A ready-made model reduces design work if your business fits it. A flexible foundation is useful when relationships are unusual, but implementing those relationships requires separate work.
Shopify B2B and Adobe Commerce: from company to sales terms
Shopify B2B uses companies and their locations, while Adobe Commerce B2B uses company accounts. These are built-in product concepts, but they do not automatically map to your particular contract. Ask to see how the platform's objects correspond to your buyers.
In Shopify's documentation, a company brings together locations, each of which can have its own company details, addresses, contacts and payment terms. Do not automatically treat a location as merely a delivery warehouse: in the B2B model, it establishes the purchasing context. Check whether the required catalogue assignment method and other features are available on the selected plan, rather than relying on a general marketing list.
Adobe describes a Company account as a B2B foundation that brings together buyers from one company; the B2B extension must be installed and enabled. Shared Catalogs let you define product ranges and prices for companies. But neither a company profile nor a separate catalogue alone proves support for your multiple contracts: that scenario must be checked against the configuration and integration.
Drupal and Alternative Commerce: the model needs to be designed
Drupal provides entity, field and relationship mechanisms from which you can build the buyer structure you need. Alternative Commerce is GL.ua's Drupal-based solution using the Basket module, not another name for Drupal Commerce. A flexible foundation means that implementation is possible, not that all B2B features are ready after installation.
The official description of the Drupal AlternativeCommerce (Basket) module confirms extensibility through plugins, support for content types, a custom price field and orders. This description does not confirm a built-in company hierarchy or contract-specific price lists. In a proposal for this kind of store, separate the commerce foundation from the design of companies, contracts, interfaces and data exchange.
In a project with GL.ua, use the sales structure to determine the boundary between Drupal configuration and development. If another product's standard model covers your agreements, that is also an argument in its favour.
How to compare options against your model
Put the solutions into a table with the same business questions. Compare a complete store with the required configuration, not a basic licence against bespoke development. The following are guidelines, not a platform ranking.
| Question | Shopify B2B | Adobe Commerce B2B | Drupal + Alternative Commerce |
|---|---|---|---|
| Buyer foundation | Company and locations | Company account with buyers | The company structure is designed using Drupal's tools |
| Product range and prices | Catalogues; the assignment method depends on the plan | Shared Catalogs for companies | Basket's custom price field; B2B rules are confirmed separately |
| Several contracts for one buyer | Demonstrate the mapping to product objects | Demonstrate agreement selection and ERP data exchange | Describe and implement the required relationship |
| What to include in the estimate | Plan, configuration, apps, integration | Product, B2B extension, configuration and integration | Commerce foundation, B2B model, interfaces, integration and support |
A ready-made component and a complete sales process are not the same thing. A meaningful comparison needs an answer against every criterion: works out of the box, requires configuration, an extension or development. If the mechanism has not yet been determined, it is a research question, not a fulfilled requirement.
For an ecosystem you have already chosen, separate articles on checking Shopware B2B components and Salesforce B2B Commerce storefront architecture are relevant. Here, however, the decision comes earlier: which foundation can actually represent your commercial relationships without opaque workarounds?
What demonstration to request before choosing
Ask to walk through a purchase that reflects real business practice using anonymised data: from selecting the company to the document in the ERP. The aim is not to see every button in the customer account, but to see the buyer, contract and payer retained throughout the transaction. A solution prototype is sufficient for a feature that has not yet been implemented, but it cannot count as a completed integration.
- Prepare a company with several agreements and a separate buyer with a similar name. Assign different identifiers so that the result does not depend on matching text.
- Select the contact, company, contract and delivery location. Show where the available options come from and how users understand on whose behalf they are buying.
- Place an order and cross-check its identifiers against those in the ERP. A correct label on screen without the correct relationship in the document does not complete the demonstration.
- Change the contact or company details and open the previous order. Check whether you can explain who the buyer was when the order was placed.
- Compare what you have seen with the proposal: what already works, what will be configured, and what requires separate implementation and acceptance.
The outcome of the meeting is a verified fit with the business model, not an overall CMS score. If one legal entity requires several unconnected profiles, assess the implications for history and analytics before commissioning development.
What risks to consider in the store architecture
The company model affects integrations, data access, caching and the separation of public and restricted catalogues. Account for these implications in the architecture from the outset so that you do not have to rebuild the store after a successful purchase demonstration.
For integration, define the source of truth for each object: where a company is created, who changes a contract and how the website learns that it has been closed. Synchronisation must rely on stable identifiers, not just names. When a record has not yet been matched, an agreed action by a manager is needed, rather than automatically linking it to the first similarly named buyer.
For performance, test the catalogue with a personalised product range, not just the guest page. Results that depend on a company or contract require the corresponding separation of cached data. For security, the demonstration must include an attempt to open another buyer's order or terms through a direct link: hiding a menu item is not enough.
For SEO, separate public categories that attract new customers from personalised terms available after login. Do not create indexable copies of products for every business customer merely to offer different price lists. The details of roles and everyday account actions are a separate task, covered in the article on a B2B self-service portal.
What to pay for and when to commit to a launch date
Estimate the complete implementation of the model, and refine the schedule after checking the most complex relationship and data availability. The timeline depends on the state of the ERP, the list of contracts and the readiness of the client's team.
The estimate must include sales analysis, the company and agreement structure, configuration or development, the buyer-selection interface, record migration and cleansing, ERP data exchange, testing and launch. Separately compare recurring payments for the product and services, infrastructure, updates and maintenance of custom changes. A free commerce module does not make this work free; a commercial B2B component does not eliminate integration.
The work sequence is: agree on the model → map the data → prove the key purchase scenario → implement the remaining scenarios → migrate the data and accept the store. The design must accommodate company and contract selection.
Choose the simplest model that covers your sales, not the longest feature list. A simpler store may suffice for a single wholesale price list; several payers and contracts call for an explicit transaction structure. If you are planning a new B2B platform, discuss online store development with GL.ua (Glyanets) using your own purchase as an example: this will help define the required solution configuration and implementation scope before making a final choice of foundation.
Frequently asked questions
Do buyers need to see the internal contract number from the ERP?
Not necessarily: systems need the technical identifier, while people need a clear agreement name and buyer details. Agree separately on the value used for data exchange and the label in the customer account so that purchasing agents do not need to know internal codes.
What if a new company does not yet have a contract?
Provide a separate route for applying to do business, without substituting another company’s terms or arbitrary ones. The sales team must determine when an application becomes an active buyer and who confirms the available ordering methods.
Must wholesale prices be visible to all visitors?
No. This is a business decision that needs to be aligned with the public catalogue and customer acquisition. Visitors can see a product description and an invitation to do business, with personalised terms available after the company has been verified.
How do you migrate old orders without an identified contract?
Do not arbitrarily assign them to a current agreement. Agree on a rule for archived records: retain the original details, mark the relationship as unknown and allow clarification only on the basis of verified data.
Do retail and wholesale stores need separate CMS platforms?
Not always: the choice depends on how much the catalogue, data and sales rules have in common. Compare unified and separate implementations by their support for both scenarios, administrative work and synchronisation costs, not just the appearance of the storefronts.
Just one step to your perfect website



