Catalog standard as a file
Side, margin, background, alignment by category, profile, format and name, with the date and source of each store's requirement.
Deliverable: versioned padrao_catalogo.jsonOcto for catalog and e-commerce retouching in Photoshop
Twelve hundred photos, one square, one margin, one name per SKU. The one who approves the photo is you.
Cutting out, adding a background, fitting with a margin and saving with the SKU name is the same operation repeated on different images. Octo writes the catalog standard as a file, the script that standardizes inside Photoshop or outside it, and the check that compares the folder with the spreadsheet. Artistic retouching, the difficult pieces and approval stay with people.
Resize and canvas in UXPsince 23.0resizeImage, resizeCanvas, trim, crop
Cutout paths4action, UXP script, Photoshop API, ImageMagick
Costliest findingsha256the same photo for two product colors
Sources11listed at the end of the page
01
What Octo does with your product photos.
Six possible deliverables, drawn from the research. None of them saves over the original, all of them check the file by content, and all of them go to review by whoever answers for the catalog.
Cutout with a mask
Select Subject becomes a layer mask, not deleted pixels; difficult pieces go out as PSD for the retoucher.
Deliverable: para-retoque folder with the masksMargin measured on the product
The product's bounding box is measured and fitted into the usable area; no centering the image with an offset shadow.
Deliverable: padronizar_catalogo.psjsNames by SKU
A dry run first, a copy afterward, the source → target map saved. A target that already exists becomes an open item.
Deliverable: renomear_por_sku.py and mapa_nomes.csvCheck against the spreadsheet
Missing, extra, size, edge color, margin, profile, file weight and the same photo on two SKUs.
Deliverable: conferencia.csv and a manifest with sha256Approval sheet
Thumbnails with the SKU underneath, grouped by model, to see scale and color placement at a glance.
Deliverable: sheet of open items and of the batch
02
Eight arms, a checked catalog.
The same Octo cycle, applied to product photos. Each arm has a narrow role; the ones who retouch, approve the image and answer for the product description are people.
-
Discovery
Surveys the workflow
Who shoots, who retouches, who uploads; volume per session; stores and requirements; Photoshop version.
-
Data
Writes the standard and spreadsheet
Catalog standard with date and source, a SKU spreadsheet with views and difficult pieces.
-
Security
Protects the original and the person
Original never overwritten, photos with people flagged (LGPD, Brazil's data protection law), nothing sent to an external service without assessment.
-
Architecture
Chooses the path
Action, UXP script, Photoshop API or ImageMagick, by volume and by the workstation available.
-
Development
Writes the script and the check
Standardization with a measured margin, renaming with a dry run, and the check, with the source of each rule noted.
-
Review
Checks by the file
Size, edges, margin, profile and sha256. "There are 1,200 files" is not a check.
-
Release
Prepares the delivery folder
Only what was approved goes to the store folder.
-
Documentation
Records what applies to your environment
Each store's standard with date and source, the cutout descriptor version, who approved each batch.
Octo does not save over the original, does not upscale a small photo to make it fit and does not upload images to the store without approval.
03
Each situation, its own path.
The criteria Octo uses to choose, with the limit of each path.
| Situation | Path | Note |
|---|---|---|
| A few photos a week | Action and Batch in Photoshop | Action recorded on a representative photo |
| Hundreds of photos, workstation available | UXP script (.psjs) | Cutout descriptor checked on the installed version |
| Thousands of photos, no workstation | Photoshop API, /v2/remove-background | Firefly Services contract |
| Photos already cut out | ImageMagick | -trim, -resize, -extent |
| Glass, hair, fringe, jewelry | Mask and retoucher | No automatic cutout solves it alone |
| Rename by SKU | Python, standard library only | Dry run first; nothing overwritten |
| Check the folder | Python and ImageMagick to measure | Screening; approval is human |
| New store standard | Reprocess from the masks | Never from the final images |
04
From fitting by hand to a checked catalog.
Three steps. Each one only makes sense after the previous one has shown results on your team.
A proposal, not a promise
Check
Octo checks the folder that already exists, without changing how you retouch.
- Missing and extra against the spreadsheet
- Margin and background measured
- The same photo on two SKUs
Standard and script
A written standard, a standardization script and renaming by SKU.
- Margin measured on the product
- Difficult pieces set aside
- Original intact
Scale
High volume through the Photoshop API or ImageMagick, with the same check at the end.
- Reprocess from the masks
- Versioned standard per store
- Approval sheet per model
05
Confirmed by a source.
Every point below has a source published by the vendor, by the project or by the responsible agency. The sources are in the next section.
5
points with a published source, each with its reference shown alongside.
- ConfirmedResize and canvas by script
resizeImage,resizeCanvas,trim,cropandconvertProfilesince 23.0; changing a document requiresexecuteAsModal.Source: developer.adobe.com, UXP, Document and executeAsModal- ConfirmedCloud cutout with four options
cutoutormaskmode,trim,backgroundColorandcolorDecontamination.Source: developer.adobe.com, Photoshop API, Remove background- ConfirmedCurrent desktop version
- 27.11, from September 2026; the 27 line runs on macOS 26, 15 or 14.Source: helpx.adobe.com, What's new (Oct 5, 2026) and technical requirements (Sep 9, 2026)
- ConfirmedSelect Subject by script
{"_obj": "autoCutout", "sampleAllLayers": false}is the first step of the official Product Crop ActionJSON; Octo still checks the descriptor on the client's version.Source: developer.adobe.com, Photoshop API v2, Product Crop- ConfirmedMargin in v2 Product Crop
- Runs on
/v2/execute-actionswith the published ActionJSON; the margin is thecanvasSizestep, 10 relative px, centered by default, and it can be changed.Source: developer.adobe.com, Photoshop API v2, Product Crop
06
What Octo does, and what stays with you.
Octo prepares everything, but it does not sign. The document of record stays with whoever is accountable for it.
Octo prepares
Surveys, calculates, organizes and produces the documents: processed files, proofs, reports and spreadsheets.
Deliverable: material ready to checkYour team checks
The client or the art director checks what Octo delivered before approving. If something doesn't add up, it goes back to Octo with the correction.
Step: checked by the person who approvesWho approves
Octo does not approve the artwork. Artwork carries no legal signature: approval of the artwork and the proof stays with the client or the art director.
Approval: client or art director
07
Sources.
UXP and Photoshop API documentation on developer.adobe.com, Photoshop help pages on helpx.adobe.com, ImageMagick options and Adobe community reports, consulted on Oct 31, 2026.
- UXP, Document classresizeImage, resizeCanvas, crop
- UXP, Selection classMethods since 25.0
- UXP, executeAsModalModal state
- UXP, scriptsSingle file, dialogs only
- Photoshop API, Remove backgroundModes and parameters
- Photoshop API, Product CropFraming by product
- ImageMagick, optionsVersion 7.1.2-34
- Photoshop API v2, Product CropActionJSON with autoCutout and canvasSize
- Photoshop, What's new27.11, updated on Oct 5, 2026
- Photoshop, technical requirementsLine 27, updated on Sep 9, 2026
- Photoshop, Image ProcessorResize to Fit, updated on Feb 23, 2026
Your catalog, with measured margins and a checked folder.
The assessment starts by checking a folder that is already live or ready to go up. You get what is missing, what is extra, what is off-standard and the questions only your team can answer, and you decide with that in hand.