When you run an allocation strategy, Toolio forecasts Gross Sales Units (GSU) for every variant, location, and week. Sometimes you know something the model doesn't: a launch that will run hot, a promotion, a slow seller you want to pull back. You can now edit the forecast directly in the Allocation Details grid, and your edit drives everything downstream: the allocation itself, receipts, and the derived cost and retail metrics.

Toolio keeps your number and the system's number side by side. The override you type lives in the editable Gross Sales Units row; the engine's original value is preserved in a read-only System Gross Sales Units row, so you can always compare adjusted against system.

The forecast is a strong starting point, but you sometimes know something it can't. Override GSU when you need to:

Every allocation run produces two Gross Sales Units metrics, shown as separate rows in Allocation Details:

System Gross Sales Units is your reference point. It updates every time you run the strategy, so it always reflects the latest system forecast, while your override stays in the Gross Sales Units row until you change or remove it. Comparing the two tells you exactly where, and by how much, you've adjusted the plan.

It is also distinct from Original Forecast Units: System Gross Sales Units is the post-retrend, post-promotion system value, whereas Original Forecast Units is the pre-retrend forecast.

You edit in the Allocation Details tab, one week at a time, at whatever grouping level you're viewing.

Only future weeks (from the current retail week forward) are editable. Past and actualized weeks are read-only, though any override you made earlier still shows in those weeks.

When you edit a cell above the base level, Toolio spreads the new value down to the underlying variant × location rows for that week, in proportion to each row's current Gross Sales Units. Rows that already carry a heavier forecast absorb more of the change.

For example, starting from a week that totals 100 units (Location 1 = 40, Location 2 = 60), typing 130 into the total cell scales every row up by 1.3:

If the cell you edit currently totals zero (for example, a brand-new item with no forecast), the value is spread evenly across the rows beneath it instead.

Overrides apply one week at a time. The across-time Total column in the left panel is not editable; edit each week's cell directly.

Saving an edit updates Gross Sales Units and the derived gross cost and retail for those cells, and nothing else. Your allocation results, receipts, and other downstream metrics stay as they were until you re-run the strategy. After you save, the strategy is flagged as having pending changes so it's clear a run is needed.

To flow your overrides into the allocation, run the strategy with Run Allocation Strategy. The run re-applies every override on top of the fresh system forecast, so your adjusted value is what allocation and receipts use.

A small caret in the corner of a cell marks any cell with an override beneath it. Carets appear on both the Gross Sales Units and System Gross Sales Units rows, at every grouping level, so a group total shows a caret whenever any variant or location under it has been overridden. Because the marker is driven by the stored overrides rather than by your current edit session, it persists across view changes and sessions.

Hover over a marked cell to see both numbers: System GSU (the original system value) and GSU (override) (your value).

To clear an override, right-click the cell and choose Remove Overrides. Gross Sales Units snaps back to System Gross Sales Units immediately, the derived cost and retail recalculate, and the override is cleared for every row beneath the cell. Run the strategy afterward so allocation and receipts pick up the restored system value.

The Gross Sales Units and System Gross Sales Units values and their carets also appear on the Allocation Plan page, but editing is available only in Allocation Details. Use Allocation Plan to review overrides across strategies; make changes in Allocation Details.

Yes, that's the point. Your override is stored separately from the forecast and re-applied on every run. System Gross Sales Units refreshes to the latest engine value, while your override in the Gross Sales Units row stays in place until you change or remove it.

Saving updates Gross Sales Units and its gross cost and retail only. Run the strategy with Run Allocation Strategy to flow the override into allocation and receipts.

No. Only future weeks, from the current retail week forward, are editable. Overrides you made on weeks that have since passed stay visible until those weeks age out of the data.

New locations or variants join the group without an override, so the aggregate drifts away from the number you set. Re-enter the override on the cell to recapture the new members.

Past overrides remain visible for as long as Allocation retains those weeks (roughly 8 to 10 weeks), then drop off with the underlying data.

Not today. Only Gross Sales Units can be overridden; cost and retail are derived automatically from your edit and the item's pricing.