Choose the fields the next system actually needs
Start by inspecting the import rules of the receiving PIM, DAM or publishing system. Some destinations use filenames to match products; others rely on a separate mapping. Record requirements for extension, permitted characters, maximum length and case handling before designing a convention.
Use a stable product identifier rather than a marketing title. Product names change, contain punctuation and may be translated. Treat identifiers as text so leading zeroes survive spreadsheet handling. Preserve the original source name in metadata if it is useful for tracing the photograph back to a shoot.
A naming pattern with an accompanying record
Hypothetical pattern: 004281_front_01_en-GB_web-v2.jpg. Here 004281 is the governed product key, front a controlled view, 01 the sequence, en-GB the locale and web-v2 the output profile. This is an example, not a universal import standard. Omit fields a destination does not need and keep the meaning of every field documented.
The corresponding manifest might hold asset_id, product_key, source_name, output_name, master_version, locale and approval_state. Rights and descriptive text usually belong there or in the DAM, rather than making filenames longer.
Resolve collisions before delivery
Two files called “front” may show different pack versions or duplicate exports. Do not solve that by appending “final-final”. Decide whether they are separate assets, revisions of one asset or accidental duplicates, then assign the appropriate key or version.
Check names for collisions after any planned transformation, including lowercasing, replacing spaces or removing punctuation. Two distinct source names can become identical after normalisation. Test with the destination as well: its import process may alter names or treat case differently.
Test one round trip before a bulk rename
Keep a mapping from old name to new name and retain a recoverable copy of the sources. Send a representative set through the real receiving workflow, then inspect the product association, image order and returned names. Include multiple views, variants and a product key with leading zeroes.
Finally reconcile the delivered directory with the manifest: every expected output should exist, every output name should be unique, and unexpected extras should be explained. A naming convention is valuable when it prevents a wrong product association, not merely when the folder looks tidy.
