Using POSper/User guide
Using POSper
[edit | edit source]Sales Workflow
[edit | edit source]Choose the sales window from the left hand menu options.
Using a Barcode Scanner
[edit | edit source]Simply scan the barcode. Each item scanned which has an entry in the stock table will add an entry to the sales ticket. When all of the items have been scanned, press the equals '=' sign on the screen and the payment options dialog will appear. The dialog has options for cash, cheque, ticket, card, and free. Choose the relevant option e.g. cash and type in the amount handed over by the customer. POSper will calculate the change. Press the printer button to print the receipt and open the till. Press OK to complete the transaction and return to the sales screen.
Using a Keyboard or the On Screen Keypad
[edit | edit source]This functions much as the barcode scanner does. Simply type in the barcode number and POSper will lookup the barcode item in the stock table. Then when return on the keyboard or the button with the barcode symbol on the screen is pressed, the item will be added to the sales ticket.
Using the Catalog
[edit | edit source]POSper maintains a catalog of current stock items, if icons have been added in the stock management screen they are displayed on the bottom right of the sales screen using images loaded into the database at the time of the stock update. If the images are not added to the stock items, the default icon is used.
To use these icons to make a sales transaction, select the category the stock item is in. Type in the number of items to be sold on the on screen keypad, press the multiply button '*' and only then choose the item itself from the catalog window. If only one item is to be sold, don't bother with the number or the multiply button, simply press the item's screen icon. The required number of items will be added to the sales ticket. When all of the items are added, complete the transaction as per the barcode scanner.
Selling General items which don't have barcodes/stock entries
[edit | edit source]Previously add a "General Item" entry to the stock database with an icon and with £0.00 as the price. When selling such an item, choose the general item from the catalog to add the item to the sales ticket. Then select the "General Item" on the sales ticket and press the pencil button to change the price and number of units being sold.
Reports
[edit | edit source]If you need reports that are not available in POSper you'll have to make your own. But don't worry. It's not hard.
You can change out any of the SELECT statements below for ones from here.
sources:
http://sourceforge.net/forum/forum.php?thread_id=1258240&forum_id=434921
Reporting from the Command Line
[edit | edit source][note: remember SQL is case sensitive...even in windows...]
For postgres installations:
To run in Windows, save this as filename.bat and simply double-click it:
"c:\Program Files\PostgreSQL\8.1\bin\psql.exe" -U username -d posper -c "SELECT * FROM stockdiary;"
To create a file that you can import into (for example) excel, add this to the end:
-o filename
For MySql installations:
mysql -u username -p --execute="SELECT * FROM stockdiary;" posper
You'll need to replace "username" with a real username and "posper" with the database name (posper is default). You will be prompted for a password after you hit enter.
Postgres' pgAdmin
[edit | edit source]Extremely Easy. Once the server connection has been added, go to tools, Query Tool. You simply need to paste the query into the box.
Making Printable Reports with iReports
[edit | edit source]Download iReports here: http://sourceforge.net/projects/ireport/
(more here)
PHPMyAdmin
[edit | edit source](more here)
Errors
[edit | edit source]Notice: message.nosave
[edit | edit source]After completing a sale you get a message box and this error: (with or without the psql/postgresql words)
net.adrianromero.data.loader.DataException: org.postgresql.util.PSQLException: ERROR: duplicate key violates unique constraint "tickets_pkey"
explanation:
[edit | edit source]There are sales stored in the database with the same ticket ID that the ticket you are trying to save (pressing =).
solution:
[edit | edit source]PostgreSQL:
If the result of:
select max(TICKETID) FROM TICKETS
is greater than:
SELECT last_value from ticketsnum
Do this:
SELECT setval('ticketsnum', (select max(TICKETID) FROM TICKETS))
MySQL:
if the result of:
SELECT max(TICKETID) FROM TICKETS
is greater than:
SELECT ID FROM TICKETSNUM
Do this:
UPDATE TICKETSNUM set ID = (select max(TICKETID) FROM TICKETS)