How should a reseller review imported domain prices?
Separate the registrar's cost from your customer-facing registration and renewal prices. The AIvikings module imports TLD pricing, but the hosting company or agency still needs to review its catalog, selling terms, currency handling, and storefront. This is the pricing step in the WHMCS domain resale workflow.
A price-import success tells you that data arrived. It does not prove that every supported term, premium name, or customer currency produces the offer you intended. Test a small selection before exposing a wider catalog.
Which catalog should you offer?
The module supports all-TLD, include-only, and exclude-list selection. Use the list to express the extensions your team intends to sell and support. Normalize entries and inspect the imported result rather than relying on the setting's name alone.
Keep a record of deliberate exclusions. That makes it easier to distinguish a missing extension caused by policy from an import or configuration problem. Assign the chosen extensions to the correct registrar in WHMCS after import.
The installation guide covers those controls. Avoid introducing a large catalog until you can explain the registration, renewal, nameserver, and exception workflow for it.
What needs a separate price check?
Review registration and renewal independently. A promotional acquisition cost is not a reliable renewal forecast. Inspect the requested term and whether premium pricing applies to the exact name rather than relying only on the extension's ordinary catalog row.
The module imports separate cost fields and supports premium-price checks. It can report an error when the expected premium cost differs from the current quote. Treat that as a decision to revisit, not a reason to remove the check and continue charging the customer.
WHMCS allows domain prices to vary by term and currency in its Domain Pricing configuration. Review the resulting storefront values, including the currencies your installation offers. Keep the currency of the cost and the customer price explicit in your own review record.
How should you think about margin?
Define a commercial policy that accounts for registrar cost and the work involved in providing the service. A quoted price may need to cover support and administration as well as the underlying registration. Document what the customer is buying instead of assuming a particular markup is appropriate for every account.
Do not label registrar access as zero-margin wholesale pricing. Use the actual current cost available to the account. The registration and renewal cost guide helps distinguish the first purchase from the continuing holding cost.
WHMCS documents applying a defined margin during TLD pricing import. That facility does not replace checking the retail result and deciding how your service handles later cost changes.
What should the acceptance record contain?
For each representative case, retain the exact domain or extension, selected term, cost observation, selling price, currency, and expected renewal treatment. Record whether the case was ordinary or premium and which staff member reviewed it.
Inspect a normal available candidate, an unavailable candidate, a premium candidate if offered, and an error response. The customer should not receive a misleading offer when a quote cannot be established.
Keep transfer pricing separate from transfer capability. The reviewed AIvikings module imports transfer-price information but does not execute transfer-in. Do not advertise a working transfer checkout solely because the price is visible.
Use the current AIvikings prices for catalog context and the account's exact-domain quote when the operation requires it. This guide intentionally publishes no fixed TLD prices.
How do you maintain the review?
Recheck the offer when your catalog selection, module version, cost inputs, or customer pricing configuration changes. Record the difference and investigate unexpected storefront values before enabling additional sales.
Existing customer commitments and future offers are different decisions. Review them deliberately rather than assuming a catalog import has updated every customer arrangement in the way you intended. Carry unresolved cost or payment issues into the renewal exception queue.
Frequently asked questions
Does importing cost pricing set the right customer price automatically?
It does not establish that the offer is commercially correct. Review the resulting selling prices, terms, currencies, and premium cases in your WHMCS storefront.
Can a transfer price appear when transfer-in is unsupported?
Yes. The reviewed AIvikings module imports transfer-price information but explicitly does not enable transfer-in execution.
Should I use the first-year price as the renewal price?
No. Review the separate renewal cost and customer renewal offer. Current prices are inputs to the review, not a promise that future costs will stay unchanged.