damages

We setup a customer account at the register with 100% discount sell the items to that account. That way you can run reports on the account usage. OR some locations do Standarn Transfer Outs from RMS Manager.

Jas> What would be a good method to transfer out damages or expired goods? > > Thanks

A transfer out to nothing, or to the supplier works. Otherwise I have seen people use offline inventory for this purpose as well.

What we did is create a return to offline reason code for each supplier, that way you can report on that reason code and know exactly how much is returned to each supplier. Then when we have a damaged item we go into the items properties and manually remove them from inventory using the appropriate reason code for that item. Once a month(or however often you like) run a 'Item movement history report with cost' report on each reason code to get the value for your accounting program. The default movement history report doesn't include cost, so you will need to download the one with cost added from customersource. This also works well for items removed from inventory for store use. We have separate reason codes setup for this as well. When you're ready to send the items back to the supplier go into the offline inventory and highlight each item that goes to the appropriate supplier(they will be grouped together by reason code) and transfer the items out of offline inventory to that supplier. You can then print a transfer order for those items to give to the supplier and one to keep for your records. One benefit of doing it this way(besides being able to report on it effectively)is that you can remove the item from inventory both at POS and at Manager. Plus, you're not tied to selling it to a fictitious entity at POS, which would mess with your sales(sell it for $0 and your profits screwed up), or tax collected(it would show up as a tax exempt sale) reports. These things are why reason codes where developed. Use them to your advantage. Craig

"Ryan" wrote in message news: snipped-for-privacy@TK2MSFTNGP03.phx.gbl...