Actindo App for Laioutr

A Laioutr App that integrates the Actindo Order Management System into the Laioutr platform.

The app connects a Laioutr storefront to Actindo as its commerce data source — products, variants, categories, navigation and availability — through the Actindo Storefront Data Service, a read-only web service provided by Actindo. The API is documented at laioutr.actindo.com/docs.

See laioutr.com for more information about Laioutr.

• ✨  Release Notes

How it works

The Actindo Storefront Data Service is a layout-facing read API whose field shapes mirror the Laioutr canonical components, so its responses map cleanly onto the storefront. This app wraps that service and exposes its data to the storefront through Orchestr query handlers.

• Authentication — the service uses a per-tenant Bearer API key (bearerAuth) that resolves server-side to exactly one Actindo tenant.
• Direction — read-only. The app consumes Actindo data for rendering; it does not write back to Actindo.
• Mapping — response shapes follow the canonical layout components, minimizing transformation between Actindo and the storefront.

Data the service provides

| Resource | Operations | | --- | --- | | Products | by slug, search (with filters & facets), batch fetch by IDs, breadcrumb | | Variants | per-product variant IDs, batch fetch variants | | Availability | batch availability check for multiple items | | Categories | by slug, list all IDs, batch fetch, products within a category | | Navigation | navigation tree by alias | | Health | service health check |

Features

• 🛒  Actindo as the storefront commerce data source
• 🔎  Product & category search with filters and facets
• 🧬  Variant and availability resolution
• 🧭  Category-driven navigation trees
• 🔌  Canonical-aligned responses, wired in via Orchestr handlers

Quick Setup

Before installing dependencies, you need to create a copy of the .npmrc.config file called .npmrc and fill in the NPM_LAIOUTR_TOKEN with your npm token. You can find this token in your project settings.

• pnpm i
• npx @laioutr/cli project fetch-rc -p <organization slug>/<project slug> -s <project secret key> - This will load the laioutrrc.json file with the current remote project configuration.
• pnpm dev:prepare
• pnpm orchestr-dev

You also need to configure the Actindo connection. The Storefront Data Service expects a per-tenant Bearer API key; provide it through the module's runtime config so it is only available server-side and never exposed to the client.

That's it! You can now use the Actindo App in your Laioutr Frontend ✨

You can find a thorough guide on getting started with Laioutr development in our developer guide.

Linting and Formatting

We use ESLint and Prettier to lint and format the code. This repository contains opinionated configurations for both tools. You can - of course - replace them with your own configurations.

Publishing

Releases are managed with Changesets and published to npmjs.org automatically by the release workflow.

To ship a change:

1. In your PR, run pnpm changeset and follow the prompt to record the change and the version bump (patch/minor/major). Commit the generated file in .changeset/.
2. Merge the PR to main. The release workflow opens (or updates) a "Version Packages" PR that applies the pending changesets to the version and CHANGELOG.md.
3. Merge the "Version Packages" PR. The workflow builds the package and publishes it to npmjs.org, tags the commit, and creates a GitHub release.

Publishing uses npm OIDC trusted publishing, so no npm token is stored in the repository — the workflow needs id-token: write and a trusted publisher configured for the package on npmjs.org.

Contribution

Follow the setup guide to get started.