[April 1998]
The monthly price disk contains cost prices from wholesalers. Once authorised by the wholesaler, the update disk compares the supplier's cost price with the user's cost price, and if it finds a difference applies the USERS markup to arrive at a suggested retail.
This cannot affect retail prices unless the price is applied by the user as the update update disk prepares a variance list on the hard disk of possible price changes for the user to step through accepting or rejecting, either at the time or later.
The different causes of problems produce different symptoms;
The RETAIL will be wrong if;
-- The user has the wrong markup on that item (change it) .
Both COST and RETAIL will be wrong if;
-- It there is a duplicated PLU number so the computer matches up the wrong item (change the item that should not have that number)
-- If the cost price was wrong before. E.g. suppose the item used to cost 1.00 and sell for 1.50, and then the cost goes to 1.10... if the cost in the machine was correctly set at 1.00 it will see that the previous markup was 50% and so suggest a new retail of 1.65 to retain 50%. But, if the cost in the machine was wrong previously at 0.50 with a retail of 1.50 the program will see that the user used to have a 300% markup and so will suggest a new retail of 3.30 to preserve this 300% markup. Correct this by changing both the cost and retail to the correct values. Find grossly incorrect cost prices by running the 'unusual stock item' report.
-- If the supplier's cost price is for a whole PACK but the pharmacy prices and sells it as one item. Fix by ticking the 'order in outers only' tick box on the stock cards. The program must always have the cost and retail of ONE UNIT that is sold, not the pack cost or retail. Eg, the price of one unit, not a pack. The 'outers only' tick box tells it to divide the wholesalers price by the pack quantity to arrive at the unit price. When adding this check the cost and retail to make sure they are the unit price in both cases. If they have previously been set to the pack price, the program cannot correct the wrong prices by itself so the tick will seem to be not working. Change them manually, and once the cost and retail are both the unit price and the tick is in place, it will work if the price update disk is put through again.
Related topic