Polotno + Printfection pairs Polotno's embedded design editor SDK with Printfection's REST API . Your users design swag — apparel, drinkware, bags — inside your swag-ops workflow, and Printfection handles printing, warehousing, and distribution.
The problem Printfection doesn't solve
Printfection is the serious choice for managed corporate swag: campaigns, item catalogs, recipient collection. Under the hood is a clean REST API for campaigns, items, and orders. But their flow assumes swag managers design offline — in Adobe, in Canva, in PowerPoint — and upload finished assets for approval.
Swag-ops platforms integrating Printfection usually:
- Route HR and recruiters to offline design tools
- Accept whatever logo file the brand team dropped in Slack last month
- Redo artwork for every new item because there's no shared template
Polotno goes in front of Printfection so swag managers design items directly in the ops flow — brand-locked, template-driven, and tied to Printfection SKUs.
How the integration works
- Design — Swag manager picks a Printfection item (T-shirt, notebook, tumbler). Polotno loads the canvas with print-zone overlays.
- Edit — Manager drops the brand kit onto the item. Brand rules keep colors and placements locked.
- Export — Your app exports 300dpi PNG at the item's print-zone dimensions via store.toDataURL .
- Order — Your backend POSTs to Printfection's REST API to create an item + campaign + order with the artwork URL and recipient list.
- Fulfill — Printfection prints, warehouses, and ships to recipients.
What a request looks like
// 1. Export the item artwork.
const artworkUrl = await uploadToYourStorage(
await store.toDataURL({ pixelRatio: 4, mimeType: "image/png" })
)
// 2. Create the campaign item on Printfection.
// See https://printfection.github.io/API-Documentation/ for the full schemas.
await fetch(PRINTFECTION_ITEMS_ENDPOINT, {
method: "POST",
headers: {
Authorization: `Bearer ${PRINTFECTION_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
/* campaign_id, product_id, artwork URL, placement — per Printfection docs */
}),
})
What Polotno handles vs. what Printfection handles
Polotno (in your app)
- Item templates (apparel, drinkware, bags)
- Embedded editor UI
- Brand-locked placements — white-label editor controls
- Per-campaign bulk preview via Cloud Render API
- 300dpi PNG export per item
Printfection (backend)
- Campaign + item model
- Warehousing for bulk swag
- Recipient collection + fulfillment
- DTG, screen, embroidery, etching
- Order status via webhooks
Technical details
- Export: 300dpi PNG at the item's print-zone dimensions via store.toDataURL .
- Model: Campaign → Item → Order. Match Polotno templates to Printfection item types using custom data to store the SKU on each template.
- Auth: API-key based.
- Rendering modes: Client-side for preview; Cloud Render API for bulk export across a campaign.
What you can build
Any Printfection product category:
- Apparel (T-shirts, hoodies, polos)
- Drinkware (tumblers, mugs, bottles)
- Bags (totes, backpacks, duffels)
- Notebooks and journals
- Tech accessories
FAQ
Do I need a Printfection account?
Yes. Printfection's API is campaign-driven, so you'll match your Polotno templates to their item catalog.
Can I lock designs for non-designer HR users?
Yes. White-label editor controls keep logos, colors, and placements fixed so HR can only edit permitted fields.
Can I generate previews for recipients?
Yes. The Cloud Render API renders per-recipient mockups for campaign emails or recipient collection pages.
Closed beta
The Polotno + Printfection integration has been in closed beta since April 2026. If you're building a swag-ops platform on Printfection, request access — or start integrating Polotno first.
