How can I collect design feedback in Adobe Express without applying comments to the wrong product variant?

Set Up Variant Identity

Create a working copy of the design before collecting or applying feedback. Use a clearly readable page label or identity block for each product variant, such as “SKU-RED” and “SKU-BLUE,” together with the campaign branch if both variants share the same file. This is an editorial review practice; Adobe Express does not document automatic product-variant matching for comments.

Adobe Express supports multiple pages in a design. View all pages lets you select pages and use page-level actions such as duplicate and reorder. Because pages may have different sizes, do not assume that a duplicated or neighboring page uses the same format as the page being reviewed.

1. Open the working copy and use View all pages to inspect the page order.
2. Confirm that each page visibly identifies one product variant and campaign branch.
3. If a label is missing or ambiguous, stop the review and add or clarify the identity before requesting comments.

Place And Read Comments

Use a file-level comment for feedback about the whole design and an element-specific comment when the reviewer is referring to a particular asset. Adobe Express supports both types. When a comment pin is not positioned on the correct asset, move the pin before interpreting the instruction. Tag a collaborator when the person responsible for the decision needs to see the comment.

A pin supplies location context, but it does not establish which product identity the reviewer intended. Read the visible page identity, the selected page, the comment text, and the pinned asset together. If those signals disagree, do not apply the edit yet; ask the reviewer to clarify the intended variant or add a more specific comment.

1. Select the page containing the proposed change before opening or acting on the comment.
2. Check the page identity against the SKU or campaign branch named in the comment.
3. Check that an element-specific pin sits on the asset described by the comment.
4. Record the comment as unresolved when page, identity, or asset context is unclear.

Use Version History Safely

File > Show version history displays timestamped versions. Use it to inspect what changed before deciding whether a comment belongs to the current working state. Bookmark a useful reference version when you need to retain that point for review. Create copy from version produces a new file, which is useful for a controlled comparison while preserving the current file.

Restore changes the current file, so treat restoration as a deliberate file-level action rather than a way to test a single comment. History retention depends on the plan; do not rely on indefinite availability. A historical version also does not prove that an export was corrected or approved.

1. Open File > Show version history and identify the version relevant to the comment.
2. If a separate comparison is needed, use Create copy from version and keep the current working copy unchanged.
3. Use Bookmark for a reference point, and reserve Restore for an intentional decision to change the current file.

Illustrative Exercise

Illustrative exercise: create two fictional pages in a test copy. Page 1 is “SKU-RED / Spring banner” with a red package image; Page 2 is “SKU-BLUE / Spring banner” with a blue package image. Ask a reviewer to comment, “Move the badge below the package,” without naming a page, then place the comment pin on the blue package asset.

Before editing, inspect the selected page, visible identity, comment text, and pin. If the reviewer confirms the blue variant, the comment passes the context check and you may edit only Page 2. If the reviewer intended the red variant, move the comment to the correct asset or request a new, explicit comment. If the reviewer cannot identify the intended variant, stop; do not apply the edit to either page.

The exercise is fictional and is not a completed Adobe Express test. Its acceptance condition is concrete: every comment maps to one visible variant and product identity, and no change is made to the other page by mistake.

Close The Review

After applying an edit, return to the comment and inspect the visible page and asset again. Mark the review complete only when the changed page is the intended variant and the other variant remains untouched. Do not treat the presence of a comment, a bookmarked version, or a restored version as approval of an export.

For a release record, keep the page name, variant identity, comment reference, selected version, and action taken together. This creates a manual version-to-comment check and makes the next review decision explicit without claiming that Adobe Express performs the matching automatically.

Use this question’s review worksheet

The sample rows are fictional exercise data. Preserve the example, save a working copy and record your own inputs, observations and decisions. The example is not a test receipt.

Fictional manual version-to-comment worksheet (CSV)