APZmedia E-com Filename

Not every e-commerce shoot has a catalog code to lean on. When you're generating product imagery for a brand that's still naming products by hand - a t-shirt is "The Oversized Tee," not AB1234 - the filename convention has to be readable to a human first: brand_product_variant_view_sequence. APZmedia E-com Filename is the APZmedia Naming Tools node for that world: the general-purpose sibling of the fashion e-com node, built around descriptive fields instead of catalog codes.

The fields are brand, product, variant, view, and sequence - each with the pack's standard Include/Exclude dropdown - plus the shared delimiter (default _). One output: filename. The README's example, BRAND_PRODUCTNAME_RED-XL_FRONT_01, shows the logic: brand, product name, variant (color and size in one field), camera view, and a sequence number. Mechanism is identical to every naming node in this pack: join the toggled-on, non-empty fields with the delimiter and hand you a STRING. Padding, version codes, and formatting are yours to manage - this node won't reorder or reformat a thing.

The key difference from the fashion-specific sibling is in that variant field. Fashion e-com assumes a formal SKU plus color code (AB1234_BLK); this node assumes a descriptive variant string (RED-XL) because that's what you have before a formal system exists. Which one you reach for depends entirely on your operation: if there's a catalog code, use APZmediaFashionEcomFilename; if the product is still known by name, this is the one. The two share the same skeleton and the same honest limits - no sanitization, no opinions about your naming scheme, no auto-formatting.

Where it earns its keep: batch product generation for a store that hasn't formalized SKUs yet, or for mockups/concept work where the deliverable is "front, back, detail of the red XL" rather than "asset for SKU AB1234." Fix brand and product, flip variant and view between runs, drive sequence from a counter, and every output lands with a filename your client's catalog team can actually read. Wrap it with APZmedia Clean File Name Node if any of your free-text fields might contain characters a filesystem objects to - the - in RED-XL is fine, but a stray / in a product name would not be.

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 use.