Multi-Platform Video Delivery: Build a Version Tree

Imagine receiving a “completed” delivery folder on Friday night: more than twenty horizontal, vertical, and square MP4 files. The following week, the packaging changes, legal removes a product claim, and the Amazon landing destination moves from a product detail page to a Brand Store. Which files share the same master? Which captions are still valid? Which outputs need to be rebuilt? If only the editor knows, the delivery is not operationally complete.

The hard part of multi-platform ecommerce video delivery is not export volume. It is turning one approved piece of content into a traceable version tree that can be changed locally and verified again.

A platform name is not a specification

“Make versions for TikTok, Google, and Amazon” still leaves out placement, objective, destination, market, language, and product scope. TikTok Auction In-Feed supports vertical, horizontal, and square video, while its safe zone varies with dimensions, caption length, and add-ons. TikTok's official specification therefore makes the actual placement part of the brief, not an afterthought.

Google Performance Max accepts horizontal, square, and vertical video and may generate or adapt assets automatically. Google also warns that a video can feature a product different from the landing page if product scope is not controlled.

Amazon shows why “Amazon version” is too vague. The standard Sponsored Brands product-detail-page format is 16:9, while Store-landing objectives support vertical video. The branch name should therefore include ad type, objective, destination, and market.

Define a six-level version tree before bulk export

1. Editorial master: the approved shot order, product facts, claims, and duration.
2. Clean master and component pack: high-quality clean picture, dialogue and music stems, caption files, replaceable pack shots, and contracted graphic components.
3. Format master: deliberate 16:9, 9:16, or 1:1 compositions rather than blind crops.
4. Placement master: branches such as TikTok In-Feed, a PMax asset group, or an Amazon Store placement, with safe zones and duration constraints recorded.
5. Market and product version: branches for territory, language, SKU or GTIN, packaging, and offer.
6. Release file: the final codec, resolution, bitrate, and revision. A release is a leaf, not a new master.

The GS1 Product Video Standard, ratified in May 2024, follows the same principle: product identity, video type, aspect ratio, serialization, and language can all belong in the filename. Identical content in different aspect ratios should identify the ratio explicitly.

Use filenames for identity and a manifest for meaning

A practical pattern is:

PROJECT_ASSETID_CUT_FMT_PLACEMENT_MARKET_LANG_SKU_R03.mp4

CUT identifies the editorial master, FMT identifies orientation, PLACEMENT identifies the media context, and R03 is the third revision of that release branch. Avoid names such as final_final2. Approval is a status, not a filename.

Keep status in a delivery manifest. At minimum, record asset ID, parent version, change note, specification source and check date, market, language, product scope, owner, approver, state, publication date, and live URL. A spreadsheet is enough for a small project; the essential requirement is that every release file points back to its parent.

Let change impact determine the rebuild scope

• A caption change affects the relevant language branch and requires a new obstruction and line-break check.
• A packaging or SKU change affects the relevant product branch.
• A safe-zone update affects the relevant placement branch, not every editorial master.
• A rejected core claim is an upstream content change, so every descendant using that claim must be rebuilt and re-approved.
• A music-rights change can be located by market and rebuilt from the audio stems.

Do not overwrite a released file. Create the next revision and record which release it replaces. Otherwise, performance reporting cannot be tied to the actual creative that ran. For a broader workflow, see ONCE's guide to asset versions and revision feedback.

Five checks define a complete delivery

1. An approved editorial master with an approval date.
2. A reusable clean master, audio stems, caption files, and contracted graphics.
3. A version tree or manifest that traces every release to its parent.
4. A source and check date for each placement specification.
5. A release-level QC record for picture, captions, audio, product information, and destination.

The most useful procurement question is not “How many files will we get?” It is “Can the team identify every affected release within ten minutes when a product fact changes?” A clear version tree makes high volume manageable; a folder without lineage only multiplies risk.

If your ecommerce team manages video across platforms, markets, and SKUs, contact ONCE to define the objectives, version tree, change ownership, and acceptance checklist inside an ecommerce content growth plan before deciding what to shoot, adapt, and deliver.