Stores, outlets, and registers
Cin7 Core POS is divided between stores, outlets, and registers. Each store can have its own catalog, settings, users, and logs, and is tied to a location in Cin7 Core. Stores can have one or more outlets, and outlets can have one or more registers.
At the store level, you can configure which products are listed for sale, which users are invited and what permissions they have, and the default settings (UI, tax rates, account mapping).
At the outlet level, you can set outlet-level SKUs, set outlet level settings (UI, tax rates, account mapping). Outlet-level settings take priority over store-level settings.
At the register level, you can set even more specific register-level settings (UI, tax rates, account mapping). Register-level settings take priority over outlet-level and store-level settings.
Prerequisites
At least one POS register must be included in or added to your subscription
Set up locations
Create a new POS store
POS registers and your subscription
Cin7 Core POS is divided between stores, outlets, and registers. Each store can have its own catalog, settings, users, and logs, and is tied to a location in Cin7 Core. Stores can have one or more outlets, and outlets can have one or more registers.
Cin7 Core POS is an add-on to the base subscription. Purchasing the add-on will unlock a POS store, outlet, and register. Additional POS registers can be purchased to add to the subscription, which can all belong to one store or store, or be distributed among multiple stores.
Each of the examples below requires 3 POS registers to be added to the base subscription:
Note: Legacy subscribers whose account dates from before 1st September 2023 will have no change to their current functionality of store, outlet, and register numbers.
Stores and outlets
For businesses that are operating from multiple locations, setting up outlets will help manage inventory and track sales effectively from every location. You can have one POS store outlet per location. If you have multiple POS stores, each store can have one outlet per location.
You can only add an outlet for a location that is already added to your Reference Books. See Locations for more information about adding and configuring your organization's locations if necessary.
Add an outlet
Navigate to Integrations → Point of Sale (Cin7 Core) → [store name] → Outlets setup tab.
In the Outlets column, click + New or select the location where you want to add your outlet.
-
Fill in the details of your outlet. Mandatory fields are marked with an asterisk.
Active: When an outlet is set to inactive, it can no longer be used or accessed by users.
Outlet name*: Name of the outlet.
Outlet location*: Cin7 Core location where outlet stock is picked from.
Default sales tax: Tax rule to apply to sales from this outlet. If left blank, sales tax specified in the Setup tab will be applied to all sales from this outlet.
Cash account: If the "cash" payment method has been overridden at the outlet level (see Link payment methods to payment accounts on outlet level), the payment account will appear here. If left blank, the cash account specified in the setup tab will be used for this outlet.
Receipt template: Select a receipt template to be used for this outlet. If left blank, the receipt template specified in the setup tab will be used.
Square integration to process returns: Select a Square integration to process POS payments and returns.
Print notes: Print notes on the sale receipt.
Print discounts: Print discounts on the sale receipt.
Surcharge tax rule: Select a surcharge tax rule to be applied to payment method surcharges on sales for this outlet. If left blank, surcharge tax rule specified in the setup tab for the POS store will be applied.
Link payment methods to payment accounts on outlet level
With this option you can override existing payment method account mapping on the setup tab at the outlet level. Click this to open a popup window where you can enter the payment method name and select a different payment account.
If the payment method name entered matches a payment method name from the setup tab (Default methods: Cash, Loyalty, Credit Card, Store credits, Layby; any custom payment methods), it will override the default payment account mapping. If the payment method name entered does not match a payment name from the Setup tab, it will be entered as a new custom payment method for this outlet.
E.g. Here, Cash and Credit Card payment method names matches payment method names on the Setup tab, the payment account will override the default. Bank Transfer does not match a name on the Setup tab, and will be entered as a new custom payment method for the outlet.
Set product outlet level SKUs for advanced barcodes
If you have selected GS1 based, Weight based or Price based barcodes in your integration settings, you will need to add product outlet level SKUs so your barcodes can be read correctly unless the product level SKU is configured to support the advanced barcode setup. See Advanced barcodes for more information.
Add registers
To run Cin7 Core POS on multiple devices in the same store, you need to add as many registers to the outlet as there are devices you wish to use for POS. You will need a license added to your base subscription for each additional POS register. Several settings can be configured at the register level.
Navigate to Integrations → Point of Sale (Cin7 Core) → [store name] → Outlets setup tab.
In the Outlet details column, click + New to add a register. Existing registers will be listed at the top of the outlet details column, clicking a register icon will open its details.
-
Fill in the details of your register.
Active: When a register is set to inactive, it can no longer be used or accessed by users.
Name: Enter a name for the register.
Cash account: Asset account with ability to accept payments. If left blank, cash account specified at outlet level or in the setup tab will be applied to the register.
Receipt template: Select a receipt template to be used for this outlet. If left blank, the receipt template specified in the outlet level or in the setup tab will be used.
Till discrepancy: Current asset account for till discrepancy. If left blank, till discrepancy account specified in the setup tab will be applied to the register.
Petty cash: Expense account for petty cash. If left blank, petty cash account specified in the setup tab will be applied to the register.
Cash in/out: Current asset account 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. If left blank, cash in/out account specified in the setup tab will be applied to the register.
Cash float: Current asset account used to post your daily float and float adjustments. If left blank, till discrepancy account specified in the setup tab will be applied to the register.
Receipt prefix: Add an optional prefix to the receipt to identify the register.
Receipt suffix: Add an optional suffix to the receipt to identify the register.
Quick Key: Add Quick Keys to enable you to quickly put through sales of your most popular products.
Catalog size: Select the catalog size that will be applied to the register. This controls how many rows and columns of product tiles will be displayed on the screen. If left blank, catalog size specified in the Setup tab will be applied to the register.
Tiles visibility: Select the default view of the product tiles. If left blank, tile visibility specified in the Setup tab will be applied to the register.
Product availability icon: Toggle this button to turn on/off the product availability icon on the product tile. This overrides the option specified in the setup tab.
- 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
- 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
- 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
- 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.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB
- Publish to everyone.4.log-2010416261.zip30 KB