.webp)
List once, live everywhere means a supplier configures a product a single time in FastEditor's Product Hub, with its decoration data, print areas and SKUs, and it becomes available across the Studio Tool, connected resellers, and networks like Promidata and European Sourcing. The data is maintained in one place, so every channel serves the same accurate, personalisable product.
The scaling problem in one line: configure a product once and it is live for every channel; configure it per reseller and you are maintaining the same decoration data in a dozen places, forever. FastEditor already maintains print specifications for 150+ suppliers on the first model.
On this page
First-party figures are drawn from the FastEditor Artwork Automation Benchmark 2026 (13,773 logo uploads).
A supplier adds a new jacket to their range. In the old model, that jacket has to be set up again in every place it will be sold: the supplier's own shop, each reseller's webshop, the data feed for one network, the export for another. Each setup carries the same print areas, the same decoration methods, the same colour rules, re-entered and then maintained separately. Change the print area once and you now have to change it everywhere, or accept that the versions have drifted apart. At FastEditor the whole point of the Product Hub is to make that sentence untrue: the jacket is configured once, and every channel reads from that one configuration.
| Item | Detail |
|---|---|
| Supplier print specs maintained (benchmark) | 150+ suppliers |
| Times a product is configured | Once, in the Product Hub |
| Channels reached from one listing | Studio Tool, connected resellers, Promidata, European Sourcing |
| Uploads needing at least one automated fix (benchmark) | ~85% |
The cost of the old model is not the first setup, it is every setup after it. A promotional product is not just an image and a price; it carries decoration data, the print areas, the methods available on each area, the maximum colours, the file requirements. When that data lives separately in each reseller's shop and each network feed, three things happen. Maintenance multiplies, because a single change has to be repeated across every copy. Versions drift, because in practice not every copy gets updated, so a reseller ends up selling a print area that no longer matches the product. And errors surface downstream, at the worst possible moment, when a customer's uploaded artwork is checked against decoration data that was wrong or stale. Getting the print data standardised across the catalogue is hard enough once; doing it repeatedly, per channel, does not scale.
Listing once means the product is configured a single time, in one place, and that configuration is the source every channel reads from. In FastEditor terms, that place is the Product Hub. A product enters it with its real attributes: SKUs and variants, product images, the print areas and their coordinates, the decoration methods and their limits. From that point the data is maintained centrally. Correct a print area or add a decoration method in the Hub, and every channel that serves the product inherits the change, because none of them holds its own copy. This is the same discipline described in the product data contract for artwork automation: define the product's decoration data once, cleanly, and let everything downstream depend on it.
Once a product is in the Product Hub, "everywhere" is concrete. It becomes available in the Studio Tool for the supplier's own customers to personalise. It is available to connected resellers, who can offer the same personalisable product in their own webshop under their own branding. And it flows into the promotional-industry data networks, resellers arriving through Promidata can be supported directly against the same configuration, and reach into networks such as European Sourcing extends the same product data outward rather than duplicating it. The pattern we see repeatedly is a reseller who already works through Promidata asking for a personalisation tool in their own shop; because the supplier listed the product once, that reseller is served from the same source rather than a fresh setup.
One configuration, many channels
Product Hub, configured once
SKUs, variants, print areas, decoration methods, colour rules, images.
Studio Tool
Supplier's own customers personalise.
Connected resellers
Same product, their branded webshop.
Promidata
Network resellers supported from the same data.
European Sourcing
Reach extended without duplication.
Every channel reads the same configuration. Update the Hub, and the change propagates instead of being re-entered.
| Factor | Per-shop / per-feed setup | List once in Product Hub |
|---|---|---|
| Where decoration data lives | Copied into every channel | One central configuration |
| Making a change | Repeated everywhere, manually | Once, inherited by all channels |
| Version drift | Likely, copies fall out of sync | Eliminated, there is one version |
| New reseller onboarding | Fresh product setup | Served from existing configuration |
| Artwork checks | Only as good as that channel's copy | Against the single, current spec |
List once, live everywhere only works if the "once" is correct, because everything downstream inherits it, including the mistakes. Distributing a product across every channel means distributing its decoration data across every channel, so that data has to be clean before it goes out. In practice that means three things are non-negotiable: the print areas and decoration methods must be accurate for the real product; the SKUs and variants must match so that an order maps to the right item, the failure mode behind a lot of downstream production-file errors; and the colour and file rules must be defined so that artwork automation has something correct to check uploads against. Get those right in the Hub and distribution is an asset. Get them wrong and you have simply scaled the error. The supplier go-live playbook covers getting that first configuration clean.
FastEditor already maintains print specifications for more than 150 suppliers, which is only workable because each product is configured once and reused, not re-entered per reseller. A supplier onboards a product into the Product Hub with its SKUs, images, print areas and decoration methods. From there the same product powers the Studio Tool, is offered by connected resellers under their own branding, and supports resellers arriving through Promidata and reach into European Sourcing, all reading the one configuration. When the supplier updates the product, the update propagates rather than being copied. That is what makes the network storyline real rather than aspirational: the supplier does the work once, and the reach is the platform's job. To start, follow the go-live playbook to get the first products configured cleanly, then see how the Product Hub and distribution fit together.
It means a supplier configures a product a single time, in the Product Hub, with its decoration data, print areas and SKUs, and that one configuration is served to every channel, the Studio Tool, connected resellers, and networks like Promidata and European Sourcing, instead of being set up separately in each.
Resellers who source through Promidata can be supported directly against the same product configuration held in the Product Hub. Rather than building a fresh personalisation setup for that reseller, they are served from the existing, maintained data, which is why a Promidata-connected reseller can add a personalisation tool to their own shop quickly.
You change it once, in the Product Hub, and every channel that serves the product inherits the change, because none of them holds its own copy. That is the core benefit over per-shop setup, where a change has to be repeated everywhere and copies drift out of sync.
Yes, because distribution inherits whatever you configure. If the print areas, SKUs or colour rules are wrong in the Hub, that error is now live in every channel and surfaces when a customer's artwork is checked against it. Clean data first, then distribute.
More articles in For Suppliers.
