Soroush Neyestani

Software Engineer

Application Architect

Enterprise Application Developer

Technical Author & Educator

Representative Network & Commercial Rules Engine

Representatives · Marketers · Sales Rules · Commission · Targets · Payments

One-Line Description

A commercial governance module for representative and marketer networks, combining territories, sales rules, commissions, targets, payment conditions, check tracking, incentives, penalties, and sales-conflict handling.


Why This Is Separate from CRM

CRM answers:

Who is the customer and where is the opportunity?

Commercial Rules answers:

Under what organizational and financial rules is the sale allowed to happen?

These are different domains.


Representative vs Marketer

The platform distinguished different commercial actors.

This distinction matters for:

  • ownership,
  • territory,
  • commission,
  • targets,
  • contractual responsibilities.

Commercial Rule Categories

The system specification included concepts around:

  • cash sales,
  • installment sales,
  • minimum payment requirements,
  • historical sales conditions,
  • check collection,
  • commission calculation,
  • sales targets,
  • incentives,
  • penalties,
  • representative conflicts,
  • obligations between company and representative.

Payment Conditions

A configurable commercial rule engine can define:

Sale Type
├── Cash
└── Installment

Each may include:

  • minimum deposit,
  • permitted payment structure,
  • required approvals,
  • due dates.

Check / Payment Tracking

The system could register:

  • checks,
  • amounts received,
  • payment dates.

Notifications could be connected to due dates or collection status.


Commission

Commission logic can depend on:

  • representative,
  • marketer,
  • product,
  • sale amount,
  • collection status,
  • sales target.

A modern implementation should store commission calculations transparently.


Targets

The platform supported sales targets.

Potential dimensions:

  • period,
  • representative,
  • marketer,
  • product category,
  • revenue,
  • quantity.

Incentive & Penalty Logic

Targets could feed:

  • incentives,
  • rewards,
  • penalties.

These rules should be versioned because commercial policy changes over time.


Territory / Representation Rules

Representatives may operate inside defined geographic or commercial scopes.

A modern V2 can model:

Representative
├── Territory
├── Product Scope
├── Valid From
├── Valid To
└── Contract

Sales Conflict Handling

When multiple sales actors claimed the same customer/opportunity, the platform needed a controlled resolution process.

Potential outcomes:

  • ownership to one representative,
  • shared participation,
  • commission split,
  • management decision.

Commercial Policy Versioning

Commercial rules change.

Do not overwrite old rules.

Example:

SalesPolicy v1
SalesPolicy v2
SalesPolicy v3

Existing contracts should remain linked to the rule version under which they were created.


V2 Architecture

Recommended entities:

Representative
Marketer
Territory
SalesPolicy
PaymentRule
CommissionRule
Target
IncentiveRule
PenaltyRule
Check
CollectionEvent

Career Evidence

  • sales governance,
  • commission systems,
  • representative networks,
  • rule engines,
  • commercial policy versioning,
  • financial workflow integration,
  • target management.

Suggested Slug

/projects/representative-commercial-rules

Cover Direction

Commercial Rules & Representative Network

Visual elements:

  • representative network,
  • territory map,
  • commission,
  • targets,
  • payment/check timeline,
  • policy rules.