Skip to content

Headless commerce

Generated from the architecture model

This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
Vertical Commerce
Prototype reference Commerce prototype (ConnectSoft.DesignPrototypes)
Managed edition Managed (D33, D34)
Data residency tenant-region (D31)
Catalog Examples catalog · Vision-to-Production path for this vertical

Business problem

A retailer's storefront, catalog and order systems cannot be changed independently; promotions take weeks.

Product intent

Catalog, pricing and promotions, cart and checkout, orders and fulfilment as separate contexts behind one API, with the storefront as a separate frontend.

What the Factory makes different here: pricing rules as a shared-kernel library generated from the Backend Library Blueprint.

Vision-to-Production path for this vertical

Step Factory platform Agents Blueprints
Vision and product plan Agent Mesh, Control plane Product Manager Agent, Enterprise Architect Agent vision
Architecture and domain Template & Library (BC-02) Enterprise Architect Agent service, module, api-gateway, database
Experience Template & Library, Factory Studio UX track UX Designer Agent, Frontend Developer Agent frontend
Recipe and generation Template & Library (BC-15), Agent Mesh, Tools & MCP Product Manager Agent, Enterprise Architect Agent, Backend Developer Agent, Frontend Developer Agent, Database Engineer Agent, QA Agent module plan from the context map
Quality Observability (BC-22), DevOps / GitOps QA Agent test
Delivery and provisioning DevOps / GitOps (BC-23, BC-24), Runtime Cloud (BC-25) DevOps Agent, Infrastructure Architect Agent —
Operations Product Fleet Operations (BC-35..37) — handover, objectives, rollouts, incidents, off-boarding

Delivery workflows exercised: software-engineering-workflows, growth-and-marketing-workflows.

Generated product shape

C4Context
    title Headless commerce system context
    Person(user, "Users", "Commerce users and operators")
    System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
    System_Boundary(product, "Headless commerce") {
        System(ctx_Catalog, "Catalog", "products, variants, availability")
        System(ctx_Pricing, "Pricing", "prices, promotions, rules")
        System(ctx_Checkout, "Checkout", "carts, payment intents")
        System(ctx_Fulfilment, "Fulfilment", "shipments, returns")
    }
    Rel(user, ctx_Catalog, "uses through the product gateway GW-07")
    Rel(factory, ctx_Catalog, "descriptor, health, rollouts, incidents, off-boarding")
Hold "Alt" / "Option" to enable pan & zoom

Bounded contexts

Context Responsibility Published events
Catalog products, variants, availability ProductPublished
Pricing prices, promotions, rules PromotionActivated
Checkout carts, payment intents OrderPlaced
Fulfilment shipments, returns ShipmentDispatched

Modules and templates

Module Template Notes
Microservice ×4 connectsoft-microservice
Pricing library connectsoft-library
API gateway connectsoft-apigateway
Storefront MFEs connectsoft-blazor-mfe
Every product also gets the SaaS foundations (tenants, editions, entitlements, billing, metering) and the product host shape (descriptor, health, operations handover) unless it is a library-only product.

Prototype reference

Commerce prototype in ConnectSoft.DesignPrototypes shows the intended screens; the UX track (U1–U4) maps prototype destinations to the UX model's screens with keep, merge, rename, retire or new decisions.

Operations as a managed product

Managed; payment provider through a certified connector; PCI scope kept in the provider.