| · |
Global
changes |
| · |
Multiple
sales locations. Reports can focus on an individual location
or be consolidated over all locations to give you a company
wide analysis |
| · |
Built in
data backups. Backup the database remotely. |
| · |
Transaction Server. Imports
data from the POS in real-time giving up to the minute sales
figures. |
| · |
System
Link Module. A simple, but powerful set of technologies
which enables developers to quickly develop an interface
between Back Office and any external system. |
| · |
Scheduled Jobs. Schedule
data changes and communications with your POS terminals
using Windows scheduler. |
| · |
Centralised
exception log for easy fault diagnosis by our support team. |
| · |
Customer Accounts |
| · |
Customer
statements and transactions reports. |
| · |
SQL Server relational database
system |
| · |
Integrated
SAGE Line 50 link. Connects directly to Sage’s database
to synchronise products, customers, customer sales and cash
sales. |
| · |
Integrated Stockade link.
Receives product data from Stockade and sends back sales
and financial data. Back Office essentially behaves as a
cash register plug-in in Stockade to provide a smooth upgrade
path from Stockade 1 to the SQL versions. This allows Back
Office to be rolled out in stages. |
| · |
BHT 8000
Hand Held device support. Price changes and price checking
supported. |
| · |
Comprehensive user set-up.
Allow your staff to only view, edit or have full access
to data that you want them to. Users can also be limited
to only work with certain POS locations. i.e. can change
prices in shop A, but not shop B. |
| · |
Label printing
and label templates. Print shelf edge or sales labels as
and when you want. |
| · |
Enhanced security and database
robustness. |
| · |
Remote
database connectivity (TCP/IP). LAN, WAN and Internet. |
| · |
DPOS transaction log importing.
This gives more reporting possibilities. |
| · |
Centralised
POS Job log (stored in database). |
| · |
MDI document interface (i.e.
multiple browser windows) and a fresh new look. |
| · |
Editable
and customisable (user specific) browsers. Any field displayed
in the browser can be used to order the list of records. |
| · |
Copy functions in all browsers.
This copies the selected record in a browser to a new record. |
| · |
Enhanced
edit screens. Each edit screen now has navigation capabilities
within them to easily move between records. The user can
also add new and delete records from with the edit screen
without having to drop back to the browser. |
| · |
Sub Departments. |
| · |
Automatic
program updates. Program files are stored in the database.
When a user logs on the program checks for newer versions
of files in the database and updates accordingly. This ensures
all users are using the correct version of the program for
the database. |
| · |
Enhanced report linking.
Multiple reports can now be linked to 1 report type (e.g.
Sales Report). At the time of taking the report (or refreshing)
the user can choose the report file to use. The system remembers
the user’s last report used as well. Reports are also
stored in the database. This works in the same way as the
program updates and ensures that users are always running
the correct version of the report. |
| · |
Enhanced
report settings. Report settings can now be changed in the
report window without having to close the report and start
again. All reports, where logical, have multiple selection
capabilities (i.e. selected locations and groups in sales
reports). |
| · |
New reports: Cashiers financial
report and hourly sales report. |
| · |
Transaction
Server tray application. This program sits in the background
checking for transaction log files in a selected folder
(usually C:\tillserver). Files are imported directly into
the database giving an online real-time system. |
| · |
Enhanced PLU Updates section.
PLUs are now flagged with an update type (i.e. price change,
minor change, full change). Type of update can now be selected
in the POS Job (i.e. only export price changes). |
| · |
Exception
processing of transaction logs. When importing transaction
logs, if the system cannot import the line (i.e. unknown
record type or invalid field value) then it is stored in
an exceptions file in the database. These exceptions can
then be processed later. |
| · |
Alphanumeric PLU codes can
now be used. |
| · |
Real-time
sales screen. Configure 10 views of 4 panels to display
sales data as it happens. 4 screens can be opened at once
to give a total of 16 different sales windows. Choose to
group data by POS Location, POS Terminal or Cashier. Display
data as financials or hourly sales. Please note that Transaction
Server needs to be configured and running for this to work. |
| · |
PLU Change Templates. Schedule
price changes and PLU data changes. |
| · |
System
Options - Sales Rollover Hour. Transactions recorded at
the POS before this hour will be treated as the previous
day's transactions. |
| · |
Cashiers Hourly Sales Report. |
| · |
Context
sensitive help system |
| · |
Write Offs/Wastage Report |
| · |
Promotions
and Promotions Sales Reports |
| · |
Import keyboard layout from
POS. |
| · |
Import
PLUS function. Import PLU data from a CSV file. |
| · |
Import Customers function.
Import customer data from a CSV file. |
| · |
Toolbar
customisation. Optimise your workflow by organising the
toolbar to suit you. Each toolbar layout is stored per user. |
| · |
Email support from within
the program any exceptions in the program for quick fault
diagnosis by our support team. |
| · |
Active Users screen. See
instantly who is currently logged on and from what computer. |
| · |
Auto EAN check digit calculations.
This automatically appends the EAN check digit to a PLU
code to provide trouble free scanning. |
| · |
Weighted and price encoded
PLU codes handled. |
| · |
Gross Profit Calculator.
Set your products prices up by evaluating the gross profit
or by simply telling the system what G.P. you would like
for that product. |