Polotno + Papello pairs Polotno's embedded design editor SDK with Papello's Print-on-Demand API. Your users design wall art, mugs, stationery, and frames inside your app, your backend submits the files to Papello, and Papello prints and ships.
The problem Papello doesn't solve
Papello handles the hard part of mixed-product POD — production and finishing across varied formats (rigid frames, mug wraps, flat prints, paper stationery). But their API receives files; it doesn't help you make them. Different products need different canvases, and that's where most mixed-product shops get stuck.
Teams building on Papello without a design layer usually:
- Ship a basic "upload your image" experience that underuses the catalog
- Build separate mini-editors per product format
- Rely on customers to understand bleed and aspect ratios before they order
Polotno goes in front of Papello so users switch between product formats in one editor, with the canvas reshaped and bleed enforced per product.
How the integration works
- Design — User picks a product (wall frame, mug, A5 notebook). Polotno loads the right canvas with bleed and safe-area guides for that product.
- Edit — User drops images, arranges layout. Switching products reflows the design to the new aspect ratio.
- Export — Your app exports the print-ready file — 300dpi PNG/JPEG via store.toDataURL for image products, PDF for stationery.
- Order — Your backend POSTs the order to Papello's POD API with the file URL, product SKU, and shipping address.
- Fulfill — Papello prints and ships. Your backend receives status updates.
What a request looks like
// 1. Export at 300dpi for image-first products.
const fileBlob = await store.toDataURL({ pixelRatio: 4, mimeType: "image/png" })
const fileUrl = await uploadToYourStorage(fileBlob)
// 2. Submit the order to Papello's POD API.
// See https://papello.com/print-on-demand-api for the full schema.
await fetch(PAPELLO_ORDERS_ENDPOINT, {
method: "POST",
headers: {
Authorization: `Bearer ${PAPELLO_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({
/* product SKU, file URL, shipping — per Papello's API */
}),
})
What Polotno handles vs. what Papello handles
Polotno (in your app)
- Embedded editor UI with per-product templates (frames, mugs, stationery)
- Aspect-ratio reflow across products in one session
- Bleed and safe area enforced per product spec
- Print-ready export (300dpi PNG/JPEG or PDF)
- Cloud rendering for bulk mockups
Papello (backend)
- Full POD catalog across wall art, mugs, and stationery
- Printing and finishing across varied formats
- Room-mockup preview for framed products
- Shipping and fulfillment
Technical details
- Export: 300dpi PNG/JPEG for raster products; PDF (with bleed + crop marks) for stationery.
- Per-product canvas: frame aspect ratios, mug wrap templates, stationery page sizes.
- Rendering modes: Client-side for preview; self-hosted or Polotno Cloud Render API for deterministic export.
What you can build
Any Papello product:
- Wall art — framed and unframed
- Mugs
- Picture frames
- Stationery — notebooks, cards
FAQ
Do I need a Papello account?
Yes — a self-serve Papello account with API access.
What file formats does Polotno export?
300dpi PNG/JPEG for raster products and PDF for stationery.
Does switching between products lose my design?
No. Polotno reflows the design onto the new aspect ratio so users can try a layout across product formats in one session.
Is this self-serve yet?
Not during the closed beta.
Closed beta
The Polotno + Papello integration has been in closed beta since April 2026. If you're building on Papello and need an in-app designer, request access — or start integrating Polotno first.
