1. Capture
Record What Happened On The Floor
Operators enter measured proof/volume data and product movement events. DSPdesk validates the request against current inventory before allowing post.
Workflow
How DSPdesk turns operations into monthly filings.
The system follows a strict chain: capture real activity, enforce inventory integrity, map events into reporting buckets, then generate filing outputs from the same source data.
Sequence
- 1. Capture - Record What Happened On The Floor
- 2. Reconcile - Enforce Inventory Invariants
- 3. Aggregate - Map Events To TTB Activities
- 4. File - Generate Submission-Ready Outputs
2. Reconcile
Enforce Inventory Invariants
The ledger and exception layer keep tank, lot, and packaged balances aligned. Any mismatch is surfaced with a corrective workflow instead of silent drift.
3. Aggregate
Map Events To TTB Activities
Posted events are classified into canonical TTB activity buckets, then summarized for the selected period with tie-out validation between forms.
4. File
Generate Submission-Ready Outputs
Teams review previews, generate official PDFs, and export supporting packet artifacts from the same monthly context used for filing decisions.
See the UI behind each phase
The product tour shows concrete screens for the same capture, reconcile, aggregate, and file flow described here.