Products
Names, groups, images, attributes, and variants.
Catalogs and digital sales
A catalog or storefront built around your company data
Show products, prices, and availability in a clear path from selection to a request or order. Start with a file; assess a system connection separately.
- For whom
- Sales teams, manufacturers, and distributors with product ranges that require explanation or selection.
- Business outcome
- Buyers choose independently, while sales receives the products, parameters, and contact in one request.
Buyer journeyDemonstration data
TaskFind equipment that matches a project
- 01Find
- 02Compare
- 03Request
productspricesstockattributes
When a catalog is not enough
The products exist. Choosing is still hard.
When the catalog and website are updated separately, customers see stale prices or stock and managers rebuild the same request by hand.
A buyer should find the right product, understand the terms, and send a structured request without searching spreadsheets or starting a conversation from scratch.
What to prepare
Build the path from product to action
Start with a spreadsheet or file. For a new system, assess its API, access rights, refresh frequency, and data scope first.
Prices and stock
Prices, availability, and supply terms from an agreed source.
Sales rules
Selection, quote request, cart or order, and required fields.
How the work runs
From assortment to a path you can verify
See which data is connected, what buyers can do, and where a separate setup is required.
- 01
Prepare the assortment
Provide a file or choose an available connection.
- 02
Assemble the storefront
Review categories, filters, cards, and product fields in the browser.
- 03
Add the next action
Choose a quote request, selector, cart, or another confirmed step.
- 04
Check the exchange
Agree on fields and refresh frequency before publishing.
What the result looks like
Review the complete buyer journey on one working screen
Review catalog sections, product cards, filters, and the request form inside the project. A separate example shows how approved fields move from a source system to the website and into the sales request.
Catalog and request screencatalog · product card · request
A clearer choice
Filters, attributes, and alternatives help buyers find the right item.
A structured request
The manager receives selected products and parameters instead of a blank chat.
One source of truth
The main system stays authoritative while approved fields appear on the site.
Delivery boundaries
Know what is ready and what needs setup before launch
Fluw assembles pages, forms, and ordinary changes. A new system connection, payments, and critical logic need a separate review.
Built in Fluw
Pages, cards, filters, forms, and content changes.
After verification
A confirmed source connection, approved fields, and request delivery.
Separate assessment
A new integration, payments, or rules outside a verified connection.
Questions before you start
What to check before publishing
Will I get a mockup or a working storefront?
The result opens in the browser: you can review pages, cards, and forms. Publishing and external data exchange need their own checks.
Can you connect our ERP or CRM?
Only a verified connection is treated as ready. Any other system starts with an API, access, limits, and an agreed field scope.
Do we have to retype the catalog?
You can start with a file. If a system is supported, its fields and refresh frequency are checked before launch.
What happens when the source data changes?
The site receives approved updates according to the rules of that connection. Instant sync is not promised without a verified setup.
Start