Skip to main content

Setting up the Integration Between Parting Pro and TMS

Learn how to connect your Parting Pro account with TMS for seamless data import.

Hillary Scalmanini avatar
Written by Hillary Scalmanini
Updated this week

This guide walks you through the one-time setup to connect your Parting Pro account with TMS so your case data can be imported directly into TMS.

🔐 Requirements

  • Admin access to both your TMS and Parting Pro accounts


Step 1: Enable the Integration in TMS

  1. Log in to your TMS account.

  2. Navigate to Admin Settings.

  3. Click on Integrations in the left-hand menu.

  4. Select Parting Pro.

  5. Click + Add New Integration.

  6. TMS will generate a Key and a Secret.

Important: Copy and save the Secret now - you cannot view again later!

Click the ✅ check mark to confirm.

After saving, two new configuration sections will appear: Location Mapping and GPL Mapping.


📍 Step 2: Map Your Parting Pro Locations

To import data from each of your funeral home locations, you’ll need to link them to Parting Pro using a unique Location ID.

  1. In Parting Pro, go to Settings > Tribute Tech Integration.

Find and copy the Location ID.

  1. Return to TMS and find the Location Mapping section.

  2. Click + Add New Location.

  3. Paste the copied Location ID and choose the corresponding location name in TMS.

  4. Repeat for each funeral home location you want to connect.


💰 Step 3: Map Your GPL Categories

To ensure your Parting Pro items sync correctly with your TMS invoices, you’ll need to map your product categories.

  1. In TMS, go to GPL Mapping and click + Add New GPL.

  2. Select the appropriate General Price List.

  3. Click + Add New Product Category.

  4. Choose the Parting Pro Category Name. Categories can be copied from Parting Pro.

  5. Then select the matching TMS Invoice Category and Product Category.

  6. Repeat this for each category in Parting Pro.

  7. If you have multiple GPLs, repeat this process for each list.

⚠️ Note: If any product category or GPL isn’t mapped, case imports will result in an error.

Did this answer your question?