Distinguish a mandatory reference from a replaceable preference
Before building a garment-image production brief, label each desired human or scene attribute as mandatory or negotiable. A specified licensed model, a brand-owned studio set, or an exact hairstyle may be part of a campaign approval. A general age-appropriate appearance or neutral setting might instead be a styling preference. Those are different eligibility states, even if an available gallery option appears similar.
The supplied Botika help describes its models and backgrounds as in-house options. It explicitly excludes supplying your own model or background and customizing the platform models’ makeup, hairstyle, or expression. Do not turn an unsupported upload requirement into a prompt-writing task or assume that selecting a lookalike satisfies an exact person or setting requirement.
Choose between gallery, feedback and another documented workflow
When the requirement is negotiable, the next decision is whether a gallery selection actually satisfies the approved brief. Preserve the exact garment SKU and intended use independently; gallery selection is not evidence that garment features will be accurate. If the desired model or background type is missing, the help invites contacting Botika with feedback. That is a request for consideration, not a pending order or a commitment to add the option.
When a named person or brand setting is compulsory, stop before preparing a Botika generation batch. Obtain a workflow whose current documentation supports those reference inputs, or revise the campaign specification with the decision-maker. The fact that other systems allow custom models does not establish an undocumented exception in Botika.
Keep the handoff simple: the requirement, whether substitution is permitted, whether an acceptable gallery option exists, and the resulting go/no-go decision. The source does not define an account-specific exception or an arrival date for new gallery resources.
Hypothetical decision: an approved campaign requires its contracted model
A garment seller has a campaign contract requiring the photographically approved adult model and a particular branded showroom background. Another department suggests using Botika because a catalog option might look similar. Both references are mandatory, so substitution is not authorized. Under the documented Botika limitations, the team should not schedule this task as a custom model/background upload.
If the brief owner later relaxes the requirement to an anonymous model and neutral setting, the decision changes: evaluate the available gallery, document the selected alternative, and continue only if approved. Contacting Botika about the absent exact options does not make the first plan executable.
Source and evidence scope
Prepared by the CartVisual editorial team with AI assistance. Competitor behavior is documented rather than independently executed for this guide.
Botika: Can I create my own models or backgrounds?
Official source snapshot checked .
The supplied Botika help page states general customization restrictions and a feedback channel. It does not describe exceptions, individual gallery availability, custom-reference import alternatives, or any commitment to add requested options. The go/no-go framework is an editorial application of those stated limits.