This SOP outlines the process for a public (B2C) user to register & create an account in IP1 prior to building their shopping cart. It is also possible for a B2C user to begin building their shopping cart as an anonymous user and then electing to register prior to completion of check out. That process is covered in separate Ordering Process (B2C Anonymous then Registered).
Registered users have more options in relation to their account which can be accessed by creating a registered session. B2C users may elect to create an account to be able to access past invoices and see the progress of backordered items. Also allows them to store previous contact & address details for ordering instead of having to key in every time.
This is really intended for B2C users only as it creates both a contact & a customer debtor account using appropriate CRM Contact Template. Normally B2B registered users are created against an existing customer debtor account, so that is done manually by internal staff.
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
User selects ‘Register’ option from website
Website presents screen advising that users with existing B2B accounts should contact internal staff to arrange set up of their B2B user id linked to those account(s).
For B2C registration, continue as follows.
OPTIONAL image verification step to prevent phishing to create many new accounts:
Website displays this image and asks user to input the characters displayed
Website passes these characters into UserInputCharacter for verification when executing createAccount in step 6.
Website presents ‘new registered user’ page with form containing:
title (Title)
firstName (First Name)
middleName (Middle Name)
lastName (Last Name)
loginID (User ID)
password (Password)
confirmPassword (Confirm Password)
company
personalLocation
emailAddress (Email Address) NOTE – email addresses must be unique per siteCode.
mobile (Mobile Number)
address
Address0 (Special Instructions)
Address1 (Street Address 1)
Address2 (Street Address 2)
Suburb (Suburb)
State (State)
Postcode (Postcode)
Country
PhoneNumber (Phone Number)
billingAddress – (Checkbox should be available for “My billing address is the same as my delivery address”)
Address0 (Special Instructions)
Address1 (Street Address 1)
Address2 (Street Address 2)
Suburb (Suburb)
State (State)
Postcode (Postcode)
Country
Other optional fields may be filled in, or allowed to default from template (eg. Partial delivery preferences, contact/customer classifications). Refer technical guide for list of all fields.
Website executes createAccount with the details entered, additionally adding:
contactTemplate
The website will need to pass a valid contact template id.
This means the web developer will need to know which template codes have been configured.
createAccount checks TMSWWW/REG-TMP to ensure the template passed is valid for the site of the current session. The template is used to set the valid sites for the new account.
Typically, this template might be called something like “B2C Registered”.
A corresponding CRM Contact Template must exist, which will set the defaults for the new user & customer account.
autoLogon
Normally this would be set to True to automatically create a session for this new account after creation.
IP1 back end will validate template and address details and pass back any errors in response message.
Website checks response information and asks user to correct any data issues (eg. Postcode vs Suburb or invalid email address formats).
