Additional Notes on Reseller Synchronization

There are possible edge-case scenarios a reseller may run into. Consider the following examples:

  1. The provider updated a delegated service plan, and synchronized it to direct resellers (propagated it to L1 resellers but changes did not affect L2 sub-resellers). In this case, the L1 resellers will see a special warning displayed at the list of their service plans – "The plan was changed but the changes were not propagated to sub-resellers".
  2. The provider added a new subscription period (or resource rates, or resource rate periods) with some dummy (invalid) fees/prices. The reseller has both "Disable prices synchronization" option enabled, and it is supposed that he or she manages the prices himself (herself). During synchronization, the reseller will receive the subscription periods (or resource rates/resource rate periods) with invalid prices that would immediately appear in their online store, which would be unacceptable. To handle this situation, such delegated plans will be removed from all "markets" (interfaces where they can be purchased, such as CCP v1, UX1 for Customers, and online store) of that reseller. In RCP, such plans will be displayed with the mark "Delegated confirmation needed". To get these plans back into production, the reseller needs to review the changes and confirm them.