Custom Checkout Questions

 

WebAlliance has the ability to display Custom Checkout Questions for your Users to answer during the checkout process. Custom Checkout Questions and their answers can also be imported into supported fields of your ERP. If you'd like to configure a Custom Checkout Question, or multiple, please contact Aldrich Web Solutions.

Where does the Custom Checkout Question and Answer appear?

The Custom Checkout Question(s) will appear during checkout. When the end-user answers the questions, the answers can be found in a few different locations on the site for the Customer and Admin to see:
 

  • The Checkout Complete Page (including it's printable option)
  • The Shopping Cart Receipt Email (if specified in the email template)
  • The Order Detail Page (admins only)
  • The P21 Header Note (admins only)

Question Configuration

To configure a Custom Checkout Question, we'll need a few details. These include: 

  • What Question(s) would you like to ask during Checkout?
  • What User Group(s) or Customer Code(s) would you like to display the Custom Checkout Question to?
  • What Validation Type(s) would you like to apply to the question (such as "Required", "Minimum/Maximum Length", or "Alphanumeric Only")?

Available Import Fields by ERP

P21
  • CustomerName
  • ContactName
  • Taker
  • JobName
  • ShipToName
  • SourceLocation
  • CarrierId
  • CarrierName
  • Route
  • PackingBasis
  • DeliveryInstr
  • Terms
  • TermsDesc
  • WillCall
  • Class1
  • Class2
  • Class3
  • Class4
  • Class5
  • FreightCode
  • BillingDescription
  • ContractNumber
  • ShipToEmail
  • SetInvoiceExchangeRateFrom
  • ShipToPhone
  • CurrencyId
  • ApplyBuilderAllowance
  • QuoteNumber
  • WebReferenceNumber
  • OrderTypePriority
  • UPSCode
  • ErouterReleaseNo
  • PlacedByName
TrulinX
  • Name
  • AttentionToName
  • Phone
  • EmailAddress
  • ShippingMethod
  • OutboundFreightAbsorbed
  • FreightTerms
Acumatica
  • ShipVia
  • Project

When importing Custom Checkout Questions, the value of the question/answer will override the default import mapping. This has the potential to cause import errors if proper validation is not considered on the input. Refer to your ERP documentation for the expected values of each field.