Platform Architecture

Propeller is a headless, composable commerce platform: the frontend is decoupled from the commerce backend and every capability is available through open APIs. This section gives you the mental model you need before you start building. By the end of these three pages you will understand Propeller's data model, know which API to use for what and have your API credentials ready.

Propeller platform architecture. Storefronts, customer portals and the Propeller apps use the GraphQL API. AI assistants use the MCP server. Business systems such as ERP, PIM and CRM use the REST API. Automation tools receive webhooks. Every API works on the same platform data.

Storefronts and portals

• B2B webshop
• Customer portal
• Dealer portal
• Spare parts portal

Built with the Storefront SDK, the WordPress Plugin or your own frontend

Propeller apps

• Backoffice
• Sales Hub

For merchants and their sales reps

AI assistants

• Claude Desktop
• Cursor
• Your own app

Any MCP-compatible client

GraphQL APIfor frontends

MCP serverfor AI assistants

Propeller platform

Every API reads and writes the same data: a product imported through REST is live in GraphQL straight away.

• CatalogProducts, clusters, categories and attributes
• PricingPricesheets, discounts and cost prices
• CustomersCompanies, contacts and customers
• Carts and ordersCarts, quotes, orders and shipments
• Business rulesShipping costs, carriers, payment methods and incentives
• Events and templatesEvent actions, email templates and PDF templates

One tenant, many channels. Each storefront gets its own catalog structure, languages and SEO on the shared data.

REST APIfor integrations

Webhookson events

Business systems

• ERP
• PIM
• CRM
• PLM
• WMS

Connected directly or through an iPaaS

Automation tools

• n8n
• iPaaS
• Your own services

Receive platform events and AI agent requests

API surfaces

The GraphQL API is the frontend API. Partners use it to build customer-facing experiences: webshops, B2B customer portals and self-service ordering interfaces. The Storefront SDK and the WordPress Plugin are both built on the GraphQL API. Partners who prefer no SDK use the GraphQL API directly from any framework.

The REST API is the integration API. Partners use it to connect Propeller with backend business applications: ERP systems, PIM, CRM and other operational tools. These integrations handle product sync, order flow, inventory management, customer data and pricing.

The MCP Server is the AI agent API. It lets AI agents and other MCP-compatible hosts interact with Propeller data programmatically.

Platform components

Component	Type	Description
GraphQL API	Open API	GraphQL interface for flexible data querying and mutations
REST API	Open API	REST endpoints for platform integration
MCP Server	Open API	MCP interface for AI agents and MCP-compatible hosts
Storefront SDK	npm Packages and Starter Apps	Built on the GraphQL API: a typed client, React and Vue 3 UI libraries and Next.js, Vue and Nuxt boilerplates
WordPress Plugin	Frontend Plugin	Plugin for quickly setting up a B2B customer portal on WordPress
Backoffice	Frontend UI	Platform management interface for B2B commerce logic
Sales Hub	Frontend UI	Interface for sales reps to manage quotes, orders, companies and contacts

How it fits together

Most implementations involve two primary workstreams:

1. Frontend development using the GraphQL API (directly or through the Storefront SDK or WordPress Plugin) to build the customer-facing experience
2. Integration development using the REST API to keep product data, pricing and orders in sync with backend systems

The AI agent layer is an additional surface that partners can adopt independently of the other two workstreams.

Next: Core Concepts

Learn the key data model concepts before you start making API calls.

Core Concepts →