CapitalOS Knowledge Bank

CapitalOS brings product decisions and day-to-day ecommerce operations into one connected workspace. This knowledge bank explains how organization users can move products from an early idea through sourcing and testing, then monitor products, orders, communication, finance, and returns.

Start here

If you are new to CapitalOS, begin with Getting Started. It explains organizations, navigation, module access, integrations, and the first steps after signing in.

To understand how the main product modules work together, read The Product Workflow.

Explore by area

• Core workflow: Research, Quotation, Testing, and Returns.
• Operations: Products, Orders, Communications, Finance, Spreadsheets, and Imports.
• Collaboration and access: supplier collaboration for organization users, feature requests, notifications, and AI or MCP access.
• Integrations: Shopify, Meta, Google Ads, Nylas, and Slack.
• Account and organization management: account security, billing, members, roles, modules, and organization configuration.
• Help Center: terminology, common problems, data freshness, and support guidance.

A connected data model

CapitalOS uses a shared SKU identity to connect product information across modules. A product may have research, quotation, testing, order, and returns records without those records becoming separate products. Parent and child SKUs allow variations to remain grouped while keeping their own operational data.

External data depends on the integrations enabled for your organization. Some fields are synchronized from connected platforms, while others are entered or maintained by your team. The individual module guides distinguish these sources wherever they matter.

Access and permissions

The modules you see depend on your organization, subscription, and assigned role. If a guide describes a module that does not appear in your navigation, ask an organization owner or administrator to review your access before troubleshooting the feature itself.

Documentation approach

These foundation pages explain what each part of CapitalOS does and scope the detailed guides that will follow. They describe current organization-user behavior and intentionally exclude supplier-only portal instructions and internal implementation details.