Our other projects
The brief was to help customers choose a compatible gear setup from many product options, sizes, performance profiles, and commerce links.
The experience needed to run inside Webflow while relying on data and recommendation logic that could evolve outside the page.
The product catalog was too complex for a simple static product grid. Riders needed recommendations based on discipline, level, weight, riding priority, and product compatibility.
The business also needed Webflow CMS content and commerce data to stay aligned with the recommendation output.
The implementation had to fit a Webflow page, return complete product cards, preserve checkout reliability, and avoid putting private API credentials or brittle business logic in browser JavaScript.
SoFlow implemented a Cloudflare Worker API and Webflow embed assets for a setup configurator. The endpoint returns recommended foil, tail, mast, board, alternative options, performance scores, package context, explanations, and commerce-ready fields.
The Webflow page loads hosted configurator assets. The frontend sends rider inputs to the Worker, which reads product/CMS-shaped data, applies scoring and compatibility rules, and returns a structured recommendation for the Webflow UI to render.
- Rider input based recommendation endpoint
- Foil, tail, mast, board, and alternative product output
- Priority-based scoring for freeride, surf, downwind, lightwind, speed, and pump
- Webflow-hosted embed script and styles
- Commerce fields such as SKU, price, checkout URL, and product URL support
The configurator turns a complex commerce catalog into a guided decision flow that can improve confidence before checkout or consultation.
- Supports multiple riding disciplines and rider profiles
- Returns a complete setup instead of a single product
- Keeps recommendation logic outside browser-only custom code
- Uses hosted assets for Webflow integration
Can this pattern work outside sports products?
Yes. The same pattern can support any product or service where buyers need a guided recommendation based on inputs, constraints, compatibility, or preference scoring.
Why use a Worker instead of only Webflow CMS filters?
A Worker can score combinations, normalize CMS and commerce data, return a stable API contract, and keep sensitive logic outside the browser.
Does the configurator replace the shop checkout?
No. The configurator helps users choose a setup. Checkout can remain owned by the commerce platform so payment and order flows stay reliable.
This implementation proves that SoFlow can build custom recommendation engines for Webflow commerce experiences where the buying decision depends on product data, compatibility, and business-specific scoring.
Can this pattern work outside sports products?
Yes. The same pattern can support any product or service where buyers need a guided recommendation based on inputs, constraints, compatibility, or preference scoring.
Why use a Worker instead of only Webflow CMS filters?
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
Heading 1
Heading 2
Heading 3
Heading 4
Heading 5
Heading 6
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
Block quote
Ordered list
- Item 1
- Item 2
- Item 3
Unordered list
- Item A
- Item B
- Item C
Bold text
Emphasis
Superscript
Subscript
Before the implementation, visitors had to understand a complex product catalog and compatibility choices with less guided help.
After the implementation, the Webflow page could guide users toward a complete setup and present the result with product context, reasoning, and commerce links.
A normal Webflow CMS collection can display products, but it cannot safely score combinations, relax filters when data is incomplete, build a complete setup recommendation, and connect the result to commerce fields.
That logic belongs in a backend service that can normalize product data and return a clean frontend contract.
