Works with any frontend stack

Build the storefront your way

Keep control of the shopping experience, use real tooling to connect it, and let EcomWeb handle the operations system behind it.

Architecture

Your own storefront, a shared system.

The integration path separates the customer experience from the operational modules, so teams can change the storefront without rebuilding the commerce system.

  1. Storefront
  2. Data integration layer
  3. The EcomWeb system

Setup

Three steps to a live storefront.

Scaffold from a template, connect the store data, then hand the repetitive work to the tooling. Everything else is optional.

  1. Scaffold the storefront

    Start from the Next.js starter and customize the design and content. Nothing to host or configure first.

    • Next.js starter
    • JavaScript SDK
  2. Connect the store data

    Point the storefront at products and the buying journey, and subscribe to store events where an outside workflow needs them.

    • Store data API
    • Store events
  3. Automate the rest

    Run the store from a terminal or hand routine work to a coding assistant, within the scope you allow and with confirmation before anything consequential.

    • Command line tooling
    • AI coding assistants
    • Scoped permissions

Technical examples

Start with the commands and APIs already in the codebase.

The examples below use the real EcomWeb CLI commands and the createEcomwebSdk, IHttpClient and products.getBySlug identifiers from the EcomWeb SDK.

CLI workflowshell
npx @ecomweb/cli setup
ecomweb products list --status active

Coding assistants and automations must state their scope, check the impact and get confirmation before anything consequential.

Technical documentation

Carry on with the technical docs.

Read the integration guides and the safety principles before putting the tooling into your workflow.

Build the storefront your way | EcomWeb