Duplicate PO# Issues

Angela Schmook

Industry Veteran

• March 28, 2025 14:48

HEADS UP!! If your imported commission statement includes duplicate PO#s (ie. web, direct, faire, phone, etc.)  the program selects one random retailer with the duplicate PO, pays the proper rep and the appropriate commission, but gives the rep the randomly selected retailer on their statement, not the retailer on the statement.  

 

In these cases, we suggest numbering them to: FAIRE1, FAIRE2, etc. before importing to avoid this conflict. 

0

• 

  Jessie Frank

  • March 28, 2025 15:21

  Thanks for the warning... let me see if I understand: the import file has shopA & shopB both with po "phone." The importer will go find any random order with the po "phone" already in the system, and matches it to that?

  0
• 

  Angela Schmook

  Industry Veteran

  • April 03, 2025 11:04

  Not any random in the system, but random from the statement.  

  There is shopA, shopB, shopC, shopD all used the PO# phone. The stores belong to 4 different sales reps.  

  MT pays all the correct reps and pays them the correct $, but will give all 4 reps shopA as the store name.  

  Reps assigned to shopB-D calls saying I was paid on shopA that isn't in my territory.  They get the right $, but rep has no idea about the customer they need to follow up with on the phone order. 

  0
• 

  Jessie Frank

  • April 03, 2025 14:17

  THANK YOU for this warning and explanation!

  0

Please sign in to leave a comment.