Show TOC

Object documentationCustomer Profiles Locate this document in the navigation structure

 

Customer profiles can be applied to each User-Defined Function (UDF) and are used to specify rules that determine how and when to capture customer information from a particular customer service.

Customer profiles can be associated with UDFs, items sold or returned, or other types of features.

Information includes which UDF triggers the customer entry or lookup, when the lookup is done (immediately or at the end of a transaction), whether you can bypass the customer information (if so can it be skipped entirely or just until the end of a transaction), and what to do if customer information already exists in the transaction.

General

Screen Element

Description

Customer Lookup/Entry UDF

Predefined UDF that triggers a customer lookup

Lookup Timing

Specifies when to capture the customer’s information at the POS terminal. Timing options are as follows:

  • Immediately — triggers a customer lookup as soon as the function is initiated at the POS terminal

    Example Example

    During a return transaction a customer lookup is triggered. The system sends a message to the customer service that your organization uses, and then the POS terminal receives a response allowing the cashier to continue.

    End of the example.

  • End of Transaction — triggers a customer lookup at the end of a transaction

  • End of Function — triggers a customer lookup after a function key is hit

Bypass Rule

Captures customer information as follows:

  • Do Not Allow— completes the customer data capture sequence and adds the customer to the transaction to complete a function, such as starting a transaction or selling an item

  • Allow Until EOT — cancels the customer data capture sequence until a Total or you perform a tender action

  • Allow — bypasses the customer data capture sequence completely

  • Void Transaction — disallows the transaction when you choose Clear or Esc

Multiple Customer Rule

Specifies how the POS terminal behaves when customer information is captured for a transaction. Rule options include:

  • Always Prompt — always triggers a new customer lookup

  • Prompt for Alternate Customer Service — triggers a new customer lookup if the customer information entered is for a different customer service

  • Do Not Prompt — ignores the requirement for a customer lookup if customer information is already collected