The Use Case: Many of us manage multiple storefronts with different brands within Upmind. When registering domains via Openprovider, it is crucial that clients receive customized ICANN verification emails (with different sender emails, logos, and languages depending on the specific store they purchased from).
Openprovider handles this beautifully on their end through their "Reseller Branding" feature. It triggers specific email templates by associating the domain registration with a specific "Customer Tag" (or Customer Handle) created in their system.
The Issue: Currently, there isn't a way to configure Upmind to automatically send a specific Customer Tag to Openprovider when a new client registers a domain. Because this tag isn't passed through the API, all domains provisioned via Upmind fall under a single default brand in Openprovider. This causes brand confusion for the end-user (e.g., buying from Brand B, but receiving an ICANN email from Brand A).
The Solution: Please add the ability to map or send a "Customer Tag" to Openprovider during provisioning. This could be implemented by:
Allowing us to define a specific Openprovider Customer Tag at the Upmind "Brand" settings level.
OR allowing us to map a custom Provisioning Field to the Openprovider Customer Tag in the module configuration.
Ensuring domains are grouped under the correct customer tag in Openprovider would make Upmind an even more powerful tool for multi-brand agencies.
Please authenticate to join the conversation.
Suggested
Provisioning
5 days ago

Geremias Daniel Rodriguez Santos
Get notified by email when there are changes.
Suggested
Provisioning
5 days ago

Geremias Daniel Rodriguez Santos
Get notified by email when there are changes.