Show the Logo on the Product, Before the Artwork Exists.

No. Automatic visualisation needs four things: the supplier connected to the PromoTron network, the product identified by supplier and supplier product code, the product templated for the visual engine, and the chosen print effect available for that product. On products that are not supported the controls hide themselves, so an unsupported item never shows a broken preview. Products or suppliers outside the network can be integrated and templated as a paid service.

They are visual indications, not physical proofs. Engraving, embossing and embroidery are simulated from the available product and print data, and how the finished item looks still depends on the material, the supplier and the production process. Treat a virtual sample as a sales aid that makes the choice concrete, not as a production sample.

No. What changes is where your graphics team starts: instead of a description and a chased-up email, they open the customer's original file, the flat artwork, the virtual sample and the print-area and artwork dimensions. Preparing the final production data is still work for people who know printing.

Approximately four to six hours for a basic implementation, and typically two to three days for an advanced one that connects the cart, an API or an ERP. Both are indicative rather than a commitment, and a basic implementation needs development on your side. If you would rather skip that step, TronLogo is already integrated in every TronShop package.

Not in the browser-based setup. Uploaded logos and saved motives stay available when the customer returns from the same computer and browser, so a first upload costs a visitor nothing but the file. Where you need logos tied to a customer record instead, the API and your own system can manage them.

Yes. The dialogue and button colours, your company logo and contacts, the PDF header and footer, your own process or marketing text, an optional watermark and the sender name are all configured in the administration portal, alongside the allowed domains and the supplier assignment.

Through a JavaScript event layer and a REST API. The events report what the customer does as it happens — a logo uploaded, a motive chosen, a visualisation created — so a saved motive can be attached to a cart or an order. JavaScript can also activate a particular logo, choose a motive for a product, or override a colour variant or a print effect. The API opens the DTP resources: the PDF visualisation, the flat artwork, the product virtual sample, the logo previews and the original uploaded files. Server webhooks push the same events to your systems, carrying the customer, product, supplier and resource identifiers.

Yes, through the Visualisation API. It generates a virtual sample for a chosen product and logo, and takes a known customer's logo into TronLogo, which is what makes personalised emails and campaigns possible. It is optional, charged separately and quota-based, so it is agreed with us rather than simply switched on.

For both, as source code. They cover the API key, the product identifiers, the placement of the controls and attaching a motive to an order. They were written by external developers and are supplied as-is: PromoTron does not provide technical support for the plugin or for the third-party platform itself, so treat them as a starting point your developer owns rather than a supported product.