Product photography glossary
Plain-language definitions for the terms that appear in requests, briefs, shot lists, proofs, client decisions, file naming, and final delivery.
This is an operational glossary, not a contract, channel specification, or general photography dictionary.
Use the section links below or your browser's Find command to locate a term.
Studios and clients can use the same word differently. When a term affects scope, price, timing, usage rights, acceptance, retention, or another obligation, define it in the current client agreement or job record.
Channel and retailer requirements can change. Use the current official source rather than treating a glossary definition as a technical specification.
An "In Lenso" note describes current product behavior only. Verify the latest working product before publication.
One current client engagement, from the first request or studio-entered referral through requirements, review, approval, and final-file handoff.
In studio work: Use job as the umbrella noun for the work. One job can contain several products, variants, views, proof versions, invoices, and final files.
In Lenso: Lenso keeps the request or referral, product-specific details, client decisions, and files attached to one project record. Public marketing copy calls the whole unit a job.
A structured way for a prospective or returning client to tell a studio what they need, including products, shot requirements, references, deadlines, and contact details.
In studio work: A request is not automatically a booking, accepted scope, quote, or job. The studio still reviews it and decides what happens next.
In Lenso: A requester confirms their email, and the studio reviews the request before converting it. Nothing becomes a job without the studio's action.
The current job-level record of the client goal, products, schedule, overall visual direction, review process, delivery method, and people responsible for decisions.
In studio work: A brief can begin with client input, studio discovery, or both. It should be reviewed rather than treated as correct merely because a form was submitted.
In Lenso: Lenso stores structured brief fields and history with the job. The exact fields can come from a template and can include required client confirmation.
A reusable set of account-level visual rules, such as background, crop, fill, lighting, shadow, props, retouch limits, and approved references.
In studio work: A style guide describes recurring visual treatment. It does not replace the current job brief or the per-output shot list.
Stock Keeping Unit. A SKU is a stable identifier for a sellable product or variant in the client's catalog.
In studio work: A SKU does not always require its own image set. Use the client's identifiers, then record which SKUs, variants, and views actually need files for the current job.
In Lenso: SKU values can remain attached to structured shot-list rows and related file context.
A distinct version of a product, such as a color, finish, size, pack, material, or configuration.
In studio work: Use a separate shot-list row when a variant has a distinct SKU, view, treatment, reference, output, or delivery filename. If variants are intentionally grouped, list the included identifiers.
The page on an ecommerce site where a specific product is presented and offered for sale.
In studio work: PDP image count, crop, aspect ratio, format, and other requirements vary by store, theme, retailer, region, and channel. Use the current official or client-provided requirement.
The execution-level record of the product views or assets the studio needs to create for the current job.
In studio work: A useful shot list connects a stable product identifier with one required view, its visual instructions, reference, output specification, and delivery filename.
In Lenso: Lenso supports structured SKU and shot-list rows. Use the latest in-product import template when uploading CSV or XLSX data.
One line representing one SKU or product identifier, one relevant variant, and one independently required view or asset.
In studio work: A product that needs front, back, and detail files normally needs three rows. Do not place several delivered views beside one filename.
In Lenso: A row can provide the product-level context used to organize the current brief, proof, or delivery naming.
An image, frame, file, moodboard section, or style-guide example used to show a visual requirement.
In studio work: State what the reference demonstrates, such as crop, lighting, product position, prop treatment, label orientation, color, or retouching. A file name alone may not be enough.
The technical and delivery requirements for one file, such as dimensions, aspect ratio, format, color profile, transparency, compression, channel label, or quantity.
In studio work: Use the current client or destination requirement. A remembered platform default is not a reliable specification.
An output the studio has agreed to provide, such as an image file, set, archive, manifest, or other named asset.
In studio work: The client agreement and current scope define what is included, when it is due, and what counts as accepted. A deliverable is not defined merely by what appears in a folder.
The agreed period between a named starting event and a named delivery or review milestone.
In studio work: Record when the clock starts, which days count, what pauses it, and which milestone ends it. Examples include receipt of products, confirmed scope, client feedback, or approval.
The primary image used to represent a product on a product page, category page, campaign, or another named placement.
In studio work: A hero image is not always a white-background front view. Its crop, background, styling, and product fill come from the current destination and client requirement.
A product image photographed, composited, or retouched so the final background matches the required white value.
In studio work: Some marketplaces require pure white for particular main images, while many other uses do not. Record the actual requirement and verify the exported file.
A product image shown in use, in an environment, or with contextual props, people, or complementary items.
In studio work: Define the setting, intended story, included items, usage, crop, and required variants. Do not assume a lifestyle label explains the setup.
An image made with products arranged on a surface and photographed from above.
In studio work: Record the surface, orientation, spacing, included props, overlap, crop, and whether the layout must match a reusable style guide.
A close view intended to show a specific feature, material, label, texture, construction detail, or package element.
In studio work: Name the detail explicitly. A generic 'detail' row does not say whether the file must show stitching, texture, hardware, ingredients, or another feature.
The proportional relationship between an image's width and height, such as 1:1, 4:5, 3:2, or 9:16.
In studio work: Aspect ratio is different from pixel dimensions. Record both when the destination requires both.
A captured frame or created option chosen to continue into retouching, review, or final delivery.
In studio work: Record who makes the selection, what material they can review, how many selections are included, and whether choosing another frame changes scope.
Post-production work applied to an image, such as color correction, dust removal, background treatment, masking, compositing, or controlled product cleanup.
In studio work: Define the intended treatment and limits. Retouching should not silently change product geometry, label text, quantity, colorway, or included accessories.
A deliberate studio review of the actual file or release set against the current approved requirements before it is sent or released.
In studio work: The reviewer checks the file identity, product truth, crop, color, retouching, technical output, naming, manifest, approval state, and accepted exceptions that apply.
In Lenso: Lenso can retain requirements and decisions, but it does not currently certify visual quality or automatically validate every channel rule.
An original capture, render, scan, or other input used to create review and final files.
In studio work: A source file can keep the camera, capture-system, or internal ingest name. It does not need the client-facing delivery name when the mapping remains reliable.
An editable production file used during retouching, compositing, design, color work, or export.
In studio work: Working files are not automatically deliverables. The agreement and current scope determine whether the client receives them.
A version shared so an authorized client reviewer can comment, request changes, or approve before final release.
In studio work: A proof should identify the product or asset, version, review purpose, and any limitations such as preview quality, watermarking, or color conditions.
In Lenso: Proofs and versions can remain attached to the same job, with comments and recorded client decisions.
A named or numbered state of a brief, shot list, proof, or file that distinguishes it from earlier and later states.
In studio work: Use versions when the history matters. Record what changed and which version a comment or approval applies to.
The final client-facing name used for a released output.
In studio work: The name commonly includes a stable product identifier and view, plus a channel, ratio, locale, sequence, or other distinction when needed.
In Lenso: Current shot-slot assignment can control client-facing delivery names while original storage object names remain unchanged.
A documented pattern for constructing file names consistently.
In studio work: A convention makes files easier to identify and sort. It does not create permanent storage, approval history, or a reorder system.
A structured list of the files in a release set and the product, variant, view, version, or status associated with each one.
In studio work: Use a manifest when the folder or archive alone does not make the handoff clear. Verify that every listed file exists and every delivered file belongs in the release.
In Lenso: The product supports delivery ZIPs and CSV or XLSX manifest behavior for the current job.
A file that the studio has marked for release after the applicable review, approval, quality-control, and release conditions are complete.
In studio work: The word final describes a current release state. It does not erase prior versions or prevent a later agreed update.
The process of sharing a review version, collecting comments, resolving requested changes, and recording a decision before final release.
In studio work: Define which files are under review, who can comment, who can approve, when feedback is due, and where the current decision record lives.
A note attached to a job, asset, proof, version, or other clearly identified review context.
In studio work: A comment can be a question, observation, preference, or instruction. It is not automatically a requested change or approval.
In Lenso: Client comments can remain tied to the relevant project and asset context rather than existing only in an unrelated email thread.
An explicit client decision asking the studio to alter a named proof, file, set, brief field, or requirement.
In studio work: Record the affected version, requested outcome, owner, status, and whether the request is within the current scope.
In Lenso: The client review experience includes a visible Approve action and a way to request changes, with the decision recorded on the job.
One review cycle in which feedback is received, changes are made, and a revised version is returned for another decision.
In studio work: The client agreement defines how many rounds are included and what work belongs in a round. A round count alone does not explain the size of the work.
The boundary between included changes, corrections, new requirements, and work that needs a new estimate or decision.
In studio work: Write the boundary in the governing agreement or current job record. This glossary does not decide who pays for a change.
An explicit recorded client decision that a named proof, version, or set can move to the next agreed stage.
In studio work: Identify the authorized decision maker and the exact version covered. The client agreement and applicable law define the legal effect of approval, silence, delivery, and acceptance.
In Lenso: The client review experience includes a visible Approve action and approval history attached to the job.
A documented deviation from the current requirement that an authorized decision maker agrees to accept for a named file, SKU, or set.
In studio work: Record the deviation, affected item, decision maker, date, and what will be delivered instead. An exception is not the same as quietly ignoring a failed check.
A release containing a named group of files, such as one SKU group, one job phase, or the final set.
In studio work: Define what the batch includes, its version or date, its manifest when needed, and whether another batch will follow.
A link containing a protected token or session path that gives an invited client access to a specific area of a job.
In studio work: A secure link can expire, be revoked, be resent, or be replaced. Do not treat it as permanent storage or unrestricted public access.
In Lenso: Client access is project-specific and Lenso-hosted. The latest product policy controls expiration, revocation, and release conditions.
A time-limited sign-in link sent to an email address so the recipient can access a protected area without creating a password.
In studio work: Anyone handling the link should treat it as an access credential. A new or replacement link may invalidate an earlier one.
In Lenso: Invited clients use email-based magic-link access and do not need a paid studio seat.
A protected hosted space where an invited client can view the parts of a job the studio has made available.
In studio work: The exact capabilities can include brief review, proof comments, requested changes, approval, invoice payment, or final-file download. Explain which actions are available for the current job.
In Lenso: Lenso's client area is project-specific. It is not a permanent cross-project asset library, and clients cannot start reorders from it.
An organized repository used to find and manage image or media files across a defined collection.
In studio work: An asset library may be internal to the studio, client-facing, or both. Access, retention, search, version history, and reuse rules vary by system.
In Lenso: The product has studio-side asset organization. The client area is not a universal cross-project library.
New work for a returning client that uses some context from an earlier job, such as products, shot requirements, naming, references, or delivery rules.
In studio work: Review every reused value. A prior requirement can be a starting point without being correct for the new work.
In Lenso: Repeat work is currently studio initiated. Do not promise that clients can start reorders themselves.
A new or updated set of product files created because products, variants, packaging, branding, seasons, channels, or visual direction changed.
In studio work: Define what remains valid from the earlier job and what must be reviewed again. A refresh is not automatically a smaller scope.
This glossary explains common operational language. It does not decide scope, fees, rights, approval authority, acceptance, payment, retention, security duties, or responsibility for changed work.
Use the client agreement, current brief, shot list, approved references, official channel documentation, and qualified professional advice where those questions matter.
Put the terms to work
Create one row for each SKU, variant, and required view, with styling, reference, output, and delivery-name details.
Record the owner, evidence, and completion condition at each job handoff.
Review product truth, color, crop, retouching, technical output, naming, approval, and final release.
Read direct answers about requests, client access, plans, storage, security, AI, and current product limits.
Read the current task instructions for client review and final-file access.
See the terms in one client job
The glossary works with any toolset. Lenso is useful when a studio wants the request or referral, product and shot details, proof versions, requested changes, approval, optional invoice, and final files attached to the same job.