Skip to main content
PrintStudio
Inventory
Inventory
Connecting…
Customer Shop

Inventory

Material lots, reservation holds, and hold recovery

Inventory Watch

Low-stock and currently allocated material lots across SpoolStock Pro and InvenTree-backed supplies.

Material Ops

Stage visible materials for stock adjustments or reorder requests without changing the current live inventory feed.

0 selected
Batch Reservation Control

Stage visible material lots for coordinated reserve or release passes without displacing the stock-adjustment or reorder request surfaces.

Available or actively reserved lots with staged demand 0 selected

Reserve should stay focused on available lots that can cover queued or release-ready demand, while release should target staged holds that are no longer needed, were superseded by replenishment, or should be handed back before reorder pressure grows.

  • Reserve now → available lots
  • Top off release-ready demand → staged kits
  • Release stale holds → reserved lots
  • Supplier action stays on reorder requests

No low-stock or actively reserved materials right now.

Material availability with reserved stock and reorder thresholds
Material Code Available Reserved Reorder Point Status

Active Reservation Queue

Operator queue for active reservations that may need stale-hold recovery, lot reassignment, or replenishment follow-up.

Recovery queue
Hold Aging Insights

Prioritize stale holds and rebalance opportunities

Keep aging signals, queue filters, and operator guidance next to the active reservation queue so later dashboard wiring can focus recovery and reassignment on the right holds first.

Queue insight baseline
Past recovery target 0 holds Reservations aging beyond the preferred recovery window.
Rebalance candidates 0 lots Holds that look superseded by replenishment or a better compatible lot.
Watch next shift 0 reservations Holds nearing the next operator review window before they become stale.
Historical hold trends
Keep fixed-window hold movement next to today's aging snapshot

Stable summary, status, delta, and direction slots let future trend wiring compare stale holds, rebalance pressure, and recoveries without moving the current operator shell.

Windowed trend hooks
Stale hold trend Awaiting fixed-window hold history Trend status will explain whether stale-hold pressure is easing or compounding. Previous-window movement will appear here once trend history loads. Direction will show rising, flat, or recovering stale-hold volume.
Rebalance trend Compatible lot movement pending Trend status will explain whether reassignment pressure is stabilizing or accelerating. Compatible-lot wins versus the prior window will appear here. Direction will show whether rebalance candidates are expanding or clearing.
Recovery trend Recovery pace will appear once hold history is loaded Trend status will summarize whether recent recovery work is keeping pace with new holds. Release and reassignment throughput versus the prior window will appear here. Direction will show whether recoveries are trending ahead, flat, or behind incoming holds.
Operator guidance Review the oldest compatible holds first, then rebalance anything overtaken by replenishment.
  • Escalate stale holds Keep reservations older than the target window at the top of the queue for release or reassignment review.
  • Rebalance to healthier lots Shift demand to compatible lots when a newer replenishment or better balance can absorb the same reservation.
  • Protect release-ready demand Keep handoff-ready holds visible so operators do not recover inventory needed for the next release window.

Active reservations flagged for recovery or lot reassignment will appear here when the dashboard wiring lands.

Active reservations flagged for hold recovery or compatible lot reassignment
Reservation Material Current Lot Reserved Held Since Status
Hold Recovery + Lot Reassignment

Recover Active Reservations

Select active reservations, choose a compatible target lot when reassignment is possible, or release stale holds without displacing the current inventory watch, stock adjustment, reorder, or reservation control surfaces.

Active holds with stale age, replenishment supersession, or compatible lot candidates 0 selected

Reassignment should stay focused on active reservations with compatible lots that can absorb the hold without breaking lot, expiry, or replenishment rules. Release should stay available for stale holds, superseded staging, or reservations replaced by a newly received lot.

  • Reassign → compatible active lots
  • Recover stale holds → active reservations
  • Replenishment wins → newest valid lot
  • Quantity corrections stay on stock adjustment
Compatible Target Lots

Keep the final target-lot choice close to the recovery draft so later dashboard wiring can reuse the same operator flow.

Target preview
Selected target lot No target lot selected
Recovery effect Awaiting active reservation selection
  • Compatible lots will populate here Stable hook

    Use this slot for material-code, expiry, available-balance, and replenishment compatibility signals.

Hold lineage + recommendation

Compare the current hold path against the target-lot plan

Keep stable detail slots ready for richer lineage, reason bullets, and replenishment rationale without changing the active recovery queue or target preview list.

Reasoning scaffold
Current lot Awaiting reservation selection

Reserve this area for the held lot, hold age, and reservation pressure that currently owns the inventory.

Held balance
Hold age
Demand load
Target lot No target lineage loaded

Use this area for compatible lot context, replenishment timing, and why the proposed target outranks the current hold.

Available balance
Replenishment window
Compatible demand
Trend window Historical lineage window pending

Use this slot for the selected reservation's historical hold direction, recovery cadence, and fixed-window summary once typed trend data lands.

Status
Delta
Direction
Reason bullets
  • Compatible target reasons, stale-hold flags, and release blockers can render here.
Lineage detail
  • Lot ancestry, replenishment receipts, and supersession notes can render here.
Recommendation

Replenishment rationale and operator-ready recommendation copy can render here once richer inventory reservation insights land.

The shell stays neutral until a reservation selection and target recommendation populate the lineage detail slots.

Fixed windows
Keep compact hold-history rows ready for typed window comparisons

Keep hold movement, recommendation drift, and recovery outcomes in one compact history list without reworking the lineage detail layout.

Select a reservation to compare recent hold movement, link fixed windows into rescue history, and cross-highlight matching queue pressure without leaving the current review.
  • Last 24 hours Awaiting reservation context

    Selected-reservation hold movement, recoveries, and operator touchpoints will appear here for the last 24 hours.

    Trend status will populate after a reservation is selected. Window-over-window change will populate here.
  • Last 7 days Awaiting weekly context

    Weekly hold-aging swings, recommendation changes, and recovery cadence will appear here once a reservation is in focus.

    Weekly trend status will populate after a reservation is selected. Seven-day comparison deltas will populate here.
  • Last 30 days Awaiting long-range context

    Longer-running hold pressure, recovery throughput, and lot-lineage drift will appear here once a reservation is in focus.

    Thirty-day trend status will populate after a reservation is selected. Thirty-day comparison deltas will populate here.
Selected shift detail
Keep the selected fixed window ready for shift-level operator review

Preserve stable slots for shift detail, top materials, top lots, and action mix without changing the compact hold-history list.

Selected-window detail will populate after a fixed history row is chosen.
Shift summary No fixed window selected
Awaiting operator focus

Use this summary for selected-window hold pressure, shift direction, and operator-ready status copy once richer detail payloads land.

Shift status
Shift delta
Action focus
Queue focus shell No trend focus applied
Standby

Keep shift, material, and lot focus hooks stable here so future trend-driven queue filtering can apply or clear focus without reshaping this detail shell.

Shift focus Selected window Ready to apply from the chosen history row
Material focus Material drilldown pending Await a material-level trend token before enabling focus
Lot focus Lot drilldown pending Hold this slot for lot-lineage focus state and clear affordances
Predictive replenishment
Keep fill-the-focus review hooks anchored to the current material and lot focus
Standby

Hold stable review slots here so typed predictive replenishment recommendations can attach to the current focused material or lot without reworking the shift-detail layout.

Recommendation summary No predictive replenishment recommendation staged Focus the queue on a material or lot to review the next replenishment recommendation and its operator-ready status copy.
Dry-run impact Dry-run impact pending Reserve this slot for predicted hold relief, replenishment coverage, ETA, and queue impact before operators commit the fill draft.
Recommendation rows

Keep the ranked fill options and dry-run deltas close to the active focus tokens so later wiring can compare supplier, lot, or handoff recommendations in one card.

0 recommendations

Predictive replenishment rows will populate here when the focused material or lot can be dry-run against current hold pressure.

  • Recommendation rows stay anchored here Stable hook

    Use each row for suggested fill source, projected quantity, ETA, confidence, and dry-run balance deltas once typed recommendation data lands.

No fill recommendation selected Apply stays disabled until the focused material or lot produces a predictive replenishment draft.
Multi-lot rebalance
Keep spread-the-load review hooks aligned with the current lot or material focus
Standby

Hold stable slots here for compatible lot rankings, per-lot relief deltas, and operator-ready execution guidance once the current focus can spread hold pressure across multiple lots.

Ranking summary No compatible lots ranked yet Focus a lot or material to compare compatible lots by projected relief, remaining cover, and operator fit.
Aggregate impact Dry-run rebalance pending Reserve this slot for total hold relief, residual hold risk, and operator handoff notes before the spread draft is committed.
Compatible lot ranking

Keep ranked lot rows close to fill-the-focus so later wiring can compare where current hold pressure should move and what each compatible lot changes before operators stage the rebalance.

0 compatible lots

Spread-the-load rows will populate here when the focused lot or material has compatible inventory that can absorb part of the active hold pressure.

  1. Rank 1 Compatible lot ranking stays anchored here

    Use each ranked row for lot label, compatibility reason, projected rebalance quantity, and guardrail copy once typed spread guidance lands.

    Stable hook
    Hold relief
    Pending
    Coverage after move
    Pending
    Operator load
    Pending
    Reserve this slot for pick sequencing, staged holds, and operator handoff notes tied to the ranked lot.
No spread-the-load draft selected Apply stays disabled until the current focus yields compatible lots and a rebalance plan the operator can stage or confirm.
SLA-linked rescue
Keep rescue-on-threshold alerts and operator controls anchored beside fill and spread review
Standby

Hold stable rescue-on-threshold review slots here so later wiring can surface breach timing, urgency rollups, and operator-ready execution guidance without reshaping the current Inventory Watch workflow.

Threshold-breach summary No rescue-on-threshold alerts staged Reserve this slot for the next breached threshold, impacted material or lot scope, and the typed breach reason once rescue guidance lands.
Urgency summary Urgency rollup pending Keep the next-breach clock, at-risk reservations, and escalation window in view here once alert scoring is wired.
Execution readiness Operator rescue plan pending Hold this shell for typed operator sequencing, handoff owner, and escalation-channel copy before a rescue draft is committed.
Threshold-breach alerts

Keep ranked rescue alerts close to fill and spread so later wiring can compare breach reasons, urgency, and rescue lanes without leaving the current queue review.

0 alerts

Rescue-on-threshold alerts will populate here when the current focus crosses a hold or SLA breach boundary that needs guided operator intervention.

  1. Threshold watch Rescue alert rows stay anchored here

    Use each row for breach reason, impacted queue scope, proposed rescue lane, and guardrail copy once typed rescue guidance lands.

    Stable hook
    Threshold clock
    Pending
    At-risk exposure
    Pending
    Recommended lane
    Pending
    Reserve this slot for selected alert copy, urgency badges, and execution notes tied to the breached threshold row.
Batch-the-rescue
Review grouped rescue lanes before coordinating a shared rescue push
Standby

Keep grouped rescue lanes, lane-level urgency rollups, and shared execution hooks anchored here so later wiring can batch threshold breaches without reshaping the rescue workflow.

0 rescue lanes Grouped rescue batches can summarize shared breach windows, lane ownership, and coordination readiness in this slot.

Grouped rescue lanes will populate here when multiple threshold breaches can be coordinated through the same operator lane.

  1. Batch 01 Urgency watch
    Grouped rescue lane rows stay anchored here
    Stable hook

    Use each grouped lane row for the shared breach reason, queue scope, lane owner, and operator plan once batch-the-rescue logic lands.

    Grouped alerts
    Pending
    Queue scope
    Pending
    Lane owner
    Pending
    Next threshold clock
    Pending
    At-risk reservations
    Pending
    Coordination readiness
    Pending
    Reserve this slot for grouped-lane urgency notes, shared execution timing, and operator handoff copy.
Sequence-the-lane
Preview the ordered lane sequence before operators commit a grouped rescue handoff
Standby

Review ordered rescue steps, checkpoints, and controls beside the grouped lanes.

No rescue lane sequenced Lane, owner, and next window appear here when a rescue sequence is ready.
Ordered step preview
Review lane steps before operators stage or advance checkpoints
0 ordered steps

Ordered rescue steps appear here when the current lane is ready.

  1. Step 01
    Pending Preview
    Ordered rescue steps appear here

    Each step shows checkpoint, owner, scope, and timing when sequencing is ready.

    Checkpoint
    Pending
    Owner
    Pending
    Window
    Pending
Checkpoint summary
Keep checkpoint rollups and fallback guidance with the selected lane
Current checkpoint No checkpoint staged Current checkpoint owner, scope, and readiness appear here.
Next checkpoint Next checkpoint pending Next window, downstream owner, and readiness notes appear here.
Fallback coverage Fallback path pending Fallback coverage, escalation points, and recovery notes appear here.
Rescue handoff packet
Keep a shareable lane brief beside the selected sequence for copy or export
Brief pending

Share lane ownership, checkpoint rollups, fallback coverage, and operator guidance here.

Shareable brief not prepared Lane, objective, and checkpoint timing appear here when a brief is ready.
Lane ownership Ownership pending Primary owner, backup, and queue touchpoint appear here.
Checkpoint rollup Rollup pending Current checkpoint, next checkpoint, and timing stay in one brief.
Fallback coverage Coverage pending Fallback coverage, escalation checkpoint, and guardrails appear here.
Operator notes Guidance pending
Next rescue handoff guidance

Stage notes, advance timing, and fallback instructions appear here for the next handoff.

Stage selected
Pending
Advance timing
Pending
Fallback note
Pending
Copy and export controls await a selected lane sequence Copy and export stay disabled until a rescue lane sequence is selected.
Compare-the-lanes
Hold a side-by-side rescue lane review beside the active sequence
Comparison pending

Compare urgency, ownership, fallback load, and relief here without leaving the active sequence.

No rescue lane comparison staged Paired lanes, comparison goal, and review posture appear here when a comparison is ready.
Comparison urgency Urgency comparison pending Lead-lane timing, trailing slack, and breach delta appear here.
Ownership balance Ownership review pending Primary owners, backup coverage, and queue touchpoints appear here.
Fallback / escalation load Fallback review pending Shared fallback capacity, escalation load, and guardrails appear here.
Projected relief Relief estimate pending Recovered reservations, escalation relief, and queue relief appear here.

Side-by-side rescue lane comparisons appear here when another lane is ready.

  1. Comparison 01
    Awaiting lane pair Preview
    Side-by-side lane review appears here

    Each comparison row shows the paired lanes, shared question, and review notes.

    Primary lane Pending
    Primary rescue lane pending

    Lead lane label, rescue posture, and owner context appear here.

    Urgency
    Pending
    Ownership
    Pending
    Fallback / escalation load
    Pending
    Projected relief
    Pending
    Comparison lane Pending
    Comparison rescue lane pending

    Comparison lane label, review posture, and escalation context appear here.

    Urgency
    Pending
    Ownership
    Pending
    Fallback / escalation load
    Pending
    Projected relief
    Pending
    Compare controls await a paired lane review Compare, review, and clear stay disabled until another rescue lane is ready.
Rescue outcomes
Review post-apply rescue outcomes beside the active sequence
Outcome pending

Track outcome state, rollups, variance, and timeline here after apply.

No rescue outcome recorded Applied lane, checkpoint posture, and outcome summary appear here after apply.
Outcome rollups
Track applied result, rollup, and realized vs planned rescue copy
Outcome state Apply result pending Applied lane, checkpoint state, and operator acknowledgement appear here.
Result rollup Rollup pending Recovered reservations, deferred work, and outcome summary appear here.
Realized relief Realized relief pending Executed recovery totals, pressure reduction, and result window appear here.
Realized vs planned Variance pending Realized vs planned results appear here after the rescue sequence is applied.
Execution timeline / result list
Review post-apply milestones and result notes after the lane sequence commits
0 recorded results

Post-apply rescue milestones will populate here when a lane sequence is committed and execution results are ready to review.

  1. Result 01
    Pending Preview
    Post-apply rescue results appear here

    Each result row shows the applied checkpoint, planned result, realized result, and follow-up.

    Checkpoint
    Pending
    Planned result
    Pending
    Realized result
    Pending
    Follow-up
    Pending
Historical coordination reporting
Keep recent rescue coordination effectiveness, summaries, and drilldown detail inside the active sequence shell
History pending

Stage recent coordination reports, effectiveness rollups, and operator drilldown copy here without breaking the live rescue lane sequence, handoff, comparison, or outcomes layout.

0 coordination reports Reporting windows, compared rescue lanes, selected report scope, and export posture appear here when coordination history is ready.
History coverage Coverage pending Keep recent reporting windows, compared lane counts, and selected sequence coverage anchored here.
Coordination effectiveness Effectiveness pending On-time rescue coordination, balanced lane selection, and comparison quality roll up here.
Handoff reliability Handoff reliability pending Reserve this slot for staged vs completed handoffs, checkpoint drift, and fallback usage.
Realized relief Relief summary pending Keep realized queue relief, pressure reduction, and unresolved follow-up load visible here.
Filter and grouping shell
Hold shell-only rescue-history filters, grouping defaults, and cross-surface state without changing dashboard wiring
Filters pending

Keep posture, lane family, outcome quality, and follow-up burden controls visible here as shell-only defaults so later rescue-history wiring can reuse the same report, playbook, and saved-packet surfaces.

No rescue-history filters applied Reports, playbooks, and saved packets stay fully inclusive until shared filtering state can narrow historical rescue rows.
  • Posture · Any
  • Lane family · Any
  • Outcome quality · Any
  • Follow-up burden · Any
Stable chips stay ready here for future filter summaries, clear-all state, and selected shell copy.
Grouping stays visual-only until rescue-history records can cluster the report, playbook, and saved-packet shells together without inventing loaded data.
Report surface hint Report rows stay unfiltered Rescue reports continue showing the full shell until shared filtering can trim by posture, lane family, outcome quality, or follow-up burden.
Playbook surface hint Playbooks mirror the full report scope Linked playbook summaries stay inclusive until rescue-history filtering can synchronize matching lane plans.
Saved-packet surface hint Saved packets remain inclusive Saved history and playbook packets stay unfiltered until shared shell state can scope reopen and save views.
Recent reports
Review recent rescue coordination reports without leaving the active lane workflow
0 report rows

Filter and grouping controls are shell-only for now, so report rows stay inclusive and the list preserves its existing flat layout.

Recent rescue coordination reports appear here when completed or reviewed lane work is ready to compare.

  1. Report 01
    Awaiting history Recent coordination
    Recent rescue coordination reports appear here

    Each report row can capture the reporting window, compared lanes, handoff result, and realized rescue effectiveness for later drilldown.

    Reporting window
    Pending
    Lane pair
    Pending
    Effectiveness
    Pending
    Follow-up
    Pending

    Select a report row to keep coordination recap, drilldown notes, and follow-up copy anchored to the current rescue shell.

History drilldown
Keep selected report detail, coordination recap, and operator follow-up inside the same shell
Drilldown pending

Use the selected report detail for report-window recap, handoff reliability, lane-comparison context, and realized-relief notes once historical coordination reporting is loaded.

No historical coordination report selected Select a recent report row to stage the coordination recap, handoff reliability, and realized-relief drilldown here.
Reporting window Window pending Start and end time, reporting scope, and compared lane count appear here.
Coordinated lanes Lane pairing pending Primary lane, comparison lane, and operator coverage stay in one detail strip.
Sequence effectiveness Effectiveness pending Sequence adherence, checkpoint drift, and compare-the-lanes confidence appear here.
Realized relief Relief pending Relief versus planned, unresolved pressure, and follow-up posture appear here.
Coordination drilldown Sequence adherence and lane comparison detail
  • Sequence adherence Current checkpoint completion, skipped steps, and timing drift can land here.
  • Handoff reliability Operator handoff notes, fallback usage, and acknowledgement timing can render here.
  • Lane comparison rationale Side-by-side urgency delta, ownership balance, and relief tradeoffs can be reviewed here.
Follow-up surface Outcome recap, escalations, and unresolved work
  • Realized vs planned relief Relief delta, recovered reservations, and remaining queue pressure can surface here.
  • Escalation follow-up Escalation status, missed checkpoints, and unresolved owners can render here.
  • Reporting export notes Shift recap copy, audit-ready context, and next review timing can stay anchored here.
Multi-lane rescue playbooks
Keep historical rescue playbook summaries and selected multi-lane drilldown beside the active report detail
Playbooks pending

Stage multi-lane rescue playbook shells here so later dashboard wiring can summarize the selected report's lane mix, recommended coordination path, and operator drilldown without reshaping the rescue-history workflow.

0 playbooks Keep grouped lane summaries, selected playbook scope, and share/export posture copy ready here for history-driven playbook review. Shared rescue-history filters are inactive, so playbook rows stay aligned with the full report shell by default.
Playbook summaries
Hold the recent multi-lane rescue playbook rows beside the selected coordination report
0 playbook rows

Playbook rows stay inclusive until report-driven rescue-history filters can narrow matching lane plans.

Multi-lane rescue playbooks appear here when historical coordination reports start carrying typed playbook summaries.

  1. Playbook 01 Awaiting playbooks
    Multi-lane rescue playbooks will populate here

    Each playbook row can capture lane groupings, trigger posture, planned rescue relief, and handoff readiness for the selected coordination window.

    Lanes
    Pending
    Trigger window
    Pending
    Planned relief
    Pending
    Handoff posture
    Pending
Selected playbook detail
Keep the active rescue playbook summary, lane fields, and operator actions in one drilldown shell
Detail pending

Use the selected playbook detail for lane-by-lane rescue intent, timing, and handoff guidance once coordination history starts supplying typed playbook drilldown.

No rescue playbook selected Select a playbook row to stage multi-lane rescue intent, drilldown copy, and operator-ready action hooks here.
Lane coverage Coverage pending Compared, fallback, and assist lanes stay visible here.
Trigger window Window pending Threshold, review timing, and escalation trigger can land here.
Relief plan Relief pending Planned recovered holds, queue impact, and fallback load appear here.
Handoff posture Handoff pending Owner, confirmation timing, and export posture stay anchored here.
Lane drilldown Primary, assist, and fallback lane guidance
  • Primary lane Keep the lead lane's rescue responsibility, coordination notes, and confidence here.
  • Assist lane Stage support-lane coverage, relief handoff, and timing dependencies here.
  • Fallback lane Reserve this slot for fallback lane criteria, stop conditions, and escalation notes.
Operator notes Checklist, handoff copy, and unresolved follow-up
  • Operator checklist Stage the review checklist, apply order, and release guards here.
  • Handoff packet Reuse this space for copied handoff notes, acknowledgements, and export-ready context.
  • Follow-up load Keep unresolved owners, escalation timing, and the next review window visible here.
No playbook action staged Detail actions stay disabled until a historical playbook row can drive compare-the-lanes, queue scope, or handoff review.
Saved rescue packets
Keep saved rescue history and playbook packets indexed beside the current export shells
Saved packets pending

Hold a stable saved-packet shell here so later dashboard wiring can list, reopen, remove, and save rescue history or playbook packets without reshaping the existing export surfaces.

0 saved packets Saved history packets, playbook packets, active selection, and blocked save posture stay visible here until persistence is wired. Saved packets continue mirroring the inclusive report and playbook shell until shared filter state can scope saved history.
History packets 0 saved history packets Saved coordination recap packets will count here once report export can persist them.
Playbook packets 0 saved playbook packets Saved lane-brief packets will aggregate here when playbook export gains persistence hooks.
Selection state No saved packet selected Packet selection, source scope, and reopen intent stay anchored here once a row is active.
Save posture Save disabled until export context exists Keep blocked save reasons explicit here until history or playbook exports can create packets.
Packet list
Hold saved rescue packet rows close to the history and playbook export surfaces
0 packet rows

Saved packet rows remain inclusive until rescue-history filter state can hide non-matching exports.

Saved rescue packets appear here after history or playbook exports gain explicit save support.

Post-remove handoff pending When packet removal is wired, this list can either advance focus to the next saved packet or restore the empty-state guidance when the final saved row is removed.
  1. Packet 01 Awaiting saved packets
    Saved rescue packets will populate here

    Each packet row can capture the saved source shell, staged export scope, timestamp, and safe reopen or remove posture for later review.

    Source shell
    Pending
    Packet scope
    Pending
    Saved at
    Pending
    Action posture
    Pending

    Select a saved packet row to stage reopen routing, remove safeguards, and packet recap copy in the detail shell.

Saved packet detail
Keep saved packet detail, source recap, and action placeholders in one review shell
Detail pending

Use this detail shell for saved packet summary copy, source-shell drilldown, and persistence guardrails once packet storage is wired.

No saved packet selected Select a saved packet row to stage the packet summary, source scope, and safe reopen or remove notes here.
Packet source Source pending History export or playbook export origin will stay visible here.
Saved timestamp Timestamp pending Save time, last refresh, and later overwrite context can land here.
Packet scope Scope pending Included recap, share copy, and linked context will be summarized here.
Retention posture Retention pending Save safety, retention windows, overwrite rules, and remove guardrails can stay explicit here.
Saved packet comparison
Stage baseline and target packet contrast beside the saved-packet detail shell
Comparison idle

Keep baseline labels, target selectors, difference summaries, and equivalent-field copy in one shell so later wiring can compare two saved packets without disturbing save, replay, lifecycle, or audit affordances.

No packet comparison staged Select a saved packet to pin the baseline, then choose another saved packet when comparison choices are wired. Until that pair exists, keep contrast, delta, and no-difference copy honest.
Baseline label Awaiting baseline packet Pin the selected packet title, source shell, or saved timestamp here once detail selection exists.
Target label Awaiting comparison packet Reserve this hook for the explicit second packet only, and leave it blank rather than implying a fallback match.

Once detail selection exists, keep recap, scope, retention, and source-shell references here as the stable baseline for packet contrast.

  • Packet recap Select a saved packet row to stage the baseline recap, source note, and saved-at context here.
  • Retention posture Retention windows, overwrite safety, and remove guardrails stay blank until the baseline packet is real.
  • Lifecycle / replay context Reuse the saved-packet detail shell below for real reopen, remove, replay, and audit affordances; this column only mirrors compare-ready packet context.

When another saved packet is chosen, mirror its recap, retention posture, and source-shell summary here for side-by-side review.

  • Packet recap Choose another saved packet before any target recap is rendered in the comparison column.
  • Retention posture Do not invent matching retention or remove posture copy for the target slot while it is empty.
  • Difference focus Once both packets are real, use this row for scope, source, or handoff contrast without mutating the baseline detail shell.
Selection coverage 0 of 2 packets ready Hold the baseline and target labels open for explicit packet choices only; side-by-side review starts after two real selections exist.
Contrast state No side-by-side contrast loaded Field-level contrast stays empty until baseline and target packets are both real saved-packet selections.
Difference rollup No field deltas reviewed When a packet pair is available, use this panel for recap, source, retention, and handoff deltas without replacing the underlying detail view.
Equivalent / no-difference copy No equivalent fields confirmed When tracked fields match, use this hook for honest no-difference messaging instead of fabricating a delta or implied packet drift.
Choose a second saved packet to unlock side-by-side contrast Select a saved packet to set the baseline, then pair it with another saved packet before any contrast summary appears. Until then, keep the comparison shell empty and the existing detail, lifecycle, audit, and replay affordances unchanged.
Packet summary Recap copy, share posture, and linked source notes
  • Recap copy Saved report recap or playbook brief copy can render here once a packet is selected.
  • Share posture Keep saved share targets, recipients, and blocked publish reasons visible here.
  • Source shell notes Reopen targets back to the originating history or playbook shell can stay anchored here.
Action guardrails Safe reopen, remove, retention, and save prerequisites
  • Reopen target Require a selected saved packet and a supported return path into the originating shell before reopen can unlock.
  • Remove safeguard Keep selection checks, retention rules, explicit confirmation copy, and a shell-only disabled remove affordance visible before any packet lifecycle wiring can send a destructive request.
  • Save prerequisite Save stays blocked until a history or playbook export shell provides packet-ready context.
Removal stays inert until a selected packet exposes retention rules and an operator can review explicit confirmation copy. This shell-only lane does not send a destructive request.
Remove status No removal request sent
Status messaging remains idle until lifecycle wiring can verify packet selection, confirmation, and backend support. No fake success state is shown from this shell.
Post-remove transition Next-selection or empty-state handoff pending
When remove is wired, hand off to the next saved packet when one remains; otherwise restore the packet empty state and clear stale detail or replay context.
Removal controls remain disabled until packet lifecycle wiring is available Keep retention visibility, explicit confirmation copy, and post-delete transition rules in place before reopen or remove affordances can unlock.

Saved packet detail remains in a safe empty state until packet persistence and selection wiring are available.

Save, reopen, and remove controls are blocked until packet wiring is ready Save requires staged history or playbook export context. Reopen and remove require a selected saved packet and supported persistence metadata.
No lane sequence selected Sequence controls stay disabled until a grouped rescue lane produces ordered checkpoints, handoff timing, and operator confirmation copy.
Coordinated execution
Keep shared rescue-lane execution controls beside the current rescue review
0 lanes selected
Coordination summary No grouped rescue lane selected Hold this slot for the shared rescue objective, total grouped exposure, and the next operator checkpoint.
Handoff readiness Handoff bundle pending Reserve this slot for grouped lane owners, channel routing, and operator packet status once batching is wired.
Escalation path Escalation path pending Keep the shared urgency tier, fallback channel, and latest commit window close to the lane batch controls.
No coordinated rescue batch selected Batch execution stays disabled until grouped rescue lanes produce a shared plan, operator handoff, or escalation draft.
Execution controls

Keep operator execution controls, staged selection copy, and escalation affordances in one shell so later wiring can confirm rescue work without shifting away from the active queue focus.

0 alerts selected
No rescue-on-threshold alert selected Rescue execution stays disabled until a breach alert produces an operator-ready plan, handoff path, or escalation draft.
Top materials
  • Material-level contributors can render here for the selected shift window.
Top lots
  • Lot-level shifts and standout hold pressure can render here once detail wiring lands.
Action breakdown
  • Recovery Recovered reservations and released held balance can summarize here.
  • Reassignment Reassigned demand and compatible lot handoff detail can summarize here.

Stock Adjustment

Stage quantity corrections, reservation updates, and operator notes for the currently selected material lot.

Adjustment shell
Select a material to load its current balance and prepare a stock adjustment.

Reorder Requests

Pending supplier replenishment requests staged from low-stock and currently allocated material lots.

Request queue

No reorder requests staged yet. Batch requests will appear here for supplier follow-up.

Material reorder requests awaiting supplier follow-up
Material Requested Priority Status