Engineers enter operating conditions
They specify requirements, units and constraints instead of guessing a product code.
For equipment manufacturers and distributors
Guide buyers from operating requirements to a quote request
Help engineers, procurement teams and dealers select a model and send sales a specific request. Your company decides which data is shown and how each enquiry is handled.
The buyer journey
Turn requirements into a useful quote request
The buyer enters flow, head, working medium and material. The catalogue presents suitable models, approved alternatives and components, then keeps the selected items with the request.
Matches the requirements
Vertical pump
Demonstration model
Show 2 approved alternativesProcurement compares options
They see model differences, compatible items and alternatives approved by the company.
Sales receives the requirements
Selected items and specifications arrive with the enquiry, not a vague “need a pump” message.
What your company prepares
Define the data and selection rules first
You do not have to connect the accounting system for the first version. Start with a prepared file, verify the catalogue structure, and assess live data exchange separately.
Product range
SKUs, models, variants, images and product documents.
Selection criteria
Specifications, units, mandatory constraints and compatibility rules.
Commercial data
Only prices, stock, lead times and statuses that buyers are allowed to see.
Enquiry handling
Contact fields, request destination and the next step after submission.
What buyers see
Company data becomes familiar catalogue screens
Each screen answers a concrete buyer question: what fits, how options differ and how to request a proposal.
- Specifications and rules
- Filters based on operating requirements
- Models and variants
- Cards with differences and documents
- Alternatives and components
- Comparison and compatible items
- Enquiry fields
- A quote request with the selected items
Connecting data
What the page can show and what needs a separate check
Fluw does not replace your CRM or accounting system. Before launch, define the main business system, allowed fields and how the catalogue behaves when its data is unavailable.
Build and verify
Sections, filters, product cards, comparison, documents and the enquiry form — using agreed test data.
Agree before connecting
Source access, allowed fields, refresh frequency, request destination and a fallback scenario.
Assess separately
A new connector, complex engineering calculations, payments and logic with special access permissions.
Before you start
Questions to answer before building the catalogue
Can we start with a spreadsheet?
Yes. Product fields, specifications and matching rules are enough for the first review. A system connection can be assessed after the screens are verified.
Will prices and stock be current?
Only when the source, allowed fields and refresh frequency have been agreed. Until then, the page must clearly label test data.
What if selection requires engineering calculations?
Separate ordinary filters from calculation logic first. Formulas, tolerances and responsibility for engineering results need their own assessment.
Do we have to add payments?
No. Selection and quote requests are often enough for a B2B catalogue. Payments are added only for a confirmed flow and require a separate check.
Where does the buyer enquiry go?
Your company defines the recipient and request contents before launch. CRM or request-system delivery depends on an available API and agreed connection scope.
Start with the task
Describe how buyers select your equipment
List the products, key selection criteria and what sales should receive. The task remains in the project after registration.