> ## Documentation Index
> Fetch the complete documentation index at: https://services.docs.growcrm.io/llms.txt
> Use this file to discover all available pages before exploring further.

# GrowCRM Products & Services: Sell Services from Your CRM

> Learn how the Products & Services module lets you sell one-time and recurring services, accept payments, and auto-generate orders and projects.

The **Products & Services** module extends GrowCRM so you can sell one-time or recurring services directly from your CRM — no third-party storefront required. Customers browse your services, select what they need, pay by card (Stripe) or PayPal, and GrowCRM automatically creates an order, invoice, and optional project on their behalf. This page introduces the three core concepts that power the module, shows you where to find everything in the navigation, explains the permission levels that control team member access, and calls out the payment gateway requirements you need to meet before your first checkout goes live.

## How the three core concepts fit together

Every sale in the Products & Services module flows through the same three building blocks.

<CardGroup cols={3}>
  <Card title="Service" icon="tag">
    A single product or service you sell — its name, price, optional add-ons, image, and the automation rules that fire after a purchase.
  </Card>

  <Card title="Checkout Form" icon="file-lines">
    A shareable public page that lists one or more services. Customers land here, choose what they want, and pay. Every account includes a built-in **All Services** form that stays in sync automatically.
  </Card>

  <Card title="Order" icon="receipt">
    A record created automatically once a customer completes checkout, or whenever a subscription renews. Orders capture a snapshot of exactly what was purchased and at what price.
  </Card>
</CardGroup>

The typical setup flow connects these three concepts in sequence: you create one or more services, those services appear on a checkout form, and completed purchases land as orders — each step feeding the next.

<Steps>
  <Step title="Create services">
    Define what you sell under **Products & Services → Services**. See [Services overview](/services/overview).
  </Step>

  <Step title="Add them to a checkout form">
    Use the built-in **All Services** form or build a custom one. See [Checkout forms](/checkout/forms).
  </Step>

  <Step title="Share the checkout link">
    Copy the public URL from the Forms list and send it to customers.
  </Step>

  <Step title="Watch orders appear">
    Completed purchases arrive automatically under **Products & Services → Orders**. See [Orders overview](/orders/overview).
  </Step>
</Steps>

## Where to find the module

### Team members

Team members with the appropriate role permission see a **Services** menu in the main navigation containing three sections:

| Menu item    | Purpose                                                           |
| ------------ | ----------------------------------------------------------------- |
| **Services** | Create and manage every product or service you sell.              |
| **Forms**    | Bundle services into shareable checkout pages.                    |
| **Orders**   | View and manage every completed purchase and active subscription. |

Module-level settings — general options, PayPal API credentials, and email templates — live under **Settings → Products & Services**. See [General settings](/settings/general).

### Clients

Clients see a simplified **Services** menu with two entries:

| Menu item    | Purpose                                                                                              |
| ------------ | ---------------------------------------------------------------------------------------------------- |
| **Services** | A public catalog listing every enabled checkout form — clients click through to browse and purchase. |
| **Orders**   | Their own purchase history and subscription status.                                                  |

Clients never see management screens such as the service editor or the forms builder. They only ever interact with the public-facing catalog and their own order records.

## Role-based permissions

Access to the Products & Services module for team members is controlled by the **Services** permission on their role. Adjust role permissions under **Settings → Roles**.

| Permission level   | What the team member can do                                                    |
| ------------------ | ------------------------------------------------------------------------------ |
| **None**           | No access to Services, Forms, or Orders at all.                                |
| **View**           | Can open and read Services, Forms, and Orders, but cannot make any changes.    |
| **Manage / Admin** | Everything in View, plus create, edit, and delete services and checkout forms. |

<Info>
  Clients are not affected by role permissions. They always see their own orders and the public services catalog — nothing more.
</Info>

## Before you start selling

Two payment gateway requirements must be met before customers can complete a checkout. Missing either one means checkout will not offer that payment method, even if it appears enabled inside this module.

<Warning>
  Payment gateways must be enabled in **two separate places**. Turning Stripe or PayPal on under **Settings → Products & Services → General** tells this module to offer that method at checkout — but the gateway also needs to be configured and enabled in your CRM's **main** payment gateway settings (outside this module). Both switches must be on for the gateway to work.
</Warning>

### Stripe

Stripe reuses the same account credentials already configured in your CRM's main payment gateway settings — you do not need to enter any Stripe keys inside this module. All you need to do is toggle **Enable Stripe payment gateway** on under **Settings → Products & Services → General**.

### PayPal

PayPal works differently. This module integrates with PayPal's API directly (to support subscriptions and webhook-based renewals), so it requires its own dedicated API credentials — separate from any PayPal gateway you may have configured elsewhere in the CRM.

<Note>
  Go to **Settings → Products & Services → PayPal (API)** and enter a Client ID and Secret Key from a PayPal API app. You will also need to paste the module's **Webhook URL** into your PayPal app's webhook configuration so that renewal and cancellation events are delivered correctly. See [Payment gateways](/settings/payment-gateways) for the full setup steps.
</Note>
