Amplience and Composable Commerce Glossary

A

Acceptance Testing

The final phase of software quality assurance in which the system is validated against agreed business requirements before go-live. In Amplience implementations, acceptance testing covers content type schema correctness, Dynamic Media delivery performance, slot and edition scheduling accuracy, API response validation, and Visualization SDK preview fidelity. It is the gate between implementation completion and live traffic.

Amplience

A headless CMS and digital asset management platform built specifically for ecommerce. Amplience manages editorial content, media assets, and content delivery for commerce storefronts via API. Its core modules are Content Hub (DAM), Content (CMS and schema), Dynamic Media (image and video delivery), Slots and Editions (scheduled publishing), AI Features (content generation), and the Content Delivery API.

Amplience Audit

AmpliFabrik's structured assessment of an existing Amplience implementation. The audit evaluates content model architecture, Dynamic Media configuration and performance, slot and edition structure, API usage patterns, integration architecture, and feature utilization gaps. It delivers a prioritized remediation roadmap with effort estimates and is the standard starting point for brands that have grown organically on Amplience and accumulated technical debt.

API (Application Programming Interface)

A defined set of protocols and endpoints that allows software systems to communicate and exchange data. In a composable commerce stack, APIs are the connective tissue between platform components — the Amplience Content Delivery API, a commerce engine's product API, and a search platform's query API all feed the storefront independently and are assembled at the rendering layer.

API-First

An architectural approach in which platform capabilities are exposed primarily through APIs rather than tightly coupled front-end interfaces. API-first platforms — including Amplience — can deliver content to any channel or front-end that can make an HTTP request, without being tied to a specific rendering technology. The A in MACH architecture.

Asset Tagging

The process of applying structured metadata — descriptive labels, categories, product associations, and usage rights — to digital assets in a DAM. In Amplience Content Hub, asset tagging can be performed manually or automated using Amplience's AI-assisted tagging capability, which generates tags from image content at ingestion. Well-configured tagging is the foundation of DAM searchability at high asset volumes.

AVIF

AV1 Image File Format. A modern image format offering significantly better compression than JPEG and WebP at equivalent visual quality. Supported in Amplience Dynamic Media as a delivery-time transformation target. Browser support has reached sufficient coverage for use in production ecommerce environments.

C

Cache / Caching

The temporary storage of data — API responses, transformed images, rendered pages — in a location closer to the consumer to reduce latency and origin server load. In Amplience implementations, caching applies at multiple layers: the Content Delivery API response cache, the Dynamic Media CDN cache, and the storefront rendering cache. Cache TTL configuration and invalidation strategy are primary performance considerations in any Amplience delivery architecture.

CDN (Content Delivery Network)

A distributed network of servers that caches and delivers content from locations geographically close to the end user. Amplience Dynamic Media delivers transformed imagery via CDN. CDN caching configuration — TTL settings, cache invalidation on content publish, format negotiation — is a critical component of Amplience Dynamic Media performance optimization.

Cloud-Native

A software architecture approach in which applications are designed to run in cloud environments from the ground up, using containerization, auto-scaling, and distributed infrastructure. The C in MACH. Cloud-native platforms in a composable commerce stack operate as managed SaaS services with no on-premise deployment dependencies — they scale automatically, receive updates continuously, and carry no infrastructure management overhead for the buyer.

Commerce Engine

The platform component in a composable commerce stack responsible for product catalog management, pricing, promotions, checkout, and order processing. In an Amplience implementation, the commerce engine — Salesforce Commerce Cloud, Shopify Plus, commercetools, SAP Commerce Cloud, or BigCommerce — operates independently of Amplience. Amplience delivers content; the commerce engine delivers product and transaction data; the storefront assembles both.

Component Library

A shared collection of reusable UI components — page sections, promotional modules, navigation elements, product tiles — that the storefront renders when it receives content from Amplience. In a headless Amplience implementation, the component library is typically built in Next.js or React, with each component mapped to a corresponding Amplience content type. A well-designed component library enables content teams to compose pages from existing components without requiring front-end development for each new layout.

Composable Commerce

An architectural approach to ecommerce that assembles best-of-breed, independently deployable platform components — commerce engine, CMS, search, personalisation — rather than relying on a single monolithic suite. Amplience is the content and media layer in a composable commerce stack.

Content Audit

A structured inventory and assessment of existing content in a CMS or DAM before migration, remediation, or content model redesign. In an Amplience context, a content audit maps existing content items to their content types, identifies schema inconsistencies, flags orphaned assets in Content Hub, and documents which content is actively used versus obsolete. The AmpliFabrik Amplience Audit includes a content audit as a standard deliverable.

Content Delivery API

Amplience's read API for delivering published content items to storefronts and other consuming applications. It returns content items as JSON via HTTP GET requests. The Content Delivery API is used by headless storefronts to query Amplience content at page render time or at build time for static site generation. API query design, response caching, and performance under catalog-scale load are primary implementation considerations.

Content Hub

Amplience's native digital asset management (DAM) module. Stores, organizes, and manages digital assets — product imagery, lifestyle photography, video, documents. Key capabilities include AI-assisted asset tagging, bulk ingestion workflows, metadata schema management, automated format transformation on ingest, and integration with Dynamic Media for delivery-time transformation. Content Hub is the operational foundation of Amplience for any brand managing high asset volumes.

Content Item

A structured JSON document in Amplience conforming to a defined content type schema. The fundamental unit of content in Amplience. Content items are authored in the Content module, versioned, and delivered via the Content Delivery API. Each content item is an instance of one content type. A homepage banner, a product feature block, and a campaign editorial story are each content items.

Content Link

An Amplience content type field that references another content item by ID rather than embedding its data directly. Content links enable content reuse across multiple pages and templates — a shared promotional banner, a global header configuration, or a reusable product feature block can be authored once and referenced wherever needed. Correct use of content links is a core schema design principle for avoiding content duplication in multi-brand environments.

Content Model

The complete schema architecture for an Amplience implementation: the full set of content types, their field definitions, validation rules, and inter-type relationships. Content model quality is the most consequential determinant of implementation success — it governs authoring efficiency, editorial flexibility, and API delivery performance. A poorly designed content model creates developer dependency for routine content tasks.

Content Operations

The operational discipline of planning, producing, publishing, and maintaining content at scale. In an Amplience context, content operations covers editorial workflow design, DAM governance, authoring efficiency, and campaign scheduling. Poor content operations is typically a symptom of a poorly architected Amplience implementation — when authors depend on developers for routine content tasks, the content operations function becomes a delivery bottleneck.

Content Type

A schema definition in Amplience that specifies the structure of a content item: field names, field types, validation rules, and relationships to other content types. Multiple content items can be created as instances of a single content type. Content type design is the foundational technical decision of any Amplience implementation — it determines what authors can do without developer involvement.

Content Type Extension

An Amplience schema feature that allows a content type to inherit the field structure of a parent content type and add additional fields on top. Extensions enable schema reuse without duplication: a base product content type can be extended into category-specific variants (electronics, fashion, beauty) that share common fields while adding category-specific ones. Correct use of extensions is a key schema design decision in catalog-scale implementations.

Core Web Vitals

Google's standardized metrics for measuring real-world user experience on web pages. The three primary metrics are Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS). Performance on Core Web Vitals affects Google search ranking. On Amplience-powered storefronts, LCP is the most commonly affected metric, driven primarily by Dynamic Media configuration.

D

DAM (Digital Asset Management)

A system for storing, organizing, and managing digital assets — images, video, documents — with metadata, search, and workflow capabilities. Amplience's DAM is Content Hub. DAM configuration — folder taxonomy, metadata schema, ingestion workflows, and automated tagging — determines operational efficiency for content teams managing high asset volumes. A poorly configured DAM creates the same authoring friction as a poorly designed content model.

Deployment

The process of releasing code, configuration, or content changes from a development or staging environment to a production environment. In an Amplience implementation, deployment covers both platform configuration (content type schemas, slot architecture, Dynamic Media transformation rules) and storefront code releases. Amplience's environment model — production, staging, preview — supports a structured deployment pipeline for configuration changes.

Dynamic Media

Amplience's image and video transformation and delivery service. Applies server-side transformations — resizing, format conversion (WebP, AVIF), cropping, color profile adjustment — at delivery time from a single master asset, without pre-generating variants. A single source asset can be delivered in any format at any resolution for any device or breakpoint. Correctly configured, Dynamic Media is the primary lever for Core Web Vitals performance on Amplience-powered storefronts.

Dynamic Slot

An Amplience slot whose content is determined at request time based on context — user segment, device type, locale, or query parameter — rather than being statically assigned. Dynamic slots enable personalization and A/B testing within the Amplience publishing architecture. Implementation requires integration with a personalization or experimentation platform that passes context to the Amplience content delivery layer at the point of content query.

E

Edition

An Amplience publishing construct that groups content changes across multiple slots into a single scheduled publish event. An edition can be built, previewed, and scheduled in advance while live content continues to operate beneath it. Editions are the mechanism that enables multi-slot campaign launches — a homepage takeover, a seasonal promotion — to go live simultaneously at a precise time, with full preview capability before they do.

Environment (Amplience)

A logical separation within an Amplience hub that isolates content configurations for different stages of the development and publishing lifecycle. Amplience environments typically include production (live content), staging (pre-release content and schema changes), and preview (visualization of scheduled content). Environment strategy — what is promoted between environments and when — is a primary architectural decision established during implementation and maintained through managed services.

F

Front-End Integration

The implementation work that connects a headless storefront to Amplience's Content Delivery API and Dynamic Media delivery layer. Front-end integration covers API query design, component-to-content-type mapping, Dynamic Media transformation consumption, Visualization SDK implementation for real-time preview, and caching strategy at the component level. It is the layer where content model quality directly determines storefront rendering performance and authoring efficiency.

G

Go-Live

The point at which a new or updated Amplience implementation is switched to receive live traffic. Go-live for an Amplience project requires validation of content model completeness, Dynamic Media configuration and performance, slot and edition scheduling, API response accuracy under load, Visualization SDK preview fidelity, and integration smoke testing across all connected platforms. AmpliFabrik uses a 24-point go-live checklist as a standard delivery gate.

H

Headless CMS

A content management system that separates the content authoring and storage layer from the content presentation layer. Content is delivered via API to any consuming channel — web, mobile, digital signage — rather than rendered by the CMS itself. Amplience is a headless CMS purpose-built for ecommerce. The alternative is a coupled or monolithic CMS where the CMS controls both content management and rendering.

Headless Storefront

A commerce storefront built using a decoupled front-end framework — typically Next.js or React — that consumes content and product data from APIs rather than being rendered by a monolithic platform. In an Amplience headless storefront, the front end queries the Amplience Content Delivery API for editorial content, a commerce engine API for product data, and a search API for catalog navigation, assembling the full page at request time or build time.

HLS (HTTP Live Streaming)

An adaptive bitrate video streaming protocol that delivers video in small file segments, adjusting quality dynamically based on the viewer's available bandwidth. Amplience Dynamic Media supports HLS delivery for video assets, enabling smooth adaptive streaming for product videos and editorial content on commerce storefronts without requiring a separate video delivery platform or manual transcoding workflow.

Hub

In Amplience, a hub is a top-level organizational unit that contains environments, content types, and content. Multi-brand retailers typically operate one hub per brand, storefront, or region. Hub architecture — what is shared across hubs versus isolated per hub, and how hubs relate to each other — is a primary content model decision in multi-brand Amplience implementations and the most common source of technical debt when designed without forethought.

I

Image Transformation

The process of converting a source image asset into a delivery-optimized variant — resizing, cropping, format conversion, color profile adjustment — for a specific rendering context. In Amplience, image transformation is handled at delivery time by Dynamic Media using transformation parameters appended to the asset URL. This eliminates the need to pre-generate and store image variants for each breakpoint, device, or format — a single master asset covers all delivery contexts.

ISR (Incremental Static Regeneration)

A Next.js rendering strategy that generates static pages at build time but allows individual pages to be regenerated in the background after a defined revalidation period, without a full site rebuild. ISR is a common rendering pattern for Amplience-powered storefronts: pages are served statically for performance, but Amplience content changes are reflected within the configured revalidation window rather than requiring a full deployment cycle.

J

JSON (JavaScript Object Notation)

A lightweight, human-readable data interchange format that represents structured data as key-value pairs and arrays. Amplience content items are stored and delivered as JSON documents conforming to their content type schema. The Amplience Content Delivery API returns JSON responses that the storefront's rendering layer parses and maps to UI components. Every field in a content type schema corresponds to a key in the delivered JSON object.

K

KPI (Key Performance Indicator)

A measurable metric used to evaluate progress toward a defined business or operational objective. In an Amplience implementation context, relevant KPIs typically include content publishing velocity (time from brief to live), developer dependency rate (percentage of content changes requiring engineering involvement), Core Web Vitals scores, and campaign time-to-market. Establishing baseline KPIs before implementation begins allows the impact of remediation work to be quantified against concrete pre-implementation data.

L

LCP (Largest Contentful Paint)

A Core Web Vitals metric that measures the time taken for the largest visible content element — typically a hero image or large text block — to render in the browser viewport. LCP is the primary page performance metric for commerce storefronts and directly influences Google search ranking. On Amplience-powered storefronts, LCP is most commonly affected by Dynamic Media configuration: incorrect format delivery, missing CDN caching, or unoptimized transformation parameters are the leading causes of poor LCP scores.

Localization

The process of adapting content for a specific market — translating copy, adjusting imagery, applying regulatory-compliant product descriptions, and configuring locale-appropriate editorial workflows. In Amplience, localization is supported through multi-locale content model architecture: shared content type structures with locale-specific field variants enable parallel localization without content duplication. Amplience AI features include translation assistance that can accelerate high-volume localization workflows.

M

MACH

An acronym for the four principles of composable commerce architecture: Microservices, API-first, Cloud-native, and Headless. Coined and promoted by the MACH Alliance. Amplience is a MACH-aligned platform. MACH architecture enables brands to select best-of-breed platform components and replace individual components without rebuilding the entire stack.

MACH Alliance

An industry organization that promotes open, best-of-breed technology ecosystems built on Microservices, API-first, Cloud-native, and Headless principles. The MACH Alliance certifies platforms and vendors that meet its architectural standards and publishes annual research on composable commerce adoption and ROI. Amplience is a MACH Alliance member.

Managed Retainer

An ongoing support and services agreement in which AmpliFabrik provides continuous Amplience platform expertise to a client on a monthly basis. A managed retainer covers content model evolution, Dynamic Media tuning, schema updates, integration maintenance, platform upgrade management, and SLA-backed support.

Microservices

An architectural pattern in which an application is built as a collection of small, independently deployable services, each responsible for a specific business function and communicating via APIs. The M in MACH. In a composable commerce stack, each platform component — CMS, commerce engine, search, DAM — is an independent service that can be updated, replaced, or scaled without affecting the others.

Monolithic CMS

A content management system in which the content authoring, storage, and presentation layers are tightly coupled within a single application. In a monolithic CMS, changing front-end presentation requires changes to the CMS itself, and the CMS controls how content is rendered. Adobe Experience Manager, Sitecore, and legacy Episerver are common examples. Amplience is not monolithic — it manages content and media independently of how or where they are rendered.

Multi-Hub Architecture

An Amplience configuration in which multiple hubs are operated from a single Amplience account — typically one per brand, storefront, or region. Multi-hub architecture enables brand-level isolation while supporting cross-brand content sharing where appropriate. It is the primary implementation pattern for multi-brand retailers on Amplience and the most complex implementation scenario AmpliFabrik regularly handles.

Multi-Locale

An Amplience content model pattern that supports content delivery in multiple languages or for multiple regional markets from a single content architecture. Multi-locale content models use shared content type structures with locale-specific field variants, enabling parallel localization without content duplication across separate CMS instances. Correct multi-locale architecture is a prerequisite for high-volume localization workflows in health and beauty and fashion retail.

O

OMS (Order Management System)

A platform component responsible for managing the post-purchase order lifecycle — order capture, fulfillment routing, inventory allocation, returns processing, and customer communication. An OMS operates independently of Amplience in a composable commerce stack. It is relevant to Amplience implementations primarily in the context of integration architecture: ensuring post-purchase content experiences — order confirmation pages, returns portals — connect correctly to OMS data without content dependencies that would create deployment coupling.

P

Partial Content Type

A reusable schema fragment in Amplience that can be embedded within multiple content types. Partials enable shared field structures — a standard media reference, a CTA block, a shared metadata block — to be defined once and referenced across content types rather than duplicated per type. Correct use of partial content types is a core schema design principle for maintaining schema consistency and reducing duplication debt in complex implementations.

PIM (Product Information Management)

A system for managing structured product data — specifications, attributes, pricing, and relationships — across channels. Amplience is not a PIM replacement. It is the editorial and media delivery layer that sits alongside a PIM (Akeneo, inRiver, Salsify), delivering marketing and editorial content that contextualizes PIM-sourced product data on the storefront. AmpliFabrik has integration experience connecting Amplience to all major PIM platforms.

Preview (Amplience)

The capability to view how Amplience content will appear on the live storefront before it is published. Amplience supports preview through the Visualization SDK — which renders content within the authoring interface — and through direct preview links that allow stakeholders to review scheduled edition content in context. Preview reduces the publish-check-revert cycle that slows content operations and increases the risk of errors reaching live storefronts.

Publishing Queue

The ordered sequence of scheduled content changes — editions, slot updates, content item publishes — that are queued for release in Amplience. A well-managed publishing queue prevents conflicts between concurrent campaigns, ensures seasonal content deploys at the correct time, and provides a clear audit trail of what changed and when. Publishing queue management is a core content operations responsibility in multi-brand Amplience environments managing simultaneous campaigns across multiple hubs.

R

Rendering

The process by which a headless storefront converts API responses — JSON content from Amplience, product data from a commerce engine, search results — into HTML that the browser displays. Rendering can occur at request time (SSR), at build time (SSG), or through a hybrid approach (ISR). The rendering strategy chosen for an Amplience-powered storefront directly affects content freshness, page load performance, and infrastructure cost.

REST API

A widely adopted architectural style for web APIs that uses standard HTTP methods (GET, POST, PUT, DELETE) and stateless request-response patterns. The Amplience Content Delivery API follows REST conventions, returning content items as JSON via HTTP GET requests. REST APIs are consumed by storefronts, third-party integrations, and automation tooling throughout the Amplience ecosystem. Understanding REST API query patterns is a prerequisite for Amplience front-end integration work.

Rollback

The process of reverting a system — content configuration, schema change, or storefront deployment — to a previous known-good state. In Amplience, rollback capability applies to content model changes (reverting schema updates), published content (replacing live content items with prior versions), and edition scheduling (canceling a queued publish event before it fires). Rollback planning is a required component of any Amplience go-live checklist and managed services SLA.

S

Schema

In Amplience, a schema is the JSON Schema definition that specifies the structure of a content type: fields, types, validation rules, and relationships. Each content type is backed by a schema document. Schema design is the foundational technical decision of any Amplience implementation — it determines what authors can do without developer involvement, how content is delivered via API, and how maintainable the implementation will be over time.

SKU (Stock Keeping Unit)

A unique identifier assigned to a specific product variant — a combination of product, size, color, and any other variant attribute that creates a distinct purchasable item. SKU count is a primary driver of implementation complexity in electronics and health and beauty Amplience projects: high SKU volumes with rich content requirements (specification tables, variant imagery, regulatory descriptions) require content models designed explicitly for scale, not adapted from simpler catalog structures.

Slot

A placeholder on a page or template in Amplience that holds a content item and supports scheduled publication via editions. Slots define where content appears on a page; the content item assigned to a slot defines what appears. Slot architecture — how many slots a page has, how they are named, and how they relate to page types — is a primary content model decision that directly affects editorial workflow efficiency and campaign publishing capability.

SSG (Static Site Generation)

A rendering strategy in which all pages are generated as static HTML files at build time, before any user requests are made. SSG produces the fastest possible page delivery since no server-side processing occurs at request time. For Amplience-powered storefronts, SSG is appropriate for content that changes infrequently. It requires a webhook trigger mechanism to regenerate static pages when Amplience content is published to production.

SSR (Server-Side Rendering)

A rendering strategy in which pages are generated on the server at request time, pulling live data from APIs — including the Amplience Content Delivery API — for each incoming request. SSR ensures content is always current but adds server processing latency compared to SSG. It is appropriate for pages where content changes frequently or where personalization requires request-time context. Most production Amplience storefronts use a hybrid approach combining SSR, SSG, and ISR.

Staff Augmentation

An engagement model in which specialist practitioners join a client's existing team on a time-and-materials basis rather than delivering a fixed-scope project. AmpliFabrik provides Amplience staff augmentation for teams that need to embed platform expertise into their existing delivery structure. Available roles include Amplience engineers, solutions architects, content architects, business analysts, and delivery managers.

Storefront

The customer-facing web application that presents commerce content and product information to end users. In a composable commerce architecture, the storefront is a headless front-end application — typically built in Next.js or React — that assembles content from Amplience, product data from a commerce engine, and search results from a search platform into a unified customer experience. The storefront is the primary consumer of Amplience's Content Delivery API and Dynamic Media delivery layer.

T

Technical Debt

The accumulated cost of implementation shortcuts, architectural compromises, and deferred design decisions that make a system harder to maintain, extend, or optimize over time. In Amplience implementations, technical debt most commonly manifests as schema duplication across brands, misconfigured Dynamic Media that underperforms, and platform features that were never activated. The AmpliFabrik Amplience Audit exists specifically to quantify and prioritize technical debt remediation before it compounds further.

Time-to-Market

The elapsed time between initiating a content, product, or campaign workflow and making it live to customers. In an Amplience context, time-to-market is directly influenced by content model architecture. When schemas are designed for author efficiency, content can be produced without developer involvement. Poor content model design creates developer dependency that extends time-to-market from hours to weeks for routine content tasks.

U

UGC (User-Generated Content)

Content created by customers or end users rather than by the brand's internal teams — product reviews, customer photography, social media posts, and community contributions. UGC integration in Amplience involves schema patterns that reference externally sourced content alongside brand-authored content, with content type fields for UGC asset links, moderation status, and source attribution. Health and beauty brands with high UGC volumes commonly integrate UGC sources into their Content Hub asset pipelines.

V

Visualization SDK

Amplience's development toolkit for implementing real-time content preview within the Amplience authoring interface. The Visualization SDK connects the Amplience authoring UI to the storefront's rendering environment via a configurable iframe, providing authors with live preview of content items as they will appear on the published storefront. Correctly implemented, it removes the publish-check-revert cycle from content authoring — a significant editorial efficiency gain for high-velocity content teams.

W

WebP

A modern image format developed by Google offering better compression than JPEG at equivalent visual quality. Supported in Amplience Dynamic Media as a delivery-time transformation target. Delivering WebP instead of JPEG for supporting browsers is a standard Dynamic Media optimization that reduces image payload size and improves LCP. AVIF offers better compression still and should be evaluated as an alternative where browser support allows.

Webhook

An HTTP callback mechanism that sends an automated notification from one system to another when a defined event occurs. In Amplience implementations, webhooks trigger downstream actions when content is published — regenerating static pages in a Next.js storefront, invalidating CDN cache entries, updating search indexes, or notifying commerce platform product pages of content changes. Correct webhook configuration is a required component of any Amplience go-live checklist.

Workforce Flows

Amplience's AI workflow automation feature that chains content generation, review, translation, and publishing steps into automated sequences. Enables content teams to automate high-volume, repetitive content production tasks — bulk description generation, alt-text creation, locale variant production — without manual intervention at each step. Available to most licensed Amplience customers and unused by the majority. Activation requires workflow integration, not just a settings toggle.