STL Merchant Licenses: Tiers, Pricing, Enforcement
Build measurable STL merchant-license tiers, price commercial permission, track licensees, and handle violations consistently.
By Tyler Reece · Published January 21, 2026 · Updated July 22, 2026 · 7 min read
A good STL merchant license answers one narrow question without requiring monthly interpretation: which business may sell which physical products, through which channels, for how long? If the answer depends on vague labels like “small seller” or rules you cannot observe, the tier system will create more support and disputes than revenue.
This is a commercial design framework, not legal advice. Copyright scope, contract formation, consumer law, and enforcement vary by jurisdiction and facts. Have counsel review the actual terms before launch.
First calculate the personal-use floor with the STL pricing model; then use this guide to price the additional commercial permission and administration.
Define the licensed unit before defining tiers
Choose what the customer is buying:
- one named design;
- a themed collection;
- the current catalog;
- a subscription catalog released during an active term.
Then identify the licensee by legal individual or business name, contact email, and storefronts. A receipt attached only to a social username becomes ambiguous when the merchant changes platforms or sells the shop.
Use one license record:
LIC-2026-0042 / Acme Models LLC / Garden Stack Collection / 2026-08-01 to 2027-07-31 / Etsy + acmemodels.com
That record should resolve to the accepted terms, payment, covered designs, amendments, storefronts, and status.
Use tiers based on observable differences
Avoid tiers based only on revenue unless you are prepared to request and evaluate financial records. Observable boundaries are easier:
Tier | Practical scope | Useful for |
|---|---|---|
| Design license | One named design; one business; listed storefronts; physical products only | Seller testing a single SKU |
| Collection license | Defined set of designs; one business; listed storefronts | Niche shop building a coordinated line |
| Catalog license | Defined catalog snapshot or releases during a term; one business; multiple disclosed storefronts | Established seller wanting breadth |
| Enterprise/custom | Multiple entities, locations, subcontractors, exclusivity, or custom rights | Negotiated relationships requiring counsel |
Do not manufacture arbitrary “100 units” and “500 units” tiers unless unit reporting is part of the workflow. If you do use unit caps, define whether one multipack is one unit, whether replacements count, and how the merchant reports totals.
State the permission positively
A merchant should not have to infer permission from a list of prohibitions. Start with a grant such as:
During the active term, the named licensee may manufacture and sell physical products made from the covered unmodified design files through the storefronts listed in the license record, subject to these terms.
That is an illustration, not ready-to-sign legal language. Your actual grant must answer:
- physical products only, or digital derivatives too;
- exact files/designs covered;
- whether resizing, adding names, or combining parts is permitted;
- seller-operated printing versus disclosed contract fulfillment;
- storefront and geographic limits;
- term, renewal, and what happens to finished stock at expiry;
- attribution and listing-image rules;
- support and update entitlement.
Keep ownership separate from permission. Under U.S. copyright law, ownership of a copy is distinct from copyright ownership, and copyright owners may authorize defined rights. The U.S. Copyright Office’s overview is a useful starting point.
Price commercial permission from expected value
Do not multiply the personal STL price by an arbitrary number. Estimate merchant value:
Expected annual merchant gross profit = expected units × gross profit per physical unit
Then choose a royalty-equivalent target and add administration/support:
Annual license target = expected gross profit × target share + merchant support/admin cost
Suppose a design is expected to sell 15 physical units per month with $12 gross profit each:
15 × 12 months × $12 = $2,160 expected annual gross profit
At a 10% value share plus $60 of expected license support, the annual target is $276. This is an internal pricing hypothesis, not an industry standard. Compare it with demand, alternatives, enforcement practicality, and the value of your catalog.
For a low-price monthly option, include payment failures, cancellation handling, and license-status checks in support cost. Annual billing is simpler and gives merchants a stable term; monthly billing lowers entry cost but creates more churn and status ambiguity.
Decide what happens when a subscription ends
Write a precise expiry rule:
- May the merchant sell finished inventory made during the term?
- For how long?
- Must listings be removed immediately or by a stated date?
- May the merchant keep photos and sales records?
- Do file updates stop while rights to old physical inventory continue?
- What happens after a failed renewal payment?
A fair wind-down might allow 30 days to sell documented finished inventory while prohibiting new manufacture. Or the business may require listings to stop at expiry. Either can be understandable if stated before purchase.
Do not remotely disable or corrupt files. Control contractual permission and future access, not a buyer’s computer.
Address outsourced fulfillment explicitly
Many merchants will use a production partner. Choose one rule:
- no third-party access to files;
- approved production partners only;
- disclosed partners allowed under confidentiality/use restrictions;
- custom enterprise agreement for multiple factories.
If a partner is allowed, define that the file may be shared only as necessary to produce for the named licensee, cannot enter the partner’s catalog, and must be deleted or made inaccessible when the relationship or license ends. Decide who is responsible for the partner’s misuse.
Printie can manufacture and fulfill mapped physical products through supported store and shipping workflows. A merchant must have license terms that permit the intended production arrangement; Printie does not expand the rights granted by the designer. Link merchants to Printie’s design-handling policy and document the production partner in the license record where required.
Build a license registry, not an inbox search
Minimum fields:
- license ID;
- legal licensee/business name;
- email and billing contact;
- storefront URLs and seller IDs;
- covered design IDs and versions;
- tier and permitted production partners;
- start, renewal, grace, and expiration dates;
- accepted terms version and acceptance evidence;
- payment/refund status;
- notices, amendments, and enforcement history.
Run a monthly exception report for expired licenses with active storefront listings, failed payments, missing storefront data, and catalog records not tied to a terms version.
Use a merchant portal or automated receipt if volume supports it, but keep an export you control. License proof should survive a payment-platform migration.
Give merchants assets that reduce misuse
A merchant kit can include:
- permitted product name and optional attribution wording;
- actual physical-product photo guidance;
- material/use limitations;
- current design and release notes;
- SKU suggestions that do not imply brand ownership;
- production notes and critical dimensions;
- renewal date and license ID;
- contact route for rights and file defects.
Do not give permission to use a third-party trademark you do not own. Your license can cover only rights you are authorized to grant.
Use an enforcement ladder
Define the process before the first violation:
- Capture: URL, timestamp, screenshots, seller identity, product images, and terms/license status.
- Verify: confirm the design match and rule; check for a valid license, amendment, or permitted partner.
- Contact: send a factual notice identifying the listing and requested cure by a reasonable date.
- Cure: document removal, purchase/renewal, attribution correction, or other agreed resolution.
- Escalate: use platform reporting or counsel when evidence and rights support it.
- Close: record outcome and apply the same policy consistently.
Do not send mass automated accusations based only on a similar silhouette. False or careless reports can harm legitimate sellers and your own credibility.
For serious infringement, U.S. registration timing can affect available enforcement options. Review the Copyright Office registration resources with an IP attorney. Registration does not cure uncertain authorship or make functional ideas protectable.
Measure whether the program works
Review quarterly:
- merchant recurring revenue;
- support minutes per active license;
- renewal and payment-failure rates;
- percent of records with verified storefronts and terms evidence;
- infringement reports verified versus mistaken;
- time to cure;
- designs generating merchant demand.
If a low-cost tier requires repeated manual audits, it may lose money even with high signups. Simplify the tier, automate evidence, or raise the price.
FAQ
Should a merchant license be lifetime?
Only if you can support the promised scope indefinitely and price it accordingly. A defined term makes updates, records, and changed business needs easier to manage.
Can a licensee give the STL to a fulfillment company?
Only if the license allows it. State permitted production-partner access, restrictions, deletion expectations, and responsibility explicitly.
Should I use revenue or unit caps?
Use a cap only if it can be defined and administered. Design-, collection-, or storefront-based scope is often easier to verify than private revenue or unit counts.