Overview

CapitalOS organizes work around your user account and one or more organizations. An organization normally represents a store, brand, or operating entity with its own members, integrations, product records, settings, and module access.

Before you begin

You need a CapitalOS account and access to an organization. Depending on your role, you may be able to create an organization yourself or join one through an invitation.

For the most complete operational data, an organization owner should connect the services the team uses, such as Shopify and the relevant advertising or communication platforms. You can still enter some information manually, but synchronized views depend on their source integrations.

Choose the correct organization

CapitalOS keeps organization data separated. Check the organization selector before adding products, reviewing orders, changing settings, or importing a workbook. The organization name in the route and interface should match the store you intend to work on.

Users who manage several organizations can switch between them. Portfolio views provide cross-organization summaries for supported modules, while organization pages remain scoped to one organization.

Understand the navigation

The organization navigation is grouped around three kinds of work:

• Product workflow: Research, Quotation, Testing, and Returns.
• Operations: Products, Orders, Communications, Finance, Spreadsheets, and Imports.
• System and collaboration: Feature Requests, organization settings, notifications, integrations, and supported AI access.

Your navigation may contain fewer items. CapitalOS filters modules according to your role and the modules enabled for the organization.

Complete organization setup

Organization owners and administrators should review these areas early:

1. Confirm the organization name and store preferences.
2. Connect Shopify if the organization needs product and order synchronization.
3. Connect advertising, email, or Slack services that the team will use.
4. Invite members and assign suitable roles.
5. Review enabled modules, categories, columns, return settings, and transaction-fee settings.
6. Confirm which users are responsible for Research, Quotation, Testing, Communications, Finance, and Returns.

Not every setting is available to every role. If you cannot open an organization setting, check with an organization owner rather than creating duplicate records elsewhere.

Recommended first workflow

For a new product, the usual path is:

1. Add or import the product into Research.
2. Record validation, competitor, sourcing, and priority information.
3. Move a suitable product into Quotation for cost and supplier work.
4. Prepare approved products for Testing and review performance data.
5. Use Products as the shared catalog and Orders for commercial activity.
6. Use Returns to understand post-purchase problems and product impact.

Read The Product Workflow for the relationships between these stages.

Data sources and freshness

CapitalOS combines synchronized and manually maintained data. A recently connected integration may need time to import historical information. Missing metrics can also mean that a product, SKU, campaign, order, or account has not been matched to the expected organization record.

Before changing data to work around a missing value, check the relevant integration status, date range, organization, and SKU.

Where to go next

• Product Workflow
• Core Workflow Modules
• Operations Modules
• Integrations
• Account and Organization Management

Detailed getting-started guides

• Select and switch organizations
• Navigate CapitalOS and understand module access
• Understand roles and permissions
• Complete the organization setup checklist
• Understand SKUs and product identity