Qlero Pricing: What Is Included in Each Plan and How to Pick the Right Tier

Qlero pricing is custom — three tiers, three add-ons, no public price list. What Lite, Pro, and Enterprise each include, what the add-ons unlock, and how to figure out which plan fits your operation.

Qlero pricing is custom — no published monthly rate, no pricing page with a slider. That's intentional. A platform serving a 15-artist indie label and one managing thousands of releases across multiple entities can't share a single price point without getting it wrong for one of them.

What this article covers: what each tier includes, what the add-ons unlock, and how to figure out which plan fits your operation right now.

How Qlero's Pricing Is Structured

There are three tiers: Lite, Pro, and Enterprise. All three run on the same core royalty workflow — catalog and contract management with tree-structured deal models, sales file ingestion, automated royalty calculation, and artist statements through a self-serve portal with a statement ledger.

Each tier builds on the one below it: Pro includes everything in Lite, and Enterprise includes everything in Pro. Three add-ons — Payments, API access, and white-label portals — sit outside the tier structure and can be attached to any plan.

Since pricing is quoted based on your actual catalog and requirements, the path to a number is a demo at qlero.io/book. But understanding what you're buying before that call makes the conversation faster and more useful.

What Each Tier Covers

Lite

Lite is for independent labels with smaller catalogs that have outgrown spreadsheets.

It includes catalog and contract management, reusable tree-structured deal models, royalty calculation and statements, an artist portal with a statement ledger, and DDEX catalog ingestion. You import sales files from any DSP or distributor, map columns once into a reusable template, apply the deal terms per payee — splits, rates, recoupment, advances — and publish auditable statements to artists.

The reusable column-mapping template deserves specific mention. If you're currently re-mapping a DistroKid or TuneCore CSV every quarter because the column order shifts, that stops with Lite. You map once; every future import from that source uses the same template automatically.

Lite fits if your catalog is focused, your roster is manageable, and your main goal is replacing a spreadsheet process with something that produces clean, auditable statements on a predictable schedule.

Pro

Pro is built for growing labels, publishers, and distributors — larger catalogs, more complex contract structures, and often more than one person running royalty operations.

Pro includes everything in Lite and adds the capabilities that complexity demands: multiple accounting periods, a report builder, configuration groups, cross-contracting, reserves and escalations, custom templates, and custom CSV statements.

Those additions matter in practice. Reserves and escalations let deal terms reflect real contracts — tiered rates that change after thresholds, held-back percentages released in later periods. Multi-period accounting means that when an artist questions why their Q2 statement looks different from Q1, you show the exact reconciliation instead of reconstructing it from memory. And custom CSV statements and the report builder cover the moment your distributor, accountant, or biggest artist asks for output in their format rather than yours.

Pro makes sense once contract terms vary meaningfully across your roster, income arrives from several sources on different schedules, or you've had your first artist dispute and realized your current process couldn't defend itself.

Enterprise

Enterprise is for large catalogs and multi-entity operations — a distributor running royalty accounting across multiple label clients, or a publisher managing rights across several sub-publishers and territories.

Enterprise includes everything in Pro and adds custom statement design, white labeling, and API integration. At this tier, API access shifts from optional to practically necessary, and white labeling of both the label-facing portal and the payee-facing artist portal matters when you're operating under your own brand and don't want a third-party platform's name visible to your artists or sub-labels.

DDEX catalog ingestion is included from Lite up, but it's most relevant at Enterprise scale, where catalog data arrives from external systems rather than being entered manually.

The Add-Ons: Payments, API, and White Label

These three capabilities are available on any plan, independent of tier.

Payments enables royalty disbursements directly through the platform. It's not built into the base tiers, so if integrated payments are a workflow requirement, factor that in when you're evaluating total cost.

API access connects Qlero to external systems — accounting software, a distribution platform, or a custom internal tool. It's most relevant for operations where Qlero needs to function as part of a larger data pipeline rather than a standalone tool. (It's included natively at Enterprise.)

White label covers both the label portal and the payee portal. If your artists or sub-label clients interact with a branded portal, white labeling keeps that experience consistent with your brand. Available as an add-on on any tier, and included at Enterprise.

How to Pick the Right Tier

Three questions get you most of the way there.

How large is your catalog, and how fast is it growing? A label with a stable roster and straightforward deals is a Lite user. A label signing new artists steadily and expecting the catalog to grow significantly within a year should start at Pro — migrating mid-cycle creates friction you don't need.

How complex are your contract structures? If every artist is on a standard royalty rate with straightforward recoupment, Lite handles that cleanly. If you have tiered rates that kick in after a sales threshold, reserves held across periods, or cross-contracted deals, you need the deal-model depth Pro provides.

Are you running royalty accounting for multiple entities? If yes, Enterprise is the tier to discuss. Multi-entity operations, white-labeled portals for external clients, and API connections to external systems are what define that tier.

If you're still unsure after working through those questions, the demo at qlero.io/book is the right next step. Qlero quotes based on your actual catalog size and operational requirements, so the conversation is diagnostic rather than a generic sales pitch.

What Every Plan Includes

Regardless of tier, every Qlero plan covers the same foundational workflow:

• Catalog and contract setup with reusable, tree-structured deal models
• Sales file ingestion with reusable column-mapping templates
• Automated royalty calculation — splits, rates, recoupment, and advances per payee
• Auditable royalty statements published to a self-serve artist portal with a statement ledger
• DDEX catalog ingestion

The tiers scale the capacity and complexity of that workflow. The add-ons extend it into payments, external integrations, and branded portals.

FAQs

Does Qlero publish its pricing publicly?

No. Pricing is custom and based on catalog size and operational requirements. There are three tiers — Lite, Pro, and Enterprise — but no public price list. You get a quote through the demo process at qlero.io/book.

What is included in the Lite plan?

Lite covers catalog and contract management, reusable tree-structured deal models, sales file ingestion with reusable column-mapping templates, royalty calculation with splits and recoupment, artist statements through a self-serve portal with a statement ledger, and DDEX catalog ingestion. It's designed for independent labels with smaller catalogs.

What does Pro add over Lite?

Multiple accounting periods, a report builder, configuration groups, cross-contracting, reserves and escalations, custom templates, and custom CSV statements — the capabilities growing labels, publishers, and distributors need as contract structures and reporting demands get more complex.

Are payments built into every plan?

No. Payments is an add-on available on any tier. If integrated royalty disbursements are a requirement, you add the Payments module to whichever base plan you're on.

Who should consider Enterprise?

Enterprise fits large catalogs and multi-entity operations — distributors running royalty accounting across multiple label clients, or publishers managing rights across sub-publishers. Custom statement design, white labeling, and API integration are the defining capabilities at this tier.

Can I white-label the artist portal on a lower tier?

Yes. White labeling is available as an add-on on any plan, not exclusively at Enterprise. If you need branded portals for your artists or sub-label clients, you can add that capability regardless of which base tier you're on.

How do I find out which tier is right for my label?

Book a demo at qlero.io/book. Qlero quotes based on your actual catalog size and contract complexity, so the conversation is focused on your specific situation rather than a generic pricing sheet.