How Do I Manage the Right Print File for Every Design on Every Print on Demand Product?

A folder called 'FINAL final'

You have a few hundred designs. Each one sells on T-shirts, hoodies, mugs, tote bags and posters. The T-shirt needs a front print file at one size, the hoodie a slightly different one, the mug a wrap-around file at a different ratio, the poster several sizes. Some designs have a light version for dark garments. Each file lives somewhere in a folder tree that made sense two years ago.

When you fix a typo in a design, you update the T-shirt file and forget the mug. A customer orders the mug and gets the typo. When you add a new product type, you spend a weekend exporting files and uploading them to the print partner one at a time.

One design is really many files

Print on demand sells the idea of one design on many products. Behind it, each product needs its own file, and the print partner does not know that they are related.

• Each product and print area has its own size, resolution and safe zone.
• Dark and light garments often need different versions of the same design.
• The partner's product template holds a copy of the file, so edits to your master do not reach it.
• File names do not say which design version or product they belong to.
• Different partners need different specifications for the same product type.

So there is no single place that answers 'which file prints when someone orders this design on this product?'

What scattered files cost

Outdated files print outdated designs. Files at the wrong size print too small, too large or off-centre, and the partner will usually say the print matched the file you supplied. Adding a product type or switching partner means redoing work for every design. The owner, usually the designer too, spends time exporting and uploading rather than designing.

It also makes it hard to know what you have. When a design sells well on T-shirts, you cannot quickly tell whether it is ready for mugs.

The print file library we build

1. Each design has a record: its master artwork, version and the products it is meant for.
2. Print files are stored against the design, product type and placement, such as front, back, sleeve or wrap.
3. Every file is checked on upload against the specification for that product and partner: pixel size, resolution, colour mode and transparency, with failures listed.
4. Where a product only needs a resized or repositioned version, a file can be generated from the master using rules you set, then checked the same way.
5. The library pushes the correct file to each product at your print partners, such as Printful, Printify or Gelato, through their APIs where available.
6. When a design is revised, every file derived from it is flagged as out of date until replaced, and the product listings using it are listed.

The specifications come from your print partners. The library applies them; artistic decisions, like placement and dark garment versions, stay with you.

Designs that are ready everywhere

When you finish a design, you upload the master and any product-specific versions once. The library shows which products are covered and which still need a file. When you fix a typo, every product using that design is flagged until its file is updated. A new product type starts with a list of which designs already have suitable files and which need work.

The folder tree stops mattering, because the library knows where everything is.

Is your file setup like this?

• Print files are named final, final-2 and final-mug.
• A design fix has reached some products and not others.
• Prints have come out the wrong size because of the file.
• Adding a new product type means re-exporting every design.
• You cannot quickly see which designs have files for which products.