---
title: "Fulfillment Accounts"
description: "A non-technical overview of Fulfillment Accounts in RevCent, focused on how they configure fulfillment provider connections, how they relate to Site Fulfillment Centers and Secure Forms, how shippable products and Shipping records use them, and how they support fulfillment, tracking, cancellation, support, automation, and reporting."
type: "feature"
company: "RevCent"
canonical: "https://revcent.com/documentation/markdown/ecosystem/feature/FulfillmentAccount.md"
relationships:
  - name: "Shipping"
    url: "https://revcent.com/documentation/markdown/ecosystem/item/Shipping.md"
technical_links:
  web_app: "https://kb.revcent.com/en/integrations/fulfillment-account"
  api:
    section: "https://revcent.com/docs/api/v2#section-fulfillment"
    operations:
      - name: "Get Fulfillment Accounts"
        operation_id: "GetFulfillmentAccounts"
        operation: "https://revcent.com/docs/api/v2#operation-GetFulfillmentAccounts"
        schema: "https://revcent.com/documentation/files/api/operation/GetFulfillmentAccounts.json"
      - name: "Create A Fulfillment Account"
        operation_id: "CreateFulfillmentAccount"
        operation: "https://revcent.com/docs/api/v2#operation-CreateFulfillmentAccount"
        schema: "https://revcent.com/documentation/files/api/operation/CreateFulfillmentAccount.json"
      - name: "Get A Fulfillment Account"
        operation_id: "GetFulfillmentAccount"
        operation: "https://revcent.com/docs/api/v2#operation-GetFulfillmentAccount"
        schema: "https://revcent.com/documentation/files/api/operation/GetFulfillmentAccount.json"
      - name: "Edit A Fulfillment Account"
        operation_id: "EditFulfillmentAccount"
        operation: "https://revcent.com/docs/api/v2#operation-EditFulfillmentAccount"
        schema: "https://revcent.com/documentation/files/api/operation/EditFulfillmentAccount.json"
      - name: "Delete A Fulfillment Account"
        operation_id: "DeleteFulfillmentAccount"
        operation: "https://revcent.com/docs/api/v2#operation-DeleteFulfillmentAccount"
        schema: "https://revcent.com/documentation/files/api/operation/DeleteFulfillmentAccount.json"
      - name: "Get Site Fulfillment Centers"
        operation_id: "GetSiteFulfillmentCenters"
        operation: "https://revcent.com/docs/api/v2#operation-GetSiteFulfillmentCenters"
        schema: "https://revcent.com/documentation/files/api/operation/GetSiteFulfillmentCenters.json"
      - name: "Get A Site Fulfillment Center"
        operation_id: "GetSiteFulfillmentCenter"
        operation: "https://revcent.com/docs/api/v2#operation-GetSiteFulfillmentCenter"
        schema: "https://revcent.com/documentation/files/api/operation/GetSiteFulfillmentCenter.json"
  mcp:
    overview: "https://revcent.com/documentation/markdown/mcp/operation/OverviewFulfillment.md"
    operations:
      - name: "Get Fulfillment Accounts"
        operation_id: "GetFulfillmentAccounts"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetFulfillmentAccounts.md"
        available_via_ai: true
      - name: "Create A Fulfillment Account"
        operation_id: "CreateFulfillmentAccount"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/CreateFulfillmentAccount.md"
        available_via_ai: true
      - name: "Get A Fulfillment Account"
        operation_id: "GetFulfillmentAccount"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetFulfillmentAccount.md"
        available_via_ai: true
      - name: "Edit A Fulfillment Account"
        operation_id: "EditFulfillmentAccount"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/EditFulfillmentAccount.md"
        available_via_ai: true
      - name: "Delete A Fulfillment Account"
        operation_id: "DeleteFulfillmentAccount"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/DeleteFulfillmentAccount.md"
        available_via_ai: true
      - name: "Get Site Fulfillment Centers"
        operation_id: "GetSiteFulfillmentCenters"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetSiteFulfillmentCenters.md"
        available_via_ai: true
      - name: "Get A Site Fulfillment Center"
        operation_id: "GetSiteFulfillmentCenter"
        markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetSiteFulfillmentCenter.md"
        available_via_ai: true
  bigquery_schema: "https://revcent.com/documentation/files/bigquery/dataset.json"
  bigquery_tables:
    - "fulfillment_account"
---

# Fulfillment Accounts

Fulfillment Accounts are the RevCent feature used to connect a business's fulfillment center, warehouse, third-party logistics provider, or fulfillment software to RevCent.

A Fulfillment Account is not a shipment. It is the reusable account-level configuration that tells RevCent which fulfillment provider account should be used when physical products need to be shipped.

The practical idea is:

```text
Fulfillment Account = configured fulfillment provider connection
Shipping = individual shipment item created from commerce activity
Site Fulfillment Center = RevCent-supported provider/integration definition
```

Fulfillment Accounts matter because ecommerce businesses often rely on external systems to pick, pack, ship, and update tracking for physical products. RevCent stores the fulfillment configuration so shippable orders can move from commerce activity into fulfillment operations.

---

## Why Fulfillment Accounts Are a Feature

Fulfillment Accounts are a feature because they are configurable account-level setup records.

A Fulfillment Account defines how RevCent connects to a fulfillment provider. It is reused across many shippable products, sales, renewals, trials, and Shipping records.

Conceptually:

```text
Business creates Fulfillment Account
  ↓
Business selects supported Site Fulfillment Center
  ↓
Credentials/configuration are saved securely
  ↓
Shippable products are associated with the Fulfillment Account
  ↓
Sales and renewals create Shipping records
  ↓
Shipping records can move through fulfillment workflows
```

This makes Fulfillment Accounts different from Shipping records. A Shipping record is the individual shipment item. A Fulfillment Account is the feature that connects eligible shipment work to a fulfillment provider.

---

## Technical Links

| Area | Link |
|---|---|
| Web App | `https://kb.revcent.com/en/integrations/fulfillment-account` |
| API | `https://revcent.com/docs/api/v2#section-fulfillment` |
| MCP / AI | `https://revcent.com/documentation/markdown/mcp/operation/OverviewFulfillment.md` |
| BigQuery Schema | `https://revcent.com/documentation/files/bigquery/dataset.json` |
| BigQuery Tables | `fulfillment_account` |

---

## Core Purpose

The core purpose of a Fulfillment Account is to connect RevCent shipping activity to the external system responsible for fulfillment.

A Fulfillment Account helps answer questions such as:

- Which fulfillment provider, warehouse, or shipping software should handle this product?
- Which user-specific provider account should RevCent use?
- Is the fulfillment connection enabled?
- Have the required provider fields been saved?
- Which shippable products are associated with this fulfillment setup?
- Can RevCent cancel an unshipped shipment after a full refund or void?
- Which fulfillment configurations exist for this RevCent account?

For a business selling physical goods, Fulfillment Accounts form the bridge between RevCent commerce records and the fulfillment system responsible for delivery.

---

## Site Fulfillment Center vs Fulfillment Account

A key concept is the difference between a Site Fulfillment Center and a Fulfillment Account.

| Concept | Meaning |
|---|---|
| Site Fulfillment Center | A RevCent-supported fulfillment provider or integration definition. It describes the available provider and the required fields needed to connect to it. |
| Fulfillment Account | The user's configured connection to one selected Site Fulfillment Center. It stores the user's specific fulfillment setup and secure credentials/configuration. |

In plain language:

```text
Site Fulfillment Center = the provider/integration type RevCent supports
Fulfillment Account = the business's configured account with that provider
```

The user does not create a Site Fulfillment Center. RevCent exposes supported Site Fulfillment Centers. The user chooses one and creates a Fulfillment Account connected to it.

---

## Site Fulfillment Centers

Site Fulfillment Centers answer:

```text
Which fulfillment provider types are available?
What information is required to connect to each provider?
```

A Site Fulfillment Center may define required provider-specific fields such as:

- API key
- account ID
- warehouse ID
- username
- password
- client ID
- location ID
- other provider-specific configuration values

The exact fields depend on the selected Site Fulfillment Center.

This matters because the provider selection determines what the Fulfillment Account needs before it can operate correctly.

---

## Secure Credential Handling

Fulfillment credentials are sensitive.

They may include API keys, passwords, account IDs, tokens, warehouse IDs, or other provider-specific values.

Fulfillment credentials should not be pasted directly into:

- AI chats
- support notes
- metadata
- ordinary API request bodies
- logs
- internal messages

Use Secure Forms instead.

For fulfillment credentials, a Secure Form should be created for the selected Site Fulfillment Center. The user then completes the Secure Form, and RevCent saves the credential/configuration data securely.

Conceptual flow:

```text
User chooses Site Fulfillment Center
  ↓
Secure Form is created for that fulfillment center
  ↓
User opens secure form URL
  ↓
User enters required credentials/configuration
  ↓
RevCent encrypts and saves the data internally
  ↓
Fulfillment Account is created or edited using secure_form_id
```

Secure Forms are temporary. They are intended for sensitive input and should be completed promptly. If credentials need to be changed later, create a new Secure Form and use it with the relevant edit workflow.

---

## Creating a Fulfillment Account

In the RevCent web app, Fulfillment Accounts are created from the Integrations > Fulfillment area.

The general setup process is:

```text
1. Review available fulfillment center/software options.
2. Choose the correct Site Fulfillment Center.
3. Review required provider fields.
4. Complete the secure credential/configuration process when needed.
5. Create the Fulfillment Account.
6. Enable the Fulfillment Account after setup is verified.
7. Associate shippable products with the Fulfillment Account.
```

Common settings include:

| Setting | Purpose |
|---|---|
| Name | Required display name for the Fulfillment Account. |
| Description | Optional explanation of what the account is used for. |
| Status | Whether the Fulfillment Account is enabled or disabled. |
| Fulfillment Center | The selected provider/integration type. |
| Provider-specific fields | Additional connection values required by the selected provider. |
| Secure Form | Secure credential/configuration collection when required. |

The Knowledge Base notes that the fulfillment center cannot be changed after the Fulfillment Account is created in the web app. Choose the correct fulfillment provider before creating the account.

---

## Fulfillment Account Naming

Fulfillment Account names should clearly identify the operational use of the account.

Good examples:

```text
Brand A - US Warehouse Fulfillment
Brand B - ShipStation Fulfillment
Main WooCommerce Store Fulfillment
Subscription Product Fulfillment
EU Warehouse Fulfillment
```

A generic name like `Fulfillment` is not helpful when the business has multiple stores, brands, warehouses, regions, or providers.

Descriptions should explain when the account is used, such as:

```text
Primary fulfillment account for Brand A physical products sold through the main WooCommerce store.
```

---

## Editing a Fulfillment Account

After creation, a Fulfillment Account can be edited.

Common edit reasons include:

- rename the account
- update the description
- enable or disable the account
- update provider-specific credentials/configuration through a secure process
- adjust cancellation behavior when supported

Important: do not assume every provider supports the same fields or capabilities. The selected Site Fulfillment Center determines which fields and behaviors are available.

---

## Important Fulfillment Account Status Fields

When retrieving or inspecting a Fulfillment Account, important status fields include:

```text
enabled
cancel_on_void
fulfillment_center
fulfillment_center_fields_saved
```

### `enabled`

`enabled` determines whether the Fulfillment Account should be treated as active.

A disabled account should not be treated as a ready fulfillment option.

A safe setup approach is:

```text
Create disabled while credentials/configuration are being tested
  ↓
Verify required fields are saved and the provider connection is ready
  ↓
Enable the Fulfillment Account
```

### `fulfillment_center_fields_saved`

`fulfillment_center_fields_saved` indicates whether the required provider fields have been saved to the Fulfillment Account.

If this value is false, the account may not be fully configured.

Conceptually:

```text
fulfillment_center_fields_saved = false
  ↓
Required provider credentials/configuration may be missing
  ↓
Fulfillment Account may not be ready for live fulfillment
```

### `cancel_on_void`

`cancel_on_void` controls whether RevCent should automatically contact the fulfillment provider and cancel an unshipped shipment if the order has been fully refunded or voided.

The business value is straightforward:

```text
Order is fully refunded or voided
  ↓
Shipment has not shipped yet
  ↓
Fulfillment provider supports cancellation
  ↓
RevCent can attempt to cancel the shipment
```

This can help avoid shipping cancelled orders, reduce unnecessary fulfillment costs, and prevent customer confusion.

Not all fulfillment centers support order cancellation. This behavior is provider-dependent.

---

## Fulfillment Accounts and Shippable Products

Fulfillment Accounts become operational when they are associated with shippable products.

For physical products, the product should be marked shippable, and its shipping attributes should identify the Fulfillment Account that should handle fulfillment.

Conceptually:

```text
Product is shippable
  ↓
Product has shipping attributes
  ↓
Product is associated with a Fulfillment Account
  ↓
Sale occurs
  ↓
RevCent knows which fulfillment provider/account should receive shipment work
```

The important operational rule is:

```text
Every product with is_shippable = true should have a valid shipping_attributes.fulfillment_account.
```

This association allows RevCent to route fulfillment based on the product sold.

Examples:

```text
Brand A Supplement → Brand A Fulfillment Account
Brand B Skincare Product → Brand B Fulfillment Account
US Product → US Warehouse Fulfillment Account
EU Product → EU Warehouse Fulfillment Account
Subscription Refill Product → Subscription Fulfillment Account
```

Without this association, RevCent may not know where to send the fulfillment request or which provider configuration should be used.

---

## Bundles and Fulfillment

Bundles can make fulfillment more complex.

If a bundle is sold, fulfillment may need to know which individual physical products should actually be shipped.

Conceptually:

```text
Bundle product sold
  ↓
Bundle is unbundled based on configuration
  ↓
Individual shippable products are identified
  ↓
Each shippable component must have proper fulfillment routing
  ↓
Fulfillment proceeds correctly
```

For bundles, confirm that every shippable component has clear fulfillment configuration.

---

## Relationship to Shipping

Fulfillment Accounts are closely related to Shipping records.

A Shipping record represents a specific shipment: what needs to be shipped, who it should be shipped to, its status, tracking details, and fulfillment progress.

A Fulfillment Account represents the connected fulfillment provider account that may handle that shipment.

Conceptually:

```text
Fulfillment Account
  ↓
Connected fulfillment provider/software
  ↓
Shipping records for shippable products
  ↓
Fulfillment, tracking, shipment status, and possible cancellation behavior
```

This relationship is important because Fulfillment Accounts are not useful in isolation. Their value comes from enabling shippable orders and Shipping records to move from RevCent into a fulfillment process.

---

## Tracking Numbers and Tracking URLs

A Fulfillment Account can be the source of shipment tracking information.

When a fulfillment provider processes a shipment, RevCent can receive details such as:

- tracking number
- tracking URL
- shipping provider
- shipping method
- shipped status
- ship date
- shipment-related status updates

Conceptually:

```text
Sale requires shipment
  ↓
Fulfillment Account sends shipment to provider
  ↓
Fulfillment provider creates tracking number
  ↓
RevCent receives tracking number / tracking URL
  ↓
User and customer can track the package
```

Tracking numbers help users and support teams answer customer questions such as:

```text
Has this package shipped?
What is the tracking number?
Which carrier is handling the shipment?
Can support send the tracking URL to the customer?
```

Tracking numbers and tracking URLs can also be used in customer-facing workflows, such as shipment notification Email Templates.

---

## Delivery Updates Require EasyPost or Shippo

Receiving a tracking number is different from knowing when a shipment was delivered.

If the business wants RevCent to know when a package was delivered, the user should add an EasyPost or Shippo third-party integration.

The distinction is:

```text
Fulfillment Account = receives tracking number / tracking URL from the fulfillment provider
EasyPost or Shippo = receives delivery updates, such as when the package was delivered
```

Use EasyPost or Shippo when the business wants delivery-level visibility for workflows such as:

- delivery confirmation emails
- post-delivery customer engagement
- AI Assistant follow-up
- AI Voice Agent follow-up
- internal operations updates
- delivered shipment reporting
- chargeback evidence for product-not-received disputes

EasyPost or Shippo is not required simply because a Fulfillment Account exists. It is needed when delivered-status updates should be available inside RevCent.

---

## Shipping Events and Automation

Shipping and fulfillment activity can trigger workflows across RevCent.

Examples of shipping-related events include:

```text
Shipment created
Tracking number added
Shipment sent to fulfillment
Shipment shipped
Shipment delivered
Shipment updated
Fulfillment notification failed
Shipment cancelled
```

These events can drive automation such as:

- Email Templates for tracking, shipped, or delivered emails
- Functions that send tracking data to external systems
- AI Assistants that summarize shipping issues or recommend next actions
- AI Voice Agents that contact customers about high-value or delayed shipments
- support alerts when fulfillment fails
- customer group or metadata updates
- chargeback prevention workflows

The exact event notation should be selected from the available RevCent trigger list when configuring the automation.

---

## Fulfillment and Customer Experience

Fulfillment data helps customers understand what is happening after purchase.

A typical customer-facing journey can look like this:

```text
Order placed
  ↓
Shipment created
  ↓
Tracking number added
  ↓
Customer receives tracking email
  ↓
Shipment shipped
  ↓
Customer receives shipping confirmation
  ↓
Shipment delivered
  ↓
Customer receives delivery confirmation or post-purchase follow-up
```

This reduces customer uncertainty and common support questions such as:

```text
Where is my order?
Has my package shipped?
Can I get my tracking number?
When will it arrive?
```

---

## Fulfillment and Customer Support

Fulfillment data helps support teams answer practical questions:

```text
Has the order been sent to fulfillment?
Which provider is handling it?
Has the item shipped?
What is the tracking number?
Was the package delivered?
Can the shipment still be cancelled?
```

A well-configured Fulfillment Account can reduce support friction because support teams can understand order and shipping status more clearly.

---

## Fulfillment and Chargeback Evidence

Fulfillment and shipping data can be important when fighting chargebacks, especially product-not-received disputes.

Useful evidence can include:

- shipping provider
- shipping method
- tracking number
- tracking URL
- shipped status
- delivered status
- ship date
- delivered date
- ship-to details
- fulfillment provider/account context

Conceptual flow:

```text
Package delivered
  ↓
Delivery update is stored in RevCent
  ↓
Customer later files product-not-received chargeback
  ↓
Chargeback evidence can include shipping/tracking/delivery details
```

This ties fulfillment directly to risk management and revenue protection.

---

## Fulfillment for Multi-Brand, Multi-Store, or Multi-Warehouse Businesses

Some RevCent accounts manage multiple brands, websites, stores, warehouses, or regions.

Fulfillment Accounts can support this by separating fulfillment setup by operational need.

Examples:

```text
Brand A Fulfillment Account
Brand B Fulfillment Account
WooCommerce Store A Fulfillment
US Warehouse Fulfillment
EU Warehouse Fulfillment
Subscription Product Fulfillment
```

Separate Fulfillment Accounts may be useful when:

- different brands use different warehouses
- different stores use different providers
- different products ship from different locations
- different regions require different fulfillment setups
- different providers require different credentials
- testing and production accounts should remain separate

---

## API and MCP Context

The API and MCP references are the technical sources for exact operation names, request schemas, and fulfillment workflow behavior.

At a high level, AI/MCP workflows should distinguish between:

```text
Site Fulfillment Center = RevCent-supported provider/integration definition
Fulfillment Account = user-created provider account connection
Shipping = individual shipment item
```

A safe AI/MCP setup flow is:

```text
1. Retrieve available Site Fulfillment Centers.
2. Choose the correct Site Fulfillment Center.
3. Review required fields.
4. Create a Secure Form for sensitive credentials/configuration.
5. Have the user complete the Secure Form.
6. Create or edit the Fulfillment Account using the secure_form_id.
7. Verify enabled status and required fields.
8. Confirm shippable products are associated with the correct Fulfillment Account.
```

AI/MCP should not request fulfillment credentials directly in chat. Sensitive credentials should be collected with Secure Forms.

---

## BigQuery Table: `fulfillment_account`

The `fulfillment_account` table contains Fulfillment Accounts created by the user.

Reference it in BigQuery as:

```sql
`revcent.user.fulfillment_account`
```

Useful fields include:

| Field | Meaning |
|---|---|
| `created_at` | Timestamp of when the Fulfillment Account was created. |
| `id` | Fulfillment Account ID. |
| `name` | Name set by the user. |
| `description` | Description set by the user. |
| `enabled` | Whether the Fulfillment Account is enabled. |

This table is useful for reporting on configured fulfillment connections, auditing which Fulfillment Accounts exist, and identifying whether fulfillment configurations are enabled or disabled.

For shipment-level operational reporting, use Shipping data and relate it back to fulfillment context where available.

---

## Fulfillment Account Reporting Examples

Fulfillment Account reporting can answer questions such as:

```text
Which Fulfillment Accounts exist?
Which Fulfillment Accounts are enabled?
When were Fulfillment Accounts created?
Which fulfillment configurations are disabled?
Which fulfillment names or descriptions need cleanup?
```

Example conceptual query:

```sql
SELECT
  id,
  name,
  description,
  enabled,
  created_at
FROM `revcent.user.fulfillment_account`
ORDER BY created_at DESC;
```

Operational reporting can also combine Fulfillment Account context with Shipping data to understand fulfillment performance, provider usage, delayed shipments, cancellation behavior, and product-not-received chargeback risk.

---

## Common Mistakes to Avoid

Do not confuse Fulfillment Accounts with Shipping records.

Do not treat a Fulfillment Account as the shipment itself.

Do not confuse a Site Fulfillment Center with a Fulfillment Account.

Do not assume users create Site Fulfillment Centers; users create Fulfillment Accounts connected to RevCent-supported Site Fulfillment Centers.

Do not collect fulfillment credentials directly in AI chat, support notes, metadata, or ordinary request bodies.

Do not assume every fulfillment provider supports the same credential fields.

Do not assume every fulfillment provider supports shipment cancellation.

Do not forget to associate shippable products with the correct Fulfillment Account.

Do not enable a Fulfillment Account before required provider fields are saved and the connection is verified.

Do not add EasyPost or Shippo solely because a Fulfillment Account exists; add them when delivered-status updates are needed inside RevCent.

Do not troubleshoot shipping failures only from the Shipping record; also verify the related fulfillment configuration and provider-specific connection settings.

---

## Setup Checklist

Before relying on a Fulfillment Account for live shipping, confirm:

1. The correct Site Fulfillment Center was selected.
2. The Fulfillment Account has a clear name and description.
3. Sensitive credentials/configuration were collected securely.
4. Required fulfillment center fields are saved.
5. The Fulfillment Account is enabled when ready.
6. `cancel_on_void` is configured appropriately for the provider and business process.
7. Every shippable product is associated with the correct Fulfillment Account.
8. Tracking number and tracking URL behavior is understood.
9. EasyPost or Shippo is added only if delivered-status updates are needed.
10. Shipping events are connected to customer communication, support, or automation workflows where useful.

---

## Summary

Fulfillment Accounts are the RevCent feature used to connect fulfillment providers, warehouses, or fulfillment software to RevCent.

They are reusable configuration records. Shipping records are individual shipment items. Site Fulfillment Centers are RevCent-supported provider definitions.

The key concept is:

```text
Site Fulfillment Center = supported provider/integration definition
Fulfillment Account = user-created configured provider account
Shipping = individual shipment item
```

A well-configured Fulfillment Account helps ecommerce businesses send shippable products to the correct fulfillment provider, keep fulfillment credentials secure, receive tracking numbers and tracking URLs, optionally receive delivery updates through EasyPost or Shippo, cancel unshipped orders after full refund or void when supported, support customer service, trigger post-purchase automation, and provide shipping evidence for chargeback mitigation.


---
Document Parent Directory
* [Features](https://revcent.com/documentation/markdown/ecosystem/feature/index.md) - Non-technical markdown documentation for features within the RevCent ecosystem. A feature is a part of the RevCent ecosystem that a user can create and configure.