Blueprint List Command

Essential knowledge

Intended Audience:

Technical User

Author:

Marco Heuer

Changed on:

20 Aug 2026

Overview

Learn to use the `blueprint list` command to view and track all blueprints installed in a Fluent Commerce account. This article enables implementing partners to perform quick environment inventories and monitor version history across dev, staging, and production.For the business, this provides a clear audit trail and ensures consistency across the platform, resolving the pain point of "version drift." Note: This command requires active account-level authentication; if no blueprints are found, the CLI will return an "info" status rather than an error.

Key points

Purpose: Use `fluent blueprint list` to display all blueprints currently installed in a specific Fluent Commerce account.
Output: Generates a table showing blueprint name, version, module count, and installation timestamp.
Requirements: Requires account-level authentication and an active profile. Use `-p` or `--profile` to check different environments (dev, staging, prod).
Audit Value: Essential for tracking "version drift," verifying deployments, and planning upgrades.
Empty State: If no blueprints are present, it returns "info: No blueprints installed."

The `blueprint list` command displays all blueprints currently installed in a Fluent Commerce account.

Syntax

`fluent blueprint list [options]`

Options

Option	Description	Required	Default
`-p, --profile <profile>`	Profile to use for authentication	No	Current active profile

Authentication

This command requires:

Account-level authentication - Must have valid account credentials
Active profile - Profile must exist and contain account settings

Output

The command displays a table with the following columns:

Column	Description	Example
`name`	Blueprint identifier	`retail-order-management`
`version`	Installed version	`1.0.0`
`modules`	Number of modules	`5`
`installedOn`	Installation timestamp	`2024-12-01T10:30:00Z`

Usage Examples

Basic Usage

List blueprints using current active profile:
`fluent blueprint list`
Output:

`┌─────────────────────────────┬─────────┬─────────┬──────────────────────────┐`

│ name                        │ version │ modules │ installedOn              │
├─────────────────────────────┼─────────┼─────────┼──────────────────────────┤
│ retail-order-management     │ 1.0.0   │ 5       │ 2024-12-01T10:30:00.000Z │
│ inventory-accelerator       │ 2.1.0   │ 3       │ 2024-11-15T08:45:00.000Z │
└─────────────────────────────┴─────────┴─────────┴──────────────────────────┘

Specify Profile

List blueprints using a specific profile:
`fluent blueprint list --profile production`

Check Empty Account

If no blueprints are installed:
`fluent blueprint list -p dev-account`
Output:
`info: No blueprints installed.`

Use Cases

Environment Inventory

Track what's deployed across environments:

`# Check development environment
`

fluent blueprint list -p dev

`# Check staging environment
`

fluent blueprint list -p staging

`# Check production environment
`

fluent blueprint list -p prod

Version Tracking

Monitor blueprint versions for upgrade planning:
`fluent blueprint list -p prod > production-blueprints.txt`

Pre-Installation Check

Verify blueprint isn't already installed:

`# List current blueprints
`

fluent blueprint list

`# Check for conflicts before installing new blueprint
`

fluent blueprint describe new-accelerator.json

Audit Trail

Document installed blueprints for compliance:

`# Generate blueprint inventory report
`

echo "Blueprint Inventory - `$(date)" > report.txt`
fluent blueprint list -p prod >> report.txt

Data Source

Blueprint information is stored in Fluent Commerce account settings:

Setting prefix: `fc.blueprints.*`
Context: ACCOUNT level
Content: Blueprint metadata including name, version, and module list

Common Scenarios

Scenario 1: First Time Setup

Situation: New account with no blueprints
`fluent blueprint list -p new-account`
Result:
`info: No blueprints installed.`
Next Step: Install your first blueprint with `blueprint install`

Scenario 2: Multiple Blueprints

Situation: Account has several accelerators installed
`fluent blueprint list -p enterprise-account`
Result:

`┌─────────────────────────────┬─────────┬─────────┬──────────────────────────┐`

│ name                        │ version │ modules │ installedOn              │
├─────────────────────────────┼─────────┼─────────┼──────────────────────────┤
│ retail-order-management     │ 1.0.0   │ 5       │ 2024-12-01T10:30:00.000Z │
│ inventory-accelerator       │ 2.1.0   │ 3       │ 2024-11-15T08:45:00.000Z │
│ customer-service-tools      │ 1.5.0   │ 4       │ 2024-10-20T14:20:00.000Z │
└─────────────────────────────┴─────────┴─────────┴──────────────────────────┘
Insight: Three blueprints installed, oldest from October

Scenario 3: Check Before Upgrade

Situation: Planning to upgrade a blueprint

`# Check current version
`

fluent blueprint list -p prod | grep order-management

`# Compare with blueprint file version
`

fluent blueprint describe new-order-mgmt-v2.json
Decision: Determine if upgrade is needed based on version comparison

Error Handling

Profile Not Found

Error:
`error: Profile 'unknown-profile' not found`Solution: Check available profiles with `fluent profile list`

Authentication Failed

Error:
`error: Authentication failed for account`Solution:

Verify profile credentials with `fluent profile list`
Correct credentials with `fluent profile update`

Network Issues

Error:
`error: Failed to query installed state: Network error`Solution:

Check internet connectivity
Verify API endpoint is accessible
Check firewall settings

Related Commands

blueprint validate - Validate blueprint structure and business rules
blueprint describe - Preview blueprint file contents
blueprint install - Install a blueprint
profile list - Manage authentication profiles