OrderLogix Real-Time Order Submission API

OrderLogix Real-Time Order Submission API

Module : Order Import V4
Topic : Real-Time Order Submission
Version(s) : Version 5.0 and up
Editions : Standard, Commerce, Call Center


A list of API Exceptions can be found HERE

Overview

OrderLogix provides real-time API access to the system for external systems to append orders without needing to use the Graphical User Interface (GUI). This is accomplished using the OrderLogix Real-Time Order Submission API Module. This module provides an XML Web service which can accept data for a single order and insert it into the OrderLogix database.
The attached documentation is an outline of the how to use this module including security considerations, process flow and details for the specification of the API.

Security 

The Web Service API is secured in  a number of  different ways to prevent unauthorized use of the service.  The following techniques are utilized to guarantee security. 

IP Restriction  – We no longer restrict access to the web service by IP address.  

SSL Encryption  – Any requests to the service will be required to use the https protocol to insure  2 way  encryption of the information. 

HTTP Basic Authentication  – HTTP basic authentication will be provided to grant access to the web service and the supplied username/password must be passed with every HTTPS request. 

HTTP basic authentication is no longer required with 5.1.333 and up

Authentication Token  – We will also provide an authentication token which must be passed as an HTTP POST parameter with every request. 

OrderLogix   Application User Credentials  – Any call to the web service must also pass a valid username & password as HTTP POST parameters with every request.   The credentials must be attached to a user account which is configured as active in the OrderLogix system.  This user account must also have been granted permission to use the web API order insert.  An administrator of the OrderLogix system can configure this permission via the   “process permissions” tab under the employee setup dialog. 

Process Flow 

  When an order is placed via a  shopping cart or some other system external to OrderLogix, that order can be inserted into the OrderLogix system by making a real-time call to the Order Submission Web Service API.  The web service API will validate the input data for suitability against  all of  the business rules assigned to the campaign and if all data is deemed valid, the order will be inserted into the OrderLogix   system and the  OrderID  will be returned to the system which called the web service. 

Diagram of the order submission process     



API Specification

The system makes use of the https protocol for posting data to the web service.  A successful request will use an HTTPS POST formatted as follows:

POST <<client>>.orderlogix.com/production/dotnetoms/olcc_api/OLCC_API_V3.asmx/ReceiveOrder HTTP/1.1

Host: <<client>>.orderlogix.com

Content-Type: application/x-www-form-urlencoded

Content-Length:  length

user = string & pwd = string & token = string & inXMLDoc = string

Post Parameters

The post parameters are defined as:
  1. user  – a valid OrderLogix user login.
  2. pwd  – password for given user.
  3. token  – a pre-assigned authentication token.
  4. inXMLDoc  – a string of well formatted XML containing field specification below and formatted according to the sample document that follows the field layout. The document will contain order information and settings information that is used to load the order.

Order Field Specification

The table below outlines the layout for Orders (Shipped, Paid and Unpaid) to be imported into the OrderLogix System.  These field names will be child XML Elements of an <Order> XML Element, which is a child element of a Root Element called <OrderImport>.  All specific instructions are noted in “ Red ” in the last column of the spec and should be reviewed carefully as they note business logic rules that affect the ability of orders to successfully load into the system.


Pos
Field Name
Required
Type
Max Width
Dec. Places
Field Description
Specific Notes & Instructions
1
CUSTOMER_NUMBER
Y
Alpha
50

Source System's Customer Number.
Please add a unique prefix and a hyphen "-" to beginning of all customer numbers.
Prefix will be provided in advance by OrderLogix Client.
2
BILL_COMPANY
N
Alpha
255

Company Name
3
BILL_FIRST_NAME
Y
Alpha
30

First Name
4
BILL_LAST_NAME
Y
Alpha
50

Last Name
5
BILL_ADDRESS1
Y
Alpha
255

First Address Line
6
BILL_ADDRESS2
N
Alpha
255

Second Address Line
7
BILL_CITY
Y
Alpha
50

City
8
BILL_STATE
Y
Alpha
20

State/Province (USE STATE ABBREVIATION)
9
BILL_ZIPCODE
Y
Alpha
20

ZIP Code/Postal Code
10
COUNTRY
Y
Alpha
3

Country code for the billing address on an order. Country codes "USA" for United States, "CAN" for Canada
11
BILL_PHONE_NUMBER
Y
Alpha
30

Format (###) ###-####
12
BILL_PHONE_2
N
Alpha
20

Billing PM Phone number
13
EMAIL
N
Alpha
255

Customer’s E-mail address
14
NO_SOLICITING
N
Numeric
1

If the customer should not be solicited pass a "1"
15
SHIP_TO_COMPANY
Y
Alpha
255

Company name (Optional Shipping Address)
16
SHIP_TO_FIRST_NAME
Y
Alpha
50

First name (Optional Shipping Address) Include shipping address information if different from Bill-to.
17
SHIP_TO_LAST_NAME
Y
Alpha
50

Last name (Optional Shipping Address) Include shipping address information if different from Bill-to.
18
SHIP_TO_ADDRESS1
Y
Alpha
255

First Address line (Optional Shipping Address) Include shipping address information if different from Bill-to
19
SHIP_TO_ADDRESS2
N
Alpha
255

Second address line (Optional Shipping Address) Include shipping address information if different from Bill-to.
20
SHIP_TO_CITY
Y
Alpha
50

City (Optional Shipping Address) Include shipping address information if different from Bill-to
21
SHIP_TO_STATE
Y
Alpha
50

State/Province (Optional Shipping Address) Include shipping address information if different from Bill-to
22
SHIP_TO_ZIPCODE
Y
Alpha
50

ZIP Code/Postal Code (optional Shipping Address) Include shipping address information if different from Bill-to.
23
SCOUNTRY
Y
Alpha
3

Country code for the shipping address on an order. Country codes "USA" for United States, "CAN" for Canada
(Optional Shipping Address) Include shipping address information if different from Bill-to.
24
SHIP_TO_PHONE
Y
Alpha
30

The shipping phone number.
25
SHIP_TO_PHONE2 
N
Alpha
30

The secondary shipping phone number.
26
ORDER_DATE
Y
Date
8

The date is the local server time to which the data is being posted. For example, if the server is in PST (-8:00) and the order is coming from EST (-5:00), the time should be
adjusted by subtracting 3 hours
27
ORDER_NUMBER
Y
Alpha
50

Source System’s Order Number. Can be more than 8 and can be alpha. Please add a unique prefix and a hyphen "-" to beginning of all order numbers.
Prefix will be provided in advance by the OrderLogix Client.
28
DNIS
Y
Alpha
50

The source code for this order.
Please Enter the DNIS, Source Code or Telephone # dialed by customer.
Values for this field will be provided in advance by the OrderLogix Client
29
KEY_CODE
N
Alpha
25

Keycode (Promo Code) for the order.
Values for this field will be provided in advance by the OrderLogix Client.
30
EMP_NUMBER
Y
Alpha
50

The employee number the order belongs to.
Values for this field will be provided in advance by the OrderLogix Client.
31
ORDER_HOLD_DATE
N
Date
8

For hold orders, enter the release date here. Order will not be payment processed until this date
32
VOICE_RECORDING_ID
N
Alpha
50

Call Recording ID. Please enter the recording transaction # here
33
PAYMENT_TYPE
N
Alpha
4

For paid credit card orders, this field must contain 'AUTH' for authorized payments or 'SALE' for settled/captured payments, otherwise leave blank.
When populated, the following additional fields will also need to be populated:
AMOUNT_ALREADY_PAID, MERCHANT_TRANSACTION_ID. Also, the Item Level PAID_PRICE, PAID_SHIPPING and PAID_TAX amounts should be completed.
34
AMOUNT_ALREADY_PAID
N
Numeric
9
2
This field will be blank for unpaid orders, and filled in with the total amount charged for paid orders. If you pass 0.00, we will assume the order was paid for prior to importing
and it will ship without payment processing.
Will contain sum of the below fields, for all of the items on the order:
  1. Paid Price
  2. Paid Shipping
  3. calculated Paid Tax
Please consult OrderLogix for amount to pass when order contains multi-pay offers
35
MERCHANT_TRANSACTION_ID
N
Alpha
50

For approved orders, Enter the Transaction ID received from the merchant processor
36
PAYMENT_METHOD
Y
Alpha
2

Method of Payment. Format: "CC" for credit card, "CK" for Telecheck/check by phone, "PC" for paper check, "IN" for invoice or "MO" for money order.
37
CC_TYPE
Y for CC
Orders
Alpha
2

Credit Card type. Please use the following codes for the supported card brands:
V=Visa, MC=MasterCard, D=Discover, A = American Express
38
CC_NUMBER
Y for CC
Orders
Alpha
30

Credit Card Number
39
EXP_DATE

Y for CC
Orders
Alpha
50

Credit Card Expiration date. The format should be MM/YY.
40
CVV_CODE
N
Alpha
4

Credit Card CVV code.
For an order that has already had an authorization or settlement processed, DO NOT pass the CVV. 
Only pass the CVV for an order that needs to have a payment transaction processed in the OrderLogix system.
41
TOKEN
N
Alpha
255

If the order was processed using credit card tokenization, put the value here.
OrderLogix will determine in advance the exact format and data to place in this field depending on the tokenization service.
42
PAY_PROC_ACCT
N
Alpha
50

If using TOKEN this pass the name of the payment processing account to use.
Override the Campaign or Product Group default PPA for an Imported payment transaction (AUTH or SALE)
This value is defined in OrderLogix and will be provided in advance.
43
ACH_BANK_NAME
Y for ACH
Orders
Alpha
255

Checking account bank name.
Use this field for phone check orders only
44
ACH_ROUTING_NUMBER
Y for ACH
Orders

50

Checking account bank routing number
Use this field for phone check orders only
45
ACH_ACCOUNT_NUMBER
Y for ACH
Orders
Alpha
50

Checking Account Number
Use this field for phone check orders only
46
ACH_CHECK_NUMBER
Y for ACH
Orders

50

Check # (Phone Check Orders Only)

47
ACH_IS_SAVINGS_ACCOUNT
N

1

for ACH orders, pass a "1" if the account is a Savings Account 
48
SHIPPING_METHOD
Y
Alpha
10

Designated shipping method for order. "REG" = Standard shipping, "RSH" = Rush Shipping or other provided shipping method codes. 
Any other valid shipping method codes will be provided in advance by the OrderLogix Client.
49
ORDER_ALREADY_FULFILLED
N
Alpha
1

This field will be blank for unshipped orders, and filled in with "Y" for orders which have already shipped
50
TRACKING_NUM
N
Alpha
35

If the order is fulfilled then provide the tracking number, otherwise, leave blank
51
SHIPPING_CARRIER
N

Alpha
35

If the order is fulfilled then provide the shipping carrier, otherwise, leave blank
52
SHIPPING_DATE
N

Date
8

If the order is fulfilled then provide the transaction date, otherwise, leave blank
53
CLIENT_TRANSACTION_ID
N

Alpha
35

If the order is fulfilled then provide the client transaction id from the fulfillment software, otherwise, leave blank
54
CONTINUED
N

Alpha
1

Indicate with a “Y” if this record is a continuation of the prior record. This is used when more than 5 products are required for a given order, otherwise it will be "N".
Always pass “N” in this field. This field is only used for the flat file version of this file specification.
55
CUSTOM_1
N

Alpha
50

Custom1. Please enter the value to put into the custom1 field here
This Custom field must be enabled in advance by the OrderLogix Client before data can be passed.
56
CUSTOM_2
N

Alpha
50

Custom2. Please enter the value to put into the custom2 field here
This Custom field must be enabled in advance by the OrderLogix Client before data can be passed.
57
CUSTOM_3
N

Alpha
50

Custom3. Please enter the value to put into the custom3 field here
This Custom field must be enabled in advance by the OrderLogix Client before data can be passed.
58
CUSTOM_4
N

Alpha
50

Custom4. Please enter the value to put into the custom4 field here
This Custom field must be enabled in advance by the OrderLogix Client before data can be passed.
59
CUSTOM_5
N

Alpha
50

Custom5. Please enter the value to put into the custom5 field here
This Custom field must be enabled in advance by the OrderLogix Client before data can be passed.
60
CUSTOMER_COMMENTS
N
Alpha
4000

Customer Notes
61
CUSTOMER_AGE
N
Numeric
4

Conditionally required based on Campaign.
62
CUSTOMER_DOB
N

Date
8

Conditionally required based on Campaign, format as mm/dd/yy
63
CUSTOMER_GENDER
N

Alpha
50

Conditionally required based on Campaign, format as "male" or "female"
64
CUSTOMER_SSN
N
Alpha
50

Conditionally required based on Campaign, format as ###-##-####
65
PACKING_SLIP_COMMENTS
N
Alpha
4000


66
ORDER_COMMENTS
N
Alpha
4000


67
LOCATION_CODE 
N
Alpha
10

Location where order is captured
If used for the given campaign, this value will be provided in advance by the OrderLogix Client.
68
USE_SHIPPING
N
Alpha
1

This field will have a “Y” to indicate that the shipping charges for the order are to follow in field 69.
If “N” is passed, the shipping charges that are defined for the items inside the OrderLogix system will be used instead. Please consult with the OrderLogix Client to determine the
value for this field.
69
SHIPPING
N
Numeric
9
2
The shipping charges to assign to the order if the USE_SHIPPING field is used.
Note that this amount applies to the entire order
70
USE_TAXES
N
Alpha
1

This field will have a “Y” to indicate that the tax amount in the ORDER_STATE_SALES_TAX should be used rather than the tax values in the OrderLogix system.
If “N” is passed, the tax rates that are defined inside the OrderLogix system will be used instead. Please consult with the OrderLogix Client to determine the value for this field.
71
ORDER_STATE_SALES_TAX
N
Numeric
9
2
State Tax (when applicable). This is the sum of all PAID_TAX_PROD0#
Note that this amount applies to the entire order
72
ORDER_FEDERAL_SALES_TAX
N
Numeric
9
2
Federal Tax (when applicable).
Note that this amount applies to the entire order
73
USE_PRICES
N
Alpha
1

This field will have a "Y" indicating that the prices are to follow for each of the products starting at field position 73.
If “N” is passed, the prices that are defined for the items inside the OrderLogix system will be used instead. Please consult with the OrderLogix Client to determine the value for this field.
74
ORDER_SUBTOTAL
N
Numeric
8

The sum of all products on the order
using formula quantity * (unit price –
discount).
75
ORDER_TOTAL
N
Numeric
8

The sum of all products, shipping and tax on the order using formula (quantity * (unit price – discount)) +shipping + tax
76
PRODUCT01
Y
Alpha
255

The 1st product code on the order.
A list of valid products will be provided in advance by the OrderLogix Client.
77
DESCRIPTION01
N
Alpha
100

Line Item Description to assign to the 1st Product Code
This field will only be used if USE_PRICES (Field72) = Y. If
USE_PRICES (Field72) = Y and value is blank, the default description from OrderLogix will be used.
78
QUANTITY01
Y
Numeric
8

The quantity of this product being ordered.
79
PRICE01
N
Numeric
9
2
The price to assign to the 1st product code. For items with QTY > 1, pass the total value divided by the quantity
This value will be ignored if the value of USE_PRICES = “N”
80
DISCOUNT01
N
Numeric
9
2
Corresponding discount amount. 
Please pass a dollar amount discount for this item. For items with QTY > 1, pass the total discount divided by the quantity
81
DISCOUNT_RATE01
N
Numeric
5
2
Corresponding discount rate. 10% would be sent as 10.00. When this value is used, rate will be applied to (unit price * quantity) then rounded either at item or order level.
This value will override anything passed in DISCOUNT01.
82
COUPON_CODE01
N
Alpha
255

The coupon code for PRODUCT01.
Coupon codes can be passed when discounts are applied to allow tracking of discounts.
83
SHIPPING01
N
Numeric
9
2
The shipping to assign to the 1st product code. For items with QTY > 1 AND multiply shipping by quantity is enabled on offer, pass the total value divided by the quantity – else pass the total unit value
This value will be ignored if the value of USE_PRICES = “N”
84
TAX_RATE01
N
Numeric
9
4
The tax rate to assign to the 1st product code. Please specify up to 4 digits of precision after the decimal point. For example, 9.3725 would represent 9.3725% and 10.0000
would represent 10%.
This value will be ignored if the value of USE_TAX = “N”
85
TAX_PROD01
N
Numeric
9
2
The product tax to assign to the 1st product code - to include the value in TAX_SHIPPING_PROD01
For items with QTY > 1, pass the total value divided by the quantity
This value will be ignored if the value of USE_TAX = “N”
86
TAX_SHIPPING_PROD01
N
Numeric
9
2
The shipping tax to assign to the 1st product code. For items with QTY > 1 AND multiply shipping by quantity is enabled on offer, pass the total value divided by the quantity – else pass the total unit value
This value will be ignored if the value of USE_TAX = “N”
87
PAID_PRICE_PROD01
N
Numeric
9
2
The product price that was already paid for the 1st product code.
This value will be used if the value of PAYMENT_TYPE = “AUTH” or “SALE”
88
PAID_SHIPPING_PROD01
N
Numeric
9
2
The shipping amount that was already paid for the 1st product code.
This value will be used if the value of PAYMENT_TYPE = “AUTH” or “SALE”
89
PAID_TAX_PROD01
N
Numeric
9
2
The tax amount that was already paid for the 1st product code.
TAX_PROD01 + TAX_SHIPPING_PROD01 = PAID_TAX_PROD01
This value will be used if the value of PAYMENT_TYPE = “AUTH” or “SALE”

90
PRODUCT02
N
Alpha
255

The 2nd product code on the order.
A list of valid products will be provided in advance by the OrderLogix Client.
91
DESCRIPTION02
N
Alpha
100

Line Item Description to assign to the 2 nd Product Code.
This field will only be used if USE_PRICES (Field72) = Y. If
USE_PRICES (Field72) = Y and value is blank, the default description from OrderLogix will be used.
92
QUANTITY02
Y if  PRODUCT02 is provided
Numeric
8

The quantity of this product being
ordered.
93
PRICE02
N
Numeric
9
2
The price to assign to the 2nd product code. For items with QTY > 1, pass the total value divided by the quantity
This value will be ignored if the value of USE_PRICES = “N”
94
DISCOUNT02
N
Numeric
9
2
Corresponding discount amount.
Please pass a dollar amount discount for this item. For items with QTY > 1, pass the total discount divided by the quantity
95
DISCOUNT_RATE02
N
Numeric
5
2
Corresponding discount rate. 10% would be sent as 10.00. When this value is used, rate will be applied to (unit price * quantity) then rounded either at item or order level.
This value will override anything passed in DISCOUNT02.
96
COUPON_CODE02
N
Alpha
255

The coupon code for PRODUCT02.
Coupon codes can be passed when discounts are applied to allow tracking of discounts
97
SHIPPING02
N
Numeric
9
2
The shipping to assign to the 2nd product code. For items with QTY > 1 AND multiply shipping by quantity is enabled on offer, pass the total value divided by the quantity – else pass the total unit value
This value will be ignored if the value of USE_PRICES = “N”
98
TAX_RATE02
N
Numeric
9
4
The tax rate to assign to the 2nd product code. Please specify up to 4 digits of precision after the decimal point. For example, 9.3725 would represent 9.3725% and 10.0000
would represent 10%.
This value will be ignored if the value of USE_TAX = “N”
99
TAX_PROD02
N
Numeric
9
2
The product tax to assign to the 2nd product code. For items with QTY > 1, pass the total value divided by the quantity
This value will be ignored if the value of USE_TAX = “N”
100
TAX_SHIPPING_PROD02
N
Numeric
9
2
The shipping tax to assign to the 2nd product code. For items with QTY > 1 AND multiply shipping by quantity is enabled on offer, pass the total value divided by the quantity – else pass the total unit value
This value will be ignored if the value of USE_TAX = “N”
101
PAID_PRICE_PROD02
N
Numeric
9
2
The product price that was already paid for the 2nd product code.
This value will be used if the value of PAYMENT_TYPE = “AUTH” or “SALE”
102
PAID_SHIPPING_PROD02
N
Numeric
9
2
The shipping amount that was already paid for the 2nd product code.
TAX_PROD02 + TAX_SHIPPING_PROD02 = PAID_TAX_PROD02
This value will be used if the value of PAYMENT_TYPE = “AUTH” or “SALE”
103
PAID_TAX_PROD02
N
Numeric
9
2
The tax amount that was already paid for the 2nd product code.
This value will be used if the value of PAYMENT_TYPE = “AUTH” or “SALE”

NOTE: Repeat the fields for PRODUCTxx, DESCRIPTIONxx, QTYxx, PRICExx, DISCOUNTxx, DISCOUNT_RATExx, COUPON_CODExx, SHIPPINGxx, TAX_RATExx, TAX_AMOUNT_PRODxx, TAX_AMOUNT_SHIPPINGxx, PAID_PRICExx, PAID_SHIPPINGxx, PAID_TAXxx for each product on the order

Settings Field Specification

 The table below outlines the layout for optional Settings to be used during processing of the order which is to be imported into the OrderLogix System.  These field names will be child XML Elements of a <Settings> XML Element, which is a child element of a Root Element called <OrderImport>.  All specific instructions are noted in “ Red ” in the last column of the spec and should be reviewed carefully as they note business logic rules that affect the ability of orders to successfully load into the system.

Field Spec Version: 4.0
Pos
Field Name
Required
Type
Max Width
Dec. Places
Field Description
Specific Notes & Instructions
1
MATCH_FIRST_NAME
N
Alpha
1

This field will have a “Y” to indicate that the first name field should be included in match criteria for merging this order to an existing customer record.
2
MATCH_LAST_NAME
N

Alpha
1


This field will have a “Y” to indicate that the last name field should be included in match criteria for merging this order to an existing customer record.
3
MATCH_ADDRESS1
N

Alpha
1


This field will have a “Y” to indicate that the address field should be included in match criteria for merging this order to an existing customer record.
4
MATCH_ADDRESS2
N

Alpha
1


This field will have a “Y” to indicate that the address 2 field should be included in match criteria for merging this order to an existing customer record.
5
MATCH_CITY
N

Alpha
1


This field will have a “Y” to indicate that the city should be included in match criteria for merging this order to an existing customer record.
6
MATCH _STATE
N

Alpha
1


This field will have a “Y” to indicate that the state field be included in match criteria for merging this order to an existing customer record.
7
MATCH _ZIPCODE 
N

Alpha
1


This field will have a “Y” to indicate that the zip code field be included in match criteria for merging this order to an existing customer record.
8
MATCH_PHONE
N

Alpha
1


This field will have a “Y” to indicate that the phone number field should be included in match criteria for merging this order to an existing customer record.
9
MATCH_EMAIL 
N

Alpha
1


This field will have a “Y” to indicate that the email address field should be included in match criteria for merging this order to an existing customer record.
10
MATCH_CLIENT
N

Alpha
1


This field will have a “Y” to indicate that the client name assigned to the order should be included in match criteria for merging this order to an existing customer record.
11
MATCH_CAMPAIGN
N

Alpha
1


This field will have a “Y” to indicate that the campaign of the order should be included in match criteria for merging this order to an existing customer record.
12
API_LAYOUT_VERSION
N

Alpha
1


The Layout Version of the API. For Extended Item level pricing, place a “2” in this field.
13
SETTLE_MODE
N

Alpha
10

The settle mode used for authed orders. The field will have A-S-F (Auth-Settle-Fulfill) or A-F-SC-S (Auth-Fulfill-Ship Confirm-Settle). If this field is left blank, it will default to
A-S-F.
14
N

Alpha
5

This field specifies whether tax calculation mode is ITEM, ORDER, or TOTAL. If this field is left blank, it will default to ORDER.
15
VALIDATE_PRICE
N

Alpha
1


This value will be ignored if the value of USE_PRICES = “N”
This field will have a “Y” to indicate that the prices passed for each item match the prices as set up in OrderLogix. If this field is left blank, it will default to “N”
16
N
Alpha
7

This field specifies whether tax calculations will be rounded as ROUND, UP, DOWN, or BANKERS.
If this field is left blank, it will default to ROUND
17
DISCOUNT_CALCULATION_METHOD
N
Alpha
5

This field specifies whether discount calculation mode is ITEM or ORDER.
If this field is left blank, it will default to ORDER.
18
DISCOUNT_ROUNDING_METHOD
N
Alpha
7

This field specifies whether discount calculations will be rounded as ROUND, UP, DOWN, or BANKERS.
If this field is left blank, it will default to ROUND.
19
VALIDATE_COUPONS
N
Alpha
1


This field specifies whether the settings of a coupon such as
percentage or amount discounted and whether coupons are enabled for the script should be validated upon import. “Y” will indicate that coupons should be validated. If this field is left blank, it will default to “N”
20
UNIT_PRICE_DECIMAL_PRECISION
N
Alpha
1

This field specifies how many digits of decimal precision will be stored for the unit price when using a discount
rate for quantities > 1. “4” will indicate extended precision. If this field is left blank, it will default to “2”
21
SHIP_TAX_CALCULATION_METHOD 
N
Alpha
10

This field specifies how to calculate tax on shipping.
Use “Aggregated” if calculating with the unit price. Use 
“Separated” if calculating separate. If this field is left blank, it will default to “Aggregated”.
22
USE_TAX_AMOUNT_INSTEAD_OF_TAX_RATE
N
Alpha
1

If you are sending TAX_PROD without TAX_RATE set this to "Y"

Attachments


    • Related Articles

    • OLX Web Services API

      The OrderLogix Web Services API provides real-time API access to an OLX system for external systems to read, change and append data without needing to use the OLX Graphical User Interface (GUI). OrderLogix provides an Application Programming ...

    • OLX Order Import/Export V4 Spec

      The OLX Order Import/Export V4 is compatible with OrderLogix version 4.0 & up. It is the newer, more detailed 145 column order import used to bring outside orders into the OrderLogix application. This is accomplished by creating a CSV (a file with ...

    • OLX Order Import/Export Spec

      The OLX Order Import/Export is compatible with OrderLogix versions 3.5 & up. It is the original (or legacy) 107 column order import used to bring outside orders into the OrderLogix application. This is accomplished by creating a CSV (a file with ...

    • OLX Shipping Export v5.0

      The OLX Shipping Export v5.0 is the file layout used to send orders to fulfillment companies from the OrderLogix application.  This is accomplished by creating a CSV (a file with information fields, each separated by a single comma) comprised of 3 ...

    • OLX Telemarketing Import Spec

      The OLX Telemarketing Import Spec is a 121 column order import used to bring outside calls and orders into the OrderLogix application. This is accomplished by creating a CSV (a file with information fields, each separated by a single comma) with all ...