Separate creative rejection from a concern report
Not every unusable fashion image is a trust-and-safety issue. A wrong garment color, awkward pose, weak composition, or poor merchandising choice may justify rejecting the asset without reporting it. Reporting becomes the appropriate next action when the issue may affect legality, personal safety, privacy, ownership rights, or the platform’s security and moderation systems.
Use the decision as a publication gate: if the image could expose the store to a rights, privacy, safety, or abuse problem, pause publication while the concern is documented. Do not treat a generated image as physical product evidence, and do not infer that a suspicious result proves how the system produced it.
- Creative rejection: the asset fails your brief but does not indicate a policy, rights, privacy, or abuse concern.
- Report and hold: the asset appears to fit one of the documented concern categories or could create a material compliance risk.
- Escalate internally first: ownership, legal, or privacy responsibility is unclear and the team needs a decision before sending or publishing.
Use a category-to-evidence gate
Botika’s official help article identifies reportable areas including illegal activity, harmful or abusive material, explicit content, privacy violations, intellectual-property infringement, and platform abuse. Those labels are useful triage categories, but they do not establish that a particular image is illegal or infringing. Describe what is visible or known, separate facts from suspicion, and leave the determination to the appropriate reviewer.
The useful planning aid is a two-part test: first identify the possible category; then ask whether you can preserve a specific pointer to the item. A report with no identifiable content, time, or description is harder to investigate. Keep evidence proportionate: retain the relevant URL, screenshot, asset identifier, and encounter time, while avoiding unnecessary personal information in working notes.
- Name the possible category without overstating the conclusion.
- Record the exact concern in observable terms.
- Capture the relevant URL, screenshot, or identifying detail if available.
- Record when the issue was encountered, including the time zone if your team operates across regions.
- Add contact information only when follow-up is useful and authorized.
Choose the next action and preserve the boundary
The source documents email reporting to Botika’s Trust & Safety Team at safety@botika.com. That is a vendor-reporting route, not proof of a response time, removal decision, investigation result, or legal finding. Do not promise customers that reporting will resolve the issue. Keep the asset unpublished while the responsible owner decides whether the concern also requires a rights, privacy, marketplace, or internal security escalation.
Record three separate states: publication status, vendor-report status, and internal ownership decision. This prevents a submitted report from being mistaken for approval to use the image. If the concern is only that the image is commercially weak, close the safety branch and route it through the ordinary creative review instead.
- Hold the image from publication when the concern is unresolved.
- Submit the vendor report only when the category and identifying evidence are sufficiently clear.
- Store the report date and owner separately from any later vendor response.
- Close or update the record only when the responsible owner has documented the next decision.
Worked example: a hypothetical model image with personal information
Hypothetically, a seller receives a Botika fashion image that visibly includes a real-looking phone number on a background sign. The seller cannot establish whether the number belongs to a real person, so the correct description is not “Botika leaked private data.” The observable concern is that the image may display personal information without authorization.
The seller marks the image unpublished, saves the image URL and a redacted screenshot in the authorized review location, records the encounter time, and identifies privacy violation as the possible category. The seller then sends a concise report to Botika’s Trust & Safety Team with the concern, URL, screenshot or asset detail, date and time, and optional contact information. Internally, the seller records that publication remains on hold pending ownership review. If the number was clearly fictional placeholder text and no other concern exists, the seller would instead reject the image as a creative or content-quality issue without treating it as a confirmed privacy violation.
Where CartVisual fits
Use CartVisual’s manual checklist only for a separate product-accuracy review after concern triage. It does not submit Botika reports, assess legality, or replace Trust & Safety review.
Source and evidence scope
Prepared by the CartVisual editorial team with AI assistance. Competitor behavior is documented rather than independently executed for this guide.
Official source snapshot checked .
This guide uses one Botika official help article, supplied and checked November 17, 2026. It documents report categories, an email route, and suggested report details. It does not document response times, investigation outcomes, takedown guarantees, legal conclusions, or CartVisual integrations.