For platform, product, and OEM teams

Put labeling and document printing in your product without building it.

Your customers keep asking your product to print their own labels and PDF documents. Building that designer in-house is a 12-month cycle of build, test, validate and release, and a budget you'd rather spend on your core roadmap. Embed Qpro+ instead. You call the API, we render, and your customers never see us or contract with us. Because you're billed on renders, a customer with 40 printers costs you the same as one with four. A technology leader in global electronics diagnostics, equipment, and services already ships Qpro+ inside what it delivers to its own customers.

Start a conversation Read the API docs

See a live render in ten seconds, no account needed.

The licensing problem

Most label vendors are priced for direct enterprise sales. That breaks on resale.

The unit you're charged in decides whether you can distribute at all. Renders are the only one that survives redistribution intact.

Priced byWhat happens when you distribute
Per printerYour cost tracks your customers' hardware, which you don't control and can't forecast.
Per seatYou're billing for people who never log in, or reconciling seat counts across every account you serve.
Per end-customer licenseThe vendor contracts with your customers directly. You've introduced a third party into your own relationship.
Per renderCost tracks usage, which tracks the value your product delivers. One contract, with you.

Your customers never see us. Qpro+ sits behind your product. You hold the contract, you own the relationship, and you set your own pricing on top.

The engineering problem

Hardcoded label and document formats turn every customer request into a release.

Layouts frozen into firmware or a central system mean new symbologies, new customer formats, colour logos, and creative variations all arrive as development work; scoped, built, tested, and shipped. That cost compounds with every customer you add.

Label and document diversity without a firmware release

Templates live in Qpro+, not in your build. Adding a customer-specific label or document format is a design task, not a development cycle.

Centrally managed across your whole fleet

One place to design, approve, and version every label and document your distributed product can produce, however many endpoints are calling it.

Reaches your endpoints without redesigning your platform

An authenticated HTTPS request in, a finished label or document out. If your product can make a web request, it can render a Qpro+ label.

Time from design to production, measured in minutes

Draft the template, promote it to Active, and the next render uses it. No coordination window, no deployment slot.

POST /custom-labels/render-zplnode · sandbox
// your product asks for a label the moment it needs one
const res = await fetch("https://api.beta.quandosol.com/api/custom-labels/render-zpl", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "X-API-KEY": process.env.QPRO_API_KEY,
    "X-API-SECRET": process.env.QPRO_API_SECRET
  },
  body: JSON.stringify({
    label_name: customer.labelTemplate,   // per-customer, no rebuild
    amount: 1,
    apiData: {
      device_serial: unit.serial,
      asset_tag:     unit.assetTag,
      grade:         unit.condition,
      processed_at:  unit.timestamp
    }
  })
});

if (!res.ok) throw new Error(await res.text());
const { labels } = await res.json();
for (const zpl of labels) printer.send(zpl);
Full API reference →

Before you commit

The questions a platform team asks in the first technical call.

What stops someone editing a live template and breaking production?
Templates carry a Draft and Active status, so work in progress never reaches your systems. An optional approval step routes a change to a reviewer before it's promoted to Active. Until someone promotes a Draft, your API calls keep resolving against the current Active version.
If a bad version does reach production, how fast can we undo it?
One step. Every revision is kept with who changed it and when, and rolling back restores an earlier version straight to Active, so the next render prints it. Rollback skips the approval queue on purpose: that version was already approved, and while the wrong artwork is live, every minute counts. The rollback is recorded in the version history like any other change. Clones work the other way round and start as clean Drafts, so nothing copied from a template reaches production until someone promotes it.
What happens to data we send you?
On the Integrate plan, any mapped field can be marked pass-through: used to render the label and never written to our database. Evaluating? We'll enable it on your test account. We'll walk you through it end to end (design, mapping, API call, database record) so you can verify the behaviour rather than take our word for it. See compliance
Can we white-label it?
Yes. Qpro+ can also sit behind your product. Your customers interact with your interface and contract with you. We don't appear in the relationship unless you want us to.
What are the rate limits at production volume?
Every key starts at 60 requests a minute, free and paid alike. Paid accounts are then provisioned against your expected throughput rather than a fixed published ceiling. Tell us your projected annual render volume and burst profile and we'll size it.
How do we test before signing anything?
Start on the free account. It has no time limit and no print cap, and it's only deactivated after 90 days of complete inactivity. It's limited to two templates and one user. ZPL output is never watermarked, so you can validate on real hardware before any commercial conversation.

Tell us what you're shipping.

Embedded deals are sized around your distribution model, not a published seat count. The first conversation is about how your product reaches customers and what volume looks like as it scales.

Start a conversation Build a prototype first
Qpro+ is a product of Quando Solutions, a supply chain & manufacturing IT company