Distribution Relationship Management
Implementation Information

This page is the design detail document for your project and acts as the technology blueprint. It provides precise details on the architecture of the system for your programmers along with feature specifications for the solution. The implementation responsibilities of the Brand, the shopping cart provider, and Reshare are documented along with expected timeframes and best practices. At the end of this page, you will be asked to acknowledge your agreement that the design is understood and that you are prepared to deliver in your areas of responsibility.

Below is a basic example of how a DRM enabled cart works:

For this process to work, the shopping cart and DRM need to “know” certain things. DRM requires that the Brand business rules are finalized, the distribution channel structure is defined and that complete lists of distributors, dealers, retailers or other intermediaries (“channel partner”) are loaded. The shopping cart needs to be programmed to accept the web service information (WSDLs), instructed what to do with the DRM ID (an identification number assigned by DRM for each channel partner) that it receives from the web service, and how to send emails to consumers, channel partners and the Brand the Brand upon order confirmation.

Steps that are taken to achieve the above are as follows:

1. The Brand has a business rules discussion with Reshare that establishes channel partner levels, channel partner selection rules, channel remuneration schema, reporting, payout schedules and more. These business rules will guide deployment. The Brand also provides Reshare with logo graphics in .jpg format for integration into DRM.
   
   
2. The Brand provides an initial and accurate channel partner list to Reshare for bulk insert into DRM.
   
   
3. Based on business rules, Reshare configures channel layers within DRM and activates it on the Reshare application server.
   
   
4. The shopping cart provider uses the WSDL information to consume both the channel partner selector and the transaction insert (sales line item information for each line that is completed) web services.
   
   
5. The Brand crafts the language for the completed sale email that the shopping cart sends to the Brand, selected channel partners and purchaser/consumer. The cart developer implements this feature.
   
   
6. Test transactions are run to ensure everything is ready. Reshare delivers a user manual and training. We go live.

_______________________________________________________________________

Below are links to helpful sections of our implementation section:

Cart Specific DRM Implementation

Brand Specific DRM Implementation