We build dealer portals as modern web applications on a stack that works in virtually any enterprise environment and stays maintainable. Front-end on React, Vue or Next.js with TypeScript, back-end on Node.js, Python (Django or FastAPI) or .NET, depending on what your own IT team knows. Ultimately the portal needs to be managed by your people, or at least be understood by whichever party takes over from us. An unfortunate stack choice can make that unnecessarily 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 a custom ERP. For product data, we work with Akeneo, Pimcore, Salsify, inriver or a custom PIM. For digital assets, Bynder, Brandfolder, Aprimo or a custom DAM. For CRM, Salesforce, HubSpot, Microsoft Dynamics CRM or Pipedrive. For BI and reporting, 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.
Compliance is not an afterthought with dealer portals. GDPR and the cookie law are the baseline; in addition, export control and dual-use regulations (DUL) come into play if you sell products that may fall under European export restrictions, such as electronics, machine parts or dual-use components. Product liability requires you to be able to demonstrate which dealer route a specific serial number has followed, including any training and certifications. We therefore build 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 depends on.