Skip to content

Distribution and partner channels

Module id: distribution

What a partner may sell, in which territory, and how that channel looks.

Product definitions stay in products. This module holds the partner, the assignment, and the branding.

Distribution, read top to bottom: partner portal, then branding and catalogue, then distributor records
Read top to bottom. The partner portal is the channel. Branding and the partner catalogue sit in the domain. Distributor, agency, and agent records sit in the core.

exp-distributor is the portal. domain-distributor-branding and domain-distributor-catalog shape what that portal shows. core-common-distributor-mgmt stores the distributor.

What it owns

  • Distributors, agencies, agents, and agent roles
  • Territories and product assignments for a partner
  • Branding, terms templates, and channel configuration
  • Partner catalogue views and simulations for that partner

What it does not own

  • The product master. That is products.
  • The party of record for a customer. That is customers.
  • Direct-to-customer journeys that do not pass through a partner.
  • Channel init for a customer app. That is exp-channel-management under shared services.

Repositories

Repository Layer What it holds OpenAPI
exp-distributor Experience Portal: profile, branding, agents, agencies, territories, products, catalogue, simulations openapi.yml
domain-distributor-branding Domain Distributor, agency, agent, territory, operation, configuration openapi.yml
domain-distributor-catalog Domain Partner catalogue, simulations, shipment queries openapi.yml
core-common-distributor-mgmt Core Distributor lifecycle, agencies, agents, territories, assignments openapi.yml

How the pieces fit

exp-distributor is the BFF at /api/v1/experience/distributors. The portal asks it for profile, branding, agents, agencies, territories, products, catalogue, and simulations.

domain-distributor-branding answers distributor, agency, agent, territory, and configuration. domain-distributor-catalog answers the constrained catalogue, simulations, and shipment queries. Those are domain queries over the partner's view, not a second product master.

core-common-distributor-mgmt persists distributors, agencies, agents, roles, territories, product assignments, terms templates, and configuration. The product id on an assignment points at products.