Project registration and price protection rules
Set the submission, decision and protection rules for reseller plant projects.
- Industry
- Manufacturing, Wholesale and Distribution
- Team
- Sales, Operations
- Use case
- CRM and sales, Requests and exceptions
- Tags
- Partner program Approval workflow
- Includes
- 1 app
Template preview
1 / 2
Included items
-
Dashboards
App · Embedded views: c-pipeline, c-registrations, i1 · Requires sign-in
Overview
What this template supports
A rules page for manufacturer channel teams and resellers registering a plant project. It explains which projects qualify, the fields a complete registration needs, how competing claims are decided, the price-protection period, extension conditions and what ends protection.
- Eligible project definition
- Complete registration checklist
- Decision and conflict sequence
- Protection and extension rules
How to use this template
-
Define eligible projects
Adapt the plant, contact, product and opportunity requirements to the program.
-
Set decision rules
Confirm who checks conflicts and approves or declines a registration.
-
Publish current terms
Review protection periods, price rules and expiration triggers before sharing.
Frequently asked questions
What happens to an incomplete registration?
Channel operations holds it for missing project details before deciding protection or a conflict.
Who uses this page?
Reseller sales teams and manufacturer channel operations.
Which product details matter in the submission?
Name the pump maker, model and size, quantities and parts so reviewers can identify the exact plant project.
What must a complete registration include?
Identify the plant project and customer contact, pump maker, model and size, quantities and parts, estimated list value, and expected order date.
What should be reviewed before using it?
Adapt the plant, contact, product and opportunity requirements to the program. Confirm who checks conflicts and approves or declines a registration.
Who can see the page and its embedded views?
The partner-facing rules can be shared; internal conflict details stay in the channel team's procedure.
