A Shirt Lookbook File-Naming System That Keeps Sizes and Edits Separate

A shirt lookbook becomes difficult to review when every file is named final, final-new or final-two. The problem is not cosmetic. A photograph of one size can be mistaken for another, a generated edit can replace its real reference and an older export can reappear in a new article. A simple naming system should identify the garment, view and revision without pretending that the filename contains every product fact.

Choose the information that belongs in a name

Start with a stable product or internal asset identifier, followed by the view and revision. Add the photographed size only when it has been confirmed. Use a neutral placeholder such as size-unconfirmed when necessary, or keep the field in a separate record. A guessed size in a filename quickly becomes a false fact when someone later writes a caption from the folder.

Use a short, readable grammar

For example, a hypothetical naming pattern could be ITEM-front-sizeM-source-01, ITEM-front-sizeM-edit-02 and ITEM-front-sizeM-article-03. These are illustrative labels, not actual TryBuy product records. The source label identifies real reference material, edit identifies a working version and article identifies an approved placement. Keep the original extension and use the same separator throughout so that the files sort predictably.

Keep a tiny revision ledger

The filename cannot explain why a change was made. Maintain a short table with file, source reference, requested change and approval status. For revision two, the note might read: background simplified; collar and print checked; cuff still under review. If revision three corrects the cuff, record that separately. This stops a reviewer from assuming that a newer number means every part of the image was approved.

Use AI to organise, not invent

Create a naming and revision ledger for these shirt image files. Use only the product identifiers, photographed sizes and view labels provided. Mark missing fields unconfirmed. Separate real source photographs, generated working edits and approved exports. Do not infer a size from the model's appearance or merge different products because their colours are similar. Show any naming conflict for manual review.

Walk through a common mix-up

Suppose two shirts share a similar cream base and the folder contains front-final.jpg for each. Rename them using their actual identifiers before editing. Then establish which file is an original photograph and which is a derivative. If that history cannot be recovered, do not declare either the authoritative reference. Return to the original capture or product record and rebuild the relationship. The naming exercise should expose uncertainty rather than hide it.

Keep output placement separate from garment identity. The same approved image may need an article export and a card export, but those are different files with different review requirements. Do not overwrite the source when resizing. Similarly, keep a supplied measurement sheet or product description linked in the ledger rather than squeezing changing specifications into a long filename.

Before handing off the folder, ask another person to locate the untouched source and the current approved export without opening the chat where they were discussed. If they can do that and explain what remains unconfirmed, the system is working. The best naming convention is one the next collaborator can follow without a private explanation.

Keep the convention simple enough to use while working quickly. If collaborators repeatedly omit a field, decide whether it belongs in the ledger instead. Consistent product identity and source status matter more than a complicated filename containing every possible attribute.

For related preparation, use 30 AI Shirt Photography Prompts for Men’s Fashion Ecommerce to frame the wider task, then consult How to Read Shirt Product Photos: ChatGPT Prompts when checking the specific garment details discussed here.