The Hotfolder Mapping feature allows you to automatically copy order output files to one or more “hotfolders.” Traditionally (the Legacy approach), hotfolders were “shared” across all storefronts, meaning any storefront could match against any active hotfolder. However, to accommodate scenarios where storefronts require more autonomy and isolated fulfillment workflows, we have introduced a Storefront-Based mode.
In Legacy mode (Shared), hotfolders are available platform-wide, matching orders from any storefront.
In the Storefront-Based mode, hotfolders are filtered exclusively by the current storefront, ensuring that orders only match hotfolders belonging to that storefront.
This new mode is controlled by a platform-level setting (explained below). The default behavior for platforms that already have orders (i.e., existing “live” platforms) remains Legacy. The default for brand-new platforms (i.e., no orders placed yet) is Storefront-Based.
New Platform-Level Setting (Shared vs. Storefront)
Location: Log in as a Platform Administrator, and click "Switch Storefront" to activate the Platform level
Then navigate to Admin → Configuration→ Print Locations and Hot Folders > Settings [Tab]
Purpose: Determines whether hotfolders are shared across the entire platform (Legacy mode) or restricted to the current storefront (Storefront-Based mode).
Default Behavior:
Existing platforms (with at least one order placed) default to Legacy (shared) mode.
Newly created platforms (no orders yet) default to Storefront-Based mode.
Hotfolder Matching Logic
Legacy (Shared) mode: All hotfolders in the platform are eligible for best-match logic.
Storefront-Based mode: Only hotfolders belonging to the active storefront are considered for best-match.
Maintain Current Functionality
If your existing setup relies on hotfolders shared across storefronts, simply keep the Legacy mode active. This ensures no disruption to your current workflows or background tasks.
Per-Storefront Isolation
If you want each storefront to have its own dedicated hotfolders, switch to Storefront-Based mode at the platform level. This is beneficial when storefronts serve different customers, products, or fulfillment sites.
Newly Launched Platforms
For a brand-new platform, the default Storefront-Based mode is ideal if you are setting up separate storefronts for unique product sets or entirely different brands. Each storefront can maintain hotfolders without conflicting with others.
Separate or Merge Production Workflows
Companies that share certain finishing equipment across multiple storefronts might prefer Legacy. Meanwhile, those with more specialized finishing or shipping workflows per store can avoid confusion by enabling Storefront-Based mode.
Existing Orders: Once a platform has switched from Legacy to Storefront-Based mode, older orders remain unaffected. However, new or reprocessed orders will use the newly selected mode.
SPO and Strict Matching: While the best-match logic typically restricts or expands the set of potential hotfolders, some storefront workflows (e.g., SPO) may have strict matching rules. If you rely on strict rules, ensure you have configured your storefront-level hotfolders accordingly.
Performance: Having many hotfolders at the storefront level can sometimes help performance in large multi-storefront setups by reducing the scope of the “best match” search.
hot folder setup, storefront hot folder settings, shared vs storefront folders, automate order file delivery, separate hot folders by storefront, legacy hot folder mode, restrict folders by store, hot folder mapping options, storefront-specific fulfillment, enable per-store hot folders