| name | sales-printful |
| description | Printful platform help — print-on-demand merch fulfillment for creators/brands (apparel, accessories, all-over print) with a REST API (v2 beta + v1), signed webhooks, mockup generator, and store connectors for Shopify/WooCommerce/Etsy/Wix. Use when orders aren't appearing in Printful or SKUs aren't matching sync variants, an order is stuck in the failed state, a Printful webhook never fired and you need a polling backup, shipping takes too long and customers complain, building a headless store that creates orders via the API, generating product mockups programmatically, or choosing between the Free and Growth plans. Do NOT use for choosing between POD providers like Printify/Gelato/Gooten (use /sales-print-on-demand) or general digital-product pricing/launch strategy (use /sales-digital-products). |
| argument-hint | [describe what you need help with in Printful] |
| license | MIT |
| version | 1.0.0 |
| tags | ["sales","digital-products","platform"] |
| github | https://github.com/printful |
Printful Platform Help
Printful is a print-on-demand (POD) fulfillment service: you design custom products, Printful prints and ships them on demand, and you hold no inventory. It plugs into your storefront (Shopify, WooCommerce, Etsy, Wix, etc.) or runs headless via its REST API.
Step 1 — Gather context
If references/learnings.md exists, read it first for accumulated platform knowledge.
Ask only what you can't infer from the user's prompt:
-
What are you trying to do?
- A) Connect Printful to a store (Shopify/WooCommerce/Etsy/Wix/etc.)
- B) Build a headless/custom integration via the API (create orders, mockups, sync catalog)
- C) Fix a broken order, webhook, or sync
- D) Decide on a plan (Free vs Growth) or understand fees/margins
- E) Product, branding, or shipping questions
-
API version? v2 (beta, recommended for new builds — /v2/ paths, leaky-bucket rate limit, signed webhooks) or legacy v1.
Skip-ahead rule: if the user's prompt already has enough context, go straight to Step 2.
Step 2 — Route or answer directly
| If the user's question is about… | Route to |
|---|
| Which POD provider to pick (Printful vs Printify/Gelato/Gooten/SPOD) | /sales-print-on-demand {question} |
| Digital-product pricing, validation, launch strategy | /sales-digital-products {question} |
| Checkout-page conversion (order bumps, upsells, cart abandonment) | /sales-checkout {question} |
| Tax / Merchant-of-Record obligations on merch sales | /sales-merchant-of-record {question} |
When routing, give the exact command: "This is a {domain} question — run: /sales-digital-products {original question}"
Otherwise, answer Printful-specific questions directly using Step 3.
Step 3 — Printful platform reference
Read references/platform-guide.md for the full reference — capabilities & automation surface, pricing/plan gates, data model (catalog product vs variant, orders, mockups), and quick-start recipes (create an order, generate a mockup, listen for a shipment webhook).
For raw endpoint detail, auth, rate limits, and webhook payloads, read references/printful-api-reference.md.
