1. Home
  2. /
  3. Web Enablement
  4. /
  5. Web Enablement – SOP
  6. /
  7. Anonymous ordering process (B2C)

Anonymous ordering process (B2C)

This SOP describes a typical high level process for Business To Consumer (B2C) Anonymous Ordering Process utilizing Iptor IP1 Web Services.

Procedure

This section documents the Headline Processes for an anonymous B2C web user to create an order in IP1. Note that the checkout procedure for anonymous users contains slightly more steps due to things like addresses not being stored in the system.

It is your responsibility to ensure that you understand this procedure before performing the following tasks.

Note

Deviations from this procedure should be covered by procedures written by your company. Before performing any tasks please ensure all the business rules are set-up accordingly. 
Process
  1. User accesses the website, createSession is executed using loginType=A (anonymous)
  2. User browses the products on the website by either browsing or searching
    • This may be handled entirely by web site if product, price & availability data is interfaced from IP1 & stored there.
    • Alternatively, clients may elect to use IP1 catalogue functionality and web services to find products.
    • Refer Product Browsing and Searching
  3. User selects product to view details
  4. Website executes viewProduct against the item being queried.
  5. Along with other data, the response values stockQty and RRP are used to display live price and availability to the user.
  6. User specifies desired QTY and selects ‘Add to Cart’, website executes addCartLine
  7. Steps 3-6 are repeated as necessary. NOTE – User may also specify QTY and ‘Add to Cart’ from search results or browse pages without viewing product details.
  8. User views the cart to see the order progress, website executes viewCart
  9. Once finished shopping, selects ‘Checkout’
  10. Website presents user with option to ‘Sign in’, ‘Create Account’ or ‘Checkout as guest’
  11. User selects ‘Checkout as guest’
  12. Website presents the current cart contents viewCart and subtotal without freight
  13. User selects ‘continue’
  14. Website presents an empty form with:
    • emailAddress (Email Address)
    • deliveryName (Name)
    • deliveryAddress
      • add:Address0 (Special Instructions)
      • add:Address1 (Street Address 1)
      • add:Address2 (Street Address 2)
      • add:Suburb (Suburb)
      • add:State (State)
      • add:Postcode (Postcode)
      • add:Country
    • billingAddressSameAsDeliveryAddress (My Billing Address is the same as my Delivery Address) checkbox
    • billingCustomerName (Billing Name)
    • billingAddress
      • add:Address0 (Special Instructions)
      • add:Address1 (Street Address 1)
      • add:Address2 (Street Address 2)
      • add:Suburb (Suburb)
      • add:State (State)
      • add:Postcode (Postcode)
      • add:Country
  1. User enters details and selects ‘Next’
  2. Website executes updateHeader, passing the sessionId as the customerReference and passing relevant orderType that has been configured for B2C orders.
    • Website checks the response from updateHeader which may include address validation errors.
    • Website goes back to step 15, highlighting incorrect values
    • Note: Some clients like the web site to conduct it’s own address validation. In that scenario, the web site would normally do this before calling updateHeader.
  3. User is presented with freight and payment options from viewCart
    1. Refer Managing Order Settings and Preferences
    2. Refer Payment Method Selection
  4. User selects freight and payment option and website executes updateHeader then viewCart to store the minAmountToPay
  5. Website retrieves payment requirements from retrievePaymentFields and presents user with payment entry form based on values returned.
    • This step is generally redundant for credit card processing using 3rd party payment gateway
    • For other payment methods, refer Payment Method Selection
  1. Credit Card entry/validation and retrieval of token:
    • Website passes information & control to a 3rd party payment gateway landing page (LP) such as Cybersource, Securepay or Curbstone) where user will key in credit card details.
    • LP will perform necessary validations and interactions with end user until a valid credit card has been entered.
    • LP passes back token & non-sensitive payment details such as credit card mask (eg. xxx-xxx-xxxx-1234) information back to website.
    • Website executes makePayment passing token and other payment details returned from LP.
  2. User is redirected to a “Thanks for your order” page – containing the customerReference value.
  3. Once order is picked, Iptor emails user copy of invoice.

 

Print Friendly, PDF & Email