DIGITIZING & FILE PREPARATION
File Preparation Checklist Before Loading a Design
Quick Answer
Use the approved file version. Check finished size, colors, stitch data, start point, orientation and field fit. Confirm the controller's supported export and transfer method, then test before releasing production.
Version and approval status
Check that the file is the version approved for the order. Keep a clear link to the artwork and sample so an older file is not loaded by mistake.
Record dimensions, stitch types, small details, thread, material, holding method and the approval sample. Use this specification to judge later file and production changes.
- Name the exact model and revision
- Record what changed and what remains compatible
- Link the update to the current document or support route
Dimensions and field fit
Check finished dimensions and orientation against the usable hoop area. Confirm product support and clearance for the full design.
Measure the largest recurring design and the most difficult product access separately. A large flat field may help with panels or jacket backs, but it does not prove suitable cap or shaped product access. Request a setup and sample using the intended holding method.
- Measure the recurring design and finished placement
- Identify the exact hoop, frame or support method
- Check product access and clearance with a representative setup
Stitch and color review
Review colors, sewing order, stitch load, trims and jumps. Compare exported data with the approved file and any sample changes.
Test the intended material at the finished design size. Inspect coverage, edges, registration, distortion, small details, thread condition and the reverse. Keep the approved source file, exported production file and revision record together so later edits do not replace the tested version unnoticed.
- Describe the recurring work
- Confirm the relevant model and configuration
- Record the condition that still needs verification
Start point and orientation
Confirm the intended start point, orientation and placement reference. Use the model's documented checking method rather than guessing from the screen alone.
Confirm the documented method for checking the start point, orientation and design position. Check the loaded file against the approved job and holding setup. Resolve an uncertain position before sewing the sample.
- Describe the recurring work
- Confirm the relevant model and configuration
- Record the condition that still needs verification
Confirm the Export Format
Export in a format supported by the exact controller. Confirm whether DSB or DST is appropriate for that version and review the exported file.
Confirm file formats, transfer methods and operating instructions for the exact controller and software revision. Do not treat DSB, DST, USB or WiFi as proof of compatibility with every configuration. Confirm required interface languages separately from the language or scope of human support.
- Record the controller and software revision
- Keep the approved source file and exported production file
- Verify the screen result before releasing the job
Transfer, sample and release
Load the approved version through a supported transfer method. Check the screen result and sew a sample before releasing the job.
Confirm file formats, transfer methods and operating instructions for the exact controller and software revision. Do not treat DSB, DST, USB or WiFi as proof of compatibility with every configuration. Confirm required interface languages separately from the language or scope of human support.
- Record the controller and software revision
- Keep the approved source file and exported production file
- Verify the screen result before releasing the job
Frequently asked questions
Which file and transfer details should I confirm?
Check the accepted file type and transfer steps in the matching controller manual. Confirm dimensions, stitch count, colors, trims, orientation and field fit before loading the approved version.
What should I share with FUJA?
Keep the source and exported files with the model, controller version, material and frame details. Record the approved filename and sample result so later changes are easy to trace.