Ask Pixerr (chat assistant)
Real sentences you can type into Ask Pixerr (the chat bubble on most Pixerr pages), and what should happen on screen. Use this like a creator playbook—not a developer checklist.
Sign in first
General questions work while logged out. Mockups, gallery picks, Buy now, Sell this, and store actions need a signed-in account with tokens.
Supported products: mugs, phone cases, apparel, posters, canvas, puzzles, pillows, holiday decor, pet bandana collars, calendars, and more—see Creating Products. Stickers are not available yet.
Open Ask Pixerr
- Click the Ask Pixerr button (bottom-right).
- Type a message and press Send, or use the paperclip to upload artwork first.
- Watch for Awaiting confirmation on plans that spend tokens—click Confirm before mockups generate.
For transparent PNGs, store pricing (automatic for physical products), and Studio placement, see also Working with transparency and How pricing works.
Getting started
Open Copilot from the launcher (chat bubble) on most Pixerr pages. Sign in as a creator with a store and some tokens.
Copilot should answer in plain language about making designs, putting them on products, adding to your store, and checkout—not a wall of error codes.
- The chat panel opens and you can scroll past the welcome chips.
- While it thinks, the status text should rotate (not stay stuck on one word forever).
It should list real things from Pixerr’s live Studio catalog—mugs, phone cases, desk calendars, posters and canvas, puzzles, pillows, holiday ornaments and stockings, pet bandana collars, DTG shirts, sublimated socks, digital downloads, coloring books, and more—not a vague “phone cases, mugs, and more.” Stickers are not supported yet—do not suggest them. Staged-off pet SKUs (bowl, leash, sweater) should not appear. See Creating Products for the full list.
It should use your account context when possible, or tell you to check the dashboard—not invent a random number.
Your first product preview
This is the core loop: Copilot creates a product preview card with a mockup (your art on a mug, shirt, etc.).
Copilot should not claim the mug already exists. It should show a confirmation step first (because generating costs tokens).
- You see a short plan: what it will generate, rough token cost.
- You click Confirm.
- A card appears with your artwork thumbnail and a product mockup.
- Two big buttons at the top: Buy now and Sell this.
Same flow, but it should plan for a PNG with transparency and show a checkerboard-style preview when relevant.
Should work for supported calendar types. If you ask for a “wall calendar 2026” that isn’t built yet, Copilot should explain what is available (e.g. desk calendar) instead of saying “we don’t support products.”
Copilot should check capabilities and respond with honest alternatives—hoodies may be on the roadmap—with similar supported types (shirt, sweatshirt, etc.), not a flat “unavailable.”
Same confirm → mockup flow as mugs. Pillow should appear in Try another product and in “what can I create?” listings.
Holiday decor homography mockup (not a flat poster fallback). Confirm plan before tokens are spent.
Should resolve to live pet SKU pet_bandana_collar. Staged-off pet products (bowl, leash) should not be offered as available.
Buy now, Sell this, and Publish
Every product preview card should offer two clear paths:
- Buy now — you order one item for yourself (Stripe checkout in a new page).
- Sell this — Pixerr adds the design to your shop, usually with all size/color variants.
Buy a sample for yourself
What you do: Click Buy now on the preview card (or say “I want to buy this mug”).
- Brief “thinking” message, then your browser goes to Stripe’s checkout page (secure payment—not a credit card form inside the chat).
- If the product wasn’t in your store yet, Pixerr prepares it behind the scenes first, then checkout opens for the variant you picked.
- After payment, you land back on Pixerr; Copilot should open and say payment went through, with an order reference when possible.
- If you cancel checkout, you return to Pixerr with a friendly “cancelled” message—the preview is still in the chat.
Sell it in your shop
Or click Sell this on the card.
- Copilot may ask you to confirm (medium-risk action).
- After confirm: a success card with View product page (opens
/shop/{your-store-slug}/{product-handle}in a new tab), View your store, and edit/variation actions. - Assistant message may include a clickable markdown link to the same product page.
- Preview card (
product_example_result) gains View product page when the product is already in your store. - Clicking Sell this again should say it’s already in the store—not create duplicates.
Should use the same add-to-store flow that creates the full variant set (S, M, L, colors, etc.), not only the one mockup you see.
Publish (make the listing public)
Sell this adds the product to your shop; it may still be private. Publish is the separate step that makes an eligible listing visible on your public storefront.
Or click Publish on the preview card (shown after the product is in your store).
- Agent path: confirmation plan, then success—or a clear message if the store or listing is not eligible yet.
- Card/rail path: direct API; assistant message or updated card reflects public status when allowed.
- Does not replace add-to-store; publishing without a store product should fail gracefully.
When the preview is in a different shop than Doggy Dogs, Copilot should not silently publish elsewhere. Expect: switch store, add-to-store in target shop first, or a clear “wrong store” message—not a fake success.
Storefront product links
Your live product page lives at /shop/{store-slug}/{product-handle}.
Your shop home is /shops/{store-slug} (note the extra “s”).
Creative collection pages are separate: /shops/{slug}/creative/{handle}.
Should call get_store_products and show a card listing products with buttons that open each product page at /shop/…—not generic text links with wrong paths.
Or click welcome chip Generate social posts / My product links when you have products in the active store.
- Copilot should load real handles from
get_store_productsfirst. - Copy should reference actual
/shop/{slug}/{handle}URLs—not invented product names.
After the mug is in your store, Copilot should answer with the canonical product URL. Bare paths in chat (e.g. /shop/doggy-mugs/monday-mug) should become clickable links in the thread.
Continuity and workspace rail
After you generate a collection or several mockups, Copilot should remember what you are working on—without you re-describing the whole project every turn.
Should name the active prompt collection (AI artwork set), image count, and recent mockups—not confuse it with a storefront product grouping called “Collections.”
Should summarize drafts: previews not in the store, or store products not public—aligned with the draft count on the workspace rail when possible.
Or click Continue on the rail (prefills this line). Should re-mock the same collection images onto a new product type—not start a brand-new collection plan.
Should describe the active preview (product type, in-store vs draft, public vs private)—using session/commerce memory, not a guess.
Gallery → product workflow
Expect a gallery picker card with thumbnails numbered 1–5 and image ids.
- No active preview: Select updates Copilot context only.
- With a pillow (or other) preview already in the thread: Apply to preview rerenders that card’s mockup.
- Multi-sided product: tiles also offer Apply to front / Apply to back.
Agent calls select_gallery_image. If a preview is active, it should apply artwork (card path or apply_gallery_image_to_product_example with confirm). The gallery picker card should not stay pinned on the next message.
After selection, expect a confirmation plan and product_example_preview with Awaiting confirmation—not a finished mockup and not “I’ve created a mockup…” until you click Confirm.
/uci/… on localhost); gallery picker repeats on every reply; “Add to Store” or “mockup created” before Confirm.
After artwork is selected, expect a batch plan card listing product types and token estimate, then Confirm to create multiple preview cards.
Listing metadata
Should call draft_product_listing (title, description, tags) and show copilot_listing_draft. Tap Apply to preview to save on the preview—not separate SEO fields or price changes.
With active preview: update_product_example_listing inline. After Sell this: update_store_product_listing with confirm (visibility changes are higher risk).
Double-sided products (pillows)
manage_product_example_surfaces → confirm plan → back matches front placement. Mugs should explain single wrap surface only.
Gallery picker Apply to back or surface tools with targetSurfaceId back.
Generate more like this
After a creative collection has finished generating, you can expand it with more images in the same style—without restarting from the style picker.
Or “expand this collection” / “same style, different pose.”
- Copilot should call
generate_more_like_this, notplan_creative_collectionfrom scratch. - Confirmation plan shows token estimate and which seed image (e.g. index 2) will anchor the new batch.
- After confirm: progress card → new thumbnails appended or new collection job, same style/concept context.
Creative collection pages (public)
Separate from grouping products in your shop: a creative collection page showcases the AI artwork set and story at a URL like /shops/your-store/creative/your-handle.
Typical flow:
- Confirmation plan (slug/handle, description).
- After confirm: a card with View public page (owner can open even before anonymous visitors see it, depending on publish flags).
- Social share and OG image:
/og/collection/{slug}.pngwhen published.
Batch publish for products linked to the prompt collection via lineage; partial success should list what failed (eligibility, store not live).
Pillows, holiday decor, and pets
These product families joined the live Studio manifest in May 2026. They use homography mockup templates (Pillows/, HolidayDecor/, PetProducts/).
Confirm → pillow mockup card. Same Buy now / Sell this / Try another product flow as mugs.
Should pick a holiday ornament SKU (not poster fallback). Mockup should follow the ornament shape.
Live pet product. Pet bowl, leash, and sweater are staged off—they should not show in catalog listing or Try another product until released.
After a mug or collection mock exists: reuses artwork via apply flow; new preview card for the stocking type.
Workspace rail (clicks, not typed)
Use the rail to sanity-check continuity and active storefront without typing.
- Continue — prefills “Continue this collection on another product” in the input.
- Mock all — same as grid “Mock all on {product}” (direct API, one mockup per collection image).
- New collection — prefills “Start a new collection”.
- View store — opens the active shop URL in a new tab.
- Switch store — prefills “Show my stores” (store list card in chat).
- Plan hint — e.g. “2 of 2 storefronts · plan limit reached” when at cap.
- Open / Sell / Share on a recent preview — Studio, add-to-store (active shop), or share-copy card. Recents are filtered to the active store.
- In-store preview titles in the rail are clickable links to
/shop/{slug}/{handle}when the product exists in the store.
Moving art on the mockup (not resizing the file)
These change how your design sits on the product photo—centered, bigger on the mockup, rotated. The original PNG file does not get cropped by these buttons.
Or click Center on the card (secondary row).
- The mockup image updates; the small “source artwork” thumb should look the same.
Or Fit safely. Mockup should show a safe default placement (not cut off by the print area).
Or Expand 5%. Only the composition on the product changes.
Use overflow actions Rotate left / Rotate right if shown.
Fixing the artwork file itself
These live under overflow labels like Prep:—they change the actual image (margins, shrink pixels, transparency cleanup), often via Studio or regenerate.
Or Prep: fit margin. The source artwork should change; mockup may refresh.
Prep shrink—not the same as “Shrink 5%” on the mockup, which only zooms on the product photo.
Or click Fix transparency on the card.
- Confirmation plan (uses tokens).
- New artwork + updated mockup after confirm.
Should trigger regenerate, not silently move the mockup.
Open in Studio
Studio is the full editor. Copilot’s Open in Studio is a secondary button so it doesn’t compete with Buy now / Sell this.
What you do: Click Open in Studio on the preview card.
- Pixerr Studio opens with your artwork and product type.
- You can fine-tune placement, run print prep, save.
- When you close Studio, Copilot syncs—your mockup in the chat should reflect what you left.
Or use overflow Fine-tune in Studio, which may open Studio already in placement-edit mode.
Same design, different product
Or click Try another product.
- Copilot reuses your artwork when possible (saves tokens).
- A new preview card for the poster.
Should pick up the current session’s product example, not an old unrelated design. See also Continuity for “what did we just make?”
I already have an image
What you do: Attach or upload an image in Copilot.
- Card says upload succeeded; shows size/aspect if available.
- You pick a product (mug, case, etc.).
- Preview card appears with Buy now, Sell this, Open in Studio.
Should guide you to pick another product type or use Try another product after a preview exists.
Collections and themed sets
Typical flow:
- Style picker if you haven’t chosen a style yet.
- You pick watercolor (or say the style).
- “Give me ideas” → several concept titles.
- You pick one concept → plan for 1–6 images → confirm → progress → thumbnails.
- Then: “Put these on mugs” → plan → confirm → product previews.
After a style is set, Copilot should update style—not show the style picker again unless you ask to browse styles.
Should ask or use count 1–6 in Copilot chat before planning generation.
After thumbnails exist: should re-mock the same images (direct API or collection apply)—not restart style/concept picking. Workspace rail Mock all should match the product you named.
Multi-store (list, switch, create)
If you have more than one storefront, Copilot tracks an active store for this chat (same cookie as the Dashboard). Switching updates the cookie, conversation record, workspace rail, and which shop receives new products.
Should call get_stores and show a Your storefronts card (copilot_store_switcher) with each shop, public product count, Active/Default badges, and Switch to … buttons—not the old stub message.
Should call get_active_store and answer with the active shop name, slug, and lifecycle—or an copilot_active_store card with Open shop / View products / Switch store.
Should call switch_store with fuzzy name match. On success:
- Short assistant message (“Switched to Doggy Mugs”).
copilot_active_storecard (optional).- Workspace rail updates to Doggy Mugs; recent previews filter to that store.
- Designer/Dashboard cookie matches if you open the gallery elsewhere.
If two shops match (“Doggy Mugs” and “Doggy Dogs”), Copilot should not pick one silently. Expect a clarifying question or the store switcher card again.
Should list top products in the active storefront (get_store_products) with a copilot_store_products card. Each row opens /shop/{slug}/{handle} in a new tab—not /shops/{slug}/{handle}.
Confirmation plan (medium risk) → after confirm, new shop created via StoreService. If you are at plan cap (e.g. Creator = 2 shops), expect copilot_store_limit with upgrade link—not a generic error.
Should explain that moving products between storefronts is not supported and suggest: switch to the target store, then Sell this / create a new product there. No fake “moved” success.
POST /api/copilot/active-store (sets cookie + conversation). View products on the active-store card prefills a chat message. See store card phrases.
Store setup and going live
Should explain Stripe Connect in calm language—what’s missing, what to click—not blame you.
Uses live status from tools; may show a setup card if restricted.
Checklist style: store image, products, Stripe, email verification—as facts allow.
Should not say you’re live unless the store really is published.
Flash sales
Copilot should call the sale tool and show a confirmation plan—not say the sale is active until you confirm.
(Right after it asked how long.) Should set a 2-minute countdown sale, not just say “OK” without doing anything.
Should disable the flash sale and confirm it’s off.
Wall art and wallpaper packs
Draft pack card → you confirm → pack saved. Should not claim it’s saved before confirm.
Similar draft/confirm pattern for wallpaper packs.
When something goes wrong
Card may say mockup pending; you can retry mockup or open Studio. Artwork asset should still exist.
What you do: Click retry on the mockup (if offered).
Mockup image should refresh without regenerating the whole design.
Should use status tool, session, or commerce memory—not say “I don’t know” if the preview still exists in the database.
What you do: Refresh the browser mid-session after a collection + mockups.
History reload should restore messages; workspace rail should show the same active collection and recent previews (requires commerce-memory schema deployed).
When a confirmation plan is showing, Cancel should drop the plan without charging tokens or creating products.
Signed out vs signed in
What you do: Open Copilot while logged out; ask a simple question.
You may get a few public messages, then a prompt to sign in for product creation, Buy now, or Sell this.
What you do: Sign in and repeat “Put my design on a mug.”
Full flow with confirmation and cards should work.
Quick day-in-the-life test (30 minutes)
Run this once before a release:
- Say hello; ask what products exist.
- Generate a mug preview; confirm.
- Click Center, then Fit safely—mockup only changes.
- Click Sell this; confirm; open product link.
- Click Publish (if shown); confirm when agent asks.
- Click Share or ask for Reddit copy; copy text from card.
- Click Buy now; complete or cancel Stripe; return to Copilot.
- Say “try it on a poster”; confirm new card.
- Open in Studio; nudge placement; close; check chat mockup updated.
- Ask “what did we just make?” — check workspace rail matches.
If all ten feel smooth, core Copilot commerce and product flows are in good shape for most creators.
Commerce memory path (extra ~15 min)
- Make six images in watercolor; confirm generation.
- Make 3 more like the second one; confirm expansion plan.
- Mock all on mugs; confirm rail shows collection + recent previews.
- Refresh page — rail and history should still reflect the collection.
- Sell one mockup; Publish; Share copy.
- Create a public page for the collection; open the link.
Multi-store path (extra ~10 min, two shops)
- Ask “Show my stores”; click Switch to … on the card.
- Confirm workspace rail shows the new shop + plan hint.
- Create a mug; Sell this — product should land in the active shop.
- Switch shops; ask “Show products in this store.”
- Ask to move the mug to the other shop — expect not-supported guidance.