Ruby B2B storefront
The Ruby B2B storefront is enabled for B2B e-commerce. The sample B2B storefront is called Ruby B2B. The Ruby B2B storefront features include B2B features, in addition to all of the available features in the B2C storefront.
The following additional feature is included in the Ruby B2B storefront.
- Pricing and Catalog filters
Pages in the Ruby B2B storefront
- Registered user management
- Contract and Account selection
- Requisition lists
- Buyer registration for an organization (requires approval from Commerce Lab)
- Organization registration (requires approval from Commerce Lab)
- Registered organization management (requires approval from Commerce Lab)
- Register buyer organization (requires approval from Commerce Lab)
- Pricing and Catalog filters (enabled implicitly during shopping and checkout flows)
Flows in the Ruby B2B storefront
In addition to flows already available in the Ruby storefront, the following new flows are available in Ruby B2B storefront:
| Page | Flows |
|---|---|
|
|
Registration of new organizations and buyers
The storefront offers a user-friendly registration page that easily accommodates both organizational and buyer registrations. For more information, see Organization and buyer registration.
Organization and contract selection
The selected active organization and contract choices apply to the buyer's shopping and checkout processes. The selections impact the pricing displayed on products and the catalog available for the buyer throughout the shopping session, until the selections are changed.
The checkout flow also respects the pricing of the items when they are added to the buyer's order.
- To configure price rules with contracts, see Price rule assignment and contracts
- To index prices in the Elastic, see Indexing contract prices in
- To configure contracts with catalog filters, see Catalog filter assignment and contracts
- To use catalogs with the Elastic, see Storefront product/SKU data display logic
Limitations of contracts
If the buyer has a parent organization with two child organizations, creating a contract for the parent organization will make it visible to all child organizations. To restrict contract visibility to child organizations, administrator need to create a contract for respective child organization only.