Item Export

Explanation: CAPP’s Item Export feature supports two configured targets: local disk (operator’s computer or a mounted network share) and PhotoRobot Cloud (which generates a downloadable link with 7-day retention). Direct ERP push and customer FTP are possible via integration / API but are not options inside the standard Item Export window.

Explanation: Cloud export links are valid for 7 days from the moment the export completes. After that the bundle is purged and the link is dead. The operational implication is that delivery confirmation should happen within ~5 days; otherwise re-export to refresh the window.

Explanation: WebP is PhotoRobot’s recommended default — it consistently produces smaller files than JPG at equivalent visual quality, supports transparency like PNG, and is well-supported in modern browsers / e-commerce platforms. JPG remains a safe fallback for legacy downstream systems that don’t yet accept WebP. PNG is too large for typical web delivery; TIFF is reserved for special legacy compatibility cases.

Explanation: The WebP quality range 50–80 is the productive band. Above 80 you get diminishing visual returns with rapidly growing file size; below 50 quality degrades sharply with only marginal size savings. JPG’s productive band is different — typically 80–95 for high quality, 70–80 for medium.

Explanation: The custom formatting syntax is ${variable:length:start}. ${order:4:1} means order index, 4 digits wide, starting from 1 → 0001, 0002, …. ${order:4} alone defaults the start; ${order:1:4} would be 1-digit wide starting from 4 (which doesn’t pad). ${turnIndex:4:0} uses turnIndex not order — different semantics.

Explanation: A Duplicate Path Error means two output configurations would write to the same target filename. The fix is to add a disambiguating variable — ${order}, ${label}, or ${rowIndex} — to at least one template so the paths are unique. The manual specifically calls out adding ${order} to handle multi-row spins where row/turn angle combinations may otherwise collide.

Explanation: CAPP’s item list displays 25 items per page by default. Ticking the page-level checkbox selects only those 25. To export the entire project the operator must explicitly click “Select all entries” — the prompt next to the count indicator. This is one of the most common operator mistakes. There is no 25-item hard limit on exports.

Explanation: The flag changes each successfully-exported item’s CAPP status to Exported, which has two effects: items disappear from “not yet finished” views (cleaner operator dashboards) and subsequent re-exports filtered by status skip already-exported items (no accidental double uploads). Uncheck the flag for preview exports or multi-target exports where you don’t yet want items marked done.

Explanation: DPI in the export window only changes a metadata tag, not the pixel count. The image’s actual resolution is determined by capture settings + the “Original / Resized” selection, not by DPI. DPI defaults to 72 and the manual recommends leaving it there unless a specific downstream demands a DPI tag for compliance.

Explanation: The right answer is per-customer template configuration. Each downstream consumer has its own format requirements; the studio’s template library should accommodate them by name (e.g., customer-erp-jpg-q85). Telling the customer to upgrade is rarely viable; ignoring their spec produces rejected uploads; switching everyone to PNG inflates file sizes for customers who don’t need it. The point of the template library is exactly this — easy per-downstream variation without operator improvisation.

Explanation: Cloud export downloads are gated by the PhotoRobot File Manager app (Mac / Windows installer). The landing page from the email link prompts customers to download File Manager if they haven’t already. This is the most common friction point for new customers using cloud delivery — expect 1–2 support tickets per new customer on first delivery and coach them through the install. No PhotoRobot account login is required for the download itself.

Explanation: 150 items per week to the same customer in the same configuration is a textbook case for auto-publish. The operator-driven manual export step exists to absorb variability; when the configuration is invariant and the volume is high, the manual step is pure overhead. Auto-publish (or an API feed) eliminates the 90-min weekly operator time and the human-error surface (selecting wrong items, loading wrong template, missing the email confirmation). Lowering JPG quality is a micro-optimization that misses the structural opportunity. Keeping the manual workflow is OK if volume is low; at 200 items / week to the same target it’s wasteful.