Your creative partner in China has trained a model using your product photography. They consider the handoff complete when they deliver campaign images. Your marketing team expected to keep generating new scenes independently. Both parties may have worked diligently while promising different things.
Before commissioning a “brand-owned model,” distinguish finished outputs, client-operated generation and portability. They are separate buying decisions, even when a proposal uses the same reassuring language for all three.
A specific source, with a specific scope
Adobe’s enterprise Firefly Custom Model PSLT, 2026v1, section 2.5, limits the covered model use to internal purposes: the customer cannot give its clients model access or use, although sharing generated outputs is permitted. Section 2.3 separately requires an appropriate Creative Cloud license for generation. The model license alone does not include it.
Those provisions concern the specified enterprise add-on document. They are not a universal rule for every Adobe plan or custom-model product. Verify the terms and order applicable to the proposed arrangement; this article does not determine which contract governs a particular buyer. The document was checked November 2, 2026; 2026v1 is its version label, not a publication date established here.
Adobe’s Share custom models help page, updated September 21, 2026, describes different collaborator roles for editing, review and generation. ONCE’s interpretation is that a sharing control demonstrates technical functionality, rather than permission for every commercial handoff. A screenshot of an invitation menu does not settle the applicable arrangement.
ONCE’s three handoff tests
This proposed procurement framework is not a platform standard or a report of measured client outcomes. Select the capability your business needs, then specify a separate acceptance test for each part.
Finished assets: what usable files arrive?
A practical acceptance statement describes approved images, formats, dimensions and any agreed editable files. Assign generation, selection, retouching, product-detail checks and final approval. Receiving those assets does not automatically give the buyer the supplier’s account or an independently operable model.
This can suit a team that wants a creative partner to own production and review. Compare usable deliverables, revision scope and the process for ordering more, rather than whether a model has been named after the brand.
Self-service: can your actual operator do the work?
Define a task that your designated employee can complete under the approved account and licensing arrangement. Record the account holder, operator, role, required subscriptions, payment responsibility and ongoing administration after the partner leaves.
Verify this before investing in formal training. If the proposed design uses the brand’s own account, confirm how external production staff may participate. Moving the account name is a proposal to check, not a universal workaround.
Portability: can the capability move?
Specify the actual deliverables, dependencies, permitted environment and a demonstration in a mutually agreed independent setup. Keeping photographs and prompts can support rebuilding; it is not proof that a runnable model has been handed over.
If a proposal only provides hosted capability, buy and describe that capability honestly. Ask the supplier to substantiate any portability promise. Where it cannot, remove that promise or evaluate a different arrangement. This is an acceptance method, not a claim that one model format works everywhere.
| Buying objective | Acceptance focus | Do not equate it with |
|---|---|---|
| Finished assets | Files, quality, approvals and revisions | Independent model operation |
| Self-service generation | Real operator, account, permissions and costs | A supplier-only demonstration |
| Future portability | Deliverables, dependencies and independent verification | A backup of source photography |
Resolve the business task before the training task
Consider a hypothetical overseas home-accessory brand working with a Shenzhen production partner. Its brief asks for a model “we can use later.” Does that mean another batch of approved images next month, a designer operating it directly, or the ability to change suppliers without losing a working generation setup? This is an illustrative buyer, not an ONCE client.
For an output service, begin by accepting a tightly scoped content package. For employee-operated generation, verify the planned licensing and identity workflow before formal training. If portability is essential, make the independent demonstration part of selection instead of demanding an unspecified file on the final delivery date.
Use authorized material and agreed tasks for any pilot, and retain its actual findings. No customer account was created, product photography uploaded or model trained for this article.
Compare setup with continuing use
Keep separate accounting categories for asset preparation and validation, platform licensing and use, generation and human finishing, and maintenance or exit handoff. These are evaluation categories, not an instruction to charge twice for an item already bundled into a package. Use actual quotes and identify who pays, what is included and when the cost occurs.
A low training fee does not establish a low lifetime cost. A monthly service does not establish self-service access either. Compare equivalent usable results, operating responsibilities and periods of use. Without real volume and rework data, leave payback uncertain instead of inventing a break-even month.
Build a service that can explain its handoff
For ONCE’s progression toward managed content services, useful records include approved source assets, task definitions, operator responsibilities, the applicable plan, acceptance methods and an exit checklist. Distinguish hosted capability from materials the brand can retain. Do not describe either as complete ownership without substantiation.
Ongoing creative services can earn their value through ideas, reliable finishing and clear response commitments. They do not need an ambiguous model-delivery promise. Explore ONCE’s AIGC articles when preparing a brief, and specify what your team must still be able to do after the engagement ends.
Research scope
The two official sources linked above were checked November 2, 2026. This is evergreen procurement analysis, not a report of newly issued rules. It does not generalize a particular enterprise document to all products. The framework, acceptance suggestions and hypothetical buyer are ONCE analysis, with no claimed customer results.
