Automated checks are still valuable
Machine metrics, previews, reports, Ink/Stitch marker checks, and packet manifests make the sewout review more controlled.
Proof boundary
Software-ready is a review state. Sewout-approved is the production gate.
DigitizingFlow uses software checks to decide when a generated embroidery file is ready for operator review, but it does not treat that as production approval. A production claim needs physical sewout evidence tied to the same design and artifacts.
Direct answer
Direct answer
Software-ready means the file passed automated checks and can move to sewout review. Sewout-approved means a stitched sample has been reviewed and accepted for production.
Boundary
Why this matters
Fabric, stabilizer, thread, hooping, and machine behavior can change the result. Software evidence narrows risk; it does not replace stitching the sample.
Evidence table
Status comparison
The product model keeps status language precise so operators and customers do not confuse an export with approval.
| Status | Meaning | Allowed claim |
|---|---|---|
| queued | The run is waiting for worker execution or retry. | No generated-file claim yet. |
| manual_review_required | The system found blockers or uncertainty that need operator attention. | Do not present the result as ready. |
| software_ready_pending_sewout | Software evidence passed and artifacts can be reviewed/downloaded. | Ready for sewout review, not production-approved. |
| sewout_approved | Physical stitch evidence has been accepted for the exact design. | Production claim can be allowed. |
The sample decides production readiness
A stitched sample catches material and machine behavior that software cannot fully prove.
The trail should be inspectable
A trustworthy workflow keeps source files, generated artifacts, hashes, status changes, notes, and approvals connected.
Questions
What this page can honestly claim
Why not call a clean PES or DST export production-ready?
A clean export can still stitch poorly on the target fabric or setup. Production approval requires physical evidence.
Can operators download software-ready files?
Yes. Downloads are allowed while the UI and packet language continue to show that physical sewout is pending.
Next step
Move from claim to reviewable evidence.
Queue artwork, inspect generated evidence, and keep physical sewout approval separate from software readiness.