How to approve a batch of SKU creatives without mixing variants

Fill in the cells before calling the launch approved

In this fictional launch, a team sells four pouch colors. The navy pouch now has a new zipper pull. Its latest video still shows the old pull. The beige storefront image is correct. Neither finding tells the team whether an image showing all four colors is ready.

Give each file its own row. Name the SKU, use and exact version. A file name or saved asset reference is useful only if the reviewer and publisher can locate that same file. “Pouch campaign approved” is too broad.

These are invented records, not completed tests. The table is a team document. CartVisual does not create these approval states or publish the rows automatically.

Check shared design and product facts separately

The four colors can share a type style, layout and seasonal message. They still need separate checks for shade, closures, contents and any claim that varies by SKU. If only the large pouch fits a named device, its sentence must not appear on the small pouch.

When a part changes, use the product-change asset review to find every file that shows it. A close-up far from the zipper may remain usable after review. A use demonstration with the old pull needs a different decision. Do not remake unrelated work just to make all file dates match.

Give a blocked row one clear next step

For navy-clip-r2, write “replace the old zipper pull in the video, then review the new file.” Name the person who will make that change. If the team lacks a photo of the new pull, the next step is to obtain that source, not to approve a guess.

Keep task progress separate. A generation marked complete can still be held for a visible defect. A file approved for a storefront slot can be ready while a separate video task is still running. Use “published” only after someone has checked the actual destination.

Release only the rows that can stand on their own

The beige hero can go live if its page, offer and available product all agree. The navy video stays held. The four-color image needs its own review: if it shows the old navy pull, holding the navy video does not make that collection image accurate.

If the launch requires one comparison containing all four colors, that comparison remains blocked. If three separate product pages can launch truthfully, a partial release may work. Record which shared asset or offer prevents a row from standing alone. A newer upload is not approval; Frame.io’s versioning reference illustrates keeping older revisions available for inspection.

Match the approved file to the live slot

Use the destination release checklist to check the final crop, wording, link and selected SKU. After upload, open the live placement and confirm that it shows the approved file. An older export may have been selected even when the reviewed file was correct.

When navy-clip-r3 is ready, review r3 and record that result. Keep r2 held or retired in the external record; do not change its history to approved. A corrected video also does not approve a collection image that still uses the old product.