For instance, if Activemenus has a direct client, we would submit a form including the client's logo, branding, and information. The seller would be Activemenus, while the product and client would both be associated with Activemenus. The client's setup will be under client.activemenus.com, utilizing Activemenus' branding.

Alternatively, if Activemenus has a reseller onboard a new client, the form will already contain a field for the reseller name in our database. When completed, the product will automatically default to Activemenus. Similarly to above example 1 scenario.

In another case where we have a new white label domain named Duda with its own branding similar to that of Activemenus, users can fill out a form which includes an identifier flag for Duda as its product. The seller can then set up a merchant that establishes their own subdomain at merchant.duda.com. Sellers must be able to input their names on these forms using fuzzy matching when integrated into our system. If there is an 80% match or higher with existing sellers in our database, it will automatically sync; otherwise, it will inject as new data.

Additionally for server admin - Automate subdomains and DNS pointing (implementing functionality akin to .rdslogic) for all products including Activemenu.

For tech team- Release geographical overlap globally between Activemenu and DeliverClub.