Contents
1. Eight core tabs; nine with Extra permission2. Units and conversions — read this twice3. Prices: what do the six levels mean?4. The Status tab: where and how many?5. Movements: the product's history6. Equivalents: "if this is out, give that"7. Deleting a card: usually impossible, and that is good8. Frequently asked questions9. Glossary10. Technical files on the stock card11. The card image (main database) and the images (EK1)12. The card's type and family — which tabs, which fields?12.1 Where the type is shown and where it is changed12.2 Tabs and sections hidden by family12.3 Giving a type to "Unclassified" old cards13. The Reports tab — the card's nine charts14. The Reports tab — four new reports15. The Reports tab — five new reports (profitability, classification, planning)16. The Reports tab — planning reports (availability, demand forecast, basket analysis)Help › Stock Card
The Stock Card — A Product's Identity
A stock card is a product's identity document in the program: its name, units, prices, where and how many there are, what happened to it in the past. Setting a card up correctly takes five minutes; a badly set-up card produces wrong invoices, wrong stock and wrong profit for months. This guide focuses on those five minutes — especially the units section.
1. Eight core tabs; nine with Extra permission
The actual tabs are General · Prices · Status · Movements · Equivalents · Extra Information · Images · Technical Documents. Extra is visible only to users with stok_extra permission. Warehouse, purchasing and sales staff who work with product definitions can read the card; creating, changing and deleting a card requires stock-card write/delete permission.
The Images tab manages two layers together: the product photographs in the EK1 database and the single card image kept in the main database — the card image is the small picture shown in the list and in the card header, described in section 11.
In addition, the Fabric tab appears only while the production profile is textile (or the custom profile has fabric inspection switched on); the profile is chosen under Settings › HNR Preferences › Company Information › Production Preferences. In an automotive or Level 1 company the tab is never drawn — if the profile changes while the tab is open, the card falls back to the first tab.
The number of tabs also depends on the card's type: on a card in the expense family the Prices and Status tabs are never drawn, and in the machine/equipment family Prices is not. The full rule is in section 12.
🗺 What each field does Figure 1 — When creating a card, General and Prices are enough; the rest fills in over time.
2. Units and conversions — read this twice
You may sell the same product by the piece and by the box. The program solves this with three units on one card: a main unit and two alternatives, tied together by a conversion factor. "1 box = 12 pieces" is that factor.
Figure 2 — If a unit's name changes, the server updates it on documents itself; but changing the factor later distorts history.
If the card ran for a year as "1 box = 12 pieces", every past document was written with that factor. Changing it to 24 leaves old documents untouched while new calculations differ — a permanent drift appears between stock and cost. If the packaging really changed, the correct route is a new stock card.
You can give each unit its own barcode (a piece and a box have different barcodes so scanning picks the right unit). Barcodes are stored lower-cased — an HNR rule; typing capitals still stores lower case. A barcode you remove from the list is deleted when you save the card.
3. Prices: what do the six levels mean?
Sales prices (FIYAT1–6) are six separate price levels — so the same product can be sold to different customer groups at different prices. Which customer sees which level is decided by the price list field on the account card; on document entry the price is filled from there automatically.
| Field | What it is for |
|---|---|
| List price (FIYAT1) | The public, undiscounted base price. The other levels usually sit below it. |
| FIYAT2–6 | Dealer, wholesale, contracted customer… the naming follows your business. |
| Sales discount | The discount percentage applied to this item by default. |
| Purchase discount | The discount your supplier gives you — used on purchase documents. |
| KDV % | The item's tax rate. Document VAT comes from here; if it is wrong, every invoice is wrong. |
The card shows a Recorded cost field, and the program itself notes beside it: "the COST field is not maintained in this database; do not use it as the truth about cost." For the real cost look at the purchase entries on the Movements tab, or for manufactured goods at the production confirmation cost. Never base a pricing decision on this field.
4. The Status tab: where and how many?
This tab lists how many are in which warehouse, warehouse by warehouse, with a Total on hand at the bottom. It is the screen that answers a salesperson's "can I promise this?". The Minimum level is set here too: items that fall below it are listed in red on the Warehouse → Replenishment tab.
The Planned Production card shows what remains on open work orders. Finished-goods receipt is the quantity that will be produced into this item; component issue is the quantity of this item that open orders will consume. Future-dated lines separate the part planned after today. Stock after production is a forecast; actual on-hand does not change until a confirmation is posted. Before promising stock, also check After orders + production in the document-entry item panel.
If you add the warehouse rows up yourself you may get twice the truth: the list also contains a row carrying the grand total. Use the Total on hand figure the screen gives you. This is a trap the system's own reports have to watch for.
5. Movements: the product's history
Every in and out sits here in date order: with which document, from/to whom, how many, at what price. Each row also shows the quantity remaining after this movement — so you can see what the stock was on any given day. When a number does not add up, this is where you walk backwards.
"Hide inter-warehouse transfer slips" — transfers are not buying or selling; hiding them leaves the real commercial movements. If you are warehouse staff you only see your own warehouse's movements anyway; that is not a restriction but noise reduction.
6. Equivalents: "if this is out, give that"
When different brands or sizes do the same job you define them as each other's equivalents. The benefit: when the item a customer wants is out of stock, the salesperson can look at the list and say "we have this instead" — without hanging up the phone. A small field that wins back lost sales.
7. Deleting a card: usually impossible, and that is good
A stock card that has movements cannot be deleted — the server refuses. The reason is simple: invoices, delivery notes and production records hang off that card, and deleting it would make all of them meaningless. Instead of deleting an unused card, make it inactive; it disappears from lists but keeps its history.
8. Frequently asked questions
I cannot pick a unit on the document — it says "invalid unit".
That unit is not defined on this stock card. Add it under Units and conversions on the card's General tab (name + factor). If the card cannot be read from the server the program says so too — then refresh the window (🔄).
I changed the price — do old invoices change?
No. A document stores the price inside itself as of the moment it was issued. The card's price only feeds future documents. This is correct: a past sale's price is that day's price.
The same product exists twice — can I merge them?
Cards are not merged. What you do: set the unwanted card inactive, move its stock to the correct card with a transfer/adjustment slip if needed, and add it to the equivalents list so searchers land on the right card.
9. Glossary
| Türkçe | English | Bahasa Indonesia |
|---|---|---|
| Stok kartı | Stock card / item master | Kartu stok |
| Ana birim | Main unit | Satuan utama |
| Çevrim katsayısı | Conversion factor | Faktor konversi |
| Barkod | Barcode | Barkod |
| Liste fiyatı | List price | Harga daftar |
| Fiyat seviyesi | Price level | Tingkat harga |
| Satış / alış iskontosu | Sales / purchase discount | Diskon jual / beli |
| KDV oranı | VAT rate | Tarif PPN |
| Toplam mevcut | Total on hand | Total tersedia |
| Min seviye | Minimum level | Level minimum |
| Muadil | Equivalent / substitute | Padanan (muadil) |
| Hareket | Movement | Pergerakan |
| Pasif kart | Inactive card | Kartu pasif |
To use this card on a document see Document Entry; for per-warehouse stock and replenishment Warehouse; for the cost of manufactured goods Production.
10. Technical files on the stock card
Attach the part's technical drawing, specification, certificate, and control plan to its stock card. Enter revision for drawings/specifications/control plans and document number plus validity for certificates. For customer-owned drawings, set customer property and the company security class.
When revision changes, do not delete the old attachment; upload the new version as a new attachment. Field and cancellation rules: Practical User Handbook.
11. The card image (main database) and the images (EK1)
Images on a stock card live in two layers. The photographs on the Images tab are kept in the EK1 database: their number is unlimited, they may be high resolution and they can be used on document/PDF forms. A downsized copy of one of them is kept in the main database; that one is called the card image. The split has a practical reason: the stock list and the card header must show the picture without delay, while EK1 carries large files and does not exist at all in some companies.
The card image appears in two places: in the header of the stock card (to the left of the description) and in the Code column of the Stock list. In the list it is drawn only next to codes that have one — the server is asked once which codes have a card image, so a list of thousands of rows makes no wasted requests.
You choose it on the Images tab. The ★ Use as card image button under each picture downsizes that picture and writes it as the card image, replacing the previous one. When the card has no card image and you upload the first picture, the program sets it as the card image by itself and says so with a notification. The Card image box at the top of the tab shows the current small image; if there is none it shows "—" and points you to the ★ button.
Remove card image deletes only the small copy in the main database; the original photograph in EK1 stays. The reverse is also true: deleting a picture from EK1 does not remove the card image — the card image is a separate copy. So when you delete the original and upload a new one, remember to pick the card image again.
Limits. The downsizing happens in the browser: the longest edge is reduced to 160 pixels and a JPEG is produced, with quality stepped down if needed. The server accepts at most 96 KB and recognises only JPEG, PNG, GIF and WebP — it looks at the file's own bytes, not at the extension. A request for a card that does not exist is rejected. The write permission is the same one as for uploading images: Attach stock/account documents. No extra permission is needed to see a card image.
The card image is for recognition only: it helps you tell a product apart by eye in the list and in the card header. The photographs used on documents and PDF forms are the originals in EK1; do not blow up the 160-pixel card image and use it in print.
12. The card's type and family — which tabs, which fields?
Every stock card carries a Type, and the type puts the card into one of three families: stock (material, semi-finished, semi-finished 2, finished goods, scrap), expense (expense, service, labor) and machine (machine, equipment, spare part). The family decides two things: which list the card appears in (see List Screens, section 14) and which sections are drawn on the card screen. A meaningless field is not greyed out — it is not drawn at all.
12.1 Where the type is shown and where it is changed
In the Identity & Units box on the General tab, right under the description, there is a Type row: the type name as a coloured chip with the family name beside it in muted text. For the expense family "· no stock is kept" is appended after the family. Hovering the chip shows the full description of the type in a tooltip.
You change the type in the Edit form: the dropdown in the Identity group, between Description and QR code. All eleven types are in that one list and each option carries its family beside it (like "Spare part — Spare Parts / Equipment"); the first option is Unclassified (old card — stock is kept). That is how you move a card from one family to another — once saved, the card is listed in the other window.
12.2 Tabs and sections hidden by family
| Family | Tabs that disappear | On the General tab | In the Edit form |
|---|---|---|---|
| Stock | none — everything is shown | the full card | the full form |
| Expense | Prices · Status (· Fabric) | the Storage Location box drops; in the header strip the type name plus "no stock is kept" replaces Total on hand, and List Price is replaced by Family | the Sales Prices (FIYAT1–6), Stock (Min Level) and Storage Location groups are not drawn at all |
| Machine | Prices (· Fabric) — Status stays, because stock is kept | the withholding row drops from the Tax & Withholding box; in the header strip List Price is replaced by Family | the Sales Prices group and the Withholding Rate field are not drawn at all |
The Fabric tab was already drawn only in the textile production profile (section 1); in the expense and machine families it is not drawn even when the profile is textile. The Cost (MaliyetSTK), Groups and Identity fields stay in all three families — an expense card can have a cost and a group too.
Moving a card into the expense family does not delete movements, lots or the quantity already recorded — it only stops future purchase/sales documents from producing a stock movement for that card. The values of hidden fields are not deleted either: move the card back into the stock family and the old sales prices and storage-location data are still there and drawn again. So picking the wrong type is not an irreversible mistake.
12.3 Giving a type to "Unclassified" old cards
A card that was never given a type shows a muted Unclassified chip; hovering it brings up "An old card whose type has not been chosen yet — stock is kept; set the type from Edit". An unclassified card behaves by the stock family's rules: no tab or section is hidden, a purchase invoice increases stock, and the card is listed in the Stock window. Postponing the type therefore breaks nothing.
-
Find the unclassified cards in one go
Open the Stock window and click the Unclassified chip on the chip strip — the list narrows to the cards without a type, and the number on the chip tells you how many are left.
-
Open the card and pick the type from Edit
Click the row, press Edit, choose the right type from the Type list in the Identity group and save. When choosing, ask: does this card need its stock tracked (stock / machine) or only its expense followed (expense)?
-
The card is not lost, it only moves
If you gave it an expense or machine type, the card leaves the Stock list and shows up in the Expense or Spare Parts / Equipment window. No need to panic — the code is unchanged and you can still open the card by its code.
An expense card has no Status tab, because there is no quantity to keep. The "how much" question is answered in two places: the Movements tab document by document, and the Expense Tracking panel in the Expense window by month and by card — described in List Screens, section 14.4.
13. The Reports tab — the card's nine charts
The Reports tab at the far right of the stock card gathers the history of that single product into nine charts. The tab is not visible to everyone: the user must have the may see graphical reports or the stock/customer reports permission (an administrator always sees it) — exactly the same gate as the Reports tab on the customer card. A user without the permission never sees the tab; there is no hidden button.
On the left of the tab there is the report list under four headings, on the right the selected report. The strip on top carries the Start/End dates (left empty: start of year → today) and, depending on the report, Direction (sales / purchase), VAT (excluded / included), Warehouse and Currency boxes. An empty warehouse means the grand total; typing USD into Currency draws a second line of the price series at the exchange rate of the invoice date.
| Report | What it shows | Data source |
|---|---|---|
| Monthly Sales / Purchases | Amount and quantity month by month; the same months of last year as a second line on the same chart. | Invoice/dispatch lines |
| User Breakdown | Who sold (or bought) this item the most — pie slices plus a breakdown table. | The user on the line item |
| Price Change | The monthly weighted average of the realised sales and purchase unit price; a currency-indexed second series on request. | Line prices + the exchange-rate table |
| Stock Level | How many were on hand at the end of each month — walked backwards from today's quantity. | Stock status + movements |
| Turnover Rate | Monthly turnover (cost of issues ÷ average stock value) and days of cover (on hand ÷ average daily issue). | Movements + unit cost |
| Monthly Quotations | The quotation amount and quantity issued for this item month by month (cancelled quotations do not count). | Quotation lines |
| Quotation → Order Conversion | How much of the quotation turned into an order — amount, quantity and percentage. | The quotation–order chain |
| Monthly Production | For a card with a recipe, the quantity produced month by month and the confirmation cost; without a recipe no chart is drawn. | Production confirmations |
| Work Order Durations | The average days from opening to start and from start to the first confirmation, plus a duration-distribution bar. | Work orders |
The card's Price 1-6 values keep no history; the Price Change chart is built from the realised sales/purchase prices (if the company keeps price lists in the Prices and Campaigns window, the list price is resolved from the list version valid on the sale date and the monthly breakdown also shows list price and deviation % columns) and the card's current list price is printed beside it as a reference. If the quotation → order link is missing, the report is marked "approximate": the conversion is then estimated from the order total of the same item in the same month. The unit cost of the turnover rate is read from the weighted average of the period's purchases first; if there is no purchase in the period it falls back to the MALIYET field on the stock card — but if that value is more than 20 times the period's sales unit price it counts as unreliable and is not used; if neither exists the turnover is computed on quantity — which one was used (and any card value rejected as suspicious) is written under the chart. If the Warehouse box is empty, the grand-total row is taken; if a line's unit cannot be converted to the card unit, the series is marked "approximate".
A very wide period is trimmed. If you pick a range longer than ten years, both the chart and the totals are trimmed to the last 120 months of the range; when that happens a warning under the report states which months were drawn. Choose a narrower period to look at older months. Return documents are not in the main total. In the Monthly Sales / Purchases report the purchase-return lines that appear on the sales side (and the sales-return lines on the purchase side) are collected in a separate Return column; if the card has returns of its own, Sales return / Purchase return and Net sales / Net purchases boxes appear as well.
14. The Reports tab — four new reports
Four more reports have been added to the same tab: Last Prices, Customer Breakdown and Return Rate sit under the Trade heading on the left, while Purchase Price Variance sits under the new Procurement heading. The permission gate and the date strip are the same as in §13; the boxes specific to these reports (row count, customer code, reference price) appear in a second small strip above the report itself.
| Report | What it shows | Data source |
|---|---|---|
| Last Prices | The last sales and the last purchase lines side by side: customer, date, quantity, unit price, discount, currency/rate and the linked invoice. The answer to "what did we last quote this customer?" — typing a code into the Customer code box and pressing Enter narrows the list to that customer; the Row count box ranges from 10 to 100. | Invoice/dispatch lines + the invoice link |
| Customer Breakdown | Who buys this product: the top N customers as pie slices (the rest folded into "Others"), and in the table the amount, quantity, document count, last purchase date and gross profit / margin. Switching the Direction box to purchase turns the same table into "whom do we buy from" (no profit is computed in that direction). | Invoice/dispatch lines + unit cost |
| Return Rate | Month by month, the ratio of the return amount to sales (%), with the sales/returns lines underneath. The documents counted as returns are invoices of the sales return kind; cancelled documents do not count. With Direction set to purchase, the purchase-return kinds and the purchase denominator are used. | Invoice/dispatch lines + the invoice kind |
| Purchase Price Variance | Supplier by supplier, the difference between the realised purchase unit price and the reference price, with its percentage; each supplier's lowest/highest price and last purchase date are in the table too. The Reference box offers three options: period average (default), last purchase and list price (List no picks which price slot). The monthly bars show the variance percentage. | Purchase lines (returns excluded) + card prices |
Return lines are posted as stock receipts. That is why a sales return shows up in the purchase leg of the Monthly Sales/Purchases report; the Return Rate report separates them by document kind and never mixes them into the sales total (the ratio is against gross sales). Return documents are excluded from the Last Prices and Purchase Price Variance lists — otherwise a customer return would look like "a purchase from a supplier". Gross margin is an estimate: the unit cost is read from the weighted average of the period's purchases per card main unit first, and if there is no purchase in the period the MALIYET field on the stock card is used — if that value is more than 20 times the period's sales unit price it counts as unreliable and is not used; which one was used (and any card value rejected as suspicious) is written under the chart. If the same card is bought and sold in different units (e.g. both metres and bars), every price is converted to the card's main unit; if a line cannot be converted the report says "approximate". The list-price reference reads one of the card's Price 1-6 slots — the schema has no separate "purchase list price" field, so you choose which slot is the purchase price; if the chosen slot is empty the report quietly falls back to the period average and says so.
Free-of-charge issue. Sales lines with a price of 0 (samples, gifts, material shipped with a labour invoice) are not included in turnover, sales quantity or profit; their quantity is multiplied by the same unit cost and shown in a separate Free-of-charge issue box and section. The "Show document list" link lists the date, document, quantity and cost of these lines; clicking a document number opens the invoice. This way a single free-of-charge document does not falsely push the month's profit negative.
15. The Reports tab — five new reports (profitability, classification, planning)
Five more reports have been added to the same tab: Product Profitability sits under the Trade heading on the left, ABC / XYZ Class, Stock Ageing and Replenishment Suggestion under the Stock heading, and Order Fulfilment under the Quote / Order heading. The permission gate and the date strip are the same as in §13/§14. The Direction box appears in ABC / XYZ Class and Order Fulfilment, the VAT box in Product Profitability, and the Warehouse box in Stock Ageing and Replenishment Suggestion; Stock Ageing also has a Dead stock threshold (days) option in its own small strip (30 / 60 / 90 / 180 / 365, 180 by default).
| Report | What it shows | Data source |
|---|---|---|
| Product Profitability | Monthly turnover (excluding VAT) minus quantity sold × unit cost: gross profit and margin %. The cards at the top show turnover, cost, gross profit, margin, unit cost and the average selling price. The turnover measure is identical to the Monthly Sales/Purchases report — both give the same amount for the same month. The unit cost has three stages: first the weighted average of the period's purchases per card main unit, and if there is no purchase in the period the MALIYET field on the stock card — but if that value is more than 20 times the period's sales unit price it counts as unreliable and is not used; if neither exists, the cost and profit columns stay blank. The realised purchase price comes first because the card's MALIYET field is filled inconsistently in this database; which one was used (and any card value rejected as suspicious) is written on screen. | Invoice/dispatch lines + unit cost |
| ABC / XYZ Class | This card's place across the whole company. Every card with sales in the period is ranked by turnover; up to a cumulative share of 80% the card is A, up to 95% it is B, above that C. The screen shows the badge, the turnover rank, the turnover share, the cumulative share, a Pareto curve, an A/B/C pie and a table of the ten highest-turnover cards. XYZ is the coefficient of variation of this card's monthly quantity (standard deviation ÷ mean, months without sales counted as zero): below 0.5 is X (steady), below 1 is Y (fluctuating), above that Z (erratic). The combined badge (e.g. "AY") is used when deciding counting frequency, safety stock and price discipline. | The invoice/dispatch lines of every card |
| Stock Ageing | The age of the stock as of today: quantity and value in the 0-30 / 31-60 / 61-90 / 91-180 / 180+ day buckets, as bars and as a pie. If the card has lot records the age is computed from the receipt date in the lot ledger, so it is exact; without lots a FIFO assumption is used — today's quantity on hand is aged by consuming the most recent receipts backwards, and the report says "approximate". The last receipt and last issue dates, the days since the last issue and a dead / slow stock badge are also shown; the badge appears when the dead-stock threshold you picked in the strip is exceeded, or when the card has never had an issue. The date range you choose only sets the unit cost in the value column, not the age. | The lot ledger or the stock movements + unit cost |
| Replenishment Suggestion | The answer to "when and how much should I order". Projection = quantity on hand today + open purchase orders − open sales orders. The minimum level is read from the selected warehouse's own record first, and from the stock card if there is none there (which one was used is written out). The schema has no separate lead-time field, so the lead time is measured: the average number of days from the order date to the receipt date on order-linked purchase receipts. The reorder point = average daily consumption × lead time + minimum level. The target level is the maximum level if one is defined; otherwise it is the minimum level plus the consumption over the lead time. The suggested quantity = target − projection, rounded up to the card's order multiple; if the card defines an upper limit for a single order, the report also says how many batches are needed. The run-out date and the order date are computed from daily consumption, and the badge states the situation: below the minimum level, below the reorder point, above the maximum level, in order, or undefined. | Quantity on hand + open orders + card levels + the measured lead time |
| Order Fulfilment | The fulfilment rate is a cohort measure: a month is credited with the quantity of the orders placed in that month, and the report shows what percentage of them has been shipped. Once an order is fully invoiced its line is deleted from the order list, so "orders placed" = the quantity still open + the quantity shipped against an order (found through the invoice-to-order link; the dates of deleted orders are read from the order archive). The shipments of the calendar month are a separate column and are identical to the Monthly Sales/Purchases report. The open orders block is as of today: quantity, amount, the oldest order, the average age and the 0-15 / 16-30 / 31-60 / 60+ day buckets. Direct shipments not linked to an order are kept out of the rate, and their quantity is written on screen. | Order lines + invoice/dispatch lines + the invoice-to-order link |
The unit cost is an estimate, and four reports — Turnover Rate, Customer Breakdown, Product Profitability and Stock Ageing — use the same number: first the weighted average of the period's purchases per card main unit, and if there is no purchase in the period the MALIYET field on the stock card — if that value is more than 20 times the period's sales unit price it counts as unreliable, is not used, and the cost/profit columns are left blank. The purchase average comes first because the card's MALIYET field is filled inconsistently in this database and a single junk value could distort the profit. If the same card is bought and sold in different units (e.g. both metres and bars), every quantity is converted to the card's main unit; if a line cannot be converted the report says "approximate". Without lot records, ageing is a FIFO assumption: if the receipt movements do not cover today's quantity on hand, the remainder is placed in the oldest bucket — which usually means the opening balance was entered outside the document flow. The ABC class depends on the date range you choose; changing the range can change the class. The classification only covers cards that moved during the period, so a card that never sold does not appear in the list. The replenishment suggestion is advice; it does not raise an order. The lead time is measured from past purchases; if there is no order-linked purchase at all, 0 days is assumed and the suggestion is based on the minimum level alone. If no minimum or maximum level is defined the report cannot check for a breach, and it says so plainly. The fulfilment rate can change retroactively: an order that is open today and shipped tomorrow raises that same month's rate. Shipments against orders placed outside the date range are not written into the monthly rows; their quantity is stated in the note.
16. The Reports tab — planning reports (availability, demand forecast, basket analysis)
Three more reports have been added to the same tab. A new Planning heading has appeared in the menu on the left: Availability Projection and Demand Forecast live there, while Frequently Bought Together sits under the Trade heading. The permission gate and the date strip are the same as in §13/§14/§15. The Warehouse box appears in Availability Projection and Demand Forecast. Each report has its own small strip: Projection horizon (weeks) (4 / 8 / 13 / 18 / 26, 13 by default), Forecast horizon (months) (3 / 4 / 5 / 6, 3 by default) and List length (5 / 10 / 15 / 20 / 30, 10 by default).
| Report | What it shows | Data source |
|---|---|---|
| Availability Projection | Where the stock is heading over the coming weeks. The curve starts from today's quantity on hand; each week open purchase orders and open production are added, while open sales orders and open production consumption are subtracted. The expected date decides which week a movement falls into: the delivery date of the order, or the order date if that is empty (on the purchase side the measured lead time is added), and for production the planned start plus the planned duration. The first week the projection goes negative is printed in red and shown with its date on the badge at the top; weeks below the minimum level are amber. Open movements whose expected date has already passed are not ignored — they are pulled into the first week and listed in a separate "overdue" table. | Quantity on hand + open order lines + open work orders and their frozen recipes |
| Demand Forecast | A three-to-six-month demand forecast from the monthly sales history. The method is exponential smoothing: the level, the trend and — when there is enough data — a seasonal term are updated every month. If the range you choose holds fewer than 24 months, no seasonal pattern can be computed and only the trend is used; with fewer than 12 months the report marks the result as "approximate". The line chart shows the actual sales, the model's fit to the past and the forecast together; the lower and upper bounds around the forecast are ±1 standard deviation (σ is measured from past forecast errors). The run-out date is when the quantity left — today's stock plus open purchase orders minus open sales orders — will be consumed by the forecast demand. The seasonal-pattern bars show each month's deviation from the yearly average. | Monthly sales quantity + quantity on hand + open order lines |
| Frequently Bought Together | Which other cards appear on the sales documents that contain this card. The list is ordered by the number of documents they share, and each row carries two measures: support % is the percentage of this card's documents that also contain the other card; lift says how much stronger the pairing is than chance — 1 means unrelated, above 1 is a tendency to be sold together, below 1 a tendency to replace one another. The bars show the number of shared documents, the pie the amount sold together. The basket is keyed by transaction type + document number: the same number is a different document on an invoice and on a dispatch note, so foreign lines cannot leak into the basket. Return documents and cancelled headers are not counted. | This card's sales documents + all the lines on them + the company-wide document counts |
Availability is not a forecast, it is a count: it only adds up the open orders and open work orders that exist in the system today. It cannot see orders that have not been entered yet or production that has not been planned — if you also want to allow for the orders you are going to receive, that is what the Demand Forecast report is for. The two give the same number by two different routes and may disagree: availability speaks from the commitments in hand, the forecast from past sales. The order table only holds the outstanding quantity — once an order is fully invoiced its line is deleted, so nothing is counted twice in the projection. The report uses the same quantity on hand, the same set of open orders and the same measured lead time as the Replenishment Suggestion; the two screens print the same number.
A forecast is a continuation of the past, not a guarantee of the future. The model looks only at this card's own sales history; a campaign, a new customer, a price change or a one-off large order are things it cannot see. Months with no sales in the range count as zero demand — if the card did not sell because it was out of stock for a while, the forecast will come out too low. So watch the ±1σ band: a wide band means the model is not confident about that card. Lift, in turn, can mislead on small numbers; a card that appears together on two documents can show a high lift, but that is not a pattern. If the support percentage is low (say below 5%), do not take that row seriously.