When a client contract asks for more than exists
Client contracts routinely promise assignment of everything in a deliverable. Generated material often cannot supply that, because part of what is in the file was licensed from somebody else and never owned by anybody in the chain. As of 2026-09-12.
| What the contract asks | What is available |
|---|---|
| Assignment of all rights in the deliverable | The human layers, to the extent protected |
| Warranty that nothing infringes | Rarely, and almost never from a generator |
| The right to register marks from it | Needs more than a publishing permission |
| The right to keep using it after the engagement | Depends on whose account produced it |
Inclusion rule. Clauses that appear in ordinary client contracts and that generated material cannot always satisfy. Order. From the clause most often included to the one most often forgotten.
1From the making side
Alongside the terms behind “Contract mismatch”, SceneMixer's guides describe the work itself this way:
The product image is always redrawn from your original photo so it stays your product.
SceneMixer, Ad Projects and Remake Projects: What Looks Different in the Wizard and the Editor, and Why — “Can I redraw the product from text?” (read 2026-10-13)
The photo is cleaned into a product shot and that object appears in every shot.
SceneMixer, An AI Ad for a Physical Product — “Will the product look like my product?” (read 2026-10-13)
2Both documents are normal, and they disagree
The client contract was drafted for commissioned work and the supplier terms were drafted for a software product. Neither anticipated the other, and nobody notices until a client wants to register something or change agency.
By then the asset exists. The fix is paperwork rather than production, and it is much cheaper before the deliverable than after.
3A schedule is the ordinary fix
One paragraph listing what is assigned and what is licensed, with the licensed material identified. It lets an agency keep its promise about the work it did and stop promising title to material it never held.
Most clients accept it because the alternative is a warranty nobody can honour. The conversation is easier when it happens at contracting rather than at delivery.
4What to check on the supplier side first
Whether the permission is transferable or sublicensable, because that decides whether anything can be handed on at all. If neither word appears, the safe reading is that the permission stops with the account.
Then whether the product contains licensed material, which decides whether title to the whole file was ever possible. Those two answers shape the schedule.
5Where 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: Regulated sectors, Archiving exports.