Front and Back, One Garment

GS1’s product-image standard identifies views in relation to a defined front face and distinguishes front, back, and other facings. Use that principle in your own library without adopting a complex naming system: decide what each photograph shows, label it clearly, and keep the same product identifier attached to every view.

Add wearer-relative left or right when a feature is asymmetric. A mirrored front photograph can look tidy while moving a pocket or graphic to the wrong side. Do not let a file called back determine the review by itself; inspect the visible construction and confirm that the label actually describes the image.

List the features shared across the set, such as colorway, collar, sleeve treatment, and overall cut. Then list what belongs to the front and what belongs to the back. For the example, the front map includes the placket and chest pockets; the back map includes the yoke and pleat. Your real map should follow your item.

The map is not a demand for matching pixels. Perspective, pose, and folds can change the visible outline. It is a way to spot an unexplained new pocket, missing rear feature, altered sleeve finish, or contradictory garment length. Keep each check tied to a source photograph rather than to a generic expectation of how an overshirt usually looks.

If the yoke seam or pleat disappears in a distant photo, add a closer view that includes enough context to locate it. Show the full back print when one exists. A crop from the front cannot verify a feature that only occurs on the reverse, even when the fabric and color appear similar.

Shopify recommends multiple clothing angles and detail views to explain an item. Apply that approach selectively: add the view that resolves the missing information. Avoid filling the set with almost identical frontal photos while leaving the back unrecorded. The goal is a complete description of the important design, not a large number of interchangeable files.

Use a simple manifest such as front, back, and rear-detail under the same SKU. Include the colorway and revision when your range needs them. Do not mix an early sample’s back with the production front. Check that a second colorway does not introduce a different pocket, trim, or print arrangement into the reference group.

Google Merchant Center supports additional product images for other angles. Use the same practical idea in the delivery set: the supplementary view should explain the same item as the primary image. Keep a clear source for each view so another teammate can understand why the collection was approved without reconstructing the decision from memory.

In Studiola Lookbook, choose a model when needed, add your own product, and select a ready scene suited to the required presentation. Its visible pose, light, and framing help settle the starting direction without a basic written prompt. For a back-view brief, make sure the intended composition actually makes the rear details inspectable.

The prepared direction helps reduce setup decisions; it does not guarantee matching front and back outputs. TRY ON is a lower-credit-cost alternative for more open exploration, where scene and pose choices may need more iteration. Review each candidate against its relevant source and then compare the whole set for shared product identity.

Lay out the candidate views together with their original references. Check shared colorway, sleeve treatment, collar, material character, and cut. Then inspect front-only and back-only features. Mark whether a difference is due to visible pose and fold, a hidden region, or an actual contradiction in the design. Those are different review decisions.

If the back reference is missing, capture it instead of approving an imagined construction. If the reference is clear but a candidate changes it, revise that view and check the set again during the normal editorial decision. Keep the design map and original photographs in the handoff so future crops and campaign versions remain tied to the same product.