Keeping one file per supplier, and what goes in it
A supplier file is four or five items: the terms as they stood, the plan in force, any dated answers to questions, and what the product settings were. All of it is cheap to keep and impossible to reconstruct. As of 2026-09-12.
| Item | Question it answers |
|---|---|
| The terms and licence pages as they stood | What we were permitted to do, and when |
| The plan in force, with dates | Which grant applied to which deliverable |
| Dated replies from the supplier | What we were told, by whom, and when |
| Product settings that carry a position | Which clause applied to a given generation |
Inclusion rule. Items that cannot be reconstructed after the fact, and that a rights question will ask for. Order. From the document that binds to the settings that select between clauses.
1A saved page is worth more than a bookmark
Suppliers rewrite terms, and a link to a page that has changed proves nothing about what it said. Keeping the text as it stood, with the date, is the difference between showing a decision was reasonable and asserting it.
This is not a legal exercise. It is the same instinct as keeping a signed purchase order, applied to a document nobody signs and everybody relies on.
2The plan is the part people forget
On most products the permission is conditional on a plan, and a plan is a fact about a moment. A file that records terms without recording which subscription was active has kept half the answer.
Where a product is priced per seat, the account matters as much as the plan, because the permission attaches to a login and the deliverable carries no trace of which one produced it.
3Settings can select a clause
On some products a visibility or privacy setting decides which ownership sentence applies. That makes the setting part of the rights position, and it is recorded nowhere unless a production records it.
One line per export covers it: the plan, the account, the relevant settings. Teams that add that line to an existing delivery log never notice the cost.
4Where the vendor statements are kept
The mechanics above apply to anyone. What a given vendor has committed to in writing is held on the register instead, each line with the plan page it came from and the date it was checked.
An explainer, not an entry in the register. Vendor statements are held, with their sources, on commercial use, and nothing on this page is legal advice. Related: Which account, Input logs.
5What the output is for
Alongside the terms behind “A supplier file”, SceneMixer's guides describe the work itself this way:
You can recomposite with different end-card text, and in step-by-step mode you can reshoot individual segments. The finished file can also be downloaded and shared with a link.
SceneMixer, How to Make an Ad from One Photo — “Can I change the ad after it is finished?” (read 2026-10-13)
The spoken lines and the end card follow your interface language across fifteen dialogue languages, with the cast and setting adapted to that market. The end card falls back to a language it can typeset when a script needs shaping or right-to-left layout.
SceneMixer, AI Ad Video Generator — “Which languages can the ad be in?” (read 2026-10-13)