From purchase order to shipment, every milestone tracked and risk-scored
SPUN ingests structured PO data, monitors factory-reported production checkpoints, and runs a delay risk model that alerts brands when milestone velocity falls behind schedule.
How data flows through SPUN
PO data is structured at order creation into a milestone schedule with committed checkpoint dates per stage. Factory logs checkpoint timestamps as work completes. SPUN computes expected versus actual milestone progression and updates a delay risk score on each checkpoint event. Architecture is based on structured event log, not polling or scraping.
The order board
How active purchase orders appear in SPUN, with AI risk scoring and expandable alert detail.
| Order ID | Factory | Due Date | Current Stage | AI Risk Score | Status |
|---|---|---|---|---|---|
| PO-2026-0841 | Garmen Nusantara | Sew complete | 12% | On Track | |
|
Estimated slipNone detected
Checkpoint statusAll milestones on or ahead of schedule
Factory reasonNo delay reason logged
Recommended actionContinue monitoring. Next checkpoint: QC pass in 5 days.
|
|||||
| PO-2026-0854 | Texindo Bandung | QC pass | 61% | At Risk | |
|
Estimated slip3 to 5 days
Checkpoint behindSew complete logged 4 days past committed date
Factory reasonQuality rework on two SKUs required extra handling time
Recommended actionMonitor QC completion closely. Consider confirming logistics booking with carrier for flexibility window.
|
|||||
| PO-2026-0819 | Sejahtera Garmen | Ship ready | 88% | Delayed | |
|
Estimated slip7 to 9 days
Checkpoint behindQC pass logged 6 days past committed date
Factory reasonMaterial delay: fabric delivery from mill arrived 3 days late, affecting cut schedule
Recommended actionRebook logistics. Contact factory to confirm revised ship-ready date.
|
|||||
| PO-2026-0862 | Primajaya Textile | Cut complete | 8% | On Track | |
|
Estimated slipNone detected
Checkpoint statusCut complete logged on committed date
Factory reasonNo delay reason logged
Recommended actionNo action needed. Next checkpoint: sew complete in 8 days.
|
|||||
| PO-2026-0877 | Bandung Knit Co. | Fabric in | 44% | At Risk | |
|
Estimated slip2 to 4 days
Checkpoint behindFabric receiving logged 2 days past committed date
Factory reasonCapacity conflict: concurrent order volume delayed fabric inspection scheduling
Recommended actionFlag to factory coordinator. Verify cut date will hold at revised fabric-in timing.
|
|||||
Click any row to see alert detail. Factory names are synthetic sample data only.
How SPUN identifies risk before it becomes a miss
Milestone velocity: days elapsed between checkpoints versus the baseline rate required to meet the scheduled PO completion date. When velocity falls below threshold, delay risk score increases.
- Estimated lag days
- Specific checkpoint that is behind
- Factory-reported reason, if logged
- Remaining lead time before due date
Decide whether to act now or monitor. With enough lead time, a four-day slip is manageable. Without early warning, the same slip surfaces at week six when your logistics window is already gone.
How data gets into SPUN
PO data ingested via email import. Forward your purchase order confirmation and SPUN extracts the structured milestone data.
Available nowUpload a structured CSV with PO fields. Works with any spreadsheet export. No proprietary format required.
Available nowMessage parsing for factories that log checkpoints through chat. Factories send a formatted update; SPUN parses it into a structured checkpoint event.
PlannedDirect webhook for brands running inventory management systems. Sends PO events automatically without manual upload.
PlannedIntegration philosophy: factories do not need to change how they work to participate. SPUN adapts to existing factory communication patterns.
See SPUN with your current order setup as context
We do a 30-minute screenshare with your sourcing setup in mind. Email [email protected] to schedule. Deferred access, not a self-serve signup.