Forecast Administration
The Forecast Admin section provides tools for configuring how forecasts are generated, managing bulk data, and controlling forecast versions. These settings significantly impact forecast quality.Forecast Administration is restricted to Admin users.
Accessing Forecast Admin
Navigate to Demand Forecast → Admin (or through the settings menu).Admin Tabs
The Forecast Admin page has multiple tabs:| Tab | Purpose |
|---|---|
| Settings | Model selection and configuration |
| Upload | Bulk forecast data imports |
| Versioning | Manage forecast versions |
Model Selection
Available Models
Tether may offer multiple forecast models:| Model | Description | Best For |
|---|---|---|
| Moving Average | Average of recent periods | Stable demand |
| Exponential Smoothing | Weighted recent data | Trending products |
| Seasonal Decomposition | Captures seasonality | Seasonal products |
| Machine Learning | AI-based predictions | Complex patterns |
| Consensus | Combination of models | General use |
Selecting a Model
Model Parameters
Some models have configurable parameters: Moving Average:- Number of periods to average
- Weighting (equal or weighted)
- Smoothing factor (alpha)
- Trend factor (beta)
- Seasonal factor (gamma)
- Feature selection
- Training period
- Update frequency
Forecast Settings
General Settings
| Setting | Description |
|---|---|
| Forecast Horizon | How far ahead to forecast |
| Update Frequency | How often forecasts regenerate |
| Granularity | Daily, weekly, or monthly |
| Default Channel | Channel for new SKUs |
Threshold Settings
Configure alerts and indicators:| Setting | Description |
|---|---|
| Accuracy Threshold | Alert if accuracy drops below |
| Change Threshold | Highlight changes above X% |
| Confidence Interval | Display range (e.g., 95%) |
Bulk Upload
Upload Tab
The Upload tab allows importing forecast data in bulk.Upload Process
Prepare Data
Fill in the template with forecast values:
- SKU code (required)
- Channel (required)
- Period (required)
- Forecast quantity (required)
Preview
Review the preview of changes:
- New forecasts to be added
- Existing forecasts to be updated
- Errors to resolve
Template Format
| Column | Required | Description |
|---|---|---|
sku_code | Yes | SKU identifier |
channel_id or channel_name | Yes | Sales channel |
period_date | Yes | Date in YYYY-MM-DD or YYYY-MM |
quantity | Yes | Forecast quantity |
notes | No | Optional notes |
Upload Validation
The system validates:- SKU codes exist
- Channels exist
- Dates are in valid range
- Quantities are numeric and positive
Upload History
View past uploads:- Upload date and time
- User who uploaded
- File name
- Record count
- Status (success, partial, failed)
Versioning
What is Forecast Versioning?
Versioning maintains historical snapshots of forecasts:| Version Type | Description |
|---|---|
| Current | Active forecast being used |
| Historical | Past versions for comparison |
| Draft | Work-in-progress (not active) |
Versioning Tab
The Versioning tab shows:- List of forecast versions
- Version dates and descriptions
- Actions (view, restore, compare)
Creating a Version
Comparing Versions
Compare forecast versions:- Select two versions
- Click Compare
- View differences by SKU/channel/period
Restoring a Version
To revert to a previous version:Forecast Regeneration
When Forecasts Regenerate
Forecasts typically regenerate:- On a scheduled basis (daily, weekly)
- When model settings change
- When historical data is updated
- On manual trigger
Manual Regeneration
To trigger a forecast update:Regeneration may take time for large datasets. User edits are typically preserved unless specifically overwritten.
Data Quality
Monitoring Data Quality
Good forecasts require good data:| Quality Issue | Impact | Solution |
|---|---|---|
| Missing history | Inaccurate baseline | Import historical data |
| Outliers | Distorted patterns | Clean or flag anomalies |
| Gaps | Incomplete patterns | Fill or interpolate |
| Late data | Delayed updates | Improve sync timing |
Data Quality Indicators
Watch for warnings about:- SKUs with no history
- Channels with sparse data
- Products with high variability
- Recent data gaps
Best Practices
Model Selection
Model Selection
Choose models carefully:
- Start with simpler models
- Compare performance before switching
- Consider product segments
- Document selection rationale
Regular Updates
Regular Updates
Keep forecasts current:
- Ensure regular regeneration
- Monitor data freshness
- Review model performance
Version Discipline
Version Discipline
Use versioning effectively:
- Create versions before major changes
- Name versions descriptively
- Compare versions during planning
Upload Carefully
Upload Carefully
Handle bulk uploads with care:
- Validate data before upload
- Preview changes
- Keep backup of current state
- Document upload purpose
Troubleshooting
Forecasts Not Updating
Possible causes:- Regeneration not scheduled
- Processing error
- Data sync issues
- Check regeneration schedule
- Trigger manual regeneration
- Review system logs
- Verify data sources
Upload Errors
Common issues:- Wrong file format
- Invalid SKU codes
- Date format problems
- Use the provided template
- Verify SKU codes exist in system
- Use standard date formats
- Check for special characters