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.
The planning model
Every planning page reads from the same underlying data:
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 — 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.
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:1
Click Run now
The button switches to Running with a spinner while the solve is in flight, and stays disabled until the job finishes.
2
Wait for completion
When the job completes, the grid picks up the fresh plan automatically and the freshness strip resets.
3
Review solve timings (optional)
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.
Running the supply solver is separate from generating demand forecasts. Forecast generation has its own admin surface — see Forecast 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:
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. 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, Production, and Purchases are the focus pages, each with Schedule, Worksheet, and List views.
- MRP covers material requirements for committed production.
- The Execution plan is the roll-up of everything you’ve committed.
- Data issues surfaces structural problems the solver’s data audit found.
Best practices
Check the freshness strip before acting
Check the freshness strip before acting
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.
Use the lenses as questions, not settings
Use the lenses as questions, not settings
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.
Prefer scheduled solves over automatic re-planning
Prefer scheduled solves over automatic re-planning
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.
Troubleshooting
Next Steps
Recommendations
Accept, modify, reject, and dismiss solver recommendations
Purchases
Plan supplier buys with the Schedule, Worksheet, and List views
Coverage
Understand days-of-supply, thresholds, and coverage impact
Demand Forecasting
The demand side that feeds the supply plan