> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tetherdata.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Supply Planning Overview
> How Tether generates, refreshes, and frames your supply plan
# Supply Planning Overview
Supply Planning is where Tether turns your demand forecast, inventory position, network, and policies into a concrete plan of purchases, production runs, and transfers. The plan is produced by Tether's planning service, which solves your whole network at once — every recommendation you see on the planning pages comes from the same solved plan.
If you used older versions of Tether (or older docs), you may remember a **Supply Plan** page under Inventory and a manual refresh action on the dashboard. Those have been replaced by the Supply Planning section described here: plans are now generated by the planning service and refreshed with **Run now** or on a schedule.
The planning pages appear in the sidebar only for organizations with supply planning enabled. They live under the **Supply Chain** group: Connected Planning, Transfer, Production, Purchase, MRP, Execution plan, and Data issues. Navigation labels (like Locations or Policies) can be renamed per organization in [Settings → Terminology](/administration/terminology).
## The planning model
Every planning page reads from the same underlying data:
| Layer | What it is |
| --------------- | ------------------------------------------------------------------------------------------------------- |
| **In progress** | Real, already-happening supply — open Purchase Orders, in-flight transfers, in-progress production runs |
| **Committed** | Movements you have accepted into the execution plan — the plan the solver must respect |
| **Recommended** | The solver's uncommitted suggestions from the latest solve |
The solver re-optimizes recommendations only when it runs. Committed edits you make between solves show on the grids immediately, but the solver's own suggestions stay as of the last solve until the next run.
## Plan freshness
Every planning page shows a freshness strip in its header:
```
Plan as of 2 hours ago · 3 edits since · next solve in 5 hours
```
* **Plan as of** — when the current plan was solved. Hover for the exact timestamp.
* **N edits since** — committed edits made after the solve. These are reflected on the grid now, but the solver's recommendations don't account for them until the next solve. The count is highlighted as a warning cue when non-zero.
* **next solve** — when the next scheduled solve will run, if one is configured.
The indicator only appears once a plan has been solved.
## Running the solver
### Run now
On the **Connected Planning** page, the **Run now** button (with a play icon) triggers a solve against the current network state:
The button switches to **Running** with a spinner while the solve is in flight, and stays disabled until the job finishes.
When the job completes, the grid picks up the fresh plan automatically and the freshness strip resets.
After a run, a clock icon appears next to the button. Click it to open the **Last solve timing** popover — a per-phase breakdown (Snapshot capture, Solve, Plan assembly, Plan persist, and a Total), with the solve phase further broken down into its sub-phases where available.
### Scheduled and automatic re-planning
Solves can also run without anyone clicking a button:
* **Scheduled solves** run on your organization's schedule; the next one is shown in the freshness strip.
* **Automatic re-planning** is configured at **Settings → Automatic Re-planning**. When the toggle is on, every policy, network, or catalog change from upstream triggers a new solve. When off (the default), the planner only runs on manual or scheduled triggers.
With automatic re-planning on, frequent upstream edits can queue many long-running solves. Turn it off if re-plans are getting in the way. Managing this setting requires the feature-flag management permission.
Running the supply solver is separate from generating demand forecasts. Forecast generation has its own admin surface — see [Forecast Admin](/demand-forecasting/admin).
## The scenario strip
The first line of most planning pages is the scenario strip — it names which "world" the numbers below come from and lets you change it:
| Lens | Dataset | Question it answers |
| ------------------- | -------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| **Do nothing** | In progress | If I take no new action, where do I land? Only real, already-happening supply counts. |
| **Follow my plan** | Committed | If I do exactly what I've committed to, where do I land? In progress plus your accepted commitments. |
| **Tether's plan** | With recs | What does the solver want me to do? Committed plus the solver's uncommitted recommendations. This is the default on Connected Planning. |
| **No input limits** | Counterfactual | What could each production stage do if it were never constrained by its inputs — bounded only by its own capacity and demand? |
The first three lenses are cumulative — each adds a layer on top of the previous one. Supply a lens excludes isn't hidden; it renders ghosted so you can see what each lens sets aside.
### The No input limits counterfactual
**No input limits** is different: it is a separate solved world served from its own paired relaxation solve, not a layer on top of Tether's plan. When it's active, the strip shows a stamp like "Counterfactual solved 3 hours ago · committed supply current" — the counterfactual comes from its own solve, but committed supply and the position it projects are current.
The position is always offered, and disabled with a stated reason when it can't be selected:
* Not enabled for this organization.
* Needs a solved plan first — no plan run to compare against yet.
* The last plan run produced no no-input-limits comparison.
* The comparison could not be read (try again shortly).
The scenario strip appears only on pages whose numbers actually re-project across scenarios (Connected Planning, Transfers, Purchases). Production carries its own two-axis lens — see [Production](/supply-planning/production). MRP, the Execution plan, and Data issues don't re-project, so they carry no strip.
## Where to go from here
* **Connected Planning** is the cockpit — the whole network in one grid, with **Run now**.
* [Transfers](/supply-planning/transfers), [Production](/supply-planning/production), and [Purchases](/supply-planning/purchases) are the focus pages, each with Schedule, Worksheet, and List views.
* [MRP](/supply-planning/mrp) covers material requirements for committed production.
* The [Execution plan](/supply-planning/execution-plan) is the roll-up of everything you've committed.
* [Data issues](/supply-planning/data-issues) surfaces structural problems the solver's data audit found.
## Best practices
Before accepting recommendations, glance at "Plan as of" and the edit count. A plan with many edits since the last solve means the solver hasn't yet re-optimized around your recent changes — run a solve first if the edits are significant.
Each lens answers a different question. Start on **Tether's plan** to see the full proposal, flip to **Follow my plan** to see where your commitments alone land you, and use **Do nothing** to see the urgency of acting at all.
Automatic re-planning is powerful during heavy configuration work, but each upstream change queues a full solve. For day-to-day operation, scheduled solves plus the occasional **Run now** keep the plan fresh without surprise queue backlogs.
If the counterfactual produces meaningfully more than Tether's plan for a SKU, some input (a raw material, an upstream stage) is the binding constraint. Cross-check with [MRP](/supply-planning/mrp) and [Data issues](/supply-planning/data-issues) to find it.
## Troubleshooting
| Issue | Cause | Solution |
| -------------------------------------------- | ------------------------------------------------------ | ------------------------------------------------------------------------------------------------- |
| No planning pages in the sidebar | Supply planning isn't enabled for your organization | Contact your Tether administrator |
| Freshness strip missing | No plan has been solved yet | Run a solve from Connected Planning with **Run now** |
| Recommendations look stale after edits | The solver only re-optimizes when it runs | Check "N edits since" in the freshness strip; run a solve to refresh recommendations |
| **No input limits** is disabled | The strip states the specific reason below the control | Follow the stated reason: enable the feature, run a solve, or retry shortly |
| **Run now** stays on Running for a long time | Large networks take time to solve | Wait for completion; afterwards, check the clock-icon timing popover to see which phase dominated |
## Next Steps
Accept, modify, reject, and dismiss solver recommendations
Plan supplier buys with the Schedule, Worksheet, and List views
Understand days-of-supply, thresholds, and coverage impact
The demand side that feeds the supply plan