Team operations
Assign clear owners for catalog updates, storefront changes, billing, and support so your Closku launch remains easy to operate.
Reviewed by Closku documentation team ·
Assign operating responsibilities
| Responsibility | What to maintain |
|---|---|
| Catalog owner | Product images, variants, active status, imports, and Closku ID mapping |
| Storefront developer | Script placement, origin configuration, product buttons, and theme regression checks |
| Account owner | Subscription, billing portal, confirmations, and access decisions |
| Support contact | Incident details, affected products, job IDs, and the checks already performed |
Use the account roles actually available in your dashboard. Keep privileged account credentials out of storefront code.
Support by plan
The public plan catalog describes Standard support for Starter, and Priority support for Growth and Scale. Enterprise arrangements are defined by the agreed contract. See current plans for the offered tier.
Use Contact or the support contact in your account for help. A support priority label is not a guaranteed response or resolution time. Specific channels, coverage hours, and any Enterprise SLA should be confirmed in the actual account agreement.
Escalate with useful context
Include your merchant ID, storefront origin, affected product, job ID if known, response error, timestamp with timezone, and impact on shoppers. List any recent theme, catalog, or billing change and what you have tested. Do not send account cookies, secrets, or shopper images through ordinary support messages.
Use Troubleshooting to check mapping, images, origin access, and subscription status first.
Keep a small operating routine
- Review usage and failed renders during launch and busy periods.
- Retest a product after theme or catalog changes.
- Reconcile product exports instead of repeatedly importing duplicate records.
- Retain billing confirmations and follow up on mismatched subscription status.
- Use these public guides as the current reference; do not assume an unlisted training library or account-management service is included.
Next steps
Review service and data boundaries.
Run first checks before escalation.
Related pages
Revisit launch verification.
Review account-owner billing actions.