Skip to content
Besh Bilişim Technology Services
bilgi@beshbilisim.com
İsmet Kaptan, 1372 Sk. No:15, İzmir
Besh Bilişim Besh Bilişim Besh Bilişim
  • Home
  • Services
    • Izmir Software and Web Services

      Izmir-based Besh Bilişim: website design, custom software, mobile apps, e-commerce and automation services under one roof.

    • Website Design

      We design fast, secure, mobile-friendly and SEO-ready corporate websites so your brand looks professional on every screen.

    • Besh CMS

      Manage your pages, blog and media from a single panel with minimal coding knowledge and update your site whenever you like.

    • Mobile Applications

      We build fast, user-focused mobile apps for both iOS and Android from a single React Native codebase. Get a quote for your mobile project.

    • Automation Software

      We build software that automates processes such as invoicing, delivery notes and stock tracking, and saves you time.

    • Accounting Software

      Track and manage invoices, accounts, stock, cash and bank transactions easily from a single program. Explore Besh Bilişim accounting software.

    • E-Commerce

      Sell your products online and track orders in one place; we build tailor-made, SEO-friendly e-commerce platforms.

    • SEO Services

      We help your website become more visible on Google and win more visitors and potential customers. Get in touch for our SEO services.

    • Web Software

      We build fast, scalable corporate web applications and portals with Next.js, React, TypeScript and .NET. Get a quote for your project.

    • Support and Maintenance

      Installation, training, maintenance and 24/7 technical support keep your systems running without interruption.

    • Custom Software Development

      Where off-the-shelf programs fall short, we build custom software designed around your business. Tell us what you need and get a quote.

  • Designs
  • Blog
  • About
  • Contact
EN
EN
Contact Us
November 16, 2026 Besh Bilişim Software Development

Moving Dealer Orders Off WhatsApp and Excel: A B2B Portal Transition Roadmap

Short answer: move dealers over in stages instead of closing the old channel in one go

The riskiest way to move dealer orders from WhatsApp and Excel to a portal is to announce one day that "from now on, portal only". The safer path has four stages: first measure the current setup, run a pilot with a small group of dealers, work in parallel while keeping the old channel open, and close the old channel only after the portal has settled. The plan below is a general suggestion; the durations are examples and are not based on the timeline of a completed Besh project. They change with your dealer count, product structure and ERP connection.

Stage Example duration Purpose Output of this stage
1. Measurement and preparation 1-2 weeks Get a picture of the current setup Order count, channel split, error types, dealer list
2. Pilot 3-6 weeks Take real orders with 5-10 dealers A corrected portal, a short guide
3. Parallel period and expansion 4-8 weeks Add dealers in groups Measurement of the portal's share of orders
4. Closing 1-2 weeks Close the old channel An announcement, an exception rule

We explained what a portal is in What is a B2B dealer portal? and the ERP connection in connecting a dealer portal to an existing ERP.

Why leave WhatsApp and Excel?

These two tools are not wrong; they work while order volume is small. The problems appear as volume and dealer count grow:

  • Excel produces errors. In a compilation of spreadsheet audits, in nine studies using known methods, errors were found in 84% of real organisations' spreadsheets on a weighted average (the researcher calls this an "alarming percentage"). Assuming that the spreadsheet of a company tracking orders in Excel is error-free would be optimistic. This research does not measure order tracking in particular; it is a general spreadsheet error rate.
  • The order stays tied to a person. An order that arrives on WhatsApp sits on the phone of the employee who received the message; if the employee is on leave or leaves, the record and its context go with them. This is not an observation of ours but a consequence of the structure.
  • Personal data stays scattered. The names and phone numbers of dealer contacts are personal data. KVKK article 12 places data security obligations on the data controller; order conversations scattered across personal phones are hard to audit in this respect. For a definitive legal assessment, consult your legal adviser.
  • Price and stock information goes stale. A price list sent to a dealer on WhatsApp starts to age the day it is updated.

Stage 1: Measure the current setup first

Before building a portal, count the last 30 days of orders and answer these questions:

  • How many orders came in, through which channel (phone, WhatsApp, email, Excel)?
  • How many needed correction: wrong product code, wrong price, out-of-stock item, forgotten line?
  • How many hours pass between an order arriving and being entered into the ERP, and who does the entry?
  • Which dealers place most of the orders? Which are regular and which seasonal?

These numbers do two jobs: they show what work the portal will actually do, and they form the baseline for the question "did the move work?" at the end. If you have no data, record it in a simple table for one month; do not start from guesses.

Stage 2: How do you choose pilot dealers?

Build the pilot in a way similar to how the GOV.UK Service Manual describes the beta phase: first invite a limited number of users, collect feedback and improve, and open it to everyone once you are confident about scale. A dealer portal is not a public service, but the logic of starting with limited users is the same. For the pilot dealers, pay attention to:

  • Different types of dealers: If you choose only the most willing and tech-friendly dealers, problems stay hidden. Take one example each from small and large, frequent and occasional, computer-based and phone-based dealers.
  • Dealers with a solid relationship: There will be errors in the pilot; choose dealers who will tolerate them and give you open feedback.
  • Number: 5-10 dealers is a manageable start for most businesses; this is our suggestion, not a rule. It should be small enough that you can listen to each one's feedback and wide enough to cover the different types.
  • A clear pilot scope: Which orders will pilot dealers place through the portal (all, or a certain product group)? Do not mix "test" orders with real ones.

Stage 3: Training: what do you teach dealers, and how?

A dealer should not need long training to use the portal; if they do, there is a problem in the design. The first orders are still critical:

  • Place the first order together. By phone or screen sharing, guide the dealer through a first order with their own products.
  • A one-page guide: Login, product search, adding to the basket, order status, who to contact when there is a problem. Long documents do not get read.
  • Do not teach something new; make a familiar thing easier: The dealer already orders by product code or name; the portal should let them search the same way. Shortcuts such as re-ordering from a previous order help the dealer adopt the portal.
  • Train your own staff too: A sales representative can enter an order received on WhatsApp into the portal themselves, setting an example for the dealer; this is a transition method.

Stage 4: The parallel period: do not close the old channel right away

On the same page, GOV.UK says that if you are replacing a legacy service, you should keep the legacy service running until the new service goes live. For dealer orders this means: during the pilot and expansion periods the WhatsApp and Excel channel stays open, but you answer each order that arrives by telling the dealer, in the same minute, how to see it in the portal. Keep the rules in writing during the parallel period:

  • From which date will each dealer order only through the portal?
  • Does an order from the portal get shipping priority? (If so, say it openly and apply it; this is an incentive, not a penalty.)
  • When is an exception accepted? If the portal is down, where does the dealer place the order?

Why do dealers resist, and what do you answer?

Resistance Likely reason behind it Answer
"WhatsApp is faster" Finding a product or ordering in the portal is slow Improve search and re-order shortcuts; measure
"I cannot see my price in the portal" The dealer-specific price is not defined or is wrong Check prices with the dealer during the pilot (pricing rules)
"We don't work on a computer" The dealer works from a phone Verify the portal is comfortable to order from on mobile
"Who do I ask if something comes up?" The support channel is unclear A single support address/phone inside the portal and in the guide
"I can't see my order" Status information is missing Add order statuses and email notifications

What do you measure?

Track the progress of the move with three numbers:

  1. Portal share of orders: What percentage of total orders comes through the portal?
  2. Share of orders needing correction: Compare with the Stage 1 measurement.
  3. Time for an order to enter the ERP: If the portal transfers automatically, it should drop to seconds; if manual entry remains, find out why.

You set the target numbers; we do not give a general figure such as "X percent in the first month" because it depends heavily on the dealer structure.

Checklist before starting the move

  • ☐ Order count, channel and error types for the last 30 days are worked out
  • ☐ Dealer-specific price and stock show correctly in the portal
  • ☐ Orders from the portal go to the ERP, or it is clear who will enter them manually
  • ☐ Pilot dealers are chosen from different types
  • ☐ A one-page guide and a support channel are ready
  • ☐ When the old channel closes and the exception rule are written down
  • ☐ There is a starting value for the three measurement numbers

Frequently Asked Questions

How many months does the move take?

It depends on your dealer count, product structure and ERP connection. The four stages above add up to a few months as an example, but this is a general planning example, not a commitment or the duration of a Besh project. Set a realistic duration with the numbers measured when the pilot ends.

What if dealers refuse to use the portal?

First find out why; often the portal makes the dealer's work harder (wrong price, product not found). Imposing a requirement without fixing the cause can lose the dealer. Write the exception rule in advance: the dealer may order through the old channel for a while, but someone on your side enters the order into the portal.

Should I set up the ERP first or the portal?

If stock, price and limit data are scattered, this data first needs to be gathered in one place. For the move from Excel to ERP, see our 90-day plan. If you already have an ERP, the portal can start by reading from it and writing orders to it.

Do I have to give up WhatsApp entirely?

No. You can keep it as a communication channel (shipping information, questions) while dropping it as an ordering channel. What has to stop is an order being placed inside a chat and never reaching any system.

If you would like to work out the portal and the transition plan for your dealer network together, you can look at our custom software development and automation software services or get in touch.

Sources: Audits of Operational Spreadsheets (Raymond R. Panko), How the beta phase works (GOV.UK Service Manual), Law No. 6698 on the Protection of Personal Data (Ministry of Justice)

Cover photo: Unsplash

Dealer OrdersChange ManagementB2BPilot RolloutWhatsApp OrdersExcelKVKKDealer Portal
All posts
Latest posts
  • CRM Software Selection: Ready-Made, ERP-Linked or Custom CRM?
    November 19, 2026
  • ERP for Building Materials Wholesalers and Manufacturers: Variants, Price Lists and Dealers
    November 19, 2026
  • Marketplace Integration: Managing Trendyol, Hepsiburada and n11 from One Stock Pool
    November 19, 2026
  • Manufacturing ERP: BOM, Work Orders and Stock Costing Features to Look For
    November 19, 2026
  • ERP for Wholesalers: Features to Look for in Multi-Warehouse Stock, Due Dates and Accounts
    November 16, 2026
Categories
  • Software Development 16
  • Web Development 9
  • AI and Security 3
  • SEO and Digital Marketing 2
  • E-Commerce 1
Tags
ERPSMEsE-CommerceDealer PortalIntegrationCustom SoftwareTotal Cost of OwnershipB2BSoftware SelectionWholesaleAIChecklistDeveloper ToolsERP IntegrationIzmirKVKKOff-the-Shelf SoftwareAI AgentsAPI IntegrationAstro
Besh Bilişim
  • Fb.
  • Ig.
  • In.

Besh Bilişim - Izmir Office İsmet Kaptan, 1372 Sk. No:15, İzmir

Email

bilgi@beshbilisim.com

Phone

+90 553 443 30 00
Newsletter

© 2026 Created by Besh Bilişim Teknolojileri

BESH

We use cookies to offer you a better experience and to analyze site traffic. Analytics cookies only work with your consent. Cookie and privacy information