2602_Coupon_Logic

1. Coupon Lifecycle

Release
Send to Installer
Use by Reseller
Utilize
Report
•Owner: MKT
•Observer: Sales
•Fields: Coupon UID, Options
•Description: an owner releases any
quantity with pre-configured
parameters
•Owner: MKT
•Observer: Sales
•Fields: Installer UID
•Description: an owner sends
coupons by available channels to
installers, the platform should
automatically link Installer UID to
Coupon UID
•Owner: Sales
•Observer: MKT
•Fields: Reseller ID, Activation time
•Description: when Installer comes to
Reseller, Reseller should check
Coupon UID via special form. When
pass: provide the discount and
automatically link Reseller ID to
Coupon UID; reject in other case
•Owner: MKT
•Observer: •Fields: Resellers
•Description: Reseller ID should be
linked to Installer ID in CRM
Company Card (1:N). Coupon ID
should be stored for UID controlling
•Owner: MKT
•Observer: Sales, Presales
•Fields: •Description: Historical data should
be able for internal analysis

2. Coupon Lifecycle | Release

• Description: Coupon is an UID that can be used to receive additional resources through
official Dahua sales chain in pre-determined period. Coupon release policy is under
Marketing control, it can be adjust by the options list.
• Fields:
• UID: unique ID, should be generated automatically by Bitrix24 platform. It contains Latin
characters and Arabic numbers.
• Options: adjustable object that contains Coupon values (will be extended in future):
Expiration: expiration date, set to Utilize automatically, mandatory
Product type: set limitations by official product groups, optional
Discount: price-off, percentage, optional
Amount: price-off, RUB, optional
Limit: min-max amount range for using, optional
Activation: activation date, empty when release, mandatory
• Release process requirements:
• Access should be limited
• Owner can adjust Options and set Coupons quantity

3. Coupon Lifecycle | Send to Installer

• Description: Coupon can be sent to target person (CRM Contact) manually
or automatically (in batch) by available channels (email in the current step).
When Coupon was successfully send to Installer, it should be automatically
bind to CRM Company card, linking one coupon to multiple Installers
should not be possible. One CRM Company card can takes more that one
Coupon.
• Fields:
• Installer UID: CRM Object – Company card
• Sending process requirements:
• Single and batch sending
• Adjustable channels
• Errors handling

4. Coupon Lifecycle | Use by Reseller

• Description: The solution should provide an interface for Reseller for
Coupon UID checking. Easy form with controllable access should takes
Coupon ID and returns checking results. One-time coupon using.
• Fields:
• Reseller UID: CRM Object – Company card
• Sending process requirements:
• Reseller account control
• Checking results feedback in the same window, single error stile in the front-side
• If success – lock coupon and bind it to Reseller
• Brute-force protection
• Email push to Reseller and Reseller Owner

5. Coupon Lifecycle | Utilize

• Description: The platform should automatically bind Installer to
Reseller in CRM Card. One Installer can be binned to many Resellers
• Fields:
• Resellers: CRM Object – Company card
• Utilize process requirements:
• Fully automated
• Using flag changing

6. Coupon Lifecycle | Report

• Description: Coupons List should support search and filtering by
Fields and Options. It should support one-click operations for manual
Utilize.
• Fields:
•-
• Utilize process requirements:
• Single and batch one-click operations
• Filters by any field
• Coupon re-use protection