How ShopPilot turns a product folder into a published Etsy listing
A ShopPilot run takes a folder of designs and returns a review-ready Etsy listing. Here is what happens at each stage, and where the seller stays in the loop.
Listing a print-on-demand product by hand is the same six or seven steps every time: size the artwork, drop it onto product photography, export the images, write a title, choose tags, write a description, set attributes, upload, publish. None of the steps is difficult. The cost is that they are repeated per listing, and a shop that publishes forty products a week pays that cost forty times.
ShopPilot collapses the repetition into a single run over a product folder. The run has four stages.
1. Design prep
The run starts from a folder of designs, or directly from the connected shop. Designs are curated, edited if needed, and locked to a fixed output size so every product image in the batch shares consistent dimensions. Getting this fixed early is what makes the rest of the run reproducible: variable input sizes are the usual reason a batch of mockups comes out inconsistent.
2. Mockups
Each prepared design is placed onto product photography to produce listing images. Placement is not a naive centred paste. For phone cases, the camera cut-out is treated as a protected zone: artwork is positioned so it clears the camera, and background fill extends to the edges rather than leaving the case border bare. Backgrounds can be swapped against saved presets, so a shop can restyle a whole batch without regenerating the underlying designs.
3. Listing copy
Title, tags, description, and attributes are generated together, from the product folder and the niche profile the run belongs to. Generating them in one pass rather than separately matters, because a title and its tags should agree with each other — writing them independently is how shops end up with tag sets that do not reflect what the title actually promises.
The prompts behind this stage are editable. A shop with an established voice is not stuck with a generic one.
4. Etsy draft, or publish
The finished listing is created through Etsy’s official API. By default the run stops at a review-ready draft: the seller looks at the result, keeps the good ones, and deletes the rest. Shops that have built confidence in a particular niche profile can turn on auto-publish, and finished runs go live without stopping.
That default is deliberate. The automation is in the preparation, not in the decision to publish. See draft-first versus auto-publish for how that choice is structured.
What the seller supplies
Listing folders — optionally, since a run can start from the shop — and a connected Etsy shop. The connection is made through Etsy’s own OAuth authorization screen; ShopPilot never asks for an Etsy password. The specific permissions requested are listed on Etsy permissions and explained in which Etsy API permissions listing automation actually needs.
After the sale
The same dashboard carries the rest of the loop: paid orders can flow to a print partner without copy-paste, buyer messages can be drafted for review, and per-shop analytics cover views, favourites, orders, and revenue by day.
The term ‘Etsy’ is a trademark of Etsy, Inc. ShopPilot uses Etsy’s API but is not endorsed or certified by Etsy.