How Your printIQ Orders Sync with HP SiteFlow
How Your printIQ Orders Sync with HP SiteFlow
A plain-English overview of what happens when an order moves from printIQ into SiteFlow production - and how status flows back the other way.
Once your printIQ system is connected to HP SiteFlow, eligible orders move into production automatically - no manual re-entry, no separate uploads. Production status from SiteFlow flows back to printIQ in real time, so what you see in printIQ always reflects what is actually happening on the shop floor.
What This Integration Does for You
🔁 No double entry Orders flow straight from printIQ into SiteFlow with the right SKU, components and routing already attached. | 📡 Live status visibility Print Ready, sub-batch progress, completions and cancellations all update in printIQ automatically. |
⚙️ Configurable per product You choose which products go to SiteFlow. New SKUs can be added without custom development. | 🛡️ Isolated & reliable Your integration runs on its own pipeline, so workload spikes do not affect other customers - or get affected by them. |
How It Works at a Glance
Figure 1: System-level view of the printIQ ↔ HP SiteFlow integration
What Happens When an Order Is Submitted
From the moment a job is ready in printIQ to the moment it is marked complete, here is what happens behind the scenes:
Figure 2: End-to-end order lifecycle
Status Updates You Can Expect to See
As your order progresses through HP SiteFlow, the corresponding status will update automatically in printIQ:
| When this happens in SiteFlow... | ...you will see this in printIQ |
|---|---|
| Order received | The job is acknowledged as submitted to production. |
| Print Ready | Files have been pre-flighted and the job is queued for printing. |
| Sub-batch scanned | The job has been picked up at a production station and is in progress. |
| Batch complete | Production for the order has finished and it is ready for the next stage. |
| Order cancelled | The matching job in printIQ is marked as cancelled to keep both systems aligned. |
Behind the Scenes: Technical Sequence
For technical readers. The diagram below shows the full sequence of system-to-system interactions, including the validation step, success and failure paths, and how production milestones flow back to printIQ. If you are not the technical owner of this integration, feel free to skip ahead to the FAQ.
Each vertical lane represents a system or service. Time flows from top to bottom. Solid arrows are requests, dashed arrows are responses.
Figure 3: End-to-end technical sequence between printIQ, the integration middleware, and SiteFlow
Reading the Sequence
- Steps 1-4: a printIQ job arrives, the middleware loads its mapping rules, and transforms the job into a SiteFlow-shaped payload.
- Steps 5-6: the order is validated against SiteFlow before any production resources are committed.
- Validation successful: the order is created in SiteFlow, batch IDs come back, and printIQ receives a success acknowledgement.
- Validation failed: a clear error returns to printIQ so the issue can be corrected without partial production.
- Steps 11-15: as production progresses, SiteFlow webhooks fire on every milestone. Each event is mapped to a printIQ operation, and the production status is updated via the printIQ Production API.
Frequently Asked Questions
Do all our orders go to SiteFlow automatically?
No - only products you have configured for SiteFlow are sent. Everything else continues to flow through your normal printIQ process. You decide which products are eligible.
What if we want to add a new product to SiteFlow later?
New products can be added to the integration through configuration - there is no need for custom development. We will work with you to map the new product to the right SiteFlow SKU and finishing options.
What happens if SiteFlow is temporarily unavailable?
Orders are queued safely and processed in order once the connection is restored. Nothing is lost, and the integration resumes automatically without manual intervention.
Can a job be cancelled after it has been sent to SiteFlow?
Yes. If an order is cancelled in SiteFlow, the cancellation flows back to printIQ automatically so the two systems stay in sync.
Will this affect orders that do not use SiteFlow?
No. The integration only acts on orders flagged for SiteFlow. All other printIQ workflows continue exactly as before.
Is our data secure?
Yes. The integration uses authenticated, encrypted connections to both printIQ and SiteFlow, and your pipeline runs in isolation from other customers.
Need help or have questions?
Get in touch with our support team - we are happy to walk you through any part of the integration.
Related Articles
HP BOX connectivity
Overview HP BOX is an application of HP's printOS cloud solution. HP BOX can receive files from various sources, and easily submit jobs to production. When configured for HP BOX, printIQ will have a unique "HP Box Integration" operation. This ...Setting Up Infigo Integration with printIQ
Summary This article outlines the steps required to configure your Infigo platform to integrate with printIQ. Most of the setup is performed within the Infigo environment. Note: The printIQ team does not manage the Infigo-side configuration. Please ...printIQ Integration toolbox
Integration Toolbox Getting started with integration and API overview Access printable attachment at the top or bottom of this article depending on your browser. Introduction When it comes to workflow and integration, everyone’s requirements are ...HP Box flow reference per printIQ Job Operation
Essentially, we can reference a unique HP BOX flow per printIQ Job Operation. printIQ now polls the list of available flows from your printOS HP BOX application. You can name and describe your Job Operation as you require. A drop-down selector in ...Orders Board
The intended audience for this article is everyday internal IQ users. Introduction Quotes are made up of Production Products and / or Pick and Pack items or a combination of both. After accepting a quote, the production products create a job per ...