POS settings
Integration settings can be configured for each POS store. Some default settings can be further customized at the outlet or register level. These settings affect how Cin7 Core POS captures orders, processes sales, and generates accounting transactions.
POS settings are configured from the Setup section of your POS integration. The settings are accessed from Cin7 Core web, and cannot be configured from the mobile application.
General settings
General settings control how your POS store will process sales, treat customers, and apply taxes to sales.
Capture POS sale when it is:
Depending on your requirements, you can choose to capture POS sales when they are either created or completed (fully paid).
Consolidate sales:
You are able to configure how pending POS sales are processed in Cin7 Core by using the Consolidation type feature.
There are two modes:
No consolidation:All walk-in/cash register sales will be created as individual sale orders in Cin7 Core.
Daily consolidation: All POS sales for the day will be pooled into a single sale order at a specified consolidation time.
Regardless of the selected consolidation method, On Account and Layby sales will always be created in Cin7 Core as individual sale orders. This allows you to fulfill the orders and attach relevant payments when necessary.
Consolidation time:
This is the local time for consolidating all pending sales into a single sale order containing all sales that occurred during the day. This option is only visible when Consolidate sales: Daily consolidation is selected.
Customer:
Select a default customer to be used in POS sales when no customer info is available for the sale order or when the Daily consolidation option is selected. If the customer information exists in the POS sale order, the default customer defined in POS settings is ignored.
When No consolidation is selected, the default customer may be used in cases where customer information is not attached to the POS sale order, e.g. walk-in sales.
When Daily consolidation is selected, the default customer is used to create a new sale task that will combine all daily sales into a single sale.
Sale price tier:
This setting determines which product price tier (within Cin7 Core) will be used when publishing products from Cin7 Core to POS.
Default sales tax:
When a pending sale is processed in Cin7 Core, a sale task is created with order and invoice lines completed. Select the tax rule that should be applied to sales coming from POS where sales tax applies. The default tax rule can still be overwritten within POS at the outlet level or during the sale itself.
Zero tax:
Select the tax rule to be applied to a sale where no sales tax applies. The zero tax rule can still be overwritten within POS at the outlet level or during the sale itself.
Cin7 Core allows tax rules to be added or deleted at the outlet level during the Cin7 Core POS checkout process. When you add or delete a tax rule during checkout, the selected option in this field is applied to the product instead. However, this tax rule can still be edited or deleted.
Tax inclusive:
Select whether POS sales are tax inclusive (this setting enabled) or tax exclusive (this setting disabled). Ensure that the POS tax inclusive/exclusive setting matches the pricing that has been set for your products in Cin7 Core.
Ignore customer tax rule
Ignore tax rule applied in customer record when a customer is added to the sale. This will not affect tax rules applied at the product level.
Pick, pack and ship processing mode:
This feature allows you to automate some or all of the pick, pack and ship steps of the fulfillment process when a pending sale is converted into a sale order in Cin7 Core. For example, POS sales where the stock is taken away immediately by the customer can be set to auto pick + pack + ship.
Note: If there is not enough stock on hand to allow pick of the whole quantity of products in a sale order, pick, pack, and ship will not be completed.
Process auto-assembly as:
This setting affects how sales of finished good products with auto-assembly enabled are processed. See Finished goods assembly - Auto assembly for more information.
This dropdown field has two options:
For ordered quantity: Does not check stock quantity. An assembly order is created for the quantity specified in the sale order, regardless of stock availability.
-
For minimum quantity required for picking: Assemble stock required to meet the quantity of specific sale order.
If stock availability is negative, auto-assembly will produce a finished goods quantity which is more than the quantity ordered through sale order.
If there is already stock available in inventory but not enough to fulfill the sale order quantity, auto-assembly will assemble the difference in quantity needed to meet the sale order requirement.
If stock availability exceeds sale order quantity, auto-assembly is not triggered.
Stock availability is validated against the sale order location and does not take quantity on order into account.
Check availability on checkout
When this setting is enabled, Cin7 Core will perform an availability check during the POS checkout process. A confirmation message will appear informing the user if the item is no longer in stock. When turned off, no check is performed.
Customers load mode
This setting determines how customer data is loaded to the POS application. There are three options:
Online: In online mode customer data is not sent to the application. POS will retrieve customer information when a request is made, e.g. looking up a customer.
Offline: In offline mode, all customers are loaded to the POS application local app storage. When online, POS will check periodically for new customers.
Hybrid: This will use offline mode when there are less than 10 000 customers but online mode when the number of customers exceeds the threshold. This mode is applied automatically to all new stores.
Note: Hybrid mode is applied by default to all new shops. Online mode will be applied to new stores with more than 10 000 customers once the customer number is checked for the first time. Offline mode is applied to all existing stores, no matter how many customers they have.
Payment workflow order:
Users can specify whether payment amount or payment method is required first on the payment screen of an order. When payment amount is specified first, selecting the payment method completes the sale without allowing further editing of the payment amount.
Account and cash settings
Account and cash settings control how POS accounting transactions are recorded in your records. Accounts for petty cash, till discrepancy, etc. set here to apply to all POS outlets and registers. If you are looking for further granularity in till records, accounts can also be set at the outlet/register level. See Accounts and Chart of Accounts for more information about adding accounts, and consult your bookkeeper if necessary.
Invoice status:
Controls the invoice status for a sale task created as a result of processing a pending sale from POS.
By default, the invoice will be created in draft state and adjustable. If invoice status is set to authorized, the invoice will be automatically authorized and pending sync will be created for it so that it can synchronize with your accounting application.
Till discrepancy account:
This Current asset account will be used to track the differences between the amount expected when you close your register and the amount you count. This can be overridden at the register level.
Petty cash:
This Expense account will be used to post any petty cash amounts taken or added into your cash drawer for any small expenses in your store. This can be overridden at the register level.
Cash in/out:
This account should be a Current asset and will serve as a clearing account when cash is put in or taken out of the till. Amounts coming in/out of this account will be reconciled against bank or wage accounts. This can be overridden at the register level.
Cash float account:
This account should be a Current asset and will be used to post your daily float and any float adjustments that were made during the day. This can be overridden at the register level.
Rounding account:
This Revenue account will be used for rounding differences for amounts owed to the nearest specified increment based on your chosen rounding rule.
Round to:
Pick the cash rounding denomination based on the regulations of your country/currency. You can choose from the nearest 0.01, 0.05, 0.10, 0.50 or 1.00.
Rounding rule
You will need to specify your rounding rule. This rule determines how your chosen denomination is rounded in a cash sale. You can choose from always round down, always round up, round midpoint down or round midpoint up.
Optional revenue account
The revenue account to be used for all POS sales. If this is selected, it will take priority over accounts set at the account mapping, customer, and product level.
Use as sales representative
Fill in this field with the name of a sales representative to be specified for sales captured by Cin7 Core from POS. Default options are Outlet name and Cashier name.
Receipt template:
Select a default receipt template to be used across your POS Store. Receipt template can also be set at the outlet level. Templates are accessed and customised from Settings → Document and email templates. See Managing document and email templates for more information.
Enable loyalty
Toggle the button to Yes to turn loyalty on. Loyalty is a feature where your customers earn dollars for every purchase they make in your store. See Setting up and using loyalty in Cin7 Core POS for more information.
Loyalty expense account
When Enable loyalty is toggled to Yes (see above), you'll need to select where in Cin7 Core to post the loyalty expenses. If you are not sure where to set this account up in the chart of accounts, or which codes to use, contact your accountant.
Earning loyalty
When Enable loyalty is toggled to Yes (see above), you need to enter the amount a customer needs to spend to earn 1 unit of the currency applicable to your country.
Security settings
Default user's password
Set a default password that will be used by users to access Cin7 Core POS for the first time when you invite them. Upon accessing POS for the first time, they will be prompted to reset their password to their own unique one. See Access the POS store for more information.
Reply-to address
This is the default email address for your account. It is used when sending sales documents to your customers.
Enable PIN
Toggle this button to Yes to enable a PIN to be set for the POS point, or POS terminals, if you have multiple locations.
PIN code length
Set the desired length of the PIN code to be set for the POS terminal/s.
Enable auto lock
Set the POS application to be locked out after a certain amount of idle time has passed to prevent unauthorized use of the POS application.
If enable PIN is active, the lock screen will prompt the user to enter their security PIN.
If enable PIN is not active, the user will need to log in again with their email and password.
Auto lock after (seconds)
When active, this setting will be displayed, allowing you to configure how much idle time is required before the POS application is locked automatically.
POS integrations
You can connect the following payment processors and hardware with your POS store. Follow the links for detailed instructions on how to set up each payment processor. You will then need to enable the payment processor in this section before you can accept payments.
Square (Square must be enabled at the outlet-level, not here - see documentation)
Use Tyro
Toggle this button to Yes if you are using a Tyro eftPOS terminal at your POS point, or Tyro eftPOS terminals in your outlets, if applicable. See Tyro integration for more information.
Use Vantiv triPOS
Toggle this button to Yes if you are using Vantiv triPOS payment processing solutions for the POS point. See Vantiv triPOS integration for more information.
Use Paymentsense
Toggle this button to Yes if you are accepting Paymentsense card payment solutions for the POS point. See Paymentsense integration for more information.
Use Linkly Cloud
Toggle this button to Yes if you are accepting Linkly Cloud card payment solutions for the POS point. See Linkly Cloud integration for more information.
Use Windcave
Toggle this button to Yes if you are accepting Windcave card payment solutions for the POS point. See Windcave integration for more information.
Use LoyaltyLion Rewards
Toggle this button to Yes if you are want to use the LoyaltyLion loyalty program instead of Cin7 Core's own loyalty system. This setting is only visible when LoyaltyLion integration has been connected. This will automatically disable and remove the Cin7 Core loyalty program setting from the setup tab. See LoyaltyLion Integration for POS for more information.
POS UI settings
POS UI settings affect how your products will be displayed on your POS display
Catalog size
Select the default catalog size that will be applied to all registers. This controls how many rows and columns of product tiles will be displayed on the screen. This can be also be set at the register level.
Tiles visibility
Select the default view of the product tiles. Available options are Image and text, Image, and Text.
Product availability icon
Toggle this button to Yes to show the product availability icon on the product tile.
Surcharge tax rule
Select a surcharge tax rule to be applied to payment method surcharges. See Surcharges for more information.
Use customer price tier
This setting overwrites the sales price tier value for POS. If Use customer price tier is toggled to Yes, then the customer price tier will be applied in Cin7 Core POS item sale when a customer is added to the sale. If Use Customer Price Tier is toggled to No, the regular price tier will be applied to sales in Cin7 Core POS, even if a customer is selected.
Use advanced barcodes
By default, Cin7 Core POS is configured to use product-based barcodes. Cin7 Core POS can also handle advanced barcodes with embedded data, which are ideal for stores that sell products based on weight or price, e.g. butcher shops, delicatessens, and fruit stands. Cin7 Core supports the following barcode types:
Product based: Barcode is input at the product setup level and only contains the product code. There will be no additional information retrieved through reading this type of barcode, barcode is used to lookup item only. Product quantity is entered manually by the cashier during checkout and price would be determined based on the entered qty and price per unit as per the product setup.
-
GS1 based:These are standard barcodes used in retail stores worldwide and capable of holding additional product attributes such as weight and price.
UPCA codes which start with 2 and are twelve digits in length
EAN 13 codes which start with 2 and are thirteen digits in length
Weight based: Barcode consists of product code/outlet SKU, then the weight information. Typically these are generated by a third party weight scale. Cin7 Core POS reads these barcodes at the check out and retrieves product price information based on the weight given on the barcode.
Price based: Barcode consists of product code/ outlet SKU and product price. Cin7 Core POS reads the barcode to calculate the quantity or weight based on the barcode price during checkout in order to determine the quantity that must be reduced from the inventory.
When you change this setting, the Barcode setup section will be enabled. This is where you configure your barcodes. See Advanced barcodes for more information.
POS templates
Customize certain POS documents to match your branding. Templates are accessed, added and customized from Settings → Document and email templates. See Managing document and email templates for more information.
Closure register report:
Select a default Closure Register Report template to be used across your POS store.
POS quotes
Select a default quote template to be used when printing quotes or emailing them to your customers.
Link POS payment methods to payment accounts
Cin7 Core captures payments made against sales in POS and is able to automatically add payments to sale tasks that have not been consolidated. If you want Cin7 Core to create these payments, you need to map an account from the chart of accounts that has the ability to receive payments. If accounts are not mapped, payments will not be created automatically.
Make sure that you have an account in Cin7 Core for each payment method in POS (Cash, loyalty, credit card, store credits, on account and lay-by) and any additional custom payment methods. This way, the payment will be automatically allocated to the appropriate account. Accounts can be duplicated. Surcharges can be applied to credit card payments or any custom payment methods.
Payment method mappings can also be set at the outlet level. If no outlet level payment method mapping is specified, the default payment method mapping is applied. See Set up Outlets for more information. Cash account can also be set at the register level.
Set cash payment denominations
Bank note denominations of the chosen currency are displayed on the POS register so cashiers can quickly enter cash payments. Depending on your base currency, the bank note denominations may already provided by Cin7 Core. Check the bank note denominations are correct and add any missing denominations before starting to make sales with Cin7 Core POS.
Go to Integrations → POS → Cash payment setup
Use + Denomination to add any missing bank note denominations.
Save to finish.
Enter reasons for adding/removing cash from a register
When using the Cin7 Core POS app, cash may need to be added or removed from a register. Cin7 Core allows you to provide default cash management reasons which can be selected when adding or removing cash. It is also possible to enter a custom reason when adding or removing cash.
Go to Integrations → POS → Cash reasons
Use + Reason to add any cash management reasons.
Save to finish.
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB
- Publish to everyone.4.log-2010416261.zip20 KB