When a part is sold via c9 point of sale, the part sold to the customer can be either:

• In stock – on the shelves in the dealerships premises - as such the part is sold to the customer immediately.
• Not in stock and as such the dealership will need to place an order with their supplier to source the part on customer's behalf.

For parts that are ordered there are multiple things that the system operator needs to be aware of when using the c9 DMS.

Read more...

C8 Systems has been designed to maximise user productivity by focusing on making it as simple and fast as possible to perform operations such as selling parts.

With advent of graphical operating systems such as Microsoft Windows, the computer mouse has become the primary mechanism which people use to nagivate a computer program.

A mouse is good for 'discovering' how software works – you can click around and sort of figure things out most of the time.

A mouse is no good though for repetitive operations that you perform over and over again. Beyond RSI (Repetitive Strain Injury) the key problem with a mouse is that using a mouse is significantly slower. For example, a user familiar with C9 and keyboard shortcuts can sell a single part in less than 5 seconds, where a mouse oriented DMS can take substantially longer than this.

Read more...

• Redesigned units menu. To make it easier to feed in rebates and writebacks
• Modified main menu to include correct support/admin contact details
• Tweaked select job so job records are preferentially highlighted. Makes user experience smoother.

This version needs to modify the database. On upgrade it will ask you to log out of all terminals.

• Added unit rebates
• Added tradein writebacks
• Changes to import generic
  • Improved memory efficiency when importing .xlsx files
  • Cope with files which have more than 10 columns better; by ignoring columns that appear to not contain data
• Units Point of Sale can now print/request Tender information. Needs to be enabled via setup.
• Print stock/daily orders. Increased page real-estate for part description. So when part description ends with critical data, i.e. engine oil 2T/4T and/or size of the bottle tends to be at the end of the part description.
• Business modify activity/ledger item. Fixed date format

• Improved range of files that import master file (generic) will handle
  • .xlsm files are just .xlsx file. Handle accordingly
  • if file does not have an extension. Inspect the file to determine if it is .xls or .xlsx type
• Messenger, if on sending sms/email it appears that messenger is not working then auto-restart it on the terminal that detected this
• Menus and buttons in c9. Fixed menus which use mnemonic hotkey shortcuts so that with any screen that has hotkeys, all buttons are hotkeyed and no two buttons share the same mnemonic

It has come to our attention that there is a potential problem in C9's database that may cause data loss or corruption on a power failure. In past 9 months we have had 4 instances of data corruption, 2, in the past week, are confirmed to be related to power failures. One recently required the dealer to completely rebuild and restore from backups.

This page contains important information on how to configure your c9 to be more resilient against such failures. It is strongly recommended that you read and follow the instructions on this page at the earliest opportunity to minimise risk of loss/corruption of data.
Read more...

• Import Master File. Now supports password protected XLS and XLSX files.
• In point of sale. Give user ability to either order on daily or order on stock for individual parts
• Accounts. In view old transactions allow user to jump to appropriate workshop, spares, units invoice type.
• Export Orders. Provide option to 'collapse' same part number appearing multiple items into a single line item.  some suppliers cannot handle part appearing more than once in a single order. i.e. Kawasaki online.
• Workshop weekly calendar. Memorize pickup checkbox filter setting
• Print job card. If print barcode is disabled then print job number on the top in a normal font
• Workshop & POS. Display what * means if there are any parts/jobs on screen with '*'
• Improved readability and shrunk size of c9*.log files
• Under some conditions an upgrade of c9 will not upgrade database properly. System will be unusable without remote support. Changes in this version will make the system more resilient to such problems.
• Bugfix with database access: sometimes database would get into a state where cannot do anything and had to exit c9.
• Bugfix: type in date 1.1.10000 - would reformat as 1.1.0000.  This could trigger above problem in some circumstances
• Workshop modify Bug. If you change unit, but select 'view unit' in change unit list, this would setup system so that you could not save modification. It would report an error: Primary Key Position not established (33). If you did not view the unit, it would work okay.

Supports mail merging to SMS or Email notification.

Be aware of anti spam legislation (Spam Act 2003). You need to provide users an ability to opt out. A simple solution is to define a customer account customer field for Mailer (Y|N). And implement a miner rule test i.e. Mailer: /N. Later versions of c9 will include a check box opt-out option on accounts that will make configuring this sort of thing easier.
Read more...

C9 includes a new feature in version 4.156; the ability to report on multiple cash tills. For example your spares till and workshop till may be in completely different buildings.  This new feature now allows you to separate out transactions into multiple locations.  This post explains how to setup and use this feature.

Read more...

This version needs to modify the database. On upgrade it will ask you to log out of all terminals.

• Support Multiple Cash Tills for Reporting
• Print Stock Take Sheets. Allow user to specify order of parts on the print list.
• Workshop weekly planner
  • Corrected display of customer code
  • Permit filtering of picked up jobs from planner list
• Enabled debugging as a permanent feature. A large portion of bug reports require detailed logging in order to understand the problem. Most reported problems these days are user error. Detail logging logs everything a user did, so not only is better diagnostic data provided but opportunity to separate user errors for real defects is improved. Downside is increased disk usage; to deal with this files older than 2 months are automatically removed.