Polotno + Scalable Press pairs Polotno's embedded design editor SDK with Scalable Press's developer APIs . Your users design on a wholesale catalog, your backend quotes and places the order, and Scalable Press prints and drop-ships.
The problem Scalable Press doesn't solve
Scalable Press gives partners a serious wholesale stack: thousands of products, live pricing quotes, and a quote-before-order flow. But dropshippers and print brokers integrating that stack into client apps get catalog and fulfillment — not design UX. Their customers still need a place to actually compose artwork.
Brokers building on Scalable Press without a design layer usually:
- Ask end customers to upload completed artwork
- Build simple logo-placement tools and lose multi-placement work
- Skip apparel variants because per-garment setup is manual
Polotno goes in front of Scalable Press so brokers can ship end-to-end brand-builder apps on top of the wholesale catalog.
How the integration works
- Design — User picks a Scalable Press garment SKU. Polotno loads the canvas with print-zone overlays and placement guides.
- Edit — User composes artwork across placements (front, back, sleeve, leg).
- Export — Your app exports 300dpi PNG per placement via store.toDataURL .
- Quote — Your backend calls Scalable Press's Quote API with SKU, quantity, and placements to get live pricing before charging the customer.
- Order — Your backend POSTs the order to Scalable Press with artwork URLs and shipping.
- Fulfill — Scalable Press prints and drop-ships.
What a request looks like
// 1. Export per-placement artwork.
const frontPng = await frontStore.toDataURL({ pixelRatio: 4, mimeType: "image/png" })
const frontUrl = await uploadToYourStorage(frontPng)
// 2. Quote first, then order.
// See https://scalablepress.com/docs/ for the full schemas.
const quote = await fetch(SP_QUOTE_ENDPOINT, {
method: "POST",
headers: { Authorization: `Basic ${SP_API_KEY}`, "Content-Type": "application/json" },
body: JSON.stringify({ /* SKU, quantity, placements */ }),
})
await fetch(SP_ORDERS_ENDPOINT, {
method: "POST",
headers: { Authorization: `Basic ${SP_API_KEY}`, "Content-Type": "application/json" },
body: JSON.stringify({ /* items with artwork URLs, shipping */ }),
})
What Polotno handles vs. what Scalable Press handles
Polotno (in your app)
- Garment + promo-product templates
- Multi-placement design canvas
- Embedded editor UI
- 300dpi PNG export per placement
- Brand locking for broker clients
Scalable Press (backend)
- Wholesale product catalog
- Live pricing via Quote API
- DTG, screen, embroidery
- Drop-ship fulfillment
- Order status webhooks
Technical details
- Export: 300dpi PNG per placement via store.toDataURL .
- Quote-before-order: Your backend calls the Quote API with placement and quantity data; Polotno has already validated the artwork spec before the quote goes out.
- Auth: Basic auth with API key — see Scalable Press docs .
- Rendering modes: Client, self-hosted, or cloud rendering .
What you can build
Any product in Scalable Press's catalog:
- Apparel (T-shirts, hoodies, long sleeves, tanks)
- Outerwear
- Bags and accessories
- Headwear
- Promotional products
FAQ
Do I need a Scalable Press account?
Yes, with API credentials. Their stack leans wholesale and enterprise.
Does Polotno support their quote-before-order flow?
Yes. Your backend calls the Quote API with placement and quantity data; Polotno has already validated the artwork spec before the quote goes out.
How many placements can I design per garment?
As many as the garment SKU allows — Polotno builds a canvas per placement.
Closed beta
The Polotno + Scalable Press integration has been in closed beta since April 2026. If you're a broker or dropshipper building on Scalable Press, request access — or start integrating Polotno first.
