Set up B2B companies and purchasing EN

Configure company members, locations, purchasing functions and approval before inviting real buyers to use them.

This guide adapts the Norwegian B2B setup guide. Availability depends on release, licence, store settings, company portal profile and role. Administrative staff roles and company-portal roles are different access systems. /admin/ and /portal/ paths refer to the store, not this website.

Use an agreed test company and synthetic data for practice. Inviting people, changing access, approving credit, creating orders and enabling automatic purchasing have real consequences; agree those actions before carrying them out.

Administrator setup

In Settings → Commerce → B2B, confirm the master Enable B2B portal setting and the switches for the required features. A company's portal profile can customise available functions. Do not assume every listed feature is active in every store or that a hidden menu proves a server-side restriction.

On the company customer card, use the company setup checklist:

  1. Create delivery locations, or review an appropriate location import.
  2. Invite the intended users and confirm acceptance. A pending invitation is not an active signed-in member.
  3. Assign location restrictions where needed. Without a restriction, a member may be able to order for all company locations.
  4. Enable location-level user management only if location managers should manage buyers at their own locations.
  5. Review price group, assigned purchase-list templates, approval rule, credit decision and portal profile.

Portal roles include Buyer, Location manager and Company administrator. A location manager does not automatically manage the company's other locations. The portal adapts to company scale; an administrator can lock the relevant level on the customer card. Test a restricted buyer, not only an administrator.

Locations, projects and cost centres

Locations hold delivery addresses and instructions and may carry a cost centre. Where enabled, Deliver to selects a location and One cart per location changes the cart with that selection. Review the actual checkout delivery details.

Projects are separate from locations. Where enabled, the buyer chooses a project at checkout, and related orders/documents can be followed from the portal. Whether it is required depends on configuration; a closed project cannot be used. Cost centres can also be required and carried into order/invoice references and accounting export. Verify destination mapping separately.

The order-dimension setting changes whether grouping is presented as Locations, Projects or Weekdays. Purchasing mode, when enabled, provides a purchasing desk with carts, reorder work, approvals, orders and lists rather than a normal storefront landing page.

A user linked to several companies can use the company selector where enabled. Cart, prices, addresses, history and role follow the selected company. Requesting to join a company does not itself grant authority to order for it.

Prepare and reuse orders

The Order Assistant can support pasted item numbers/EANs with quantities, CSV, history-based reorder and assigned templates. Document import is an additional AI-enabled function, not a requirement for normal purchasing. Do not upload personal or confidential documents without permission and provider review.

Inspect every product match, variant, unit, quantity and current price before adding lines. A suggestion is not an order. Shopping lists are reusable customer purchase templates, not supplier purchase orders in Kaduno Purchasing.

Multiple carts can be saved, resumed, renamed, duplicated or archived where available. Check out selected can submit a group: each cart becomes its own order and delivery. Limits are checked for the group, but a later partial failure can still leave some orders created. Inspect the reported results and failed cart before retrying; do not blindly submit the whole group again.

Approval and credit are separate policies

A company rule can require approval for all relevant buyer orders or at/above a threshold. The buyer submits a request; it is not a completed order yet. An eligible approver can approve or reject, and approval can place the order. Company administrators may not follow the same approval path as ordinary buyers. Location-manager approvals depend on the configured feature and assigned locations; a location manager does not approve their own request.

Requests can be withdrawn while pending or expire. The default expiry is seven days but configuration and company-profile overrides can change it. Pending requests count toward the relevant spending-limit calculation; an approver can approve above the limit. Do not describe the meter as a universal hard cap.

Credit approval and available payment methods are separate from company registration and order approval. Check credit-limit policy and which system owns the credit flag. Do not change these controls simply to get a test order through. Customer AI-agent approvals require separate settings and acceptance; human approval is the intended first walkthrough.

Recurring purchasing needs its own decision

With recurring orders enabled, a shopping list can repeat every chosen number of weeks on a selected weekday. The store chooses the run mode:

  • Create a cart for review is the default mode. The buyer reviews and orders.
  • Place the order automatically creates orders through checkout without the buyer pressing Order each time. Payment compatibility, accepted terms, approval, credit, budget, stock and pricing rules still matter.

If a run is stopped by a rule, inspect the remaining cart/explanation or approval request. Do not enable automatic mode as part of a demonstration without an explicit agreement. Plans can be changed or paused by the eligible owner or administrator; inspect the actual schedule and outcomes before promising delivery.

Verify before handing over

Check company, restricted locations, agreement price/VAT display, address, required references, payment and approval outcome. Notification availability also depends on live-store and email configuration; missing email is not proof that no action happened. Do not mark a store live just to test notifications.

If a feature is missing, check role, store switch and company profile. For wrong prices, check company and agreement before changing catalogue values. For a timeout, check requests and order history before resubmission.

Follow the first B2B order walkthrough for a controlled scenario and integration verification for the separate ERP handover. These guides are source-reviewed instructions, not a claim that your company's complete purchasing process has passed acceptance.