Nonprofit Cloud extension metadata reference

This reference documents the custom metadata entries (movedata__Movedata_Pipeline__mdt) that configure the Donation Pipeline and Commerce Pipeline for Nonprofit Cloud implementations.

Extension configuration#

Extension registration#

The NPC Extension is registered through two core metadata entries that identify the extension namespace and enable NPC-specific processing.

Extension namespace#

Metadata entry: EXTENSION_DONATION_NAMESPACE

Field	Value
Label	`EXTENSION_DONATION_NAMESPACE`
Handler	`md_npc_pack`
Order	5
Type	`Config`

Purpose: Identifies the package namespace for all NPC Extension components. This namespace prefix (md_npc_pack) is used throughout the configuration to reference flows, fieldsets, and other extension resources.

Extension mode#

Metadata entry: EXTENSION_DONATION_NPC

Field	Value
Label	`EXTENSION_NPC`
Handler	`true`
Order	5
Type	`Config`

Purpose: Activates Nonprofit Cloud-specific processing logic. When enabled, the pipeline uses NPC data models (GiftTransaction, GiftCommitment) instead of NPSP models (Opportunity, Recurring Donation).

Pipeline schema registration#

Donation schema#

Metadata entry: movedata__Movedata_Schema_Map__mdt.donation

Field	Value
MasterLabel	`donation`
Handler	`MoveDataDonationPipeline`
Version	1
Type	`Apex`

Purpose: Registers the Donation Pipeline to process notifications using the donation schema. This is the primary entry point that routes donation notifications to the multi-stage processing engine.

Commerce schema#

Metadata entry: movedata__Movedata_Schema_Map__mdt.commerce

Field	Value
MasterLabel	`commerce`
Handler	`MoveDataCommercePipeline`
Version	1
Type	`Apex`

Purpose: Registers the Commerce Pipeline for processing e-commerce and merchandise transactions through the NPC Extension.

Donation pipeline configuration#

Stage 1: Account processing#

The Account stage creates or updates Account records for organisational donors, matched gift companies, and fundraising organisations. In NPC implementations, accounts may be configured as person accounts for individual donors.

Account disable#

Metadata entry: DONATION_ACCOUNT_DISABLE

Field	Value
Label	`PIPELINE_DONATION_ACCOUNT_DISABLE`
Handler	`false`
Order	5
Type	`Config`

Purpose: Controls whether account processing is enabled. Set to false by default, meaning account processing is active. Change to true to bypass account creation/updates entirely.

Account fieldset#

Metadata entry: DONATION_ACCOUNT_FIELDSET_001

Field	Value
Label	`PIPELINE_DONATION_ACCOUNT_FIELDSET`
Handler	`md_npc_pack__MoveData_Donation_Account_Fieldset`
Type	`Fieldset`

Purpose: Specifies the fieldset that defines which Account fields should be loaded when existing account records are located during duplicate matching. This ensures all necessary fields are available for mapping and comparison operations.

Account platform key#

Metadata entry: DONATION_ACCOUNT_PLATFORM_KEY_001

Field	Value
Label	`PIPELINE_DONATION_ACCOUNT_PLATFORM_KEY`
Handler	`md_npc_pack.MoveData_Donation_Account_Key`
Order	5
Type	`Flow`

Purpose: Lightning Flow that generates the unique platform identifier used to track account records across systems. This key enables reliable duplicate detection and maintains data lineage from fundraising platforms.

Flow: md_npc_pack.MoveData_Donation_Account_Key

Account duplicate detection#

Metadata entry: DONATION_ACCOUNT_DUPLICATE_001

Field	Value
Label	`PIPELINE_DONATION_ACCOUNT_DUPLICATE`
Handler	`md_npc_pack.MoveData_Donation_Account_Duplicate`
Order	5
Type	`Flow`

Purpose: Lightning Flow that implements duplicate matching logic to locate existing account records before creating new ones. Prevents duplicate account creation by checking platform keys, external IDs, and other matching criteria.

Flow: md_npc_pack.MoveData_Donation_Account_Duplicate

Account field mapping#

Metadata entry: DONATION_ACCOUNT_MAPPING_001

Field	Value
Label	`PIPELINE_DONATION_ACCOUNT_MAPPING`
Handler	`md_npc_pack.MoveData_Donation_Account_Mapping`
Order	5
Type	`Flow`

Purpose: Primary Lightning Flow that maps notification data to Account fields. Handles standard field mappings including organisation name, address information, and account type classifications.

Flow: md_npc_pack.MoveData_Donation_Account_Mapping

Account post-processing#

Metadata entry: DONATION_ACCOUNT_POST_001

Field	Value
Label	`PIPELINE_DONATION_ACCOUNT_POST`
Handler	`md_npc_pack.MoveData_Donation_Account_Post`
Order	5
Type	`Flow`

Purpose: Lightning Flow that executes after account records are created or updated. Handles post-upsert operations such as relationship creation, additional record updates, or triggering downstream processes.

Flow: md_npc_pack.MoveData_Donation_Account_Post

Stage 2: Contact processing#

The Contact stage creates or updates Contact records for individual donors, fundraisers, and tribute contacts. In Nonprofit Cloud implementations using person accounts, this stage is configured to process Account records instead of Contact records.

Contact disable#

Metadata entry: DONATION_CONTACT_DISABLE

Field	Value
Label	`PIPELINE_DONATION_CONTACT_DISABLE`
Handler	`false`
Order	5
Type	`Config`

Purpose: Controls whether contact processing is enabled. Set to false by default for active processing.

Contact SObject override#

Metadata entry: DONATION_CONTACT_SOBJECT

Field	Value
Label	`PIPELINE_DONATION_CONTACT_SOBJECT`
Handler	`Account`
Order	5
Type	`Config`

Critical for NPC implementations

This entry overrides the default Contact object with Account to support person account processing. When set to Account, the pipeline treats individual donors as person accounts rather than traditional Contacts, aligning with Nonprofit Cloud's person account model.

Contact fieldset#

Metadata entry: DONATION_CONTACT_FIELDSET_001

Field	Value
Label	`PIPELINE_DONATION_CONTACT_FIELDSET`
Handler	`md_npc_pack__MoveData_Donation_Contact_Fieldset`
Type	`Fieldset`

Purpose: Defines which fields should be loaded when existing contact/person account records are located. In person account scenarios, this fieldset includes both standard Contact fields and Account-specific fields.

Contact platform key#

Metadata entry: DONATION_CONTACT_PLATFORM_KEY_001

Field	Value
Label	`PIPELINE_DONATION_CONTACT_PLATFORM_KEY`
Handler	`md_npc_pack.MoveData_Donation_Contact_Key`
Order	5
Type	`Flow`

Purpose: Generates unique platform identifiers for contact/person account records to enable cross-system tracking and duplicate prevention.

Flow: md_npc_pack.MoveData_Donation_Contact_Key

Contact duplicate detection#

Metadata entry: DONATION_CONTACT_DUPLICATE_001

Field	Value
Label	`PIPELINE_DONATION_CONTACT_DUPLICATE`
Handler	`md_npc_pack.MoveData_Donation_Contact_Duplicate`
Order	5
Type	`Flow`

Purpose: Implements duplicate matching logic for contacts/person accounts using email, name matching, and platform keys.

Flow: md_npc_pack.MoveData_Donation_Contact_Duplicate

Contact field mapping#

Metadata entry: DONATION_CONTACT_MAPPING_001

Field	Value
Label	`PIPELINE_DONATION_CONTACT_MAPPING`
Handler	`md_npc_pack.MoveData_Donation_Contact_Mapping`
Order	5
Type	`Flow`

Purpose: Maps notification data to Contact or person Account fields including names, contact information, and donor classifications.

Flow: md_npc_pack.MoveData_Donation_Contact_Mapping

Contact post-processing#

Metadata entry: DONATION_CONTACT_POST_001

Field	Value
Label	`PIPELINE_DONATION_CONTACT_POST`
Handler	`md_npc_pack.MoveData_Donation_Contact_Post`
Order	5
Type	`Flow`

Purpose: Executes post-upsert operations for contact/person account records.

Flow: md_npc_pack.MoveData_Donation_Contact_Post

Stage 3: Campaign processing#

The Campaign stage creates or updates Campaign records representing fundraising initiatives, peer-to-peer campaigns, and campaign hierarchies.

Campaign disable#

Metadata entry: DONATION_CAMPAIGN_DISABLE

Field	Value
Label	`PIPELINE_DONATION_CAMPAIGN_DISABLE`
Handler	`false`
Order	5
Type	`Config`

Purpose: Controls campaign processing. Set to false for active processing.

Campaign fieldset#

Metadata entry: DONATION_CAMPAIGN_FIELDSET_001

Field	Value
Label	`PIPELINE_DONATION_CAMPAIGN_FIELDSET`
Handler	`md_npc_pack__MoveData_Donation_Campaign_Fieldset`
Type	`Fieldset`

Purpose: Defines Campaign fields to load during duplicate matching and processing.

Campaign platform key#

Metadata entry: DONATION_CAMPAIGN_PLATFORM_KEY_001

Field	Value
Label	`PIPELINE_DONATION_CAMPAIGN_PLATFORM_KEY`
Handler	`md_npc_pack.MoveData_Donation_Campaign_Key`
Order	5
Type	`Flow`

Purpose: Generates unique platform identifiers for campaign records.

Flow: md_npc_pack.MoveData_Donation_Campaign_Key

Campaign name generation#

Metadata entry: DONATION_CAMPAIGN_NAME_001

Field	Value
Label	`PIPELINE_DONATION_CAMPAIGN_NAME`
Handler	`md_npc_pack.MoveData_Donation_Campaign_Name`
Order	5
Type	`Flow`

Purpose: Custom campaign name generation logic that can construct campaign names based on notification data, hierarchies, or naming conventions.

Flow: md_npc_pack.MoveData_Donation_Campaign_Name

Campaign duplicate detection#

Metadata entry: DONATION_CAMPAIGN_DUPLICATE_001

Field	Value
Label	`PIPELINE_DONATION_CAMPAIGN_DUPLICATE`
Handler	`md_npc_pack.MoveData_Donation_Campaign_Duplicate`
Order	5
Type	`Flow`

Purpose: Locates existing campaign records using platform keys and name matching to prevent duplicates.

Flow: md_npc_pack.MoveData_Donation_Campaign_Duplicate

Campaign field mapping#

Metadata entry: DONATION_CAMPAIGN_MAPPING_001

Field	Value
Label	`PIPELINE_DONATION_CAMPAIGN_MAPPING`
Handler	`md_npc_pack.MoveData_Donation_Campaign_Mapping`
Order	5
Type	`Flow`

Purpose: Maps notification data to Campaign fields including campaign type, goals, dates, and hierarchy relationships.

Flow: md_npc_pack.MoveData_Donation_Campaign_Mapping

Campaign post-processing#

Metadata entry: DONATION_CAMPAIGN_POST_001

Field	Value
Label	`PIPELINE_DONATION_CAMPAIGN_POST`
Handler	`md_npc_pack.MoveData_Donation_Campaign_Post`
Order	5
Type	`Flow`

Purpose: Handles post-upsert operations for campaigns including parent-child campaign linking and campaign member creation.

Flow: md_npc_pack.MoveData_Donation_Campaign_Post

Stage 4: Recurring donation processing#

The Recurring Donation stage creates or updates recurring gift records. In Nonprofit Cloud, this stage processes GiftCommitment objects which represent ongoing, scheduled giving arrangements.

Recurring disable#

Metadata entry: DONATION_RECURRING_DISABLE

Field	Value
Label	`PIPELINE_DONATION_RECURRING_DISABLE`
Handler	`false`
Order	5
Type	`Config`

Purpose: Controls recurring donation processing. Set to true to disable processing.

Recurring SObject override#

Metadata entry: DONATION_RECURRING_SOBJECT

Field	Value
Label	`PIPELINE_DONATION_RECURRING_SOBJECT`
Handler	`GiftCommitment`
Order	5
Type	`Config`

Critical for NPC implementations

This entry sets the SObject type to GiftCommitment, the Nonprofit Cloud standard object for recurring donations. This overrides the NPSP npe03__Recurring_Donation__c object.

Recurring fieldset#

Metadata entry: DONATION_RECURRING_FIELDSET_001

Field	Value
Label	`PIPELINE_DONATION_RECURRING_FIELDSET`
Handler	`md_npc_pack__MoveData_Donation_Recurring_Fieldset`
Type	`Fieldset`

Purpose: Defines GiftCommitment fields to load during processing.

Recurring platform key#

Metadata entry: DONATION_RECURRING_PLATFORM_KEY_001

Field	Value
Label	`PIPELINE_DONATION_RECURRING_PLATFORM_KEY`
Handler	`md_npc_pack.MoveData_Donation_Recurring_Key`
Order	5
Type	`Flow`

Purpose: Generates unique platform identifiers for recurring donation records.

Flow: md_npc_pack.MoveData_Donation_Recurring_Key

Recurring duplicate detection#

Metadata entry: DONATION_RECURRING_DUPLICATE_001

Field	Value
Label	`PIPELINE_DONATION_RECURRING_DUPLICATE`
Handler	`md_npc_pack.MoveData_Donation_Recurring_Duplicate`
Order	5
Type	`Flow`

Purpose: Locates existing GiftCommitment records to prevent duplicate recurring donation creation.

Flow: md_npc_pack.MoveData_Donation_Recurring_Duplicate

Recurring field mapping#

Metadata entry: DONATION_RECURRING_MAPPING_001

Field	Value
Label	`PIPELINE_DONATION_RECURRING_MAPPING`
Handler	`md_npc_pack.MoveData_Donation_Recurring_Mapping`
Order	5
Type	`Flow`

Purpose: Maps notification data to GiftCommitment fields including recurring frequency, amount, status, and schedule information.

Flow: md_npc_pack.MoveData_Donation_Recurring_Mapping

Recurring post-processing#

Metadata entry: DONATION_RECURRING_POST_001

Field	Value
Label	`PIPELINE_DONATION_RECURRING_POST`
Handler	`md_npc_pack.MoveData_Donation_Recurring_Post`
Order	5
Type	`Flow`

Purpose: Executes post-upsert operations for recurring donations including schedule creation and donor relationship management.

Flow: md_npc_pack.MoveData_Donation_Recurring_Post

Stage 5: Donation processing#

The Donation stage creates or updates individual donation transaction records. In Nonprofit Cloud, this stage processes GiftTransaction objects which represent individual monetary gifts.

Donation platform key#

Metadata entry: DONATION_DONATION_PLATFORM_KEY_001

Field	Value
Label	`PIPELINE_DONATION_DONATION_PLATFORM_KEY`
Handler	`md_npc_pack.MoveData_Donation_Donation_Key`
Order	5
Type	`Flow`

Purpose: Generates unique platform identifiers for donation transaction records.

Flow: md_npc_pack.MoveData_Donation_Donation_Key

Donation fieldset#

Metadata entry: DONATION_DONATION_FIELDSET_001

Field	Value
Label	`PIPELINE_DONATION_DONATION_FIELDSET`
Handler	`md_npc_pack__MoveData_Donation_Donation_Fieldset`
Type	`Fieldset`

Purpose: Defines GiftTransaction fields to load during processing.

Donation duplicate detection#

Metadata entry: DONATION_DONATION_DUPLICATE_001

Field	Value
Label	`PIPELINE_DONATION_DONATION_DUPLICATE`
Handler	`md_npc_pack.MoveData_Donation_Donation_Duplicate`
Order	5
Type	`Flow`

Purpose: Locates existing GiftTransaction records to prevent duplicate donation creation using platform keys and transaction identifiers.

Flow: md_npc_pack.MoveData_Donation_Donation_Duplicate

Donation field mapping#

Metadata entry: DONATION_DONATION_MAPPING_001

Field	Value
Label	`PIPELINE_DONATION_DONATION_MAPPING`
Handler	`md_npc_pack.MoveData_Donation_Donation_Mapping`
Order	5
Type	`Flow`

Purpose: Maps notification data to GiftTransaction fields including amount, date, payment method, designation, and tribute information.

Flow: md_npc_pack.MoveData_Donation_Donation_Mapping

Donation post-processing#

Metadata entry: DONATION_DONATION_POST_001

Field	Value
Label	`PIPELINE_DONATION_DONATION_POST`
Handler	`md_npc_pack.MoveData_Donation_Donation_Post`
Order	5
Type	`Flow`

Purpose: Executes post-upsert operations for donation records including acknowledgment processing, tax receipt generation, and campaign member updates.

Flow: md_npc_pack.MoveData_Donation_Donation_Post

Commerce pipeline configuration#

The Commerce Pipeline processes e-commerce transactions, product catalog management, and order fulfilment. Like the Donation Pipeline, it follows a multi-stage architecture but is optimised for merchandise sales, event registrations, and other commercial transactions.

Commerce pipeline architecture#

The Commerce Pipeline operates through seven distinct stages:

Configuration — Pipeline configuration and setup
Preprocess — Pre-processing transformations (optional)
Account — Customer account management
Contact — Customer contact/person account management
Campaign — Marketing campaign association
Catalog — Product catalog management
Order — Order header processing
Order Item — Individual line item processing

Extension configuration#

Commerce extension namespace#

Metadata entry: EXTENSION_COMMERCE_NAMESPACE

Field	Value
Label	`EXTENSION_COMMERCE_NAMESPACE`
Handler	`md_npc_pack`
Order	5
Type	`Config`

Purpose: Identifies the package namespace for Commerce Pipeline components. Uses the same md_npc_pack namespace as the Donation Pipeline.

Commerce extension mode#

Metadata entry: EXTENSION_COMMERCE_MODE

Field	Value
Label	`EXTENSION_COMMERCE_MODE`
Handler	`single_step` or `multi_step`
Order	5
Type	`Config`

Purpose: Controls the commerce processing mode. When set to single_step, all commerce processing occurs in a single flow. When set to multi_step (default), the pipeline executes through all seven stages sequentially.

Stage 0: Configuration#

Metadata key: PIPELINE_COMMERCE_CONFIGURATION

Purpose: Enables configuration flows that set conditional values or advanced settings not exposed through the Settings interface. Configuration flows execute before all other stages.

Stage 1: Pre-processing#

Metadata key: PIPELINE_COMMERCE_PREPROCESS

Purpose: Allows transformation or enhancement of commerce notifications before main processing begins. Common use cases include:

Notification transformation or enrichment
Conditional routing logic
Data validation and cleansing

Stage 2: Commerce account processing#

Creates or updates Account records for commerce customers and organisations.

Commerce account disable#

Metadata entry: COMMERCE_ACCOUNT_DISABLE

Field	Value
Label	`PIPELINE_COMMERCE_ACCOUNT_DISABLE`
Handler	`false`
Order	5
Type	`Config`

Purpose: Controls whether commerce account processing is enabled. Default is false (enabled).

Commerce account fieldset#

Metadata entry: COMMERCE_ACCOUNT_FIELDSET_001

Field	Value
Label	`PIPELINE_COMMERCE_ACCOUNT_FIELDSET`
Handler	`md_npc_pack__MoveData_Donation_Account_Fieldset`
Type	`Fieldset`

Purpose: Defines Account fields to load during duplicate matching. Reuses the donation account fieldset for consistency.

Commerce account platform key#

Metadata entry: COMMERCE_ACCOUNT_PLATFORM_KEY_001

Field	Value
Label	`PIPELINE_COMMERCE_ACCOUNT_PLATFORM_KEY`
Handler	`md_npc_pack.MoveData_Donation_Account_Key`
Order	5
Type	`Flow`

Purpose: Generates unique platform identifiers for commerce customer accounts.

Flow: md_npc_pack.MoveData_Donation_Account_Key

Commerce account field mapping#

Metadata entry: COMMERCE_ACCOUNT_MAPPING_001

Field	Value
Label	`PIPELINE_COMMERCE_ACCOUNT_MAPPING`
Handler	`md_npc_pack.MoveData_Donation_Account_Mapping`
Order	5
Type	`Flow`

Purpose: Maps commerce notification data to Account fields for customer organisations.

Flow: md_npc_pack.MoveData_Donation_Account_Mapping

Commerce account duplicate detection#

Metadata entry: COMMERCE_ACCOUNT_DUPLICATE_001

Field	Value
Label	`PIPELINE_COMMERCE_ACCOUNT_DUPLICATE`
Handler	`md_npc_pack.MoveData_Donation_Account_Duplicate`
Order	5
Type	`Flow`

Purpose: Locates existing customer account records to prevent duplicates.

Flow: md_npc_pack.MoveData_Donation_Account_Duplicate

Commerce account post-processing#

Metadata entry: COMMERCE_ACCOUNT_POST_001

Field	Value
Label	`PIPELINE_COMMERCE_ACCOUNT_POST`
Handler	`md_npc_pack.MoveData_Donation_Account_Post`
Order	5
Type	`Flow`

Purpose: Executes post-upsert operations for commerce customer accounts.

Flow: md_npc_pack.MoveData_Donation_Account_Post

Stage 3: Commerce contact processing#

Creates or updates Contact records (or person Accounts) for individual customers.

Commerce contact disable#

Metadata entry: COMMERCE_CONTACT_DISABLE

Field	Value
Label	`PIPELINE_COMMERCE_CONTACT_DISABLE`
Handler	`false`
Order	5
Type	`Config`

Purpose: Controls commerce contact processing. Default is false (enabled).

Commerce contact SObject override#

Metadata entry: COMMERCE_CONTACT_SOBJECT

Field	Value
Label	`PIPELINE_COMMERCE_CONTACT_SOBJECT`
Handler	`Account`
Order	5
Type	`Config`

Critical for NPC implementations

This entry overrides the default Contact object with Account to support person account processing for individual customers.

Commerce contact fieldset#

Metadata entry: COMMERCE_CONTACT_FIELDSET_001

Field	Value
Label	`PIPELINE_COMMERCE_CONTACT_FIELDSET`
Handler	`md_npc_pack__MoveData_Donation_Contact_Fieldset`
Type	`Fieldset`

Purpose: Defines fields to load for customer contact/person account records.

Commerce contact platform key#

Metadata entry: COMMERCE_CONTACT_PLATFORM_KEY_001

Field	Value
Label	`PIPELINE_COMMERCE_CONTACT_PLATFORM_KEY`
Handler	`md_npc_pack.MoveData_Donation_Contact_Key`
Order	5
Type	`Flow`

Purpose: Generates unique platform identifiers for customer contacts.

Flow: md_npc_pack.MoveData_Donation_Contact_Key

Commerce contact field mapping#

Metadata entry: COMMERCE_CONTACT_MAPPING_001

Field	Value
Label	`PIPELINE_COMMERCE_CONTACT_MAPPING`
Handler	`md_npc_pack.MoveData_Donation_Contact_Mapping`
Order	5
Type	`Flow`

Purpose: Maps commerce notification data to customer Contact/person Account fields.

Flow: md_npc_pack.MoveData_Donation_Contact_Mapping

Commerce contact duplicate detection#

Metadata entry: COMMERCE_CONTACT_DUPLICATE_001

Field	Value
Label	`PIPELINE_COMMERCE_CONTACT_DUPLICATE`
Handler	`md_npc_pack.MoveData_Donation_Contact_Duplicate`
Order	5
Type	`Flow`

Purpose: Locates existing customer contact records to prevent duplicates.

Flow: md_npc_pack.MoveData_Donation_Contact_Duplicate

Commerce contact post-processing#

Metadata entry: COMMERCE_CONTACT_POST_001

Field	Value
Label	`PIPELINE_COMMERCE_CONTACT_POST`
Handler	`md_npc_pack.MoveData_Donation_Contact_Post`
Order	5
Type	`Flow`

Purpose: Executes post-upsert operations for customer contacts.

Flow: md_npc_pack.MoveData_Donation_Contact_Post

Stage 4: Commerce campaign processing#

Associates commerce transactions with marketing campaigns.

Commerce campaign disable#

Metadata entry: COMMERCE_CAMPAIGN_DISABLE

Field	Value
Label	`PIPELINE_COMMERCE_CAMPAIGN_DISABLE`
Handler	`false`
Order	5
Type	`Config`

Purpose: Controls commerce campaign processing. Default is false (enabled).

Commerce campaign fieldset#

Metadata entry: COMMERCE_CAMPAIGN_FIELDSET_001

Field	Value
Label	`PIPELINE_COMMERCE_CAMPAIGN_FIELDSET`
Handler	`md_npc_pack__MoveData_Donation_Campaign_Fieldset`
Type	`Fieldset`

Purpose: Defines Campaign fields to load for commerce campaigns.

Commerce campaign platform key#

Metadata entry: COMMERCE_CAMPAIGN_PLATFORM_KEY_001

Field	Value
Label	`PIPELINE_COMMERCE_CAMPAIGN_PLATFORM_KEY`
Handler	`md_npc_pack.MoveData_Donation_Campaign_Key`
Order	5
Type	`Flow`

Purpose: Generates unique platform identifiers for commerce campaigns.

Flow: md_npc_pack.MoveData_Donation_Campaign_Key

Commerce campaign name generation#

Metadata entry: COMMERCE_CAMPAIGN_NAME_001

Field	Value
Label	`PIPELINE_COMMERCE_CAMPAIGN_NAME`
Handler	`md_npc_pack.MoveData_Donation_Campaign_Name`
Order	5
Type	`Flow`

Purpose: Generates campaign names for commerce-related campaigns.

Flow: md_npc_pack.MoveData_Donation_Campaign_Name

Commerce campaign field mapping#

Metadata entry: COMMERCE_CAMPAIGN_MAPPING_001

Field	Value
Label	`PIPELINE_COMMERCE_CAMPAIGN_MAPPING`
Handler	`md_npc_pack.MoveData_Donation_Campaign_Mapping`
Order	5
Type	`Flow`

Purpose: Maps commerce notification data to Campaign fields.

Flow: md_npc_pack.MoveData_Donation_Campaign_Mapping

Commerce campaign duplicate detection#

Metadata entry: COMMERCE_CAMPAIGN_DUPLICATE_001

Field	Value
Label	`PIPELINE_COMMERCE_CAMPAIGN_DUPLICATE`
Handler	`md_npc_pack.MoveData_Donation_Campaign_Duplicate`
Order	5
Type	`Flow`

Purpose: Locates existing campaign records for commerce transactions.

Flow: md_npc_pack.MoveData_Donation_Campaign_Duplicate

Commerce campaign post-processing#

Metadata entry: COMMERCE_CAMPAIGN_POST_001

Field	Value
Label	`PIPELINE_COMMERCE_CAMPAIGN_POST`
Handler	`md_npc_pack.MoveData_Donation_Campaign_Post`
Order	5
Type	`Flow`

Purpose: Executes post-upsert operations for commerce campaigns.

Flow: md_npc_pack.MoveData_Donation_Campaign_Post

Stage 5: Product catalog processing#

Manages product records and catalog information.

Catalog disable#

Metadata entry: COMMERCE_CATALOG_DISABLE

Field	Value
Label	`PIPELINE_COMMERCE_CATALOG_DISABLE`
Handler	`false`
Order	5
Type	`Config`

Purpose: Controls product catalog processing. Default is false (enabled).

Catalog SObject override#

Metadata entry: COMMERCE_CATALOG_SOBJECT

Field	Value
Label	`PIPELINE_COMMERCE_CATALOG_SOBJECT`
Handler	Custom product object name
Order	5
Type	`Config`

Purpose: Allows override of the default product SObject type. Can be used to specify custom product objects or alternate catalog structures.

Catalog fieldset#

Metadata entry: COMMERCE_CATALOG_FIELDSET_001

Field	Value
Label	`PIPELINE_COMMERCE_CATALOG_FIELDSET`
Handler	`md_npc_pack__MoveData_Commerce_Product_Fieldset`
Type	`Fieldset`

Purpose: Defines product fields to load during catalog processing.

Catalog platform key#

Metadata entry: COMMERCE_CATALOG_PLATFORM_KEY_001

Field	Value
Label	`PIPELINE_COMMERCE_CATALOG_PLATFORM_KEY`
Handler	`md_npc_pack.MoveData_Commerce_Catalog_Key`
Order	5
Type	`Flow`

Purpose: Generates unique platform identifiers for product catalog items.

Flow: md_npc_pack.MoveData_Commerce_Catalog_Key

Catalog name generation#

Metadata entry: COMMERCE_CATALOG_NAME_001

Field	Value
Label	`PIPELINE_COMMERCE_CATALOG_NAME`
Handler	`md_npc_pack.MoveData_Commerce_Catalog_Name`
Order	5
Type	`Flow`

Purpose: Generates product names and handles product naming conventions.

Flow: md_npc_pack.MoveData_Commerce_Catalog_Name

Catalog field mapping#

Metadata entry: COMMERCE_CATALOG_MAPPING_001

Field	Value
Label	`PIPELINE_COMMERCE_CATALOG_MAPPING`
Handler	`md_npc_pack.MoveData_Commerce_Catalog_Mapping`
Order	5
Type	`Flow`

Purpose: Maps commerce notification data to product catalog fields including SKU, description, pricing, and inventory information.

Flow: md_npc_pack.MoveData_Commerce_Catalog_Mapping

Catalog duplicate detection#

Metadata entry: COMMERCE_CATALOG_DUPLICATE_001

Field	Value
Label	`PIPELINE_COMMERCE_CATALOG_DUPLICATE`
Handler	`md_npc_pack.MoveData_Commerce_Catalog_Duplicate`
Order	5
Type	`Flow`

Purpose: Locates existing product records using SKU, platform keys, or other identifiers to prevent duplicate product creation.

Flow: md_npc_pack.MoveData_Commerce_Catalog_Duplicate

Catalog post-processing#

Metadata entry: COMMERCE_CATALOG_POST_001

Field	Value
Label	`PIPELINE_COMMERCE_CATALOG_POST`
Handler	`md_npc_pack.MoveData_Commerce_Catalog_Post`
Order	5
Type	`Flow`

Purpose: Executes post-upsert operations for product catalog records including price book entries and product categorisation.

Flow: md_npc_pack.MoveData_Commerce_Catalog_Post

Stage 6: Order processing#

Manages order header records representing complete customer transactions.

Order disable#

Metadata entry: COMMERCE_ORDER_DISABLE

Field	Value
Label	`PIPELINE_COMMERCE_ORDER_DISABLE`
Handler	`false`
Order	5
Type	`Config`

Purpose: Controls order header processing. Default is false (enabled).

Order SObject override#

Metadata entry: COMMERCE_ORDER_SOBJECT

Field	Value
Label	`PIPELINE_COMMERCE_ORDER_SOBJECT`
Handler	Custom order object name
Order	5
Type	`Config`

Purpose: Allows override of the default Order SObject type for custom order management implementations.

Order fieldset#

Metadata entry: COMMERCE_ORDER_FIELDSET_001

Field	Value
Label	`PIPELINE_COMMERCE_ORDER_FIELDSET`
Handler	`md_npc_pack__MoveData_Commerce_Order_Fieldset`
Type	`Fieldset`

Purpose: Defines Order fields to load during processing.

Order platform key#

Metadata entry: COMMERCE_ORDER_PLATFORM_KEY_001

Field	Value
Label	`PIPELINE_COMMERCE_ORDER_PLATFORM_KEY`
Handler	`md_npc_pack.MoveData_Commerce_Order_Key`
Order	5
Type	`Flow`

Purpose: Generates unique platform identifiers for order records.

Flow: md_npc_pack.MoveData_Commerce_Order_Key

Order name generation#

Metadata entry: COMMERCE_ORDER_NAME_001

Field	Value
Label	`PIPELINE_COMMERCE_ORDER_NAME`
Handler	`md_npc_pack.MoveData_Commerce_Order_Name`
Order	5
Type	`Flow`

Purpose: Generates order numbers and handles order naming conventions.

Flow: md_npc_pack.MoveData_Commerce_Order_Name

Order field mapping#

Metadata entry: COMMERCE_ORDER_MAPPING_001

Field	Value
Label	`PIPELINE_COMMERCE_ORDER_MAPPING`
Handler	`md_npc_pack.MoveData_Commerce_Order_Mapping`
Order	5
Type	`Flow`

Purpose: Maps commerce notification data to Order header fields including totals, status, shipping information, and payment details.

Flow: md_npc_pack.MoveData_Commerce_Order_Mapping

Order duplicate detection#

Metadata entry: COMMERCE_ORDER_DUPLICATE_001

Field	Value
Label	`PIPELINE_COMMERCE_ORDER_DUPLICATE`
Handler	`md_npc_pack.MoveData_Commerce_Order_Duplicate`
Order	5
Type	`Flow`

Purpose: Locates existing order records using platform keys and order numbers to prevent duplicate orders.

Flow: md_npc_pack.MoveData_Commerce_Order_Duplicate

Order post-processing#

Metadata entry: COMMERCE_ORDER_POST_001

Field	Value
Label	`PIPELINE_COMMERCE_ORDER_POST`
Handler	`md_npc_pack.MoveData_Commerce_Order_Post`
Order	5
Type	`Flow`

Purpose: Executes post-upsert operations for order records.

Flow: md_npc_pack.MoveData_Commerce_Order_Post

Order final processing#

Metadata entry: COMMERCE_ORDER_FINAL_001

Field	Value
Label	`PIPELINE_COMMERCE_ORDER_FINAL`
Handler	`md_npc_pack.MoveData_Commerce_Order_Final`
Order	5
Type	`Flow`

Purpose: Executes final order processing after all order items have been processed. This is the last step in the commerce pipeline and handles order-level calculations, status updates, and fulfilment triggers.

Flow: md_npc_pack.MoveData_Commerce_Order_Final

Stage 7: Order item processing#

Manages individual line items within orders, linking products to orders with quantities and pricing.

Order item disable#

Metadata entry: COMMERCE_ORDERITEM_DISABLE

Field	Value
Label	`PIPELINE_COMMERCE_ORDERITEM_DISABLE`
Handler	`false`
Order	5
Type	`Config`

Purpose: Controls order item processing. Default is false (enabled).

Order item SObject override#

Metadata entry: COMMERCE_ORDERITEM_SOBJECT

Field	Value
Label	`PIPELINE_COMMERCE_ORDERITEM_SOBJECT`
Handler	Custom order item object name
Order	5
Type	`Config`

Purpose: Allows override of the default OrderItem SObject type for custom order line item implementations.

Order item fieldset#

Metadata entry: COMMERCE_ORDERITEM_FIELDSET_001

Field	Value
Label	`PIPELINE_COMMERCE_ORDERITEM_FIELDSET`
Handler	`md_npc_pack__MoveData_Commerce_Order_Item_Fieldset`
Type	`Fieldset`

Purpose: Defines OrderItem fields to load during processing.

Order item platform key#

Metadata entry: COMMERCE_ORDERITEM_PLATFORM_KEY_001

Field	Value
Label	`PIPELINE_COMMERCE_ORDERITEM_PLATFORM_KEY`
Handler	`md_npc_pack.MoveData_Commerce_Order_Item_Key`
Order	5
Type	`Flow`

Purpose: Generates unique platform identifiers for order line items.

Flow: md_npc_pack.MoveData_Commerce_Order_Item_Key

Order item name generation#

Metadata entry: COMMERCE_ORDERITEM_NAME_001

Field	Value
Label	`PIPELINE_COMMERCE_ORDERITEM_NAME`
Handler	`md_npc_pack.MoveData_Commerce_Order_Item_Name`
Order	5
Type	`Flow`

Purpose: Generates order item names and handles line item naming conventions.

Flow: md_npc_pack.MoveData_Commerce_Order_Item_Name

Order item field mapping#

Metadata entry: COMMERCE_ORDERITEM_MAPPING_001

Field	Value
Label	`PIPELINE_COMMERCE_ORDERITEM_MAPPING`
Handler	`md_npc_pack.MoveData_Commerce_Order_Item_Mapping`
Order	5
Type	`Flow`

Purpose: Maps commerce notification data to OrderItem fields including product reference, quantity, unit price, discounts, and line totals.

Flow: md_npc_pack.MoveData_Commerce_Order_Item_Mapping

Order item duplicate detection#

Metadata entry: COMMERCE_ORDERITEM_DUPLICATE_001

Field	Value
Label	`PIPELINE_COMMERCE_ORDERITEM_DUPLICATE`
Handler	`md_npc_pack.MoveData_Commerce_Order_Item_Duplicate`
Order	5
Type	`Flow`

Purpose: Locates existing order item records to prevent duplicate line items within orders.

Flow: md_npc_pack.MoveData_Commerce_Order_Item_Duplicate

Order item post-processing#

Metadata entry: COMMERCE_ORDERITEM_POST_001

Field	Value
Label	`PIPELINE_COMMERCE_ORDERITEM_POST`
Handler	`md_npc_pack.MoveData_Commerce_Order_Item_Post`
Order	5
Type	`Flow`

Purpose: Executes post-upsert operations for order items including inventory updates and fulfilment triggers.

Flow: md_npc_pack.MoveData_Commerce_Order_Item_Post