How should a configurator work for dealers with several branches?

A dealer with several branches needs more than a shared company login. Define which branch owns each project, which employees can access it and which commercial or installation terms apply. Keep the dealer company, branch and individual salesperson distinguishable in the application.

Identify the operational meaning of a branch

Branches may share a catalogue while serving different territories or using different installation teams. Some companies centralize pricing; others delegate commercial approvals. Record the actual arrangement instead of assuming that every branch needs a separate copy of the configurator.

The branch attached to a project should be meaningful to the receiving sales and factory process. A logo change alone does not establish operational ownership.

Test a salesperson moving between branches

Create projects at branch A, then move the salesperson to branch B under the agreed process. Check old project access, new project ownership and any price-list changes. Decide which records remain available for service continuity and which require reassignment.

Repeat with a regional manager who should see both branches. Use ordinary accounts so the demonstration verifies the actual permission model, not an administrator's unrestricted view.

Keep shared customers from creating confusion

A customer may request a second product from another branch. Define whether the business shares customer information and how staff identify related projects. Your company's privacy and operating policies should guide those decisions.

Avoid merging projects merely because email addresses or names match. The selected product, commercial scope and responsible branch still need their own records.

Specify the network in Configurix

A Configurix manufacturer and dealer application can be scoped for branch-specific workflows. Provide examples of account administration, employee movement and project transfer. Ask which responsibilities can be managed by your administrators and which require support.

Must every branch have a separate website?

Not necessarily. A shared application can present the appropriate brand and branch context when that is the agreed architecture. Specify how customers reach the correct team.

Should branch managers see internal manufacturer costs?

Only where the approved permission model permits it. Company or branch access should not automatically imply access to every commercial field.