Friday, 4:58 p.m. A new price list is due on Monday. It has been loaded into the ERP, the dealer PDF is in the download area, two product images are missing and one sales partner still has an old basket open. This is the moment when a dealer portal reveals whether it is a dependable sales channel or merely a website with a login
Price is an outcome
Dealer sales rarely have one price per product. Customer group, country, currency, quantity, contract, promotion period and tax context can all change the same item. The portal should therefore obtain the price from traceable rules and record when it was calculated. A copied value with no provenance becomes a problem as soon as a price is disputed
Open baskets need an explicit rule. Does the old price remain valid for a period, is everything recalculated, or must the dealer confirm the change? Any of the three can be correct. What is not correct is behaviour that depends accidentally on caching or synchronisation time
Availability needs a language
“In stock” appears clear but may mean central warehouse, regional warehouse, reserved stock or a nightly import that is already stale. Dealers usually need a dependable delivery statement: available now, expected from a date, available on request or unavailable to order. When stock is low, a range may be more honest than an exact number that changes during checkout
Reservation must be atomic. Two dealers cannot both receive confirmation for the final unit. Technically, the stock display and order acceptance are separate. The display informs; acceptance decides
Product data is not a media folder
A dealer needs images, dimensions, safety information, spare parts, translations and sometimes regulatory documents. Those records have versions, markets and periods of validity. A product information system may be the source of truth, but the portal still has to communicate changes clearly
A useful change feed answers three questions: what changed, when does it apply and does the dealer need to act? “Data updated” is insufficient if a specification sheet must be replaced or a quotation corrected
Ordering on a poor connection
Field sales and workshops do not always have stable connectivity. Mobile views should load sparingly, preserve unfinished baskets locally or on the server, and resume an interrupted upload. An order marked “sent” must never exist only on the device
Full offline operation is expensive and not always necessary. Often it is enough to handle interruptions well: show the synchronisation state, retry without duplication and issue a final order number only after the server accepts the transaction
The first release in six decisions
- Which system owns product, price, stock and order data?
- At what point is a price fixed?
- Which availability statement may be presented as binding?
- Who may order, approve and manage users for a dealer?
- How are product data changes announced?
- What does a dealer see when ERP or logistics is temporarily unavailable?
Those decisions define the first architecture. Search filters, favourites and dashboards come later. They are useful, but cannot repair unclear pricing rules
Dealer portal or partner portal
If ordering, range and availability are central, a dealer portal is the right domain model. Joint leads, certifications and campaigns belong more naturally in a partner portal. Both can run on one B2B platform, but should not share the same roles and state language indiscriminately
A professional dealer portal does not prove itself on a quiet Tuesday morning. It proves itself during a price change, a stock shortage and a broken connection, when every display can amount to a commercial promise