Technical FAQ · For flexo trade shops
Technical FAQ for flexo trade shops.
Straight answers on three-party billing, Esko and CLOUDFLOW integrations, and how Flexoworks runs alongside your existing prepress stack. If your question isn't here, book a 20-minute walkthrough.
Plate area · jobs · customers · AR — one system of record
Three-party billing & invoicing
Brand pays, converter orders, designer approves. Who gets the invoice?
How does Flexoworks handle three-party billing where the brand owner pays but the converter places the order?
Every job in Flexoworks carries three party fields independently: the customer of record (who gets invoiced), the converter (who runs the job), and the brand or designer (who supplies artwork and approves proofs). You can route the invoice to any of the three on a per-job basis without restructuring the customer record. Approval emails, proof links, and delivery confirmations route to the brand contact while the AR document goes to whoever's footing the bill.Can we split a single job across multiple POs from different cost centers?
Yes. A job can carry multiple PO references, and plate-area billing can be allocated across them by SKU, plate set, or fixed percentage. The split shows on the invoice as separate line items so accounting on the customer side can reconcile against their internal cost centers.How do gang runs get allocated when one plate sheet serves multiple customers?
Gang allocation is plate-area-aware: Flexoworks measures the actual square inches of each customer's artwork on the gang sheet and bills proportionally. Setup charges, plate-mount labor, and proof costs can be split equally, by area, or by a custom rule per customer.Does plate-area billing support tiered or contracted rates per customer?
Yes. Every customer record carries a rate card with tier breakpoints (for example 0–500 sq in, 500–2000, 2000+) and contracted overrides per plate type, gauge, and screening method. Rate changes are versioned, so historical jobs invoice at the rate that was in effect on the job date, not the current rate.How are reprints, revisions, and customer-caused remakes invoiced?
Each revision is tracked as a linked sub-job with its own plate-area calculation and cost code. You set the policy per customer — common patterns are customer-caused revisions billed at full rate, shop-caused billed at zero, and within-tolerance reruns flagged for review. The audit trail shows what changed between revisions so disputes have evidence, not guesswork.
Native integrations — Esko, Hybrid, imagers
Keeps your workflow engine. Owns the business layer around it.
Does Flexoworks integrate natively with Esko Automation Engine? At what level?
Yes. Flexoworks integrates with Automation Engine at three levels: job intake (Flexoworks creates the AE job ticket via XML/JDF and hands off the artwork), status updates (AE workflow events flow back into Flexoworks as job-status updates via webhooks or polled XML), and plate output (imager events write back to the job so billing fires off measured area, not estimated). You keep AE as your production engine. Flexoworks is the business layer on top — quote, intake, status, billing.Does it integrate with Hybrid Software CLOUDFLOW? What's the data exchange model?
Yes. CLOUDFLOW integration uses CLOUDFLOW's REST API for job creation and asset handoff, plus workflow webhooks for status. Same model as the Esko integration — Flexoworks owns the customer, job, and billing records; CLOUDFLOW owns the prepress workflow.Can we keep ArtPro+ or PACKZ as our editor and use Flexoworks only as the MIS layer?
Yes — that's the most common deployment. Your prepress team keeps the editor they know. Flexoworks doesn't touch the artwork itself; it tracks the job around the artwork (who, what, when, how much, who pays). Editor choice is independent.How do plate imager events (CDI, Kodak Flexcel NX) flow back into job status?
Through the imager's job log or workflow integration. For CDI we read the AE imager log; for Flexcel NX we ingest the Prinergy / Miraclon job report. In both cases the event writes the measured plate area to the Flexoworks job, which is what plate-area billing fires off — so invoiced area matches imaged area, not estimated area.What happens to the QC step — is it tracked inside Flexoworks or does it stay in the prepress tool?
Both layers see it, but Flexoworks owns the business record. QC pass/fail and operator notes are captured against the job (for SLA reporting and customer disputes). The visual QC itself happens in your prepress tool — we don't replace the proofing or color-check workflow.
Operational logic
How the 8-stage workflow, escalations, and accounting line up.
How does the 8-stage prepress workflow map to our existing intake-to-delivery process?
The 8 stages are intake, file prep, screening, proofing, approval, imager, QC, and delivery + invoice. Each is a tracked stage with owner, timestamp, and SLA. You can rename stages, merge them, or add shop-specific stages (for example a press-side check step) without touching code. Jobs surface in a kanban board grouped by stage so the floor sees what's queued and what's stuck.What happens when a job stalls — how does Flexoworks surface and escalate it?
Each stage has a target duration per customer or job type. If a job sits longer than its target it surfaces on the dashboard as at risk, and escalates after a second threshold to the owner's manager. Escalations can route by email or Slack. The point is to catch the Friday-afternoon discovery on Tuesday morning.Can we run Flexoworks alongside QuickBooks for AR/AP, or does it replace accounting?
Alongside. Flexoworks is your operational system of record — customers, jobs, plate production, invoices. Invoices export to QuickBooks (Online or Desktop) for AR/AP, GL, and tax. You're not replacing your accountant's tool of choice.What's the migration path from spreadsheets, ePS Pace, or generic ERP — how long and what gets moved?
Typically 4–8 weeks end to end, in three phases. Phase 1: customers, rate cards, and open jobs imported via CSV or direct DB extract (~1 week). Phase 2: historical job data for the last 12 months for reporting continuity (~2 weeks). Phase 3: integration cutover — AE/CLOUDFLOW hooks, QuickBooks export, imager log ingestion (~1–2 weeks of overlap where both systems run in parallel). You don't go cold-turkey. We run side-by-side until your team confirms the new numbers reconcile to the old ones.Where does customer-facing data (proofs, approvals, delivery) live — portal or email?
Both. Each customer gets a portal for proof review, approval, and job history. Emailed approval links route to the same portal. Brand-side contacts can be added as portal users without giving them access to your shop's job costing — they see proofs and approvals only.
Still have a question we didn't answer?
Book a 20-minute technical walkthrough.
We'll answer your specific integration or billing scenario live — on your stack, your workflow, your customer mix. No slideware.