A: Thanks Pablo — let me go through each point briefly and honestly based on how UniBee works today.
1. CUSTOMER PORTAL
We don’t have a full standalone “customer self-service portal” in the Cloud version yet.
What we do have today:
• Hosted Checkout + Hosted Subscription Update page, where end customers can update payment method when a card fails and keep paying.
• Admins can upgrade/downgrade plans, add add-ons, change subscription status for any customer directly from the UniBee admin panel (so you can still operate without exposing a portal).
Spanish: our checkout / emails are already moving toward multi-language (Spanish is in scope); invoices are currently in English and multi-language invoices are planned.
2. On the multi-entity / multi-brand question:
We already support operating multiple brands / legal entities under one UniBee account.
For each payment gateway you add, you can configure a different “invoice identity” for that brand — including:
Company name shown on the invoice
Company address
Registration / tax numbers (VAT, etc.)
That means Brand A can have its own legal name, address, tax ID and payment gateway, and Brand B can have a completely different set. Invoices generated through each gateway will show the correct company details for that brand.
This is how we handle:
different payment gateways per brand,
different company info per brand,
and effectively separate invoice information per brand.
We do not force a single global company identity across all invoices.
3. Mobile (iOS / Android)
We don’t ship a public mobile app right now for end customers or for admins. Current usage is via web dashboard.
4. Admin control without portal
Yes. As an admin you can fully manage a customer from the backend: upgrade/downgrade, add extras, adjust pricing, handle failed payment, etc. You do not need to wait for the customer to self-serve.
5. Migration / self-hosted option
We also offer a self-hosted / open-source deployment. Data (customers, subscriptions, invoices) can be exported out of the Cloud version. But maybe this part we need to discuss more deeply.