The volume shown in a ship-to's forecast is automatically pulled from that ship-to's consumption (depletion) forecast — it is not entered or edited directly on the ship-to screen itself.
Removing a SKU or Region From a Ship-To
If a ship-to is pulling in volume that shouldn't be there (for example, a planning group configured to route through the wrong distributor, surfacing units for a region you don't actually sell into), don't edit the ship-to directly — go to the consumption forecast for that customer instead and delete the row for the affected product/region.
Navigate to the consumption forecast for the relevant customer
Locate the row for the product/region you want removed
Delete the row
This will zero out the forecast columns going forward in the ship-to. Any historical actuals will remain visible in that row (since real sales occurred), but the forward-looking forecast will reflect the removal.
Exception: Customers With "Direct Order Forecasting" Enabled
The automatic consumption-to-ship-to flow described above applies to most customers, but not all. In Forecast Settings, a customer can instead be flagged as "Direct order forecasting." For these customers, the ship-to forecast is entered directly as a total shipment value and does NOT pull from the consumption forecast at all. If two similar customers behave differently, check whether "Direct order forecasting" is enabled for one of them in Forecast Settings.
Switching a Customer From Direct Order to Consumption Forecasting
If you move a customer from Direct Order Forecasting to consumption-based forecasting in Forecast Settings, the Ship-to forecast may not immediately reflect the change. Previous direct order forecast values can remain "sticky" and continue to appear even after the setting is disabled, because the prior direct order forecast is still referenced by the system.
If this happens — the Ship-to still shows as a direct order rather than pulling from consumption — contact support@confidotech.com. The Confido team will soft-delete the residual direct order forecast, after which the consumption forecast will flow through correctly to the Ship-to view.
Master data changes like switching a customer's forecast method are sensitive. Before making this type of change, export any forecast data you need to retain — reversing it may require engineering assistance.
Can I Manually Override the Ship-To Forecast?
Not within the Sales Forecast module. For consumption-based Planning Groups, the Ship-to tab is read-only. If you need to manually adjust a shipment number, that capability exists in the Demand Planning Module, not Sales Forecast (see "7. Adjustments, Overrides, and Collaboration").
Why a Ship-To Might Show No Volume At All
If a ship-to isn't showing any volume, check these two prerequisites before assuming something is broken:
Actualized data must exist. The Ship-to view is built from ERP shipment actuals. If no invoices have synced yet for this customer (check the "ERP Invoice Coverage" screen), there is nothing for the forecast to pull from.
The customer must be assigned as the RTM on a Planning Group. Ship-to volume is only derived for customers that are set up as the RTM (distributor) on at least one Planning Group. A new "solo" ship-to customer with no Planning Group relationship will not show any volume, even once invoices start flowing.
Why Don’t Actuals Appear at the SKU Level?
For retailers that do not provide base and incremental units, such as Whole Foods, you must select the "derive incremental units" option during data upload. Without this setting, imported actuals may display as zeros at the SKU level. For syndicated sources that include base and incremental units, leave "derive incremental units" unselected to use the provided breakdown.
Why Do Negative Adjustments Appear?
Ship-to forecasts are tied to shipment actuals. To reconcile with these actuals, underlying demand drivers (e.g., consumption) may require adjustments. Negative adjustments can appear when actuals, including credits or returns, are lower than previously forecasted.