One product catalog. Clear responsibilities for every dealer.
Define what partners share, what they can change, and who takes ownership of the customer’s next step.
Agree which product rules every dealer shares.
Separate product knowledge from commercial rules
Dealers need consistent product names, dimension ranges, finish descriptions, and compatibility rules. These are the shared foundation. Price lists, commercial permissions, territory arrangements, and service responsibilities may vary by partner.
Document that distinction before designing a partner experience. A dealer should not need to maintain a separate interpretation of the product to work with a different commercial arrangement. Keep the shared vocabulary stable and identify who owns each update.
Specify permissions with real tasks
Instead of asking for a generic dealer portal, list the tasks people need to perform. Can a dealer create a concept, revise a brief, see a trade price, request a review, or place an approved order? Does someone at the manufacturer need to approve changes?
Define the visibility of customer information as carefully as the product controls. Write down which records a dealer may see and what reaches the manufacturer. The production implementation should follow those agreed responsibilities.
Make routing understandable to the customer
A customer may start on a manufacturer’s website and continue with a local dealer. Decide when that handover happens, what information travels with it, and how the customer learns who will contact them. Preserve the configuration so they can recognize the conversation.
Use clear ownership when a buyer changes location or asks about a different range. The brief should show which team is currently reviewing the request. Technology can support the handover after the business process has been agreed.
Keep updates and review work visible
When a finish changes or an accessory becomes unavailable, identify who updates the shared source and how partners learn about it. Review representative configurations after a rule or price update. A consistent catalog needs an operating process, not just a launch checklist.
Start with a small group of partners and their real tasks. Observe where they need extra explanation, where a permission is too broad, and where ownership is unclear. Use those findings to define the next release before extending the network.
Worked example: a shared carport range
In a hypothetical network, the manufacturer maintains carport dimensions and compatible panels. A dealer discusses the customer’s setting and prepares the brief.
- Shared source: product names, dimensions, finishes, and option rules.
- Dealer task: collect selections and local installation context.
- Manufacturer task: review the specification before the agreed commercial next step.
Your review list.
- Agree which product rules every dealer shares.
- Describe permissions using specific tasks.
- Name the team responsible for each enquiry stage.
- Define how catalog changes reach partners.
See the next step
in Sales Visualizer.
Explore an illustrative experience, then review your own range and requirements with your team.
Explore the dealer network approach