DST file automation
DST file automation is the process of routing ecommerce embroidery orders into production-ready DST output so commercial teams do not keep translating routine jobs by hand.
What DST is used for
DST is one of the most common commercial embroidery exchange formats and is widely associated with Tajima and Barudan-oriented production environments. For ecommerce teams, the operational question is not only what DST is. The question is when the workflow should send an order into a DST path automatically.
Persofy treats DST as a production-routing decision connected to the product, the facility and the handoff model. That is more scalable than making an operator decide the format again on every standard order.
- 2 machine families most commonly associated here are Tajima and Barudan.
- 1 repeatable routing rule is better than ad hoc format choice on every order.
- 8+ supported formats means DST can sit inside a broader mixed-format workflow.
When merchants usually need DST
DST is often the first format to automate when the production path expects an industrial exchange standard, a contract embroidery partner requests DST, or multiple facilities need a broadly compatible commercial output route.
What Persofy controls in a DST workflow
Order-to-DST mapping
Assign DST to the products or production destinations that actually require it.
Validation before handoff
Check that the order and production rules are complete before the DST route is used.
Linked production context
Keep order metadata and handoff instructions attached so DST is not sent as an isolated file with missing context.
Commercial embroidery machines that use DST
DST is the usual default when you need broad industrial machine compatibility across commercial embroidery production.
Tajima
Commercial single-head
TMEZ-SC, TMBR2-SC, SAI
Tajima
Industrial multi-head
TMAR-VC, TFMX-IIC, TMCS-VF
Barudan
Industrial embroidery machines
BEKY and BEXY series
SWF
Commercial embroidery machines
MAS and KX series
ZSK
Industrial embroidery machines
Sprint and Racer series
How the DST workflow runs
-
Step 1
Read the order
Capture personalization and product context from the storefront.
-
Step 2
Apply DST routing rules
Confirm the order belongs in the DST path based on the product and production destination.
-
Step 3
Prepare the handoff package
Generate or route the approved order into the required DST output package.
-
Step 4
Handle only exceptions manually
Keep unusual jobs out of the routine DST queue so standard orders keep moving.
DST questions
What is DST file automation?
DST file automation is the process of routing or generating DST output from ecommerce orders through a repeatable production workflow rather than through manual format decisions.
Which machines typically use DST?
DST is most commonly used in Tajima-oriented and other industrial embroidery environments, including Tajima TMEZ-SC, TMBR2-SC, TMAR-VC, TFMX-IIC and SAI models, plus Barudan-style commercial setups that expect DST stitch data.
When should a merchant prioritize DST first?
A merchant should prioritize DST first when the production team or fulfillment partner already expects DST as the standard commercial handoff format.
Can DST sit inside a mixed-format workflow?
Yes. DST can sit alongside PES, JEF and other outputs as long as the workflow maps each product or destination to the right format automatically.
Which pages should I read next?
See supported formats, embroidery file generation and Shopify embroidery automation for the surrounding workflow detail.
Need DST output handled as part of a real production workflow?
We can scope when DST should be used and how the order should move into that handoff path.
Automate DST output