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.
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.
Fictional demo environment
Dealer order desk
For Market A: sample box prices (excluding VAT). Available sample credit limit: TRY 6,000. In a real project, prices and limits are verified against the authoritative system.
Dealer prices and the approval amount are fixed within the demo. In a real application, approval authority is verified on the server; switching roles on screen does not grant access rights.
Credit-limit check: The order exceeds the available TRY 6,000 limit. This sample policy requires additional manager approval; a real business policy may block the order entirely.
In a real integration, ERP acceptance is a separate status after this flow. This demo has no ERP, stock reservation, payment or dispatch.
Workflow and limitations
- Dealer: Views assigned sample prices and specifies quantities in boxes.
- Rule check: The order goes for manager approval. Exceeding the available limit requires additional approval.
- Manager: Approves the order and, if necessary, the credit-limit exception.
- 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
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.
One app for dealers, one dashboard for the sales team.
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.
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.
Accounts, invoices and payments
Balance, credit limit, open invoices and due dates in one view. Dealers can make payments in the app.
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
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 conceptThis is an example, not a limit; we apply the same approach to similar processes in other industries.