Embroidery business software from digitizing to dispatch
Blanks, stitch count, setup and carriage as separate costed lines, the digitized logo approved against the line, and the wholesaler PO raised from the job.
The machine only earns while the approval is in
An embroidery job waits on two things: the blanks arriving and the digitized logo being approved. Both are outside your building, and both are usually chased by email.
- Blanks, stitch count and setup price as separate costed lines
- Wholesaler POs are raised from the job and acknowledged in Zigaflow
- Logo approval is an eForm on the line and can be chased automatically
- The approved file stays on the record for the next reorder
How it runs in Zigaflow
- Inquiry or reorderThe garment, the logo and the quantity land on one record.
- Quote the partsBlanks, stitches, setup and carriage price as separate costed lines.
- Approve the digitizingThe stitch-out proof is approved against the line before blanks are ordered.
- Run and dispatchThe job moves through production, then delivery note and invoice.
More about Zigaflow for Embroidery Businesses
Zigaflow raises the wholesaler purchase order from the job lines and lets the supplier acknowledge it and add tracking, while the artwork approval runs as an eForm against the line and can be chased automatically, so the head is never idle waiting for a reply nobody is responsible for.
The problems we solve
Reorders are retyped from an email
"Same again, twelve more polos" arrives in an inbox and somebody keys it in and hopes the logo file is the right one.
The account orders from its own store at agreed prices with the approved artwork attached, and the order lands as a job.
Blanks are ordered by hand from three wholesalers
Orders are keyed into supplier websites and reconciled to jobs at month end, by which time a short delivery has already cost a deadline.
Purchase orders go to every supplier on the job at once and the supplier acknowledges and adds tracking in Zigaflow.
Approval stalls the head
The digitized logo goes out in an email, the machine sits idle, and nobody knows whose turn it is.
Approval is requested against the line and chased automatically, and the job moves to production when it is given.