Installing the MoveData Commerce Extensions

The MoveData Commerce Extensions enable the processing of Sale notifications into Salesforce. Supported platforms are:

Platform	Functionality
Raisely	Tickets
Funraisin	Registrations Merchandise Raffles

Demonstration

The following is a demonstration of MoveData processing a ticket sale from Raisely into Salesforce. All other Platform integrations work in a similar manner.

Step 1: Install Commerce Extensions

You can install the MoveData Commerce Extensions at https://api.movedata.io/installer/commerce-extension.

Step 2: Activate Standard Price Book

You then need to activate the Standard Price Book. You can find this by opening Price Books from the App Launcher and ensuring Active is set to True.

Step 3: Replicate Settings

You then need to configure your Settings for the MoveData Commerce Extensions. You can access these by opening MoveData from the App Launcher and navigating to Settings → Commerce. In most cases you will replicate settings from Fundraising & Donations.

Step 4: Replicate Metadata Entries

The MoveData Commerce Extensions contain their own set of Flows and therefore their own Metadata entries under Setup → Custom Metadata → MoveData Pipeline. If you have developed custom Flows for your MoveData integration, then you will also need to register them under Custom Metadata → MoveData Pipeline.

The only fundamental difference between your Fundraising & Donation and Commerce entries is that DONATION will be replaced with COMMERCE for your Label (optional) and MoveData Pipeline Setting Name (mandatory). This ensures your entry is registered when the MoveData Commerce Extensions run as detailed in the example below:

Field	Fundraising & Donations Entry	Commerce Entry
Handler	`MoveData_Donation_Contact_Mapping_Ext`	`MoveData_Donation_Contact_Mapping_Ext`
Type	Flow	Flow
Label	`PIPELINE_DONATION_CONTACT_MAPPING`	`PIPELINE_COMMERCE_CONTACT_MAPPING`
MoveData Pipeline Setting Name	`DONATION_CONTACT_MAPPING_EXT`	`COMMERCE_CONTACT_MAPPING_EXT`
Order	6	6

In general:

PIPELINE_DONATION_ACCOUNT entries are to be registered under PIPELINE_COMMERCE_ACCOUNT
PIPELINE_DONATION_CAMPAIGN entries are to be registered under PIPELINE_COMMERCE_CAMPAIGN
PIPELINE_DONATION_CONTACT entries are to be registered under PIPELINE_COMMERCE_CONTACT
PIPELINE_DONATION_DONATION entries are to be registered under PIPELINE_COMMERCE_DONATION
- PIPELINE_DONATION_DONATION_POST are to be registered under PIPELINE_COMMERCE_ORDER_FINAL
PIPELINE_DONATION_RECURRING entries do not need to be registered given PIPELINE COMMERCE has no equivalent concept

Step 5: Enable in Integration

You can then enable the processing of Commerce notifications within your Integration.

Raisely

Processor Version	Select `V2: Donation and Tickets`
[V2 Only] Fee Allocation Method	In the case of transactions which comprise Sale and Donation, specify if the Fee is to be allocated to the Sale Opportunity, Donation Opportunity, or split evenly across each
Aggregate Order Line Items	Aggregates multiple "same" Line Items into a single Opportunity Product (e.g. `2 x Adult` versus `1 x Adult, 1 x Adult`). Set to `Retain Individual Order Lines` if you wish to write contextual information to each Opportunity Product.
Remove Discounts	Includes or excludes Discounts as Opportunity Products

Funraisin

Disable Product Sales	Set to `Process Product Sales` to process Sale and Raffle information into Salesforce
Disable Registrations	Set to `Process Registrations` to process Registration information into Salesforce

Step 6: Review Resulting Records

You can now process a Sale in your connected platform and it will be processed into Salesforce.

Flow Customisation Tips for Commerce

Occasionally you may need to implement Commerce-specific logic. For instance, you may wish to set a different Opportunity Record Type for ticket sales as opposed to donations. To achieve this, you can decision on the variable Schema and nest your Commerce-specific logic under a value of commerce.
Enable Products on your Opportunity Page Layout
Line Items on your Sale (for example Adult versus Child or Hat versus T-Shirt) are processed under the PIPELINE_COMMERCE_ORDERITEM Custom Metadata → MoveData Pipeline entries. If you wish to map specific Line Item data over to Opportunity Products, we recommend creating an Extension Flow which runs in line with [MoveData] Commerce: Order Item - Mapping. This can be registered as an addition to PIPELINE_COMMERCE_ORDERITEM_MAPPING under Custom Metadata → MoveData Pipeline.