Cart Content

Your cart is empty

Addresses

Existing addresses

Additional addresses can be rendered in TemplateTag-based designs by using the UserManagement:User.UserAddresses loop, which returns the address on the user as well as any additional addresses belonging to this user from the AccessUserAddress table.

As of 9.9.5 I cannot find a way to retrieve all addresses on a user via the API - the GetUserAddresses()-method returns only the addresses in the AccessUserAddresses table but not the address on the user itself.

Select a billing address

This user has no additional addresses

Select a delivery address

This user has no additional addresses

Billing address

Billing address details are submitted using input fields with specific names and ids, as in the example below. Many - but not all - of the order fields available can be matched with a specific user field when the user is logged in.

You can also retrieve the user object directly via the API and access the properties directly.


Personal

All the personal fields map directly to a specific user field, here accessible via the Ecom:Order.Customer.{Field} tags.

Address

Like personal fields, the address fields are matched to standard user fields. The exception is the Country field - which determines which payment and shipping methods are selectable. For this field you can use the Countries loop to list all the Ecommerce countries available on the solution.

Contact

The customer can also submit contact information to the cart - Phone, Fax(!) and Cell numbers - as well as an order comment.

Other

Finally, a selection of miscellaneous fields can be submitted to cart to add additional information to the order - e.g. an EAN-number, a VAT registration number, or the customer Company.

Delivery Address

In almost all respects, the delivery address fields are identical to the billing address fields. The only difference is that there is no Comment field, and that billing specific information such as the Vat Registration Number is not present.

The 'Copy customer info to delivery info fields if empty'-checkbox under Settings > Ecommerce > Advanced Configuration > Shopping cart allows you to copy billing address field values to the delivery address fields if no part of the delivery address has been filled out.

Personal

All the personal fields map directly to a specific user field, here accessible via the Ecom:Order.Customer.{Field} tags.

Address

Like personal fields, the address fields are matched to standard user fields. The exception is the Country field - which determines which payment and shipping methods are selectable. For this field you can use the Countries loop to list all the Ecommerce countries available on the solution.

Contact

The customer can also submit contact information to the cart - Phone, Fax(!) and Cell numbers.

Other

Finally, a selection of miscellaneous fields can be submitted to cart to add additional information to the order - e.g. an EAN-number, a VAT registration number, or the customer Company.

Comment

Address formats

It is possible to format addresses according to the country-context - Ecom:Order.Customer.Country - as set on the order.

Billing Address Edit Format

Billing Address Display Format

Delivery Address Edit Format

Delivery Address Display Format

Payment Methods

Payment methods are rendered via the Paymethods loop. Some extra logic is needed if you want to support saved cards - both to save the card and to ensure that you don't submit both a saved payment method and a regular payment method to cart. In this case we use a javascript function to clear the Payment Methods radio button if a saved card is selected.

Saved Cards

Saved Cards - or more properly saved payment methods - are most easily rendered in a separate list. Like for payment methods, we use a js function to clear any payment method selected when a saved card is selected.

No saved cards for this user

Inline payment form

If a checkout handler supports inline forms, the tag Ecom:Cart.PaymentInlineForm is used to render the checkout handler post form inline.

The selected payment method does not support inline payments

Shipping Methods

Shipping method selections are submitted to cart using input elements with the name EcomCartShippingmethodID and an ID of the type EcomCartShippingmethodID_{ShippingMethodID}.

Vouchers, Coupons & Pay with Points

Vouchers are submitted to cart using a field with EcomOrderCustomerVoucher as the name and id. Coupons are discounts triggered by a code - the coupon field is simply a custom order field selected on the discount. Like all custom fields you post values to it using input elements with a name matching the system name of the custom field - no id property necessary.

Sign in to see your loyalty points balance.

Gift Card

Create user during checkout

To create a user during checkout submit a field with the name and ID EcomUserCreateNew to cart alongside fields creating a user name and a password

Recurring Orders

To create a recurring order you must first check if the payment method supports it - if it does you must submit a field with the ID and name EcomRecurringOrderCreate alongside an interval, an interval unit, and a start and end date to the cart.

This payment method does no support recurring orders

Custom Fields

Custom fields - such as order fields - are posted to the cart using input elements which take the system name as the field name. No ID is necessary.

Opt-ins

From the cart you can change the value of the Email permission field on the logged in user, and the user can be asked to accept the Terms & Conditions.

  • This cart does not have the 'Use email subscription' field checked in the app settings