Configure domain pricing in Blesta after the module account authenticates correctly. The connector provides upstream prices by TLD, currency, year term and operation. Your retail configuration must use supported annual terms and the intended selling prices.
01 Prepare Domain Manager
- Confirm Domain Manager is installed for the correct Blesta company and the registrar module is available.
- Open Packages > Domain Options > TLD Pricing.
- Add or review the intended TLD and assign the eligible registrar account through the supported interface.
- Review registration, renewal and transfer prices for each supported annual period and active company currency.
- Check default nameservers and any enabled DNS, forwarding, privacy or EPP options against the actual upstream offering.
- Enable the TLD for ordering only after reviewing the price and service configuration.
02 Keep the upstream matrix intact
The connector reads the pricing export and requires a valid currency and term matrix. It rejects an incomplete or malformed price response instead of returning a partial price import as if it were complete.
Use yearly domain package pricing. The connector's service and renewal callbacks derive the renewal term from the annual service period and reject a non-year period. Do not represent a one-year registry term as twelve independent monthly renewals.
Before changing pricing, preserve the existing configuration and test a representative quote or order. Confirm the currency, operation and number of years rather than comparing only one headline price.
Common questions
Why is a newly added TLD disabled?
Blesta creates new TLD entries without a reviewed selling price and keeps them disabled. Set the intended prices and enable the offer deliberately.
Does a successful profile test import prices?
No. Authentication and Domain Manager pricing are separate setup tasks.
Can I change the registrar module of an existing TLD with active services?
Follow Blesta's supported migration process. Its Domain Manager restricts direct module changes when active services exist; do not force a database reassignment that leaves incompatible service fields.
Why did the importer return no prices?
Inspect the upstream catalogue, account eligibility and error report. An incomplete export can be refused. Do not replace missing terms with zero or extrapolated prices.
Related articles
- Connect Blesta Domain Manager to us Domain Nexus
- Consume the exact reseller pricing export without inventing unsupported terms
- Build a domain search form from the current TLD catalogue
- Prepare a new reseller account for its first live domain order
- Use Blesta's domain management tab with the connector's actual capabilities