Update, Monthly, PoS, Rolling back

 

[Revised Sep 03]

 

The wholesaler bulk PoS price update is a powerful function that can do a large amount of work very quickly. It can also do a large amount of damage just as quickly if the action requested is not what is really wanted. Some changes can be rolled back;

 

Reversing accidental price change

If some items slip through that you should have deleted before Updating, bring up the list again and fix the unwanted change on the list then 'Update' again. E.g. if item had an old price was $1.00 and a new price $1.50, and you want it to stay at $1.00 but did not notice it and pressed Update, it will go to $1.50. To fix this, bring up the list again, and change the 'New price' to $1.00 (same as the old price) then Update, to change it back. This can be done any time up to the next monthly update.

 

To rollback 'cost only' update.

If a user selects 'cost only update, the markups will all be recalculated to match the old retail and the new cost. This is useful if the costs are all incorrect and the retails correct, but looses the desired markup if selected without thought.

It can usually be reversed with a little work;

1. Read through this section in full, being sure you understand how the rollback is to work, before starting. Any mistakes in this could lead to an unrecoverable situation.

2. Make a backup so that, no matter what happens, you can get back to where you are now.

3. Run the previous month's update again (NOT the current month update which was incorrectly put though as 'cost on', but the month before that.) Eg, If the March update was incorrectly put through as 'cost only' run the February update again). If you have lost it, the support service can send another.

5. Once the variance list is made up accept change cost only. It is important to change only the cost, since that is the one that is wrong. This will change the cost prices back to the old costs, and so compare to the existing (old) retails and so get the correct markup back.

Be aware that it will also change the premiums and drug availability etc back to 1st February, so watch this is dispensing a script during this process. It will not revert any of the patient records or histories though, just pricing.

6. Check a few items to confirm that this has worked as expected, e.g. the old costs are back and the old retail remains meaning that the correct markup is restored.

7. Assuming all is well, then run the current month update again, and this time when the variance list comes up accept change both cost and retail. This will also return the premiums etc to the correct march values.

8. Have a look at a few prices to confirm all is well, so you can restore from the backup if it is not.

 

Related topic

Update, Monthly, PoS