When To Request A Custom License Instead Of Checking Out Directly
Retail checkout is the right path for many buyers, but some projects need wider rights, more explicit terms, or product-specific approval.
Direct purchase licensing is designed to keep common commercial use simple. But not every project is common, and that is exactly where a custom license request becomes the cleaner path.
Use the inquiry route when the scope is unusual
- The font will be embedded in a product, app, or game beyond standard retail terms.
- The work will be distributed across a larger company or multiple business entities.
- The client needs written approval for broader transfer, redistribution, or audience scale.
- The project combines assets, deliverables, or channels that do not fit a standard checkout option cleanly.
Why this matters operationally
The safest order flow is one where the purchased terms, the certificate, and the real use case all line up. If a buyer forces a complex project through the wrong retail license, the friction appears later during delivery, compliance, or client review.
Custom requests are part of the product, not an exception
SibelumPagi is built to sell standard licenses directly and route broader cases into inquiry workflows. That is not a fallback. It is part of the intended commercial model.
If the project description sounds bigger than a normal retail order, treat that as a signal and ask for custom terms before payment.