Design Quotes: Masters, Adaptations and Export Counts

Define what one image means before discussing a quote

When a client requests ten images, they may mean ten independent creative concepts or one design exported in ten specifications. Counting only the images in a folder can place very different workloads under the same number. Flux Art can help create candidates, but it does not define delivery units for either party. This article recommends recording design masters, adaptations and exported files separately, then discussing fees according to the actual agreement. It offers no standard unit price and does not present any counting method as an industry or contractual standard.

A master records a visual direction, not every source file

Give each independent design direction an ID and specify its product, main information, composition and intended use. Here, a master means the design baseline in a working record; it does not mean the client necessarily receives editable source files, or that a generated candidate has been approved. Repeated generation attempts in the same direction can remain candidate versions without automatically increasing the number of formally delivered designs. The actual task scope and confirmation records still determine which directions enter delivery.

Distinguish adaptations from exports by the actual work

Changing a landscape design to portrait sometimes means exporting an approved design, and sometimes requires rearranging the headline, product and explanatory text. A resolution change alone cannot determine whether it is a new design. A language change may involve replacing approved short text or reorganizing longer copy. The table below gives hypothetical categories, not real quotation records, to help both parties identify the work involved; it does not determine fees. Recording the actions and acceptance requirements before classifying them makes the scope more actionable than arguing over whether a file counts as one image.

Give every exported file a source master

Map master IDs, adaptation IDs and final filenames: for example, direction A has portrait adaptation A-V, which is then exported in two approved specifications. These are internal ID examples, not requirements for particular software or naming rules. The file list should also include language, use, dimensions, format and status to prevent identical names from overwriting earlier drafts. You can count total files, but do not treat every file as an independent creative concept or describe specification changes requiring individual checks as work-free.

Count language files and record review responsibilities

Turning a Chinese image into an English image may add copy approval, line-break, font and layout checks alongside another file. Establish who provides and approves the translation and whether material must be adapted for different markets. Do not assume translation and proofreading are included in a vaguely defined export action. If the service covers layout but not translation, record that the input is approved text. Link each language version to its master so a client does not approve text on an old composition and receive a different new design.

Keep generated candidate counts separate from delivery counts

You can prepare product-image candidates at https://flux-art.net/en/ai-ecommerce and record actual generation consumption from the submission page. Candidates, rejected images and revision versions are internal process materials, not part of the promised finished count unless both parties explicitly include them as deliverables. Generating many times also does not prove that multiple designs are complete. Record attempts, candidate directions, approved masters, delivered adaptations and final files separately, preserving production-cost records while making clear what the client can ultimately use.

Identify changes before deciding whether they incur charges

Suppose the original list includes two layouts in one language, and a new set of selling points is later requested. First identify the affected master, adaptations and number of exports, then discuss whether they fit the current arrangement. Do not call every change another quick export, or count every alteration as a new project without discussion. The quantity table supports communication; it does not automatically create a payment obligation. Confirm fees, timing and usage scope according to the actual agreement. This article does not judge specific disputes or legal effect.

Trace the delivery list back to confirmation records

Before delivery, pick a file at random and check that you can retrieve its master, corresponding adaptation, approved text and actual confirmation outcome. A filename saying final is insufficient; approval in a screenshot may concern only a background or language. If a file uses another composition, check it again instead of inheriting old approval based on resemblance. Mark missing files as not delivered and those whose acceptance is still unknown as pending confirmation. Do not pad the list with process drafts or old versions to improve the total.

Clear quantities create a reusable basis for future quotes

After the project, separately total design directions, adaptations, exports, manual proofreading and actual consumption. Use your own records for future estimates rather than presenting one experience as industry-wide pricing. Flux Art, operated by MORNING STAR INDUSTRY LIMITED, is a multi-model AI visual creation and production platform that supports commercial use. Confirm platform commercial use, project-material rights and source-file scope separately. This article contains no hands-on client-quotation test. The table is maintained outside the platform by the team; it does not claim a built-in quotation, contract or approval system.