Home » Categories » Solutions by Business Process » Stock Control and Batch Tracking |
Forecasting and Stock Replenishment |
Article Number: 403 | Rating: Unrated | Last Updated: Thu, Jun 22, 2023 at 11:29 PM
|
Datafile Software Forecasting and Stock Replenishment A stock system can pay for itself if it helps to avoid the "lost sale” — the situation where you haven’t made a sale because you had not got the item in stock. An example of this is given in the figure overleaf, which charts stock holding against time to show a typical cycle of events. In some sectors you may be able to substitute a different item, which can reduce the effect of lost sales. For example, if you stock two brands of cola and run out of one, then the other may be an acceptable alternative. The key to avoiding lost sales is to forecast the rate at which sales are made, and therefore to re-order new stock in time so that you do not run out. The Datafile Software stock system contains a number of facilities and reports to help you manage stockholding to maximise sales.Typically a stock controller would review stock on a weekly basis — not necessarily the whole stockholding, but possibly a group of stock codes each week on a rolling basis. A number of pieces of information are needed for these mechanisms: Time Period Unit. You must specify (under the stock System Profiles) a time period that represents the size of filter through which you will analyse your sales and stockholding.Typically this is a week, but could be days (a week might be too long for fast moving stock) or a fortnight, or a month even. This is a global decision and everything else is based on this time period Lead Time. This is defined for each product, and
represents the length of time, measured in the time units just defined, which
would elapse between ordering the item from your supplier and you receiving
it. You do not have to give a lead time
for every item, only to those which you want the system to monitor Minimum Stock Level. For some stock items you may want to set a minimum level, to act as a buffer for variations in demand — see later. For slower-moving items you might set its value at one, so that every time you sell one you are prompted to order a replacement You now have enough information to make one of the first judgements on your stock items — is it time to order more? A typical cycle of events is shown in the following diagram: You can ask the computer whether or not you have enough stock to satisfy demand and still not fall below the minimum stock level during the time it would take to order and receive more (this is based on the estimated usage of this item and the lead time). If so, then you can relax for a week, say. If not, you should consider ordering more — see Potential Out-of-Stock Report described in more detail in the User Instructions section and Buying Quantity below.In the above example, the stock controller got it right the first and third time, but was a bit slow re-ordering the second time round. Even the minimum buffer stock was not enough to prevent the item becoming out of stock. Were sales lost because of it? We’ll never know for sure that some customers didn’t buy elsewhere. |
Attachments
There are no attachments for this article.
|
Security and User Manager - Batch Tracking
Viewed 1452 times since Tue, Jun 19, 2012
Default Batch Type for New Stock Items
Viewed 1449 times since Fri, Jun 8, 2012
Currency Considerations
Viewed 1455 times since Mon, Jun 18, 2012
Assemblies - Omit Component from Build
Viewed 1598 times since Fri, Jun 8, 2012
Maintain Stock File - Stock Control
Viewed 1576 times since Tue, Jun 19, 2012
Expand Data Files - Batch Tracking
Viewed 1386 times since Tue, Jun 19, 2012
Batch Statements - Batch Tracking
Viewed 1457 times since Wed, Jun 20, 2012
Automatic Reports - Stock Control
Viewed 1678 times since Mon, Jun 18, 2012
Location Transfer - Stock Control
Viewed 1463 times since Mon, Jun 18, 2012
Works Order Entry - Batch Tracking
Viewed 1382 times since Tue, Jun 19, 2012
|