Walk through a first B2B order safely EN
Check a restricted buyer's company, location, prices and approval outcome before enabling a real purchasing workflow.
Use this walkthrough to review one company purchasing scenario with the store administrator, a buyer and an approver. It describes supported workflow concepts, not a completed acceptance test for your account. Labels and available functions depend on installed version, store settings, company portal profile and role.
Use an agreed test company, synthetic products and a non-production environment where possible. Before submitting anything, agree whether orders, messages, reservations, payment, shipment and ERP export may occur. Approval can place an order; it is not just a preview button. Stop before that step if its side effects are not authorised. Do not invite real colleagues or send external emails merely to test the guide.
Prepare the scenario
The store administrator should confirm:
- B2B portal, the required purchasing functions and order approval are enabled.
- An active company, an accepted membership and the intended company role exist. Administrative staff roles and company-portal roles are different systems.
- The buyer is restricted to the intended location. Without a location restriction, a user may be able to order for all the company's locations; an empty assignment list is not proof of restricted access.
- Company price group/agreement, delivery address, available payment methods, required reference/project/cost-centre fields and applicable credit decision are configured for this scenario.
- The company approval rule and threshold are known. Use a buyer who requires approval, not a company administrator whose permissions may bypass that path.
- Notification behaviour and test-data cleanup are agreed. Do not mark a store live just to trigger emails during a demonstration.
The Norwegian setup guide provides broader settings context. This walkthrough does not change any setting for you.
1. Sign in as the buyer and choose context
Confirm the company name and Deliver to location before adding products. If one login belongs to several companies, switch deliberately and recheck prices, addresses and role. Test the restricted account as well as an administrator; an administrator seeing everything does not prove the buyer's restrictions work.
If the expected company or location is missing, check active membership, location assignment and portal settings. Do not give broader permissions simply to make a menu appear. An invitation waiting for acceptance is not an active login.
2. Prepare one cart
Use the catalogue, an assigned shopping list or the Order Assistant where enabled. For a list or pasted item numbers, review every product match, variant, unit and quantity. Old lists do not guarantee old prices or current availability. For this first exercise, avoid AI document import and real customer documents.
Check the agreed company price, VAT display and any quantity tier, then review the cart and checkout. Browsing may deliberately show list prices or hide prices; checkout shows the company's own price. Investigate the selected company, price-view setting and agreement before changing the catalogue price.
Where location carts are enabled, changing location changes the cart. Confirm that the chosen cart and delivery location still match. Keep this first test to one cart; grouped checkout creates separate orders and needs its own failure tests.
3. Review checkout before submission
Check recipient, full delivery address or pickup choice, shipping cost, required reference, project/cost centre, payment method and tax totals. A closed project must not be used. A company registration alone does not grant invoice credit.
If the buyer needs approval, checkout offers Submit for approval instead of placing the order directly. If that path is missing, inspect the company rule, threshold, buyer role and feature configuration before submitting anything. Do not assume a missing approval button means no approval is needed by the business.
4. Follow the request as both roles
After an authorised test submission, confirm that the buyer sees a pending request, not a completed order. A buyer may withdraw a request while it is still unprocessed.
The approver opens Approvals, checks buyer, location, lines and total, then approves or rejects and confirms the decision. Location-manager approval depends on the store's setting and assigned locations; it is not universal approval access. Do not use bulk approval for the first test.
Once approved, verify the actual order result and its details. If rejected, verify the reason and buyer-facing outcome. A request can also expire; the default deadline is configurable, including company-profile overrides. Do not use a fixed waiting period as an acceptance criterion without checking the configuration.
Pending requests count toward the relevant spending-limit calculation. An approver can approve above the spending limit, so that limit is not an unconditional hard cap on every approval. Review the business policy separately from the UI meter.
5. Handle failures without duplicate purchases
| What you observe | Safe next check |
|---|---|
| Wrong price or VAT display | Recheck company, agreement, quantity, unit and display mode; do not overwrite catalogue prices as a shortcut |
| Missing invoice payment | Check the company's credit approval and available payment methods; do not assume registration grants credit |
| Rejected location or project | Confirm assignment, company ownership and active/open status |
| Submission timed out | Check pending requests and order history before submitting again |
| Approval reports an error | Inspect the request and any created order before repeating the decision |
| No notification email | Verify the in-app state and configured notification/live-store behaviour; do not infer that no order was created |
| Grouped checkout partly succeeds | Record orders already placed and the cart that failed; do not resubmit the entire group blindly |
Sign off only what you observed
Record the test roles, location, pricing/VAT expectation, approval rule and observed outcome. Include permitted and denied actions, plus a withdrawal or rejection test. Use synthetic identifiers and redact personal data, secrets and negotiated prices from shareable evidence. Check any destination-system effects separately.
This walkthrough does not enable recurring or automatic purchasing. The recurring workflow can create a cart for review or place orders automatically depending on configuration; that is a separate business decision and test scope. It also does not prove all portal roles, multi-cart checkout, AI-agent approvals or ERP return flows have passed acceptance.
For external order handover, read Visma export verification.