Distribution, Manufacturing, and Internet Modules

[Rhino17]

Hello All,

We are in the process of implementing credit card processing in MAS 90 using SagePayment Solutions.  We have noticed that during SO entry, the system attempts to obtain a pre-authorization for the order when you click accept. 

The issue we have is that we input orders into the system with ship dates weeks or months into the future.  The system is attempting to get pre-authorizations for these orders, regardless is the order is on hold, or the shipment date is in advance of the current date.  This doesn't work for us, as the pre-auth will expire long before the order is actually shipped.

 Is there any way to set criteria for when it attempts to get a pre-authorization?  If not, any suggestions on how to handle these types of orders, and still maintain the ease of use regarding credit cards?

Thanks,

Rhino

[wjezewski]

If you set the Default Payment Type in Customer Maintainence to NONE, MAS will not automatically preauthorize the credit card. When you are ready to preauth the card all you have to do is go back into the sales order, change the payment type on the totals tab to CREDIT CARD and complete the preauth.

I should warn that MAS will preauth the entire amount of the SO and not just what can be shipped. Also, if an order goes on backorder status the payment field will still be set to CREDIT CARD, so if you open the order to review it and then click Accept MAS will preauth the card.

To be honest we have been somewhat suprised by how poorly MAS handles credit cards.

[Rhino17]

Having to change the payment type really seems to defeat the purpose of the integration.

We were sold on pre-authorization making things simpler, and having the ability to make sure that nothing is sent to shipping without ensuring the invoice can be covered by the credit card on file.  However, having to have our CSRs have to remember to change the payment type back to CREDIT CARD before they release the order is asking for trouble. 

I'm with you regarding how poor the system seems to handle credit cards.  I guess the Credit Card Module is really only for companies that ship every order as soon as it is placed, or for companies that work in industries where every customer has excellent cash flow and perfect credit, so pre-authorizations aren't really needed.

[givingtr]

You may wish to review whether SO-1245 can be of benefit here.

[wjezewski]

From the DSD website "Allows you to process Credit Card charges for ‘Shippable’ Amounts. ‘Shippable’ is defined as the difference between the Quantity Ordered and the Quantity Back Ordered on each line."

This led me to believe that backorders would still authorize for the entire amount, which a quick phone call to DSD confirmed, so for us SO-1245 would only fix the issue part of the time.

[givingtr]

What if you backordered these items instead? Else, ask if they can modify the logic to look for a UDF value to exclude the line from consideration (or exclude the item if promise date is greater than some threshold).

[Pappy]

Well, probably not what some companies would prefer; we process the card right then and there for the whole order ... whether we ship it in the next day or two, or in two or three week's time.  To be honest, no one has ever had issue with us doing it that way.

[givingtr]

I suspect if I asked several users to define the perfect credit card module, there would be several variations based upon different business processes. Some of my customers charge the card as a sale for orders that can't be filled for several weeks or months. This is because they may have to wait for the items to be shipped from abraod and clear customs. They don't want to risk the expense of getting the product without a firm purchase commitment from their customer. Most orders can be filled within the 7-10 days a pre-auth is in effect, but it would be nice if users could define the pre-auth amount instead of having it default to the full order amount.

[Rhino17]

Really we just want the system to prevent the pre-authorization if the order is on hold.

This is just a thought, but could I attach a BOI script to the accept button that checks if the order is on hold, and has a payment type of credit card.  If both are true, it would swtich the payment to None, close the order, and then change the payment back to Credit Card?  My skills in BOI aren't strong, but it seems like it should work.

I'm going to look into it, but if anyone has info on why it wouldn't work, please let me know.

Cheers,

Rhino

[wjezewski]

We are using BOI to prevent preauthorizations on backorders once the initial portion of the order has shipped so you should be able to do this.