Filenames should help systems identify an asset without carrying every business meaning. A stable product key, view code, sequence and locale are usually more durable than a long human product name.
Use SKU or another governed product key, then add controlled view and variant codes. Avoid values that change when merchandising renames the product.
Channel, locale, rights, approval and descriptive names may belong in a manifest, PIM or DAM fields. Filenames remain short enough for transfer and integration safety.
Use output-profile and version data where a destination needs traceability. Do not create final-final-2 filenames that require a person to guess which file was approved.
Usually not if titles change often; keep them in metadata.
Yes. Store source name separately while generating a controlled delivery name.
It lets downstream systems verify expected files and important output attributes.
Rupato keeps uploads, specifications, tasks, review and delivery attached to the same production record.
Start an order ↗