Sell a Motion Graphics template only after the exact customer `.mogrt` installs in Premiere Pro, exposes the promised controls and renders correctly without your working folder. A demo reel proves appearance; it does not prove that fonts, media, expressions, plug-ins, aspect ratios or app versions survive delivery.
This release workflow is for motion designers selling titles, lower thirds, transitions and other editable MOGRTs. Its original asset is a six-sequence buyer test tied to one versioned retail ZIP.
Define the Editable Product
List the minimum Premiere Pro version, whether After Effects is required, the tested operating systems, installed fonts, third-party plug-ins, included media, supported frame sizes and every editable control. Separate what the buyer can customize from what is baked into the design.
| Release field | Record | Buyer-facing promise |
|---|---|---|
| Template identity | Product name, MOGRT version and checksum | The delivered file matches the listing |
| Host requirement | Premiere Pro and, if needed, After Effects versions | A narrow, tested compatibility range |
| Controls | Text, color, position, media replacement and ranges | Only controls visible in Essential Graphics |
| Dependencies | Fonts, plug-ins, footage and audio | Included items and lawful external requirements |
| Output | Frame sizes, frame rates, duration and color conditions | Tested cases rather than “works everywhere” |
Adobe's current Motion Graphics template documentation explains how Premiere Pro installs and customizes MOGRTs. Use the documentation for the exact current version, but treat every compatibility promise as something your retail file must prove.
Run the Six-Sequence Buyer Test
Create a clean Premiere Pro project and import the MOGRT from the retail ZIP. Test six short sequences without opening your development project.
| Sequence | Stress case | Pass condition |
|---|---|---|
| HD landscape | Short and long text | No clipping; controls remain understandable |
| UHD landscape | High-resolution export | Shapes and included media remain sharp |
| Vertical | 1080×1920 composition | Layout adapts or the limitation is disclosed |
| Square | 1080×1080 social crop | Essential content stays visible |
| Duration | Minimum, default and extended length | Protected timing and animation behave as stated |
| Dependency | Test account without creator-only assets | Missing requirement is removed, bundled lawfully or clearly disclosed |
Record the host version, operating system, sequence settings, template checksum, control values, render result and warnings. If the product promises replaceable media, use portrait, landscape and transparent samples rather than one ideal placeholder.
Audit Fonts, Media and Plug-ins
Remove development-only paths and inspect every font, stock clip, icon, sound and plug-in. A license to use an asset in a rendered video does not necessarily permit redistribution inside an editable template. Where redistribution is not allowed, replace the dependency or name the lawful source before checkout.
Test the customer package on a clean user account or second machine. Temporarily make the original project and cache unavailable; otherwise Premiere Pro may resolve a dependency that the buyer will never receive.
Package the Retail ZIP
Include the MOGRT, a START-HERE guide, license, changelog and a dependency manifest. Add a short preview video separately so customers do not mistake it for an editable source. The guide should show installation, browser location, controls, tested versions, output conditions and support boundaries.
Give the ZIP and MOGRT the same release version. Calculate a checksum, extract the uploaded archive and repeat the HD and dependency tests. Archive the approved ZIP with its six-sequence result so support can identify exactly what a buyer received.
Deliver the Tested MOGRT After Payment
Use PayRequest's video-template product workflow with protected file delivery to release the approved ZIP after confirmed payment. Put compatibility, dependencies, license scope and update policy on the sales page before checkout.
Complete one buyer-view order, download the receipt file and compare its checksum with the approved build. The release is ready when another editor can install, find, customize and render the template using only the delivered archive and instructions.