Purpose: Use this screen to define settings related to fraud.
General Values
• Use Gift Card Fraud Checking (L72)
• Allow Order for New Bill-to Without Order Hold (D84)
• Maximum Order Amount for E-Commerce Orders (H54)
• Maximum Order Quantity (C60)
• Maximum Order Line Value (E98)
Ship To Mismatch Values
• Maximum Order Amount for Fraud Checking (D24)
• # of Times Shipped to Same Address (D25)
• Ship Via Priority for Ship To Mismatch (L71)
• # of Days Since Last Order (D26)
Customer Service Values
• Order Discount Percentage Limit (D16)
• Price Override Limit Percent (E55)
• Negative Additional Charge Limit (E49)
External Integration Values
• Fraud Score Cancel Reason Code (M14)
• Product Classification for Fraud Scoring (M15)
Defines whether fraud checking will be performed against customer name and address information during credit checking routines.
Yes/No field: If you select this field, a match code will be assembled for each address on the order, using the three match code algorithms defined in the Match Code table. The match codes will then be checked against the records existing in the Fraud table to flag fraud customers. (See Working with Customer Fraud Tables (WCFD).) You must set up the standard match code and the three fraud match code algorithms (F1, F2, and F3) through the Change Match Codes function. See Setting Up Match Codes (MMCH).
The customer sold-to, bill-to, ship-to, and order address information is evaluated.
Also, the system checks the Miscellaneous Fraud table, in which fraudulent zip codes, credit cards, email addresses, IP addresses, and checks are defined. Any order with a match in this table will be held.
If you leave this field unselected, fraud checking will not be performed; however, fraudulent credit cards and checks as defined in the Miscellaneous Fraud table will still be evaluated. If a match is found, the order will be placed on hold.
For more information: See Working with Miscellaneous Frauds (WMFF) for information on entering miscellaneous frauds. Also, see Introducing Order Hold Reason Codes for an overview of the various hold reason codes used in fraud checking.
Use Gift Card Fraud Checking (L72)
Defines whether the system places an order on GC Gift Card order hold if it contains a stored value card item and a stored value card payment method.
Yes/No field: Select this field if you want the system to place an order on GC Gift Card order hold if it contains a stored value card item and a stored value card payment method.
Note: The stored value card item purchased can be a physical or virtual card and the order can also contain other items. The order can contain multiple payment methods, as long as one of the payment methods is a stored value card payment.
During order entry, the system evaluates the order for gift card fraud checking when you accept the order after evaluating the order for customer fraud checking and before dollar and miscellaneous hold checking; see Updates at Accept.
During order maintenance, the system evaluates the order for gift card fraud checking when you accept the order if the order total has increased and the order is not on hold.
Sold to customer hold/bypass/fraud setting: The system evaluates the order for gift card fraud checking, regardless if the Hold/Bypass/Fraud field for the sold to customer on the order is set to Bypass.
Source code bypass credit check setting: The system does not evaluate the order for gift card fraud checking if the Bypass credit check field for the source code on the order header is selected.
Leave this field unselected if you do not want the system to place an order on hold if it contains a stored value card item and a stored value card payment method.
Allow Order for New Bill-to Without Order Hold (D84)
Defines whether to place orders you enter for new bill-to customers, created through Order Entry, on hold automatically.
Yes/No field: Select this field to process orders for new bill-to customers you create in Order Entry without automatically placing them on hold.
Leave this field unselected to place orders for new bill-to customers on hold automatically. When you create a new bill-to customer in Order Entry, the order is assigned a hold reason of UB (unreferenced bill-to).
For more information:
• Establishing Order Hold Reason Codes (WOHR)
• Creating and Updating Bill-to Customers (WCBT)
Defines the order amount that will cause an order to be placed on hold automatically.
Dollar amount field: Enter the order total amount that will cause an order to be placed on hold automatically. This field is 12 positions with a 2-place decimal.
This dollar amount hold applies to all methods of payment.
If the order total, including all charges, freight, tax, and additional freight, is greater than the amount defined here, the order will be placed on dollar hold (DH type hold) when Credit Checking is performed (when selecting Accept or Accept/Add Rcp to accept a new order). These orders appear on the Release Held Orders screen and must be released from hold manually using Release Held Orders. See Selecting Held Orders (ERHO).
E-Commerce (order API) orders: You can define a separate dollar amount to cause an e-commerce order (order API) to be placed on hold automatically by entering a dollar amount in the Maximum Order Amount for E-Commerce Orders (H54) system control value. If you do not specify a maximum amount for e-commerce orders, or if the order exceeds the Maximum Order Amount (A92) but not the Maximum Order Amount for E-Commerce Orders (H54), the system puts the order on DH hold.
Note: You must specify a value for the Maximum order amount system control value to have the Maximum Order Amount for E-Commerce Orders (H54) apply to e-commerce orders.
Leave this field blank if you do not want to establish a maximum dollar amount.
These calculations are performed on each line on the order, except for vendor drop ship items. The freight charge for each vendor is calculated by totaling the merchandise amount for the vendor and multiplying this total by the Frt%. The system will validate this freight charge against the value in the Min frt field. The difference between the calculated freight charge and the Min frt value is added to the order in the Fr+ (additional freight) field in Order Entry.
Maximum Order Amount for E-Commerce Orders (H54)
Defines the order amount that will cause an e-commerce (order API) order to be placed on hold automatically.
Dollar amount field: Enter the order total amount that will cause an e-commerce order (order API) to be placed on hold automatically. This field is 12 positions with a 2-place decimal.
This dollar amount hold applies to all methods of payment.
Maximum order amount required: In order for the system to evaluate e-commerce orders, you must also specify a Maximum Order Amount (A92). If the Maximum Order Amount (A92) is zero, the order API does not apply the e-commerce hold based on the Maximum Order Amount for E-Commerce Orders (H54).
Important: If this system control value is set to zero, the dollar hold evaluation does not take place; in other words, the system does not automatically put all order API orders on hold.
If the total amount of the order is greater than the amount defined here, the system puts the order on e-commerce hold (EH type hold) during the credit checking process. You need to release these orders from hold manually using Release Held Orders. See Selecting Held Orders (ERHO).
Order history message: When the system puts an order on e-commerce dollar hold, it writes an order history message, such as SYS HLD---E-COMMERCE DOLLAR HOLD. You can review order history messages at the Display Order History Screen.
Determining an e-commerce order: In evaluating an order against this maximum dollar amount, Order Management System considers an order an e-commerce order if the order type matches the E-Commerce Order Type (G42) system control value or if the Internet order flag in the Order Header table is set to I. The order API sets this flag to I when it creates an order.
Leave this field blank (.00) if you do not want to establish a separate maximum dollar amount for e-commerce orders. The Maximum Order Amount (A92) applies.
For more information: See Establishing Order Hold Reason Codes (WOHR) for more information on creating the e-commerce dollar hold reason code.
Defines the maximum number of units that you can enter on an order detail line.
Number field: Enter the maximum item quantity you can enter on a single order detail line in order entry or order maintenance. This validation can help you prevent inaccurate order line quantities due to user error (for example, entering 100 rather than 10).
The Allow Maximum Order Quantity Override (A70) secured feature controls the ability to exceed this maximum. If you have the proper authority, a pop-up window displays informing you that the order line you have just entered exceeds the maximum; you can select Accept to add the line to the order. If you select Exit or OK, an error message such as the following indicates:
Order Qty of 10 exceeds the maximum allowed in SCV C60.
If you do not have proper authority, no pop-up window displays when the order line exceeds the maximum quantity. Instead, the screen displays an error message.
Leave this field blank or set to 0 if you do not want the system to perform a check against the order line quantity.
The system checks the quantity on an individual order line basis, not an order-level basis. In other words, no check takes place to prevent the total unit quantity on the order from exceeding this maximum.
Maximum Order Line Value (E98)
Defines the maximum dollar value of an order line you can enter in order entry or order maintenance.
Dollar amount field: Enter the maximum dollar value you can enter on a single order detail line in order entry or order maintenance.
The Allow Maximum Order Line Value Override (A69) secured feature controls the ability to exceed this maximum. If you have the proper authority, a pop-up window displays informing you that the order line you have just entered exceeds the maximum; you can select Accept to add the line to the order. If you select Exit or OK, an error message indicates:
Order line value of 1000.00 exceeds maximum allowed in SCV E98.
If you do not have proper authority, no pop-up window displays when the order line exceeds the maximum dollar value. Instead, the screen displays an error message. See Working with User Records (WUSR) for information about user authority.
Leave this field blank if you do not want the system to perform a check against the order line total.
Note: The system checks the dollar total on an individual order line basis, not an order-level basis. In other words, no check takes place to prevent the order total from exceeding this maximum.
Maximum Order Amount for Fraud Checking (D24)
Defines the order amount that will cause a credit card order, shipping to an address other than the sold-to address, to be placed on hold if the order does not also meet the criteria for the Ship Via Priority for Ship To Mismatch (L71), and the # of Times Shipped to Same Address (D25) or the # of Days Since Last Order (D26) system control values.
These system control values can help you identify fraudulent credit card orders. The system tries to identify a credit card customer shipping to different addresses within a short period of time. The system places orders that fail this credit check on a SM Ship To Mismatch hold so that you can review the orders before shipping product.
Dollar amount field: Enter the dollar amount that will cause a credit card order with different ship-to and sold-to (billing) addresses to be placed on hold. This field is 12 positions with a 2-place decimal.
The system places an order on SM Ship To Mismatch hold if the following conditions are met:
• the order contains a Credit Card pay category payment method, and
• the ship to address on the order is different from the sold to address, and
• the order total is greater than the Maximum Order Amount for Fraud Checking (D24), and
• the ship via priority for the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), and
• the number of times shipped to the address is less than the # of Times Shipped to Same Address (D25) OR the number of days since the last shipment to the address is less than the # of Days Since Last Order (D26).
Ship to mismatch process: The system evaluates an order for Ship To Mismatch hold when Credit Checking is performed (when selecting Accept or Accept/Add Rcp. to accept a new order).
1. |
The system determines if the order contains a Credit Card pay category payment method and a ship to address that is different from the sold to address. • If the order does not meet these requirements, the system does not evaluate the order for Ship To Mismatch hold and continues with regular processing. • If the order meets these requirements, the system evaluates the order for Ship To Mismatch hold. |
2. |
The system determines if the order total is greater than the order amount in the Maximum Order Amount for Fraud Checking (D24) system control value. • If the order total is less than the maximum specified in the Maximum Order Amount for Fraud Checking (D24) system control value, the system does not place the order on Ship To Mismatch hold and continues with regular processing. • If the order total is greater than the maximum specified in the Maximum Order Amount for Fraud Checking (D24) system control value, the system continues with the ship to mismatch check. |
3. |
The system determines if the priority of the ship via on the order header matches the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value. • If the priority of the ship via on the order header does not match the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system does not place the order on Ship To Mismatch hold and continues with regular processing. • If the priority of the ship via on the order header matches the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system continues with the ship to mismatch check. Note: If you do not define a ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system skips this step in the Ship To Mismatch process and continues to the next step. |
4. |
The system determines if the order passes the requirements in the # of Times Shipped to Same Address (D25) OR the # of Days Since Last Order (D26) system control values. • If the number of times shipped to the address is greater than the # of Times Shipped to Same Address (D25) AND the number of days since the last shipment to the address is greater than the # of Days Since Last Order (D26), the system does not place the order on Ship To Mismatch hold and continues with regular processing. • If the number of times shipped to the address is less than the # of Times Shipped to Same Address (D25) OR the number of days since the last shipment to the address is less than the # of Days Since Last Order (D26), the system places the order on SM Ship To Mismatch hold. The system updates the Status field on the Order Header to H Hold and updates the Hold reason field to SM Ship To Mismatch. The system updates the Hold reason for the Order Ship To record to SM Ship To Mismatch. You can review the order, then release the order manually though the Release Held Orders function, if appropriate. See Performing the Release. |
Dollar hold check: The system also checks all orders, regardless of the payment method, for a total dollar amount exceeding the Maximum Order Amount (A92) system control value. The system places orders exceeding this amount on a DH Dollar Hold. If a credit card order matches the criteria for both a DH Dollar Hold and a SM Ship To Mismatch hold, it will go on a dollar hold first. For this reason, you should specify a greater value for the catch-all Maximum Order Amount (A92) system control value than the Maximum Order Amount for Fraud Checking (D24).
Order transaction history: The system writes a message to the Order Transaction History table (History in standard and streamlined Order Inquiry) if the system places the order on SM Ship To Mismatch hold.
Date Type Transaction Note Amount User
5/02/06 H Shipments (0) LT limit (150). PAUL_P 5/02/06 H Days (14) from DLO LT limit (100). PAUL_P 5/02/06 H SYS HLD---SHIP TO MISMATCH PAUL_P |
The message indicates the number of times you shipped to the same address and the number of days since the customer's last order. This helps you determine the reason why the order was placed on hold and evaluate whether you can release the order from hold using the Release Held Orders function. See Performing the Release.
Example: Examples of this credit checking process. In each example, the order payment method is a credit card.
System Control Value |
Setting |
Maximum Order Amount for Fraud Checking (D24) |
$250.00 |
Ship Via Priority for Ship To Mismatch (L71) |
1 |
# of Times Shipped to Same Address (D25) |
2 |
# of Days Since Last Order (D26) |
5 |
Example |
Result |
#1: A new customer places an order for $300.00 and has the order shipped using a shipper whose priority is 1 to the customer's home (billing) address. |
The order is not held because the ship-to address is the same as the sold-to (billing) address. The order must be both a credit card order and shipped to a different address other than the sold-to customer’s address for the system to check any of the other Fraud Checking system control values. |
#2: An existing customer places a gift order for $100.00 and has it shipped using a shipper whose priority is 1 to a friend’s address. |
The order is not held because the order is less than $250.00. The order must be over $250.00 to be held. In this case, the remaining system control values are not evaluated. The order is evaluated for Fraud Checking because it is shipping to a different address other than the sold-to (billing) address, has a credit card pay type, and the priority of the ship via on the order matches the Ship Via Priority for Ship To Mismatch (L71). |
#3: A new customer places a credit card order for $300.00 and has it shipped using a shipper whose priority is 1 to a work address. |
The order is held because the order total is greater than $250.00, the priority of the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), the number of times shipped to same address is less than 2 times, and the number of days since last order is less than 5 days. The order is held because it is being shipped to a different address other than the sold-to (billing) address, the order total is greater than $250.00, the priority of the ship via on the order matches the Ship Via Priority for Ship To Mismatch (L71), and the order fails both of the remaining two criteria (shipping address and days since last order). |
#4: A new customer places a credit card order for $300.00 and has it shipped using a shipper whose priority is 2 to a work address. |
The order is not held because the priority of the ship via on the order does not match the Ship Via Priority for Ship To Mismatch (L71). In this case, the remaining system control values are not evaluated. The order is evaluated for Fraud Checking because it is shipping to a different address other than the sold-to (billing) address, has a credit card pay type, and the order total is greater than $250.00. |
#5: An existing customer places a gift order for $300.00 and has it shipped using a shipper whose priority is 1. The customer has ordered 3 times before, all orders shipping to the customer's home (billing) address. The customer last ordered about 2 months ago. |
The order is held because the order total is greater than $250.00, the priority of the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), and the number of times shipped to the same address is less than 2 times. The number of days since last order is greater than 5 days. The order is held because this is the first time the customer has shipped to the address on the order (gift recipient's address). |
#6: An existing customer places an order for $300.00 and ships the order using a shipper whose priority is 1 to an office address. The customer has ordered 3 times before, all orders shipping to the customer's home (billing) address. The customer last ordered about 2 months ago. |
The order is held because the order total is greater than $250.00, the priority of the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), and the number of times shipped to the same address is less than 2 times. The number of days since last order is greater than 5 days. The order is held because this is the first time the customer has shipped to the address on the order (using Cust. Ship To in Order Entry for a Customer Ship To address). |
#7: An existing customer places an order for $300.00 and ships the order using a shipper whose priority is 1 to a neighbor's address. The customer has ordered 3 times before, all orders shipping to the customer's home (billing) address. The customer last ordered about 2 months ago. |
The order is held because the order total is greater than $250.00, the priority of the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), and the number of times shipped to the same address is less than 2 times. The number of days since last order is greater than 5 days. The order is held because this is the first time the customer has shipped to the address on the order (using Order Ship To in Order Entry for an Order Ship To address). |
#8: An existing customer places an order for $300.00 and ships the order using a shipper whose priority is 1 to an office address. The customer has ordered twice before, always shipping to the office address. The last order was placed about 2 months ago. |
The order is not held. Although the order total is greater than $250.00 and the priority of the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), previous orders have shipped to this address (using Cust. Ship To for Customer Ship To address in Order Entry), and the customer's last order was more than 5 days ago. |
#9: An existing customer places an order for $300.00 and ships the order using a shipper whose priority is 1 to an office address. The customer has ordered 3 times before, and has shipped to this address before, but in each instance the operator entered the address using Order Ship To. The last order was placed about 2 months ago. |
The order is held because the order total is greater than $250.00, the priority of the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), and the number of times shipped to the same address is less than 2 times. The number of days since last order is greater than the required value of 5. The order is held because this is the first time the address was entered using Cust. Ship To, instead of Order Ship To. The Credit Check program determines the number of times previously shipped to this address is 0. |
#10: An existing customer places an order for $300.00 and ships the order using a shipper whose priority is 1 to an office address. The customer has ordered 3 times before, all shipping to the office address. All orders have been placed within the last week. |
The order is held because the order total is greater than $250.00, the priority of the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), and the number of days since the last order is less than 5 days. The number of times shipped to the same address is greater than 2 times. The order is held because the customer ordered before the required number of days had passed. |
#11: An existing customer places an order for $300.00 and ships the order using a shipper whose priority is 1 to an office address. The customer has ordered 3 times before, all shipping to the office address. In all cases the operator has entered the address using Order Ship To. The last order was placed 1 month ago. |
The order is not held. Although the order total is greater than $250.00 and the priority of the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), the number of times shipped to the same address is greater than 2 times (because each order was entered using Order Ship To), and the number of days since the last order is greater than 5 days. |
Important: As shown above, the system tracks the ship-to address separately at an order and a customer level. Therefore, how the operator enters the order, either using Order Ship To to create an order ship-to address or using Cust. Ship To to create a customer ship-to address, affects when an order will be placed on a ship to mismatch hold.
Leave the Maximum Order Amount for Fraud Checking (D24) field blank if you do not want to evaluate an order for Ship To Mismatch hold.
# of Times Shipped to Same Address (D25)
Defines the minimum number of times a customer must ship to a recipient address for the order not to be placed on a ship to mismatch hold if it also exceeds the dollar amount specified in Maximum Order Amount for Fraud Checking (D24) and has a ship via on the order header whose priority matches the Ship Via Priority for Ship To Mismatch (L71).
This credit check feature helps you identify fraudulent credit card orders. With the Maximum Order Amount for Fraud Checking (D24), the Ship Via Priority for Ship To Mismatch (L71), and the # of Times Shipped to Same Address (D25) system control values, you can identify a possible bad order (over the maximum order amount) because of a frequently changing ship to address.
Number field: Enter the number of times you require a customer to ship to a recipient address (a ship-to address that is different than the sold-to address) for the order not to be placed on a Ship To Mismatch hold. This system control value is used in conjunction with the Maximum Order Amount for Fraud Checking (D24) and Ship Via Priority for Ship To Mismatch (L71) system control values. This is a 7 position numeric field.
The system places an order on SM Ship To Mismatch hold if the following conditions are met:
• the order contains a Credit Card pay category payment method, and
• the ship to address on the order is different from the sold to address, and
• the order total is greater than the Maximum Order Amount for Fraud Checking (D24), and
• the ship via priority for the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), and
• the number of times shipped to the address is less than the # of Times Shipped to Same Address (D25) OR the number of days since the last shipment to the address is less than the # of Days Since Last Order (D26).
Determining the number of shipments:
• For gift recipient orders (Sold To/Rcp.) and customer ship to orders (Address Book), the system checks the number of shipments to the ship to customer in the Customer Shipment History table. The order will not be held if the number of shipments in this table is greater than or equal to the number in this field.
• For orders where there is a one-time-only address (One Time Ship To), the system compares the address with all other one-time shipping addresses in the Order Ship To Address table. The order will not be held if the number of times the address information appears in this table is greater than or equal to the number in this field. The address must be an exact match to one in this table or the system considers the address a new one and places the order on hold.
Ship to mismatch process: The system evaluates an order for Ship To Mismatch hold when Credit Checking is performed (when selecting Accept or Accept/Add Rcp. to accept a new order).
1. |
The system determines if the order contains a Credit Card pay category payment method and a ship to address that is different from the sold to address. • If the order does not meet these requirements, the system does not evaluate the order for Ship To Mismatch hold and continues with regular processing. • If the order meets these requirements, the system evaluates the order for Ship To Mismatch hold. |
2. |
The system determines if the order total is greater than the order amount in the Maximum Order Amount for Fraud Checking (D24) system control value. • If the order total is less than the maximum specified in the Maximum Order Amount for Fraud Checking (D24) system control value, the system does not place the order on Ship To Mismatch hold and continues with regular processing. • If the order total is greater than the maximum specified in the Maximum Order Amount for Fraud Checking (D24) system control value, the system continues with the ship to mismatch check. |
3. |
The system determines if the priority of the ship via on the order header matches the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value. • If the priority of the ship via on the order header does not match the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system does not place the order on Ship To Mismatch hold and continues with regular processing. • If the priority of the ship via on the order header matches the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system continues with the ship to mismatch check. Note: If you do not define a ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system skips this step in the Ship To Mismatch process and continues to the next step. |
4. |
The system determines if the order passes the requirements in the # of Times Shipped to Same Address (D25) OR the # of Days Since Last Order (D26) system control values. • If the number of times shipped to the address is greater than the # of Times Shipped to Same Address (D25) AND the number of days since the last shipment to the address is greater than the # of Days Since Last Order (D26), the system does not place the order on Ship To Mismatch hold and continues with regular processing. • If the number of times shipped to the address is less than the # of Times Shipped to Same Address (D25) OR the number of days since the last shipment to the address is less than the # of Days Since Last Order (D26), the system places the order on SM Ship To Mismatch hold. The system updates the Status field on the Order Header to H Hold and updates the Hold reason field to SM Ship To Mismatch. The system updates the Hold reason for the Order Ship To record to SM Ship To Mismatch. You can review the order, then release the order manually though the Release Held Orders function, if appropriate. See Performing the Release. |
Examples: See the examples provided for the Maximum Order Amount for Fraud Checking (D24) system control value for a description of how the Maximum Order Amount for Fraud Checking (D24), the Ship Via Priority for Ship To Mismatch (L71), the # of Times Shipped to Same Address (D25), and the # of Days Since Last Order (D26) system control values work together.
Leave the # of Times Shipped to Same Address (D25) field blank if you do not want to hold orders because of the delivery address.
Ship Via Priority for Ship To Mismatch (L71)
Defines the ship via priority that prompts the system to place an order on SM Ship To Mismatch hold, provided the order also exceeds the dollar amount specified in the Maximum Order Amount for Fraud Checking (D24) and the number of times shipped to the address on the order is less than the # of Times Shipped to Same Address (D25) OR the number of days since the last shipment to the address is less than the # of Days Since Last Order (D26).
Number field: Enter the ship via priority the system uses for ship to mismatch fraud checking. Valid ship via priorities are 1-9.
The system places an order on SM Ship To Mismatch hold if the following conditions are met:
• the order contains a Credit Card pay category payment method, and
• the ship to address on the order is different from the sold to address, and
• the order total is greater than the Maximum Order Amount for Fraud Checking (D24), and
• the ship via priority for the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), and
• the number of times shipped to the address is less than the # of Times Shipped to Same Address (D25) OR the number of days since the last shipment to the address is less than the # of Days Since Last Order (D26).
Ship to mismatch process: The system evaluates an order for Ship To Mismatch hold when Credit Checking is performed (when selecting Accept or Accept/Add Rcp. to accept a new order).
1. |
The system determines if the order contains a Credit Card pay category payment method and a ship to address that is different from the sold to address. • If the order does not meet these requirements, the system does not evaluate the order for Ship To Mismatch hold and continues with regular processing. • If the order meets these requirements, the system evaluates the order for Ship To Mismatch hold. |
2. |
The system determines if the order total is greater than the order amount in the Maximum Order Amount for Fraud Checking (D24) system control value. • If the order total is less than the maximum specified in the Maximum Order Amount for Fraud Checking (D24) system control value, the system does not place the order on Ship To Mismatch hold and continues with regular processing. • If the order total is greater than the maximum specified in the Maximum Order Amount for Fraud Checking (D24) system control value, the system continues with the ship to mismatch check. |
3. |
The system determines if the priority of the ship via on the order header matches the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value. • If the priority of the ship via on the order header does not match the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system does not place the order on Ship To Mismatch hold and continues with regular processing. • If the priority of the ship via on the order header matches the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system continues with the ship to mismatch check. Note: If you do not define a ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system skips this step in the Ship To Mismatch process and continues to the next step. |
4. |
The system determines if the order passes the requirements in the # of Times Shipped to Same Address (D25) OR the # of Days Since Last Order (D26) system control values. • If the number of times shipped to the address is greater than the # of Times Shipped to Same Address (D25) AND the number of days since the last shipment to the address is greater than the # of Days Since Last Order (D26), the system does not place the order on Ship To Mismatch hold and continues with regular processing. • If the number of times shipped to the address is less than the # of Times Shipped to Same Address (D25) OR the number of days since the last shipment to the address is less than the # of Days Since Last Order (D26), the system places the order on SM Ship To Mismatch hold. The system updates the Status field on the Order Header to H Hold and updates the Hold reason field to SM Ship To Mismatch. The system updates the Hold reason for the Order Ship To record to SM Ship To Mismatch. You can review the order, then release the order manually though the Release Held Orders function, if appropriate. See Performing the Release. |
Examples: See the examples provided for the Maximum Order Amount for Fraud Checking (D24) system control value for a description of how the Maximum Order Amount for Fraud Checking (D24), the Ship Via Priority for Ship To Mismatch (L71), the # of Times Shipped to Same Address (D25) and the # of Days Since Last Order (D26) system control values work together.
Leave this field blank if you do not want to include the ship via priority for the ship via on the order header in the ship to mismatch evaluation. In this situation, the system places the order on SM Ship To Mismatch hold if:
• the order contains a Credit Card pay category payment method, and
• the ship to address on the order is different from the sold to address, and
• the order total is greater than the Maximum Order Amount for Fraud Checking (D24), and
• the number of times shipped to the address is less than the # of Times Shipped to Same Address (D25) OR the number of days since the last shipment to the address is less than the # of Days Since Last Order (D26).
# of Days Since Last Order (D26)
Defines the minimum number of days that must pass before a customer can place and ship an order to a recipient address and not have the order placed on a ship to mismatch hold if it also exceeds the dollar amount specified in Maximum Order Amount for Fraud Checking (D24) and has a ship via on the order header whose priority matches the Ship Via Priority for Ship To Mismatch (L71).
Number field: Enter the number of days that must pass before a customer can place another customer ship to, order ship to, or recipient/gift order, and not have a ship to mismatch hold placed on the order. This system control value is used in conjunction with the Maximum Order Amount for Fraud Checking (D24) and Ship Via Priority for Ship To Mismatch (L71) system control values. This is a 7 position numeric field.
The system places an order on SM Ship To Mismatch hold if the following conditions are met:
• the order contains a Credit Card pay category payment method, and
• the ship to address on the order is different from the sold to address, and
• the order total is greater than the Maximum Order Amount for Fraud Checking (D24), and
• the ship via priority for the ship via on the order header matches the Ship Via Priority for Ship To Mismatch (L71), and
• the number of times shipped to the address is less than the # of Times Shipped to Same Address (D25) OR the number of days since the last shipment to the address is less than the # of Days Since Last Order (D26).
Ship to mismatch process: The system evaluates an order for Ship To Mismatch hold when Credit Checking is performed (when selecting Accept or Accept/Add Rcp. to accept a new order).
1. |
The system determines if the order contains a Credit Card pay category payment method and a ship to address that is different from the sold to address. • If the order does not meet these requirements, the system does not evaluate the order for Ship To Mismatch hold and continues with regular processing. • If the order meets these requirements, the system evaluates the order for Ship To Mismatch hold. |
2. |
The system determines if the order total is greater than the order amount in the Maximum Order Amount for Fraud Checking (D24) system control value. • If the order total is less than the maximum specified in the Maximum Order Amount for Fraud Checking (D24) system control value, the system does not place the order on Ship To Mismatch hold and continues with regular processing. • If the order total is greater than the maximum specified in the Maximum Order Amount for Fraud Checking (D24) system control value, the system continues with the ship to mismatch check. |
3. |
The system determines if the priority of the ship via on the order header matches the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value. • If the priority of the ship via on the order header does not match the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system does not place the order on Ship To Mismatch hold and continues with regular processing. • If the priority of the ship via on the order header matches the ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system continues with the ship to mismatch check. Note: If you do not define a ship via priority in the Ship Via Priority for Ship To Mismatch (L71) system control value, the system skips this step in the Ship To Mismatch process and continues to the next step. |
4. |
The system determines if the order passes the requirements in the # of Times Shipped to Same Address (D25) OR the # of Days Since Last Order (D26) system control values. • If the number of times shipped to the address is greater than the # of Times Shipped to Same Address (D25) AND the number of days since the last shipment to the address is greater than the # of Days Since Last Order (D26), the system does not place the order on Ship To Mismatch hold and continues with regular processing. • If the number of times shipped to the address is less than the # of Times Shipped to Same Address (D25) OR the number of days since the last shipment to the address is less than the # of Days Since Last Order (D26), the system places the order on SM Ship To Mismatch hold. The system updates the Status field on the Order Header to H Hold and updates the Hold reason field to SM Ship To Mismatch. The system updates the Hold reason for the Order Ship To record to SM Ship To Mismatch. You can review the order, then release the order manually though the Release Held Orders function, if appropriate. See Performing the Release. |
Examples: See the examples provided for the Maximum Order Amount for Fraud Checking (D24) system control value for a description of how the Maximum Order Amount for Fraud Checking (D24), the Ship Via Priority for Ship To Mismatch (L71), the # of Times Shipped to Same Address (D25), and the # of Days Since Last Order (D26) system control values work together.
Leave the # of Days Since Last Order (D26) field blank if you do not want to hold orders because of the recency of the last order.
Order Discount Percentage Limit (D16)
Defines the maximum discount amount that can be applied to an order during Order Entry or Order Maintenance.
Percentage field: Enter the highest discount amount that can be taken on the order during Order Entry or Order Maintenance. You may leave this field blank if any discount percentage can be applied to an order.
The system checks this setting when you type a discount amount in the Discount % field during Order Entry or Order Maintenance. If the discount you want to apply to the order is greater than this value, the system issues the following message:
Discount % (xxx.xx) is greater than allowable limit.
This is a numeric, 5-position field with a 2-place decimal.
Price Override Limit Percent (E55)
Defines the percentage of the price override limit Order Entry operators can enter for items.
Percentage: Enter the maximum percentage order entry operators can discount an item through a price override. The system uses the price defined in the item/offer to determine whether the price override exceeds the percentage. The override limit applies only to prices that are lower than the item/offer price. This is helpful in reducing the possibility of fraud by order entry operators.
Enter 0 (zero) or leave this field blank if you do not want to define a price override limit for items in Order Entry and Order Maintenance.
Override price override limit: The Override Price Override Limit (A64) secured feature controls the ability for Order Entry operators to override the percentage defined in this system control value.
Secured Feature Setting |
Price Override Exceeds Percentage |
Price Override Does Not Exceed Percentage |
Exclude |
A message similar to the following displays if an operator enters a price that is less than the percentage allowed: Entered price exceeds override limit. The system processes the order line if an operator enters a price that is greater than the percentage allowed and writes a W order transaction history record for the price override. |
The system processes the order line if an operator enters a price that does not exceed the percentage. |
Allow |
The system processes the order line and writes a W order transaction history record for the price override. The W transaction history record shows you the line on the order where a price override occurred, the price override amount and the user ID of the person who performed the price override. |
The system processes the order line. |
Price override example: The system uses this calculation to determine the percentage of the price override:
(offer price - price override entered) / offer price * 100 = price override percentage
Example |
price override percentage = 10% offer price = $40.00 price override = $35.00 (40.00 - 35.00) = 5.00 5.00/40.00 = .125 .125 * 100 = 12.50 (12.50 exceeds the 10% price override) |
Negative Additional Charge Limit (E49)
Defines the dollar value used to limit the total negative additional charges applied to an order.
Number field: Enter a dollar value here to define the total negative additional charges you can apply to an order. This dollar value will apply towards negative charges only. Any positive additional charges that you enter will not offset the negative charges limit.
You can override the dollar limit for negative additional charges applied to an order if you have authority. See Setting Up Secured Features.
A message indicates if the total value of negative additional charges exceeds the dollar value and you do not have authority:
Negative additional charge exceeds the limit for this order.
Enter a 0 or leave this field blank if you do not want to limit the value of negative additional charges you can apply to an order.
Note:
• This limit applies to additional charges entered in interactive order entry and order maintenance only; it does not apply to the order API (CWOrderIn).
• Additional charges that the system adds to an order (through a promotion, for example) are not included in the negative additional charge total.
Fraud Score Cancel Reason Code (M14)
Defines the cancel reason code the system assigns to an order that is automatically cancelled due to the fraud scoring results from Cybersource Decision Manager.
Number field: Enter the cancel reason code the system assigns to an order that is automatically cancelled due to the fraud scoring results from Cybersource Decision Manager.
Cancel reason codes are defined in and validated against the Cancel Reason Code table; see Establishing Cancel Reason Codes (WCNR).
Leave this field blank if you do not use Decision Manager Fraud Scoring.
For more information: See Cybersource Point-to-Point Integration, specifically Decision Manager Fraud Scoring.
Product Classification for Fraud Scoring (M15)
Defines whether Order Management System uses the item class or item category description for the product classification code passed to Cybersource during Cybersource Decision Manager Fraud Scoring.
Code field:
ITM CLASS |
Order Management System maps the item’s item class description to the ProductCode in the Cybersource Authorization Request (ccAuthService) XML Message when Cybersource Decision Manager Fraud Scoring is enabled. Item class codes are defined in and validated against the Item Class table; see Working with Item Classes (WICL). |
ITM CATGRY |
Order Management System maps the item’s item category description to the ProductCode in the Cybersource Authorization Request (ccAuthService) XML Message when Cybersource Decision Manager Fraud Scoring is enabled. Item category codes are defined in and validated against the Item Category table; see Working with Item Category Codes (WITG). |
Product codes used by Cybersource services are:
• adult_content: Adult content.
• coupon: Coupon applied to the entire order.
• default: Product classification has not been defined for the product.
• electronic_good: Electronic product other than software.
• electronic_software: Software distributed electronically rather than on disks or other media.
• handling_only: Fee that you charge the customer to cover administrative selling costs.
• service: Service that you perform for the customer.
• shipping_and_handling: The shipping portion is the charge for shipping the product to the customer. The handling portion is the fee you charge the customer to cover your administrative selling costs.
• shipping_only: Charge for transporting tangible personal property from your location to the customer. You must maintain documentation that clearly establishes the location where the title to the property passed from you to the customer.
• subscription: Subscription to a web site or other content.
Important: It is your responsibility to set up the item class description or item category description to match the correct value required by Cybersource Decision Manager.
Leave this field blank if you do not use Cybersource Decision Manager Fraud Scoring.
For more information: See Cybersource Point-to-Point Integration, specifically Decision Manager Fraud Scoring.
