Corporate website and dealer channel

• The catalogue from a single sourceProducts, documents and prices are fed from the system; nothing is copied by hand.
• A dealer sees their own priceThe same page, with prices and a request flow by the dealer's tier.
• A request turns into a saleThe basket becomes a quote request; the order's status is visible to the dealer.

The site is the ERP's outward face

The product data, documents and contact forms on the site are fed from the system's own records. Products are presented in a family → series → model hierarchy, and technical specifications come from measurable fields; that is why comparison tables and filters really work.

Specifications shared across a series are gathered in a separate table. For a specification to count as shared in a series it must either be present in every member, or in at least two and at least half of them; those below that are not listed, and a badge says how many members it covers. Saying in how many models something is available, instead of "available on some models", changes the reader's decision.

Quote basket

Visitors put the products they are interested in into a basket; the basket is not a shopping cart but a quote list. It sits in the header as a badge, opens a drawer from the side when clicked, the full list is shown on a separate page, and from there the contact form opens in one click, already filled in. The drawer is deliberately a review step: it holds no form and no send button.

Dealer channel

The basic design decision: no separate site was built for dealers. A dealer sees the page everyone sees; the only difference is that prices are visible and they can open an order. Two catalogues drift apart sooner or later and raise the question of which one is right.

The price comes from a pricelist rule tied to the dealer's tier. Products without a price are not shown as 0.00 — they read "to be priced" and can still be added to a request. Showing zero would give the impression of "free".

Basket → Request → Review → Quotation → Signature → Order → Delivery → Invoice → Payment

A dealer's basket is directly a request: lines and line notes, the dealer's own reference, the requested date, the end customer, payment term and payment method preference. In every state the request page shows the sentence "what comes next"; from there the dealer can ask for a change or a cancellation — these are messages, not actions; sales makes the decision.

An approved request turns into a quotation; the dealer can confirm the order by signing the quotation in the portal. The correspondence of the request and of the order it became merges into a single timeline; internal notes do not enter this stream.

Site accounts

Visitors can open an account. Three things are set up deliberately: verification (an account is not fully enabled until its address is verified), proof of consent (what the person consented to, and when, is recorded) and a sign-up rate limit.