Upgrade the hub before customer connectors

1. Back up the hub database and plugin folders. Preserve each website's Data Protection key ring, usually App_Data/DataProtectionKeys.
2. Deploy Client Success on the hub first, restart, and complete the normal update process without uninstalling.
3. Review Connected Websites: each needs an explicit hub store and an active registered primary customer.
4. Update customer sites to Client Connector 4.80.8 and run connection tests.
5. Preserve the client delivery/reminder tasks and nopCommerce email queue task preferences.

The hub requires its existing Core and Stripe dependencies. Client sites receive connector credentials, not hub Stripe/Zoho credentials. Full hosting, SMTP, Stripe, and Zoho acceptance still needs staging verification.

Website ownership and billing responsibility

One customer may own multiple connected websites, each with a name, URL, Site ID, secret, and billing responsibility. The hub store is the store in the central service website, not a store number from the customer's independent installation. A separate billing customer replaces the primary customer for billing notices.

On multi-store hubs, legacy sites remain unassigned until an administrator chooses the correct hub store. Connections fail until that assignment is valid. Single-store migrations can select the sole hub store automatically.

Billing portal and notices

The billing portal shows the signed-in customer's own Stripe orders at the current store, with invoice links, currency, pagination, and store timezone. Owning a website does not grant access to another customer's invoices or billing contacts.

Billing notices reconcile against persisted order state; a stale failure must not reopen a paid notice. Payments remain account-level and are not allocated to individual websites' line items. This ownership update does not initiate charges, refunds, or subscription changes.

Transfer a connected website

1. Review and change the website's primary customer, billing customer, or hub store.
2. The hub generates a new secret and access version; old credentials no longer authorize the assignment.
3. Update the intended customer's connector with the new secret and test the connection before handoff.
4. Check notices and support access under the new assignment.

Earlier support history is retained for hub administrators and is not exposed as the new owner's history. Already queued/sent emails or notices previously cached on another site cannot be recalled.

Bookings, training, and email delivery

Support/training bookings recheck store scope, available capacity, and schedule buffers. The connector displays appointment times using the hub-provided timezone. Version 4.80.8 removes the older fixed Pacific label.

Client Email Delivery shows pending outbox work and retry controls. The outbox hands messages to nopCommerce's standard Message queue; queue handoff is not proof of SMTP delivery. Check both places when troubleshooting confirmations or reminders.

Connection and retry troubleshooting

Use the configured HTTPS hub root and current Site ID/secret. Explicit connection tests refresh the feed. Invalid credentials or malformed responses clear cached notices; transient failures may show previously received notices with a stale caption for up to 24 hours.

When retrying an uncertain support submission, keep its form/request unchanged so the hub can replay the original result. A failed Data Protection restore requires re-entering connector credentials. Never include secrets or private customer history in support screenshots.