Introduction

Sellforge brings product catalogs, orders, inventory, checkout, and invoicing into a shared commerce platform. These guides cover two ways to integrate: calling the HTTP API and extending the kernel with a plugin.

Choose your integration

Shops and sales channels

A tenant represents a shop and defines its data boundary. A sales channel is a selling context inside that shop, with its own product listings and configuration. A channel does not grant access to another tenant.

Administrative requests inherit the permissions of their authenticated user. Storefront requests identify the shop with a publishable key. See Authentication before choosing credentials.

How the backends fit together

The kernel is shared by several backend processes. Each process exposes a specific set of routes:

Use the base URL of the backend serving your integration. A route that exists in the kernel can return 404 on a backend that does not expose it.

About this reference

These guides describe the checked-in kernel at commit fe5c475, reviewed on October 17, 2026. Examples use environment variables for deployment-specific URLs and credentials. Sample IDs are illustrative: replace them with IDs returned by your own shop.

The reference documents the integration paths listed in the navigation. Endpoint behavior is described per resource; do not assume that every legacy route follows one universal response format.

Next step

Follow the quickstart to make a read-only request and inspect a real response from your shop.