Service · Web development

Custom dealer portal development for manufacturers and wholesalers.

A secure environment for your dealers, resellers and distributors to place orders, view stock, get pricing tiers, submit claims and download marketing content. Custom built, integrated with your ERP, PIM and CRM, and in your own brand look and feel.

Orders & stockPricing tiersClaims & warrantyDAM & MDFERP integration

A dealer portal is your distribution channel in software.

A dealer portal, sometimes called a reseller portal, distributor portal or partner portal, is the central platform on which your indirect sales channel runs. The dealers, resellers, importers and distributors who take your products to the end customer do their daily work there: they place orders, check stock and delivery times, request discounts, submit claims, download marketing material and keep their certifications up to date. When that work runs over email, Excel and the phone, it costs your channel managers, sales support team and finance department a disproportionate amount of time, and it gives dealers an experience that they usually compare, without saying so, with that of your competitors.

A well-built dealer portal removes that workload by being the single source of truth for your channel. Dealers see their own pricing tier, their available stock in your warehouses, their open orders and their current warranty claims in real time. Your internal team, on the other hand, sees each dealer's revenue, MDF balance, training status and compliance position, and can steer on that data rather than on gut feeling. What separates a dealer portal that falls into disuse after a few months from one that sticks is rarely the technology; it lies in how well the portal fits the work your dealers already do, the language their product managers and salespeople use, and the moments at which they get in touch.

We have been building dealer, vendor and partner portals for manufacturers, wholesalers and importers since 2015. This type of platform is closely related to a B2B e-commerce portal, but it stands out for its focus on channel management: pricing tiers per dealer contract, MDF budgets, distribution of your end-customer leads to your dealers, and controlled access to brand assets. For the reverse direction, with suppliers who deliver to you, see our page on a vendor portal. For a marketplace model in which multiple sellers sit side by side, we take a separate approach, described under building a marketplace platform.

Three flavours of dealer portal.

Which type of platform suits you depends on the size of your channel, the complexity of your pricing structure, and how deeply the portal needs to connect to your existing ERP, PIM and CRM. In the first conversation, we advise which variant makes sense for your situation.

Compact project · fixed sprint budget

Reseller portal for an SME manufacturer

A secure environment in which your dealers can see their open orders, easily place repeat orders, check stock in your central warehouse and download marketing files. SSO, role-based access and a simple pricing tier per dealer. Suitable for manufacturers and wholesalers with a few dozen to a hundred active resellers.

SSOOrder flowStock APIDAM-light
Mid-sized project · fixed sprint budget

Dealer portal with claims, warranty and lead distribution

For manufacturers where after-sales service plays a major role: claims management for warranty and defects, warranty registrations, distribution of consumer leads to the nearest dealer, and marketing content at contract level. Including integrations with order management and your CRM.

Claim workflowWarranty registerLead routingCRM sync
Larger project · fixed sprint budget

Enterprise dealer platform with multi-region and MDF

A mission-critical platform that connects in real time to SAP, Microsoft Dynamics, AFAS or a proprietary ERP, with multi-region pricing, contract management, MDF budgets (marketing development funds), training tracking, certifications per product category and EDI integrations with large retail partners. Multi-tenant theming for different brands or business units.

SAP / DynamicsMDF balancesEDIMulti-tenant

What you get at the end.

A production-ready dealer portal plus everything around it to manage and extend it yourself as your channel grows.

  • The platform itself, in productionProduction and staging environments, running in your own cloud (GCP, AWS, Azure) or hosted by us. Includes a CDN for the DAM files so your dealers get fast downloads worldwide.
  • Full codebase and documentationSource code, build instructions, architecture overview and API documentation. You are not locked in to a vendor; another team can take it over.
  • ERP, PIM, CRM and DAM integrationsWorking integrations with your existing systems via smart API integrations or a message bus. Real-time stock, product data, pricing and orders.
  • Admin and dealer manualsShort manuals for your channel managers, sales support and finance team, plus a dealer-facing manual you can embed in onboarding emails.
  • Onboarding and train-the-trainer sessionsSessions for your channel team plus train-the-trainer sessions for your key dealers, so they can bring their own people on board in their own language.
  • Maintenance and further developmentOptional maintenance contract: monitoring, backups, security patches, keeping ERP integrations up to date and ongoing extensions with new modules. Fixed monthly price per tier.

When a dealer portal is the right choice.

Four patterns in which a dealer, reseller or distributor portal takes noticeable work off your hands, for your own team and for your channel partners. If you recognise one of them, a conversation is usually worth your while.

Orders and stock

Ordering goes through inkoop@

Your dealers email or phone sales support to check stock, request delivery dates or place a rush order. Your team handles that back-and-forth in a shared mailbox and then types the orders into your ERP by hand. Versions get lost, errors creep in, and nobody has an overview.

Pricing per dealer

Pricing tiers in Excel

Different dealers get different discounts based on volume, contract or certification level. Those pricing tiers live in spreadsheets that your sales team maintains by hand, and changes only reach the invoice with a delay. A dealer often only sees their own price after the fact.

After-sales service

Claims and warranty are ad hoc

Defects, warranty claims and RMAs run through separate forms, photos buried in emails and manual processing. Your service team loses days searching for the right parts, photos and dealer details, while the end customer waits for an answer.

Marketing & leads

Brand assets and leads are fragmented

Your dealers ask for product photos, datasheets and logos by email. Consumer leads that come in via your website are distributed by hand by your marketing team to the nearest dealer, with delays and no visibility of follow-up. MDF budgets are tracked in a spreadsheet.

How a dealer portal project works.

1

Introduction

A conversation in which we understand which flows need to run through the portal (orders, stock, claims, marketing content, leads, MDF, training, reporting), which ERP and CRM systems surround it, and what your dealer tier structure looks like. At the end you have a first sketch of the scope and an idea of where we start.

2

Discovery with your dealers

A workshop with your channel team plus short interviews with a cross-section of your dealers: a large A-dealer, a mid-tier partner and a smaller reseller. What do they do now, where do they run into problems, and what do they expect from your portal? At the end: scope, screen flow and a plan per module.

3

Building in sprints

A working build every two weeks. Your team tests along, and so does a small group of pilot dealers. We start with the most critical flow, usually ordering plus pricing tier, and extend in later sprints with claims, marketing, leads, MDF and reporting. That way you see value early and can adjust the scope every sprint.

4

Phased rollout and maintenance

We roll out in phases to your full dealer base, run onboarding sessions, and provide ongoing maintenance for security, ERP integrations and continued development of new modules. As your channel grows, the portal keeps evolving with it.

Modules we build almost every time.

A dealer portal is made up of a set of recognisable building blocks. Which ones you need depends on your situation and your industry, but the following modules appear in almost every project, sometimes as the core, sometimes as an extension in a second phase once the foundation is running.

Identity

Single sign-on and role management per dealer

SSO via Azure AD, Okta, Google Workspace or your own identity provider for your internal team. For dealers we work with an invitation flow plus multi-factor authentication, and SSO where a larger dealer offers it themselves. Multiple roles per dealer organisation: dealer admin, buyer, service technician, marketing manager. That way every user only sees what they need.

Orders and stock

Real-time stock and ordering

Dealers see available stock per location, planned incoming stock and their open orders in real time. Simple bulk ordering via SKU list, CSV upload or CSV template, with immediate validation against your ERP. Rush orders, partial deliveries and split shipments are supported. Status feedback (ordered, in production, shipped, delivered) per line number.

Pricing

Pricing tiers per contract

Pricing is driven by the contract the dealer has with you — volume tier, certification level, region or strategic status. For each item, the portal shows the correct net price, including volume discounts and temporary promotions where relevant. Changes in your ERP come through automatically, so sales doesn't have to make manual updates.

Claims & warranty

Claim management and warranty register

Dealers submit claims through a structured form — defect type, serial number, photos, customer details. The portal automatically routes the claim to your service team, links it to any open warranty record and tracks SLA timers. On request, end customers receive a unique warranty claim link, so the dealer doesn't have to be involved.

Marketing & DAM

Brand asset management for dealers

A secure DAM environment with logos, product photos, datasheets, videos and social media templates. For each asset, you control which dealers may use it and in which regions. Co-branding templates with automatic logo insertion and a pre-approval flow for dealers who want to create their own adverts.

MDF

Marketing development funds

Each dealer gets an MDF budget based on revenue or contract. Dealers request budget for a specific marketing activity, submit proof of execution (campaign report, invoice, photos) and have their claim processed once approved. Your channel team gets an overview of where the marketing euros are going and what ROI they deliver.

Leads

Lead distribution and end customer flow

Consumer or B2B leads that come in via your website or comparison site are assigned to the nearest or best-matching dealer through a dealer locator or strategic routing. The dealer sees the lead in their portal and accepts or declines it, and you see the follow-up result. This prevents leads from sitting in a mailbox or being picked up by several dealers at once.

Training

Training tracking and certifications

For industries where product knowledge is critical — automotive, agri, electronics — a training module with online courses, knowledge tests and certificates. For each dealer and employee, it tracks who has completed what, with automatic renewal reminders. Certain product lines or pricing tiers can depend on active certifications.

Reporting

Dashboards for channel and dealer

Insight into dealer revenue, claim frequency, stock velocity, MDF spend and lead conversion. Dashboards for your channel managers and self-service reports for dealers, so they can track their own performance — and adjust course before you need to have a conversation. Exportable to Power BI, Tableau or Looker.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Industries we build dealer portals for.

The terminology differs by industry — some brands call it a "dealer portal", others a "reseller platform", "distributor portal" or "channel partner portal" — but the underlying patterns are similar. In automotive and agricultural machinery, it often involves in-depth warranty flows, certification per product line and integrations with manufacturer software. In building materials and electronics, stock visibility and volume pricing play a bigger role. For white-label manufacturers, the focus is often on brand asset management, co-branding templates and separate tenants per customer brand.

In automotive and trailers, we often work with manufacturers who sell through importers to independent dealers, with workshop certifications and spare-parts flows on top. In agri and agricultural machinery, you also get heavy EDI integrations with machinery dealers, plus warranties that run for years on expensive components. In building materials and sanitaryware, we see a lot of volume pricing, project pricing and specified delivery times per building site. In electronics and household appliances, training tracking and compliance play a major role — your dealers may only sell certain product lines after passing a certification. And for white-label manufacturers producing for multiple brands, multi-tenant theming with separate DAM vaults is often the norm.

We choose the right architecture case by case. For one client, a lightweight solution with Sanity Studio or Strapi as the back end may be enough; for another, a deeper integration with SAP S/4HANA and a custom React front end is the right route. For yet another, a marketplace model in which dealers can actively buy and sell themselves makes a useful addition, and then we also look at our page on a marketplace platform as a reference. We always advise based on what your team already runs and what your maintenance partner supports — not on a preferred stack.

Tech stack and integrations.

We build dealer portals as modern web applications on a stack that works in virtually any enterprise environment and stays maintainable. Front end in React, Vue or Next.js with TypeScript, back end in Node.js, Python (Django or FastAPI) or .NET — depending on what your own IT team knows. Ultimately, the portal has to be managed by your people, or at least understood by whoever takes it over after us. An unfortunate stack choice can make that needlessly expensive in the medium term.

On the ERP side, we typically integrate with SAP S/4HANA, SAP Business One, Microsoft Dynamics 365 Business Central, Microsoft Dynamics 365 Finance & Supply Chain, Exact Online, Exact Globe, AFAS Profit, Unit4 or an in-house ERP. For product data, with Akeneo, Pimcore, Salsify, inriver or an in-house PIM. For digital assets, with Bynder, Brandfolder, Aprimo or an in-house DAM. For CRM, with Salesforce, HubSpot, Microsoft Dynamics CRM or Pipedrive. For BI and reporting, with Power BI, Tableau, Looker or Metabase. For EDI with large retail chains, we work with the usual standards (EDIFACT, X12) or via an EDI broker.

With dealer portals, compliance is not a side issue. GDPR and the cookie law are the baseline; export control and dual-use regulations also come into play if you sell products that may fall under European export bans — think electronics, machine parts or dual-use components. Product liability requires you to be able to show which dealer route a specific serial number has taken, including any training and certifications. That is why we build in an immutable audit log as standard, with traceability from order to end customer. For the broader architecture, you may also want to look at our page on smart API integrations, which covers the integration foundation a dealer portal sits on.

Frequently asked questions.

What clients usually want to know before we start.

What is the difference between a dealer portal and a B2B web shop?
A B2B web shop is, at its core, a transaction environment: placing orders, invoicing, paying. A dealer portal is broader and relationship-oriented: orders are one module alongside pricing tiers, claims, warranty, marketing content, MDF, leads, training and certifications. In practice, a single platform is often built that fulfils both roles — a dealer can place orders and handle warranty cases in the same environment. For a purely transaction-focused case, we refer you to our page on B2B e-commerce portals; for a broader channel platform, a dealer portal is the right route.
What is the difference between a dealer portal and a vendor portal?
The direction of the relationship. A dealer portal is for your indirect sales channel: dealers, resellers and distributors who pass your products on to the end customer. A vendor portal or supplier portal is for your suppliers, the parties who supply you with raw materials, components or services. Architecturally, both are secured web applications with SSO and role management, but the flows differ significantly: dealer portals have pricing tiers and lead distribution, while vendor portals have onboarding checks and certificates.
Can the portal integrate with SAP, Dynamics, Exact or AFAS?
Yes. We build integrations with SAP S/4HANA, SAP Business One, Microsoft Dynamics 365, Exact Online, Exact Globe, AFAS Profit, Unit4, NetSuite, Odoo and in-house ERPs via REST, SOAP or a message bus (RabbitMQ, Azure Service Bus). For dealers who supply large retail chains themselves, we can also set up EDI flows via EDIFACT or X12, with an EDI broker as an intermediate layer. Our approach is described on smart API integrations.
How do we handle access and authentication?
For your internal users, via SSO on your existing identity provider: Azure AD, Okta, Google Workspace or your own solution. For dealers, we usually work with an invitation-based account flow, optionally with SSO for dealers who offer it themselves, plus multi-factor authentication. Multiple roles are possible per dealer organisation: dealer admin, buyer, service technician, marketing manager, controller. That way, each user sees only what they need, and you safeguard the segregation of duties at the same time.
How does pricing per dealer work, and can contracts be kept in sync?
Pricing is driven by the dealer contract held in your ERP or CRM. The portal requests the correct price per item in real time, based on volume tier, certification level, region and any temporary promotion. Changes to the contract, for example a dealer moving up to a higher tier after reaching their annual volume, come through automatically without manual updates. For seasonal or promotional pricing, we can set up temporary discounts with start and end dates.
Does the portal work multi-tenant for multiple brands or business units?
Yes. For groups with multiple operating companies, brands or regions, we build multi-tenant theming on a single codebase: each tenant gets its own branding, its own DAM vault, its own roles, its own ERP integration and its own pricing structure. Dealers only see the tenant or brands they have access to, and your internal channel managers can switch between tenants from a single login. This is particularly relevant for white-label manufacturers or for groups that run multiple product lines under different names.
How do we handle lead distribution from consumers to dealers?
A lead comes in via your consumer website or a comparison site: a quote request, a service query or an expression of interest in a product. The portal routes that lead based on rules you set yourself: nearest dealer by postcode, dealer with the right certification, dealer with capacity at that moment, or strategically, an A-dealer first. The dealer sees the lead in their portal and accepts or declines within a set time, and if they decline, it is routed to the next candidate. This prevents leads from going cold or being picked up by several dealers at once.
What about security, GDPR, export control and the audit trail?
Encryption in transit (TLS 1.3) and at rest, role-based access following the principle of least privilege, and an immutable audit log for every action. GDPR baseline as standard, with data processing agreements per dealer where they process end customers' personal data. For export control (dual-use), we build in validation checks where needed, based on destination, end use and product category. For product liability, we retain the full order-to-end-customer chain so that, in the event of a recall or liability case, you can demonstrate the trail.
How long does it usually take to go live?
That depends heavily on the modules and the number of integrations. For a compact reseller portal with one primary flow (ordering plus pricing), we work in a project of a few sprints. For a dealer portal with claims, lead distribution and a CRM integration, we run over several sprints. For an enterprise platform with multi-region pricing, MDF, EDI and multi-tenant theming, it is a project of several consecutive sprints, sometimes delivered in phases per brand or region. We always work with a fixed sprint budget so you can adjust the scope sprint by sprint.
Do you build custom, or do you set up an off-the-shelf package?
Custom, but pragmatic. For SSO, document storage, search and email flows, we use proven libraries and services; we don't rebuild those. The application logic, screens, pricing engine and integrations with your order management system, ERP and CRM we do build custom, because that is exactly where every organisation differs. That way you stay in control of what is strategic, and you don't pay for custom work where standard building blocks do the job perfectly well.

Talk to us about your dealer portal.

A no-obligation introductory call of half an hour. We listen to your channel structure, your ERP landscape and the pain points that currently cost you the most time, ask sharp questions, and give you direction you can actually use, even if we turn out not to be the right partner in the end. For the broader context of our approach, you may also want to look at our software development page.

Share LinkedIn Email

Edit content