Contents
On Monday morning, customer service gets three calls about delivery, two quote requests and a message asking to reorder last month’s purchase. Each request takes a few minutes. One might require someone to check stock, look up contract terms and confirm a date with the warehouse. To decide where a B2B portal should start, look at what customers ask for and what it takes to answer them.
Choose a task customers already do
Sample two weeks of calls and messages. With the team, record the request, the work it took and the piece of information most often missing. Order tracking can be a good start if ERP status data is kept up to date. If the same buyers regularly ask for another price or order, a prefilled request might suit them. Invoices and packing slips are another option if the files and access rules are already reliable.
TablePossible starting points for a distributor’s customer portal · shareable block
| Minimum data to make reliable | Exception to test before launch | |
|---|---|---|
| Order tracking | Status and update time for each order line. | Partial shipment with one line on backorder. |
| Repeat ordering | Active item reference, price and available quantity. | Discontinued product or price negotiated since the original order. |
| Quote request | Company, buying location and requested items. | Unusual quantity that requires internal sign-off. |
| Document access | Invoice or packing slip tied to the right location. | Removal of a buyer’s role at one branch. |
Keep track of the requests that fall outside the normal case. One line may have shipped while a second remains on backorder. Ask how the team explains that situation today. Buyers should be able to tell what has left the warehouse and what still needs a date. A single “In progress” label may simply send the call to someone else.
Decide what the portal can promise
Assign a source and owner to each piece of information displayed. The portal can show the latest status provided by the ERP, with an update time. Sales can retain responsibility for exceptional pricing that needs approval. The warehouse confirms what it can ship. If synchronization stops, show the time of the last update and give the customer a way to request confirmation.
For an initial launch, repeat ordering can start by preparing a request from a past purchase. Recheck price, available quantity and shipping location before placing a new order. Flag discontinued items even when the original product reference remains in the history.
Give buyers access to the right location
One person might place orders in Laval and view invoices for Longueuil, while a colleague can only access one location. Agree on these rules with the pilot customer. Shopify B2B distinguishes companies, their locations and the people buying for them. Pricing and terms can vary by location. A custom portal needs equally explicit rules for the data it uses.
Test real changes during the pilot. One buyer moves to another branch, another leaves the organization and a manager takes over their work. Check account access, links to documents and which part of the history remains visible after the change.
Decide when to invite more customers
Invite a few buyers who already use the workflow you chose. Record which requests they complete online, where staff still re-enter data and what comes back to customer service. Have someone verify the records read from or written to the ERP. Frequent corrections to quantities, prices or permissions tell you what to fix before expanding the launch.
If the portal connects to Shopify, the B2B location access update gives your team specific permission changes to test.
Daillac can scope the first workflow from two sample requests and the way your team handles them today. That gives you a basis for estimating the integration work and deciding what the first version can show customers.
Frequently asked questions
Should a distributor launch reordering first?+
It can make sense for buyers who routinely purchase the same products if the portal can recheck prices and availability before confirming an order.
Can we proceed without live inventory data?+
Yes, if the portal shows how current its stock data is and offers a way to confirm it. Decide when a quantity can be treated as a commitment.
What should we test for a multi-location customer?+
Check pricing, terms, addresses and document access by location. Test a role removal while the customer account remains active.
How should we choose pilot customers?+
Invite buyers who already use the selected workflow and can report issues. Include a case that requires manual confirmation.
Scope my portal’s first workflow
D
Written by
Daillac

