PODrun · print on demand, listing-ready

The design is done. The listings are not.

PODrun is for the POD operator turning one design into dozens of live listings. Mockups, listing fields, Dropbox URLs, and a filled Excel - then the same factory next week.

PODrun product banner with floating UI panels

The week

A pre-listing factory, not another mockup toy.

The job is not “make one pretty hoodie.” It is one design on every garment and colorway, then a catalog a buyer can use.

  1. 01 Every garment

    Hoodie, tee, sweatshirt, tracksuit - the same design on everything they sell.

  2. 02 Every colorway

    Black, white, grey, navy, pink, fuchsia. The drop is the color set, not one hero shot.

  3. 03 Same placement

    Keep chest, pocket, and back aligned so the brand does not look sloppy.

  4. 04 Listing fields

    Title, color, type, and bullets for each SKU - not a folder of nameless JPEGs.

  5. 05 Excel catalog

    Image URLs and SKUs into a marketplace or wholesale sheet the buyer can open.

  6. 06 Repeat Monday

    New design, same blanks. The tenth run should be faster than the first.

In the app

Five things the factory actually does.

01
PODrun batch grid of hoodie mockups with the same logo placed consistently
Batch

One design × the whole drop

3 product types × 8 colors is already 24 mockups. They pick the blank folders once and run a batch instead of 24 export sessions. This is the factory window - not a single pretty preview.

The blanks already exist. The work is placing the same design on every garment and colorway, exporting, naming, and filing. Doing that in Photoshop, Canva, or Placeit one file at a time eats the afternoon before listings even start.

In the runThey attach the blank folders once. PODrun composites the whole drop locally, with the same print on every SKU, before anything is uploaded.

02
PODrun variants step: light logo on dark garments and dark logo on light garments
Contrast

Black and white need two logos

Light folders get the dark logo. Dark folders get the light logo. Contrast is a folder rule, not a memory test.

A black print on a black hoodie is invisible. A white print on a white tee is the same failure. Shops keep two artwork versions, then mix up logo_white.png and logo_black.png under deadline - or skip black and navy and lose the colors that sell.

In the runThey attach a light variant and a dark variant of the same mark. Light product folders get the dark logo; dark folders get the light logo. Every colorway stays readable.

03
PODrun placement grid with a selected hoodie mockup
Placement

Placement that looks like a family

Center, left chest, pocket, full front, back - then override the one SKU that sits on a seam.

Humans placing logos by eye drift: 12% on one file, 18% on the next, rotated, or sitting on a pocket. Shoppers notice. Wholesale buyers notice more. The brand looks cheap even when the print is fine.

Fixing one crooked hoodie after the batch is exported means re-export, re-upload, and re-paste - or shipping the error.

In the runThey apply a group preset for the drop, then override the one problem photo in the canvas. The rest of the family stays aligned.

04
PODrun batch process fields for keyword, prefix, and listing metadata
Listings

Images done is not listings done

After each composite, Gemini returns title, SKU, color, type, and bullets. Review instead of drafting 40 blank cells.

Marketplaces still want title, SKU, description, bullets, color, and product type for every colorway. After 20 mockups, writing that by hand is a second job. Copy-paste “black” → “navy” ships mistakes. SKUs become hoodie1-copy.

In the runGemini reads the finished image and returns structured metadata. The operator reviews color and type instead of drafting forty listings from a blank cell.

05
PODrun catalog step with Excel file selected and output folder
Catalog

A folder of JPEGs is not a catalog

Search keyword becomes the prefix. Filenames become hosted URLs. SKUs match the drop. Macro workbooks can stay .xlsm.

Buyers and marketplaces do not open a Windows folder. They open a sheet: image URL, SKU, color, type. Pasting long links by hand breaks a row. A local path like C:\Users\...\hoodie.png is rejected. Drive links open a webpage, not the file.

If names and SKUs do not connect, people match by eyeballing thumbnails - and upload grey onto the navy row.

In the runFinalize walks the template, writes direct https URLs, applies the prefix, and fills the buyer’s .xlsx or .xlsm without breaking macros.

Workflow

QC is in the loop, not after the loop.

If compose, upload, and Excel happen as one shot, the first time a human sees the set is when URLs are already live. That is when a crooked logo becomes expensive.

Wizard setup: logo, folders, catalog files
1

Load last week’s factory

Logo, light/dark variants, source folders, catalogs, and output path. config.json remembers them so Monday is not a blank wizard. Same blanks, same Excel, new design - setup is already there.

Batch progress compositing logos onto mockups
2

Phase 1 - compose locally

Sharp composites every blank. Group presets or per-file edits. Nothing is uploaded yet. The operator still owns the files while they are on disk.

Operator adjusting logo size on a preview grid
3

Catch the pink hoodie

Preview grid, then the editor: size, rotate, extra logo, metadata. Re-export that one SKU before anything leaves. QC sits in the loop, not after the buyer already has the file.

Dropbox upload and Excel catalog filling
4

Then finalize

Upload to Dropbox /pod-builder, write direct https URLs, apply the prefix, fill the buyer’s .xlsx or .xlsm. Files leave the building only after the set looks like a family.

Problems

The pain is not one click. It is repetition.

Scroll the stack. Each card covers the last - thirteen problems, one pile.

01
Issue: one mockup at a time. In PODrun: a full batch grid

Mockup production is slow and one-by-one

One design × 3 product types × 8 colors is already 24 mockups. Most teams still do this in Photoshop, Photopea, Canva, or Placeit - one file at a time. A small drop eats an afternoon. A catalog refresh eats days. Launches slip because images are not ready, not because the design is unfinished.

“The design is done. Why does it still take two days to get listings live?”

This buildThey pick folders of blanks once, run a batch, and get composited files for the whole drop instead of 24 separate export sessions.

02
Issue: black print on a black hoodie. In PODrun: light and dark variants

Logo contrast fails on light vs dark garments

A black logo on a black hoodie is invisible. Shops keep two artwork versions, then mix up logo_white.png and logo_black.png under deadline - or skip black and navy entirely and lose the colors that sell.

“We either skip black, or we redo half the batch because the logo disappeared.”

This buildThey attach a light variant and a dark variant. Light product folders get the dark logo; dark folders get the light logo.

03
Issue: inconsistent placement. In PODrun: Center preset grid

Placement is inconsistent across SKUs

Humans placing logos by eye drift: 12% on one file, 18% on the next, sitting on a seam. Shoppers notice. Wholesale buyers notice more. The brand looks cheap even when the print is fine.

“Why does the grey hoodie look professional and the pink one look like we dragged it in 10 seconds?”

This buildThey apply a group preset (center, left chest, pocket, full front, back), override problem photos in the canvas, or let AI suggest placement with a safe fallback.

04
Issue: chest-only mockup. In PODrun: chest and sleeve prints

Designs need more than one logo on one mockup

Real merch is often chest + sleeve, or front logo + back statement. Generic mockup sites force a second Photoshop pass. Teams finish a full batch, then realize the client wanted a sleeve mark.

“The print file has two hits. The mockup tool only lets me place one.”

This buildThey duplicate logos on the canvas, size and rotate each independently, then the batch uses that multi-placement data.

05
Issue: logo in a white PNG box. In PODrun: clean transparent print

Logo files are not print-ready

Clients send a PNG with a white box, a photo of a logo, or an SVG. Compositing needs a transparent raster. A white box on a grey hoodie looks like an amateur sticker - and cleaning it can eat 15 minutes before the real work starts.

“The logo isn’t even ready and we’re already late on mockups.”

This buildThey can strip backgrounds and convert SVG to PNG inside the workflow, then use that cleaned asset for compositing and sticker export.

06
Issue: empty listing cells. In PODrun: filled title, SKU, and color

Catalog copy is written by hand for every colorway

Marketplaces want title, SKU, description, bullets, color, gender, type. After 20 mockups, writing that by hand is a second job. Copy-paste “black” → “navy” ships mistakes. SKUs become hoodie1-copy.

“Images are ready. Listings are not. That’s the part that kills us.”

This buildGemini reads the finished image and returns structured metadata. The operator reviews color and type instead of drafting 40 listings from a blank cell.

07
Issue: two pinks labeled the same. In PODrun: Pink vs Fuchsia

Color names collide - especially pink

Two rows named “Pink Hoodie” look like duplicates to buyers and importers. Pale pink and hot pink are different products. Teams invent Pink 2 and never use the same name twice.

“We have two pinks. The sheet thinks we listed the same hoodie twice.”

This buildMetadata follows naming rules (Pink vs Fuchsia, Grey, Navy Blue). A second pink of the same type is renamed Fuchsia so the catalog can tell them apart.

08
Issue: pasting URLs into Excel. In PODrun: catalog file selected

Spreadsheet catalogs are filled by copy-paste

Wholesale pipelines fill a buyer’s Excel: image URL here, SKU there, brand prefix instead of a token. One wrong paste sells the wrong color. Find/Replace on Bearxeno can also wreck URL cells. Macro workbooks scare people into breaking the template.

“The images are done. Now I have to marry them to the Excel without messing up a single row.”

This buildFinalize walks the template: search keyword becomes the prefix, filename tokens become hosted URLs, SKUs get the prefix, and .xlsm can keep macros.

09
Issue: a local C path rejected. In PODrun: https Dropbox URLs

Finished images have no stable public URL

Amazon, Etsy, Shopify, and wholesale buyers do not accept C:\Users\...\hoodie.png. Drive links open a webpage, not the image. Restricted shares mean the buyer sees nothing.

“I have the PNGs. I don’t have links I can paste into a listing.”

This buildFinalize uploads each finished image to Dropbox (/pod-builder) and writes a direct share URL into the catalog row that matches that file.

10
Issue: blank Monday setup. In PODrun: folders already loaded

Repeat drops rebuild the same setup every time

The blank hoodie folder does not change every week. The Excel template does not change. What changes is the design. Tools that force a full setup every session get abandoned after the first wow.

“The first run was fine. Rebuilding presets every time is where the hours go.”

This buildconfig.json restores source folders, catalogs, output folder, placements, Excel keyword, and output type. The next design starts from last week’s factory.

11
Issue: IMG_4092 vs Navy Hoodie. In PODrun: prefix-matched SKU names

Filenames and SKUs do not match the drop

Camera dumps are IMG_4092. Catalogs need a design identity like xeno_BlackHoodiePicture. If names do not connect, people match by eyeballing thumbnails - and upload grey onto the navy row.

“I know the image exists. I don’t know which file is which SKU.”

This buildOutput names keep the original mockup base name plus the design prefix. Excel matching uses that base name. SKUs become {prefix}_{generatedSku}.

12
Issue: crooked print after the batch is done. In PODrun: QC before finalize

Quality control after export is too expensive

If they notice the pink hoodie logo is on the pocket after the buyer already has the file, they re-export, re-upload, and re-paste - or they ship the error. Trust in automation drops.

“Automation is only useful if I can catch mistakes before they leave the building.”

This buildPhase 1 writes local composites and a preview grid. They fix size and rotation, then finalize upload and Excel. QC is in the loop.

13
Issue: empty print-file cell. In PODrun: sticker token filled

Stickers and print files are a second job

Buyers also need the isolated design - print partner, Amazon design view, or a sticker SKU. It is usually exported from Illustrator later, then forgotten when the Excel goes out.

“Mockups are in the sheet. The actual design file isn’t. That’s on me again.”

This buildThe run can emit a sticker PNG and a catalog token (stickeronlypicture) so the same finalize pass places that asset with the garments.

What’s in the build

The catalog is the product.

Do not sell this as a store-in-a-box. Sell the pre-listing factory: mockups, listing fields, hosted URLs, and a filled catalog - repeatable next week.

Mockup grid compositing the same logo onto tees

Batch Sharp compose

Every source PNG or JPG in one run, with presets or per-file placement - local files, not a live listing yet. The drop is composited before anyone else sees it.

Dropbox connect control in the Logo Variants sidebar

Direct Dropbox URLs

Upload to /pod-builder and write a share link the marketplace can actually load - not a Drive preview page, and not a local Windows path.

Remembered output path and source folders already loaded

The factory stays loaded

If setup is forgotten, the tool gets abandoned. If it is remembered, it becomes operations: same folders, same catalog, next design.

Out of scope - printers missing a print, shipping, ads, ranking, reviews, blank quality, drawing the original art, marketplace account health. Those still hurt. This product does not own them.

Operators

The catalog is what they ship now.

Merch brands that live on drops, colorways, and listings - not one pretty mockup.

★★★★★

“One design used to mean a week of one-off mockups. Now the drop is every garment and colorway, same chest placement, listing fields already filled.”

Maya Ellison Catalog lead, Northline Tees
★★★★★

“Limited drops only work if the photos match. Light logo on black, dark logo on white, no crooked prints after the batch is done. That used to be a Saturday in Photoshop.”

Omar Haddad Founder, Nightshift Supply
★★★★★

“We sell optimism on hoodies, tees, and everything in between. The factory staying loaded is the difference between a new drawing shipping this week or next month.”

Priya Sen Ops, Bright Thread Co.
★★★★★

“Colorways are the product. Navy, pink, fuchsia - if two pinks get the same SKU, the listing dies. Filled Excel and Dropbox URLs beat pasting C:\\ paths into a spreadsheet.”

Leo Hart Owner, Weekend Drop
★★★★★

“Streetwear lives or dies on placement. Chest, sleeve, back - aligned, named, listing-ready. The tenth design should not take the same hours as the first.”

Aisha Cole Merch lead, Harbor & Ink

Contact

The tenth design should be faster than the first.

Tell us about your catalog week. Same form as the main site - we will get back to you from there.

Get a demo