POS
These settings control the integration with the Kensium POS. The options are:
-
Register
- The POS register definition that Kensium POS should use when saving sales and other transactions.
-
This register definition should be created in the POS admin tools.
- Important: the register should be for the exclusive usage by Kensium POS.
-
It’s important to ensure that the register definition is created properly. Kensium POS will use the register definition for:
– Location and Store settings- Customer template to use when creating new customers
- Default transaction class for any orders created through POS (e.g. checkout)
- Customer template to use when creating new customers
-
Default Clerk
-
The POS user (or clerk) account to use when saving sales and other transactions.
-
Kensium POS does not use or observe register security settings; this field’s purpose is for POS to supply a valid user in transaction records.
-
-
Default Customer
-
The POS customer account to use when saving sales and other transactions, when a customer context is not known (e.g. a ‘guest’ customer is placing an order, or a salesperson is creating an order for a guest customer).
-
This customer account should be created in the POS admin tools and Acumatica, if applicable.
-
This customer account is like the “Cash Customer” account used by registers, except that it should be configured for the exclusive use by Kensium POS.
-
-
Payment Type
-
The POS payment type for payments that are made against orders within Kensium POS.
-
This payment type should be created in the POS admin tools and Acumatica, if applicable.
-