X Dağıtım Product concept

From dealer to approval, every order step in one place.

Orders, campaigns and account information in one app; dealers place their own orders without waiting for a representative.

X Dağıtım product concept with sample data: the dealer portal's Place Order screen shows Market A's account balance, a dealer-specific sunflower oil campaign and frequently purchased products based on recent orders. In front, a phone displays a smart basket of 22 boxes based on last month's order, the dealer discount and the Confirm Order button.
Dealer-specific campaignFull screen ↗
Product concept: screen designs and a sample order flow you can try below. X Dağıtım is fictional; screen data is illustrative.
Industry
Retail & Distribution
Capabilities
Product Strategy, Experience Design, Software Engineering
Platform
Web, iOS, Android
Try it

Take an order from the dealer to manager approval.

Different price lists, telephone orders and unclear approvals can complicate a single workflow. This short demo shows where the dealer and manager take responsibility.

Sample data only: X Dağıtım and Market A are fictional. The demo runs in your browser; it creates no orders, payments, ERP records or emails. Data resets when the page is refreshed.

Workflow and limitations

  1. Dealer: Views assigned sample prices and specifies quantities in boxes.
  2. Rule check: The order goes for manager approval. Exceeding the available limit requires additional approval.
  3. Manager: Approves the order and, if necessary, the credit-limit exception.
  4. Activity history: Completed steps are visible; you can restart and try again.

What does a real ERP integration require?

Define which system owns prices, stock, account limits and orders; API or file access; user roles; data refresh frequency; a transaction ID that prevents duplicate orders; and outage and reconciliation rules. Acceptance of a request by the portal is not the same as ERP approval.

The demo does not prove access-control security, concurrent transaction behaviour or compatibility with an ERP product. Those require separate design and testing in a real project. See the guide to ERP data ownership and error handling for more information.

Scope of our B2B portal development service · Prepare a dealer portal brief

The flow in one minute

Watch the dealer order demo

About one minute: screens from the same fictional workflow with synthetic Turkish narration, Turkish subtitles and a transcript.

Video transcript

This dealer ordering demo works with sample data only. In the dealer role, you see the box prices assigned to Market A. You can change the sample basket or create the order using the initial quantities. No real order, payment or email is created.

The sample order totals seven thousand one hundred and sixty Turkish lira. It exceeds the available six-thousand-lira credit limit, so additional approval is required. Switch to the manager role, review the amount and approve exceeding the limit for this demo only. In a real system, authorisation is checked on the server.

After manager approval, open the activity history. You can see order creation, the limit warning and approval in sequence. There is no ERP record or dispatch in this flow. Use Start over to reset the example, or visit the B2B portal service or project brief for your actual requirements.

Problem and approach

Problem

At many distributors with dealer networks, orders still pass through a field representative's phone.

The dealer lists requirements one by one and the representative enters the order manually. Campaigns disappear in group messages, and another call is needed to check balances and due dates. Representatives spend their time entering orders instead of selling.

Approach

We start designing at the dealer's counter, not in the office.

First, we examine the dealer's and representative's current ordering process and identify the sources of prices, stock and credit limits. A pilot user group evaluates the prototype. First-phase scope and timing are agreed after reviewing ERP access, data quality and acceptance criteria. Rollout is planned based on pilot results.

Solution

One app for dealers, one dashboard for the sales team.

The X Dağıtım concept's field sales dashboard, with sample data: monthly targets and order cards, a chart showing weekly orders by channel, the daily visit route and a table of dealers' account positions.
Order channel overviewFull screen ↗
Field sales dashboard: monthly targets, visit routes and dealer accounts in one view.
A campaign notification and two screens from the X Dağıtım concept's dealer app, with sample data. Left, the home screen: a personalised campaign for Market A and a basket based on last month. Right, the account view: current balance, available limit, next due date and invoices.
Dealer appFull screen ↗
The dealer app remembers last month's purchases before the dealer has to.
  1. Smart basket based on order history

    The basket is prepared from previous orders; dealers approve it with one tap or adjust it box by box.

  2. Dealer-specific campaigns and prices

    Each dealer sees only their own prices and campaigns. The basket shows how many more boxes are needed to qualify for a campaign.

  3. Accounts, invoices and payments

    Balance, credit limit, open invoices and due dates in one view. Dealers can make payments in the app.

  4. Visit and target dashboard

    Representatives start the day with their route and target. Their commission remains assigned to them regardless of which channel brings in the order.

Scenario and scope

Example users

Dealer ordering user, dealer approver, accounting and sales representative.

Example workflow

A dealer sees their own prices, builds a basket from a previous order and approves it within their permissions. The ERP verifies prices and limits; the order number, dispatch and account status return to the portal.

Decisions for a real project

Define dealer and branch roles, price and campaign sources, stock update delay, credit-limit behaviour, payment provider and pilot group. Representative incentives and visit rules follow the company's own policies.

Related service: B2B portal development. You can list your own users and systems in the project brief tool.

Timelines, teams and technologies in this scenario are illustrative planning choices; actual scope, schedule and team are defined during discovery. Product names do not imply partnerships.

What we measure

%60Target: share of orders through digital channels in the first year
%10Target: increase in average basket value
6 hoursTarget: weekly order-entry time saved per representative
%50Target: reduction in calls about balances and due dates

These targets are example measures defined for this scenario; actual results vary by project.

Technology and team

Technology

  • Flutter
  • NestJS
  • TypeScript
  • PostgreSQL
  • Redis
  • ERP integration (Logo, Netsis, SAP)
  • GCP

For dealer portal scope, ERP integration and delivery terms, see the B2B portal development page.

Suggested team 7 people

  • 1 product strategist
  • 1 product designer
  • 4 software engineer (mobile, web, backend)
  • 1 QA engineer

Your process

Do you manage a similar operation? Let's schedule a 30-minute conversation about bringing dealer orders and accounts into one app.

Let's discuss this concept

This is an example, not a limit; we apply the same approach to similar processes in other industries.