A working demo, not a slide deck

Product data in, finished Etsy listings out.

One engine takes your product data and produces two things: the finished listing rendered as a buyer would see it, and the exact Etsy Open API v3 request body behind it – plus an importable Make.com blueprint so it runs in your own shop. Two demos below, each built around a real listing problem.

◑

Everything here runs on synthetic sample data. No real shop is touched and no personal data is stored. Each payload is validated against the live Etsy Open API v3 request schema. The only step that needs a shop is the final push, authorised once by the owner.

Variation inventory

56 Design × Size → one listing

A Google Sheet of 56 combinations, each with its own SKU and price, assembled into the exact updateListingInventory body – the part Etsy has no single module for.

Open the variations demo →

Print-on-demand SEO · Deutsch

One design → three SEO listings

A finished design becomes a title, 13 tags and an SEO description across t-shirt, hoodie and mug – in English and German, all within Etsy's field limits.

Zur POD-Demo →

What “working” means here

Real request bodies

The payloads are the actual Etsy v3 createDraftListing and updateListingInventory requests, validated field-by-field against the published OpenAPI schema.

Importable automation

Each demo ships a Make.com blueprint you can import and wire to your own Google Sheet and Etsy shop. The plumbing is done.

iii

Honest about the last mile

Etsy has no sandbox, so writing to a shop needs the owner's one-time OAuth. Everything up to that point is finished and visible here.