APZmedia Fashion E-com Filename

E-commerce product photography runs on SKUs, not titles. The file that ships to a PDP (product detail page) has to be traceable back to a catalog item by name alone, which is why the convention is brand_sku_colorcode_view_sequence - and why ACNE_AB1234_BLK_FRONT_01 means something to a merchandising team while pretty_dress_final2.png means nothing at all. APZmedia Fashion E-com Filename is the APZmedia Naming Tools node for that pipeline: it assembles the product-photo filename in the exact shape a fashion e-com operation expects.

The fields are brand, sku, colorcode, view, and sequence, each with the pack's standard Include/Exclude toggle, plus the shared delimiter (default _). One output: filename. The example from the README - ACNE_AB1234_BLK_FRONT_01 - is the whole convention in one line: brand, SKU, color code, camera view, and a sequence number so multiple shots of the same SKU/color don't collide. Mechanism is the same as the pack's other naming nodes: include the toggled-on, non-empty fields, join with the delimiter. No auto-padding - if your catalog uses BLK you type BLK, and the README is explicit that numbers and codes are your responsibility.

This is the node for people generating product imagery at volume in ComfyUI - color variants, angle variations, whole lookbook-to-PDP batches. The natural setup: brand and sku are fixed per product, colorcode flips as you change colorway, view cycles through FRONT/BACK/DETAIL, and sequence increments for multiple takes. Drive the varying fields from other nodes (APZmediaCycleInt for sequence, a text list for views) and the whole batch files itself into the catalog convention with zero hand-typing.

The honest distinction from its sibling: this node is fashion e-com - it assumes a catalog with SKUs and color codes. The pack also ships a general APZmedia E-com Filename with product and variant fields instead, for when you're shooting items that don't have a formal SKU/colorcode system yet. Pick based on whether your operation thinks in AB1234_BLK or in PRODUCTNAME_RED-XL. Both share the same skeleton, toggles, and limitations: no sanitization, no formatting opinions, no enforcement of your client's particular code style. If the catalog format is anything but the standard, wrap it with APZmediaDictionaryReplace to translate.

Install

ComfyUI Manager → search "APZmedia Naming Tools". Or:

cd ComfyUI/custom_nodes
git clone https://github.com/APZmedia/ComfyUI-APZmedia-cleanName-from-string
cd ComfyUI-APZmedia-cleanName-from-string
pip install -e .

Restart, find it under APZmedia/Naming. No model downloads, no heavy dependencies - the pack's only extra is unidecode, which this node doesn't even need.