WHAT IT PLUGS INTO
Will it work with what you already run?
Described by capability rather than by brand, so you can check your own stack against it. If you are not sure whether a piece of your setup qualifies, ask and we will tell you straight.
A store or order platform that can post a webhook when an order is placed, and accept an update when the order moves forward. Multiple sources at once is normal, not an edge case.
A RIP with a REST job API and hotfolder support. Jobs are placed as complete files and status is polled back. The system never takes a socket the printer needs.
Print files reachable at a URL, including inside a ZIP. Five different order formats are already understood.
More than one. Routing between printers by product, size and queue is a large part of what this does. It still works with a single printer.
An Android device for scan-driven QA and shipping. The web surfaces work without it.
Any screen that renders 1920 by 1080 in a browser.
Networked label printers for shipping and identification.
For shipping scans and tracking reconciliation at the packing desk.
It runs on our hardware, not yours. You connect your stores and printers to it. There is no box to buy, no patching, no backups to remember, and no copy of the code sitting on a machine you have to secure.
Can be taken on its own, or bundled together with your RIP software as one package. Ask which arrangement fits your shop.