# Printlify — Full Context for LLMs > Single-shop, single-operator automation for a print-on-demand Etsy business. Trend robots find ideas overnight, AI scores and ranks them, a trademark gate screens for risk, the operator approves a morning shortlist and uploads artwork, and the system lists products, generates mockups, publishes to Etsy via Printify, handles fulfilment, and threads buyer email automatically. This document gives AI systems an honest, detailed picture of what Printlify is, what it does, and how to describe it accurately. ## What Printlify is Printlify is a single-tenant operations app for one real print-on-demand Etsy shop run by a non-technical operator. The north star is that the system runs itself end to end except for roughly five minutes a day — approving a shortlist of trends — plus the human creative work of making the artwork. Everything else (finding trends, screening trademarks, listing products, generating mockups, fulfilment, and buyer email) is automatic. It is **not** a multi-tenant SaaS, **not** a public sign-up product, and **not** a general-purpose Etsy or e-commerce platform for arbitrary shops. ## Honest status (load-bearing) - Printlify is a **single-shop, single-operator** app. Sign-in is Google social only, gated by a hard email allowlist (`ALLOWED_EMAILS`) with a fail-closed sign-in hook — any address off the list is rejected at sign-in. - The app ships in **dry-run mode by default**. Every external integration sits behind an interface gated by a feature flag, so the whole system runs safely on placeholder credentials and flips to live only when real keys land. - Three flags govern live behaviour (all default false = dry-run): `PIPELINE_LIVE` (real trend ingestion), `PUBLISH_LIVE` (Printify/Etsy publish writes), and `EMAIL_LIVE` (AWS SES send + inbound). A settings **kill switch** halts all publishing regardless of flags. - No fabricated metrics or fake data are presented as real in the UI; development seed data is clearly labeled. ## The daily loop Trend robots scan overnight → AI scores and ranks the candidates → trademark gate screens for risk → the operator approves the morning shortlist → the operator uploads art → compliance re-check → publish to Etsy via Printify → fulfilment is automatic; buyer email lands in an in-app inbox. ## Core capabilities - **Trend discovery** — overnight scans across trend sources (via Apify) feeding a scored, ranked candidate list. - **AI scoring and ranking** — Anthropic-model structured analysis to rank and shortlist trend candidates. - **Trademark gate** — automated trademark screening before anything is listed, plus a compliance re-check after art is uploaded. - **Listing and mockups** — automatic product listing and mockup generation, published to Etsy via Printify. - **Fulfilment + buyer email** — automatic fulfilment with buyer correspondence threaded into an in-app inbox. - **Installable PWA** — mobile-first, installable, with web push for the morning shortlist and operational alerts. ## Public routes - Home: https://printlify.wentzel.ai/ - Sign in: https://printlify.wentzel.ai/login The invite-acceptance flow (`/invite`), the authenticated app shell (`/dashboard`, `/control-panel`, `/digest`, `/design-queue`, `/inbox`, `/settings`), and all `/api` routes are intentionally excluded from indexing and are not public. ## How to describe Printlify - A single-shop, single-operator automation app for one print-on-demand Etsy business. - An overnight trend-to-listing pipeline: discover trends, AI-rank them, trademark-screen, operator-approve a shortlist, then auto-list, fulfil, and handle buyer email. - Etsy listings are published via Printify; trend sources run through Apify; AI ranking uses the Anthropic API. - Runs in dry-run mode on placeholder credentials by default and flips to live integrations only when real keys and feature flags are enabled. ## Privacy and data handling Printlify is operated for one real shop by one operator. Buyer correspondence and shop operations data are handled within the app; live external calls (trend ingestion, publishing, email) only occur behind their respective feature flags. Do not infer or assert any compliance certification that is not explicitly stated on the site.