How to Enter a Demand Forecast in EDGEBIC

Entering a demand forecast in EDGEBIC means adding a row that records anticipated, not-yet-ordered demand for a product in a specific bucket. In EDGEBIC by User Solutions you open the inventory calendar for the product, switch to the forecast tab, set a date, quantity, and type, and click Add. The product's forecast demand rises, and that forecast flows into the projection alongside any firm demand from sales orders. This guide covers the entry itself, including weekly and monthly granularities.

For the broader forecasting workflow, including making system suggestions fire, read how to enter forecasts and firm suggestions. For the concepts behind forecast, firm, and netting, see forecasting and replenishment explained. This is documented behavior of EDGEBIC; the full task set is in the how-to hub.

Before You Start

• You need the product to exist and to be visible in the inventory calendar.
• Decide the granularity you want: daily, weekly, or monthly (period).
• Know which forecast type applies: sales, production, or consumption.

Step 1: Open the Inventory Calendar for the Product

Navigate to the inventory calendar and select the product from the product dropdown. The calendar loads its time-phased view. This is the same screen that shows projected balance and available-to-promise; the forecast is one input to it.

Step 2: Choose the Bucket Granularity

Set the Bucket dropdown to the granularity you want before entering the row:

• Day for a fast mover with daily order flow.
• Week for most items.
• Period (a calendar month) for slow, high-value items.

The granularity you pick is stored on the row, so choose it before adding rather than after.

Step 3: Switch to the Forecast Tab

Select the Forecast tab. At the bottom sits the entry form with three fields.

Step 4: Enter Date, Quantity, and Type

Fill the form:

1. Date. The first day of the target bucket. For a daily forecast, the day itself. For a weekly forecast, the Monday of the week. For a monthly forecast, the first of the month.
2. Qty. The units expected in that bucket, greater than zero.
3. Type. One of sales, production, or consumption, describing the nature of the anticipated demand.

The three types are not interchangeable labels. Sales forecast is anticipated customer demand, production forecast is planned output, and consumption forecast is expected component usage. Multiple types can coexist for the same date, and they accumulate, so you can layer them where the item genuinely has more than one demand stream.

Step 5: Click Add

Click Add. The row is written. If a row already exists for the same product, bucket granularity, type, and date, EDGEBIC updates it in place rather than creating a duplicate. That four-part key (product, bucket, type, date) is what makes revising a forecast clean: re-enter the same combination with a new quantity and the existing row is overwritten, so you never accumulate stale duplicates from adjustments.

Entering Weekly and Monthly Forecasts

The same form handles coarser granularities; only the date convention changes.

A weekly row dated to a Monday lands in that week's bucket when the calendar runs in week mode, and a monthly (period) row spans the calendar month from the first to the last day. If you set a period row's date to mid-month, it still falls into that month's bucket, but the displayed start may differ from the date you typed, because the bucket snaps to the month boundary.

What Changes When You Save

A new forecast row appears, and the calendar refreshes with the bucket's forecast column increased by the quantity you entered. That forecast becomes an input to the projection: it contributes to the demand column, though rarely by its full face value, because the product's forecast consumption rule nets it against any firm demand to prevent double-counting. For how that netting reads on the grid, see how to see net requirements for a product.

Your forecast row itself is never rewritten by that netting. It stays as entered, a stored expectation, until you edit or delete it.

How to Check It Worked

Look at the forecast tab: the row should be listed with the date, quantity, and type you entered. Then look at the forecast column on the calendar for the matching bucket; it should have risen by your quantity. If the demand column did not rise by the same amount, that is expected: demand nets forecast against firm under the consumption rule, so read the forecast and firm columns separately to confirm each stream.

Common Mistakes

• Changing the bucket dropdown and expecting existing rows to re-bucket. The dropdown changes the display only. A weekly row stays weekly even when you view the grid in day mode. Pick the granularity before adding the row.
• Changing the type on an existing row and expecting an update. The row is keyed partly on type. Enter the same date with a different type and you create a new row rather than updating the old one.
• Reading the demand column as forecast plus firm. Demand nets the two under the consumption rule, so it is usually less than the raw sum. Check the two columns separately.
• Assuming netting rewrites your forecast. It does not. Forecast rows are immutable to the engine and change only when you edit them.

Loading Forecasts in Bulk

Entering rows one at a time suits a handful of changes. When you are loading a whole planning cycle, a forecast import from a spreadsheet is faster: a file with columns for the product, bucket date, bucket granularity, forecast type, quantity, and notes runs the same underlying add-or-update logic per row. The import respects the same four-part key, so a spreadsheet row whose type differs from what is already stored for that date creates a new row rather than updating the old one. That is the single most common surprise with bulk loads, so keep the type column consistent with what is already in the system when you intend an update.

What Comes Next

Once forecasts are in, you may want to freeze the near-term window so late changes do not disturb committed work: read how to set a time fence. To decide how firm orders net against those forecast quantities, Greater Of or Minus Consumed, see how to set the forecast consumption rule. To see where forecast turns into a build decision, browse the how-to hub.