1. User accesses the website and selects ‘Log In” option.
2. Website executes login process for registered user.
   • Refer Logging In and Out – Single Account or Logging In and Out – Multiple Accounts depending if this installation allows user to be linked to multiple accounts.
3. Website executes process to determine appropriate order type.
   • Refer Establish Order Type.
   • Eg. May use retrieve retrieveCustomerClassification to determine if user is linked to a B2B customer rather than B2C, then use updateHeader with the relevant orderType that has been configured for B2B.
4. User browses the products on the website by either browsing or searching
   • Refer Product Browsing and Searching
5. User selects product to view details
6. Website executes viewProduct against the item being queried.
7. Along with other data, the response values stockQty and RRP are used to display live price and availability to the user.
   • Note: This price & availability data is specific to the B2B customer account which the user has selected during the login process
8. User specifies desired QTY and selects ‘Add to Cart’, website executes addCartLine
9. Steps 4-8 are repeated as necessary. NOTE – User may also specify QTY and ‘Add to Cart’ from search results or browse pages without viewing product details.
10. User views the cart to see the order progress, website executes viewCart
11. Once finished shopping, selects ‘Checkout’
12. Website presents the current cart contents viewCart and subtotal without freight
13. User selects ‘continue’
14. Website presents user with default delivery address and user selects or keys relevant delivery address. Refer Delivery Address scenarios section of this SOP document for different variations of this process.
15. Website also asks user to key a customerReference for this order.
16. Website executes updateHeader with the new deliveryNumber or with overridden delivery address details, as well as an appropriate customerReference.
17. User is presented with freight and payment options from viewCart.
    • Refer Managing Order Settings and Preferences
    • Refer Payment Method Selection
18. User selects freight and payment option and website executes updateHeader then viewCart to store the minAmountToPay.
19. Website also displays the revised total order amount based on selected freight option.
20. Website retrieves payment requirements for the nominated payment method option from retrievePaymentFields and presents user with payment entry form based on values returned.
    1. In case of ‘on account’, this simply gives user opportunity to review the final order amount before proceeding to finalise the order.
    2. User presses a button on website to proceed with final step of checkout.
    3. For other payment methods, refer Payment Method Selection
21. Website executes makePayment
22. User is redirected to a “Thanks for your order” page – containing the customerReference value.

Additional notes & scenario variations

Alternative scenario building shopping cart before logging in

Note that B2B users could use alternative scenario similar to Ordering Process (B2C -Anonymous then Registered) whereby the where user begins building their shopping cart as an anonymous (guest) user, but then elects to sign in as registered user. However, it is preferable for B2B users in particular to log into their account first, so that all pricing and availability information is specific to their account. This also enables them to access other self service and account management features.

Customer reference scenarios

Website may allow user to enter their own customerReference or could automatically assign a reference. Generally for B2B, the website would insist on customer keying their own reference, however, it would be possible for the website to assign a default customerReference = sessionId.

Depending on IP1 customer master file setups, the customerReference may need to be unique for this customer.

Delivery address scenarios

Depending on business rules for each implementation, clients may want to restrict maintenance of delivery address(es) for a customer account to back end customer service staff. However, it is also possible to allow B2B users (contacts) to maintain their own. Following is an outline of possible scenarios:

Don’t give B2B user any option for delivery address (use default)

1. User is presented with the default delivery address details from viewCart

Allow B2B user only to select an existing delivery address from customer account

1. Website executes getDeliveryAddresses
2. User is presented with the default delivery address and other delivery address options
3. User then selects desired delivery address for this order.
4. Website executes updateHeader with the new deliveryNumber as well as an appropriate customerReference.

Allow B2B user to select an existing delivery address, or to override the address just for this specific order

1. Website executes getDeliveryAddresses
2. User is presented with the default delivery address and other delivery address options
3. User then selects desired delivery address for this order, or keys an override address
4. Website executes updateHeader with the new deliveryNumber or with overridden address details, as well as an appropriate customerReference.

Allow B2B user to maintain delivery addresses for the customer account

1. Website executes getDeliveryAddresses
2. User is presented with the default delivery address and other delivery address options
3. Website gives user option to update or add delivery address(es) for this customer account.
   • This also allows update of the default delivery address.
   • Note that these changes impact not only web orders, but also back end orders keyed through order entry!
   • Refer SOP-WEB-230
4. User then selects desired delivery address for this order.
5. Website executes updateHeader with the new deliveryNumber or with overridden delivery address details, as well as an appropriate customerReference.