From Catalogue to Live: The Promo Supplier Go-Live Playbook

Most suppliers think of going live as a per-channel chore: add the product to one webshop, then repeat it on the next, and the next. FastEditor inverts that. You configure a product once as an editor configuration in the Product Hub, and it becomes available everywhere FastEditor reaches at the same time. This is a go-live playbook built around one idea: configure once, live across the network.

This guide is for suppliers and distributors who want their range visualisable, proofable, and order-ready across as many channels as possible, with the least repeated work. It covers what going live actually means, what you need in place first, the spec each product needs, the steps to get there, and what changes once you are live.

What going live really means for a supplier

A product is live when a customer can personalise it, see an accurate preview, and place an order that produces a correct production-ready file, without anyone touching the artwork by hand. That requires the product to exist as a proper editor configuration: print areas, decoration methods, colour rules, and the right images per variant. A listing in a catalogue is not the same as a live, orderable, personalisable product.

The old way: relist your catalogue on every channel

The traditional path is to rebuild your product data inside each reseller's webshop, each distributor's system, and each marketplace, one integration at a time. Every channel is a separate project, every update has to be pushed everywhere, and a small spec change means touching many systems. It does not scale, and it is why most supplier catalogues are live in far fewer places than they could be.

The FastEditor model: configure once, live across the network

When you set a product up as an editor configuration in the Product Hub, you do that work one time. From there the same configuration is automatically available across the FastEditor network:

• The Studio Tool: every sales rep and offline reseller can generate an accurate print proof of your product in a meeting, with no design team. Your range becomes something a rep can sell live.
• All connected resellers and distributors: any reseller running FastEditor can switch your products on in their own webshop, in their own brand and checkout, without you building a per-reseller integration.
• The Promidata network: your configured products surface to the resellers working through Promidata, so the personalisation option appears on their product pages.
• The European Sourcing network: your range is included in the supplier-matching batches that put products in front of that network's members.

The effect is a network one. One configuration is not one listing; it is distribution to every channel FastEditor already connects. List once, live everywhere. See the connected suppliers for how this fits together, and for suppliers for the supplier view.

What you need in place before go-live

The network distribution only works if the underlying product is clean, because the same configuration flows to every channel. Three things have to be right first:

• Standardised print data: print areas in millimetres, decoration methods, and colour limits per product. This is the foundation, covered in standardising decoration data across a supplier catalogue.
• Clean artwork handling: customers upload whatever logo they have. FastEditor's own benchmark of 13,773 logo uploads found about 85% are not print-ready on arrival, so the configuration has to assume artwork needs automatic vectorization and correction, not perfect input.
• Reliable SKU matching: the identifier in your feed has to map cleanly to the editor product, or proofs and files attach to the wrong variant across every channel at once.

Get these right and the network works for you. Get them wrong and the same error is distributed everywhere, which is the one real risk of a list-once model. The supplier artwork workflow goes deeper on automating the intake side.

The onboarding spec: what each product needs

Configuring a product means giving FastEditor a defined set of characteristics. You can provide these as JSON schemas (Logo Products, Photo Gifts, Photo Wall Decoration, Photo Book) or, if JSON is not your thing, through a spreadsheet template that captures the minimum required properties. The full field reference lives in the supplier developer docs.

The core required fields fall into a few groups:

• Identity: SKU (your unique identifier), productName, and productDescription. An optional skuGroup links variations of the same product so the editor can switch between them.
• Supplier: supplierName and supplierReference, the code the supplier uses to identify the product (the same as the SKU if you are the supplier).
• Decoration: printMethod (the technique), printColors (1 to 12, or full-colour), and optional printPosition and productColor.
• Production output: outputWidthMM and outputHeightMM for the print PDF, with outputDPI defaulting to 300.
• Editor placement: editorImageURL plus insertX, insertY, insertWidth, and insertHeight (and optional insertAngle) to define exactly where the design sits on the product image.
• Localisation: name_en and name_[language] for translated product names.

Deeper configuration is documented in the developer guides: SKU concepts (baseSku, sku, virtualSku), print methods, masks for non-rectangular print areas, fill lines for drinkware, adding data to the print proof, and 3D models. Getting these fields right per product is what turns a catalogue entry into a true editor configuration, the thing the whole network reads from.

The go-live steps

1. Connect your product data: feed your catalogue into the Product Hub, directly or through a distributor.
2. Configure each product: define print areas, decoration methods, colour rules, and variant images so each item is a true editor configuration, using the JSON schema or the spreadsheet template.
3. Validate: confirm SKU matching and that previews and proofs render correctly before anything is switched on.
4. Go live in the Product Hub: the configuration becomes the single source the whole network reads from.
5. Distribute: the product is automatically available to the Studio Tool, connected resellers and distributors, and the Promidata and European Sourcing networks.

What changes once you are live

Going live across the network changes the supplier's position. Your range is visualisable wherever FastEditor reaches, so resellers can show and sell it without asking you for mockups. Sales reps can proof it live in front of a client. New resellers who join the network inherit your products without a new project. And because every channel reads the same configuration, an update you make once propagates everywhere, instead of being re-keyed per system. The work moves from repeated per-channel listing to a single, maintained source of truth.

Frequently asked questions

What does it mean to get a product live in FastEditor?

It means the product exists as an editor configuration with print areas, decoration methods, colour rules, and variant images, so a customer can personalise it, see an accurate proof, and order a production-ready file automatically.

How do I provide my product data?

As JSON schemas (Logo Products, Photo Gifts, Photo Wall Decoration, Photo Book) or through a spreadsheet template for the minimum required fields. The full reference is in the supplier developer documentation at developers.fasteditor.com/supplier.

Do I have to integrate with each reseller separately?

No. Once a product is configured in the Product Hub it is available across the FastEditor network, including connected resellers and distributors, the Studio Tool, and the Promidata and European Sourcing networks, without a per-reseller build.

What is the difference between listing a product and getting it live?

A listing is a catalogue entry. A live product is a configured, personalisable, orderable item that generates a correct production file. Only the second one can be sold across the network.

What slows a supplier go-live down most?

Missing print data and SKU mismatches. Because the same configuration is distributed to every channel, those issues have to be resolved before go-live, not after.

Key takeaways

• Going live is configuring a product once as an editor configuration, not relisting it per channel.
• One configuration in the Product Hub is distributed across the whole FastEditor network: the Studio Tool, connected resellers and distributors, and the Promidata and European Sourcing networks.
• Each product needs a defined spec (identity, supplier, decoration, output PDF, editor placement, translations), provided as JSON or a spreadsheet. See the supplier developer docs.
• Clean print data, automatic artwork handling, and reliable SKU matching have to be right before go-live, because the configuration flows everywhere.