This article explains how to assign KSF or print configurations to apparel product models so they resolve automatically at print time. The profiles are stored against your machines in Machine Park; this article covers the second stage of the flow — telling the system which configuration to use for which products and variants.
Overview
Print configurations are assigned at the product-model level using a set of conditions. A condition can match an attribute combination (e.g. colour = dark + print location = back) or target a single specific variant. The same configuration then resolves for any customer product built on that model, and also for job-based apparel workflows that don't go through a customer product.
Why this changed (May 2026). Until May 2026, KSF was assigned per customer product. That broke whenever the manufacturer UID was disconnected from a customer product, and didn't work at all for job-based workflows. Moving the linkage to model + conditions fixes both cases.
Before you start
Your print configurations must already exist in Machine Park → [Select the machine] → Configurations tab. If they don't, see Create and manage KSF print configurations in Machine Park first.
The product model must exist (apparel or otherwise). Both legacy apparel models and the new streamlined apparel model are supported.
Your workflow must use the Get KSF Configuration activity for the configuration to be picked up at runtime.
Step 1 — Open the Print Profiles tab on the product model
Go to Product Models and open the model you want to configure (for example, your apparel model).
Switch to the Print Profiles tab (also called Machine Configurations in some tenants).
Select the machine these rules apply to from the machine picker at the top — for example, Kornit Atlas. Rules are scoped per machine; if you have multiple Kornit machines, configure each independently.
Step 2 — Add a rule
A rule has three parts: the conditions that determine when the rule applies, the configuration to use when it matches, and a priority that resolves conflicts when multiple rules could match.
Click Add rule.
Pick a rule type:
Product-level — applies to every variant of the model. Use this for a default that covers everything not handled by a more specific rule.
Group (attribute combination) — applies when a set of attributes matches. For example, all variants where Colour = dark and Print location = back. Select one or more values per attribute; multiple values are OR-matched within a rule.
Exact match (variant) — applies to one specific variant. Provide values for every variant option (e.g. Colour = Navy + Size = XL + Fabric = Cotton).
Pick the configuration from the list — these come from Machine Park.
Click Save rule. New rules are assigned the highest priority by default.
Step 3 — Order rules by priority
When an order arrives, the system evaluates rules from highest priority to lowest and applies the first one that matches. A common stacking pattern is:
Priority 3 (highest): Exact-match overrides — for the one Gildan SKU that needs a specific configuration.
Priority 2: Group rules — colour + print location combinations.
Priority 1 (lowest): Product-level fallback — always matches if nothing else does.
Always include a product-level fallback. If no rule matches an incoming variant, the workflow will fail with a configuration-missing error.
Step 4 — Override at the customer-product level (optional)
If a single customer needs a different configuration for a product that otherwise follows the model-level rules, you can still set an override on the customer product. Open the customer product, go to its Machine Configuration tab, and add a rule. Customer-product overrides take precedence over model-level rules.
Step 5 — Verify the workflow uses Get KSF Configuration
Make sure your apparel workflow has the Get KSF Configuration activity (it replaces the legacy JavaScript activity that some older workflows still use). At order time, the activity picks up the resolved configuration from Machine Park, substitutes any template variables, and passes the XML to the next step. See the Workflow Builder article on the Get KSF Configuration activity for details.
Editing and removing rules
Edit a rule — click it in the rule list. You can change the configuration assignment, the conditions, the values, or the priority. Changes apply at the next workflow run; in-flight jobs are unaffected.
Remove a rule — click the delete icon at the end of the row. If the rule is the only thing keeping a configuration in use, the system will warn you before deleting.
FAQ
Does this work for the old apparel product model? Yes. Both the new streamlined apparel model and the legacy apparel model are supported, as long as the workflow has the Get KSF Configuration activity.
Can I assign rules from multiple machines to the same model? Yes. Each machine has its own independent set of rules. Switch the machine picker at the top of the Print Profiles tab to manage another machine's rules.
What file formats are supported for configurations? As of May 2026, XML is the only supported format. JSON and other formats are planned.
What happens if no rule matches an incoming variant? The workflow has no configuration to send, and the job fails with a configuration-missing error. Always keep at least one product-level rule as a fallback.
Can the same group rule apply to multiple values of the same attribute? Yes. When creating a Group rule, you can select multiple values for one variant option (e.g. Colour = Navy and Black) in a single rule. This avoids duplicating rules for the same configuration.