Overview: Capturing Additional Customer Data
- Jenni Buonanni
- Sarah Holst
This feature is supported for: Commerce configured with standard Aspenware Login
This feature is NOT supported for: Commerce configured with Identity for Login/Authentication.
Feature Description
Consider setting up the ability to require additional customer data if you require a zip code, phone number, and/or address on file for every customer that completes an order in your shop. When configured, this required customer data will be collected through the Create Account flow so that customers coming to your shop for the first time will only enter the required info when creating an account and will not be asked again during checkout. If a customer logs in to an existing account, bypassing the Create Account flow, and doesn’t have the required info stored to their profile, they will be asked once to enter data during checkout and then will not be asked again.
Aspenware Commerce resorts to selectively implement customer data capture, including any combination (none, one, some, or all) of these specific fields: phone number, address 1, address 2, city, and postal code.
NOTE: County, Province/State, and Country are currently excluded from this feature. When this feature is turned on, because RTP|One requires a full address profile and cannot store a partial profile, we have to send some default values to the customer address profile. Country defaults to USA (currently not configurable) and County, Province, and State are sent with blank values.
In the instance where fewer fields are selected than are required to create a Primary Address Profile in the resort Point of Sale (RTP|One, for example), a single character placeholder is passed for each field the POS requires for saving a Primary Address Profile.
The default setting for field capture is off but can be easily activated by resort staff.