First setup

Place an order

Order once as your test buyer, then process it in the Cockpit, so you have seen the whole loop before a customer runs it.

Everything so far was setup. This is the first time the platform does what it is for: a buyer at a customer company orders an article at their price, and the order appears in the Cockpit for your Innendienst to process. Run it once by hand, as the buyer and then as yourself, before any integration automates it.

Before you begin. You need the storefront from Create a storefront, the contact from Add a customer with the role buyer, and a way to sign in as them. Keep one such test contact per major account permanently; it is how you will answer "why does this customer see that price" for years.

As the buyer

  1. Open the storefront in a private window and sign in as the contact.
  2. Search for the product by its SKU. In B2B, buyers work from parts lists and search by number far more than they browse.
  3. Check the price at two quantities: 12, which should show the rung at 1, and 60, which should show the rung at 50. Check it in the cart as well as on the product page.
  4. Add it to the cart and go to checkout. Expect the checkout to ask for the things a B2B order needs: a delivery address, a payment method such as invoice, and the buyer's own order number.
  5. Place the order. The confirmation mail should arrive at the contact's address, in the contact's locale.

As yourself, in the Cockpit

  1. Open the dashboard. Order pipeline now shows one order, and Live Activity shows it arriving.
  2. Go to Order Management › Orders and open it.
  3. Read the three badges in the header. An order carries three independent statuses: the lifecycle (placed), the payment status (open, for an invoice order) and the fulfilment status (unfulfilled). All three can disagree and be correct; see The three order statuses.
  4. Find the customer order number under the header. That is the buyer's own PO number and it belongs on every document you send them.
  5. Select Acknowledge. This records that the fulfilling system has taken the order and freezes addresses and buyer details, because two systems editing one order is how goods go to the old address. With an ERP connected, the ERP does this itself.
  6. Select Create shipment, enter the quantity, a carrier and a tracking code, and confirm. The lifecycle moves to in_fulfillment, and when the last quantity ships the order completes.
  7. Open the History tab. Every action you took is there with your name. This tab is the answer to almost every "who changed this" question.

What to check

  • The price on the order line is the price you expected from Configure pricing. If it is not, the order is right about what was agreed and the price list is wrong; fix the list, not the order.
  • The dashboard's Revenue, Orders and Average order tiles moved.
  • The shipment appears on the Fulfilment tab with its own number.
  • The order's fulfillment_status reads fulfilled.

When it does not work

  • The buyer cannot sign in or cannot order: work through the six layers in When a customer cannot order. The commonest causes are a contact status of invited, a role of viewer, or a company that is blocked.
  • The price is wrong: Check a price walks the resolution order by hand.
  • No confirmation mail: run the provider check under Experience Studio › Build › Messaging. See Forms and email.

What you have proved

One article from your catalog, priced on a list, sold to a company at their price, through a storefront on your domain, processed to shipment in the Cockpit. That is the loop a live shop runs a hundred times a day. Everything in Going live is about doing it for the whole catalog and every customer, with the ERP in the loop.

Next

Create a storefront

A site, a theme and a domain: the shortest route to a shop your test buyer can log in to.

Go live

From a tenant that works to a shop your customers use: the first week, the months after it, and the checklist before the domain goes on.