Modular kitchens and home
TERMINO
TERMINO is a project-led modular-kitchen case: Framer carries premium brand and spatial storytelling, Shopify Storefront API supplies commerce data, and configurator, showroom and B2B enquiry drive conversion.
Visit the live project
Core implementation review
Three storefront journeys from model choice to purchase
TERMINO does not sell a finished kitchen as an impulse product. It sells a composable aluminium system. WESWOO kept spatial storytelling, module literacy and project contact in a Framer frontend, and used the Shopify Storefront API as the source for module records, price and availability—so a layout can be explained first and only then resolved to commerce.
Project context
Define how customers choose before defining the storefront
Customers first understand the system, explore single-drawer, open, sink, induction and oven modules plus island or wall systems, then assemble through the 3D configurator before estimate, showroom or project enquiry.
Framer headless frontend development; Shopify Storefront API integration; modular content components; configuration, enquiry, showroom and B2B entry points; responsive implementation.
Framer holds the rooms; Storefront API holds the modules
The brand surface is taken out of a Shopify theme so spatial storytelling and commerce data can change on different clocks.
- 01Enter the brand and spatial narrative
- 02Compose systems and modules in Framer
- 03Query module, price and availability data
- 04Keep enquiry, showroom and checkout as separate exits
Implementation
- Framer owns composition, motion and reusable content; Shopify supplies product and commerce data through the Storefront API.
- The public site loads a Framer bundle. UI state lives in frontend components, not Liquid sections or theme Ajax assets.
- The API contract covers module records, variant mapping, inventory and price. Enquiry, showroom booking and any standard checkout stay on distinct paths.
Deployment and acceptance
- Caching, empty states and failures are handled in Framer components, so module copy and contact remain readable if a commerce query fails.
- If a standard sellable component later enters Shopify checkout, the brand pages do not have to be rewritten as a theme template.
- Kitchen photography, material close-ups and system copy are no longer constrained by product templates.
- Price and availability can follow the Shopify catalogue without rebuilding the spatial pages.
View script and Shopify API evidence
Shopify Storefront APIscript_main.BlrV35tL.mjsTreat drawers, sinks and islands as parts of one system
The catalogue is a set of queryable aluminium modules. Island and wall systems assemble those modules into a kitchen, rather than selling one finished SKU.
- 01Learn the system and materials
- 02Browse drawer, open, sink, hob and oven modules
- 03Assemble them in an island or wall system
- 04Resolve the layout to shared module records
- 05Choose a sellable component or a project enquiry
Implementation
- Single-drawer, open, sink, hob and oven modules are addressable entities; island and wall systems aggregate them.
- Dimensions, material, worktop compatibility and installation constraints are structured fields shared by the configuration summary and Storefront queries.
- Standard components and project enquiry remain two journeys over the same module records, so the catalogue is not copied twice.
Deployment and acceptance
- Project spaces and showrooms are maintained as separate content, not stuffed into module descriptions.
- The UI only presents modules inside the sellable range returned by Storefront, so impossible combinations never appear as buyable.
- Shoppers understand how a kitchen is composed before they choose an estimate or a standard component.
- A configuration can resolve to commerce data without operations maintaining two catalogues.
View script and Shopify API evidence
Shopify Storefront APIOnce a layout exists, the next step is a conversation
High-consideration kitchens usually need an estimate, a Berlin showroom visit or a B2B discussion—not an immediate add-to-cart.
- 01Assemble a layout in the 3D configurator
- 02Confirm dimensions and materials in the summary
- 03Choose estimate, showroom or B2B contact
Implementation
- The configuration session stays in Framer components. Selected state lives in the summary, not a full-screen highlight.
- Calls to action appear by stage—learn the system, assemble modules, request an estimate or book a showroom—so every viewport does not compete for checkout.
- Enquiry and booking are independent submissions. Popup contact sits beside the configuration instead of routing the project through a theme cart.
Deployment and acceptance
- A failed commerce query does not wipe the configuration; contact and showroom information remain available.
- Cutaways and dimension tables become scrollable layers on small screens, so 3D or long imagery cannot cover enquiry.
- Units, tax language and lead times in the enquiry copy match the modules actually returned as sellable.
- Buyers enter estimate or showroom conversations with a specific module combination, not a raw SKU list.
- Project contact stays reachable through the long page, without depending on an add-to-cart control.
View script and Shopify API evidence
Shopify Storefront APIloader.jsOperational handoff
The operating team can continue after launch
- Catalogue objects are composable aluminium modules: single-drawer, open, sink, hob and oven units, aggregated into island or wall systems.
- Dimensions, material, worktop compatibility and installation constraints are shared fields for configuration and Storefront queries.
- Project spaces and showrooms stay separate from module records, so photography is not dumped into product copy.
- The English site serves German and European project buyers. Millimetre dimensions, tax, freight, installation coverage and showroom access are maintained by region.
- Module and material records stay shared; service radius, project qualification and contacts change by market.
- Enquiry and B2B copy only offer modules the destination can fulfil.
Research notesPublic sources and verification boundary
Public research sources
Content verification
Industry, product and observable feature notes are verified against the brand site. Apps, admin configuration and commercial data that cannot be confirmed from the storefront are not inferred. WESWOO scope is stated only from project records and client authorization.
Public information last reviewed: 2026-08-20
Related service: Shopify storefront design and frontend delivery