Guidelines
17-Nov-2026
Guide - PWA B2B Storefront Functionality
Document Properties
Kbid
L47880
Added to KB
21-Nov-2025
Status
online
Product
Intershop Progressive Web App
Last Modified
17-Nov-2026
Public Access
everyone
Doc Type
Guidelines
Document Link
https://knowledge.intershop.com/kb/L47880

Introduction

This guide describes the out-of-the-box storefront functionality of the Intershop Progressive Web App (PWA) for B2B customers.

For the Responsive Starter Store, refer to Guide - B2B Storefront Functionality (valid from 7.10.17).

Permissions and Roles

The B2B storefront supports the following roles and permissions:

Role

Description

PURCHASE

MANAGE USERS

ORDER APPROVAL

MANAGE OWN QUOTES

MANAGE COST CENTER

Buyer

can place orders and quotes

(tick)

(error)

(error)

(tick)

(error)

Approver

can approve orders of buyers

(tick)

(error)

(tick)

(tick)

(error)

Cost Center Manager

can manage cost centers of the customer organization

(tick)

(error)

(error)

(tick)

(tick)

Account Admin

can manage all aspects of the customer organization

(tick)

(tick)

(tick)

(tick)

(tick)

My Account - Dashboard

The My Account overview page provides a dashboard for B2B users. The displayed information depends on the user's assigned role. The following sections may be available:

  • My Budget

  • My Requisitions

  • My Cost Centers (only available for Cost Center Manager / Account Admin)

  • My Approvals (only available for Approver / Cost Center Manager / Account Admin)

  • My Quotes

  • My Order Templates

  • Most Recent Orders

My Account - Navigation

The navigation section of the My Account area contains the following information:

  • The customer which the currently logged in user belongs to

  • The role(s) of the currently logged in user

  • Separate sections based on user roles

Quotes

Quotes are used for price negotiations between the customer and the merchant.

Flow

While there are more complicated processes possible, the current implementation is intentionally kept simple.

Storefront

The current implementation recommends that the user is logged in before doing anything. After logging in, the user can:

  • Create new quotes (only one active new quote is allowed at a time, the quote behaves like a shopping cart).
  • Submit / delete / refuse a quote.
  • See/manage the list of quotes in the My Account section.
  • See the quote request details in the My Account section.

Commerce Management Application

The current implementation supports the following administrative tasks:

  • A quote manager can see a list of quotes.

  • The quote manager needs to be assigned to the customer to see a customers quotes.

  • The quote manager can reject/edit/submit a quote.

Limitations

In the ICM standard implementation quotes and recurring orders are incompatible.

Generally, a recurring order is a one-time triggered, but periodically executed purchase of certain products or services. In subscription-based business models, consequently, customers pay periodically to use or receive a defined set of products at a regular base.

The B2X edition of Intershop Commerce Management supports subscription models via recurring orders.

Note

Recurring orders do not work with quotes and vice versa. That is, one cannot create a recurring order from a cart that contains a quote. The other way around, a quote cannot be added to a cart if it is already marked as recurrent.

Registration in Storefront

When a new user registers in the storefront, they are prompted to enter the name of their organization. The system then creates this organization, and the user is assigned the role of Account Admin.

As an account admin, this user can add additional users and assign them specific roles in the User Management section of the My Account area.

User Management

The B2B storefront contains a management section for users of a customer organization, where administrators of the organization can create and manage users.

Creating Users

Administrators can create new users of an organization from the user list. New users will receive an e-mail in order to provide a password and login.

Managing User Roles and Budgets

In addition to creating and deleting users, you can manage the roles assigned to an individual user.

Furthermore, you can set budget limits for individual users. 

User Roles

The roles assigned to a user define what a user is allowed to do in the storefront. The buyer role is always assigned to a user. Additional roles can be assigned to perform specific tasks, such as approving orders or managing cost centers.

User Budget and Order Spend Limit

User budgets and order spend limits can be defined separately for each user. If defined, these values are used to decide whether an order requires approval or not. An approval is necessary if one or both values are exceeded. If no values are defined, orders can be placed without approval. For more information, see Order Approval.

There are jobs which are created with the purpose to reset the user budgets at the end/start of each period. The following budget types are available: yearly, half-yearly, quarterly, monthly, and weekly.
The names of the corresponding job configurations are: ResetYearlyBudgetsSpentJob,ResetHalfYearlyBudgetsSpentJob,ResetQuarterlyBudgetsSpentJob, ResetMonthlyBudgetsSpentJob, and ResetWeeklyBudgetsSpentJob. They can be found in the Intershop System Management's Schedules | Scheduling menu item under root domain:

By default these jobs are disabled. This can remain as it is if user budgets are not used. If user budgets are used, these jobs need to be configured once. To do this, click on the desired one to enter the job configuration details page:

On the job configuration details page:

  • Select the Enabled checkbox.

  • Choose the Recurring Interval option.

  • Configure the desired interval when the job is planned to run (e.g., for weekly on Monday, 01:00:00 am; for monthly Every 1 Months; for quarterly Every 3 Months).

This way, resetting of user budgets will be performed automatically at the desired time. It is not necessary to configure all three jobs if, for example, only one type of budget period is used. For example, if weekly is the only type available, then ResetYearlyBudgetsSpentJob,ResetHalfYearlyBudgetsSpentJob,ResetQuarterlyBudgetsSpentJob, and ResetMonthlyBudgetsSpentJob can remain disabled.

Activating and Deactivating Users

In the Edit User Profile dialog it is possible to activate and deactivate a user. Deactivated users are not able to log in.

Deleting Users

Administrators can delete users, e.g., in case they left the company. This can be done from the user list by clicking on the delete icon.

Note

Interference between recurring orders and user assignment:

Orders created from a recurring order belong to the user who created the corresponding recurring order. If a user is deleted, that user's recurring orders are also deleted.

Cost Centers

Cost centers allow customer organizations to track purchases according to their internal cost accounting and ensure purchases align with defined budgets.

Customer organization administrators can create, edit, and delete cost centers. They can also assign a cost center owner and buyers to each cost center.

Cost centers can be activated and deactivated to adapt to changes in a customer organization's accounting.

Cost Center Management

Cost centers can be managed in the Cost Centers section of My Account. Administrators and Cost Center Managers can create, edit, activate/deactivate, and delete cost centers here and get an overview of the amount of orders and spent budget per cost center.

Create Cost Centers

Cost center managers and administrators can create new cost centers from the Cost Center list. A cost center must have a unique ID within the customer organization, a name, and cost center manager defined that approves or rejects all orders placed for this cost center.

Note

Only users with the role Cost Center Manager assigned can be set as a cost center manager for a specific cost center. In addition, a budget can be defined for cost centers.

Delete Cost Centers

Administrators or Cost Center Managers can delete cost centers that are no longer needed by clicking on the delete icon in the Cost Centers list.

Deactivate/Reactivate Cost Centers

Cost centers that are not needed now but should be saved for later use or to see all orders placed for this cost center later on, can be deactivated and reactivated again by clicking on the on the deactivate/reactivate icon in the Cost Centers list.

Add Buyers to a Cost Center

Adding buyers to a cost center can be done in the Add Buyers dialog. To open the dialog, click Add in the buyers section of the cost center details page.

Edit Buyer Budgets

Editing a buyer's budget is achieved by the Edit Budget dialog. To open the dialog, click the Edit button next to each buyer in the cost center details page.

Assigning Orders to Cost Centers

Buyers can select a cost center for their order in the shopping cart. 

If a buyer has cost centers assigned, the selection of a cost center for an order is mandatory. Otherwise, an order could be placed without providing a cost center.

Note

Deactivated cost centers cannot be selected in the shopping cart.

Note

Interference between recurring orders and cost center assignment:

Orders created from a recurring order belong to the cost center to which they were initially assigned. A recurring order can create future orders even if the initial cost center is deactivated or deleted.

Therefore, cancel all recurring orders for a cost center before deactivating or deleting it.

Cost Center Budgets

Budgets can be defined for the cost center itself and specifically for each buyer of the cost center. Budget periods can be set to yearly, half-yearly, quarterly, monthly, weekly, or fixed. Recurring budgets are automatically reset at the end of the defined period.

Interactions of Budgets and Recurring Orders

Generally, a recurring order is a one-time triggered, but periodically executed purchase of certain products or services. In subscription-based business models, consequently, customers pay periodically to use or receive a defined set of products at a regular base.

Note

Once the recurring order is approved, all subsequent orders created by this recurring order do not require any additional approval. While such a order created by recurring order reduces the budget, the recurring order itself will not be checked against the budget. That is, the recurring order will be placed even if it exceeds the budget.

Cost Center Approval

When an order is assigned to a cost center the approval from the cost center owner is required, regardless of the cost center budget or the user-specific cost center budget. The cost center owner receives information about already spent total cost center and user-specific cost center budgets in context of the order approval. Based on this, the order can be approved or rejected. The reason for a rejection can be captured by a comment.

Note

Cost Center Managers can approve their own orders.

Order Templates

The order templates feature allows the customer to collect products in a special product list to order them later or more than once. Adding products to an order template always requires selecting an order template by name or creating a new one. Order templates can be managed (create, update delete) in the My Account section. They can be added to the cart completely. And the cart can be saved into an order template.

Order Approval

B2B customer organizations can use order approval to check orders before they are placed. The approval contains two checks, one for cost center specific approval and one to check orders against a user's budget and order spend limit. Using the order approval is optional. If no budgets and spend limits are defined for users and no cost centers are defined for a user, orders are placed without approval.

Whenever an order requires approval due to exceeding the user's spend limit or budget, an e-mail is sent to all users with either the Approver role or the Administrator role. These users also see all orders requiring approval in their Dashboard and Approvals section of My Account. Approvers can either approve or reject an order. If an order is approved, it is placed automatically. If an approver rejects an order, a reason for the rejection can be provided.

Users can see a list of pending, approved, and rejected orders in the My Account section.

Particularities for the Approval of Recurring Orders

Generally, a recurring order is a one-time triggered, but periodically executed purchase of certain products or services. In subscription-based business models, consequently, customers pay periodically to use or receive a defined set of products at a regular base.

The B2X edition of Intershop Commerce Management supports subscription models via recurring orders.

Recurring orders have different approval rules compared to one-time purchases.

  • The user-specific order approval is always required irrespective of the configured budget.

  • The approval page for the approver shows the recurrence information, so that the approver is aware to approve a recurring order.

  • The responsible cost center manager must also approve the recurring order.

Note

A recurring order, which was once approved through all instances, never needs an additional approval, even if the recurring order was deactivated and reactivated later on.

Quick Order

It is possible to add multiple products to the cart or a quote request at once by entering product ID and quantity via the Quick Order functionality.

By default, the user can add five products. Clicking Add 5 more rows extends the form by five additional lines, each with input fields for product ID and quantity.

Using the CSV import, you can import a customizable number of products in one step, just by providing a CSV file (encoding UTF-8). Find a sample CSV import file in the following zip file: quickorder.zip

The quick order functionality was also implemented at the cart page with the restriction of only one product at the time.

Order Search Enhancements

The order search in the Order History of My Account enables you to search by order number, product ID, buyer name, and/or a specific time frame.

Punchout

Punchout allows an external procurement system to connect to the storefront as a catalog, add products to a cart, and transfer that cart back for further processing (e.g., in an ERP or procurement system). The storefront supports two standard punchout formats:

  • OCI Punchout (Open Catalog Interface)

  • cXML Punchout (commerce eXtensible Markup Language)

Both formats share the same general workflow (login as a punchout user → browse/shop → transfer cart), but differ in authentication fields, session setup, and the transfer format of the resulting cart data.

The Punchout functionality in the Intershop PWA is not enabled by default. It is controlled by a feature toggle and must be explicitly activated during deployment. In addition to the feature toggle, a matching identity provider configuration is required for the SSR and NGINX layers. See this guide for more information.

cXML Punchout

cXML (commerce eXtensible Markup Language) is one of the standard formats for connecting to external punchout catalogs. The cXML punchout format allows to transfer data of a shopping cart from the external catalog to other systems (e.g., ERP, Procurement System).

References

Enable cXML Punchout

To use the cXML punchout functionality as a customer, at least one user with the role "cXML Punchout User" must exist. The first cXML punchout user can be created by the Account Admin on the My Account | Punchout | cXML tab. The cXML punchout user is usually not related to a dedicated storefront user. External procurement systems use one punchout account for multiple employees. Therefore, a cXML punchout user does not need profile settings like first name, last name, addresses, or date of birth, and other. Only login and password are required.

grafik-20260824-135302.png

cXML Punchout Information

The required information (setup request URL) to configure the external procurement system is shown on the cXML tab of the Punchout overview page:

{restUrl}/customers/{customerNo}/punchouts/cxml{version}/setuprequest

The credentials must be specified in the Sender section of the cXML SetupRequest document: the username as Identity and the password as SharedSecret.

grafik-20260824-135711.png

cXML Punchout Profile Settings

The pencil icon to the right of a cXML user opens a single edit form for that user. Use it to change the password (and confirm it) and toggle the active flag. The login cannot be changed once the user has been created. There is no separate e-mail address to edit — cXML punchout users do not have a user-facing e-mail address.

Match the username to your login type preference, e.g., use an email address for logins based on email addresses.

grafik-20260824-135641.png

cXML Punchout Storefront (Outbound Section)

The available storefront functionality of a cXML punchout user is only a subset compared to a regular storefront user.

The following areas are examples of hidden functionalities:

  • My Purchases (Orders, Recurring Orders, Requisitions, Quotes, Order Templates submenu entry, Wishlists)

  • My Approvals

  • My Organization (Addresses, Users, Cost Centers, Punchout, Organization Settings)

  • My Profile (Payment, Notifications, Profile)

  • Page footer

  • Create Quote functionality on product or cart page

  • Checkout button on the cart page (replaced by the Transfer Cart button)

  • Payment section on the cart page

  • Recurring-order editing on the cart page

grafik-20260824-140427.png

The user can browse or search for products and add items to the cart.

Transfer Cart (Inbound Section)

The user can transfer the compiled basket back to the external system. On the cart page, the Checkout button has been replaced by a Transfer Cart button. Once the user clicks the button, the system generates a cXML PunchOutOrderMessage document and posts it as an HTTP form request. The address of the post request is retrieved from the BrowserFormPostURL parameter, which is part of the original cXML SetupRequest.

grafik-20260824-140730.png

cXML Punchout Configuration

If the punchout.cxmlUserConfigurationEnabled setting (from the ICM configurations call) is enabled, a gear icon appears next to each cXML punchout user in the list. It opens a per-user configuration page where the account admin can customize the content of the outgoing cXML punchout document. Values can be reset to their defaults.

grafik-20260824-135711.png

The cXML configuration is per user and consists of a fixed set of predefined fields. Each field shows its default value as a placeholder. Leaving a field empty resets it to the default. A collapsible help text below each field explains its purpose and required format.

The following fields are available:

Field

Purpose

Format

Default

unitmapping

Maps external unit-of-measure codes to internal ones and vice versa

&-separated value1;value2 pairs, e.g. EA;pcs&BX;Box

EA;pcs&BX;Box&DZ;Dozen&CS;Case

punchout.locale

Locale used for localized product name/description

e.g. en_US

Falls back to the channel's default locale (or the system's lead locale, if none is set)

punchout.classificationCatalogID

Product classification catalog type

e.g. UNSPSC

UNSPSC

punchout.mapper.supplierPartID

Determines which product identifier is used as the SupplierPartID value

ProductRef or SKU

ProductRef

punchout.useShortNameTagInDescriptionTag

Whether to use a nested ShortName tag or the plain Description tag

true or false

true

An invalid value is rejected with a field-specific error message explaining the expected format.

grafik-20260824-144804.png

OCI Punchout

The Open Catalog Interface (OCI) is one of the standard formats used to connect to external punchout catalogs. Using the OCI punchout format allows to transfer shopping cart data from the external catalog to other systems (e.g., ERP, procurement system).

Enable OCI Punchout

To use the OCI punchout functionality, at least one user with the role OCI Punchout User must exist. The first OCI punchout user can be created by the account admin on the My Account | Punchout | OCI page. The OCI punchout user is usually not related to a dedicated storefront user. External procurement systems use one punchout account for multiple employees. Therefore, an OCI punchout user does not need profile settings such as first name, last name, addresses, or date of birth. Only login and password are required.

grafik-20260824-145700.png

OCI Punchout Information

The required information (login URL) to configure the external procurement system is shown on the OCI tab of the Punchout overview page. The URL points to an ICM pipeline endpoint and contains the placeholders <USERNAME>, <PASSWORD>, and <HOOK_URL>, which must be replaced with the relevant OCI punchout user credentials and the procurement system's hook URL:

grafik-20260824-145512.png

OCI Punchout Profile Settings

The pencil icon to the right of an OCI user opens an edit form for that user. Use it to change the password (and confirm it) and toggle the active flag. The login cannot be changed once the user has been created. There is no separate e-mail address to edit. OCI punchout users do not have a user-facing e-mail address.

Make sure to match the username to your login type preference, e.g., use an email address for logins based on email addresses.

OCI Punchout Storefront (Outbound Section)

An OCI punchout user has access to only a subset of the storefront functionality available to a regular storefront user.

The following areas are examples of hidden functionalities:

  • My Purchases (Orders, Recurring Orders, Requisitions, Quotes, Order Templates submenu entry, Wishlists)

  • My Approvals

  • My Organization (Addresses, Users, Cost Centers, Punchout, Organization Settings)

  • My Profile (Payment, Notifications, Profile)

  • Page footer

  • Create Quote functionality on product or cart page

  • Checkout button on the cart page (replaced by the Transfer Cart button)

  • Payment section on the cart page

  • Recurring-order editing on the cart page

  • Product review/rating submission section on product pages

grafik-20260824-150508.png

The user is able to browse or search for products and add items to the cart.

Transfer Cart (Inbound Section)

The user can transfer the compiled basket back to the external system. On the cart page, the Checkout button has been replaced by a Transfer Cart button. Once the user clicks the button, the system generates an HTTP form post request. The address of the post request is retrieved from the HOOK_URL parameter, which is part of the original OCI punchout request. The cart content is transferred as NEW_ITEM-* key/value fields, which you can customize on the OCI Punchout configuration page.

grafik-20260824-150821.png

OCI Punchout Configuration

To configure the OCI punchout feature, click the Configure button on the upper right of the Punchout page.

The return values of the fields shown on the Punchout configuration page can be customized for the OCI Punchout transfer format. A transformation can be defined, followed by optional formatting.

Parameter Value

To set an OCI Punchout value, define a transformation. Therefore, constants and/or placeholders can be used. The latter are defined by the system and quoted with curly brackets (for example, {sku}).

Transform Value

Result

Annotation

"Stk."

"Stk."

Similar to returning a constant.

"My {unit}"

"My kg"

Assuming that {unit} resolves to "kg"

The system provides the following placeholders:

  • Currency

  • Description

  • ManufacturerName

  • ManufacturerSku

  • ProductName

  • Price

  • Quantity

  • Sku

  • SupplierName

  • SupplierSku

  • Unit

  • Discarded

These placeholders are case-insensitive.

Custom Attribute Placeholder

  • The custom attribute placeholder (transformer) cannot be selected directly. Define the names of the custom attributes in the following property key: oci.ver5.punchout.configuration.custom.attributes.with.access=
    This key defines which custom attribute of the product can be accessed (e.g.: MyColor, MySize, MyEAN).

Without that property key, the custom attribute placeholder does not do anything.

  • To display a list of available placeholders based on the product custom attribute names configured in this property key, click the information icon.

  • Unlike the standard placeholders, the product custom attribute names configured in this property key are case-sensitive.

grafik-20260825-084827.png

Mapping

Data mapping allows values to be assigned individually to the configuration. The system maps field values from the external Punchout catalog to your procurement system. These details are also available via the information tooltip, as shown in the screenshot below:

  • A mapping rule can only be entered for fields that have a parameter value.

  • A mapping rule must always have both a from and a to value, otherwise the system will not save it.

  • If multiple mapping rules exist, only the first matching rule is applied; chaining rules is not possible.

  • A rule is only applied once within a string.

  • An asterisk (*) matches any number of characters. For example, 2345* matches 23450000.

Formatting

A successfully transformed value can be post-processed by a formatter of choice. Available options are:

  • (empty) - no formatting is applied.

  • LowerCase - Converts all letters to lowercase.

  • UpperCase - capitalizes all letters.

  • Trim - removes leading/trailing whitespace such as spaces, line breaks, and tabs.

Disclaimer

The information provided in the Knowledge Base may not be applicable to all systems and situations. Intershop Communications will not be liable to any party for any direct or indirect damages resulting from the use of the Customer Support section of the Intershop Corporate Website, including, without limitation, any lost profits, business interruption, loss of programs or other data on your information handling system.

Home
Knowledge Base
User Manuals
Product Releases
Log on to continue
This Knowledge Base document is reserved for registered customers.
Log on with your Intershop Entra ID to continue.
Write an email to supportadmin@intershop.de if you experience login issues,
or if you want to register as customer.