Qpro+ for platform and OEM teams — embed label and document output, priced per render

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 by	What happens when you distribute
Per printer	Your cost tracks your customers' hardware, which you don't control and can't forecast.
Per seat	You're billing for people who never log in, or reconciling seat counts across every account you serve.
Per end-customer license	The vendor contracts with your customers directly. You've introduced a third party into your own relationship.
Per render	Cost 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.

Embedded render callnode

// your product asks for a label the moment it needs one
const res = await fetch("https://api.qproplus.com/v1/render", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.QPRO_TOKEN}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    template: customer.labelTemplate,   // per-customer, no rebuild
    format: "zpl",
    data: {
      device_serial: unit.serial,
      asset_tag:     unit.assetTag,
      grade:         unit.condition,
      processed_at:  unit.timestamp
    }
  })
});

const { output } = await res.json();
printer.send(output);

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 promotion. Version history and rollback are on the near-term roadmap — worth asking us where they stand before you commit, and we'll tell you plainly.

What happens to data we send you?

Any mapped field can be marked pass-through: used to render the label and never written to our database. 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+ sits 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?

Paid accounts are 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. Free accounts are limited to 60 renders per minute.

How do we test before signing anything?

Start on the free account. It doesn't expire and doesn't cap prints — it caps templates at five and users at one. 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