Keep your frontend experience. Add ii3d configuration.
For custom storefronts, CMSs and complex frontends, choose clearly between app, component embed or API-driven patterns, then define lifecycle, data contracts and security boundaries together.
- Web Component
- API design
- Frontend architecture
Existing frontend or CMS
Page structure, user session and content
ii3d configuration runtime
Product loading, interaction and outcome
Business services & events
Price, order, save and notification
See the business breaks clearly first.
Not another system layer — a way to connect configuration, operations and delivery in the workflow you already run.
The frontend experience cannot be compromised
The brand site already has a design system, performance strategy and content orchestration that should not be rebuilt for one capability.
Integration boundaries are unclear
Teams do not know who loads products, saves configurations, calculates price or handles order events.
Credentials and domains lack governance
Cross-origin, identity, environment and credential use are not designed early, causing late rework.
How the route moves from input to business outcome.
Agree responsibilities and information boundaries at each stage before choosing the technical connection.
Get an integration assessment- 01
Existing frontend or CMS
Page structure, user session and content
- 02
ii3d configuration runtime
Product loading, interaction and outcome
- 03
Business services & events
Price, order, save and notification
Design the key connection points for handoff.
These are the capabilities to confirm during assessment and delivery; they do not replace technical validation in the project.
Choose the right integration model
Compare app, component and API approaches by page control, engineering resources and business complexity.
Define the page lifecycle
Clarify key events: initialization, product load, user configuration, saving and continuing to purchase.
Agree the data contract
Confirm input parameters, output summary, error states and version policy against the project data model.
Set security boundaries
Plan responsibilities for domains, environments, identity and server-side credentials without exposing sensitive information to the browser.
Use concrete scenarios to decide what to connect first.
These are typical delivery scenarios that use no client names or sensitive data, helping define an initial scope.
Configuration modules in custom storefronts
Add configuration capability within the existing page framework, design system and user session.
CMS-driven product content
Let content teams retain product-page composition while technical teams govern required data connections.
Channel-facing business apps
Design controlled creation and handoff of proposals for dealer, sales or designer tools.
Use four steps for a controlled integration.
Use source material, samples and a test environment to reduce rework and align business and technical teams.
- Step 01
Assess the stack and page goal
Understand frontend framework, CMS, session state, performance needs and business actions to be handled.
- Step 02
Select the model and contract
Set embed scope, event boundaries, input/output and error-handling approach.
- Step 03
Integrate in an isolated environment
Use test products, test users and simulated business services to validate key interactions.
- Step 04
Run performance and release checks
Confirm loading, fallback, monitoring and release approach before production.
Common questions
Before a project begins, clarify scope, ownership and the materials to prepare.
Must we use a specific frontend framework?
The approach should not be promised by framework name alone. Assessment starts with the existing page, integration model and data boundaries.
Do API keys need to be exposed?
Sensitive credentials should be managed by server-side or controlled identity flows. Browser access should follow a project-approved least-privilege approach.
How are API upgrades handled?
Before launch, define versioning, compatibility, change notification and rollback so upgrades do not become unexpected frontend failures.
Where do we get API documentation?
Once publishable API scope, authentication and examples are available, controlled developer materials can be provided; this page first clarifies the needed capabilities.
Bring your current stack and target flow. We’ll map the connection path together.
Share your current platform, business flow and constraints for an integration assessment tailored to the project.
Get an integration assessment