CartVisualCreate account

When should I attach a Pixelcut Brand Library to a product campaign instead of briefing each image manually?

Attach a Pixelcut Brand Library when the campaign needs one reusable brand identity across multiple generated assets and that identity is already configured in the Pixelcut web app. Use the library ID as the governing reference, then map each output to its request. If the brand details are incomplete, outdated, or intentionally different for a one-off asset, resolve that decision before generation rather than assuming visual similarity proves brand compliance.

Published · By CartVisual editorial team

Make the identity decision first

The useful question is not whether an image looks generally on-brand. It is whether the campaign has one approved identity that should govern every generated asset. Pixelcut documents a Brand Library as a stored identity containing the brand name, website, tagline, and description. That makes the library attachment a source-of-instructions decision, not an asset replacement or file-library migration.

Use a library when the same identity should govern a set of deliverables, such as a launch announcement, product visual, and supporting banner. Do not attach one merely because the product belongs to the company. First confirm that the library represents the current name, positioning, and description for this campaign. If the campaign intentionally uses a sub-brand or temporary identity, record that exception instead of silently borrowing the parent brand.

Use an attachment trail

Treat the Brand Library ID as the campaign’s identity handle. In the Pixelcut workflow documented by the source, an agent can find available libraries, identify the matching ID, and pass that ID to generate_media. The operational record should therefore connect three things: the chosen library, the generation brief, and each returned output.

This is an original planning aid, not a Pixelcut guarantee or a substitute for review. Record the library name and ID, the exact campaign purpose, and the output filenames or links returned by the generation workflow. Review the finished images for product and copy accuracy separately. A generated image can follow a brand direction while still being unsuitable as physical product evidence or as a final listing asset.

Separate identity consistency from format planning

A Brand Library answers who the content should represent. It does not answer every deliverable question. Keep the identity attachment constant when the campaign is one brand, but decide each asset’s platform format and content requirement independently. Pixelcut’s documentation lists aspect_ratio and num_variations as generation parameters alongside brand_library_id; the source registry separately covers the variation-versus-aspect-ratio decision.

This separation prevents a common handoff error: treating several outputs as one approved result because they share a brand reference. Approve the identity mapping first, then review each output for its own composition, product depiction, text, and publishing purpose. If no current library can be identified, pause the branded generation request and resolve the identity owner before producing a batch.

Worked hypothetical: one launch, one identity record

Hypothetical example only; no Pixelcut request was executed. A seller is preparing three launch graphics for the same cookware brand. The web app contains one current Brand Library whose name, tagline, and description match the launch brief. The seller chooses that library rather than repeating brand instructions in three separate prompts.

The seller first records the library name and returned brand_library_id, then submits each generation request with that same identity reference and a brief describing the individual asset. After results return, the seller maps each file to its request and reviews the cookware, offer wording, layout, and intended channel separately. The correct decision evidence is the consistent identity reference across requests plus the output-to-request map; it is not simply that the graphics look similar.

If the library’s tagline were outdated, the seller would stop and update or select the appropriate library before generating. If one graphic were for a legally separate sub-brand, the seller would treat it as a separate identity decision rather than reusing the parent library by default.

Where CartVisual fits

After choosing and documenting the intended brand identity, sellers can use CartVisual’s product-image workflow with a product description and creative requirements. CartVisual does not implement Pixelcut’s MCP or brand_library_id workflow, so the route is for a separate image-generation handoff, not automatic transfer.

See the current CartVisual workflow and its limitations

Source and evidence scope

Prepared by the CartVisual editorial team with AI assistance. Competitor behavior is documented rather than independently executed for this guide.

Pixelcut: Brand Libraries

Official source snapshot checked .

Pixelcut official documentation supplied as src-457, checked 2026-11-17. The source describes Brand Libraries and MCP-connected generation behavior. No Pixelcut feature was executed or independently tested here. The campaign-record method and review boundaries are editorial planning guidance.

Related decisions

Browse ecommerce creative workflows