When a warehouse employee adds a part in CARRO.Business, its QR label can appear on the printer assigned to that location. The employee stays in the web or mobile workflow instead of downloading a PDF and choosing a printer manually.
## The workflow CARRO.Business combines inventory, sales and ecommerce workflows for automotive dismantlers and parts businesses. Printing is part of the warehouse operation: the application creates a label or document, selects the company and assigned printer, and submits the job from the same workflow. ## Why browser printing was not enough The operation may start in a browser, on a phone or on a computer different from the one next to the printer. The printer is usually behind the customer's router, firewall and operating-system queue. A useful integration therefore needs a preassigned printer, an outbound connection, observable job states and safe retries—not just a **Download PDF** button. ## Customer setup without a separate CloudPrint registration CARRO.Business provisions and manages the CloudPrint account for each customer company. The administrator starts in CARRO.Business, chooses whether the printer is connected to the current computer or another one, installs CloudPrint Agent and assigns a discovered print queue. For another computer, CARRO.Business can issue a limited one-time setup link, so the person near the printer does not need access to the full CARRO.Business account. ## How a print job reaches the printer 1. CARRO.Business prepares the document and selects the company, workflow and assigned printer. 2. The CARRO.Business backend submits the job to the CloudPrint Print API. 3. CloudPrint stores and routes the job to the correct installation; a stable `Idempotency-Key` protects a retry from creating a duplicate. 4. CloudPrint Agent maintains an outbound connection, receives the job and passes it to the operating-system queue. 5. The printer driver sends the data to the physical printer, while the job status returns through CloudPrint. ## Reliability rules that matter in production - **Accepted is not printed.** The product follows the job to a terminal status instead of reporting success immediately after the API accepts it. - **Retries keep the same identity.** A timeout is retried with the same idempotency key, avoiding duplicate labels. - **Printer assignments use stable IDs.** A display name is helpful in the interface but is not a durable integration key. - **Diagnostics stay close to the action.** Support can distinguish an unavailable computer or Agent from an operating-system queue or printer problem. ## Responsibility boundary CloudPrint provides job transport, the outbound local connection, printer discovery and print-status visibility. CARRO.Business owns the business object that starts printing, the label template, permission to change the company printer, reprint and error behavior, history, audit and first-line customer support. That boundary keeps the customer experience inside the SaaS product. ## When this pattern is a good fit This approach is useful when printing starts in a cloud or mobile product, happens regularly and must reach a known printer. It is common in inventory, ERP, WMS, CRM, delivery, healthcare, point-of-sale and production systems. For an occasional document printed from one office computer, a PDF and the system print dialog may still be simpler. ## Verified public sources - [CARRO.Business CloudPrint setup guide](https://carrobiz.com/docs/integrations/printnodecom) - [CARRO.Business July 2026 product update](https://carrobiz.com/docs/news/29) ## Common questions ### Does a CARRO.Business customer need to register with CloudPrint separately? No. In this managed integration, CARRO.Business provisions the customer company and starts the computer connection from its own settings. ### Can printing start from a mobile device? Yes. The business action can start in the CARRO.Business web or mobile interface; its backend submits the job to the printer already assigned to the company. ### Does the customer have to open an inbound network port? No. CloudPrint Agent maintains an outbound connection and uses printers already installed in the operating system. ### Does an accepted API request mean the label was printed? No. Acceptance only confirms that the service received the job. CARRO.Business can follow the status through printing to `printed`, `failed` or `cancelled`. ## Next steps