PPID & web export

Once a product image is approved in the Iconik review loop

• whether it came from photography or CG - it’s prepped as a PPID image: resized, renamed to the convention, and published to the website. All of this is handled in Photoshop via the Groot Publisher plugin.

The trigger is the ppid_images subitem flipping to Ready to start: Jude or his team (the assignee) is notified automatically. This means the photography or renders (or both) were approved and are ready to be formatted - crop, aspect ratio, file naming - to meet website requirements.

Trigger conditions

• Photography Versions or Renders subitem = Approved.

Prep & Brand Manager review

The first pass produces a JPG for Brand Manager review. Open the approved PSD/PSB for that SKU using the Iconik link - it lives in images/versions/ or images/renders/ relative to /product_images.

1. Open the approved PSD from the versions/ or renders/ folder via the Iconik link.
2. Save Work - navigate to /web_thumbnails and save your PSD/PSB file there.
3. Crop, center, and resize to spec:
   • aspect ratio 1:1
   • 2000×2000 px (optional - the plugin resizes on Publish)
   • 72 dpi (optional - the plugin updates on Publish)
4. Version Up to generate a JPG for Brand Manager review. The image appears in Iconik, a share link is pushed to Monday, and the status is set to BM Review.
5. The reviewer either comments/annotates for revisions or sets the status to Approved.

Publish - Filtered & Unfiltered web images

Once the Brand Manager approves, publish the final web images.

1. Click the approved Iconik link to open the file via the Iconik agent.
2. Click Publish and choose PNG or JPG (this applies only to PPID images).
3. The plugin generates all images based on preset conditions and writes them to:
   • web_thumbnails/_published/ - the final locked PSD/PSB
   • /ppid - exported PPID image (preset conditions)
   • /filtered - exported image for website filter use
   • /unfiltered - images carrying the main thumbnail type code (_T, _H, _V, _S, _C) plus the order token (_1, _2, … _9)
4. Trigger: share links are pushed to Monday and the status flips to Complete.

No duplicates

The graphix-working.wac filespace has a zero-tolerance duplicate policy - never copy-paste or back up files within it, and never rename files manually after upload. Duplicates break Iconik’s auto-versioning. See the automation ecosystem and folder structures.

Naming convention

PPID web images carry type codes and an order number. Iconik tags use the bare letter; filenames use the underscore form.

Code	Filename	Meaning
T	_T	Thumbnail
H	_H	Horizontal
V	_V	Vertical
S	_S	Spec
C	_C	Ceiling

• Order tokens _1 … _9 set website display order; the type code precedes the number (e.g. T 1).
• Codes combine when one image serves multiple roles, e.g. T S 1 = thumbnail + spec, first in order. A thumbnail that’s also the first website image gets the lowest number.
• IMRO is the fixed suffix on published web images (e.g. PD-25518-BKAB_FRONT_IMRO.JPG); /filtered outputs omit it.
• PPID export specs: aspect ratio 1:1, 2000×2000 px, 72 dpi, output JPG/PNG.

Tip

This table is the single source of truth (authored once, shown here and in the naming reference). Edit it in src/partials/ppid-naming-table.mdx.

Final output

Based on Brand Manager approval and Product Manager website tagging:

• Images are renamed according to web-team guidelines (the IMRO suffix marks published files; /filtered outputs omit it).
• Files are saved to the correct locations on LucidLink for downstream website use.
• Share links and status updates are handled automatically by existing automations.