...
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 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 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 after they have added it.
Aspenware Commerce allows for 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. (
| Info |
|---|
NOTE: County, Province/State, and Country are currently excluded from this feature. |
...
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.
Default The default setting for field capture is off but can be easily activated by resort staff.
HINT: This feature might be useful if you use Square or Braintree as a payment processor and want to capture any guest address information in your Point of Sale. Aspenware’s integration to Square and Braintree does not require address collection and does not store zip code in the resort POS even though it is collected to verify the payment by the payment gateway.
...
| Child pages (Children Display) | ||
|---|---|---|
|
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
...