Questions about RMS, need help.

Hi Tony,

1. Tracking Lost Sales

There are quite a few ways you could do this and I'm sure the others will have some good suggestions too. But I would use the messages function.

Simply set up a cashier called lost sales and whenever it occurs the cashier on the floor can send a message to lost sales. Upside: It uses free text fields and compiles the information in a central location. Downsides: You will have no reporting or exporting functionality of data. Also I'm not sure if there are any limits on the number of messages a cashier can hold.

"T> 1. Does RMS have the ability to track lost sales?

Hi Greg,

I gave this a try this with error. I called up the lookup code, simply entered a new description in the description column, and tendered. But when I went to print the report it turned out the original description name.

Do I need to go > 1. Tracking Lost Sales

1. Tracking Lost Sales

In other words the program won't do it, it has to be done manually.

As for track> You could use a PO filter set to make PO's based on sales from a previous

When you change the description of an item in a transaction, that description is only kept in the receipt image; it is not stored as text anywhere in the database.

Also, changing the description under Item Properties each time won't work either, because the Description is pulled from the Item table when the report is generated.

The messages idea would work, however you will have to write a custom report which pulls the text from the Messages table (there is no existing report to do this).

My suggestion would be use a spreadsheet, outside of RMS, to keep track of lost sales.

I'll also note that this something that could be developed as a customization .. for example, you could add the items to the transaction, then hit Escape to abort the transaction and a customization hook would record the items to a spreadsheet or database table .. it could even prompt the cashier for a reason of losing the sale.

You could use a PO filter set to make PO's based on sales from a previous date. For instance, filter a PO for a department or supplier based on sales for last Nov1 thru Dec 31. Then print and delete them. This will give the buyer data to use to make purchase decisions with.

As for tracking customers you can have customers called, Mail, Paper, Friend, Walk In, etc. and then ring up the sales based on where they found out about the business using the right customer. I find this is ok but lazy cashiers ring up using the least path of resistance and just hit customer 1 every time for instance. But you could try it. mt

For #2, I'm not sure what you mean. Do you mean forecasting future sales and stocking based on those? The only inventory feature that might be applicable is the "Restock Level" and "Reorder Point" properties for each item. This allows purchase orders to be generated automatically when an item reaches the "Reorder Point".

As for #3, this would have to be done with a customization.

That would be a pretty advanced ordering system. RMS definately doesn't do it otu of the box. I haven't heard of anyone attempting to do it either.

That is usually the type of thing that a purchasing manager or buyer determines themselves. Seasonal businesses (especially with clothing) are always constantly changing and have unexpected conditions which would prevent items from being orderes (discontinuation of the item, new model and item #'s, decisions not to carry that brand anymore, etc), so I think it would be very difficult to automate this process. There are just some things that are better left to humans :)

Tony,

Another idea would be to setup a Primary Sales rep for the customer in the Customer Options tab. Create sales reps as Mail, Phonebook, Walk-in, etc. This is reportable, permanent, and will work as long as you don't pay commissions to the sales rep. You could then run a Commission report to see what's happening.

You can add an Item Comment to a line item. There is an option in SO Manager, Configuration that determines if the comments will be saved to the DB or only to the journal. I'm not positive, but I think that if you turn on the setting to save item comments, the edited description would also be saved as a comment on the Transaction Entry - give it a test and see...

Hi Tony,

I think you'll find after testing Jeff's previous suggestion, that it's a pretty good out of the box solution. However, if it doesn't cover your needs we are currently developing something similar for a client.

It is a very basic add on designed to capture zip and country details at POS. Basically when the transaction is tendered a pop up box appears and details can be selected from a drop down box (or two or three).

At this stage I am not sure where the data is p> Tony,

Correct, the comments are in fact saved to the database (TransactionEntry table).