Farm control for live print operations.
Track quote intake, release gating, machine telemetry, QC handoff, and shipment readiness across FDM and UV lanes from one surface.
Control center
Refresh the latest snapshot, seed demo data, and confirm the API target before stepping into live queues.
Connection details
- Queue
- 0
- Manual Review
- 0
- Ready For Release
- 0
- Printing
- 0
Profitability Watch
Track margin exposure, realized profitability, and energy usage for every active job.
| Job | Status | Machine | Family | Quoted | Realized | Δ margin | Started |
|---|
Ops Alerts
SLA risk, stale telemetry, machine health, camera gaps, and inventory pressure in one queue.
No active alerts. The farm is within its current operating thresholds.
Quote Intake
Create a new quote request from the ops console to test pricing, ETA, and review gates.
Quote Review Queue
Newest quotes first, with manual-review items floated to the top for operator approval.
Stage visible quotes for comparison, approval, or rejection without changing the current review-card layout.
No quotes recorded yet. Use the intake form or seed demo data.
Approved Quotes Pending Order
Operator-safe staging queue for approved quotes that still need order creation. Quotes with linked orders stay out of this batch surface.
Stage only visible approved quotes without linked orders so later dashboard wiring can create production-ready orders in one operator-reviewed pass.
No approved quotes are waiting on order creation. Quotes with existing linked orders stay out of this queue.
| Quote | Customer | Approved | Total | Due | Order Scope |
|---|
Quote Review Detail
Inspect the original intake, asset metadata, per-line review reasons, and approval state before syncing an order.
Reserve a stable operator action for duplicating the currently inspected quote once the review workflow is wired.
Select a quote from the review queue to inspect the full intake snapshot.
Quote Comparison
Stage quotes side by side to compare pricing, service commitments, and manual-review gates before taking a bulk action.
Select up to two quotes from the review queue to populate the comparison shell.
- Total delta
- —
- Ship window delta
- —
- Manual review delta
- —
- Asset mix delta
- —
SLA Summary
Upcoming due windows, escalations, and at-risk jobs staged for the next reporting wave.
At-Risk Queue
Review jobs closest to their committed handoff window and confirm the visible scope before acting in the release queue.
No at-risk jobs in the current report window.
| Job | Customer | Due | Status | Owner |
|---|
Escalation Notes
Track exception reasons, handoffs, and next steps for the current reporting snapshot.
No escalations are staged for this reporting snapshot.
Machine Overview
First-class and legacy machines share one routing surface with guarded release rules.
Stage visible machine cards for service windows, return-to-service checks, and recovery actions without disturbing the current plant overview layout.
Start maintenance should target idle or paused machines, return-to-service applies to machines already in maintenance, and power-cycle recovery should stay scoped to paused, maintenance, or offline hardware until telemetry is healthy again.
- Start → idle, paused
- Return → maintenance
- Power cycle → paused, maintenance, offline
K2 Plus
k2-plus-01
First-class machine is idle and can join calibration, inspection, or preventative maintenance batches without displacing the current card layout.
Kobra 3 Max
kobra-3-max-01
First-class machine is idle and can join calibration, inspection, or preventative maintenance batches without displacing the current card layout.
Centauri Carbon
centauri-carbon-01
First-class machine is idle and can join calibration, inspection, or preventative maintenance batches without displacing the current card layout.
Snapmaker U1
snapmaker-u1-01
First-class machine is idle and can join calibration, inspection, or preventative maintenance batches without displacing the current card layout.
eufyMake E1
eufymake-e1-01
First-class machine is idle and can join calibration, inspection, or preventative maintenance batches without displacing the current card layout.
AnkerMake M5
ankermake-m5-01
Legacy machine is idle and can join calibration, inspection, or preventative maintenance batches without displacing the current card layout.
Release Queue
Jobs awaiting review, ready to release, or actively printing.
Reserve stable hooks for passing or failing visible QC rows without disturbing the current release-queue layout.
Stage visible production rows for complete, resume, requeue, or cancel flows without displacing the current single-job controls.
Complete applies to printing and paused jobs, resume applies to paused jobs, requeue applies to failed jobs, and cancel can stay available for manual-review, release-ready, printing, or paused work.
- Complete → printing, paused
- Resume → paused
- Requeue → failed
- Cancel → review, release, printing, paused
Stage visible release-queue jobs for a coordinated target-machine reroute while the current QC, release, and per-job override shells stay in place.
Batch reroute should stay focused on queued, scheduled, awaiting-manual-review, or ready-for-release jobs. Use the dedicated emergency failover surface below for printing, paused, or failed work that lost its primary machine.
- Route now → queued, scheduled
- Hold for review → manual review
- Release lane → release ready
- Emergency failover stays on route override
Stage visible release-queue jobs for coordinated inventory reserve or release passes while the current QC, release, reroute, and per-job controls stay in place.
Reserve should stay focused on queued, scheduled, awaiting-manual-review, or ready-for-release jobs that still need material holds before release. Release should stay available when operator review, rerouting, or replenishment removes the need for a staged reservation before the job leaves the release queue.
- Reserve now → queued, scheduled
- Hold before release → manual review, release ready
- Release staged holds → review, release ready
- Active print consumption stays on production + inventory watch
No active jobs yet. Seed sample data with POST /demo/bootstrap.
| Job | Status | Family | Machine | Quality | Due | Actions |
|---|
Job Inspector
Review the richer release, compliance, inventory, and routing context for the selected job.
Select a job from the release queue to inspect release blockers, manual review context, compliance audit facts, and candidate routes.
- Job
- n/a
- Status
- n/a
- Family
- n/a
- Service Tier
- n/a
- Machine
- n/a
- Due Date
- n/a
Release Blockers
- No release blockers recorded.
Manual Review Reasons
- No manual review reasons recorded.
Compliance Audit Summary
No compliance audit context loaded.
- Traceability
- n/a
- Evidence
- n/a
Inventory Reservations
No inventory reservations loaded.
Route Context
No candidate routes or route override context loaded.
- No route candidates recorded.
Route Override
Pin a queued job to a different machine or quality tier before release when the operator wants to override `AUTO`.
Reserve a dedicated reroute surface for printing, paused, or failed jobs that need an operator-directed fallback machine.
Inventory Watch
Low-stock and currently allocated material lots across SpoolStock Pro and InvenTree-backed supplies.
Stage visible materials for stock adjustments or reorder requests without changing the current live inventory feed.
Stage visible material lots for coordinated reserve or release passes without displacing the stock-adjustment or reorder request surfaces.
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 | 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.
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.
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.
- 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.
| Reservation | Material | Current Lot | Reserved | Held Since | Status |
|---|
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.
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
Keep the final target-lot choice close to the recovery draft so later dashboard wiring can reuse the same operator flow.
- Compatible lots will populate here Stable hook
Use this slot for material-code, expiry, available-balance, and replenishment compatibility signals.
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.
Reserve this area for the held lot, hold age, and reservation pressure that currently owns the inventory.
- Held balance
- —
- Hold age
- —
- Demand load
- —
Use this area for compatible lot context, replenishment timing, and why the proposed target outranks the current hold.
- Available balance
- —
- Replenishment window
- —
- Compatible demand
- —
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
- —
- Compatible target reasons, stale-hold flags, and release blockers can render here.
- Lot ancestry, replenishment receipts, and supersession notes can render here.
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.
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.
- Last 24 hours Awaiting reservation context
Selected-reservation hold movement, recoveries, and operator touchpoints will appear here for the last 24 hours.
- Last 7 days Awaiting weekly context
Weekly hold-aging swings, recommendation changes, and recovery cadence will appear here once a reservation is in focus.
- 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.
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.
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
- —
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.
Keep fill-the-focus review hooks anchored to the current material and lot focus
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.
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.
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.
Keep spread-the-load review hooks aligned with the current lot or material focus
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.
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.
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.
- Stable hookRank 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.
- Hold relief
- Pending
- Coverage after move
- Pending
- Operator load
- Pending
Keep rescue-on-threshold alerts and operator controls anchored beside fill and spread review
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.
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.
Rescue-on-threshold alerts will populate here when the current focus crosses a hold or SLA breach boundary that needs guided operator intervention.
- Stable hookThreshold 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.
Review grouped rescue lanes before coordinating a shared rescue push
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.
Grouped rescue lanes will populate here when multiple threshold breaches can be coordinated through the same operator lane.
- Stable hookBatch 01 Urgency watchGrouped rescue lane rows stay anchored here
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
Preview the ordered lane sequence before operators commit a grouped rescue handoff
Review ordered rescue steps, checkpoints, and controls beside the grouped lanes.
Review lane steps before operators stage or advance checkpoints
Ordered rescue steps appear here when the current lane is ready.
- Step 01Pending PreviewOrdered rescue steps appear here
Each step shows checkpoint, owner, scope, and timing when sequencing is ready.
- Checkpoint
- Pending
- Owner
- Pending
- Window
- Pending
Keep checkpoint rollups and fallback guidance with the selected lane
Keep a shareable lane brief beside the selected sequence for copy or export
Share lane ownership, checkpoint rollups, fallback coverage, and operator guidance here.
Stage notes, advance timing, and fallback instructions appear here for the next handoff.
- Stage selected
- Pending
- Advance timing
- Pending
- Fallback note
- Pending
Hold a side-by-side rescue lane review beside the active sequence
Compare urgency, ownership, fallback load, and relief here without leaving the active sequence.
Side-by-side rescue lane comparisons appear here when another lane is ready.
- Comparison 01Awaiting lane pair PreviewSide-by-side lane review appears here
Each comparison row shows the paired lanes, shared question, and review notes.
Primary lane PendingPrimary rescue lane pendingLead lane label, rescue posture, and owner context appear here.
- Urgency
- Pending
- Ownership
- Pending
- Fallback / escalation load
- Pending
- Projected relief
- Pending
Comparison lane PendingComparison rescue lane pendingComparison 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
Review post-apply rescue outcomes beside the active sequence
Track outcome state, rollups, variance, and timeline here after apply.
Track applied result, rollup, and realized vs planned rescue copy
Review post-apply milestones and result notes after the lane sequence commits
Post-apply rescue milestones will populate here when a lane sequence is committed and execution results are ready to review.
- Result 01Pending PreviewPost-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
Keep recent rescue coordination effectiveness, summaries, and drilldown detail inside the active sequence shell
Stage recent coordination reports, effectiveness rollups, and operator drilldown copy here without breaking the live rescue lane sequence, handoff, comparison, or outcomes layout.
Hold shell-only rescue-history filters, grouping defaults, and cross-surface state without changing dashboard wiring
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.
- Posture · Any
- Lane family · Any
- Outcome quality · Any
- Follow-up burden · Any
Use this shell to keep a selected fixed trend window, the active rescue report row, and current queue cross-highlighting in one place so later dashboard wiring can move between hold pressure, coordination history, and live queue context without adding a separate dashboard section.
Review recent rescue coordination reports without leaving the active lane workflow
Recent rescue coordination reports appear here when completed or reviewed lane work is ready to compare.
No rescue coordination reports match the active posture, lane family, outcome quality, and follow-up burden filters. Widen or clear the shell filters when live history is available.
- Report 01Awaiting history Recent coordinationRecent 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
Keep selected report detail, coordination recap, and operator follow-up inside the same shell
Use the selected report detail for report-window recap, handoff reliability, lane-comparison context, and realized-relief notes once historical coordination reporting is loaded.
- 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.
- 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.
Stage selected report recap copy, share-target notes, and export packet hooks here so later dashboard wiring can publish rescue history without reshaping the current drilldown.
Keep historical rescue playbook summaries and selected multi-lane drilldown beside the active report detail
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.
Hold the recent multi-lane rescue playbook rows beside the selected coordination report
Multi-lane rescue playbooks appear here when historical coordination reports start carrying typed playbook summaries.
No historical playbooks match the active rescue-history filters. Expand the shell defaults once linked playbook summaries can respond to report filtering.
- Playbook 01 Awaiting playbooksMulti-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
Keep the active rescue playbook summary, lane fields, and operator actions in one drilldown shell
Use the selected playbook detail for lane-by-lane rescue intent, timing, and handoff guidance once coordination history starts supplying typed playbook drilldown.
- 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 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.
Stage the most relevant live queue slice, best linked report context, and compare or staged sequence jump here so later dashboard wiring can guide operators into the next follow-through without reshaping the rescue playbook detail.
Stage selected playbook lane brief copy, share targets, and export packet hooks here so later dashboard wiring can publish multi-lane rescue handoffs without shifting the history layout.
Keep saved rescue history and playbook packets indexed beside the current export shells
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.
Hold saved rescue packet rows close to the history and playbook export surfaces
Saved rescue packets appear here after history or playbook exports gain explicit save support.
No saved rescue packets match the active rescue-history shell filters. Widen the shell scope after saved history and playbook packets can sync with shared filters.
- Packet 01 Awaiting saved packetsSaved 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
Keep saved packet detail, source recap, and action placeholders in one review shell
Use this detail shell for saved packet summary copy, source-shell drilldown, and persistence guardrails once packet storage is wired.
Stage baseline and target packet contrast beside the saved-packet detail shell
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.
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.
Stage comparison readiness, export/share handoff copy, and packaging-safe summary labels here so later wiring can publish the contrast view without reshaping saved-packet detail, lifecycle, audit, or replay affordances.
- 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.
- 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.
Stage recent replay and removal summaries, packet-activity hints, and honest empty-history messaging here so later lifecycle wiring can fill in real audit details without reshaping the saved-packet detail shell.
- Replay activity row No replay event stagedEmpty
- Removal activity row No removal event stagedEmpty
- Audit summary copy Aggregate replay or remove counts, last-updated timestamps, and safe lifecycle posture can render here without changing the surrounding detail shell.
- Recent row copy Each recent row can later show actor, timestamp, packet target, and outcome details while preserving these stable hooks.
- Empty-state messaging If a saved packet has no audit history, keep the honest empty notice and avoid implied success or destructive completion copy.
Stage replay readiness, partial restore notices, and per-target reopen summaries here so later dashboard wiring can resume saved report, playbook, queue, or guided follow-through context without reshaping this review shell.
Keep shared rescue-lane execution controls beside the current rescue review
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.
- Material-level contributors can render here for the selected shift window.
- Lot-level shifts and standout hold pressure can render here once detail wiring lands.
- 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.
Reorder Requests
Pending supplier replenishment requests staged from low-stock and currently allocated material lots.
No reorder requests staged yet. Batch requests will appear here for supplier follow-up.
| Material | Requested | Priority | Status |
|---|
Failure Incidents
Machine-side stoppages and requeue candidates captured from plant telemetry.
Auto-requeue data will appear here when failures are recorded.
No failure incidents recorded.
Orders
Commercial orders synchronized into production-ready jobs.
Stage visible QC-cleared or packed orders for batch packing and label purchase once the fulfillment script is wired.
Stage visible QC-cleared or packed orders for coordinated carrier-rate passes while the existing pack and label-purchase controls stay in place.
Batch rating should stay focused on QC-cleared or already packed orders that still need a shipment quote. Packed orders can remain eligible for re-rating before label purchase, while shipped orders stay on the shipment-side tracking refresh shell.
- Rate now → qc
- Re-rate → packed
- Purchase labels stays on fulfillment
- Shipped orders stay on refresh
No Medusa orders synced yet.
| Order | State | Total | Jobs | Shipment | Actions |
|---|
Shipments
Rate, label, and tracking outcomes from ShipStation, with manual tracking refresh controls.
Stage visible labeled shipments for coordinated carrier refresh sweeps without displacing the current exception-recovery shell or row-level tracking actions.
Batch refresh should stay focused on labeled, in-transit, or exception shipments with an active tracking number. Delivered rows can remain read-only, while replacement creation stays on the exception-recovery shell below.
- Initial poll → label_purchased
- Follow-up → in_transit
- Investigate → exception
- Delivered stays row-level
Stage only visible exception shipments for operator-reviewed tracking refreshes or replacement-order recovery once the shipment queue script is wired.
No shipment labels purchased yet.
| Shipment | Carrier | Status | Tracking | Actions |
|---|
Integration Health
Webhook intake posture across Medusa and ShipStation, including failures, rejected payloads, and duplicate suppression.
No external webhooks processed yet.
Receipt Inspector
Inspect receipt metadata, linked entities, dedupe identity, and payload fingerprint for any processed webhook.
Select a webhook receipt to inspect its exact result, dedupe identity, and linked order or shipment.
- Receipt
- n/a
- Source
- n/a
- Event Type
- n/a
- Status
- n/a
- Result Code
- n/a
- Event Identity
- n/a
- Order
- n/a
- Shipment
- n/a
- Received
- n/a
- Processed
- n/a
n/a
n/a n/a Recent Events
Audit trail for route freezes, manual approvals, releases, and failures.
No production events recorded yet.
Operating Notes
Current defaults carried over from the print-ops policy engine.
Quote policy: instant for low-risk jobs, manual review for flagged geometry, unsupported profiles, specialty UV work, and compliance risk.
Release policy: auto only when machine health, camera, power telemetry, and profile checks pass. Operator approval clears manual blockers.
Scheduling: maximize expected margin per machine hour subject to SLA floor, capability match, and inventory readiness.