Picture of Understanding Storefront-Based Hotfolder Configuration

Understanding Storefront-Based Hotfolder Configuration

The Storefront-Based Hotfolder mode offers a more targeted way to route order outputs by limiting hotfolder matching to the active storefront, rather than relying on a single shared set of hotfolders for the entire platform. This option is controlled by a new platform-level setting, which defaults to Legacy (shared) mode for existing installations, and to Storefront-Based mode for new platforms with no orders. By isolating hotfolders per storefront, each brand or storefront can maintain its own dedicated file workflows and fulfillments, while still preserving the traditional approach where necessary.

Tutorial Video Transcript

A transcript of our tutorial video, ensuring you can find exactly what you need, when you need it.

You can search this page to find the relevant time-stamp in the video. Also, this text can be used as part of the tutorial search feature.

0:00
This tutorial looks at understanding storefront-based hot folder configuration. The hot folder mapping feature allows you to automatically copy, order output files to one or more hot folders.
0:13
Traditionally, the legacy approach, hot folder folders were shared across all storefronts, meaning any storefront could match against any active hot folder.
0:23
However, to accommodate scenarios where storefronts require more autonomy and isolated fulfillment workflows, we have introduced a storefront-based mode. So, two things to understand here.
0:35
In legacy mode, which we consider to be shared, hot folders are available platform-wide, matching orders from any storefront. In the storefront-based mode, hot folders are filtered exclusively by current orders.
0:48
Current storefront, ensuring the order's only match hot folders belonging to that storefront. Now, if you need any more information on hot folders and configuring hot folders in general, you can find this elsewhere on the Infigo Academy.
1:04
So we'll start off with the new platform level setting, which is shared versus storefront. The first thing you need to make sure is what you've done is log in as your platform administrator, because you need to get to the platform level of your entire system.
1:20
Click on switch storefront, and navigate to the platform level. Once here, navigate to- bring locations and hot folders in your admin search menu.
1:39
And then you want to go across to the settings tab. Based on your requirements, activate or deactivate the enable hot folders per store for an option.
1:51
And make sure you click- safe. This determines where the hot folders are shared across the entire platform, again as a legacy mode, or restricted to the current store front, which is the store front base mode.
2:05
Just to reiterate the default behaviour, for any existing platforms, so if you've been an infigo customer for a while, with at least one order place, the default is the legacy or shared mode.
2:17
For any brand new infigo customers, so you've got a brand new creative platform, then it will default to the store front.
2:24

It's not mode, but you can change it at any time.

Incomplete
Step by Step Guide

Overview

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.


2. Key Settings

    • 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]

      • Activate or deactivate the ":" setting.
      • 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

    •  

      • Hotfolder mapping exists to direct artwork to certain hot folders based on specified conditions. You can learn more about this feature here.
      • 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.


3. Use Cases

  1. 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.

  2. 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.

  3. 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.

  4. 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.


4. Additional Considerations and Best Practices

  • 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.

Alternate Search Terms

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