Engin Sistem
PROJECT CASE STUDY

A Multi-Level Dealer Portal

A wholesaler brought a three-level dealer network into one portal with role-based access, pricing, commission calculations and Netsis ERP integration.

Industry Wholesale and distribution

Problem

Manual pricing, stock and commission handling across a three-level dealer structure caused errors and repeated reconciliation work.

System built

One hierarchical portal combined level-based access, pricing rules, commission calculations and ERP-connected stock and orders.

Outcome

The portal became a core part of the dealer operation. The Turkish case study reports lower pricing and commission errors and faster order processing, using anonymized ranges.

We built a digital operating structure for a wholesaler’s three-level network: main distributor, regional dealer and retail sub-dealer.

Context and operating conditions

The distributor used Netsis and had more than 300 sales points across the country. Products passed through distributors to sub-dealers, so a single dealer category could not represent the network.

The problem: an opaque chain

Each level had its own purchase price and commission rate. Staff managed the structure with spreadsheets, phone calls and email.

  • Commission reconciliation: Distributor premiums were sometimes miscalculated, leading to repeated disputes.
  • Disconnected pricing: Price lists moved from ERP to spreadsheets and then to dealers, creating opportunities for incorrect prices.
  • Invisible stock: Retail dealers could not see stock at the center or their distributor, increasing phone traffic.

Why one hierarchical portal was chosen

Early ideas included giving dealers access to Netsis’s own B2B module or creating three separate B2B sites. Exposing ERP interfaces to the dealer network would have created access and usability concerns. Three separate sites would also have multiplied product and stock administration.

We chose one portal with a role and rules engine. Everyone entered through the same portal, but each person saw the information and actions appropriate to their level. A main distributor could see sub-dealers and premium information; a retail dealer saw a simpler buying screen and its own purchase prices.

System architecture

  • Role-based interface: Menus, actions and views followed each user’s permission matrix.
  • Commission engine: Orders from a sub-dealer contributed to the associated main distributor’s commission calculation.
  • Netsis integration: The portal read price lists, account balances and open invoices from ERP and sent orders back with the relevant dealer code.

Operational result

The dealer structure was brought into one view. The Turkish record reports commission-reconciliation disputes falling to almost zero, pricing-related objections and returns declining by 90%, and roughly two hours a day of central-office phone queries about stock, price and premiums being removed. It reports pricing and commission error ranges moving from 5–10% to 0.5–1%, and order processing from 15–25 minutes to 4–8 minutes over five months. These are anonymized project figures, not general guarantees.

The system has remained in active use for years as a central part of the dealer operation.

Related dealer portal and custom pricing scenarios are currently in Turkish.

Considering a similar system?

Tell us how the process works in your business and where it slows down.

Request a system review

Read the Turkish original →

Measurement preference

Choose whether Google Analytics and Google Ads tags may load in this browser.

Withdrawing permission stops new measurement events. This control cannot retrieve measurements already sent.

Privacy notice