The First 90 Days of a Dealer Portal Rollout

A dealer portal project rarely slips because of the software. It slips because of data: nobody has settled which product belongs on which list, the same dealer has two account records in the ERP, and there is a quantity-break table nobody owns.

The schedule below is not a commitment. It is a frame showing how the sequence is built, and the order of the steps matters more than their duration.

Before you start: one owner per dataset

The first decision in the project is not a technical one. Product data, pricing data, and dealer records each get a named owner. That person is not the one who answers questions; they are the one who decides when two answers conflict. Any dataset without an owner turns into a waiting item halfway through the project.

Days 0-30: product, price, and dealer data

You review what the product record will look like on the portal: name, code, unit, inner-case quantity, assortment rule, technical attributes, and image. On the pricing side, the list, group discounts, contract rates, and quantity breaks are gathered into a single table. On the dealer side, duplicate account records are merged and each dealer's price group is confirmed. This month feels less like a portal project and more like a data cleanup, and it should.

Days 30-60: integration and pilot

The ERP connection goes in and is verified field by field: stock quantities, account balances, and open invoices in one direction; orders and collection records in the other. Then a small pilot group is picked — dealers close enough to call you directly, and varied enough to represent the channel. The point of a pilot is not to find bugs but to see how the flow you designed is actually used. Those are not the same thing.

Days 60-90: opening the channel

Go live in waves rather than all at once. Each wave gets a short walkthrough, credentials, and hands-on help with the first order. Adoption moves noticeably faster when the field team runs that walkthrough themselves. Do not close the phone channel at this stage; simply enter every phoned-in order on the portal, so the habit shifts on its own.

What to look at after day 90

Define your own measures up front: the share of order lines coming through the portal, the number of dealers who have never logged in, the number of post-order corrections, and how the overdue balance is moving. Those four tell you whether the project worked far more honestly than a satisfaction survey will.

The most common mistake

Planning it like a software installation. A portal is the written form of the commercial relationship a company has with its dealer channel; if that relationship is unclear, the portal will not clarify it, it will only show it to everyone at once. The good news is that the clarity is yours to keep, even if the project stalls.