Setup guide, permissions and daily workflows
Use this guide before installing Kit POS Desktop on a till. It covers the exact role permissions needed to log in, how table and PIN settings behave, and the selling flows your cashier can run offline.
Requirements
Device
- Windows 10/11 64-bit, macOS 12+, or a modern 64-bit Linux distro.
- 4 GB RAM minimum; 8 GB recommended for busy restaurants or multi-user tills.
- 500 MB free disk space plus room for offline sale history.
Network
- Internet is required for the first username/email login.
- After setup, selling continues offline and syncs when the connection returns.
- Keep the server URL pointed to
https://pos.kit.africafor production.
Printing
- Receipt and KOT/BOT printing use the same Kit printing flow as web POS.
- Install QZ Tray when using ESC/POS receipt printers.
- Kitchen and bar routing follows the product station setup in Kit.
Permissions required to log in
Assign these in Kit under User Management, Roles & Permissions.
| Permission area | Permission | Why it is required |
|---|---|---|
| KOT POS Desktop | Login on a new device (pos_desktop.login_new_device) |
Allows the user to register this till and pull the business data needed for offline use. |
| Products | View products (product.view) |
Allows the desktop app to show products, variations, prices, lots and stock. |
| Sell | Sell products (sell.create) |
Allows the cashier to create sales, quotations and suspended token orders. |
If any required permission is missing, Kit POS Desktop stops the login and shows User permissions are insufficient. Add the missing role permission, then sign in again.
Connect a business to the till
1. Install
- Download the installer from the desktop app page.
- Open Kit POS Desktop and confirm the server is
https://pos.kit.africa. - Use a Kit username/email and password for the first login.
2. Choose location
- If the user has more than one location, choose the till location.
- The app downloads products, customers, staff, settings, taxes and payment accounts.
- The logged-in user becomes the user shown in sale Added by.
3. Staff login mode
- If staff PINs are enabled, eligible staff can use the PIN pad after setup.
- If service staff PINs are disabled, those users do not get PIN pad access.
- If the business has no tables module, staff go straight to POS and sell directly.
Daily selling workflows
Cash sale
- Open POS, add products, quantities and discounts.
- Choose cash or express checkout.
- Finalize. Fully paid sales sync to Kit Online as paid.
Credit sale
- Select or add the customer before checkout.
- Finalize with no full payment or partial payment.
- The due balance appears on the customer ledger after sync.
Quotation
- Add products in POS.
- Use the quotation action instead of final sale.
- No stock is deducted until the quotation is converted to a sale.
Token / suspended sale
- Add items, table or waiter where enabled.
- Suspend the sale to create a token.
- Resume the token later and finalize payment.
Kit Pay mobile money
- Choose Kit Pay / mobile money in checkout.
- Enter the phone number and amount using the visible numpad.
- Confirm once the payment status succeeds.
Invoice numbering
Desktop sale invoice and order numbers use uppercase
KOD-{login count}-{invoice no}, for example KOD-7-23.
Sync, deleted records and recovery
| Situation | What to do |
|---|---|
| Sales are pending | Keep selling. They remain queued locally and retry automatically when the server is reachable. |
| A sale was deleted in Kit Online | Ask an admin to open Reports > Deleted Documents, restore the sale, then sync the desktop app. |
| A paid sale shows partial | Sync again and check the sale payment lines. Fully paid desktop sales should reflect as paid in Kit Online. |
| User attribution looks wrong | Sign out and sign back in as the cashier who is selling. Desktop sales use that user as Added by. |
Troubleshooting
User permissions are insufficient
Add pos_desktop.login_new_device, product.view and sell.create to the user role or override, then try again.
No tables screen
This is correct when the tables module is not enabled for the business. The app logs straight into POS and sells as takeaway/direct sales.
No PIN pad access
Confirm staff PINs are enabled and the user is allowed to use a PIN. Businesses with service staff PINs disabled do not expose those staff on the PIN pad.