@kbeatty21 I think Vendor Price Worksheets are your best option. On the Customer Pricing side, we have a client that has >60k parts and >seven pricing levels with frequent updates. Here are the tips I’ve learned along the way. Keep the commits in the import scenario to the bare minimum (end of each row?) - as the worksheet gets larger, it is the save that takes the time. Break up the vendor price sheets using some logical division, vendor, classes,... Keep the number of rows as low as feasible, but you can see we pushed 80k a number of times. Run the load after-hours if possible :)

HI @DConcannon 

I figured that was my only route unfortunately. I have an import scenario as well that I was testing but it didn’t like a few of my fields, so I will retry with that. 

Thanks for the tips! I have already stressed with them the importance of running these after hours as that is when they have the best chance to have it go faster. 

I appreciate your help :)

Were you able to create an import scenario for this? I’m struggling to do the same.

I ran into a similar issue with vendor pricing.  We have a customer who has over 100k prices that needed updating and using the Vendor Price Worksheet with the license limitation was not going to cut it.

We had to build an import scenario to facilitate the need.  This cannot be done using the simplified method on the Import by Scenario screen.  You’ll need to build the scenario from scratch on the Import Scenarios screen (SM206025).  This means creating a Data Provider before building the Import Scenario.  It’s a rather simple scenario to build after that, though.

Here is our mapping:

​@Kandy Beatty  Vendor Price Worksheet is for regular vendor price management and moderate bulk updates, it is not suitable for extremely large imports or updates due to technical and performance limitations.

For high-volume scenarios, consider alternative methods such as API integrations or breaking the workload into smaller, manageable batches