Integrations

Works with the equipment you already own

NestSheet is designed to sit between your order intake and your RIP without asking either one to change. Every major RIP, every major cutter, and every order-intake flow the industry actually uses.

RIP software

RIPs NestSheet exports to

NestSheet writes CMYK+W TIFF with embedded ICC, PDF with spot channels, and JPEG for sublimation — in exactly the shape the target RIP expects. No second export step, no manual channel fix-up.

MainTOP
Supported

CMYK+W, 6+W and 8-channel DTF configurations. Hot-peel and cold-peel film profiles.

Cadlink Digital Factory
Supported

Apparel and DTF editions. ICC embedded per job, white channel handed through as dedicated spot.

AcroRIP
Supported

DTF setup with variable-dot white opt-in. Native RIP preset on the export dialog.

Roland VersaWorks
Supported

VersaStudio, VersaEXPRESS and TrueVIS print-and-cut. CutContour spot colour exported on its own layer.

Mimaki RasterLink
Supported

UV, solvent and DTF. White / Clear channels via the RasterLink dictionary.

Fiery / CADlink
Supported

Fiery-driven engines and CADlink Digital Factory; single White + Varnish multiplexed internally.

PrintEXP
Supported

WHITE / VARNISH channel tokens, case-exact.

ColorLogic ZePrA
Supported

InkNames + DeviceN aware; White / Varnish tokens.

Mutoh VerteLith
On request

UV and solvent platforms. Spot_White and Spot_Varnish channel names — compatibility expanding.

Wasatch SoftRIP
On request

Apparel, DTF and dye-sublimation configurations — compatibility expanding.

Onyx Thrive / Rip Queue
Supported

Eco-solvent, UV and large-format print. Per-media ICC handed through on export.

Caldera
Supported

Textile, UV, signage.

Flexi (SAi Flexi)
Supported

Sign shops running print-and-cut pipelines.

Sawgrass Virtuoso
Supported

Small-shop sublimation.

Your RIP not listed?
On request

We verify against a real shop-side test file before claiming compatibility. Send us your RIP name and a sample expected output.

Cutter registration

Cutters and cut-contour formats

For print-and-cut and eco-solvent workflows, NestSheet generates registration marks in the format your cutter actually reads. Wrong marks = blind cutter = wasted sheet.

Roland (GX, GR, VG2, TrueVIS series)
Supported

Roland-native registration marks, CutContour spot colour.

Graphtec FC/CE/FCX series
Supported

ARMS registration marks, TIFF + cut-data pair.

Summa (S-Class, D-Class)
Supported

OPOS X / OPOS CAM marks.

GCC (Jaguar, Puma, AR-24)
Supported

AAS II registration marks.

Silhouette / Cricut
On request

Small-shop workflows via PDF + manual registration.

Order intake

Order intake and shop-management flows

NestSheet ingests your order list directly so gang sheets build themselves from the orders, rather than from a folder someone manually dragged files into.

CSV import
Supported

Any order intake that can export CSV — Shopify, WooCommerce, Etsy, BigCommerce, custom.

Zapier / Make / n8n
Supported

Webhook-based order trigger from thousands of sources.

REST API order submission
Supported

POST an order JSON to NestSheet and get back a ready-to-print gang sheet.

Printful / Printify style forwarders
On request

If you fulfil for them, we can ingest their order format on request.

Direct Shopify / WooCommerce plugin
On request

Planned — in roadmap.

API and automation

API surfaces for your own pipeline

If your shop has a developer, NestSheet exposes a REST API so the whole pipeline — order in, sheet out — can run unattended.

POST /nest
Supported

Submit an order, receive a packed gang sheet.

POST /remove-bg
Supported

Batch background removal for customer-uploaded artwork.

POST /uv-channels
Supported

Generate white and varnish channels for UV-DTF output.

POST /split-multi-sheet
Supported

Split an over-sized order across N gutter-safe sheets.

Webhook on export complete
Supported

Subscribe to notifications when sheets are ready or exports finish.

OpenAPI spec
Supported

Full schema downloadable, use it with your client generator of choice.

Don't see your RIP or cutter?

Send us your setup. We verify against a real test file before claiming compatibility — and "on request" is how most of the supported list started.