Navigate

hello@customei.apponline
Fulfilment & production

How the artwork reaches whoever makes it

This is the question merchants ask before they commit, so here is the straight answer: Customei does not want to own your supply chain. It renders a correct print file and delivers it to your production partner automatically — by bucket, API, signed link or webhook.

customeirenderedfileS3 BUCKETDIRECT APISIGNED URLWEBHOOK

Checkout to production

  1. 01

    Order paid

    Rendering is triggered by the paid-order webhook, so cancelled and fraudulent orders never consume a render or reach a printer.

  2. 02

    File rendered

    Lambda workers composite the layers at 300dpi, preserving colour spaces and fonts, and add bleed, safe area and cut paths per product type.

  3. 03

    Proofed, if you want it

    Auto-approve the simple orders; route anything with an upload or a long inscription to a review queue before production sees it.

  4. 04

    Delivered and recorded

    The file goes to your partner by S3, API, signed URL or webhook, and the delivery state is recorded against the order.

A — Delivery

Four ways the file lands

Pick whichever your partner already uses. Delivery state is recorded per file, so a missing order is a question you can answer rather than one you have to investigate.

S3 bucket
We write the print file straight into a bucket you own, in the folder structure your partner already watches. Most in-house and contract production runs this way.
Direct API
We POST the order, its option values and the file to your partner's endpoint, with retries and a recorded delivery state.
Signed URL
A time-limited link on the order, readable by your partner without an account. Right for large canvas and blanket files that should never be emailed.
Webhook
Subscribe to file-rendered and file-delivered events and pull into whatever system you already run.
print file+ order dataAPPAREL PARTNERRULE 1DRINKWARE PRESSRULE 2IN-HOUSERULE 3
Routing rules per vendor and product type

B — Production

Your printer, your call

Customei takes no cut of production and has no preferred supplier. In-house presses are a first-class case, not a fallback.

Bring your own fulfilment
Your press, your contract printer, your existing supplier. This is the default and the best-supported path — Customei's job ends when the correct file is in their hands.
In-house production
A first-class case, not a fallback. Files land in your bucket, the order dashboard is your work queue, and routing rules replace the person sorting emails.
POD networks
Direct integrations are in progress. Until one exists for your partner, the S3 and API paths already deliver to them — tell us who you produce with and it moves up the list.
Multi-vendor
Route by vendor, product type or tag, so apparel reaches one partner and drinkware another without anyone sorting a queue.
submittedRosalindAUTO-APPROVEREVIEW QUEUErules decide which
Proofing rules decide what a human sees

Straight answer

About the partner network

We would rather be straight about this than print logos we have not earned. Customei is fulfilment-agnostic by design: the print pipeline delivers to any partner who can accept a file over S3, an API, a signed URL or a webhook — which in practice is all of them. Named, one-click integrations with specific POD networks are in progress, and the order we build them in is set by which partners our merchants actually use.

What every file guarantees

Print-ready means print-ready

Bleed, safe area and cut paths are applied in the file rather than described in an email. Fonts are embedded or outlined — never silently substituted.

Every print file
Resolution
300 DPI at final print size (150 DPI accepted above 100cm)
Colour
sRGB in, original colour space preserved; substrate profile applied at production
Fonts
Embedded or outlined — never substituted silently
Layers
Layered output where the process needs it; flat where it does not
Geometry
Bleed, safe area and cut paths generated per product type
Naming
Order number, line item, panel and product type in the filename

Full per-product tables: https://docs.customei.com/print-files

Specs by product type

  • 300 DPI · 3mm wrap bleed · per-model dimensions · cut-out masks
  • 300 DPI · per-panel print areas · underbase flagged on darks
  • 300 DPI · flat wrap dimensions · handle zone excluded
  • 300 DPI (150 above 100cm) · 10mm bleed · wrap depth on canvas
  • Vector only · minimum stroke per material · depth passed through
  • 300–600 DPI · 2mm bleed · separate vector cut layer

Fulfilment questions

Do I have to use a fulfilment partner you have integrated with?
No. Customei has no preferred supplier and takes no cut of production. If your partner can read a file from a bucket, an API call, a signed link or a webhook, they are supported today.
What does my printer actually receive?
A print-ready file at 300dpi with bleed, safe area and any cut path already applied, named with the order number, line item and panel — plus the option values, so they can verify without opening the design.
Can I check a file before it is produced?
Yes. Proofing can be set to auto-approve, to require review on specific conditions (an upload, a long inscription, a high-value order), or to require review on everything.
What if a file is wrong?
Re-render it from the order. The design record is stored separately from the rendered file, so fixing a font or a print area and re-rendering does not require the customer to reorder.
Where are customer uploads stored?
On Cloudflare R2 with signed URLs. EU-only storage is available on request, and a signed DPA is available on every plan.

Get started

Stop exporting
artboards by hand.

Install Customei, place one test order, and watch the print file arrive where your printer expects it.