Dashboard
Orders by Source
Pipeline Status
| Order | Source | Customer | Qty | Product | Status | Due | Actions |
|---|
Bill of Materials Configuration
Define material usage per piece for each product type. These values are used to calculate expected consumption and identify waste.
| Material | Postcard | Printed Letter | Hybrid | Fully Written | Unit |
|---|---|---|---|---|---|
| Envelope | per piece | ||||
| Postage | |||||
| Forever Stamp | per piece | ||||
| Presort Stamp | per piece | ||||
| Printed Postage (Indicia) |
per piece | ||||
| Paper Stock | |||||
| Letter Paper (8.5x11) |
sheets per piece | ||||
| Insert Stock | sheets per piece | ||||
| Postcard Stock | per piece | ||||
| Ink & Toner | |||||
| Black Toner | % of cartridge | ||||
| Color Toner | % of cartridge | ||||
| Pens (Robot Writing) | |||||
| Blue Pen | % of cartridge | ||||
| Black Pen | % of cartridge | ||||
Unit Conversion Reference
Use these guidelines to calculate your usage percentages:
Expected Usage Calculator
Based on current BOM settings and recent production:
Waste Analysis
Comparing expected usage (based on orders shipped) vs actual consumption to identify waste, misprints, and potential theft.
| Material | Scheduled | Ordered | Expected Use | Actual Use | Variance | Status |
|---|
Expected Time Per Piece (seconds)
Configure expected processing time per piece for each station and product type. Used to calculate efficiency variance.
| Station | Postcard | Printed Letter | Hybrid | Fully Written | Unit |
|---|---|---|---|---|---|
| ๐ฅ Incoming | sec/piece | ||||
| ๐ Prep | sec/piece | ||||
| ๐จ๏ธ Printing | sec/piece | ||||
| โ๏ธ Writing | sec/piece | ||||
| ๐จ Inserting | sec/piece | ||||
| ๐ฆ Shipping | sec/piece |
Station Performance Log
| Date | Order | Station | Product | Pieces | Expected | Actual | Variance | Operator |
|---|
Active Integrations
Order sources feeding into the production dashboard.
Webhook Endpoints
Incoming order webhooks from integration partners.
Outbound Webhooks (Status Updates)
Recent API Activity
| Time | Source | Event | Order ID | Details | Status |
|---|---|---|---|---|---|
| 2 min ago | PropStream | order.created | BP-28813 | 1,250 pieces โข Hybrid Letter | Success |
| 8 min ago | SoldFast | order.created | BP-28812 | 500 pieces โข Written Letter | Success |
| 15 min ago | PropStream | order.created | BP-28811 | 2,100 pieces โข Postcard | Success |
| 1 hr ago | Shopify | order.created | BP-28810 | 100 pieces โข Hybrid Letter | Success |
| 2 hr ago | Manual | order.created | BP-28809 | 750 pieces โข Written Letter | Success |
PATCH /orders/{id}/status calls per order. Partners are unaware of batching.โ
Requests
Ingest Pipeline
Webhooks
| Endpoint | Requests | p50 | p95 | p99 | Latency |
|---|---|---|---|---|---|
| Waiting for metrics data... | |||||
| Person | Role | Stations | Modules | Status | Actions |
|---|
Authentication Method
Security Settings
Offline Queue Safety
Backend Implementation Notes
dashboard.ballpointmarketing.com, the auth flow will be:1.
POST /auth/send-code โ sends OTP to the user's email via SES/SendGrid2.
POST /auth/verify-code โ validates OTP, returns short-lived session token. If user is management role, returns requires_totp: true3.
POST /auth/verify-totp โ validates authenticator code, upgrades session to full access4. Session stored as HttpOnly, Secure, SameSite=Strict cookie with 8h expiry. Dashboard currently uses sessionStorage as interim; migrate to cookie-based auth when backend is deployed.
5. TOTP enrollment: Management users set up authenticator on first login via QR code from
POST /auth/enroll-totpโ Server-side authorization (required for production):
6. Session tokens must encode
role, allowed_stations, and allowed_modules as JWT claims (or store server-side and validate per request)7. All API endpoints must enforce role-based access: employees may only read/write orders at their assigned station(s); management-only endpoints (
/batches, /reports, /staff, /sla) must return 403 for employee tokens8.
GET /orders must filter by employee's station scope server-side โ never trust client-side filtering alone9.
PATCH /orders/:id/status must verify the operator has permission for that station before accepting the transition10.
GET /orders?q=... (server search) must also enforce station-scoped results for employee sessions11. Before go-live, complete and archive a targeted authorization middleware audit for all dashboard-consumed endpoints (see
deploy/developer-integration-checklist.md)
Service Level Agreements by Source
Define turnaround times for each order source. Integration orders have faster SLAs.
* All times in business days
Processing Time by Product Type
Hours required per stage. Variable stages scale with order quantity.
* Times are estimates for 1,000 piece orders. Larger orders scale proportionally.
Station Capacities
Maximum throughput per hour for scheduling calculations.
Daily Production Summary
| Date | Pieces In | Pieces Out | Active Orders | In Production | Completed | Overdue | Low Stock Items |
|---|
Staff Performance vs Station Capacity
| Operator | Station | Orders Processed | Pieces Handled | Avg Time/Order | vs Expected | Efficiency |
|---|
Missed Due Today Tasks
| Order | Customer | Station | Should Have Completed | Actual Status | Hours Behind | Impact |
|---|