fedex ship manager api · table of contents fedex ship manager® api/direct tagged transaction...

298
FedEx Ship Manager ® API/DIRECT Tagged Transaction Guide Jun05.0

Upload: truongnga

Post on 26-Jul-2018

224 views

Category:

Documents


1 download

TRANSCRIPT

FedEx Ship Manager® API/DIRECT

Tagged Transaction Guide

Jun05.0

Confidential and Proprietary

The information contained in this Tagged Transaction Guide is confidential and proprietary to FedEx Corporate Services, Inc. and its affiliates (collectively "FedEx"). No part of this Tagged Transaction Guide may be distributed or disclosed in any form to any third party without written permission of FedEx. This guide is provided to you under and its use is subject to the terms and conditions of the FedEx End User and/or Consultant License Agreement. The information in this document may be changed at any time without notice. Any conflict between either of these guides, the FedEx End User and/or Consultant License Agreement, and the FedEx Service Guide shall be governed by the FedEx End User and/or Consultant License Agreement and the FedEx Service Guide, in that order.

© 2005 FedEx. FedEx and the FedEx logo are registered service marks. All rights reserved. Unpublished.

Table of Contents

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 1

Table of Contents

Introduction .................................................................................................................................................................................................................. 5 Tagged Transaction Set............................................................................................................................................................................................ 5 Formatting a Tagged Transaction............................................................................................................................................................................. 5 UTIs: Universal Transaction Identifiers..................................................................................................................................................................... 6

What’s New ................................................................................................................................................................................................................... 8 Referenced Documents............................................................................................................................................................................................. 10 Tagged Transaction Layouts .................................................................................................................................................................................... 11

Transaction 211: Subscription/Registration Request ............................................................................................................................................. 13 Example of Transaction 211: Subscription/Registration Request ..................................................................................................................... 15

Transaction 311: Subscription/Registration Reply.................................................................................................................................................. 16 Example of Transaction 311: Subscription/Registration Reply ......................................................................................................................... 17

Transaction 019: Service Availability Request (For FedEx Express Only)............................................................................................................. 18 Examples of Transaction 019: Service Availability Request (Express)............................................................................................................. 20

Transaction 119: Service Availability Reply (For FedEx Express Only)................................................................................................................. 22 Examples of Transaction 119: Service Availability Reply.................................................................................................................................. 23

Transaction 022: Rate a Package Request ............................................................................................................................................................ 26 Example of Transaction 022: Rate a Package Request.................................................................................................................................... 32

Transaction 122: Rate a Package Reply ................................................................................................................................................................ 34 Example of Transaction 122: U.S. Domestic Rate a Package Reply................................................................................................................ 43

Transaction 025: Rate Available Services Request ............................................................................................................................................... 44 Transaction 125: Rate Available Services Reply.................................................................................................................................................... 49 Transaction 021: Ship a Package Request ............................................................................................................................................................ 55

Example of Transaction 021: Ship a Package Request (Domestic Express) ................................................................................................... 81 Transaction 121: Ship a Package Reply................................................................................................................................................................. 83

Example of Transaction 121: Ship a Package Reply (Domestic Express)........................................................................................................ 94 Transaction 023: Delete a Package Request ......................................................................................................................................................... 96

Example of Transaction 023: Delete a Package Request................................................................................................................................. 97

Table of Contents

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 2

Transaction 123: Delete a Package Reply ............................................................................................................................................................. 98 Example of Transaction 123: Delete a Package Reply ..................................................................................................................................... 99

Transaction 007: Close Request (Applicable to FedEx Ground Only) ................................................................................................................. 100 Example of Transaction 007: Close Request .................................................................................................................................................. 102

Transaction 107: Close Reply (Applicable to FedEx Ground Only) ..................................................................................................................... 103 Example of Transaction 107: Close Reply ...................................................................................................................................................... 105

Transaction 403: Track a Package Request......................................................................................................................................................... 106 Example of Transaction 403: Track by Tracking Number ............................................................................................................................... 109

Transaction 503: Track a Package Reply............................................................................................................................................................. 110 Example of Transaction 503: Track a Package Reply .................................................................................................................................... 115

Transaction 405: Signature Proof of Delivery Request ........................................................................................................................................ 119 Example of Transaction 405: Signature Proof of Delivery............................................................................................................................... 123

Transaction 505: Signature Proof of Delivery Reply............................................................................................................................................. 124 Example of Transaction 505: Signature Proof of Delivery............................................................................................................................... 125 Sample Signature Proof of Delivery (SPOD) Letter ........................................................................................................................................ 126

Transaction 410: FedEx Locator Request ............................................................................................................................................................ 127 Example of Transaction 410: Locator Request ............................................................................................................................................... 131

Transaction 510: FedEx Locator Reply ................................................................................................................................................................ 132 Example of Transaction 510: Locator Reply ................................................................................................................................................... 134

Transaction 037: E-Mail Label Request................................................................................................................................................................ 136 Example of Transaction 037: Email Label Request ........................................................................................................................................ 146

Transaction 137: E-Mail Label Reply.................................................................................................................................................................... 149 Example of Transaction 137: Email Label Reply............................................................................................................................................. 151

Transaction 033: Cancel E-Mail Label Request ................................................................................................................................................... 152 Example of Transaction 033: Cancel Email Label Request ............................................................................................................................ 153

Transaction 133: Cancel E-Mail Label Reply........................................................................................................................................................ 154 Example of Transaction 133: Cancel E-mail Label Reply ............................................................................................................................... 155

Transaction 044: Call Tag Create Request .......................................................................................................................................................... 156 Example of Transaction 044: Call Tag Create Request .................................................................................................................................. 161

Transaction 144: Call Tag Create Reply............................................................................................................................................................... 164 Example of Transaction 144: Call Tag Create Reply ...................................................................................................................................... 165

Table of Contents

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 3

Transaction 045: Call Tag Cancel Request .......................................................................................................................................................... 166 Example of Transaction 045: Call Tag Cancel Request.................................................................................................................................. 167

Transaction 145: Call Tag Cancel Reply .............................................................................................................................................................. 168 Example of Transaction 145: Cancel Call Tag Reply...................................................................................................................................... 169

Transaction 046: Express Tag Dispatch Create Request .................................................................................................................................... 170 Example of Transaction 046: Express Tag Dispatch Create Request ............................................................................................................ 175

Transaction 146: Express Tag Dispatch Create Reply......................................................................................................................................... 178 Example of Transaction 146: Express Tag Create Dispatch Reply ................................................................................................................ 180

Transaction 047: Express Tag Dispatch Cancel Request .................................................................................................................................... 181 Example of Transaction 047: Express Tag Dispatch Cancel Request............................................................................................................ 182

Transaction 147: Express Tag Dispatch Cancel Reply ........................................................................................................................................ 183 Example of Transaction 147: Express Tag Dispatch Cancel Reply................................................................................................................ 184

Transaction 048: Express Tag Availability Request ............................................................................................................................................. 185 Example of Transaction 048: Express Tag Availability Request..................................................................................................................... 186

Transaction 148: Express Tag Availability Reply ................................................................................................................................................. 188 Example of Transaction 148: ExpressTag Availability Reply .......................................................................................................................... 190

Shipping Label Specifications................................................................................................................................................................................ 191 Plain Paper and Thermal Label Specifications..................................................................................................................................................... 191

General Printing Overview and Methods......................................................................................................................................................... 191 PNG Plain Paper Label.................................................................................................................................................................................... 192 Determining Screen Resolution....................................................................................................................................................................... 193 Custom Labels................................................................................................................................................................................................. 194

Shipping Label Support......................................................................................................................................................................................... 195 Label Data Buffer............................................................................................................................................................................................. 195 Using Buffer Data to Print PNG or Thermal Labels......................................................................................................................................... 196

Appendix A: Field Descriptions by Field Tag........................................................................................................................................................ 202 Appendix B: Country Codes ................................................................................................................................................................................... 259 Appendix C: Vague Commodity Descriptions ...................................................................................................................................................... 263

Table of Contents

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 4

Appendix D: Legal Terms and Conditions ............................................................................................................................................................ 286 Legal Terms .......................................................................................................................................................................................................... 286

Plain Paper and Thermal Label ....................................................................................................................................................................... 286 Conditions of Contract .......................................................................................................................................................................................... 287

Glossary.................................................................................................................................................................................................................... 290 Index.......................................................................................................................................................................................................................... 294

Introduction

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 5

Introduction

Tagged Transaction Set In the following pages, we will take a closer look at the transactions that FedEx Ship Manager API and Direct support. Before that, however, we will describe the rules governing well-formed tagged transactions.

Formatting a Tagged Transaction The Tagged Transaction Set uses the ASCII character set. A transaction consists of a set of fields concatenated together. Each field contains a tag, a comma, and a value – in that order. The value must be enclosed in double-quotes. Note that the commas are not used to separate the fields within a transaction. They are used to separate the tag from the value within each field. The tag in the field 955 (test) would be 955, and the value would be “test”.

The first field in a transaction must be the Transaction Type, whose tag is 0 (zero). Its value identifies the transaction as being of a certain type. For instance, Add Shipment transactions always begin with 0,”021” and Delete Shipment transactions begin with 0,”023”. The Transaction Type should not be confused with the Universal Transaction Identifier (UTI) (see below), which uniquely defines a transaction type across all transaction sets. The Transaction Type is unique only within the Tagged Transaction Set.

The last field in a transaction must be the Transaction Terminator, whose tag is 99, which has a null value (“”). It is the only field whose value can be empty. Thus, you can always find the end of a transaction by searching for 99,””.

NOTE:

Except in the case of the Transaction Terminator (99,””), empty values (“”) are not allowed.

Aside from the Transaction Type and Transaction Terminator, the fields in a transaction can be in any order. No meaning should be ascribed to the ordering of the fields, and no reliance should be placed on fields in Replies appearing in any particular order.

Introduction

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 6

An ordinary tag is a decimal integer without leading zeroes. A multiple-occurrence tag will add a dash character followed by another decimal integer (again without leading zeroes). A field with a multiple-occurrence tag is an instance of a field which can take an ordered set of more than one value. The integer following the dash tells us which position in the set is occupied by this instance (see example below). If only one instance of such a field is in the transaction, the dash and integer 1 can be omitted from its tag, so that it looks like an ordinary tag. However, if there are multiple occurrences of this tag, the first tag must include the “-1” and so forth.

The values of all fields (except those of certain binary data fields) can contain only printable characters. Different fields have different rules governing their format. But generally, numeric values do not have leading zeroes. Alphanumeric values should not contain leading or trailing blanks. The null (0x00) and double-quote (0x22) characters are never allowed in values, even in binary fields, where they are replaced with special escape sequences (see discussion on label buffers in the Shipping Label Support section of this document).

UTIs: Universal Transaction Identifiers

NOTE:

The UTI section of this guide is only applicable when the FedEx Tagged Transactions are being used with FedEx Ship Manager API. The UTI codes are not applicable to FedEx Ship Manager Direct.

The Universal Transaction Identifier (UTI) is a unique integral code that has been assigned to a given transaction type. For example, the UTI of the tagged Transaction Type 021 (FedEx Express global Ship a Package Request) is 2016.

UTIs are unique not just within the tagged transaction set, but across all transaction sets that have been or will be approved for transmission via the API.

The UTI accompanying a transaction indicates where it should be routed within the FedEx systems. The FedEx server recognizes the UTI passed in a call to FedExAPITransaction and routes the transaction to the correct business server.

Introduction

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 7

Valid UTI codes are listed below:

UTI Transaction Type Applicable Carrier Description

1002 007 / 107 FDXG End-of-day Close

1005 023 / 123 FDXE FedEx Express Delete-A-Package

2016 021 / 121 FDXE FedEx Express Ship-A-Package

2017 022 / 122 FDXE Global Rate-A-Package

2018 019 / 119 FDXE Service Availability

2024 025 / 125 ALL Rate Available Services

2025 410 / 510 ALL FedEx Locator

2027 037 / 137 FDXE FedEx Express Email Label

2028 033 / 133 FDXE FedEx Express Cancel Email Label

2029 046/146 FDXE FedEx Express Tag

2030 047/147 FDXE FedEx Cancel Express Tag

2031 048/148 FDXE FedEx Express Tag Availability

3000 021 / 121 FDXG FedEx Ground Ship-A-Package

3001 023 / 123 FDXG FedEx Ground Delete-A-Package

3003 211 / 311 ALL Subscription

3004 022 / 122 FDXG Global Rate-A-Package

3010 044 / 144 FDXG FedEx Ground Call Tag

3011 045 / 145 FDXG FedEx Ground Cancel Call Tag

3012 037 / 137 FDXG FedEx Ground Email Label

3013 033 / 133 FDXG FedEx Ground Cancel Email Label

5001 405 / 505 ALL Signature Proof of Delivery

5002 403 / 503 ALL Track By Number, Destination, Ship Date, and Reference

What’s New

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 8

What’s New

International Document Shipping Improvements

• Support documents with commercial value – to improve document shipping process • Clearer field names for International shipments – with ‘Purpose’ description • Allow multiple countries of manufacture for one package containing items manufactured in different countries • Expanded Commodity Description – from 148 characters to 450 • Venezuela Postal Stamp fee – for inbound and outbound packages • Excess Customs Value – allows entry of customs value greater than the default amount

Signature Service Options

• Indirect Signature Required: FedEx will obtain a signature 1) from any person at the delivery address, or 2) from someone at a neighboring address, or 3) the recipient can leave a signed FedEx door tag authorizing release of the package without anyone present. Available for residential deliveries only.

• Direct Signature Required: FedEx will obtain a signature from any person at the delivery address and will reattempt delivery if no one is available to sign for the package. Available for both residential and nonresidential deliveries.

• Adult Signature Required: FedEx will obtain a signature from any person at the delivery address who is at least 21 years old and who has government-issued photo identification as proof of age, and will reattempt delivery if no one is available to sign for the package. Available for both residential and nonresidential deliveries.

• Direct Signature Required replaces FedEx Express Signature Required, FedEx Ground® Auto P.O.D., FedEx Home Delivery® Auto P.O.D. and FedEx Signature Home DeliverySM. Until Direct Signature Required is available, shippers can still choose the above options.

• Label Type 1 – Standard will not print the new Direct Signature code on the Label. • Label Type 1 – Standard does not support Signature Service. • AOD is no longer supported – Error returned if indicated in ship request.

* The impact of signature options fees may vary depending on your agreement with FedEx.

What’s New

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 9

Customer Bar Code on Doc Tab

Customer-specific information can be indicated in the bar code and human-readable form on the doc-tab.

New Customs Regulations and Edits for Canada and U.S.

Ineligible for Money Back Guarantee

• For intra-Canada shipments – A warning when an area being shipped to is not eligible for Money Back Guarantee (MBG).

Admissibility Package Type – A 3-character code representing a specific package type. Applicable for:

• All origin countries to Canada, excluding intra-Canada • Canada and Mexico origins to U.S. and Puerto Rico destinations

Vague Commodity Description – A list of descriptions considered vague. Applicable for:

• All origin countries to Canada, excluding intra-Canada • Canada and Mexico origins to U.S. and Puerto Rico destinations

Revised Paper Invoice Format • Provides two additional reference fields for Express shipments

Referenced Documents

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 10

Referenced Documents

Title Location

FedEx Service Guide To download in .pdf format: http://www.fedex.com/us/services/express/pdf.html. To request a printed copy, please call 1.800.Go.FedEx (1.800.463.3339).

Tagged Transaction Layouts

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 11

Tagged Transaction Layouts

This section introduces the FedEx Tagged Transaction fields included in each of the transactions. Each transaction will be presented in a table format. The table columns will be:

Column Description

Field Tag The tag corresponding to each of the defined fields. A comma should follow this tag, followed in turn by the actual value of the field. For example: 32,”My Company”.

Field Name The name of the transaction field.

Applicable Carrier This column is used for identifying if a field tag is valid for use with which Service (Carrier). Valid values:

ALL = All carriers (FedEx Express and FedEx Ground) FDXE = FedEx Express only FDXG = FedEx Ground only

Valid For This column is used to identify how the functionality (field tag) is supported. Valid values:

ALL = Applicable to U.S. Domestic and all International shipments INTL = Applicable to non-Intra U.S. Domestic shipments USD = Applicable to U.S. Domestic shipments (U.S. to U.S.) CA = Applicable to Canada (Intra/Inter-Canada) PR = Applicable to Puerto Rico

Field Tag The tag corresponding to each of the defined fields. A comma should follow this tag, followed in turn by the actual value of the field. For example: 32,”My Company”

Field Name The name of the transaction field.

Field Requirements The information regarding the transaction field. Comments on the meaning of the tag, and whether it is required, conditionally required, or optional. “Required” means that the field tag is required in the case of the specified “Applicable Carrier” and “Valid For” values. Appendix A offers a comprehensive listing of the field characteristics in numeric order by field tag.

Tagged Transaction Layouts

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 12

Field Tag Examples

Alpha-Numeric Field – Single Occurrence The sender company name will be included in a transaction in the following manner: 4,”FedEx Corporation”

Alpha-Numeric Field – Multiple Occurrences The second occurrence of commodity number of pieces in the shipment response transaction will be included in the transaction in the following manner: 76-2,”5”

NOTE:

A tag with occurrence number of 0, as in 76-0, “5”, will be ignored.

Numeric Field – Whole Number The dimmed height will be included in a Ship Request transaction in the following manner: 57,”10”

Numeric Field – Two Explicit Decimal Positions The base rate will be included in a shipping response transaction in the following manner: 1419,”50.00”

NOTE:

The fields do not need to be in numeric order when you are formatting your transaction. The only requirement is to always begin your data string with the 0 tag and end the data string with 99,””.

Tagged Transaction Layouts – Transaction 211: Subscription/Registration Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 13

Transaction 211: Subscription/Registration Request

This is a one-time Request, meaning that a customer needs to subscribe to the FedEx API service only once. The transaction data and a unique meter number specific to the customer’s FedEx account number will be returned to the client.

Field Tag Field Name Field Requirements

STANDARD INFO

0 Transaction Code Required.

1 Customer Transaction Identifier Optional. This field allows a FedEx customer to assign a unique identifier to a transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

10 Sender FedEx Account Number Required. This field tag should represent the FedEx account number for the FedEx customer to which the unique meter number will be assigned.

498 Meter Number The unique meter number assigned to the Sender’s FedEx account number is required to successfully receive a rate quote. Note: This field tag should only be supplied within the Request when attempting to update the meter information.

SUBSCRIBER

4003 Subscriber Contact Name Required. This field tag is only required if Company Name is not provided.

4007 Subscriber Company Name Optional. This field tag becomes required if Person Name is not provided.

4008 Subscriber Address Line 1 Required.

4009 Subscriber Address Line 2 Optional.

4011 Subscriber City Name Required.

4012 Subscriber State Code Required if Sender Country Code is US or Canada.

Tagged Transaction Layouts – Transaction 211: Subscription/Registration Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 14

Field Tag Field Name Field Requirements

4013 Subscriber Postal Code Required. Required only if Recipient Country Code is US or CA. May be required for other postal-aware countries. Represents the postal code of the subscriber of account. Valid characters: A-Z; 0-9; a-z

4014 Subscriber Country Code Required.

4015 Subscriber Phone Number Required. The maximum length is 10 for US and CA, 16 for all other countries. Do not include embedded special characters.

4017 Subscriber Pager Number Optional. The maximum length is 10 for US and CA, 16 for all other countries. Do not include embedded special characters.

4018 Subscriber Email Address Optional.

4022 Subscriber Fax Number Optional. The maximum length is 10 for US and CA, 16 for all other countries. Do not include embedded special characters.

TRANSACTION TERMINATOR

99 End Of Record Required.

Tagged Transaction Layouts – Transaction 211: Subscription/Registration Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 15

Example of Transaction 211: Subscription/Registration Request

If you are a new subscriber to the FedEx Ship Manager API, the first thing you need to do is send the 211 transaction to FedEx to register your account. For example, your name is Jim Smith (you are acting on behalf of your company), your company name is “Creative Widgets,” and your address is 123 Main Street, Anycity, VA 24060. Your phone number is 540.555.9900, and your FedEx Account Number is 123456789. The input transaction should be formatted as follows:

Data File Field Description

0,"211" Transaction Type 211 is Subscription/Registration Request.

1,"my 1st transaction to FedEx" Customer Transaction identifier.

4003,"Jim Smith" Your name.

4007,”Creative Widgets” Your company’s name.

4011”Anycity” Your city name.

4008,"123 Main Street" Your street address.

4015,"5405559900" Your phone number, no dashes.

4012"VA" Your state abbreviation.

10,”123456789” Your FedEx account number.

4013,"24060" Your ZIP code.

4014,”US” Your Country Code. See Appendix B for a list of FedEx Country Codes.

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 311: Subscription/Registration Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 16

Transaction 311: Subscription/Registration Reply

Once you submit your Request to subscribe to FedEx, you will receive a subscription Reply. The format of the Reply is as follows:

Field Tag Field Name Field Requirements

STANDARD INFO

0 Transaction Code Required.

1 Customer Transaction Identifier Optional. Returned if the customer included it in the Request transaction, containing the same value.

ERROR HANDLING

2 Transaction Error Code Passed back in the Reply indicating failed processing of transaction. For an erroneous transaction, the error code will be placed in this field tag.

3 Transaction Error Message Passed back in the Reply indicating failed processing of transaction. For an erroneous transaction, the error message will be placed in this field tag.

SUBSCRIBER

498 Meter Number Returned in successful Reply. Meter number assigned to the FedEx account number.

4021-# Subscription Service Name Returns (in multiple occurrences of the field) the FedEx Services the customer is eligible for.

TRANSACTION TERMINATOR

99 End Of Record Returned.

Tagged Transaction Layouts – Transaction 311: Subscription/Registration Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 17

Example of Transaction 311: Subscription/Registration Reply

Continuing with the example on the previous page, the Reply transaction would be formatted as follows:

Data File Field Description

0,”311” Transaction Type 311 is Subscribe/Register Reply.

1,”Subscribe” Customer Transaction identifier. FedEx will return to you the same identifier you send in.

498,”1234567” Your meter number.

4021-1,”0001” Authorized for FedEx Express Shipping.

4021-2,”0002” Authorized for FedEx Ground Shipping.

99,”” Transaction terminator.

If the input transaction contains an error, an error message number and message text are included in the transaction Reply. If, for example, the ZIP code entered had only 3 digits, FedEx would respond with the following transaction:

Data File Field Description

0,”311” Transaction Type 311 is Subscribe/Register Reply.

1,” Subscribe “ Customer Transaction identifier. FedEx will return to you the same identifier you send in.

2,”1235” Error code.

3,”Bad Zip Format” Error message.

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 019: Service Availability Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 18

Transaction 019: Service Availability Request (For FedEx Express Only)

The Service Availability Request is used to determine which FedEx Express services are available between a given origin and destination. To check the availability of one particular FedEx service and packaging type, include fields 1273 (service) and 1274 (packaging type) in the Request transaction. Only information regarding that single service and packaging type will be returned in the 119 Reply transaction. To obtain a list of all available services for a certain origin and destination, omit fields 1273 and 1274 from the Request. The Reply will contain information on every available service.

Field Tag Field Name Field Requirements

STANDARD INFO

0 Transaction Code Required.

1 Customer Transaction Identifier Optional. This field allows a FedEx customer to assign a unique identifier to a transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

10 Sender FedEx Account Number Required. The FedEx account number of the Sender is required to successfully receive a Service Availability response.

498 Meter Number Required. The unique meter number assigned to the Sender’s FedEx account number is required to successfully receive a Service Availability response.

3025 Carrier Code Required. Valid value:

FDXE – FedEx Express

ORIGIN

9 Sender Postal Code Required only if Sender Country Code is US or CA. Postal code may also be required for other postal-aware countries. Represents the postal code from which the shipment will be originating. Valid characters: A-Z; 0-9; a-z

Tagged Transaction Layouts – Transaction 019: Service Availability Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 19

Field Tag Field Name Field Requirements

117 Sender Country Code Required. Represents the country from which the shipment will be originating.

DESTINATION

17 Recipient Postal Code Required only if Recipient Country Code is US or CA. Postal code may also be required for other postal-aware countries. Represents the postal code to which the shipment is destined. Valid characters: A-Z; 0-9; a-z

50 Recipient Country Code Required. Represents the country code to which the shipment is destined.

SHIPMENT INFO

24 Ship Date Recommended. The date in which the package will be shipped. Should not be a past date or a date that is more than 10 days in the future. Format: YYYYMMDD Defaults to current system date if not present.

116 Package Total (Total Number of Pieces)

Required for multiple-piece shipments (MPS). For MPS shipments, 1 piece = 1 box. For International Freight MPS shipments, this is the total number of “units.” Units are the skids, pallets, or boxes that make up a freight shipment. Each unit within a shipment should have its own label. FDXE only applies to COD, MPS, and International. Valid values: 1 to 999

1273 FedEx Packaging Type Optional.

1274 FedEx Service Type Optional.

TRANSACTION TERMINATOR

99 End Of Record Required.

Tagged Transaction Layouts – Transaction 019: Service Availability Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 20

Examples of Transaction 019: Service Availability Request (Express)

You plan to ship an Express package on Monday, May 21, 2005. The origin is GA, 30052. The destination is VA, 24012. It is a single piece shipment. To determine which FedEx Express services are available, your input transaction is formatted as follows:

Data File Field Description

0,”019” Transaction Type 019.

1,”Service Availability Transaction” Transaction Identifier. This field will be included in any error or Reply messages.

498,”1234567” Shipper meter number.

3025,”FDXE” Carrier Code.

9,”30052” Shipper ZIP code.

10,”123456789” Shipper FedEx account number.

17,”24012” Destination ZIP code.

50,”US” Destination Country code.

117,”US” Shipper’s country code.

24,”20050521” Date of the shipment (May 21, 2005).

116,”1” Package total.

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 019: Service Availability Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 21

You plan to ship an Express package on Monday, May 21, 2005. The origin is GA, 30052. The destination is VA, 24012. It is a single piece shipment, and the packaging is a tube. If you want to know if FedEx Priority Overnight service is available, your input transaction is formatted as follows:

Data File Field Description

0,”019” Transaction Type 019.

1,”Service Availability Transaction” Transaction Identifier. This field will be included in any error or Reply messages.

498,”1234567” Shipper meter number.

3025,”FDXE” Carrier Code.

9,”30052” Shipper ZIP code.

10,”123456789” Shipper FedEx account number.

17,”24012” Destination ZIP code.

50,”US” Destination Country code.

117,”US” Shipper’s country code.

24,”20050521” Date of the shipment (May 21, 2005).

116,”1” Package total.

1273,”04” Packaging type (tube).

1274,”01” Service type (Priority Overnight).

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 119: Service Availability Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 22

Transaction 119: Service Availability Reply (For FedEx Express Only)

In response to the previous Service Availability Request transaction, your Reply transaction would be formatted as follows:

Field Tag Field Name Field Requirements

STANDARD INFO

0 Transaction Code Required.

1 Customer Transaction Identifier Optional. Returned if the customer included it in the Request, containing the same value.

ERROR HANDLING

2 Transaction Error Code Passed back in response indicating failed processing. For an erroneous Request or server failure, the error code will be placed in this field tag.

3 Transaction Error Message Passed back in response transaction indicating failed processing. For an erroneous transaction, the error message will be placed in this field tag.

SERVICE INFORMATION

1133 Service Availability Service Count FedEx service(s) available for the Requested origin/destination pairing. There may be up to 22 occurrences of the Entry grouping representing services available.

AVAILABLE SERVICES

409-# Delivery Date In regards to International services, the delivery date availability is limited to some postal supported countries. The delivery date will be returned if available.

194-# Delivery Day Day of week: SUN, MON, TUE, WED, THU, FRI, SAT. In regards to International services, the delivery date availability is limited to some postal supported countries. The delivery date will be returned if available.

195-# Destination Station ID FedEx location identifier of the package destination.

1274-# FedEx Service Type Returned.

TRANSACTION TERMINATOR

99 End Of Record Returned.

Tagged Transaction Layouts – Transaction 119: Service Availability Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 23

Examples of Transaction 119: Service Availability Reply

The following is an example of the Reply transaction format for Requests that specify that all available services should be returned:

Data File Field Description

0,”119” Transaction Type 119.

1,” Service Availability Transaction” Transaction Identifier. This field will be included in any error or Reply messages.

1133,”08” Service count. Eight FedEx Express services are available.

1274-1,”01” FedEx Service Type (Priority Overnight).

194-1,”TUE” Delivery Day.

195-1,”ROA” Destination Station ID.

409-1,”22MAY01” Delivery Date.

1274-2,”03” FedEx Service Type (Economy Two Day).

194-2,”WED” Delivery Day.

195-2,”ROA” Destination Station ID.

409-2,”23MAY01” Delivery Date.

1274-3,”06” FedEx Service Type (First Overnight).

194-3,”TUE” Delivery Day.

195-3,”ROA” Destination Station ID.

409-3,”22MAY01” Delivery Date.

1274-4,”05” FedEx Service Type (Standard Overnight).

194-4,”TUE” Delivery Day.

195-4,”ROA” Destination Station ID.

409-4,”22MAY01” Delivery Date.

1274-5,”80” FedEx Service Type (Two Day Freight).

194-5,”WED” Delivery Day.

Tagged Transaction Layouts – Transaction 119: Service Availability Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 24

Data File Field Description

195-5,”ROA” Destination Station ID.

409-5,”23MAY01” Delivery Date.

1274-6,”70” FedEx Service Type (Overnight Freight).

194-6,”TUE” Delivery Day.

195-6,”ROA” Destination Station ID.

409-6,”22MAY01” Delivery Date.

1274-7,”20” FedEx Service Type (Express Saver).

194-7,”WED” Delivery Day.

195-7,”ROA” Destination Station ID.

409-7,”23MAY01” Delivery Date.

99,”” The required transaction terminator. It must be the last pair in the transaction.

The following is an example of the Reply transaction format for Requests regarding the availability of a single service type:

Data File Field Description

0,”119” Transaction Type 119.

1,” Service Availability Transaction” Transaction Identifier. This field will be included in any error or Reply messages.

1133,”01” Service count.

1274-1,”01” FedEx Service Type (Priority Overnight).

194-1,”TUE” Delivery Day.

195-1,”ROA” Destination Station ID.

409-1,”22MAY01” Delivery Date.

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 119: Service Availability Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 25

If the input transaction contains an error, an error message number and message text are included in the transaction Reply. For example, if the destination ZIP code were not served by FedEx, the response transaction would be:

Data File Field Description

0,”119” Transaction Type 119 is Service Availability Reply.

1,”112301” Transaction identifier.

2,”6011” Error code.

3,”Postal code not served.” Error message.

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 022: Rate a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 26

Transaction 022: Rate a Package Request

As a courtesy to our customers, FedEx provides an estimated rate for a shipment if requested. The courtesy rates returned are estimates and may differ from the actual amount invoiced depending upon the specific circumstances regarding the shipment. The following fields can be included in the U.S. Domestic Rate a Package Request:

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code ALL ALL

1 Customer Transaction Identifier

ALL ALL Optional. This field tag allows a FedEx customer to assign a unique identifier to a transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

10 Sender FedEx Account Number

ALL ALL The FedEx account number of the Sender is required to successfully receive a rate quote.

498 Meter Number ALL ALL The unique meter number assigned to the Sender’s FedEx account number is required to successfully receive a rate quote.

3025 Carrier Code ALL ALL Required. Valid values:

FDXE – FedEx Express rate quotes FDXG – FedEx Ground rate quotes

ORIGIN

8 Sender State ALL ALL Required only if Sender Country Code is US or CA. Represents the state or province from which the shipment will be originating.

9 Sender Postal Code ALL ALL Required only if Sender Country Code is US or CA. Postal code may also be required for other postal-aware countries. Represents the postal code from which the shipment will be originating. Valid characters: A-Z; 0-9; a-z

Tagged Transaction Layouts – Transaction 022: Rate a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 27

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

117 Sender Country Code ALL ALL Required. Represents the country from which the shipment will be originating.

DESTINATION

16 Recipient State ALL ALL Required only if Recipient Country Code is US or CA. Represents the state or province to which the shipment is destined.

17 Recipient Postal Code ALL ALL Required only if Recipient Country Code is US or CA. Postal code may also be required for other postal-aware countries. Represents the postal code to which the shipment is destined. Valid characters: A-Z; 0-9; a-z

50 Recipient Country Code ALL ALL Required. Represents the country code to which the shipment is destined.

RATE DATA

1529 Rate Indicator FDXE FDXG

USD ALL

Optional.

SHIPMENT DATE/TIME STAMP

24 Ship Date ALL ALL Optional. The date in which the package will be shipped. Should not be a past date or a date that is more than 10 days in the future. Format: YYYYMMDD Defaults to current system date if not present.

PAYMENT

23 Pay Type ALL ALL Optional. Defaults to bill sender. If value other than 1 (bill sender) is used, bill sender rates will still be returned.

Tagged Transaction Layouts – Transaction 022: Rate a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 28

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

SHIPMENT/ PACKAGE INFORMATION

57 Dim Height ALL ALL Optional. Required only if a FedEx Express heavyweight service is selected for the shipment. Only applicable if the package type (tag 1273) is 01 (Customer Packaging).

58 Dim Width ALL ALL Optional. Required only if a FedEx Express heavyweight service is selected for the shipment. Only applicable if the package type (tag 1273) is 01 (Customer Packaging).

59 Dim Length ALL ALL Optional. Required only if a FedEx Express heavyweight service is selected for the shipment. Only applicable if the package type (tag 1273) is 01 (Customer Packaging).

68 Customs/Declared Value Currency Type

ALL ALL Optional. Required if tag 1415 (Declared Value/Carriage Value) is provided. Must be equal to USD Only.

75 Weight Units ALL ALL Required. Valid weight types: • LBS • KGS Must be LBS on a Domestic rate quote.

Tagged Transaction Layouts – Transaction 022: Rate a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 29

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

116 Package Total (Total Number of Pieces)

ALL ALL Required for MPS. Total number of packages in a shipment including the master package. May be used for International shipments if supplying shipment Total Pieces and Total Weight. DO NOT use as an input field for U.S. Domestic shipping. FDXE only applies to COD, MPS, and International.

1116 Dim Units ALL ALL Required if dimensions are entered. Only applicable if the package type (tag 1273) is 01 (Customer Packaging). U.S. Domestic Express must be in inches.

1273 FedEx Packaging Type ALL ALL Required. If value entered in this field is 06 (FedEx Letter), MPS rate quote is not allowed.

1274 FedEx Service Type ALL ALL Required.

1401 Total Package Weight ALL ALL Required.

1415 Declared Value/Carriage Value

ALL ALL Required, except FedEx Express International PIB (document) shipments.

SPECIAL SERVICE

27 COD Flag FDXE FDXG

USD ALL

Y if shipment is Collect on Delivery (COD). If Flag is Y and the customer is enabled by FedEx for Electronic COD (ECOD), then ECOD will take affect.

440 Residential Delivery Flag ALL USD Y if shipment is Residential Delivery. If Recipient Address is in a rural area (defined by table lookup), additional charge will be applied. This field is not applicable to the FedEx Home Delivery service.

1120 Inside Pickup Flag FDXE USD Y if shipment is Inside Pickup.

1121 Inside Delivery Flag FDXE USD Y if shipment is Inside Delivery.

1174 BSO Flag FDXE INTL Y if shipment is BSO (Broker Select Option).

Tagged Transaction Layouts – Transaction 022: Rate a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 30

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1200 HAL Flag FDXE ALL Y if shipment is Hold at Location.

1266 Saturday Delivery Flag FDXE ALL Y if shipment is targeted for Saturday delivery.

1267 Saturday Pickup Flag FDXE ALL Y if shipment is targeted for Saturday pickup.

1268 Dry Ice Flag FDXE ALL Y if shipment contains dry ice.

1331 Dangerous Goods Type FDXE ALL A if shipment contains accessible dangerous goods, else I for inaccessible dangerous goods. Not allowed with Return Shipments if field tag 2382 (Return Shipment Indicator) is set to 1, 2, 3 or 4.

1332 Alcohol Flag FDXE ALL Y if shipment is alcohol, else N.

1333 Drop Off Type FDXE ALL Required.

1409 COD Collect Amount FDXG ALL Required if the COD or ECOD Flag is set to Y.

2399 Signature Option ALL ALL Optional. Valid values:

1 = Deliver without Signature 2 = Indirect Signature 3 = Direct Signature 4 = Adult Signature

3000 COD Collection Type FDXG ALL Required if the COD or ECOD Flag is set to Y. Cash is only applicable with FedEx Ground.

3015 Hazardous Materials Flag FDXG USD Y if shipment contains hazardous materials Not allowed with Return Shipments if field tag 2382 (Return Shipment Indicator) is set to 1, 2, 3 or 4.

3018 Nonstandard Container Flag FDXG ALL Y if nonstandard container.

3020 Home Delivery Type FDXG USD Required if shipping FedEx Home Delivery (FHD). Not allowed with Return Shipments if field tag 2382 (Return Shipment Indicator) is set to 1, 2, 3 or 4.

Tagged Transaction Layouts – Transaction 022: Rate a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 31

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

3231 Residential Pickup Flag FDXG USD Optional. Y = Residential N = Commercial/Business Indicates the type of pickup location for a Ground E-mail Label and/or Ground Call Tag. (Only applicable if field tag 2382 = 3 or 4.)

VARIABLE HANDLING

1427 Variable Handling Charge ALL ALL Optional. Required in conjunction with Variable Handling Type. Allowed with Return Shipments if field tag 2382 (Return Shipment Indicator) is set to 0 or 2 only.

1588 Variable Handling Type ALL ALL Optional. If valid value is present, a valid Variable Handling Charge is required.

1606 Variable Handling Charge Level

ALL ALL Optional. Only applicable if valid Variable Handling Type is present.

RETURNS

2382 Returns Shipment Indicator ALL USD Optional. Indicates the type of return shipment: • Print Return Label • Email Label • FedEx Tag (ExpressTag/CallTag – (carrier code dependency) Note: Surcharges may apply: 2 = Return Label surcharges apply 3 = E-mail Label surcharges apply 4 = FedEx Tag surcharges apply (dependent on carrier)

TRANSACTION TERMINATOR

99 End Of Record ALL ALL Required.

Tagged Transaction Layouts – Transaction 022: Rate a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 32

Example of Transaction 022: Rate a Package Request

On Friday, February 6, 2005 your customer, ABC Widget, requests a shipment of parts to be delivered on Saturday, February 14. ABC Widget’s delivery address is 123 N. Main Street, Suite 26, Roanoke, VA 24012. Their phone number is 703.555.1212. The requested shipment is one piece, and weighs a total of 2 pounds, and is being shipped in a FedEx Box. Your company has agreed to pay the freight charges. Your FedEx account number is 123456789, and your Meter number is 1234567. Your location is Atlanta, GA 30052.

To determine your cost of shipping this package, your input transaction is formatted as follows:

Data File Field Description

0,”022” Transaction Type 022 is Rate a Package Request.

1,”Rate Transaction” Transaction Identifier. This field will be included in any error or Reply messages.

498,”1234567” Shipper meter number.

3025,”FDXE” Carrier Code.

9,”30052” Shipper ZIP code.

8,”GA” Shipper state.

10,”123456789” Shipper FedEx account number.

16,”VA” Destination state abbreviation.

17,”24012” Destination ZIP code.

50,”US” Destination Country code.

117,”US” Shipper’s country code.

1401,”2.0” Shipment weight.

75,”LBS” Weight units.

23,”1” Pay type is Bill Shipper.

24,”20050206” Date of the shipment (February 6, 2005).

116,”1” Package total.

1415,”10.00” Declared value.

68, “USD” Customs/Declared Value Currency Type.

Tagged Transaction Layouts – Transaction 022: Rate a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 33

Data File Field Description

1273,”03” Packaging type.

1274,”03” Service type.

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 122: Rate a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 34

Transaction 122: Rate a Package Reply

In response to the previous rating Request transaction, your Reply transaction would be formatted as follows:

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code ALL ALL Required.

1 Customer Transaction Identifier

ALL ALL Optional. Returned if the customer included it in the Request transaction, containing the same value.

ERROR HANDLING

2 Transaction Error Code ALL ALL Returned only if an error occurred while processing the transaction.

3 Transaction Error Message ALL ALL Returned only if an error occurred while processing the transaction.

RATING

431 Dim Flag ALL ALL Y if Dim applies.

1089 Rate Scale Code FDXE USD Returned.

1090 Rate Currency Type ALL ALL Rate currency type returned upon successful transaction Reply.

1092 Rate Zone FDXE USD Returned.

1402 Bill Weight ALL ALL Bill Weight = Dim if Dim applies.

1403 Dim Weight FDXE ALL Returned if applicable.

1416 Base Rate Amount ALL ALL Base rate amount returned in successful transaction Reply.

1417 Total Surcharge Amount ALL ALL Total surcharge amount returned in successful transaction Reply.

1418 Total Discount Amount ALL ALL Total discount amount returned upon successful transaction Reply.

1419 Net Charge Amount ALL ALL Net charge amount returned upon successful transaction Reply.

1420 Total Rebate Amount FDXE ALL Total rebate amount return upon successful transaction Reply.

Tagged Transaction Layouts – Transaction 122: Rate a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 35

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1507 List Total Surcharge Amount

FDXE FDXG

USD ALL

Returned when tag 1529 (Rate Indicator) = 2. Sum of total surcharges.

1525 Effective Net Discount FDXE FDXG

USD ALL

Returned when tag 1529 (Rate Indicator) = 2. List Net Charge – Net Charge Amount.

1528 List Net Charge Amount FDXE FDXG

USD ALL

Returned when tag 1529 (Rate Indicator) = 2. Rate + Surcharges – Discounts.

1530 List Base Rate Amount FDXE FDXG

USD ALL

Returned when tag 1529 (Rate Indicator) = 2. List base rate amount.

1531 List Total Discount Amount FDXE FDXG

USD ALL

Returned when tag 1529 (Rate Indicator) = 2. List total discount amount (will always = 0).

1532 List Total Rebate Amount FDXE FDXG

USD ALL

Returned when tag 1529 (Rate Indicator) = 2. List total rebate amount (will always = 0).

2399 Signature Option ALL ALL Optional.

2405 Ineligible for MBG FDXG ALL Y if a shipment does not qualify for MBG (Money Back Guarantee).

Tagged Transaction Layouts – Transaction 122: Rate a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 36

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

3124 Oversize Classification FDXG ALL Required. Valid values: (Defaults to 0)

1 = A package weighing less than 30 lbs. and measuring more than 84” but equal to or less than 108” in combined length and girth will be classified by FedEx Ground as an Oversize 1 (OS1) package. The transportation charges for an Oversize 1 (OS1) package will be the same as a 30-lb. package being transported under the same circumstances. 2 = A package weighing less than 50 lbs. and measuring more than 108" but equal to or less than 130" in combined length and girth will be classified by FedEx Ground as an Oversize 2 (OS2) package. The transportation charges for an Oversize 2 (OS2) package will be the same as a 50-lb. package being transported under the same circumstances. 3 = A package weighing 150 lbs. or less and measuring more than 130" but equal to or less than 165" in combined length and girth will be classified by FedEx Ground as an Oversize 3 (OS3) package. The transportation charges for an Oversize 3 (OS3) package will be based on the greater of the package's actual rounded weight or a 90-lb. minimum billable weight. An additional oversize charge will be assessed on any package measuring more than 130" in length and girth.

POSSIBLE SURCHARGES

* Indicates that the surcharge is influenced by the Rate Indicator field (tag 1529)/List Rate field.

2402 Signature Option Fee ALL ALL Returned when tag 2399 (Signature Option) has a value of 2, 3, or 4.

2403 List Signature Option Fee ALL ALL Returned when tag 2399 (Signature Option) has a value of 2, 3, or 4.

3095 Appointment Delivery Surcharge

FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3096 *List Appointment Delivery Surcharge

FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

Tagged Transaction Layouts – Transaction 122: Rate a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 37

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

3101 Home Delivery Date Certain Surcharge

FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place

3102 *List Home Delivery Date Certain Surcharge

FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3103 Home Delivery Evening Delivery Surcharge

FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3104 *List Home Delivery Evening Delivery Surcharge

FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3107 Additional Handling Charge (AHS) / Non Standard Container Surcharge

FDXE/ FDXG

ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place. For Express, this field tag will contain any surcharges resulting from an Additional Handling Charge (AHS). For Ground, this field tag will contain any surcharges resulting from the use of a Non Standard Carrier.

3108 *List Additional Handling Charge (AHS) / Non Standard Container Surcharge

FDXE/ FDXG

ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place. For Express, this field tag will contain any surcharges resulting from an Additional Handling Charge (AHS). For Ground, this field tag will contain any surcharges resulting from the use of a Non Standard Carrier.

3109 Hazardous Materials Surcharge

FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3110 *List Hazardous Materials Surcharge

FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3111 Residential Surcharge FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3112 *List Residential Surcharge FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

Tagged Transaction Layouts – Transaction 122: Rate a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 38

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

3053 Multiweight Surcharge FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3054 Shipment Net Charge FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3115 *List Shipment Net Charge FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1421 COD Surcharge ALL ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place

1422 *List COD Surcharge ALL ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1423 Saturday Pickup Surcharge ALL ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1424 *List Saturday Pickup Surcharge

ALL ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1425 Declared Value Surcharge ALL ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1426 *List Declared Value Surcharge

ALL ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1682 Oversize surcharge ALL ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1683 List Oversize surcharge ALL ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1641 Return label surcharge ALL USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1643 *List Return label surcharge ALL USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

2390 Email Label surcharge ALL USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

Tagged Transaction Layouts – Transaction 122: Rate a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 39

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

2391 *List Email Label Surcharge ALL USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1672 FedEx Tag Surcharge ALL USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1673 *List FedEx Tag Surcharge ALL USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place

612 Harmonized Sales Tax (HST) Surcharge

ALL INTL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

613 Global Sales Tax (GST) Surcharge

ALL INTL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

614 Provincial Sales Tax (PST) Surcharge

ALL INTL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1434 Saturday Delivery Surcharge

FDXE ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1435 List Saturday Delivery Surcharge

FDXE ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1436 Dangerous Goods Surcharge

FDXE ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1437 List Dangerous Goods Surcharge

FDXE ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1438 Out of Pickup Area / H3 Surcharge

FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1439 List Out of Pickup Area / H3 Surcharge

FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1440 Out of Delivery Area / H3 Surcharge

FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1441 List Out of Delivery Area / H3 Surcharge

FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

Tagged Transaction Layouts – Transaction 122: Rate a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 40

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1442 Inside Pickup Surcharge FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1443 List Inside Pickup Surcharge

FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1444 Inside Delivery Surcharge FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1445 List Inside Delivery Surcharge

FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1446 Residential Delivery Surcharge

FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1447 List Residential Delivery Surcharge

FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1636 Delivery Area Surcharge ALL USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1637 List Delivery Area Surcharge

ALL USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1639 List Fuel Surcharge FDXE ALL Returned if applicable.

1640 FedEx International Controlled Export (FICE) Surcharge

FDXE INTL Returned if applicable.

1642 Value Added Tax FDXE ALL Returned if applicable.

1644 Offshore Surcharge FDXE INTL Returned if applicable.

1645 List Offshore Surcharge FDXE INTL Returned if applicable.

1649 Other Surcharges FDXE ALL Returned if applicable.

1650 List Other Surcharges FDXE ALL Returned if applicable.

1682 Oversize Surcharges FDXE ALL Returned if applicable.

1683 List Oversize Surcharges FDXE ALL Returned if applicable.

Tagged Transaction Layouts – Transaction 122: Rate a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 41

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

VARIABLE HANDLING

1428 Variable Handling Charge Amount

ALL ALL Contains the Handling Charge amount (in billing currency for the shipment) that was calculated based on Discounted freight (either Freight or Net freight as specified by Variable Handling Charge Type field) plus the value input in Variable Handling Charge. If Variable Handling Type is FIXED_AMOUNT, field will be equal to the Variable Charge. Format: Two explicit decimal positions (e.g. 5.00). 10 total length including decimal place.

1429 List Variable Handling Charge Amount

ALL ALL Contains the Handling Charge amount (in billing currency for the shipment) that was calculated based on List freight (either Freight or Net freight as specified by Variable Handling Charge Type field) plus the value input in Variable Handling Charge. If Variable Handling Type is FIXED_AMOUNT, field will be equal to the Variable Charge. Format: Two explicit decimal positions (e.g. 5.00). 10 total length including decimal place.

1430 Total Customer Charge ALL ALL Contains Shipper’s discounted Net Freight Charge (in the billing currency) plus Variable Handling Charge Amount. Will contain piece level or shipment level dependent on the Variable Handling Charge Level field. Format: Two explicit decimal positions (e.g. 5.00). 21 total length including decimal place.

1431 List Total Customer Charge ALL ALL Contains Shipper’s list Net Freight Charge (in the billing currency) plus Variable Handling Charge Amount. Will contain piece level or shipment level dependent on the Variable Handling Charge Level field. Format: Two explicit decimal positions (e.g. 5.00). 21 total length including decimal place.

3043 MTW Variable Handling FDXG ALL Handling charge returned to the customer calculated with multiweight freight. Format: Two explicit decimal positions (e.g. 5.00). 10 total length including decimal.

Tagged Transaction Layouts – Transaction 122: Rate a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 42

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

3113 MTW Customer Total Charge

FDXG ALL Shipper’s Freight charge plus Multiweight Variable Handling Charge Amount. Format: Two explicit decimal positions (e.g. 5.00). 21 total length including decimal.

TRANSACTION TERMINATOR

99 End Of Record ALL ALL Returned.

Tagged Transaction Layouts – Transaction 122: Rate a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 43

Example of Transaction 122: U.S. Domestic Rate a Package Reply

The following is an example of the Reply transaction format:

Data File Field Description

0,”122” Transaction Type 122 is Rate a Package Reply.

1,” Rate Transaction” Transaction Identifier. This field will be included in any error or Reply messages.

1419,”8.02” Net charge amount.

1416,”10.25” Base rate amount.

1417,”0.02” Total surcharge amount.

1418,”2.25” Total discount amount.

1402,”2.0” Bill Weight.

1403,”4.0” Dim Weight.

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 025: Rate Available Services Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 44

Transaction 025: Rate Available Services Request

Rate Available Services provides the ability to send a single Request in order to receive the FedEx service(s) available and corresponding rate quote(s) for your package, service, and origin/destination criteria.

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code ALL ALL

1 Customer Transaction Identifier

ALL ALL Optional. This field tag allows a FedEx customer to assign a unique identifier to a transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

10 Sender FedEx Account Number

ALL ALL The FedEx account number of the Sender is required to successfully receive a rate quote and Service Availability response.

498 Meter Number ALL ALL The unique meter number assigned to the Sender’s FedEx account number is required to successfully receive a rate quote and Service Availability response.

3025 Carrier Code ALL ALL Optional. If FDXE indicated, Express returned in Reply data. If FDXG indicated, Ground returned in Reply data. If blank, Express and Ground (if applicable/available) returned in Reply data.

ORIGIN

8 Sender State ALL ALL Required only if Sender Country Code is US or CA. Represents the state or province from which the shipment will be originating.

9 Sender Postal Code ALL ALL Required only if Sender Country Code is US or CA. Postal code may also be required for other postal-aware countries when rating an International shipment. Represents the postal code from which the shipment will be originating. Valid characters: A-Z; 0-9; a-z

Tagged Transaction Layouts – Transaction 025: Rate Available Services Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 45

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

117 Sender Country Code ALL ALL Required. Represents the country from which the shipment will be originating.

DESTINATION

16 Recipient State ALL ALL Required only if Recipient Country Code is US or CA. Represents the state or province to which the shipment is destined.

17 Recipient Postal Code ALL ALL Required only if Recipient Country Code is US or CA. Postal code may also be required for other postal-aware countries when rating an International shipment. Represents the postal code to which the shipment is destined. Valid characters: A-Z; 0-9; a-z

50 Recipient Country Code ALL ALL Required. Represents the country code to which the shipment is destined.

SHIPMENT DATE/TIME STAMP

24 Ship Date ALL ALL Required. The date in which the package will be shipped. Should not be a past date or a date that is more than 10 days in the future. Format: YYYYMMDD Defaults to current date if tag is omitted.

SHIPMENT/ PACKAGE INFORMATION

57 Dim Height ALL ALL Required if tag 1274 (Service Type) is not supplied or if Express heavyweight service is selected. Required if the package type (tag 1273) is 01 (Customer Packaging) or is not indicated.

58 Dim Width ALL ALL Required if tag 1274 (Service Type) is not supplied or if Express heavyweight service is selected. Required if the package type (tag 1273) is 01 (Customer Packaging) or is not indicated.

Tagged Transaction Layouts – Transaction 025: Rate Available Services Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 46

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

59 Dim Length ALL ALL Required if tag 1274 (Service Type) is not supplied or if Express heavyweight service is selected. Required if the package type (tag 1273) is 01 (Customer Packaging) or is not indicated.

68 Customs/Declared Value Currency Type

FDXE FDXG

INTL ALL

Required if tag 1415 (Declared Value/Carriage Value) is provided.

75 Weight Units ALL ALL Optional for Domestic. Required for International. Defaults to LBS for Domestic.

116 Package Total FDXE FDXG

ALL ALL

Required. FDXE only applies to COD, MPS, and International.

1116 Dim Units FDXE FDXG

ALL ALL

Required if dimensions are entered. Only applicable if Dims apply, tag 1273 (Package Type) is 01 (Customer Packaging), or tag 1274 (Service Type) is not indicated or indicates Heavyweight service. Defaults to IN for Domestic.

1273 FedEx Packaging Type ALL ALL Optional. Defaults to 01 (Customer Packaging).

1274 FedEx Service Type ALL ALL Optional. If not present, all available service types apply.

1401 Total Package Weight/ Shipment total weight

FDXE FDXG

USD ALL

Required. Used for MPS with tag 116 (Package Total).

1415 Declared Value/Carriage Value

ALL ALL Optional. Required for all shipments except FedEx Express International documents. The declared value of package contents. This value cannot exceed the total customs value.

RATE DATA

Tagged Transaction Layouts – Transaction 025: Rate Available Services Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 47

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1427 Variable Handling Charge ALL ALL Optional. Required in conjunction with Variable Handling Type.

1529 Rate Indicator FDXE FDXG

USD ALL

Optional.

1588 Variable Handling Type ALL ALL Optional. If valid value is present, a valid Variable Handling Charge is required.

1606 Variable Handling Charge Level

ALL ALL Optional. Only applicable if valid Variable Handling Type is present.

SPECIAL SERVICE

27 COD Flag FDXE FDXG

USD ALL

Y if shipment is COD. For Ground shipments, if the flag is Y and the customer is enabled by FedEx for Electronic COD (ECOD), then ECOD will take effect.

1432 COD Customer Amount FDXG ALL Required if COD Flag is set to Y.

3000 COD Collection Type FDXG ALL Required if the COD Flag is set to Y.

440 Residential Delivery Flag ALL ALL Y if shipment is Residential Delivery.

1120 Inside Pickup Flag FDXE USD Y if shipment is Inside Pickup.

1121 Inside Delivery Flag FDXE USD Y if shipment is Inside Delivery.

1174 BSO Flag FDXE INTL Y if shipment is BSO.

1200 HAL Flag FDXE ALL Y if shipment is Hold at Location.

1266 Saturday Delivery Flag FDXE ALL Y if shipment is targeted for Saturday delivery.

1267 Saturday Pickup Flag FDXE ALL Y if shipment is targeted for Saturday pickup.

1268 Dry Ice Flag FDXE ALL Y if shipment contains dry ice.

1331 Dangerous Goods Type FDXE ALL A if a shipment contains accessible dangerous goods, else I for inaccessible dangerous goods.

1332 Alcohol Flag FDXE ALL Y if shipment is alcohol. Else Optional.

Tagged Transaction Layouts – Transaction 025: Rate Available Services Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 48

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1333 Drop Off Type FDXE ALL Required.

2399 Signature Option ALL ALL Optional. Valid values:

1 = Deliver without Signature 2 = Indirect Signature 3 = Direct Signature 4 = Adult Signature

3015 Hazardous Materials Flag FDXG USD Y if shipment contains hazardous materials.

3018 Nonstandard Container Flag FDXG ALL Y if shipment packaging is a nonstandard container.

3020 FedEx Home Delivery Type FDXG USD Optional.

RETURNS

2382 Return Shipment Indicator FDXE/ FDXG

USD Required for return shipments. Valid values:

2 = Print Return Label 3 = Email Label

TRANSACTION TERMINATOR

99 End Of Record ALL ALL Required.

Tagged Transaction Layouts – Transaction 125: Rate Available Services Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 49

Transaction 125: Rate Available Services Reply

Rate Available Services provides the ability to send a single Request in order to receive the FedEx service(s) available and corresponding rate quote(s) for your package, service, and origin/destination criteria.

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code ALL ALL Required.

1 Customer Transaction Identifier

ALL ALL Optional. Returned if the customer included it in the Request, containing the same value.

ERROR HANDLING

2 Transaction Error Code ALL ALL Returned only if an error occurred while processing the transaction. For an erroneous Request or server failure, the error code will be placed in this tag.

3 Transaction Error Message

ALL ALL Returned only if an error occurred while processing the transaction. Passed back in response indicating failed processing. For an erroneous Request or server failure, the error code will be placed in this tag.

SOFT ERRORS The errors in this section are warnings, not fatal errors. May indicate inability to rate some services based on the specific information provided in the Request.

557 Message Type Code ALL ALL Returned only if a soft error occurred while processing the transaction.

558 Message Code ALL ALL Returned only if a soft error occurred while processing the transaction.

559 Message Text ALL ALL Returned only if a soft error occurred while processing the transaction.

SERVICE INFORMATION

1133 Service Availability Service Count

ALL ALL Returned if applicable. Maximum count is 22. Zero if none available.

Tagged Transaction Layouts – Transaction 125: Rate Available Services Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 50

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

RATING

431-# Dim Flag ALL ALL Y returned if Dim applies.

1089-# Rate Scale Code FDXE USD Returned if applicable.

1090-#

Rate Currency Type ALL ALL Express reflects currency of the sender’s account number (tag 10). Ground reflects currency of the origin country station.

1092 Rate Zone FDXE USD Returned if applicable.

1273 FedEx Packaging Type ALL ALL Returned if applicable.

1376 Rate Weight Unit Of Measure

FDXE

INTL For Domestic Requests, LBS will be returned. For International Requests, the unit of measure from the Request will be returned.

1377 Dim Weight Unit Of Measure

FDXE

INTL For Domestic Requests, LBS will be returned. For International Requests, the unit of measure from the Request will be returned.

1402-# Bill Weight ALL ALL Returned if applicable.

1403-# Dim Weight FDXE ALL Returned if applicable.

1416-# Base Rate Amount ALL ALL Returned if applicable.

1417-# Total Surcharge Amount ALL ALL Returned if applicable.

1418-# Total Discount Amount ALL ALL Returned if applicable.

1419-# Net Charge Amount ALL ALL Returned if applicable.

1420-# Total Rebate Amount FDXE ALL Returned if applicable.

1507 List Total Surcharge Amount

FDXE FDXG

USD ALL

Returned when tag 1529 (Rate Indicator) = 2. Sum of total surcharges.

1525 Effective Net Discount FDXE FDXG

USD ALL

Returned when tag 1529 (Rate Indicator) = 2. List Net Charge - Net Charge Amount.

Tagged Transaction Layouts – Transaction 125: Rate Available Services Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 51

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1528 List Net Charge Amount FDXE FDXG

USD ALL

Returned when tag 1529 (Rate Indicator) = 2. Rate + Surcharges - Discounts.

1530 List Base Rate Amount FDXE FDXG

USD ALL

Returned when tag 1529 (Rate Indicator) = 2. List base rate amount.

1531 List Total Discount Amount

FDXE FDXG

USD ALL

Returned when tag 1529 (Rate Indicator) = 2. List total discount amount (will always = 0)

1532 List Total Rebate Amount FDXE FDXG

USD ALL

Returned when tag 1529 (Rate Indicator) = 2. List total rebate amount (will always = 0)

1682 Oversize Surcharges FDXE ALL Returned if applicable.

1683 List Oversize Surcharges FDXE ALL Returned if applicable.

Tagged Transaction Layouts – Transaction 125: Rate Available Services Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 52

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

3124 Oversize Classification FDXG ALL Required. Valid values:

1 = A package weighing less than 30 lbs. and measuring more than 84" but equal to or less than 108" in combined length and girth will be classified by FedEx Ground as an Oversize 1 (OS1) package. The transportation charges for an Oversize 1 (OS1) package will be the same as a 30-lb. package being transported under the same circumstances. 2 = A package weighing less than 50 lbs. and measuring more than 108" but equal to or less than 130" in combined length and girth will be classified by FedEx Ground as an Oversize 2 (OS2) package. The transportation charges for an Oversize 2 (OS2) package will be the same as a 50-lb. package being transported under the same circumstances. 3 = A package weighing 150 lbs. or less and measuring more than 130" but equal to or less than 165" in combined length and girth will be classified by FedEx Ground as an Oversize 3 (OS3) package. The transportation charges for an Oversize 3 (OS3) package will be based on the greater of the package's actual rounded weight or a 90-lb. minimum billable weight. An additional oversize charge will be assessed on any package measuring more than 130" in length and girth.

VARIABLE HANDLING

1428 Variable Handling Charge Amount

ALL ALL Contains the Handling Charge amount (in billing currency for the shipment) that was calculated based on Discounted freight (either Freight or Net freight as specified by Variable Handling Charge Type field), plus the value input in Variable Handling Charge. If Variable Handling Type is FIXED_AMOUNT, field will be equal to the Variable Charge. Format: Two explicit decimal positions (e.g. 5.00). 10 total length including decimal place.

Tagged Transaction Layouts – Transaction 125: Rate Available Services Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 53

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1429 List Variable Handling Charge Amount

ALL ALL Contains the Handling Charge amount (in billing currency for the shipment) that was calculated based on List freight (either Freight or Net freight as specified by Variable Handling Charge Type field), plus the value input in Variable Handling Charge. If Variable Handling Type is FIXED_AMOUNT, field will be equal to the Variable Charge. Format: Two explicit decimal positions (e.g. 5.00). 10 total length including decimal place.

1430 Total Customer Charge ALL ALL Contains Shipper’s discounted Net Freight Charge (in the billing currency) plus Variable Handling Charge Amount. Will contain piece level or shipment level dependent on the Variable Handling Charge Level field. Format: Two explicit decimal positions (e.g. 5.00). 21 total length including decimal place.

1431 List Total Customer Charge

ALL ALL Contains Shipper’s list Net Freight Charge (in the billing currency) plus Variable Handling Charge Amount. Will contain piece level or shipment level dependent on the Variable Handling Charge Level field. Format: Two explicit decimal positions (e.g. 5.00). 21 total length including decimal place.

3043 MTW Variable Handling FDXG ALL Handling charge returned to the customer calculated with multiweight freight. Format: Two explicit decimal positions (e.g. 5.00). 10 total length including decimal place.

3113 MTW Customer Total Charge

FDXG ALL Shipper’s Freight charge plus Multiweight Variable Handling Charge Amount. Format: Two explicit decimal positions (e.g. 5.00). 21 total length including decimal place.

AVAILABLE SERVICES

194-# Delivery Day ALL USD For some postal supported countries, delivery will be returned if available.

195-# Destination Station ID FDXE USD Returned if applicable.

409-# Delivery Date ALL USD For some postal supported countries, delivery will be returned if available.

1273-# FedEx Packaging Type ALL ALL Returned if applicable.

Tagged Transaction Layouts – Transaction 125: Rate Available Services Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 54

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1274-# FedEx Service Type ALL ALL Returned if applicable.

2399-# Signature Option ALL ALL Optional.

2405-# Ineligible for MBG FDXG ALL Y if a shipment does not qualify for MBG (Money Back Guarantee).

3058-# Time in Transit FDXG USD Returned if applicable.

TRANSACTION TERMINATOR

99 End Of Record ALL ALL Returned.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 55

Transaction 021: Ship a Package Request

When sending a Ship a Package Request to the FedEx server, there is information that the server requires before it will process the Request.

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code ALL ALL Required.

1 Customer Transaction Identifier

ALL ALL Optional. This field allows a FedEx customer to assign a unique identifier to a transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

10 Sender FedEx Account Number

ALL ALL The FedEx account number of the Sender is required to successfully process a shipment Request.

498 Meter Number ALL ALL The unique meter number assigned to the Sender’s FedEx account number is required to successfully process a shipment Request.

3025 Carrier Code ALL ALL Required. Valid values:

FDXE – FedEx Express shipment Request FDXG – FedEx Ground shipment Request

ORIGIN

4 Sender Company ALL ALL Required if the sender contact name is not passed in the transaction. If included in the transaction, a minimum of 3 alpha characters must be passed.

5 Sender Address Line 1 ALL ALL Required. Primary address line from which the shipment is originating.

6 Sender Address Line 2 ALL ALL Optional. Secondary address line from which the shipment is originating.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 56

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

7 Sender City ALL ALL Required. City name from which the shipment is originating. Minimum of 3 alpha characters must be passed for shipping.

8 Sender State ALL ALL Required for shipping only if Country Code is US or CA. State code from which the shipment is originating.

9 Sender Postal Code ALL ALL Required for shipping only if Country Code is US or CA. May be required for other postal-aware countries when shipping internationally. Postal code from which the shipment is originating. Must be numeric for U.S. No embedded dashes allowed. Valid characters: A-Z; 0-9; a-z

32 Sender Contact Name ALL ALL Required if the sender Company Name is not passed in the transaction. If included in the transaction, a minimum of 3 alpha characters must be passed.

38 Sender Department ALL ALL Optional. Name of the department from which the shipment is originating.

117 Sender Country Code ALL ALL Required. Name of the country from which the shipment is originating.

183 Sender Phone Number ALL ALL Required. The phone number of the person initiating the shipment. The maximum length is 10 for US and CA, 16 for all other countries. Do not include embedded special characters.

1103 Sender Fax ALL ALL Optional. The fax number of the person initiating the shipment. The maximum length is 10 for US and CA, 16 for all other countries. Do not include embedded special characters.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 57

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1139 Sender SSN/EIN ALL INTL Required for any* International Shipment. If SSN/EIN Identifier (1352) = S then a 9-digit SSN is required. If SSN/EIN Identifier (1352) = E then a 9-digit plus 2-alpha EIN is required.

1201 Sender E-mail Address ALL ALL Optional. Required field for ShipAlert. The e-mail address of the person initiating the shipment.

1341 Sender Pager Number ALL ALL Optional. The pager number of the person initiating the shipment. The maximum length is 10 for US and CA, 16 for all other countries. Do not include embedded special characters.

DESTINATION

11 Recipient Company ALL ALL Required if Recipient Contact Name was not passed in the Request transaction. If entered, a minimum of 3 alpha characters must be passed.

12 Recipient Contact Name ALL ALL Required if Recipient Company Name was not passed in the Request transaction and COD service is selected. If passed in the transaction, a minimum of 3 alpha characters must be passed.

13 Recipient Address Line 1 ALL ALL Required. Primary address line to which the shipment is destined.

14 Recipient Address Line 2 ALL ALL Optional. Secondary address line to which the shipment is destined.

15 Recipient City ALL ALL Required. Name of the city to which the shipment is destined. A minimum of 3 alpha characters must be passed.

16 Recipient State ALL ALL Required only if Recipient Country Code is US or CA, or if SED applies and country is MX. State or province code to which the shipment is destined.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 58

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

17 Recipient Postal Code ALL ALL Required only if Recipient Country Code is US or CA. May be required for other postal-aware countries. Represents the postal code to which the shipment is destined. Valid characters: A-Z; 0-9; a-z

18 Recipient Phone Number ALL ALL Required. Phone number for the contact person to whom the shipment is destined. The maximum length is 10 for US and CA, 16 for all other countries. Do not include embedded special characters.

50 Recipient Country Code ALL ALL Required. Name of the country to which the shipment is destined.

118 Recipient SSN/EIN ALL INTL Optional.

1145 Recipient Department ALL ALL Optional. Name of the department to whom the shipment is destined.

1202 Recipient E-mail Address ALL ALL Optional. E-mail address for the contact person to whom the shipment is destined.

1342 Recipient Pager Number ALL ALL Optional. Pager number for the contact person to whom the shipment is destined. The maximum length is 10 for US and CA, 16 for all other countries. Do not include embedded special characters.

2254 Recipient Fax Number ALL ALL Optional. Fax number for the contact person to whom the shipment is destined. The maximum length is 10 for US and CA, 16 for all other countries. Do not include embedded special characters.

SHIPMENT DATE/TIME STAMP

24 Ship Date ALL ALL Required if Future Ship Date Flag is set to Y. Will be overridden by today’s date if Future Ship Date Flag is set to N Central Daylight Time (CDT). Should not be a past date or a date that is more than 10 days in the future. Format: YYYYMMDD

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 59

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1115 Ship Time ALL ALL Required. Time of shipment based on shipper's time zone. Defaults to the current time, CDT.

1119 Future Day Shipment Flag ALL ALL Required for FDXG. A value of N causes any passed Ship Date (tag 24) to be overridden by today’s date. If a value of Y is entered, the passed Ship Date will not be overridden. For FDXE, defaults to N. Y if shipment is scheduled for a future date. Date must be less than ten days in advance.

RATE DATA

1529 Rate Indicator FDXE FDXG

USD ALL

Optional.

PAYMENT

20 Payer Account Number ALL ALL For FedEx Express shipping, required if Pay Type is 2 (Bill Recipient) or 3 (Bill Third Party). For FedEx Ground shipping, required if Pay Type is 3 (Bill Third Party).

23 Pay Type ALL ALL Required. For Return Manager, only Bill Sender and Bill Third Party are allowed.

68 Customs/ Declared Value Currency Type

FDXE FDXG

INTL ALL

Required.

70 Duties Pay Type FDXE INTL Required for a dutiable International Express shipment. This field is not applicable to an International document Express shipment.

71 Duties Payer Account Number

FDXE INTL Required if Duties Pay Type is 3 (Bill Third Party).

1032 Duties Payer Country Code

FDXE INTL Optional.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 60

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

MULTIPLE-PIECE SHIPPING

116 Package Total (Total Number of Pieces)

FDXE FDXG

INTL ALL

Required for multiple-piece shipping. FDXE only applies to COD, MPS, and International.

1117 Package Sequence FDXE FDXG

INTL ALL

Required for multiple-piece shipping if Package Total (116) value is greater than 1.

1123 Master Tracking Number FDXE FDXG

INTL ALL

Required for multiple-piece shipping if Package Sequence (1117) value is greater than 1.

1124 Master Form ID FDXE ALL Required for multiple-piece shipping via the Express Server if Package Sequence (1117) value is greater than 1.

1400 Total Shipment Weight ALL INTL Required for International multiple-piece shipping. The Total Shipment Weight is in the Master only, not the Child. For example, piece “1 of n” pieces will have the total shipment weight of all the pieces.

SHIPMENT/ PACKAGE INFORMATION

25 Reference Information FDXE ALL Optional. This field allows customer-defined notes to print on the shipping label. Can also be used to Track By Reference. This field cannot be used if shipping alcohol. If used, customer-defined notes will be discarded.

57 Dim Height ALL ALL Required only if a FedEx Express heavyweight service is selected for the shipment. Recommended (but still optional) field if Your Packaging is used as Packaging Type (value 01 in field 1273).

58 Dim Width ALL ALL Required only if a FedEx Express heavyweight service is selected for the shipment. Recommended (but still optional) if Your Packaging is used as Packaging Type (value 01 in field 1273).

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 61

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

59 Dim Length ALL ALL Required only if a FedEx Express heavyweight service is selected for the shipment. Recommended (but still optional) field if Your Packaging is used as Packaging Type (value 01 in field 1273).

72 Terms Of Sale ALL INTL Required for a dutiable International Express shipment. This field is not applicable to an International document Express shipment.

73 Parties To Transaction FDXE INTL Required. A Y is required if the exporter and the consignee of the transaction are related. To determine if the parties are related, the company of the exporter and the company of the consignee have a parent/child relationship or either the exporter or consignee must have at least 10% ownership in the other (e.g. subsidiaries, branches of same company etc.).

75 Weight Units ALL ALL Required. Valid values: • LBS • KGS

190 Document Flag FDXE INTL Y if the shipment type is document. If multiple-piece shipment, this field must be set to Y in the Master transaction and all Child transactions.

2396 Document Description Code

FDXE INTL Required if field tag 190 (Document Flag) is set to Y. The code that represents the description of document.

413 NAFTA Flag FDXE INTL Y if NAFTA shipment, else N. May be applicable if origin and destination countries are US, CA, or MX.

1116 Dim Units ALL ALL Required if package dimensions are passed in the Request transaction. Defaults to inches if a value is not passed in the transaction.

1273 FedEx Packaging Type ALL ALL Required.

1274 FedEx Service Type ALL ALL Required.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 62

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1401 Total Package Weight ALL ALL Required for single and multiple-piece shipments. This is used for actual piece weight only, not total shipment weight. For multiple-piece shipments, this field must contain the actual piece weight for this package.

1411 Total Customs Value ALL INTL Required.

1415 Declared Value / Carriage Value

ALL ALL Optional for a U.S. Domestic, International dutiable Express, and Ground shipments. This field is not applicable to an International PIB (document) Express shipment. For Express International MPS Master piece should contain the total declared value/carriage value, with no declared value/carriage value in Child pieces. For example, piece “1 of n” pieces will have the total declared value/carriage value of all the pieces.

3001 FedEx Purchase Order ALL ALL Optional. If passed in the transaction, it can be used later to track by P.O. (Purchase Order).

3002 FedEx Invoice ALL ALL Optional. If passed in the transaction, it can be used later to track by Invoice.

3003 FedEx Customer Reference

ALL ALL Optional. If passed by the transaction, it can be used later to track by Reference.

VARIABLE HANDLING

1427 Variable Handling Charge ALL ALL Optional. Required in conjunction with Variable Handling Type.

1588 Variable Handling Type ALL ALL Optional. If valid value is present, a valid Variable Handling Charge is Required.

1606 Variable Handling Charge Level

ALL ALL Optional. Only applicable if valid Variable Handling Type is present.

3025 Carrier Code ALL ALL Required.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 63

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

SPECIAL SERVICE – COD

27 COD Flag FDXG FDXE

ALL USD

Y if shipment is COD. If Flag is Y and the customer is enabled by FedEx for Electronic COD (ECOD), then ECOD will take affect. Not allowed with Return Manager shipments.

186 COD Add Freight Flag FDXG FDXE

ALL USD

Required if the COD Flag is set to Y. Indicates that freight charges should be added to the COD collect amount. Accumulate these charges into the COD Amount for a single package:

1 = Add discounted rate to COD Amount 2 = Add list rate to COD Amount 3 = Add discounted COD Surcharge 4 = Add list COD Surcharge 5 = Add discounted **Customer Total Charge 6 = Add list **Customer Total Charge

Accumulate these charges into the COD Amount for a shipment: 7 = Add MTW Net Charge (shipment level) 8 = Add Discount Shipment Net Charge to last package in a Shipment 9 = Add List Shipment Net Charge to last package in a shipment.

Values 2, 4, 6 are only valid when Rate Indicator (tag 1529) = 2. Values 1, 3, 5, are valid when Rate Indicator (tag 1529) is not present or equals 1 or 2. Values 7-9 are only valid options for Ground MPS and have no dependency on the Rate Indicator.

1432 COD Customer Amount FDXE FDXG

USD ALL

Required if COD Flag is set to Y.

3000 COD Collection Type FDXG FDXE

ALL USD

Required if the COD Flag is set to Y.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 64

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

COD REMITTANCE

If shipping a COD single-piece shipment, the COD remittance fields may be passed in the 021 Request transaction. If shipping COD MPS, the COD remittance fields should be passed in the 021 Request transaction representing the last piece of the shipment. The COD Return Contact information will default to the Shipper Contact information if not provided in the 021 Request transaction.

28 COD Return Tracking Number

FDXE USD Required if the COD Flag is set to Y and the 021 shipment Request transaction represents the last piece in a multiple-piece shipment. This tracking number is returned in the 121 Reply of the first 021 Request of a COD shipment. Not applicable for non-MPS shipments.

439 COD Return Contact Name

ALL USD Required only if the COD Flag is set to Y and is different from the Sender.

1237 COD Return Phone ALL USD Required only if the COD Flag is set to Y and is different from the Sender.

1238 COD Return Company ALL USD Required only if the COD Flag is set to Y, is different from the Sender, and a COD contact name has not been entered.

1239 COD Return Department ALL USD Optional.

1240 COD Return Address 1 ALL USD Required only if the COD Flag is set to Y and is different from the Sender.

1241 COD Return Address 2 ALL USD Optional.

1242 COD Return City ALL USD Required only if the COD Flag is set to Y and is different from the Sender.

1243 COD Return State ALL USD Required only if the COD Flag is set to Y and is different from the Sender.

1244 COD Return Postal Code ALL USD Required only if the COD Flag is set to Y and is different from the Sender.

3045 COD Return Reference Indicator

FDXG USD Optional. This indicator determines which reference value will prints on the Ground shipping label.

SPECIAL SERVICE - HOME DELIVERY

3020 Home Delivery Type FDXG USD Optional.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 65

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

3021 FedEx Home Delivery Instructions

FDXG USD Optional.

3023 Home Delivery Date FDXG USD Required if home delivery type is set to 1, Date Certain.

3024 Home Delivery Phone Number

FDXG USD Required if home delivery type is set to 1, Date Certain, or 3, Appointment.

SPECIAL SERVICE – ALCOHOL (LIMITED TO AUTHORIZED SHIPPERS)

40 Alcohol Type FDXE ALL Required if the Alcohol Flag is set to Y.

41 Alcohol Packaging FDXE ALL Required if the Alcohol Flag is set to Y.

52 Alcohol Packages FDXE ALL Required if the Alcohol Flag is set to Y.

1332 Alcohol Flag FDXE ALL Y if shipment is alcohol, else N.

1405 Alcohol Volume FDXE ALL Required if the Alcohol Flag is set to Y.

SPECIAL SERVICE - HOLD AT LOCATION

44 HAL Address FDXE ALL Required if the Hold At Location Flag is set to Y.

46 HAL City FDXE ALL Required if the Hold At Location Flag is set to Y.

47 HAL State FDXE ALL Required if the Hold At Location Flag is set to Y and country is US or CA.

48 HAL Postal Code FDXE ALL Required if the Hold At Location Flag is set to Y and country is US or CA. May be required for other postal-aware countries when shipping internationally.

49 HAL Phone Number FDXE ALL Required if the Hold At Location Flag is set to Y. Required for freight shipping.

1200 HAL Flag FDXE ALL Y if shipment is Hold at Location.

SPECIAL SERVICE - DANGEROUS GOODS

1331 Dangerous Goods Type FDXE ALL A if shipment contains accessible dangerous goods, else I for inaccessible dangerous goods. If A or I sent, assumes shipment is Dangerous Goods.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 66

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

SPECIAL SERVICE - HAZARDOUS MATERIALS

3015 Hazardous Materials Flag FDXG

ALL

Y if shipment contains hazardous materials.

3066 Hazardous Materials DOT Shipping Name of Materials

FDXG ALL Required for OP-950. Optional if Hazardous Materials Flag is Y. (Can have blank or incorrect value.)

3085 Hazardous Materials DOT Shipping Name of Materials

FDXG ALL Required for OP-950. Optional if Hazardous Materials Flag is Y. (Can have blank or incorrect value.)

3086 Hazardous Materials DOT Shipping Name of Materials

FDXG ALL Required for OP-950. Optional if Hazardous Materials Flag is Y. (Can have blank or incorrect value.)

3067 DOT Hazard Class or Division Number

FDXG ALL Required for OP-950. Optional if Hazardous Materials Flag is Y. (Can have blank or incorrect value.)

3068 Hazardous Materials DOT ID Number

FDXG ALL Optional if Hazardous Materials Flag is Y. (Can have blank or incorrect value.)

3069 Hazardous Materials Packing Group

FDXG ALL Optional if Hazardous Materials Flag is Y. (Can have blank or incorrect value.)

3072 Hazardous Materials Type DOT Label(s)

FDXG ALL Optional. Type DOT Label(s) Required, Label(s) Required, Ltd., Qty., or Exemption Number. (Can have blank or incorrect value.)

3088 Hazardous Materials Quantity

FDXG ALL Required if Hazardous Materials Flag is Y. (Can have blank or incorrect value.)

3075 Hazardous Materials Emergency Contact Phone Number

FDXG ALL Required if Hazardous Materials Flag is Y. (Can have blank or incorrect value.)

3087 Hazardous Materials Emergency Contact Name

FDXG ALL Required if Hazardous Materials Flag is Y. (Can have blank or incorrect value.)

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 67

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

3089 Hazardous Materials Unit of Measure

FDXG ALL Optional for OP-950. (Can have blank or incorrect value.)

SPECIAL SERVICE - DRY ICE

1268 Dry Ice Flag FDXE ALL Y if shipment contains dry ice.

1406 Dry Ice Weight FDXE ALL Required if Dry Ice Flag is Y. Represents cumulative dry weight for the entire shipment. Cannot be greater than shipment weight. Weight type is KGS only.

SPECIAL SERVICE - ALERTS When requesting a ShipAlert in the 021 ship Request transaction, sender’s e-mail address (tag 1201), recipient’s e-mail address (tag 1220), broker’s e-mail address (1343), or E-mail Notification Address (1204) must be used in conjunction with the fields in this section.

1203 ShipAlert Optional Message

ALL ALL Optional.

1204-# E-mail Notification Address

ALL ALL For FDXE: • A minimum of one occurrence is required if tag 1206 (ShipAlert Flag) or

tag 1551 (Delivery Notification Flag) is Y. • A maximum of three occurrences is allowed for FedEx Express shipments

for ShipAlert or Delivery Alert Notification.

For FDXG: • One occurrence is required if tag 1206 (ShipAlert Flag) is Y and tag 3035

(ShipAlert Fax Number) is not included in the Request transaction. • Delivery Notification is not supported for FDXG.

Tag 1204 and tag 3035 (ShipAlert Fax Number) cannot both be selected for the same shipment Request transaction.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 68

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1206-# ShipAlert Notification Flag ALL ALL Required for ShipAlert. If = Y, corresponding e-mail address in tag 1204 (E-mail Notification Address) will be e-mailed ShipAlert. For FDXE: • Maximum of three occurrences allowed for FedEx Express shipments

(repeating, must use “-#”).

For FDXG: • One occurrence allowed for FedEx Ground shipments (non-repeating

must not use “-#”).

Not allowed with Return Manager shipments.

1551-# Delivery Notification Flag FDXE ALL Required for Delivery Notification. If = Y, corresponding e-mail address in field 1204 will be e-mailed delivery notification. Maximum of three occurrences allowed for FedEx Express shipments

1552-# Language Code FDXE ALL Optional for Delivery Notification. Applies to Delivery Alert for corresponding e-mail address in tag 1204. Maximum of three occurrences allowed for FedEx Express shipments. Valid values:

en = English fr = French

Defaults to en.

1553 Shipper Delivery Notification Flag

FDXE ALL Required for Delivery Notification to the shipper. If = Y, Sender’s E-mail Address (tag 1201), will be e-mailed Delivery Notification e-mail.

1554 Shipper ShipAlert Flag FDXE ALL Required for ShipAlert Notification to the shipper. If = Y, Sender’s E-mail Address (tag 1201) will be e-mailed ShipAlert e-mail.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 69

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1555 Shipper Language Code FDXE ALL Optional for Delivery Notification. Applies to Delivery Alert for shipper e-mail address. Valid values:

en = English fr = French

Defaults to en.

1556 Recipient Delivery Notification Flag

FDXE ALL Required for Delivery Notification to the recipient. If = Y, Recipient E-mail Address (tag 1202), will be e-mailed Delivery Notification e-mail.

1557 Recipient ShipAlert Flag FDXE ALL Required for ShipAlert Notification to the recipient. If = Y, Recipient’s E-mail Address (tag 1202) will be e-mailed ShipAlert e-mail.

1558 Recipient Language Code FDXE ALL Optional for Delivery Notification. Applies to Delivery Alert for recipient e-mail address. Valid values:

en = English fr = French

Defaults to en.

1559 Broker Delivery Notification Flag

FDXE INTL Required for Delivery Notification to the broker. If = Y, Broker E-mail Address (tag 1343) will be e-mail Delivery Notification e-mail.

1560 Broker ShipAlert Flag FDXE INTL Required for Delivery Notification to the broker. If = Y, Broker E-mail Address (tag 1343) will be e-mailed ShipAlert e-mail.

1561 Broker Language Code FDXE INTL Optional for Delivery Notification. Applies to Delivery Alert for broker e-mail address. Valid values:

en = English fr = French

Defaults to en.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 70

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

3035 ShipAlert Fax Number FDXG ALL Required if tag 1206 (ShipAlert Flag) is Y and tag 1204 (E-mail Notification Address) is not included. Tag 3035 and tag 1204 (E-mail Notification Address) cannot both be selected for the same shipment Request transaction.

SPECIAL SERVICE - SIGNATURE RELEASE

1118 Release Authorization Number

FDXE USD CAN

Required if Signature Release flag is Y.

OTHER SPECIAL SERVICES

440 Residential Delivery Flag FDXG FDXE

ALL USD

Required for Ground Home Delivery. Y if shipment is Residential Delivery. If Recipient Address is in a rural area (defined by table lookup), additional charge will be applied.

1120 Inside Pickup Flag FDXE USD Applicable to freight shipping only. Y if shipment is originated from an inside pickup area.

1121 Inside Delivery Flag FDXE USD Applicable to freight shipping only. Y if shipment is traveling to an inside delivery area.

1266 Saturday Delivery Flag FDXE ALL Y if shipment is to be delivered on Saturday.

1267 Saturday Pickup Flag FDXE ALL Y if shipment is to be picked up on Saturday.

1333 Drop Off Type FDXE ALL Required.

2399 Signature Option ALL ALL Optional. Valid values:

1 = Deliver without Signature 2 = Indirect Signature 3 = Direct Signature 4 = Adult Signature

3018 Nonstandard Container Flag

FDXG ALL Y if nonstandard container.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 71

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

ALTERNATE SENDER / RETURN INFO FOR LABEL

1485 Alternate Sender / Return Address Contact Name

ALL ALL Required if Alternate Sender/Return Address Flag = Y and Alternate Sender/Return Company Name is not present.

1486 Alternate Sender / Return Address Company Name

ALL ALL Required if Alternate Sender/Return Address Flag = Y and Alternate Sender/Return Contact Name is not present.

1487 Alternate Sender / Return Address Line 1

ALL ALL Required if Alternate Sender/Return Address Flag = Y.

1488 Alternate Sender / Return Address Line 2

ALL ALL Optional.

1489 Alternate Sender / Return Address City Name

ALL ALL Required if Alternate Sender/Return Address Flag = Y.

1490 Alternate Sender / Return Address State Code

ALL ALL Required if Alternate Sender/Return Address Flag = Y and Alternate Sender/Return Address Country Code is US or CA.

1491 Alternate Sender / Return Address Postal Code

ALL ALL Required if Alternate Sender/Return Address Flag = Y and Alternate Sender/Return address Country Code is US or CA. May be required for other postal-aware countries when shipping internationally.

1492 Alternate Sender / Return Address Phone Number

ALL ALL Required if Alternate Sender/Return Address Flag = Y.

1585 Alternate Sender / Return Address Country Code

ALL ALL Required if Alternate Sender/Return Address Flag = Y.

1586 Alternate Sender / Return Address Flag

ALL ALL Optional. Valid values: • Y • N If = Y, Alternate Sender/Return Address prints on label in the “sender” area. Defaults to N, sender address prints on label in the “sender” area.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 72

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1587 Alternate Sender / Return Address Department

ALL ALL Required if Alternate Sender/Return Address Flag = Y and Alternate Sender/Return Contact Name is not present.

2975 Mask Account Number Flag

ALL ALL Optional. Valid values.

N – Print the Account Number on Label Y – Default, do not print the Account Number on Label

CONFIGURABLE DOC TAB INFO FOR LABEL

2973 Doc Tab Type Indicator ALL ALL Required for doc-tab use on label. Valid values:

0 or not present – Ground Default Doc Tab. 1 – Zone 001 Doc Tab Format 2 – Barcoded Doc Tab (Code 128) Defaults to 0 (zero)

For the Zone 001 and the Ground Doc Tab Printing: • Header plus data combined can be up to 23 maximum length. If no

header, data can be 23. If no data, header can be 23. • The header will be truncated (down to a minimum of 4 characters not

including colon and space) as needed to accommodate printing the maximum characters of the associated data field.

1607 Doc Tab Header 1 ALL ALL Optional.

1608 Doc Tab Header 2 ALL ALL Optional.

1609 Doc Tab Header 3 ALL ALL Optional.

1610 Doc Tab Header 4 ALL ALL Optional.

1611 Doc Tab Header 5 ALL ALL Optional.

1612 Doc Tab Header 6 ALL ALL Optional.

1613 Doc Tab Header 7 ALL ALL Optional.

1614 Doc Tab Header 8 ALL ALL Optional.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 73

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1615 Doc Tab Header 9 ALL ALL Optional.

1616 Doc Tab Header 10 ALL ALL Optional.

1617 Doc Tab Header 11 ALL ALL Optional.

1618 Doc Tab Header 12 ALL ALL Optional.

1621 Customer Doc Tab Barcode

ALL ALL Required field if field tag 2973 (Doc Tab Type Indicator) has a value of 2, otherwise this is an optional field. Maximum of 30 characters to be encoded as a bar code on the Doc Tab of supported shipping labels.

1622 Customer Doc Tab Barcode Symbology

ALL ALL Required field if field tag 2973 (Doc Tab Type Indicator) has a value of 2, otherwise this is an optional field. Maximum of 30 characters to be encoded as a bar code on the Doc Tab of supported shipping labels.

1624 Doc Tab Data Field 1 ALL ALL Optional.

1625 Doc Tab Data Field 2 ALL ALL Optional.

1626 Doc Tab Data Field 3 ALL ALL Optional.

1627 Doc Tab Data Field 4 ALL ALL Optional.

1628 Doc Tab Data Field 5 ALL ALL Optional.

1629 Doc Tab Data Field 6 ALL ALL Optional.

1630 Doc Tab Data Field 7 ALL ALL Optional.

1631 Doc Tab Data Field 8 ALL ALL Optional.

1632 Doc Tab Data Field 9 ALL ALL Optional.

1633 Doc Tab Data Field 10 ALL ALL Optional.

1634 Doc Tab Data Field 11 ALL ALL Optional.

1635 Doc Tab Data Field 12 ALL ALL Optional.

1607 Doc Tab Header 1 ALL ALL Optional.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 74

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

RETURN SPECIFIC

2382 Return Shipment Indicator ALL USD Required for return shipments. Valid value:

2 = Print Return Label

2210 RMA Number ALL USD Optional. Return Merchandise Authorization (RMA).

FREIGHT SPECIFIC

1253 Packaging List Enclosed Flag

FDXE USD Optional. Y if packaging list is enclosed, else N.

1271 Shipper’s Load And Count (SLAC)

FDXE INTL Required for a single piece or on the first piece of an MPS for International freight shipping.

1272 Booking Confirmation Number

FDXE INTL Required for International freight shipping.

FORMS/ PRINTERS

1368 Label Type ALL ALL Required to indicate label formatting.

1369 Label Printer Type ALL ALL Required to indicate label formatting.

1370 Label Media Type ALL ALL Required to indicate label formatting.

BROKER

66 Broker Name ALL INTL Required if Broker Select Option (BSO) Flag is set to Y. Minimum of 3 alpha characters must be passed.

67 Broker Phone Number ALL INTL Required if Broker Select Option (BSO) Flag is set to Y.

1174 BSO Flag FDXE INTL Y if shipment is Broker Select Option. A flag value Y indicates that the package is to be shipped using a different broker than FedEx.

1179 Broker FedEx Account Number

FDXE INTL Optional.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 75

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1180 Broker Company ALL INTL Optional.

1181 Broker Address Line 1 ALL INTL Optional.

1182 Broker Address Line 2 ALL INTL Optional.

1183 Broker City ALL INTL Required if Broker Select Option (BSO) Flag is set to Y. Minimum of 3 alpha characters must be passed.

1184 Broker State ALL INTL Optional. Required field if Broker Country Code is US, CA, or MX.

1185 Broker Postal Code ALL INTL Required if Broker Select Option (BSO) Flag is set to Y and Broker Country Code is US and CA. May be required for other postal-aware countries when shipping internationally.

1186 Broker Country Code ALL INTL Required if BSO Flag is Y. Must be the same as the Recipient Country Code (field tag 50).

1187 Broker SSN/EIN FDXE INTL Optional.

1343 Broker Email Address FDXE INTL Optional.

1344 Broker Fax Number FDXE INTL Optional.

1345 Broker Pager Number FDXE INTL Optional.

COMMODITY (A maximum of twenty occurrences of commodity line item information is supported in this Request transaction.) For International multiple-piece shipments, this commodity information must be passed in the Master and each Child 021 transaction.

76-# Commodity Number Of Pieces

FDXE INTL At least one occurrence is required for International shipments.

79-# Commodity Description of Contents

FDXE INTL A minimum of three characters must be passed in the field. At least one occurrence is required for International. Maximum number of characters is 450. Please refer to Appendix C: Vague Commodity Descriptions for a list of appropriate commodity descriptions.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 76

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

80-# Commodity Country Of Manufacture

FDXE INTL At least one occurrence is required for International dutiable shipments. Country code where commodity contents were produced or manufactured in their final form.

81-# Commodity Harmonized Code

FDXE INTL At least one occurrence is required for U.S. Export shipments if the Customs Value is greater than $2500 or if a valid U.S. Export license is required.

82-# Commodity Unit Quantity FDXE INTL At least one occurrence is required for International dutiable shipments. This field is optional for an International PIB (document) Express shipment.

83-# Commodity Export License Number

FDXE INTL Required if commodity is shipped on commerce export license, Customs Value is greater than $2500, and International Traffic in Arms (ITAR), License Exception Symbol, and Foreign Trade Statistics Regulations (FTSR) are not supplied. Applicable to U.S. Export shipping only.

84-# Commodity Export License Expiration Date

FDXE INTL Required only if commodity is shipped on commerce export license, and Export License Number is supplied. Applicable to U.S. Export shipping only.

120-# CI Marks And Numbers FDXE INTL Optional. Applicable only if the commercial invoice flag is set to Y.

404-# Commodity License Exception Symbol

FDXE INTL At least one occurrence is required for U.S. Export shipments if the Customs Value is greater than $2500, and when export license, ITAR, and FTSR are not supplied.

414-# Commodity Unit Of Measure

FDXE INTL At least one occurrence is required for International dutiable shipments. This field is optional for an International PIB (document) Express shipment.

528-# Commodity ECCN FDXE INTL Required if the Export License Number is supplied or if the Commodity License Exception Symbol is supplied and does not indicate NLR or TMP.

601-# Commodity ITAR Exemption

FDXE INTL Optional. Applicable to U.S. Export shipping only.

1407-# Commodity Weight FDXE INTL At least one occurrence is required for International dutiable shipments. The weight of each unit of quantity.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 77

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1408-# Commodity Unit Value FDXE INTL At least one occurrence is required for International dutiable shipments. The value of each unit of quantity.

1410-# Commodity Customs Value

FDXE INTL At least one occurrence is required for International dutiable shipments. The commodity customs value should equal the commodity unit quantity times commodity unit value.

SHIPPER'S EXPORT DECLARATION (SED) - Applicable To U.S. Export Shipments Only.

The following AES (Automated Export System) data elements are required to be submitted to FedEx by the exporter or the exporter’s authorized agent prior to departure of the merchandise from the U.S. if an SED is required. Precedence for government issued licenses or exemptions for SED:

1. Export License 2. International Traffic Arms Regulation (ITAR) 3. License Exception Symbol 4. Foreign Trade Statistics Regulations (FTSR) 5. Custom Value

SED - GENERAL INFORMATION

1352 Sender EIN/SSN Indicator FDXE INTL Required for any International shipments. This field pairs with field 1139.

1358 AES/FTSR (Foreign Trade Statistics Regulations) Exemption

ALL INTL Express: Required for non-document U.S. Export Shipments. Ground: Required.

1391 Client Revision Indicator FDXE INTL-FDXE

Required. Value must be 2.

1399 AES Entry Number FDXE INTL Only required for commodities imported into the United States for export to a third-party country of destination.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 78

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

Canada Export Declaration B13A - Applicable to Canadian originating shipments only.

Required for any International non-document shipments originating in Canada destined for any country other than Canada, the United States, Puerto Rico or the U.S. Virgin Islands.

1651 B13A Filing Option ALL INTL Required for Canadian Export non-document shipments.

1652 Export Statement Data ALL INTL Used to indicate Export required data for any country.

1653 Export Permit Number ALL INTL Optional. Only applicable for any Canada export (International) non-document shipment.

COMMERCIAL INVOICE (CI)

113 Commercial Invoice Flag ALL INTL Y if required for electronic upload of CI data. It will serve to create/transmit an Electronic Commercial invoice through FedEx’s System. Customer will print their own Commercial Invoice. Commercial invoice support consists of a maximum of 4 commodity line items.

CI - GENERAL INFORMATION Applicable only if Commercial Invoice Flag (tag 113) is set to Y. 418-# CI Comments ALL INTL Maximum of four occurrences.

1297 Customer Invoice Number ALL INTL Optional.

1412 Freight Charge ALL INTL Required if Terms Of Sale is CF or CIF. This charge should be added to the total customs value amount.

1413 Insurance Charge ALL INTL Required if Terms Of Sale is CIF. This charge should be added to the total customs value amount.

1414 Taxes/ Miscellaneous Charge

ALL INTL Additional Charges is an optional entry for a dutiable International shipment only. No entry should be allowed for additional charges for an International document shipment. This charge should be added to the total customs value amount.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 79

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1958 Admissibility Package Type

ALL INTL Required if field tag 1273 (FedEx Packaging Type) is set to 01 – Other (Express) or Customer (Ground) packaging. Applicable for all origins to Canada (excluding Intra-Canada), CA to US, CA to PR, MX to US, and MX to PR.

2397 Purpose of Shipment Code

ALL INTL Optional. The code that represents the purpose of the shipment.

CI - IMPORTER

Applicable only if Commercial Invoice Flag (tag 113) is set to Y. If the consignee and importer are not the same, the importer fields are required. If some importer fields are provided in the 021 shipment Request, the following required fields must be provided as well.

169 Importer Country ALL INTL Required for Importer.

170 Importer Name ALL INTL Required for Importer.

171 Importer Company ALL INTL Required for Importer.

172 Importer Address Line 1 ALL INTL Required for Importer.

173 Importer Address Line 2 ALL INTL Optional.

174 Importer City ALL INTL Required for Importer.

175 Importer State ALL INTL Required if Importer Country Code is US or CA.

176 Importer Postal Code ALL INTL Required if Importer Country Code is US or CA. May be required for other postal-aware countries when shipping internationally.

177 Importer Account Number FDXE INTL Optional.

178 Importer Phone Number ALL INTL Required for Importer.

180 Importer SSN/EIN Number ALL INTL Optional.

INSIGHT CONTENT CAPTURE

1394 Shipment Content Records Total

ALL ALL Optional.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 80

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1395-# Part Number ALL ALL Optional. Repeating field up to 50 times per tracking #.

1396-# SKU/Item/UPC ALL ALL Optional. Repeating field up to 50 times per tracking #.

1397-# Receive Quantity ALL ALL Optional. Repeating field up to 50 times per tracking #.

1398-# Description ALL ALL Optional. Repeating field up to 50 times per tracking #.

INBOUND VISIBILITY

1392 Inbound Visibility Block Shipment Indicator

FDXE ALL Optional.

TRANSACTION TERMINATOR

99 End Of Record ALL ALL Required.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 81

Example of Transaction 021: Ship a Package Request (Domestic Express)

On Monday January 3, 2005, your customer, ABC Widget, requests a shipment of widget parts to be delivered. ABC Widget’s delivery address is 322 Latta Woods, Roanoke, VA, 24012. Their phone number is 703.555.1212. You are to send the package to the attention of Bernard F. Smith. The requested shipment is one piece, weighs a total of 4 pounds, and is being shipped using a FedEx Box. It should be sent via FedEx Express using the FedEx 2Day service. Your company is Total Widget Rebuilders, 445 East Street, Dallas, TX, 75247. Your phone number is 214.555.8765, and your FedEx account number is 123456789. The meter number is 1234567. Your input transaction is formatted as:

Data File Field Description

0,"021" Transaction Type 021 is Ship a Package Request.

1,"112301" Customer Transaction identifier. This field will be included in any error or Reply messages if you include it in the Request.

4,"Total Widget Rebuilders" Your (sender) company name.

5,"445 East Street" Your street address.

7,"Dallas" Your city name. Note that field tag 6 is not needed to complete your address.

8,"TX" Your state abbreviation.

9,"75247" Your ZIP code.

10,"123456789" Shipper’s account number.

498,”123567” Shipper’s meter number

1333,”1” Drop-off type is regular pickup

117,”US” Shipper’s country code.

183,"2145558765" Your phone number.

50,"US" Destination country code.

11,"ABC Widget" The destination company name.

12,"Bernard F. Smith" The destination contact name.

13,"322 Latta Woods" The destination street address.

14,"Suite 26" The destination suite number.

15,"Roanoke" The destination city name.

Tagged Transaction Layouts – Transaction 021: Ship a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 82

Data File Field Description

16,"VA" The destination state abbreviation.

17,"24012" The destination ZIP code.

18,"7035551212" The destination phone number.

23,"1" Payment code: 1 = Bill Sender.

1401,"4.0" The shipment weight, in pounds, one explicit decimal.

1273,"03" Packaging Type is FedEx Box.

1274,"03" Service selected is FedEx 2Day.

25,"SPECIAL CALL-IN" Your personal reference notes.

24,"20050103" Date of the shipment (January 3, 2005).

1115,"130555" Time of your shipment.

1368,”2” Standard label.

1369,”1” Label to print on Laser Printer.

1370,”5” Label to print on Plain Paper.

1116,”I” Dim Measurements unit is inches.

75,”LBS” Units of weight is LBS.

3025,”FDXE” Carrier Code, FDXE for FedEx Express.

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 121: Ship a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 83

Transaction 121: Ship a Package Reply

The following information is returned from the FedEx server after a U.S. Domestic ship a package Request has been processed:

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code ALL ALL Returned.

1 Customer Transaction Identifier

ALL ALL Optional. Returned if the customer included it in the Request transaction, containing the same value.

ERROR HANDLING

2 Transaction Error Code ALL ALL Returned only if an error occurred while processing the transaction. For an erroneous Request or server failure, the error code will be placed in this tag.

3 Transaction Error Message

ALL ALL Returned only if an error occurred while processing the transaction. Passed back in response indicating failed processing. For an erroneous Request or server failure, the error code will be placed in this tag.

557 Message Type Code FDXG ALL Returned only if a soft error/warning message is available.

558 Message Code FDXG ALL Returned only if a soft error/warning message is available.

559 Message Text FDXG ALL Returned only if a soft error/warning message is available.

TRACKING INFO

28 COD Return Tracking Number

FDXE USD Returned only for COD Express shipments.

29 Tracking Number ALL ALL Contains the tracking number assigned to the shipment if successful.

526 Form ID FDXE ALL Label form ID returned upon successful transaction Reply.

527 COD Return Form ID FDXE USD Returned only for COD and the first piece of a FedEx Express multiple-piece shipment.

Tagged Transaction Layouts – Transaction 121: Ship a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 84

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1123 Master Tracking Number FDXE INTL USD-COD

Returned if an International multiple-piece shipment or a U.S. Domestic COD multiple-piece shipment.

1124 Master Tracking Form ID FDXE INTL USD-COD

Returned if an International multiple-piece shipment or a U.S. Domestic COD multiple-piece shipment.

RATING INFO The rating information is only returned in the Reply for the last piece of a multiple-piece shipment. Only List Rates are returned in the Reply when field tag 1529 = 2 in the Request.

2399 Signature Option ALL ALL Optional.

2405 MBG Ineligible FDXG ALL Y if a shipment is ineligible for MBG (Money Back Guarantee).

431 Dim Weight Used Flag ALL ALL Y if the dimmed weight was used to derive freight charges.

1089 Rate Scale FDXE USD Returned.

1090 Currency Type FDXE ALL Returned.

1092 Rate Zone FDXE USD Returned.

1402 Bill Weight ALL ALL Billed weight for the shipment.

1403 Dim Weight FDXE USD DIM weight for the shipment.

1433 COD Collect Amount FDXE FDXG

USD ALL

Returns the final COD Amount when processing COD shipments.

1416 Base Rate Amount ALL ALL Base rate amount for the shipment.

1418 Total Discount Amount ALL ALL Total discount amounts applied to the shipment.

1417 Total Surcharge Amount ALL ALL Total surcharge amount returned for the shipment.

1419 Net Charge Amount ALL ALL Net charge amount returned.

1420 Total Rebate Amount FDXE USD Total rebate amount returned.

Tagged Transaction Layouts – Transaction 121: Ship a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 85

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1507 List Total Surcharge Amount

FDXE FDXG

USD ALL

Returned when tag 1529 (Rate Indicator) = 2. Sum of total surcharges.

1525 Effective Net Discount FDXE FDXG

USD ALL

Returned when tag 1529 (Rate Indicator) = 2. List Net Charge - Net Charge Amount

1528 List Net Charge Amount FDXE FDXG

USD ALL

Returned when tag 1529 (Rate Indicator) = 2. Rate + Surcharges - Discounts

1530 List Base Rate Amount FDXE FDXG

USD ALL

Returned when tag 1529 (Rate Indicator) = 2. List base rate amount.

1531 List Total Discount Amount

FDXE FDXG

USD ALL

Returned when tag 1529 (Rate Indicator) = 2. List total discount amount (will always = 0).

1532 List Total Rebate Amount FDXE FDXG

USD ALL

Returned when tag 1529 (Rate Indicator) = 2. List total rebate amount (will always = 0).

Tagged Transaction Layouts – Transaction 121: Ship a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 86

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

3124 Oversize Classification FDXG ALL Required Valid values:

1 = A package weighing less than 30 lbs. and measuring more than 84" but equal to or less than 108" in combined length and girth will be classified by FedEx Ground as an Oversize 1 (OS1) package. The transportation charges for an Oversize 1 (OS1) package will be the same as a 30-lb. package being transported under the same circumstances. 2 = A package weighing less than 50 lbs. and measuring more than 108" but equal to or less than 130" in combined length and girth will be classified by FedEx Ground as an Oversize 2 (OS2) package. The transportation charges for an Oversize 2 (OS2) package will be the same as a 50-lb. package being transported under the same circumstances. 3 = A package weighing 150 lbs. or less and measuring more than 130" but equal to or less than 165" in combined length and girth will be classified by FedEx Ground as an Oversize 3 (OS3) package. The transportation charges for an Oversize 3 (OS3) package will be based on the greater of the package's actual rounded weight or a 90-lb. minimum billable weight. An additional oversize charge will be assessed on any package measuring more than 130" in length and girth.

SURCHARGE INFO

612 Harmonized Sales Tax (HST) Surcharge

ALL INTL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

613 Global Sales Tax (GST) Surcharge

ALL INTL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

614 Provincial Sales Tax (PST) Surcharge

ALL INTL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1421 COD Surcharge ALL ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

Tagged Transaction Layouts – Transaction 121: Ship a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 87

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1422 *List COD Surcharge ALL ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1423 Saturday Pickup Surcharge

ALL ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1424 *List Saturday Pickup Surcharge

ALL ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1425 Declared Value Surcharge ALL ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1426 *List Declared Value Surcharge

ALL ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1434 Saturday Delivery Surcharge

FDXE ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1435 List Saturday Delivery Surcharge

FDXE ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1436 Dangerous Goods Surcharge

FDXE ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1437 List Dangerous Goods Surcharge

FDXE ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1438 Out of Pickup Area / H3 Surcharge

FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1439 List Out of Pickup Area / H3 Surcharge

FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1440 Out of Delivery Area / H3 Surcharge

FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1441 List Out of Delivery Area / H3 Surcharge

FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1442 Inside Pickup Surcharge FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

Tagged Transaction Layouts – Transaction 121: Ship a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 88

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1443 List Inside Pickup Surcharge

FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1444 Inside Delivery Surcharge FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1445 List Inside Delivery Surcharge

FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1446 Residential Delivery Surcharge

FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1447 List Residential Delivery Surcharge

FDXE USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1448 Priority Alert Surcharge FDXE USD Format: Two explicit decimal positions (e.g. 5.00).

1449 List Priority Alert Surcharge

FDXE USD Format: Two explicit decimal positions (e.g. 5.00).

1636 Delivery Area Surcharge FDXE USD Format: Two explicit decimal positions (e.g. 5.00).

1637 List Delivery Area Surcharge

FDXE USD Format: Two explicit decimal positions (e.g. 5.00).

1638 Fuel Surcharge FDXE ALL Format: Two explicit decimal positions (e.g. 5.00).

1639 List Fuel Surcharge FDXE ALL Format: Two explicit decimal positions (e.g. 5.00).

1640 FedEx International Controlled Export (FICE) Surcharge

FDXE INTL FedEx International Controlled Export Surcharge Amount. Format: Two explicit decimal places

1641 Return Label ALL USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1642 Value Added Tax FDXE ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1643 List Return Label Surcharge

ALL USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

Tagged Transaction Layouts – Transaction 121: Ship a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 89

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1644 Offshore Surcharge FDXE INTL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1645 List Offshore Surcharge FDXE INTL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1648 Europe First Surcharge FDXE INTL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1649 Other Surcharges ALL USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1650 List Other Surcharges FDXE ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1672 FedEx Tag Surcharge ALL USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1673 *List FedEx Tag Surcharge

ALL USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1682 Oversize Surcharges FDXE ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

1683 List Oversize Surcharges FDXE ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

2390 Email Label surcharge ALL USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

2391 *List Email Label Surcharge

ALL USD Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

2402 Signature Option Fee ALL ALL Returned when field tag 2399 (Signature Option) has a value of 2, 3, or 4.

2403 List Signature Option Fee ALL ALL Returned when field tag 2399 (Signature Option) has a value of 2, 3, or 4.

3095 Appointment Delivery Surcharge

FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3096 *List Appointment Delivery Surcharge

FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

Tagged Transaction Layouts – Transaction 121: Ship a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 90

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

3101 Home Delivery Date Certain Surcharge

FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3102 *List Home Delivery Date Certain Surcharge

FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3103 Home Delivery Evening Delivery Surcharge

FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3104 *List Home Delivery Evening Delivery Surcharge

FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3107 Additional Handling Charge (AHS) / Non Standard Container Surcharge

FDXE FDXG

ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3108 *List Additional Handling Charge (AHS) / Non Standard Container Surcharge

FDXE FDXG

ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3109 Hazardous Materials Surcharge

FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3110 *List Hazardous Materials Surcharge

FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3111 Residential Surcharge FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3112 *List Residential Surcharge

FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3053 Multiweight Surcharge FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

3054 Shipment Net Charge FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

Tagged Transaction Layouts – Transaction 121: Ship a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 91

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

3115 *List Shipment Net Charge FDXG ALL Format: Two explicit decimal positions (e.g. 5.00). 14 total length including decimal place.

VARIABLE HANDLING

1428 Variable Handling Charge Amount

ALL ALL Contains the Handling Charge amount (in billing currency for the shipment) that was calculated based on Discounted freight (either Freight or Net freight as specified by Variable Handling Charge Type field) plus the value input in Variable Handling Charge. If Variable Handling Type is FIXED_AMOUNT, field will be equal to the Variable Charge. Format: Two explicit decimal positions (e.g. 5.00). 10 total length including decimal place.

1429 List Variable Handling Charge Amount

ALL ALL Contains the Handling Charge amount (in billing currency for the shipment) that was calculated based on List freight (either Freight or Net freight as specified by Variable Handling Charge Type field) plus the value input in Variable Handling Charge. If Variable Handling Type is FIXED_AMOUNT, field will be equal to the Variable Charge. Format: Two explicit decimal positions (e.g. 5.00). 10 total length including decimal place.

1430 Total Customer Charge ALL ALL Contains shipper’s discounted Net Freight Charge (in the billing currency) plus Variable Handling Charge Amount. Will contain piece level or shipment level dependent on the Variable Handling Charge Level field. Format: Two explicit decimal positions (e.g. 5.00). 21 total length including decimal place.

1431 List Total Customer Charge

ALL ALL Contains shipper’s list Net Freight Charge (in the billing currency) plus Variable Handling Charge Amount. Will contain piece level or shipment level dependent on the Variable Handling Charge Level field. Format: Two explicit decimal positions (e.g. 5.00). 21 total length including decimal place.

Tagged Transaction Layouts – Transaction 121: Ship a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 92

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

3043 MTW Variable Handling FDXG ALL Handling charge returned to the customer calculated with multiweight freight. Format: Two explicit decimal positions (e.g. 5.00). 10 total length including decimal.

3113 MTW Customer Total Charge

FDXG ALL Shipper’s Freight charge plus Multiweight Variable Handling Charge Amount. Format: Two explicit decimal positions (e.g. 5.00). 21 total length including decimal.

ROUTING / ASTRA

30 URSA Routing Code FDXE ALL Applicable to a limited number of International countries for International shipping. Universal Routing and Sorting Aid (URSA) routing code returned for all U.S. Domestic shipments.

33 Service Commitment FDXE ALL Applicable to a limited number of International countries for International shipping.

65 Astra Barcode FDXE ALL Returned in a successful Reply.

194 Delivery Day ALL ALL Applicable to a limited number of International countries for International shipping.

195 Destination Station ID FDXE ALL Applicable to a limited number of International countries for International shipping.

409 Delivery Date ALL ALL Applicable to a limited number of International countries for International shipping.

535 COD Return ASTRA Barcode

FDXE USD Returned only for COD Express shipments. Returned only in the Reply for the last piece of a multiple-piece shipment.

536 COD Return Service Commitment

FDXE USD Returned only for COD Express shipments. Returned only in the Reply for the last piece of a multiple-piece shipment.

1136 URSA Prefix Code FDXE USD

1359 SED Legend Number FDXE INTL Returned only if SED applies.

LABEL BUFFER

Tagged Transaction Layouts – Transaction 121: Ship a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 93

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

188 Label Buffer Data Stream ALL ALL Returned only if tagged fields 1368, 1369, and 1370 were passed in the ship Request transaction.

411 COD Return Label Buffer Data Stream

FDXE FDXG

USD ALL

Returned for COD Express Domestic and Ground shipments.

1359 SED Legend Number FDXE INTL Returned if SED is filed for International shipments.

TRANSACTION TERMINATOR

99 End Of Record ALL ALL Returned.

Tagged Transaction Layouts – Transaction 121: Ship a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 94

Example of Transaction 121: Ship a Package Reply (Domestic Express)

In response to the previous shipping Request transaction, your Reply transaction would be formatted as follows:

Data File Field Description

0,”121” Transaction Type 121.

1,”112301” Transaction Identifier. This filed will be included in any error or Reply messages.

33,”A1” Service Commitment.

431,”N” Dim weight used flag.

30,”SE ROAA” URSA Code.

29,”470026455325” Tracking number.

526,”0201” Tracking form ID.

1402,”4.0” Billed weight.

1419,”4.94” Net charge amount.

1416,”14.50” Base rate amount.

1417,”.19” Total surcharge amount.

1418,”9.75” Total discount amount.

1090,”USD” Rate currency type.

1089,”00001” Rate scale.

1092,”3” Rate zone (Zone 0 A).

65,”32401265110000014700264553582016” ASTRA bar code data.

194,”WED” Delivery day.

195,”ROA” Destination station ID.

409,”05JAN00” Date to deliver package by (found on shipping label).

188,”(PNG Binary Data)” PNG label data buffer.

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 121: Ship a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 95

If the input transaction contains an error, an error message number and message text are included in the transaction Reply. If the destination state abbreviation in the example had been invalid, FedEx would respond with the following transaction:

Data File Field Description

0,"121" Transaction Type 121 is Ship a Package Reply.

1,"112301" Transaction identifier.

2,"4058" Error code.

3,"Invalid State Code" Error message.

99,”” The required transaction terminator. It must be the last pair in the transaction.

NOTE:

The error code and error messages are returned only when an error occurred or invalid data was sent with the original Request.

Tagged Transaction Layouts – Transaction 023: Delete a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 96

Transaction 023: Delete a Package Request

If you need to delete a package, you should send FedEx a delete Request. Your delete Request is formatted as follows:

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code ALL ALL Required.

1 Customer Transaction Identifier

ALL ALL Optional. This tag allows a FedEx customer to assign a unique identifier to a transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

10 Sender FedEx Account Number

ALL ALL The FedEx account number of the Sender is required to successfully process a shipment deletion Request.

498 Meter Number ALL ALL The unique meter number assigned to the Sender’s FedEx account number is required to successfully process a shipment deletion Request.

3025 Carrier Code ALL ALL Required. Valid values:

FDXE – FedEx Express FDXG – FedEx Ground

TRACKING

29 Tracking Number ALL ALL Required. Tracking number assigned to a package.

TRANSACTION TERMINATOR

99 End Of Record ALL ALL Required.

Tagged Transaction Layouts – Transaction 023: Delete a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 97

Example of Transaction 023: Delete a Package Request

After placing an order, your customer called to cancel the order. Since you have already processed the shipping transaction for this order, you will need to delete the package from your shipping log. To delete the shipment properly, you will create a transaction type 023 Delete a Package Request. Your input transaction is formatted as follows:

Data File Field Description

0,”023” Transaction Type 023.

1,”PO # 1234” Transaction Identifier. This field will be included in any error or Reply messages.

10,”123456789” Shipper FedEx account number.

29,”470012345678” Tracking number.

3025,”FDXE” Carrier Code, FDXE for FedEx Express.

498,”1234567” Meter number of the FedEx system.

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 123: Delete a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 98

Transaction 123: Delete a Package Reply

NOTE:

When shipping with FedEx Ground, you cannot delete a shipment once a Close operation has been performed. When shipping with FedEx Express, you must delete a shipment prior to the end of business.

When you Request FedEx to delete a package, your delete Reply is formatted as follows:

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code ALL ALL Returned.

1 Customer Transaction Identifier

ALL ALL Optional. Returned if the customer included it in the Request transaction, containing the same value.

ERROR HANDLING

2 Transaction Error Code ALL ALL Returned only if an error occurred while processing the transaction. For an erroneous Request or server failure, the error code will be placed in this tag.

3 Transaction Error Message ALL ALL Returned only if an error occurred while processing the transaction. Passed back in response indicating failed processing. For an erroneous Request or server failure, the error code will be placed in this tag.

TRANSACTION TERMINATOR

99 End Of Record ALL ALL Returned.

Tagged Transaction Layouts – Transaction 123: Delete a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 99

Example of Transaction 123: Delete a Package Reply

In response to the previous delete Request transaction, the following transaction is returned:

Data File Field Description

0,”123” Transaction Type 123 is Delete a Package Reply.

1,” PO # 1234” Transaction Identifier. This field will be included in any error or Reply messages.

99,”” The required transaction terminator. It must be the last pair in the transaction.

If the input transaction contains an error, an error message number and message text are included in the transaction Reply. If the destination state abbreviation in the example had been invalid, FedEx would respond with the following transaction:

Data File Field Description

0,"123" Transaction Type 123 is Delete a Package Reply.

1," PO # 1234" Transaction identifier.

2,"7099" Error code.

3,"No "Tracking Number” Error message.

99,”” The required transaction terminator. It must be the last pair in the transaction.

NOTE:

The error code and error messages are returned only when an error occurred or invalid data was sent with the original Request.

Tagged Transaction Layouts – Transaction 007: Close Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 100

Transaction 007: Close Request (Applicable to FedEx Ground Only)

This service allows a customer to Close out all shipments made for the day. Closing is a function to be used only for FedEx Ground shipments. Customers cannot cancel any shipments once they are Closed out. However, shipments can be added to a day's shipment after a Close has been performed and multiple Closes can be performed in a day.

The transaction begins when a customer sends a Request to Close out their shipment. The Reply transaction (107) includes the text buffer to produce the FedEx Ground Close Manifest.

Field Tag Field Name Field Requirements

STANDARD INFO

0 Transaction Code Required.

1 Customer Transaction Identifier Optional. This tag allows a FedEx customer to assign a unique identifier to a transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

10 Sender FedEx Account Number The FedEx account number of the Sender is required to successfully process a Close shipments Request.

498 Meter Number The unique meter number assigned to the Sender’s FedEx account number is required to successfully process a Close shipments Request.

3025 Carrier Code Required. Valid value:

FDXG – FedEx Ground Close Request

CLOSE

1007 Close/Manifest Date Required for Closing out a FedEx Ground shipping cycle.

1366 Close/Manifest Time Required for Closing out a FedEx Ground shipping cycle.

Tagged Transaction Layouts – Transaction 007: Close Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 101

Field Tag Field Name Field Requirements

1371 Report Only Request Flag Optional. Y if requesting a manifest from the last 3 days’ Closes. For example if you failed to print your Close Manifest, and you need the Manifest Data re-sent to you. N if Closing out a shipment cycle and creating the manifest. A default value of N is assumed if this field is not passed in the Request transaction. N or blank is the default. Indicates Close out current shipment cycle and create the manifest, MTW, HazMat Report. Y = Requesting a report generated from a previous Close. – Must indicate report in tag 3014. Note: Legacy behavior: Y = requesting a manifest from previous Close. N + 3014 = return report indicated for current Close (If N, operationally required reports 1, 2 and MTW are always returned.) Y + 3014 = return only the single report indicated for the previous Close cycle.

3014 Report Indicator Valid values: 1 = Ground Manifest report 2 = Ground HazMat report 3 = Ground COD report 4 = MTW (pending)

TRANSACTION TERMINATOR

99 End Of Record Required. Example: 99,””

Tagged Transaction Layouts – Transaction 007: Close Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 102

Example of Transaction 007: Close Request

By Closing, you send all the pertinent package information for this particular day to FedEx Ground. Closing will return to you the Shipping Manifest for that day. The FedEx Ground Server will keep track of all your shipments processed since your last Close transaction.

NOTE:

You CANNOT delete a package after it has been included in a Close transaction. However, you can Close many times in one day, as long as you are sure that you all the shipments since your last Close are final.

On Monday January 3, 2005, at 5:30 p.m., you have completed the processing of your outbound shipments and you are ready to Close your shipping activity with FedEx Ground. Your FedEx account number is 123456789. The meter number is 1234567. This is a Request to Close and get a Manifest. Your input transaction should be formatted as follows:

Data File Field Description

0,”007” Transaction Type 007 is Close Request.

1,”Daily Close” Transaction Identifier. This field will be included in any error or Reply messages.

10,” 123456789” Your account number.

498,”1234567” Your meter number.

3025,”FDXG” Carrier is FDXG, i.e. FedEx Ground.

1007,”20050103” Day of Close.

1366,”173000” Time of Close. This is a 24-hour clock.

1371,”N” N for Closing AND Requesting a Manifest.

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 107: Close Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 103

Transaction 107: Close Reply (Applicable to FedEx Ground Only)

Reply to the Close Request Transaction. The Close Reply brings back the ASCII Data Buffer which is used by the customer to print the Close Manifest. The Manifest is essential at time of pickup.

Field Tag Field Name Field Requirements

STANDARD INFO

0 Transaction Code Required.

1 Customer Transaction Identifier Optional. Returned if the customer included it in the Request transaction, containing the same value.

ERROR HANDLING

2 Transaction Error Code Returned only if an error occurred while processing the transaction. For an erroneous Request or server failure, the error code will be placed in this tag.

3 Transaction Error Message Returned only if an error occurred while processing the transaction. Passed back in response indicating failed processing. For an erroneous Request or server failure, the error code will be placed in this tag.

CLOSE

1005-# Manifest/Invoice File Name Returned in successful Reply. The number of field occurrences is dependent upon the value passed in Manifest Total (field 1372). File names of the Manifest(s) to be printed by the customer. (ASCII files)

1367-# Manifest Data Buffer Returned in successful Reply. The number of field occurrences is dependent upon the value passed in Manifest Total (field 1372).

1372 Manifest Total Returned in successful Reply. Number of Manifests to be printed, to be used in number of occurrences of fields 1005 and 1367.

1594 COD Report Buffer Ground COD Report Buffer. Format: Base 64 encoded ASCII

Tagged Transaction Layouts – Transaction 107: Close Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 104

Field Tag Field Name Field Requirements

3048 Multiweight Report Content Buffer This buffer will contain the multiweight report for FedEx Ground shipments. Format: Base 64 encoded ASCII

3114 Hazardous Materials Report Buffer

Contains the Hazardous Materials certification report. Format: Base 64 encoded ASCII

TRANSACTION TERMINATOR

99 End Of Record Transaction terminator.

Tagged Transaction Layouts – Transaction 107: Close Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 105

Example of Transaction 107: Close Reply

In response to the previous Closing Request transaction, and assuming that the previous was the second Closing transaction for that day, your Reply transaction would be formatted as follows:

Data File Field Description

0,”107” Transaction Type 107 is Close Reply.

1,”112301” Transaction Identifier. This filed will be included in any error or Reply messages.

1372,”2” Number of Manifest(s) for this customer/day.

1005-1,”Manifest1.txt” File name of the first manifest.

1005-2,”Manifest2.txt” File name of the second manifest.

1367-1,”(Data Buffer1)” Data buffer of the first manifest (text format contained within the buffer).

1367-2,”(Data Buffer2)” Data buffer of the second manifest (text format contained within the buffer).

99,”” The required transaction terminator. It must be the last pair in the transaction.

If the input transaction contains an error, an error message number and message text are included in the transaction Reply. If meter number were omitted in the example, FedEx would respond with the following transaction:

Data File Field Description

0,"107" Transaction Type 107 is Close Reply.

1,"112301" Transaction identifier.

2,"8029" Error code.

3,"Meter Number is required" Error message.

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 403: Track a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 106

Transaction 403: Track a Package Request

When sending a shipment tracking Request to the FedEx servers, there is information that the server requires before it will process the Request. The following fields can be sent to the FedEx server in order to track by number or track by reference:

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code ALL ALL Required.

1 Customer Transaction Identifier ALL ALL Optional. This tag allows a FedEx customer to assign a unique identifier to a transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

10 Sender FedEx Account Number ALL ALL Required if Track by Reference indicated in field 1538 (Search/Relationship Type Code). Optional for a Track Request. If Tracking Number is present, Track by Number is assumed and account number is optional.

498 Meter Number ALL ALL Optional.

3025 Carrier Code ALL ALL Required for Track by Reference. Optional for Track by Number.

TRACKING

24 Ship Date ALL ALL Optional, but recommended. The date in which the package was shipped. Should not be a future date or a date that is more than 90 days in the past. Ship date +/-5 days is allowed. Format: YYYYMMDD

50 Recipient Country Code FDXE ALL Optional, but recommended.

TRACK CONTROL FIELDS

Tagged Transaction Layouts – Transaction 403: Track a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 107

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1534 Detail Scan Indicator ALL ALL Optional. N or not present – defaults to Summary/Profile data, which includes one single scan structure with the most recent scan. Y – returns Detail Scan Activity (multiple scan structure) for each package.

Profile will return the last package status (most recent scan) and data elements other than the detail scan activity.

1537 Search / Relationship String ALL ALL Required. This field will contain the value to be tracked. If the FedEx Express Customer Reference is tracked, a maximum of 24 characters is allowed.

1538 Search / Relationship Type Code

ALL ALL Optional. This field will specify the type of track desired on the Search String (field tag 1537) field. Valid values:

0 or not present – defaults to Tracking Number/Door Tag 1 – FedEx Express MPS Master Number 2 – FedEx Express Track By Reference 3 – FedEx Ground Track By Reference – PO 4 – FedEx Ground Track By Reference – Customer Reference 5 – FedEx Ground Track By Reference – Invoice 7 – FedEx Ground Track By Reference – Shipment ID 36 – Return Materials Authorization

TRACK BY REFERENCE

1582 Begin Date ALL ALL Optional, but recommended. If provided, End Date (field tag 1583) is required. Recommend entry of date range to find desired results for reference tracking number. If not provided, results may vary. Format: YYYYMMDD

Tagged Transaction Layouts – Transaction 403: Track a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 108

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1583 End Date ALL ALL Optional, but recommended. If provided, Begin Date (field tag 1582) is required. If not provided, results may vary. Recommend entry of date range to find desired track number. Format: YYYYMMDD

PAGING/MULTIPLE REQUEST AND RESPONSES

1535 Paging Token ALL ALL Optional field. Required in order to obtain additional data on second and subsequent 403 Requests when more related tracking numbers exist that exceed the capacity of any one response structure. Applicable to Track By Reference, MPS, and Door Tag. This field should be absent from any first Track Request. It is only populated if the response results are in more than one page worth of data. If paging token contains value in first Reply, more tracking data exists. You should populate this field with the value returned in the previous 503 Reply. You should also populate the Search/Relationship String (field tag 1537) with original Request type 2 value.

TRANSACTION TERMINATOR

99 End Of Record ALL ALL Transaction terminator.

Tagged Transaction Layouts – Transaction 403: Track a Package Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 109

Example of Transaction 403: Track by Tracking Number

In order to track a package you have shipped via FedEx, the courier must scan the package before the package information has been entered into the FedEx database. If you have a package that has been scanned, you can track that package by formatting your tracking Request as follows:

Data File Field Description

0,”403” Transaction Type 403.

1,”112310” Transaction Identifier. This field will be included in any error or Reply messages.

498,”1234567” Meter number.

10,”123456789” FedEx account number.

24,”20050103” Date of the shipment (January 3, 2005).

50,”US” Recipient Country Code.

1534,”Y” Detail Scan Indicator.

1537,”470012345678” Search / Relationship String.

1538,”0” Search / Relationship Type Code.

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 503: Track a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 110

Transaction 503: Track a Package Reply

In response to the previous tracking Request transaction, your Reply transaction would be formatted as follows:

• ALL = All carriers (FedEx Express and FedEx Ground) • FDXE = FedEx Express only • FDXG = FedEx Ground only

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code ALL ALL Required.

1 Customer Transaction Identifier ALL ALL Returned if it was included in the Request transaction, containing the same value.

ERROR HANDLING

2 Transaction Error Code ALL ALL Passed back in response indicating failed processing. For an erroneous Request or server failure, the error code will be placed in this field tag.

3 Transaction Error Message ALL ALL Passed back in response transaction indicating failed processing. For an erroneous transaction, the error message will be placed in this field tag.

SOFT ERROR / WARNING MESSAGE

These Soft Error fields can repeat on a Track by Reference Reply. The number of repetitions corresponds to the number of matching tracking numbers. These fields will not repeat on a single track number Reply.

557-# Message Type Code ALL ALL Returned only if a soft error/warning message is applicable.

558-# Message Code ALL ALL Returned only if a soft error/warning message is applicable.

559-# Message Text ALL ALL Returned only if a soft error/warning message is applicable.

Tagged Transaction Layouts – Transaction 503: Track a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 111

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

TRACKING (NON-REPEATING)

These Tracking fields are non-repeating for both Track by Number and Track by Reference. Returned upon successful Reply only.

1584 Tracking Groups ALL ALL The number of tracking groups returned.

TRACKING (REPEATING)

These Tracking fields are non-repeating for Track by Number, but are repeating for Track by Reference Requests. Returned upon successful Reply only.

29-# Tracking Number ALL ALL Note: Door tag will never be returned in the response.

3025-# Carrier Code ALL ALL Specifies the particular carrier the package was shipped. Valid values:

FDXE – FedEx Express FDXG – FedEx Ground

15-# Recipient City ALL ALL

16-# Recipient State ALL ALL

17-# Recipient Postal Code ALL ALL Required only if Recipient Country Code is US or CA. May be required for other postal-aware countries. Represents the postal code to which the shipment is destined. Valid characters: A-Z; 0-9; a-z

24-# Ship Date ALL ALL Required. The date in which the package was shipped. Format: YYYYMMDD

50-# Recipient Country ALL ALL

1166-# Deliver To Code FDXE ALL Pairs with field tag 1705.

1705-# Deliver To Description FDXE ALL Pairs with field tag 1166.

Tagged Transaction Layouts – Transaction 503: Track a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 112

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1704-# Service Type Description ALL ALL A description of the service selected for the delivery of the package is returned within this tag.

1718-# Package Type Description FDXE ALL A description of the package type specified for the package delivered is returned within this tag.

1706-# Signed For ALL ALL Name of person which received possession of package.

1117-# Package Sequence FDXE INTL Sequence order number of package, only applicable for MPS.

116-# Total Package Count ALL ALL Number of packages in shipment. FDXE only applies to COD, MPS, and International.

75-# Weight Type ALL ALL KGS or LBS.

1401-# Total Package Weight ALL ALL Weight of the individual package.

DELIVERY COMMITS - RETURNED UPON SUCCESSFUL REPLY ONLY

1716-# Delivery Reattempt Date FDXE ALL Returned if Delivery Reattempt was made or a future delivery was scheduled.

1717-# Delivery Reattempt Time FDXE ALL Returned if Delivery Reattempt was made or a future delivery was scheduled.

1339-# Estimated Delivery Date ALL ALL Projected package delivery date based on ship date, service, and destination.

1340-# Estimated Delivery Time ALL ALL Projected package delivery time based on ship date, service, and destination.

1720-# Delivery Date ALL ALL Date when the package was delivered.

1707-# Delivery Time ALL ALL Time when the package was delivered.

RELATIONSHIP GROUP - RETURNED UPON SUCCESSFUL REPLY ONLY

1536-# Number of Relationships ALL ALL Number of relationships the “Search String” input into the 403 Request participates in.

Tagged Transaction Layouts – Transaction 503: Track a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 113

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1537-# Search/ Relationship String ALL ALL Relationship primary key corresponds to the relationship type code (field tag 1538) returned. Possible values: • Express master tracking number • Express customer reference • Ground PO • Ground customer reference • Ground invoice • Ground shipment ID

1538-# Search/ Relationship Type Code ALL ALL Identifies all relationships that the corresponding tracking number participates in. This field will correspond to the relationship string (field tag 1537).

SCAN DETAIL

If summary indicated, Tracking Detail Indicator = N. Only one occurrence of scan structure will occur.

Scan detail fields will repeat one to many times for each Tracking Number (except field tag 1715, Number of Tracking Activities). Scan order of appearance is determined by GMT time of scan. The scan date/times are local to the time zone of the event.

Returned upon successful Reply only.

1715-# Number Of Track Activities ALL ALL The Number of Track Activities is based on the number of scan activities.

1159-# Scan Description ALL ALL Literal description of the scan activity.

1171-# Scan Type Code ALL ALL Carrier’s scan code pairs with the description (i.e. DEX, PUP, HAL, etc.). For FedEx Ground, a value ‘=’ indicates Exception, Scan description is blank. See Exception code/description (field tags 1168 and 1711).

1168-# Status Exception Code ALL ALL Further defines the Scan Type Code’s specific type (i.e. DEX08 business closed). This field pairs with field tag 1711 (Status Exception Description).

Tagged Transaction Layouts – Transaction 503: Track a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 114

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1711-# Status Exception Description FDXE ALL The most recent status exception is returned if applicable. This field pairs with tag 1168 (Status Exception Code).

1160-# Scan Location City ALL ALL Name of the city where the shipment received scan.

1161-# Scan Location State Code ALL ALL State or province code where the shipment received scan.

1164-# Scan Location Country Code ALL ALL Returned if Recipient Country Code is US or CA. Country where the shipment received scan.

44-# Hold At Location Address Line 1 FDXE ALL This field will be populated when the most recent scan activity is a HAL scan. This field will not be populated if the package has been delivered. All other data will appear in the Scan Location fields if the scan is a HAL. These fields will appear just like other scans in the package history, regardless if delivered yet or not.

1162-# Scan Date ALL ALL Local date where scan occurred.

1163-# Scan Time ALL ALL Local time where scan occurred.

PAGING FIELDS - RETURNED UPON SUCCESSFUL REPLY ONLY.

1450 More Data Indicator ALL ALL A field value of Y indicates that more data exists.

1535 Paging Token ALL ALL Returned for Track by Reference, MPS, Door Tag only when more related tracking numbers exists that exceed the capacity of a single response. Only populated if the response results in more than one page worth of data. Client should populate paging token value in subsequent 403 tracking Request with the value returned in the previous 503 Reply.

TRANSACTION TERMINATOR

99 End Of Record ALL ALL Always returned.

Tagged Transaction Layouts – Transaction 503: Track a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 115

Example of Transaction 503: Track a Package Reply

In response to the previous tracking Request transaction, your Reply transaction is formatted as follows:

Data File Field Description

0,”503” Transaction Type 503.

1,”112310” Transaction Identifier. This field will be included in any error or Reply messages.

1117-1,”1” Package sequence number.

1159-1-1,”Delivered” First scan description for first tracking number.

1160-1-1,”Nashville” Scan location city associated with first scan description for first tracking number.

1161-1-1,”TN Scan location state associated with first scan description for first tracking number.

1162-1-1,”20050325” Scan date associated with first scan description for first tracking number.

1163-1-1,”084200” Scan time associated with first scan description for first tracking number.

1164-1-1,”US” Scan location country associated with first scan description for first tracking number.

1171-1-1,”20” Scan type code associated with first scan description for first tracking number.

1159-1-2,”On FedEx vehicle for delivery” Second scan description for first tracking number.

1160-1-2,”Nashville” Scan location city associated with second scan description for first tracking number.

1161-1-2,”TN Scan location state associated with second scan description for first tracking number.

1162-1-2,”20050325” Scan date associated with second scan description for first tracking number.

1163-1-2,”074100” Scan time associated with second scan description for first tracking number.

1164-1-2,”US” Scan location country associated with second scan description for first tracking number.

1171-1-2,”11” Scan type code associated with second scan description for first tracking number.

1159-1-3,”Arrived at FedEx destination location” Third scan description for first tracking number.

1160-1-3,”Nashville” Scan location city associated with third scan description for first tracking number.

1161-1-3,”TN Scan location state associated with third scan description for first tracking number.

1162-1-3,”20050325” Scan date associated with third scan description for first tracking number.

Tagged Transaction Layouts – Transaction 503: Track a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 116

Data File Field Description

1163-1-3,”070100” Scan time associated with third scan description for first tracking number.

1164-1-3,”US” Scan location country associated with third scan description for first tracking number.

1171-1-3,”02” Scan type code associated with third scan description for first tracking number.

1159-1-4,”Arrived at FedEx Ramp” Fourth scan description for first tracking number.

1160-1-4,”Nashville” Scan location city associated with fourth scan description for first tracking number.

1161-1-4,”TN Scan location state associated with fourth scan description for first tracking number.

1162-1-4,”20050325” Scan date associated with fourth scan description for first tracking number.

1163-1-4,”060300” Scan time associated with fourth scan description for first tracking number.

1164-1-4,”US” Scan location country associated with fourth scan description for first tracking number.

1171-1-4,”24” Scan type code associated with fourth scan description for first tracking number.

1159-1-5,”Left FedEx Sort Facility” Fifth scan description for first tracking number.

1160-1-5,”Memphis” Scan location city associated with fifth scan description for first tracking number.

1161-1-5,”TN Scan location state associated with fifth scan description for first tracking number.

1162-1-5,”20050325” Scan date associated with fifth scan description for first tracking number.

1163-1-5,”033800” Scan time associated with fifth scan description for first tracking number.

1164-1-5,”US” Scan location country associated with fifth scan description for first tracking number.

1171-1-5,”05” Scan type code associated with fifth scan description for first tracking number.

1159-1-6,”Left FedEx Sort Facility” Sixth scan description for first tracking number.

1160-1-6,”Memphis” Scan location city associated with sixth scan description for first tracking number.

1161-1-6,”TN Scan location state associated with sixth scan description for first tracking number.

1162-1-6,”20050325” Scan date associated with sixth scan description for first tracking number.

1163-1-6,”015400” Scan time associated with sixth scan description for first tracking number.

1164-1-6,”US” Scan location country associated with sixth scan description for first tracking number.

1171-1-6,”10” Scan type code associated with sixth scan description for first tracking number.

Tagged Transaction Layouts – Transaction 503: Track a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 117

Data File Field Description

1159-1-7,”Arrived at FedEx Sort Facility” Seventh scan description for first tracking number.

1160-1-7,”Memphis” Scan location city associated with seventh scan description for first tracking number.

1161-1-7,”TN Scan location state associated with seventh scan description for first tracking number.

1162-1-7,”20050325” Scan date associated with seventh scan description for first tracking number.

1163-1-7,”010100” Scan time associated with seventh scan description for first tracking number.

1164-1-7,”US” Scan location country associated with seventh scan description for first tracking number.

1171-1-7,”13” Scan type code associated with seventh scan description for first tracking number.

1159-1-8,”Left FedEx Origin Location” Eighth scan description for first tracking number.

1160-1-8,”Cordova” Scan location city associated with eighth scan description for first tracking number.

1161-1-8,”TN Scan location state associated with eighth scan description for first tracking number.

1162-1-8,”20050325” Scan date associated with eighth scan description for first tracking number.

1164-1-8,”US” Scan location country associated with eighth scan description for first tracking number.

1163-1-8,”235900” Scan time associated with eighth scan description for first tracking number.

1171-1-8,”01” Scan type code associated with eighth scan description for first tracking number.

1159-1-9,”Picked up by FedEx” Ninth scan description for first tracking number.

1160-1-9,”Cordova” Scan location city associated with ninth scan description for first tracking number.

1161-1-9,”TN Scan location state associated with ninth scan description for first tracking number.

1162-1-9,”20050325” Scan date associated with ninth scan description for first tracking number.

1163-1-9,”175200” Scan time associated with ninth scan description for first tracking number.

1164-1-9,”US” Scan location country associated with ninth scan description for first tracking number.

1171-1-9,”08” Scan type code associated with ninth scan description for first tracking number.

1166-1,”1” Deliver To Code for first tracking number.

1401-1,”1.0” Total package weight for first package.

15-1,”Nashville” Recipient city for first package.

Tagged Transaction Layouts – Transaction 503: Track a Package Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 118

Data File Field Description

1536-1,”1” Number of relationships for first package.

1537-1,”A9902301” Relationship string for first package.

1538-1-1,”2” Relationship type code for first package.

1584,”1” Tracking groups total is 1.

16-1,”TN” Recipient state code for first package.

17-1,”37243” Recipient postal code for first package.

1704-1,”Priority Overnight” Service type description for first package.

1705-1,”Receptionist/Front Desk” Deliver to description for first package.

1706-1,”L. Ragland” Signed for first package.

1707-1,”084200” Delivery time for first package.

1715-1,”9” Number of tracking activities for first package.

1718-1,”Your Packaging” Packaging type description for first package.

1720-1,”20050325” Delivery date for first package.

24-1,”20050324” Ship date for first package.

29-1,” 470012345678” Tracking number of first package.

3025-1,”FDXE” Carrier is FedEx Express for first package.

50-1,”US” Recipient country for first package.

75-1,”LBS” Weight type associated with total package weight (field tag 1401-1) of first package.

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 405: Signature Proof of Delivery Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 119

Transaction 405: Signature Proof of Delivery Request

When sending a shipment signature proof of delivery Request to the FedEx servers, there is information that the server requires before it will process the Request. The following fields can be sent to the FedEx server to obtain a signature proof of delivery:

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code ALL ALL Required.

1 Customer Transaction Identifier ALL ALL Optional. This field tag allows a FedEx customer to assign a unique identifier to a transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

10 Sender FedEx Account Number ALL ALL The FedEx account number of the Sender is required to successfully receive a Signature Proof of Delivery (SPOD) documentation.

498 Meter Number ALL ALL The unique meter number assigned to the Sender’s FedEx account number is required to successfully receive a SPOD documentation.

3025 Carrier Code ALL ALL Optional. Valid values:

FDXE – FedEx Express FDXG – FedEx Ground

TRACKING

24 Ship Date ALL ALL Required for FDXE. Optional for FDXG. The date of which package was shipped. For FDXE, +/- 5 days are allowed. Format: YYYYMMDD

29 Tracking Number ALL ALL Required.

SPOD

Tagged Transaction Layouts – Transaction 405: Signature Proof of Delivery Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 120

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1456 SPOD Request Type ALL U.S. & Canada

only

Required. The type of SPOD being Requested to be provided. Valid values:

L = Letter F = Fax

1457 SPOD Letter Format ALL U.S. & Canada

only

Required if SPOD Request Type = L (Letter).

SPOD FAX

1458 SPOD Fax Recipient Name ALL U.S. & Canada

only

Required if SPOD Request Type = F (Fax).

1459 SPOD Fax Recipient Number ALL U.S. & Canada

only

Required if SPOD Request Type = F (Fax).

1460 SPOD Fax Sender Name FDXE U.S. & Canada

only

Required if SPOD Request Type = F (Fax).

1461 SPOD Fax Sender Phone Number

FDXE U.S. & Canada

only

Required if SPOD Request Type = F (Fax).

1462 Language Indicator ALL U.S. & Canada

only

Optional. Defaults to EN if not present and Request type = L (Letter).

SPOD MAILING ADDRESS

1463 SPOD Fax Mail Recipient Name/Company Name

FDXG U.S. & Canada

only

Required if SPOD Request type = F (Fax).

Tagged Transaction Layouts – Transaction 405: Signature Proof of Delivery Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 121

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1464 SPOD Fax Mail Recipient Address Line 1

FDXG U.S. & Canada

only

Required if SPOD Request type = F (Fax).

1465 SPOD Fax Mail Recipient Address Line 2

FDXG U.S. & Canada

only

Optional. Applicable if SPOD Request type = F (Fax).

1466 SPOD Fax Mail Recipient City FDXG U.S. & Canada

only

Required if SPOD Request type = F (Fax).

1467 SPOD Fax Mail Recipient State FDXG U.S. & Canada

only

Required if SPOD Request type = F (Fax).

1468 SPOD Fax Mail Recipient Postal Code

FDXG U.S. & Canada

only

Required if SPOD Request type = F (Fax).

1469 SPOD Fax Mail Recipient Country

FDXG U.S. & Canada

only

Required if SPOD Request type = F (Fax).

SPOD GROUND CONFIGURABLE CONSIGNEE DATA

1472 SPOD Ground Recipient Name FDXG U.S. & Canada

only

Optional.

1473 SPOD Ground Recipient Company Name

FDXG U.S. & Canada

only

Optional.

1474 SPOD Ground Recipient Address line 1

FDXG U.S. & Canada

only

Optional.

Tagged Transaction Layouts – Transaction 405: Signature Proof of Delivery Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 122

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1475 SPOD Ground Recipient Address line 2

FDXG U.S. & Canada

only

Optional.

1476 SPOD Ground Recipient City FDXG U.S. & Canada

only

Optional.

1477 SPOD Ground Recipient State / Province

FDXG U.S. & Canada

only

Optional.

1478 SPOD Ground Recipient Postal Code

FDXG U.S. & Canada

only

Optional.

1479 SPOD Ground Recipient Country

FDXG U.S. & Canada

only

Optional.

1480 More Information FDXG U.S. & Canada

only

Optional.

TRANSACTION TERMINATOR

99 End Of Record ALL ALL Required.

Tagged Transaction Layouts – Transaction 405: Signature Proof of Delivery Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 123

Example of Transaction 405: Signature Proof of Delivery

In order to obtain a signature for a package that has been shipped via FedEx, the courier must have delivered the package and obtained a signature before the package information has been entered into the FedEx database. If you have a package that has been delivered and signed for, you can obtain the signature for that package by formatting your tracking Request as follows:

Data File Field Description

0,”405” Transaction Type 405.

1,”SPOD” Transaction Identifier. This field will be included in any error or Reply messages.

498,”1234567” Meter number.

10,”123456789” FedEx account number.

24,”20050103” Date of the shipment (January 3, 2005).

29,”470012345678” Tracking number.

1456,”L” SPOD Request type of letter.

1457,”1” SPOD letter format of PNG.

1462,”EN” Language indicator of English.

1472,”John Smith” SPOD recipient consignee name.

1473,”Smith, Inc” SPOD recipient company name.

1474,”103 Oak St.” SPOD recipient address line 1.

1475,”Suite 5” SPOD recipient address line 2.

1476,”Memphis” SPOD recipient city.

1477,”TN” SPOD recipient state.

1478,”38118” SPOD recipient postal code.

1479,”US” SPOD recipient country.

1480,”The signature” More information.

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 505: Signature Proof of Delivery Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 124

Transaction 505: Signature Proof of Delivery Reply

In response to the previous Signature Proof of Delivery Request transaction, your Request transaction would be formatted as follows:

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code ALL ALL Required.

1 Customer Transaction Identifier

ALL ALL Optional. Returned if the customer included a Unique Transaction Identifier in the Request transaction, containing the same value.

ERROR HANDLING

2 Transaction Error Code ALL ALL Returned only if an error occurred while processing the transaction. For an erroneous Request or server failure, the error code will be placed in this tag.

3 Transaction Error Message

ALL ALL Returned only if an error occurred while processing the transaction. Passed back in response indicating failed processing. For an erroneous Request or server failure, the error code will be placed in this tag.

SPOD

1457 SPOD Letter Format ALL U.S. & Canada

only

Returned from SPOD Request Type that was entered.

1470 SPOD Fax Confirmation Number

FDXE U.S. & Canada

only

Returned upon successful fax Request.

1471 SPOD Letter ALL U.S. & Canada

only

Returned if letter is selected. Binary Data Information %nn.

TRANSACTION TERMINATOR

99 End Of Record ALL ALL Transaction Returned.

Tagged Transaction Layouts – Transaction 505: Signature Proof of Delivery Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 125

Example of Transaction 505: Signature Proof of Delivery

In response to the previous Signature Proof of Delivery Request transaction, your Reply transaction would be formatted as follows:

Data File Field Description

0,”505” Transaction Type 505.

1,”SPOD” Transaction Identifier. This field will be included in any error or Reply messages.

1457,”1” SPOD letter format of PNG.

1471,”@PNG#A)1…” SPOD letter contents (PNG image).

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 505: Signature Proof of Delivery Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 126

Sample Signature Proof of Delivery (SPOD) Letter

Tagged Transaction Layouts – Transaction 410: FedEx Locator Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 127

Transaction 410: FedEx Locator Request

FedEx Locator allows a search to be performed for the nearest FedEx location through the API Gateway Server. FedEx Locator is limited to a maximum of ten locations returned within a 50-mile radius.

A search criterion higher in the following list will, when provided, override any criteria below it:

• Postal Code (plus optional street address or intersection) • City and State (plus optional street address or intersection) • Phone Number

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code ALL USD

1 Customer Transaction Identifier ALL USD Optional. This field tag allows a FedEx customer to assign a unique identifier to a transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

10 Sender FedEx Account Number ALL USD The FedEx account number of the Sender is required to successfully receive FedEx Location information.

498 Meter Number ALL USD The unique meter number assigned to the Sender’s FedEx account number is required to successfully receive FedEx Location information.

3025 Carrier Code ALL USD Optional. If FDXE indicated, Express returned in Reply data. If FDXG indicated, Ground returned in Reply data. If blank, Express and Ground (if applicable/available) returned in Reply data.

1697 Maximum Location Count ALL ALL Optional. Defaults to 10 if not specified. This allows the user to specify the maximum number of locations to be returned in the corresponding Reply transactions.

Tagged Transaction Layouts – Transaction 410: FedEx Locator Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 128

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1698 Beginning Record Index ALL ALL Optional. Defaults to 1 if not specified. This allows the user to specify the beginning record # to be returned in a single Reply transaction. Valid values: 0 - 500

SEARCH CRITERIA 1 Search will be based on phone number search criteria if Search Criteria two is NOT provided.

183 Sender Phone ALL USD Optional.

SEARCH CRITERIA 2 Search will be based on address/city/state/postal code search criteria if Search Criteria one is NOT provided. Search criteria two is not limited to sender address. Other addresses (ex. Recipient) may be used in tags 5, 7, 8, and 9 for the FedEx Locator transaction only.

5 Sender Address ALL USD Optional. Tag 1584 (Postal Code) OR tag 7 (Sender City) and tag 8 (Sender State) required with this tag. Address (ex. 5550 Main St.) or intersection (ex. Main at Second) can be entered for FedEx Locator only.

7 Sender City ALL USD Required if tag 8 (Sender State) is populated and tag 1584 (FedEx Location Postal Code) is not present.

8 Sender State ALL USD Required if tag 7 (Sender City) is populated and tag 1584 (FedEx Location Postal Code) is not present.

9 Sender Postal Code ALL USD Required if either tag 7 (Sender City) or tag 8 (Sender State) is not present.

Tagged Transaction Layouts – Transaction 410: FedEx Locator Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 129

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

117 Sender Country Code ALL ALL Optional. Defaults to US if not populated. Valid values: • US • CA

1555 Sender Language Code ALL ALL Optional. Defaults to EN if not populated. Valid values:

EN – English FR – French

1696 Distance Unit of Measure ALL ALL Optional. The Unit of measure for the distance returned. Defaults to MI if not populated. Valid values: • MI • KM

FEDEX LOCATOR DATA Tag 1562 (FedEx Staffed Location Flag), tag 1563 (FedEx Self-Service Location Flag), and tag 1564 (FASC Location Flag) are not mutually exclusive in one Request.

1562 FedEx Staffed Location Flag ALL USD Required if tag 1563 (FedEx Self-Service Location Flag) or tag 1564 (FASC Location Flag) is not present.

1563 FedEx Self -Service Location Flag

FDXE USD Required if tag 1562 (FedEx Staffed Location Flag) or tag 1564 (FASC Location Flag) is not present.

1564 FASC (FedEx Authorized Shipping Center) Location Flag

ALL USD Required if tag 1562 (FedEx Staffed Location Flag) or tag 1564 FedEx Self-Service Location Flag) is not present.

1200 Hold At Location Flag FDXE USD Optional.

1565 Latest Express Drop-off Flag FDXE USD Optional.

1566 Express Drop-off after time FDXE USD Optional.

Tagged Transaction Layouts – Transaction 410: FedEx Locator Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 130

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1580 Dangerous Goods Flag FDXE USD Optional.

1581 Saturday Service Flag FDXE USD Optional.

1693 Packaging Supplies Flag ALL USD Optional with sender country code set to US only. Packaging Supplies must be available at the location returned. Valid values:

Y for Yes, set this criteria N for No, don’t set this criteria

1694 Packaging Services Flag ALL USD Optional with sender country code set to US only. Packaging Services must be available at the location returned. Valid values:

Y for Yes, set this criteria N for No, don’t set this criteria

1695 FedEx Return System Flag ALL USD Optional with sender country code set to US only. Return Systems must be available at the location returned. Valid values:

Y for Yes, set this criteria N for No, don’t set this criteria

TRANSACTION TERMINATOR

99 End Of Record ALL USD Required.

Tagged Transaction Layouts – Transaction 410: FedEx Locator Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 131

Example of Transaction 410: Locator Request

In order to locate a drop-off location for your FedEx package, format your Locator Request as follows:

Data File Field Description

0,”410” Transaction Type 410.

1,”DropOff” Transaction Identifier. This field will be included in any error or Reply messages.

498,”1234567” Meter number.

10,”123456789” FedEx account number.

183,”9011234567” Sender phone number entered to search for nearest drop-off locations.

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 510: FedEx Locator Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 132

Transaction 510: FedEx Locator Reply

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code ALL USD Required.

1 Customer Transaction Identifier ALL USD Optional.

ERROR HANDLING

2 Transaction Error Code ALL USD Returned only if an error occurred while processing the transaction.

3 Transaction Error Message ALL USD Returned only if an error occurred while processing the transaction.

FEDEX LOCATOR DATA (Max of 25 occurrences.)

1574 Location Count ALL USD Returned in successful Reply.

1200-# Hold at Location Flag FDXE USD Y returned if FedEx Location supports hold at location.

1567-# FedEx Location Intersection/Street Address

ALL USD Returned in successful Reply.

1568-# Distance ALL USD Returned in successful Reply.

1569-# Hours of Operation Mon-Fri

ALL USD Returned in successful Reply.

1570-# Hours of Operation Sat

ALL USD Returned in successful Reply.

1571-# Last Express Drop-off Time Mon-Fri

FDXE USD Returned in successful Reply.

1572-# Last Express Drop-off Time Sat

FDXE USD Returned in successful Reply.

1573-# Express Service Flag FDXE USD Y returned if Express Service if available.

Tagged Transaction Layouts – Transaction 510: FedEx Locator Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 133

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1575-# FedEx Location Business Name

ALL USD Returned in successful Reply.

1576-# FedEx Location Business type ALL USD Returned in successful Reply.

1577-# FedEx Location City ALL USD Returned in successful Reply.

1578-# FedEx Location State ALL USD Returned in successful Reply.

1579-# FedEx Location Postal Code ALL USD Returned in successful Reply.

1580-# Dangerous Goods Flag FDXE USD Y returned if FedEx Location supports dangerous goods.

1693-# Packaging Supplies Flag ALL USD Y returned if FedEx Location supports Packaging Supplies.

1694-# Packaging Services Flag ALL USD Y returned if FedEx Location supports Packaging Supplies.

1695-# FedEx Return System Flag ALL USD Y returned if FedEx Location supports FedEx Returns.

1699 Record Index ALL ALL This is the individual records identifier of the “Total locations available.”

1700 Available Records Count ALL ALL The total number of locations that matched the input criteria.

3090-# Last Ground Drop-off Time Mon-Fri

FDXG USD Returned in successful Reply.

3091-# Last Ground Drop-off Time Sat

FDXG USD Returned in successful Reply.

3092-# Ground Service Flag FDXG USD Y returned if Ground Service if available.

TRANSACTION TERMINATOR

99 End Of Record ALL ALL Returned.

Tagged Transaction Layouts – Transaction 510: FedEx Locator Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 134

Example of Transaction 510: Locator Reply

Data File Field Description

0,”510” Transaction Type 510.

1,”DropOff” Transaction Identifier. This field will be included in any error or Reply messages.

1574,”2” Location Count.

1575-1,”Pak Mail” FedEx Location Business Name for first drop-off location.

1576-1,”FedEx Authorized Ship Center” FedEx Location Business Type for first drop-off location.

1567-1,”1016 W Poplar” FedEx Location Intersection/Street Address for first drop-off location.

1577-1,”Collierville” FedEx Location City Name for first drop-off location.

1578-1,”TN” FedEx Location State Code for first drop-off location.

1579-1,”38017” FedEx Location Postal Code for first drop-off location.

1568-1,”1.5” Distance to first drop-off location.

1569-1,”9:00 AM-6:00 PM” Hours of Operation for Mon-Fri at first drop-off location.

1570-1,”10:00 AM-2:00 PM” Hours of Operation on Saturday at first drop-off location.

1571-1,”4:00 PM” Last Express Drop-off Time for Mon-Fri at first drop-off location.

1572-1,”12:00 PM” Last Express Drop-off Time for Saturday at first drop-off location.

3090-1,”3:00 PM” Last Ground Drop-off Time for Mon-Fri at first drop-off location.

3091-1,”none” Last Ground Drop-off Time for Saturday at first drop-off location.

3092-1,”Y” FedEx Ground Service is available at first drop-off location.

1573-1,”Y” FedEx Express Service is available at first drop-off location.

1200-1,”N” FedEx Express Hold At Location service is supported at first drop-off location.

1580-1,”N” FedEx Express Dangerous Goods service is supported at first drop-off location.

1575-2,”FedEx staffed” FedEx Location Business Name for second drop-off location.

1576-2,”FedEx World Service Center” FedEx Location Business Type for second drop-off location.

Tagged Transaction Layouts – Transaction 510: FedEx Locator Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 135

Data File Field Description

1567-2,”1016 W Poplar Ste 105” FedEx Location Intersection/Street Address for second drop-off location.

1577-2,”Collierville” FedEx Location City Name for second drop-off location.

1578-2,”TN” FedEx Location State Code for second drop-off location.

1579-2,”38017” FedEx Location Postal Code for second drop-off location.

1568-2,”1.5” Distance to second drop-off location.

1569-2,”8:00 AM-10:00 PM” Hours of Operation for Mon-Fri at second drop-off location.

1570-2,”10:00 AM-5:00 PM” Hours of Operation on Saturday at second drop-off location.

1571-2,”10:00 PM” Last Express Drop-off Time for Mon-Fri at second drop-off location.

1572-2,”5:00 PM” Last Express Drop-off Time for Saturday at second drop-off location.

3090-2,”5:00 PM” Last Ground Drop-off Time for Mon-Fri at second drop-off location.

3091-2,”none” Last Ground Drop-off Time for Saturday at second drop-off location.

3092-2,”Y” FedEx Ground Service is available at second drop-off location.

1573-2,”Y” FedEx Express Service is available at second drop-off location.

1200-2,”Y” FedEx Express Hold At Location service is supported at second drop-off location.

1580-2,”N” FedEx Express Dangerous Goods service is supported at second drop-off location.

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 037: E-Mail Label Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 136

Transaction 037: E-Mail Label Request

A FedEx E-mail/Online Label is sent directly to the return shipper without exposing the FedEx customers account information. Returns Shippers print labels from their own printer using an application on fedex.com, place the label on the package, and drop-off or request pickup. Cancellations are handled via Cancel Email Label Request.

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code ALL USD Required.

1 Customer Transaction Identifier ALL USD Optional. This field allows a FedEx customer to assign a unique identifier to a transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

10 Sender FedEx Account Number ALL USD Required. The FedEx account number of the Sender is required to successfully receive an Email Label response.

498 Meter Number ALL USD Required. The unique meter number assigned to the Sender’s FedEx account number is required to successfully receive an Email Label response.

3025 Carrier Code ALL USD Required. Valid values:

FDXE – FedEx Express FDXG – FedEx Ground

RETURN SHIPPER / SENDER

4 Sender Company ALL USD Required if interfacing with remote Express or Ground Server and the Sender contact name is not passed in the transaction. Company from which the shipment is originating. A minimum of 3 alpha characters must be passed.

Tagged Transaction Layouts – Transaction 037: E-Mail Label Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 137

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

5 Sender Address Line 1 ALL USD Required. Primary address line from which the shipment is originating.

6 Sender Address Line 2 ALL USD Optional. Secondary address line from which the shipment is originating.

7 Sender City ALL USD Required. City name from which the shipment is originating. Minimum of 3 alpha characters must be passed for shipping.

8 Sender State ALL USD Required for shipping only if Country Code is US or CA. State code from which the shipment is originating.

9 Sender Postal Code ALL USD Required for shipping only if Country Code is US or CA. May be required for other postal-aware countries when shipping internationally. Postal code from which the shipment is originating. Must be numeric for US. No embedded dashes allowed. Valid characters: A-Z; 0-9; a-z

32 Sender Contact Name ALL USD Required if the sender Company Name is not passed in the transaction. If included in the transaction, a minimum of 3 alpha characters must be passed. Name of the person initiating the shipment.

117 Sender Country Code ALL USD Required. Name of the country from which the shipment is originating. Only US is allowed.

183 Sender Phone Number ALL USD Required. The phone number of the person initiating the shipment. The maximum length is 10 for US and CA, 16 for all other countries. Do not include embedded special characters.

1103 Sender Fax ALL USD Optional. The fax number of the person initiating the shipment. The maximum length is 10 for US and CA, 16 for all other countries. Do not include embedded special characters.

Tagged Transaction Layouts – Transaction 037: E-Mail Label Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 138

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1201 Sender’s E-mail Address

ALL USD Optional. Required field for ShipAlert. The e-mail address of the person initiating the shipment. ShipAlert and Delivery Notifications (if requested via use of tags 1553 and 1554) are sent to this address.

2392 URL E-mail Address

ALL USD Required. The e-mail label URL is sent to this e-mail address. The optional return shipper e-mail message (tag 2388) is also sent to this e-mail address.

1341 Sender Pager Number ALL USD Optional. The pager number of the person initiating the shipment. The maximum length is 10 for US and CA, 16 for all other countries. Do not include embedded special characters.

MERCHANT / DESTINATION

11 Recipient Company ALL USD Required if Recipient Contact Name was not passed in the Request transaction. Name of the company to whom the shipment is destined. If entered, a minimum of 3 alpha characters must be passed.

12 Recipient Contact Name ALL USD Required if Recipient Company Name was not passed in the Request transaction. Name of the person to whom the shipment is destined. If passed in the transaction, a minimum of 3 alpha characters must be passed.

13 Recipient Address Line 1 ALL USD Required. Primary address line to which the shipment is destined.

14 Recipient Address Line 2 ALL USD Optional. Secondary address line to which the shipment is destined.

Tagged Transaction Layouts – Transaction 037: E-Mail Label Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 139

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

15 Recipient City ALL USD Required. Name of the city to which the shipment is destined. A minimum of 3 alpha characters must be passed.

16 Recipient State ALL USD Required only if Recipient Country Code is US or CA, or if SED applies and country is MX. State or province code to which the shipment is destined.

17 Recipient Postal Code ALL USD Required only if Recipient Country Code is US or CA. May be required for other postal-aware countries. Represents the postal code to which the shipment is destined. Valid characters: A-Z; 0-9; a-z

18 Recipient Phone Number ALL USD Required. Phone number for the contact person to whom the shipment is destined. The maximum length is 10 for US and CA, 16 for all other countries. Do not include embedded special characters.

50 Recipient Country Code ALL USD Required. Name of the country to which the shipment is destined.

1202 Recipient E-mail Address ALL USD Optional. E-mail address for the contact person to whom the shipment is destined.

1342 Recipient Pager Number ALL USD Optional. Pager number for the contact person to whom the shipment is destined. The maximum length is 10 for US and CA, 16 for all other countries. Do not include embedded special characters.

2254 Recipient Fax Number ALL USD Optional. Fax number for the contact person to whom the shipment is destined. The maximum length is 10 for US and CA, 16 for all other countries. Do not include embedded special characters.

PAYMENT

20 Payer Account Number ALL USD Required field if Pay Type is 3 (Bill Third Party).

Tagged Transaction Layouts – Transaction 037: E-Mail Label Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 140

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

23 Pay Type ALL USD Required. Only Bill Sender and Bill Third Party are allowed.

EMAIL LABEL DATA

2387 URL Expiration date ALL USD Required. Date entered can be current date through current date plus thirty calendar days, (inclusive), from the date the e-mail label is requested. Format: YYYYMMDD

2388 URL Email Message ALL USD Optional. Contains a customized message from the merchant to the return shipper. Corresponds with field tag 2392.

2389 Merchant Contact Phone ALL USD Required. This phone number can differ from the merchant phone number for the shipment. This phone number is specific to the email label and will be used in case the return shipper needs to contact the merchant/recipient

3231 Residential Pickup Flag FDXG USD Optional for Ground email label Requests. Y pickup location is residential Default is N, pickup location is a business/commercial location. Field will be ignored on Express e-mail label Requests.

SHIPMENT INFORMATION

1273 FedEx Packaging Type ALL USD Required.

1274 FedEx Service Type ALL USD Required.

3021 Home Delivery Instructions FDXG USD Optional with Home Delivery service.

2210 RMA Number ALL USD Optional.

75 Weight Units ALL USD Required. This field defines the unit for the value declared in field tag 1401 (Package Weight). Must be LBS.

Tagged Transaction Layouts – Transaction 037: E-Mail Label Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 141

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1116 Dim Units ALL USD Required if package dimensions are passed in the Request transaction. Defaults to inches if a value is not passed in the transaction.

68 Declared Value Currency Type ALL USD Required. Must be USD.

116 Package Total (Total Number of Pieces)

ALL USD Required. Can contain 1-10 inclusive. FDXE only applies to COD, MPS, and International.

PACKAGE INFORMATION

(Can occur 1 – 10 times based on the value of field 116.)

1401-# Package Weight ALL USD Required. This field is used for piece weight only, not total shipment weight. Package weight must be in LBS as indicated by tag 75 (Weight Units).

57-# Dim Height ALL USD Required field only if a FedEx Express heavyweight service is selected for the shipment. Recommended (but still optional) field if Your Packaging is used as Packaging Type (value 01 in field 1273).

58-# Dim Width ALL USD Required only if a FedEx Express heavyweight service is selected for the shipment. Recommended (but still optional) field if Your Packaging is used as Packaging Type (value 01 in field 1273).

59-# Dim Length ALL USD Required only if a FedEx Express heavyweight service is selected for the shipment. Recommended (but still optional) field if Your Packaging is used as Packaging Type (value 01 in field 1273).

1415-# Declared Value / Carriage Value

ALL USD Optional for U.S. Domestic and Ground shipments. Field should contain the declared value per package.

Tagged Transaction Layouts – Transaction 037: E-Mail Label Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 142

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

2399 Signature Option ALL ALL Optional. Valid values:

1 = Deliver without Signature 2 = Indirect Signature 3 = Direct Signature 4 = Adult Signature

25-# Reference Information ALL USD Optional. This field allows customer-defined notes to print on the shipping label. If passed in the transaction, can later be used to track by reference.

3001-# FedEx Purchase Order ALL USD Optional. If passed in the transaction, can later be used to track by reference.

3002-# FedEx Invoice ALL USD Optional. If passed in the transaction, can later be used to track by reference.

1398-# Item Description ALL USD Required per piece. For Freight services, required per skid/label. For non-freight services, required package/label.

3018-# Nonstandard Container Flag FDXG USD Y if shipment packaging is a nonstandard container.

SPECIAL SERVICE – DRY ICE

1268-# Dry Ice Flag FDXE USD Y if package / Item contains dry ice, else N.

1406-# Dry Ice Weight

FDXE USD Required FOR EVERY PIECE if Dry Ice flag is Y. Represents dry weight for the package. Cannot be greater than package weight. Dry Ice weight type must be in KGS.

SPECIAL SERVICE – HOLD AT LOCATION

44 Hold At Location Address FDXE USD Required if the Hold At Location Flag is set to Y.

46 Hold at Location (HAL) City FDXE USD Required if the Hold At Location Flag is set to Y.

Tagged Transaction Layouts – Transaction 037: E-Mail Label Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 143

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

47 Hold at Location (HAL) State FDXE USD Required if the Hold At Location Flag is set to Y.

48 Hold at Location (HAL) Postal Code

FDXE USD Required if the Hold At Location Flag is set to Y.

1200 Hold at Location (HAL) Flag FDXE USD Y if shipment is Hold at Location, else N.

SPECIAL SERVICE – ALERTS

1203 ShipAlert Optional Message ALL USD Optional.

1204-# E-mail Notification Address ALL USD For FDXE: • A minimum of one occurrence is required if tag 1206 (ShipAlert Flag)

or tag 1551 (Delivery Notification Flag) is Y. • Maximum of three occurrences allowed for FedEx Express shipments

for ShipAlert or Delivery Alert Notification. For FDXG: • One occurrence is required if tag 1206 (ShipAlert Flag) is Y and tag

3035 (ShipAlert Fax Number) is not included in the Request transaction.

• Delivery Notification is not supported for FDXG. Tag 1204 and tag 3035 (ShipAlert Fax Number) cannot both be selected for the same shipment Request transaction.

1206-# ShipAlert Flag ALL USD Required for ShipAlert. If = Y, corresponding e-mail address in tag 1204 (E-mail Notification Address) will be e-mailed ShipAlert. For FDXE: Maximum of three occurrences allowed for FedEx Express shipments (repeating, must use “-#”). For FDXG: One occurrence allowed for FedEx Ground shipments (non-repeating must not use “-#”).

Tagged Transaction Layouts – Transaction 037: E-Mail Label Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 144

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1551-# Delivery Notification Flag FDXE USD Required for Delivery Notification. If = Y, corresponding e-mail address in field 1204 will be e-mailed delivery notification. Maximum of three occurrences allowed for FedEx Express shipments

1552-# Language Code FDXE USD Optional for Delivery Notification. Applies to Delivery Alert for corresponding e-mail address in tag 1204. Maximum of three occurrences allowed for FedEx Express shipments. Defaults to en.

1553 Shipper Delivery Notification Flag

FDXE USD Required for Delivery Notification to the shipper. If = Y, Sender’s E-mail Address (tag 1201) will be e-mailed Delivery Notification e-mail.

1554 Shipper ShipAlert Flag FDXE USD Required for ShipAlert Notification to the shipper. If = Y, Sender’s E-mail Address (tag 1201) will be e-mailed ShipAlert e-mail.

1555 Shipper Language Code FDXE USD Optional for Delivery Notification. Applies to Delivery Alert for shipper e-mail address. Defaults to en.

1556 Recipient Delivery Notification Flag

FDXE USD Required for Delivery Notification to the recipient. If = Y, Recipient E-mail Address (tag 1202) will be e-mailed Delivery Notification e-mail.

1557 Recipient ShipAlert Flag FDXE USD Required for ShipAlert Notification to the recipient. If = Y, Recipient’s E-mail Address (tag 1202) will be e-mailed ShipAlert e-mail.

1558 Recipient Language Code FDXE USD Optional for Delivery Notification. Applies to Delivery Alert for recipient e-mail address. Defaults to en.

3035 ShipAlert Fax Number FDXG USD Required if tag 1206 (ShipAlert Flag) is Y and tag 1204 (E-mail Notification Address) is not included. Tag 3035 and tag 1204 (E-mail Notification Address) cannot both be selected for the same shipment Request transaction.

Tagged Transaction Layouts – Transaction 037: E-Mail Label Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 145

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

SPECIAL SERVICE – OTHER

1118 Release Authorization Number FDXE USD Required if Signature Release flag is Y.

440 Residential Delivery Flag FDXE FDXG

USD Y if shipment is Residential Delivery, else N.

1120 Inside Pickup Flag FDXE FDXG

USD

Y if shipment is Inside Pickup, else N. Applicable to freight shipping only.

1121 Inside Delivery Flag FDXE

USD

Y if shipment is Inside Delivery, else N. Applicable to freight shipping only.

1690 Saturday Delivery Allowed Flag FDXE USD If set = Y, this field indicates that the merchant has agreed to allow the return shipment to be delivered back to him (or a repair/return center) on Saturday, and the merchant agrees to pay the Saturday delivery surcharge. If = Y and it is Friday when the return shipper generates their label, and service type is overnight, Saturday Delivery will be assumed. If it is Thursday when the return shipper generates their label, and the service type is two day, then Saturday Delivery will be assumed.

1646 Saturday Pickup Allowed Flag FDXE USD If set = Y, this field indicates that the merchant has agreed to allow the return shipment to be picked up on Saturday, and the merchant agrees to pay the Saturday pickup surcharge. If the return shipper generates the label on a Friday and this field = Y, Saturday pickup is assumed and is the only option. If = N, pickup date is assumed to be the next FedEx business day.

1333 Drop Off Type FDXE USD Required.

1392 Inbound Visibility Block Shipment Indicator

FDXE USD Optional.

TRANSACTION TERMINATOR

99 End Of Record ALL ALL Required.

Tagged Transaction Layouts – Transaction 037: E-Mail Label Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 146

Example of Transaction 037: Email Label Request

In order to create an E-mail Label in which another party can retrieve the label online for their FedEx package, format your E-mail Label Request as follows:

Data File Field Description

0,"037" Transaction Type 037 is Email Label Request.

1,"Email Label" Customer Transaction identifier. FedEx will return to you the same identifier you send in.

10, “000000000” Sender Account Number.

498, “0000000” Meter Number.

3025, “FDXG” Carrier Code.

4, “WAPI” Sender Company Name.

5, “5767 E Shelby Dr” Sender Address 1.

7, “Memphis” Sender City.

8, “TN” Sender State/Province.

9, “38141” Sender Postal Code.

8, “TN” Sender State/Province.

9, “38141” Sender Postal Code.

117, “US” Sender Country.

32, “WAPI-TEST-CL” Sender Contact Name.

38, “ WAPI” Sender Department.

183, “8004633339” Sender Phone Number.

1201, “[email protected]” Sender's Email Address.

11, “WAPI” Recipient Company Name.

12, “WAPI-TEST-CL” Recipient Contact Name.

13, “80 FEDEX PRKWY” Recipient Address 1.

15, “DETROIT” Recipient City.

Tagged Transaction Layouts – Transaction 037: E-Mail Label Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 147

Data File Field Description

16, “MI” Recipient State/Province.

17, “48204” Recipient Postal Code.

18, “8004633339” Recipient Phone Number.

50, “US” Recipient Country Code.

20, “1010101010” Payer Account Number.

23, “1” Payment Code.

1116, “I” Dim Units.

1117, “1” Package Sequence.

1119, “N” Future Day Flag.

116, “1” Total Number of Packages.

1273, “01” Packaging Type.

1274: 90 Service Type.

1333, “1” Drop Off Type.

1368, “2” Label Type.

1369, “1” Label Printer Type.

1370, “5” Label Orientation.

1398, “Books” Item Description.

1400, “0.0” Total Shipment Weight.

1401, “70.0” Total Package Weight.

1415, “40.00” Declared Value/Carriage Value.

2382, “3” Return Shipment Indicator.

2387, “20051030” URL Expiration Date.

2389, “8004633339” Merchant Contact Phone Number.

2392, “[email protected]” URL E-Mail Address.

Tagged Transaction Layouts – Transaction 037: E-Mail Label Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 148

Data File Field Description

3018, “Y” Non-Standard Packaging Flag.

3024, “8004633339” Home Delivery Phone Number.

440, “Y” Residential Delivery Flag.

57, “2” Dim Package Height.

58, “2” Dim Package Width.

59, “62” Dim Package Length.

68, “USD” Customs/Declared Value Currency Type.

75, “LBS” Weight Type/Unit of Measure.

24, “20051012” Ship Date.

25, “D-ANY-F42953GRD12” Reference Info.

99,”” Transaction terminator.

Tagged Transaction Layouts – Transaction 137: E-Mail Label Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 149

Transaction 137: E-Mail Label Reply

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code ALL USD Required.

1 Customer Transaction Identifier

ALL USD Optional. Returned containing the same value if the customer included information for this tag in the Request transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

ERROR HANDLING

2 Transaction Error Code ALL USD Returned only if an error occurred while processing the transaction. Passed back in response indicating failed processing. For an erroneous Request or a server failure, the error code will be placed in this tag.

3 Transaction Error Message

ALL USD Returned only if an error occurred while processing the transaction. Passed back in response transaction indicating failed processing. For an erroneous transaction, the error message will be placed in this field.

SHIPMENT LEVEL

2393 Email Label URL ALL USD Required if Error is not returned. URL for each label. Can contain not single or double quotes URL of web page at which labels can be found.

2394 Email Label Request Date Time

ALL USD Date the E-mail Label was requested. Format: CCYYMMDDTHHMMSSYYYYMMDDTHHMMSS

2208 Email Label User ID ALL USD Required if Error is not returned. User ID to be used to manually access the URL of web page at which labels can be found. 10 Alpha/Numeric characters.

Tagged Transaction Layouts – Transaction 137: E-Mail Label Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 150

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1040 Email Label Password ALL USD Required if Error is not returned. Password to be used to manually access the URL of web page at which labels can be found. 6 Alpha/Numeric characters.

1-10 occurrences of the following fields:

29-# Tracking Number ALL USD Contains the tracking number assigned to the shipment if successful.

526-# Form ID FDXE USD Label form ID returned upon successful transaction Reply.

2399-# Signature Option ALL ALL Optional.

TRANSACTION TERMINATOR

99 End Of Record ALL ALL Transaction Returned.

Tagged Transaction Layouts – Transaction 137: E-Mail Label Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 151

Example of Transaction 137: Email Label Reply

Continuing with the example on the previous page, the Reply transaction would be formatted as follows:

Data File Field Description

0,"137" Transaction Type 137 is Email Label Reply.

1,"Email Label" Customer Transaction identifier. FedEx will return to you the same identifier you send in.

1040, “0685ac” E-Mail Label Password.

2208, “WAPI” E-Mail Label User ID.

2393, “https://wwwtest.fedex.com/OnlineLabel/pLogin.jsp?labelUserCdDesc=WAPI&labelPasswordDesc=0685ac”

E-Mail Label URL.

2394, “20051012T081931” E-Mail Label Request Date/Time.

29-1, “176077215000233” Tracking Number.

99,”” Transaction terminator.

Tagged Transaction Layouts – Transaction 033: Cancel E-Mail Label Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 152

Transaction 033: Cancel E-Mail Label Request

This transaction cancels an Email Label Request. This transaction will be invalid if customer has already generated the label.

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code ALL USD Required.

1 Customer Transaction Identifier

ALL USD Optional. This field allows a FedEx customer to assign a unique identifier to a transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

10 Sender FedEx Account Number

ALL USD Required. The FedEx account number of the Sender is required to successfully cancel the Email Label Request.

498 Meter Number ALL USD Required. The unique meter number assigned to the Sender’s FedEx account number is required to successfully cancel the Email Label Request.

3025 Carrier Code ALL USD Required. Valid values:

FDXE – FedEx Express FDXG – FedEx Ground

TRACKING

29 Tracking Number ALL USD Required. Tracking number of E-mail Label/shipment to be deleted.

TRANSACTION TERMINATOR

99 End Of Record ALL ALL Transaction Returned.

Tagged Transaction Layouts – Transaction 033: Cancel E-Mail Label Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 153

Example of Transaction 033: Cancel Email Label Request

If a customer wishes to cancel an E-mail Label, the customer needs to send the 033 transaction to FedEx. For example, you created an E-mail Label for a Ground shipment and your FedEx Account Number is 123456789. The Tracking Number provided to you for this shipment was 176077215000233. The input transaction should be formatted as follows:

Data File Field Description

0,"033" Transaction Type 033 is Cancel Email Label Reply.

1," Cancel Email Label " Customer Transaction identifier. FedEx will return to you the same identifier you send in.

498,”1234567” Your meter number.

10, “123456789” Sender Account Number.

29, “176077215000233” Tracking Number.

3025, “FDXG” Carrier Code.

99,”” Transaction terminator.

Tagged Transaction Layouts – Transaction 133: Cancel E-Mail Label Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 154

Transaction 133: Cancel E-Mail Label Reply

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code ALL USD Required.

1 Customer Transaction Identifier

ALL USD Optional. Returned containing the same value if the customer included information for this tag in the Request transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

ERROR HANDLING

2 Transaction Error Code ALL USD Returned only if an error occurred while processing the transaction. Passed back in response indicating failed processing. For an erroneous Request or a server failure, the error code will be placed in this tag.

3 Transaction Error Message

ALL USD Returned only if an error occurred while processing the transaction. Passed back in response transaction indicating failed processing. For an erroneous transaction, the error message will be placed in this field.

TRANSACTION TERMINATOR

99 End Of Record ALL ALL Transaction Returned.

Tagged Transaction Layouts – Transaction 133: Cancel E-Mail Label Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 155

Example of Transaction 133: Cancel E-mail Label Reply

Continuing with the example on the previous page, the Reply transaction would be formatted as follows:

Data File Field Description

0,"133" Transaction Type 133 is Cancel Email Label Reply.

1," Cancel Email Label " Customer Transaction identifier. FedEx will return to you the same identifier you send in.

99,”” Transaction terminator.

If the input transaction contains an error, an error message number and message text are included in the transaction Reply. If, for example, the tracking number for the e-mail label entered was not valid, FedEx would respond with the following transaction:

Data File Field Description

0,"133" Transaction Type 133 is Cancel Email Label Reply.

1," Cancel Email Label " Customer Transaction identifier. FedEx will return to you the same identifier you send in.

2," 111E" Error code.

3," Tracking number is not in the database" Error message.

99,”” The required transaction terminator. It must be the last pair in the transaction.

NOTE:

The error code and error messages are returned only when an error occurred or invalid data was sent with the original Request.

Tagged Transaction Layouts – Transaction 044: Call Tag Create Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 156

Transaction 044: Call Tag Create Request

The FedEx Ground Call Tag return label combines the delivery of the Ground label with the pickup function. This transaction will dispatch a FedEx driver with a label to the location specified in the transaction. The driver will pick up the parcel using the label they have with them. Cancellations are handled via Ground Call Tag Cancel Request.

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code FDXG USD Required.

1 Customer Transaction Identifier FDXG USD Optional. This field allows a FedEx customer to assign a unique identifier to a transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

10 Sender FedEx Account Number FDXG USD Required. The FedEx account number of the Sender is required to successfully Request a Ground Call Tag.

498 Meter Number FDXG USD Required. The unique meter number assigned to the Sender’s FedEx account number is required to successfully Request a Ground Call Tag.

SENDER ORIGIN

4 Sender Company FDXG USD Required. Company from which the shipment is originating. A minimum of 3 alpha characters must be passed.

5 Sender Address Line 1 FDXG USD Required. Primary address line from which the shipment is originating.

6 Sender Address Line 2 FDXG USD Optional. Secondary address line from which the shipment is originating.

Tagged Transaction Layouts – Transaction 044: Call Tag Create Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 157

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

7 Sender City FDXG USD Required. City name from which the shipment is originating. Minimum of 3 alpha characters must be passed for shipping.

8 Sender State FDXG USD Required. State code from which the shipment is originating.

9 Sender Postal Code FDXG USD Required. Postal code from which the shipment is originating. Must be numeric and no embedded dashes allowed. Valid characters: A-Z; 0-9; a-z

32 Sender Contact Name FDXG USD Required if the Sender Company Name is not passed in the transaction.

117 Sender Country Code FDXG USD Required. Name of the country from which the shipment is originating. Must = US.

183 Sender Phone Number FDXG USD Required if interfacing with remote Express or Ground Server. The phone number of the person initiating the shipment. The maximum length is 10 for US and CA. Do not include embedded special characters.

MERCHANT / DESTINATION

11 Recipient Company FDXG USD Required if Recipient Contact Name was not passed in the Request transaction. Name of the company to whom the shipment is destined. If entered, a minimum of 3 alpha characters must be passed.

12 Recipient Contact Name FDXG USD Required if Recipient Company Name was not passed in the Request transaction. Name of the person to whom the shipment is destined. If passed in the transaction, a minimum of 3 alpha characters must be passed.

Tagged Transaction Layouts – Transaction 044: Call Tag Create Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 158

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

13 Recipient Address Line 1 FDXG USD Required. Primary address line to which the shipment is destined.

14 Recipient Address Line 2 FDXG USD Optional. Secondary address line to which the shipment is destined.

15 Recipient City FDXG USD Required. Name of the city to which the shipment is destined. A minimum of 3 alpha characters must be passed.

16 Recipient State FDXG USD Required. State or province code to which the shipment is destined.

17 Recipient Postal Code FDXG USD Required. Represents the postal code to which the shipment is destined. Valid characters: A-Z; 0-9; a-z

50 Recipient Country Code FDXG USD Required. Name of the country to which the shipment is destined.

PAYMENT

20 Payer Account Number FDXG USD For Express shipping, required field if Pay 3 (Bill Third Party). For Ground shipping, required field if Pay Type is 3 (Bill Third Party).

23 Pay Type FDXG USD Required. Only Bill Sender and Bill Third Party are allowed.

CALL TAG SPECIFIC DATA

1009 Business Close Time / Latest Pickup Time

FDXG USD Required for Commercial/Business pickup locations. Field not applicable for Residential pickup locations. This field should contain the latest time the package can be picked up for the pickup date requested. Format: HHMMSS Entry must be between 080000 and 180000.

Tagged Transaction Layouts – Transaction 044: Call Tag Create Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 159

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1008 Package Ready Time FDXG USD Required for Commercial/Business pickup locations. Not applicable for residential. This field should contain the earliest time the package will be ready for pickup on the pickup date requested. Format: HHMMSS Entry must be between 080000 and 180000.

1365 Dispatch Date

FDXG USD Required. This field contains the desired pickup date. Entry can contain the date for the next day through next day + 13 calendar days. Ground holidays and weekends may not be accepted. If accepted, the first pickup attempt will be made on this date. If the pickup is not successful, up to three pickup attempts will be made. Format: CCYYMMDD

1010 Courier Remarks/Pickup Instructions

FDXG USD Optional. This field contains any pickup instructions for the courier/driver.

SHIPMENT INFORMATION

2210 RMA Number FDXG USD Optional. Return Merchant Authorization number provided by the sender.

25 Reference Information

FDXG USD Optional.

68 Declared Value Currency Type FDXG USD Required. Must be USD.

116 Package Total (Total Number of Pieces)

FDXG USD Required. Can contain 1-10 inclusive. FDXE only applies to COD, MPS, and International.

Tagged Transaction Layouts – Transaction 044: Call Tag Create Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 160

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

PER PIECE FIELDS -# denotes recurring. These fields can recur for value indicated in tag 116.

1415-# Declared Value FDXG USD Optional for U.S. Domestic and Ground shipments. Should contain the declared value for each individual Call Tag package.

1398-# Item Description FDXG USD Required per piece. Description of item being shipped. Max 20.

SPECIAL SERVICE – OTHER

440 Residential Delivery Flag FDXG USD Y if shipment is Residential Delivery, else N.

3231 Residential Pickup Flag FDXG USD Optional. Defaults to N.

TRANSACTION TERMINATOR

99 End Of Record FDXG USD Required.

Tagged Transaction Layouts – Transaction 044: Call Tag Create Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 161

Example of Transaction 044: Call Tag Create Request

In order to create a Call Tag to dispatch a carrier to a location with pre-generated label and retrieve a FedEx package, format your Call Tag Request as follows:

Data File Field Description

0,"044" Transaction Type 044 is Call Tag Request.

1,"CallTag" Customer Transaction identifier. FedEx will return to you the same identifier you send in.

10, “000000000” Sender Account Number.

498, “0000000” Meter Number.

3025, “FDXG” Carrier Code.

4, “WAPI” Sender Company Name.

5, “5767 E Shelby Dr” Sender Address 1.

7, “Memphis” Sender City.

8, “TN” Sender State/Province.

9, “38141” Sender Postal Code.

8, “TN” Sender State/Province.

9, “38141” Sender Postal Code.

117, “US” Sender Country.

32, “WAPI-TEST-CL” Sender Contact Name.

38, “ WAPI” Sender Department.

183, “8004633339” Sender Phone Number.

1201, “[email protected]” Sender's Email Address.

11, “WAPI” Recipient Company Name.

12, “WAPI-TEST-CL” Recipient Contact Name.

13, “80 FEDEX PRKWY” Recipient Address 1.

15, “DETROIT” Recipient City.

Tagged Transaction Layouts – Transaction 044: Call Tag Create Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 162

Data File Field Description

16, “MI” Recipient State/Province.

17, “48204” Recipient Postal Code.

18, “8004633339” Recipient Phone Number.

50, “US” Recipient Country Code.

20, “1010101010” Payer Account Number.

23, “1” Payment Code.

1116, “I” Dim Units.

116, “1” Total Number of Packages.

117: US Sender Country.

1145: EDI0479 Recipient Department Name.

1008: 080010 Package Ready Time.

1009: 170030 Business Close Time/Last Pickup Time.

1273, “01” Packaging Type.

1274, “90” Service Type.

1365, “20051008” Dispatch Date.

1398, “Books” Item Description.

1415, “40.00” Declared Value/Carriage Value.

2382, “3” Return Shipment Indicator.

3231, “N” Residential Pickup Flag.

440, “Y” Residential Delivery Flag.

57, “2” Dim Package Height.

58, “2” Dim Package Width.

59, “62” Dim Package Length.

68, “USD” Customs/Declared Value Currency Type.

Tagged Transaction Layouts – Transaction 044: Call Tag Create Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 163

Data File Field Description

25, “D-ANY-F42953GRD12” Reference Info.

1010, “Schedule my package for pickup” Courier Remarks/Pickup Instructions.

2210, “RMA_TEST” RMA Number.

99,”” Transaction terminator.

Tagged Transaction Layouts – Transaction 144: Call Tag Create Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 164

Transaction 144: Call Tag Create Reply

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code FDXG USD Required.

1 Customer Transaction Identifier

FDXG USD Optional. Returned containing the same value if the customer included information for this tag in the Request transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

ERROR HANDLING

2 Transaction Error Code FDXG USD Returned only if an error occurred while processing the transaction. Passed back in response indicating failed processing. For an erroneous Request or a server failure, the error code will be placed in this tag.

3 Transaction Error Message FDXG USD Returned only if an error occurred while processing the transaction. Passed back in response transaction indicating failed processing. For an erroneous transaction, the error message will be placed in this field.

CALL TAG DATA

1011 Dispatch Confirmation Number

FDXG USD Pickup Confirmation Number. Note: This is the first tracking number for Ground. N/20 max length/number.

1-N TRACKING NUMBERS

29-# Tracking Number FDXG USD

TRANSACTION TERMINATOR

99 End Of Record FDXG USD Transaction Returned.

Tagged Transaction Layouts – Transaction 144: Call Tag Create Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 165

Example of Transaction 144: Call Tag Create Reply

Continuing with the example of a Call Tag Create Request, the Call Tag Reply transaction would be formatted as follows:

Data File Field Description

0,"144" Transaction Type 144 is Call Tag Reply.

1," CallTag " Customer Transaction identifier. FedEx will return to you the same identifier you send in.

1011, “997015600007813” Dispatch Confirmation Number.

29-1, “997015600007813” Tracking Number.

99,”” Transaction terminator.

Tagged Transaction Layouts – Transaction 045: Call Tag Cancel Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 166

Transaction 045: Call Tag Cancel Request

This transaction cancels a Call Tag Request. This transaction is only valid until tags are generated at the terminal (generally next day). Erroneous Requests should be canceled as soon as possible.

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code FDXG USD Required.

1 Customer Transaction Identifier FDXG USD Optional. This tag allows a FedEx customer to assign a unique identifier to a transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

10 Sender FedEx Account Number FDXG USD Required. The FedEx account number of the Sender is required to successfully cancel a Ground Call Tag.

498 Meter Number FDXG USD Required. The unique meter number assigned to the Sender’s FedEx account number is required to successfully cancel a Ground Call Tag.

CALL TAG DATA

1011 Dispatch Confirmation Number FDXG USD Pickup Confirmation Number. Note: This is the first tracking number for Ground. N/20 max length/number.

TRANSACTION TERMINATOR

99 End Of Record FDXG USD Transaction Returned.

Tagged Transaction Layouts – Transaction 045: Call Tag Cancel Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 167

Example of Transaction 045: Call Tag Cancel Request

If a customer wishes to cancel a Call Tag previously scheduled, the customer needs to send the 045 transaction to FedEx to cancel the Call Tag. For example, you scheduled a Dispatch for a Call Tag on October 13, 2005, and your FedEx Account Number is 123456789. The Dispatch Confirmation Number provided to you was 997015600007813. The input transaction should be formatted as follows:

Data File Field Description

0,"045" Transaction Type 045.

1," Cancel CallTag " Customer Transaction identifier. FedEx will return to you the same identifier you send in.

10, “123456789” Account number.

1011, “997015600007813” Dispatch Confirmation Number.

20, “000000000” Payer Account Number.

23, “3” Payment Code.

498, “1010101” Meter Number.

99,”” Transaction terminator.

Tagged Transaction Layouts – Transaction 145: Call Tag Cancel Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 168

Transaction 145: Call Tag Cancel Reply

The following codes are used in the Applicable Carrier and Valid for columns below:

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code FDXG USD Required.

1 Customer Transaction Identifier

FDXG USD Optional. Returned containing the same value if the customer included information for this tag in the Request transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

ERROR HANDLING

2 Transaction Error Code FDXG USD Returned only if an error occurred while processing the transaction. Passed back in response indicating failed processing. For an erroneous Request or a server failure, the error code will be placed in this tag.

3 Transaction Error Message FDXG USD Returned only if an error occurred while processing the transaction. Passed back in response transaction indicating failed processing. For an erroneous transaction, the error message will be placed in this field.

TRANSACTION TERMINATOR

99 End Of Record FDXG USD Required.

Tagged Transaction Layouts – Transaction 145: Call Tag Cancel Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 169

Example of Transaction 145: Cancel Call Tag Reply

Continuing with the example on the previous page, the Reply transaction would be formatted as follows:

Data File Field Description

0,"145" Transaction Type 145 is Cancel Call Tag Reply.

1," Cancel CallTag " Customer Transaction identifier. FedEx will return to you the same identifier you send in.

99,”” Transaction terminator.

If the input transaction contains an error, an error message number and message text are included in the transaction Reply. If, for example, the account number entered is not the account number used to create the Call Tag, FedEx would respond with the following transaction:

Data File Field Description

0,"311" Transaction Type 145 is Cancel Call Tag Reply.

1," Cancel CallTag " Customer Transaction identifier. FedEx will return to you the same identifier you send in.

2, “F5CD” Error code.

3, “A call tag may only be cancelled by the shipper who originally requested it.”

Error message.

99,”” The required transaction terminator. It must be the last pair in the transaction.

NOTE:

The error code and error messages are returned only when an error occurred or invalid data was sent with the original Request.

Tagged Transaction Layouts – Transaction 046: Express Tag Dispatch Create Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 170

Transaction 046: Express Tag Dispatch Create Request

The FedEx Express Tag return label combines the delivery of the Express label with the pickup function. This transaction will dispatch a FedEx driver with a label to the location specified in the transaction. The driver will pick up the parcel using the label they have with them. Service areas for this service are limited and should be checked using the Express Tag Availability Request. Cancellations are handled using the Express Tag Dispatch Cancel Request.

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code FDXE USD Required.

1 Customer Transaction Identifier

FDXE USD Optional. This tag allows a FedEx customer to assign a unique identifier to a transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

10 Sender FedEx Account Number

FDXE USD Required. The FedEx account number of the Sender is required to successfully Request an Express Tag Dispatch.

498 Meter Number FDXE USD Required. The unique meter number assigned to the Sender’s FedEx account number is required to successfully Request an Express Tag Dispatch.

SENDER ORIGIN

4 Sender Company FDXE USD Required if the Sender contact name is not passed in the transaction.

5 Sender Address Line 1 FDXE USD Required. Primary address line from which the shipment is originating.

7 Sender City FDXE USD Optional. Required Secondary address line from which the shipment is originating.

8 Sender State FDXE USD Required. City name from which the shipment is originating. Minimum of 3 alpha characters must be passed for shipping.

Tagged Transaction Layouts – Transaction 046: Express Tag Dispatch Create Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 171

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

9 Sender Postal Code FDXE USD Required. State code from which the shipment is originating.

32 Sender Contact Name FDXE USD Required if the Sender Company Name is not passed in the transaction. Postal code from which the shipment is originating. Must be numeric and no embedded dashes allowed. Valid characters: A-Z; 0-9; a-z

117 Sender Country Code FDXE USD Required. Must = US if the Sender Company Name is not passed in the transaction.

183 Sender Phone Number FDXE USD Required if interfacing with remote Express or Ground Server.

MERCHANT / DESTINATION

11 Recipient Company FDXE USD Required if Recipient Contact Name was not passed in the Request transaction. If entered, a minimum of 3 alpha characters must be passed.

12 Recipient Contact Name FDXE USD Required if Recipient Company Name was not passed in the Request transaction. If passed in the transaction, a minimum of 3 alpha characters must be passed.

13 Recipient Address Line 1 FDXE USD Required.

14 Recipient Address Line 2 FDXE USD Optional.

15 Recipient City FDXE USD Required. A minimum of 3 alpha characters must be passed.

16 Recipient State FDXE USD Required.

17 Recipient Postal Code FDXE USD Required.

18 Recipient Phone Number FDXE USD Required.

50 Recipient Country Code FDXE USD Required. Must be US.

Tagged Transaction Layouts – Transaction 046: Express Tag Dispatch Create Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 172

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

PAYMENT

20 Payer Account Number FDXE USD Required if Pay Type is 3 (Bill Third Party).

23 Pay Type FDXE USD Required. Only Bill Sender and Bill Third Party are allowed.

EXPRESS TAG SPECIFIC DATA

1009 Business Close Time FDXE USD Required. This field should contain the shipper’s latest package pickup time for the pickup date requested. The time entered must be earlier than the FedEx location cutoff time, or an error will be returned. There must be enough access window between the Package Ready Time and the Business Close Time, or an error will be returned.

1008 Package Ready Time FDXE USD Required. This field should contain the shipper’s earliest package pickup time for the pickup date requested. The time entered cannot be later than the Business Close Time. The Package Ready Time must be earlier than the Business Close Time (or the location’s cutoff time if it is earlier) minus the location’s Access Time, or an error will be returned.

1365 Dispatch Date FDXE USD Required. This field contains the desired pickup date. Requested date can be same business day or next business day, Monday-Saturday only.

1010 Courier Remarks/Pickup Instructions

FDXE USD Optional. This field contains any pickup instructions for the courier/driver.

SHIPMENT INFORMATION

1273 FedEx Packaging Type FDXE USD Required.

Tagged Transaction Layouts – Transaction 046: Express Tag Dispatch Create Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 173

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1274 FedEx Service Type FDXE USD Required.

2210 RMA Number FDXE USD Optional.

75 Weight Units FDXE USD Required. Must be LBS.

1400 Total Shipment Weight FDXE USD Required.

68 Declared Value Currency Type

FDXE USD Optional. Required if declared value is indicated. Must be USD.

116 Package Total (Total Number of Pieces)

FDXE USD Required. Can contain 1-5 inclusive. FDXE only applies to COD, MPS, and International.

1415 Declared Value / Carriage Value

FDXE USD Optional for U.S. Domestic Express Requests. Should contain the total declared value for the entire Express Tag pickup/shipment. Must be equal to or less than $50,000 USD. If not entered, will default to $0 USD.

REFERENCE INFORMATION

25 Reference Information FDXE USD Optional. A maximum of 30 characters is accepted in this field in this transaction. This field allows customer-defined notes to print on the shipping label.

SPECIAL SERVICE – HOLD AT LOCATION

1200 Hold at Location (HAL) Flag FDXE USD Y if shipment is Hold at Location, else N. Shipment will be held at the destination FedEx Station location.

SPECIAL SERVICE – OTHER

440 Residential Delivery Flag FDXE USD Y if shipment is Residential Delivery, else N.

Tagged Transaction Layouts – Transaction 046: Express Tag Dispatch Create Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 174

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

1208 No Indirect Delivery Flag (Signature Required)

FDXE USD Applicable to U.S. Domestic shipments only. Y if shipment is no indirect delivery, else N.

1266 Saturday Delivery Flag FDXE USD Y if shipment is targeted for Saturday delivery, else N.

TRANSACTION TERMINATOR

99 End Of Record FDXE USD Required.

Tagged Transaction Layouts – Transaction 046: Express Tag Dispatch Create Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 175

Example of Transaction 046: Express Tag Dispatch Create Request

In order to create an Express Tag to dispatch a carrier to a location with pre-generated label and retrieve a FedEx package, format your Express Tag Request as follows:

Data File Field Description

0,"046" Transaction Type 046 is Express Tag Request.

1,"ExpressTag" Customer Transaction identifier. FedEx will return to you the same identifier you send in.

10, “000000000” Sender Account Number.

498, “0000000” Meter Number.

3025, “FDXE” Carrier Code.

4, “WAPI” Sender Company Name.

5, “5767 E Shelby Dr” Sender Address 1.

7, “Memphis” Sender City.

8, “TN” Sender State/Province.

9, “38141” Sender Postal Code.

8, “TN” Sender State/Province.

9, “38141” Sender Postal Code.

117, “US” Sender Country.

32, “WAPI-TEST-CL” Sender Contact Name.

38, “ WAPI” Sender Department.

183, “8004633339” Sender Phone Number.

1201, “[email protected]” Sender's Email Address.

11, “WAPI” Recipient Company Name.

12, “WAPI-TEST-CL” Recipient Contact Name.

13, “80 FEDEX PRKWY” Recipient Address 1.

15, “DETROIT” Recipient City.

Tagged Transaction Layouts – Transaction 046: Express Tag Dispatch Create Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 176

Data File Field Description

16, “MI” Recipient State/Province.

17, “48204” Recipient Postal Code.

18, “8004633339” Recipient Phone Number.

50, “US” Recipient Country Code.

20, “1010101010” Payer Account Number.

23, “1” Payment Code.

1116, “I” Dim Units.

116, “1” Total Number of Packages.

117: US Sender Country.

1145: EDI0479 Recipient Department Name.

1008: 080010 Package Ready Time.

1009: 170030 Business Close Time/Last Pickup Time.

1273, “01” Packaging Type.

1274, “01” Service Type.

1365, “20051008” Dispatch Date.

1398, “Books” Item Description.

1400, “0.0” Total Shipment Weight.

75, “LBS” Weight Type/Unit of Measure.

2382, “3” Return Shipment Indicator.

1200, “N” Hold at Location (HAL) Flag.

58, “2” Dim Package Width.

59, “62” Dim Package Length.

1208, “N” No Indirect Delivery Flag.

1266, “N” Saturday Delivery Flag.

Tagged Transaction Layouts – Transaction 046: Express Tag Dispatch Create Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 177

Data File Field Description

440, “Y” Residential Delivery Flag.

57, “2” Dim Package Height.

58, “2” Dim Package Width.

59, “62” Dim Package Length.

68, “USD” Customs/Declared Value Currency Type.

25, “D-ANY-F42953XPRS12” Reference Info.

1010, “Schedule my package for pickup” Courier Remarks/Pickup Instructions.

2210, “RMA_TEST” RMA Number.

99,”” Transaction terminator.

Tagged Transaction Layouts – Transaction 146: Express Tag Dispatch Create Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 178

Transaction 146: Express Tag Dispatch Create Reply

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code FDXE USD Required.

1 Customer Transaction Identifier

FDXE USD Optional. Returned containing the same value if the customer included information for this tag in the Request transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

ERROR HANDLING

2 Transaction Error Code FDXE USD Returned only if an error occurred while processing the transaction. Passed back in response indicating failed processing. For an erroneous Request or a server failure, the error code will be placed in this tag.

3 Transaction Error Message FDXE USD Returned only if an error occurred while processing the transaction. Passed back in response transaction indicating failed processing. For an erroneous transaction, the error message will be placed in this field.

EXPRESS TAG DISPATCH

1011 Dispatch Confirmation Number

FDXE USD Dispatch Confirmation Number.

1012 Dispatch Location ID FDXE USD Express Location Identifier.

2268 Access Time FDXE USD Access times vary by postal code. Format: HHMMSS This is the minimum time window that must be allocated for the FedEx courier to make the pickup. This is a length of time. The difference between the Business Close Time (or the local “cutoff time” if it is earlier than the Business Close Time) and the Package Ready Time must be equal to or exceed the access time.

Tagged Transaction Layouts – Transaction 146: Express Tag Dispatch Create Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 179

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

2267 Cutoff Time FDXE USD Latest time a FedEx courier will be available to pick up the package from the Sender. Format: HHMMSS FedEx cutoff times vary by postal code.

2238 Delivery Commitment Date FDXE USD The date by which FedEx commits to deliver the shipment to the merchant if the shipment is tendered to FedEx on the scheduled pickup date. Format: CCYYMMDD

2239 Delivery Commitment Time FDXE USD The time by which FedEx commits to deliver the shipment to the merchant if the shipment is tendered to FedEx on the scheduled pickup date. Format: HHMMSS

29 Tracking Number FDXE USD

TRANSACTION TERMINATOR

99 End Of Record FDXE USD Transaction Returned.

Tagged Transaction Layouts – Transaction 146: Express Tag Dispatch Create Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 180

Example of Transaction 146: Express Tag Create Dispatch Reply

Continuing with the example of the Express Tag Request on the previous page, the Reply transaction would be formatted as follows:

Data File Field Description

0,"146" Transaction Type 146 is Express Tag Create Dispatch Reply.

1," ExpressTag" Customer Transaction identifier. FedEx will return to you the same identifier you send in.

1011, “00008” Dispatch Confirmation Number.

1012, “TSSA” Dispatch Location.

2238, “20051014” Commitment Date.

2239, “103000” Commitment Time.

2267, “193000” Cutoff Time.

2268, “023000” Access Time.

29, “301000658419” Tracking Number.

99,”” Transaction terminator.

Tagged Transaction Layouts – Transaction 047: Express Tag Dispatch Cancel Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 181

Transaction 047: Express Tag Dispatch Cancel Request

This transaction cancels an Express Tag Request. This transaction is only valid until driver is dispatched. Erroneous Requests should be canceled as soon as possible.

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code FDXE USD Required.

1 Customer Transaction Identifier

FDXE USD Optional.

10 Sender FedEx Account Number

FDXE USD Required

498 Meter Number FDXE USD Required.

EXPRESS TAG DISPATCH DATA

1011 Dispatch Confirmation Number

FDXE USD Dispatch confirmation number.

1012 Dispatch Location ID FDXE USD Express Location Identifier.

1365 Dispatch Date FDXE USD Dispatch Date. The date FedEx will attempt to pick up the shipment from the Sender.

TRANSACTION TERMINATOR

99 End Of Record FDXE USD Transaction Returned.

Tagged Transaction Layouts – Transaction 047: Express Tag Dispatch Cancel Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 182

Example of Transaction 047: Express Tag Dispatch Cancel Request

If a customer wishes to cancel an Express Tag previously scheduled, the customer needs to send the 047 transaction to FedEx to cancel the Express Tag. For example, you scheduled a Dispatch for an Express Tag on October 13, 2005, and your FedEx Account Number is 987654321. The Dispatch Confirmation Number provided to you was 00008, and the Dispatch Location which will handle your Express Tag Request is TSSA. The input transaction should be formatted as follows:

Data File Field Description

0,"047" Transaction Type 047 is Express Tag Dispatch Cancel Request.

1, “Cancel ExpressTag” Customer Transaction identifier. FedEx will return to you the same identifier you send in.

10, “987654321” Sender Account Number.

1011, “00008” Dispatch Confirmation Number.

1012, “TSSA” Dispatch Location.

1365, “20051013” Dispatch Date.

498, “1234567” Meter Number.

99,”” Transaction terminator.

Tagged Transaction Layouts – Transaction 147: Express Tag Dispatch Cancel Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 183

Transaction 147: Express Tag Dispatch Cancel Reply

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code FDXE USD Required.

1 Customer Transaction Identifier

FDXE USD Optional. Returned containing the same value if the customer included information for this tag in the Request transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

ERROR HANDLING

2 Transaction Error Code FDXE USD Returned only if an error occurred while processing the transaction. Passed back in response indicating failed processing. For an erroneous Request or a server failure, the error code will be placed in this tag.

3 Transaction Error Message FDXE USD Returned only if an error occurred while processing the transaction. Passed back in response transaction indicating failed processing. For an erroneous transaction, the error message will be placed in this field.

TRANSACTION TERMINATOR

99 End Of Record FDXE USD Transaction Returned.

Tagged Transaction Layouts – Transaction 147: Express Tag Dispatch Cancel Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 184

Example of Transaction 147: Express Tag Dispatch Cancel Reply

Continuing with the example on the previous page, the Reply transaction would be formatted as follows:

Data File Field Description

0,"147" Transaction Type 147 is Express Tag Dispatch Cancel Reply.

1,"Cancel ExpressTag" Customer Transaction identifier. FedEx will return to you the same identifier you send in.

99,”” Transaction terminator.

If the input transaction contains an error, an error message number and message text are included in the transaction Reply. If, for example, the dispatch/confirmation number entered was not valid, FedEx would respond with the following transaction:

Data File Field Description

0,"147" Transaction Type 147 is Cancel Express Tag Dispatch Reply.

1, “Cancel ExpressTag” Customer Transaction identifier. FedEx will return to you the same identifier you send in.

2, “5049” Error code.

3, “No dispatch found for this account.” Error message.

99,”” The required transaction terminator. It must be the last pair in the transaction.

NOTE:

The error code and error messages are returned only when an error occurred or invalid data was sent with the original Request.

Tagged Transaction Layouts – Transaction 048: Express Tag Availability Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 185

Transaction 048: Express Tag Availability Request

Express Tag is a premium Express service and has limited coverage. Effective applications will include this option to allow customers to see if an area has coverage. This is done to prevent a user from filling out an entire screen full of shipment information just to find out there is no coverage. This is determined using dates and ZIP codes for service areas.

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code FDXE USD Required.

1 Customer Transaction Identifier FDXE USD Optional.

10 Sender FedEx Account Number FDXE USD Required.

498 Meter Number FDXE USD Required.

EXPRESS TAG DISPATCH DATA

9 Sender Postal Code FDXE USD Required.

117 Sender Country FDXE USD Required. Must be US.

1365 Dispatch Date FDXE USD Required.

1008 Package Ready Time FDXE USD Required.

1273 Packaging Type FDXE USD Required.

1274 Service Type FDXE USD Required.

TRANSACTION TERMINATOR

99 End Of Record FDXE USD Transaction Returned.

Tagged Transaction Layouts – Transaction 048: Express Tag Availability Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 186

Example of Transaction 048: Express Tag Availability Request

If a customer wants to determine if the availability of an Express Tag for a particular area within the U.S., the customer needs to send the 048 transaction to FedEx to find out the availability of an Express Tag. For example, you wish to determine if you can schedule an Express Tag on October 13, 2005, and the package will be ready at 8:10p.m. Your FedEx Account Number is 987654321, and you are shipping from ZIP code 10001. The input transaction should be formatted as follows:

Data File Field Description

0,"048" Transaction Type 048 is Express Tag Availability Request.

1," ExpressTagAvailability" Customer Transaction identifier. FedEx will return to you the same identifier you send in.

498,”1234567” Your meter number.

10, “100100101” Sender Account Number.

1008, “080010” Package Ready Time.

117, “US” Sender Country.

1273, “02” Packaging Type.

1274, “01” Service Type.

1365, “20051013” Dispatch Date.

498, “1033934” Meter Number.

9, “10001” Sender Postal Code.

99,”” Transaction terminator.

Tagged Transaction Layouts – Transaction 048: Express Tag Availability Request

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 187

If the input transaction contains an error, an error message number and message text are included in the transaction Reply. If, for example, the ZIP code entered had only 3 digits, FedEx would respond with the following transaction:

Data File Field Description

0,"311" Transaction Type 311 is Subscribe/Register Reply.

1," Subscribe " Customer Transaction identifier. FedEx will return to you the same identifier you send in.

2,"1235" Error code.

3,"Bad Zip Format" Error message.

99,”” The required transaction terminator. It must be the last pair in the transaction.

Tagged Transaction Layouts – Transaction 148: Express Tag Availability Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 188

Transaction 148: Express Tag Availability Reply

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

STANDARD INFO

0 Transaction Code FDXE USD Required.

1 Customer Transaction Identifier

FDXE USD Optional. Returned containing the same value if the customer included information for this tag in the Request transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

ERROR HANDLING

2 Transaction Error Code FDXE USD Returned only if an error occurred while processing the transaction. Passed back in response indicating failed processing. For an erroneous Request or a server failure, the error code will be placed in this tag.

3 Transaction Error Message

FDXE USD Returned only if an error occurred while processing the transaction. Passed back in response transaction indicating failed processing. For an erroneous transaction, the error message will be placed in this field.

EXPRESS TAG DISPATCH DATA

2269 Express Tag Availability Code

FDXE USD Indicates the Express Tag Service availability at the sender postal code indicated in the Request:

2 = FedEx Express Tag service next day available 3 = FedEx Express Tag service same day and Next Day available

2268 Access Time FDXE USD Access times vary by postal code. Format is: HHMMSS This is the minimum time window that must be allocated for the FedEx courier to make the pickup. This is a length of time. The difference between the Business Close Time (or the local “cutoff time” if it is earlier than the Business Close Time) and the Package Ready Time must be equal to or exceed the access time.

Tagged Transaction Layouts – Transaction 148: Express Tag Availability Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 189

Field Tag Field Name Applicable

Carrier Valid For Field Requirements

2267 Cutoff Time FDXE USD Latest time a FedEx courier will be available to pick up the package from the Sender. FedEx cutoff times vary by postal code. Format: HHMMSS

TRANSACTION TERMINATOR

99 End Of Record FDXE USD Transaction Returned.

Tagged Transaction Layouts – Transaction 148: Express Tag Availability Reply

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 190

Example of Transaction 148: ExpressTag Availability Reply

Continuing with the example on the previous page, the Reply transaction would be formatted as follows:

Data File Field Description

0,"311" Transaction Type 148 is Express Tag Availability Reply.

1,"Subscribe" Customer Transaction identifier. FedEx will return to you the same identifier you send in.

498,”1234567” Your meter number.

4021-1,”0001” Authorized for FedEx Express Shipping.

4021-2,”0002” Authorized for FedEx Ground Shipping.

99,”” Transaction terminator.

If the input transaction contains an error, an error message number and message text are included in the transaction Reply. If, for example, the ZIP code entered had only 3 digits, FedEx would respond with the following transaction:

Data File Field Description

0,"311" Transaction Type 148 is Express Tag Availability Reply.

1," Subscribe " Customer Transaction identifier. FedEx will return to you the same identifier you send in.

2,"1235" Error code.

3,"Bad Zip Format" Error message.

99,”” The required transaction terminator. It must be the last pair in the transaction.

NOTE:

The error code and error messages are returned only when an error occurred or invalid data was sent with the original Request.

Shipping Label Specifications

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 191

Shipping Label Specifications

Plain Paper and Thermal Label Specifications

General Printing Overview and Methods

The FedEx ASTRA bar code was designed to accommodate automated scanning and sorting at the stations and hubs. The specifications are written to allow the various scanning systems throughout FedEx to accurately and reliably de-code the information in the bar code. The only way to ensure that the bar codes will work reliably with present and future scanning systems is to make sure that they always meet FedEx minimum standard specifications for print quality. There can be no deviation from these specifications nor can any waiver or modifications be allowed.

*PRINT METHODS: Preferred print methods include direct thermal, thermal transfer, LASER (xerographic) or ink jet. These print methods are chosen due to their ability to maintain a high and constant quality output throughout the life of the printer and supplies. With these systems, FedEx can check the quality of a customer-produced bar code once to verify that the major print components are correct, and be confident that the production bar code will continue to maintain very similar quality.

Dot-matrix printers are not permitted. This is because even in the best of conditions the print quality is highly variable. Some dot matrix printers are capable of printing quality bar codes when the ribbon life and platen pressure are in optimum condition, but in actual production this is nearly impossible to monitor and control.

NOTE:

While FedEx Ship Manager API will support the printing of both plain paper and thermal labels, FedEx does not provide the hardware with which to produce either type label.

Shipping Label Specifications

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 192

PNG Plain Paper Label

Printing the plain paper label is different than printing the thermal label. The image orientation dimensions can be manipulated when using a print manager to print a plain paper label. Image Orientation Dimensions are determined when the label is viewed in an imaging editor application. Image orientations for both Shipping and Tracking Signature Proof of Delivery (SPOD) PNG plain paper shipping labels are listed in the corresponding table:

Print Manager Dimensions PNG Plain Paper Image Orientation Dimensions

Width By Height

Shipping PNG (browser and non-browser) 7.0 X 4.75

SPOD PNG (browser and non-browser) 6.8 X 7.6

When the label is printed, it can either increase or decrease in size if the print manager dimensions are not properly set.

If the dimensions are increased, the following will result:

• All human readable, bar code data and bar codes will be increased in size, and bar codes may become unable to be scanned by the Courier and Ground Operations division.

• Since the label will need to be folded in half and inserted into the FedEx Pouch, the ASTRA bar code (field 35 in the table below) will need to be fully visible. To ensure full visibility, there should be between 5/16" and ¾" of white space from the bottom of the ASTRA bar code to the fold.

If the dimensions are decreased, the following will result:

• All human readable, bar code data and bar codes will be decreased in size.

• When the label is decreased in size, bar codes may become unable to be scanned by the Courier and Ground Operations division. Additionally, if the size is increased or decreased, this may result in the delay of switching the user's application from the validation to production environment.

Shipping Label Specifications

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 193

For the Browser based label, the user will need to ensure the appropriate HTML wrapper is attached. The following represents the Page name and File path of a Browser based label:

• FedEx Ship Manager API Label Page file://C:/Program Files/FedEx/Fed…ples/vb/470004122710.html

Reference the Browser-based shipping label in the following plain paper shipping label attachments for verbiage orientation.

Determining Screen Resolution

Printing the plain paper shipping labels and SPOD letters require proper sizing. This requires determining the screen resolution selected on the device running the browser. The HTTP parameters <WIDTH> and <HEIGHT> will need to be calculated using the screen DPI values and the desired reproduced screen width and height.

Below lists the typical screen resolutions for Windows and Macintosh based on the font size selected.

Browser Screen resolution (typical default)

Windows using small fonts 96 DPI

Windows using large fonts 120 DPI

Macintosh 72 DPI

Shipping Label Specifications

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 194

Examples of Populating HTML Tag Height and Width Values:

Width (pixels) = ScreenDPI * (desired image reproduced width)

Height (pixels = ScreenDPI * (desired image reproduced height)

Example: Sample code implementing Shipping plain paper label in Netscape Browser:

<HTML> <SCRIPT LANGUAGE="JavaScript1.1"> var NS4 = (document.layers) ? true : false ; var resolution = 96; if (NS4 && navigator.javaEnabled()) { var toolkit = java.awt.Toolkit.getDefaultToolkit(); resolution = toolkit.getScreenResolution(); } </SCRIPT> <SCRIPT LANGUAGE="JavaScript"> document.write('<img WIDTH=' + (700 * resolution )/100 + '<img HEIGHT=' + (475 * resolution )/100 + ' alt="ASTRA Barcode" src="path/test.png">'); </SCRIPT> </HTML>

Example for getting Screen resolution using Microsoft MFC library:

DC hDC = CreateDC( “DISPLAY”, NULL, NULL, NULL ); int DPI = getDeviceCaps ( hDC, LOGPIXELSX); DeleteDC(hDC);

Custom Labels

FedEx does not support the creation or use of a custom label for either FedEx Ship Manager API Ground or Express shipping.

Shipping Label Specifications

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 195

Shipping Label Support

Labels can be categorized by three attributes:

• label type • printer type • format

The label type (2 = 2D Common) is specified with field 1368 in the Ship transaction.

The printer type (1 = plain paper laser, 2 = Eltron Orion, 3 = Eltron Eclipse, 4 = Zebra ZPL, or 5 = Unimark) is specified with field 1369.

The format type (3 = 4x6¾ thermal with doc-tab at the bottom, 4 = 4x6 without doc-tab, 5 = plain paper PNG, and 6 = 4x6¾ thermal with doc-tab at the top) is specified with field 1370.

The shipping label data will be found in field 188 in the response transaction. If there is a COD return label, it will be found in field 411. If you requested a PNG label, the data returned will be a PNG file. If you requested a thermal label, the data returned will be a series of command codes that can be serially transmitted to a thermal printer to cause a label to be printed.

To ensure fast, reliable parsing of tagged transactions, certain characters are not allowed in the data values of fields. Any occurrences of those characters within a field will have been encoded with other legal characters. Thus, after you extract the bytes of data from the label fields (188 and 411), they must be decoded to get the PNG or thermal label image.

Label Data Buffer

NOTE:

The following example does NOT include all possible fields of the Ship Reply transaction. The label type generated by this example data string is a PNG label.

Shipping Label Specifications

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 196

Upon a successful Ship a Package Request Transaction, the following buffer is returned:

Send to FedEx:

0,"021"4,"ABC Company"5,"1234 Main Street"7,"Memphis"8,"TN"9,"38101"11,"XYZ Company"13,"9876 Southwest Street"15,"New York"16,"NY"17,"10042"18,"7035551212"23,"1"50,"US"74,"US"75,"LBS"117,"US"183,"901555121 2"1115,"123456"1116,"I"1273,"02"1274,"01"1368,"2"1369,"1"1370,"5"1401,"2.0"3025,"FDXE"10,"123456789"498,"123456 7"24,"20050531"99,""

Received from FedEx:

0,"121"33,"AA"1136,"XY"30,"XY AYZA"29,"470001338040"526,"0201"1402,"2.0"1419,"25.22"1416,"24.25"1417,".97"1090,"USD"1 089,"01552"1092,"5"65,"40048946120000014700013380402018"194,"THU"195,"EWR"409,"01JUN00" 431,"N"188,”<Label Binary Data Stored Here>”99,""

NOTE:

That field 188 will contain the label data. In the next section, we will look into how to use this data buffer to print the FedEx Shipping Label.

When a Ship a Package transaction is performed, the data necessary for producing a shipping label (and possibly a COD return label) is returned in one or more fields. The kind of label data returned depends on the printer type and format specified in your Ship Request.

Using Buffer Data to Print PNG or Thermal Labels

The rule for encoding the PNG or thermal image in the returned label buffer was designed to eliminate certain illegal characters (byte values) by replacing them with an escape sequence. Those values that are not allowed include:

• NULL (0x00 hex) • Double Quote (0x22 hex)

Shipping Label Specifications

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 197

The percent character ‘%’ (0x25 hex) is used as the escape character, and therefore must be replaced where it occurs naturally. Whenever a disallowed character or the escape character '%' is encountered, it is replaced by the escape character ‘%’ (0x25 hex), followed by two characters comprising the hexadecimal numeral representing the value of the character. For example, the NULL character (0x00 hex) is replaced by three characters:

• '%' (0x25) • '0' (0x30) • '0' (0x30)

The percent character 0x25 is replaced by three characters:

• '%' (0x25) • '2’ (0x32) • '5' (0x35)

The algorithm for decoding the PNG image in the returned label buffer is as follows. Read bytes from the label field one at a time. When a byte read is not equal to the ‘%’ character (0x25 hex), pass it through unchanged. When a byte is read that is equal to the ‘%’ character (0x25 hex), read an additional two bytes, which will each take a value from ‘0’ (0x30 hex) through ‘9’ (0x39 hex) or ‘A’ (0x41 hex) through ‘F’ (0x46 hex). These two bytes are interpreted as a character representation of a two-digit hexadecimal numeral ranging from 0x00 through 0xFF. The single byte having the integral value represented by that numeral is appended to your output. For example, when the 3-byte string '%22' is encountered, ‘ ” ’ (0x22) - the double quote character is passed out. When the 3 bytes '%00' are read, the null character is written.

In essence, the developer will need to take the data received from FedEx and store it in a buffer that has sufficient memory to hold the entire data stream. Once the data has been stored, the program might use a function similar to the one described below in order to parse the data in the buffer and extract only the PNG image data. From that point, the developers program must be able to call a print function to send the image to the laser printer. The following sample “C” function illustrates how this is accomplished.

Shipping Label Specifications

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 198

Sample C

int create_fedex_ship_label(char *receive_buffer)

{ FILE *fedex_label; int c; int data_decoded = 0; int temp_label_counter; int label_data_found = 0; int result = 1; int load_label_data = 0; char data; char temp_label_buffer[20]; char label_file_name[20]= {“FedEx Label.png”}; char data_field_buffer[6]= {“188,”}; if((fedex_label = fopen(label_file_name, "wb")) == NULL) {

return(1); }

c = 0; while(data_decoded != 1) { data = receive_buffer[c]; if(data == '1') { temp_label_buffer[temp_label_counter] = data; temp_label_counter++; c++; data = receive_buffer[c]; if((data == '8') && (temp_label_buffer[0] == '1')) { temp_label_buffer[temp_label_counter] = data; temp_label_counter++;

Shipping Label Specifications

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 199

c++; data = receive_buffer[c]; } else { temp_label_counter = 0; } if((data == '8') && (temp_label_buffer[1] == '8')) { temp_label_buffer[temp_label_counter] = data; temp_label_counter++; c++; data = receive_buffer[c]; } else { temp_label_counter = 0; } if((data == ',') && (temp_label_buffer[2] == '8')) { temp_label_buffer[temp_label_counter] = data; temp_label_counter++; c++; temp_label_buffer[temp_label_counter] = 0x00; label_data_found = 1; } else {

temp_label_counter = 0; }

} else c++; if(label_data_found) {

Shipping Label Specifications

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 200

result = strcmp(temp_label_buffer, data_field_buffer); if(result == 0) load_label_data = 1; data = receive_buffer[c]; } if(load_label_data) { data = '0'; c++; while(data != 0x22) { data = receive_buffer[c]; c++; if(data != '%') fprintf(fedex_label, "%c", data); if(data == '%') { for(e=0; e<2; e++) { data = receive_buffer[c]; c++; if(((data >= 0x30) && (data <= 0x39)) || ((data >= 0x41)

&& (data <= 0x46))) { if(e == 1) { d = data; d = d & 0x0f; if((data >= 0x41) && (data <= 0x46)) d += 9; store = store | d; } else { d = data;

Shipping Label Specifications

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 201

d = d & 0x0f; if((data >= 0x41) && (data <= 0x46)) d += 9; store = d << 4; } } } fprintf(fedex_label, "%c", store); } } data_decoded = 1; } } fclose(fedex_label); return(0);

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 202

Appendix A: Field Descriptions by Field Tag

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

0 Transaction Code 4 Numeric Identifies the type of transaction.

1 Customer Transaction Identifier 40 Alpha This field allows a FedEx customer to assign a unique identifier to a transaction. It is returned in the Reply transaction to aid in matching transaction Requests to Replies.

2 Transaction Error Code 8 Alpha Passed back in response transaction indicating failed processing. For an erroneous transaction, the error code will be placed in this field.

3 Transaction Error Message 120 Alpha Passed back in response transaction indicating failed processing. For an erroneous transaction, the error message will be placed in this field.

4 Sender Company 35 Alpha Company from which the shipment is originating.

5 Sender Address Line 1 35 Alpha Primary address line from which the shipment is originating.

6 Sender Address Line 2 35 Alpha Secondary address line from which the shipment is originating.

7 Sender City FDXE-35 FDXG-20

Alpha City name from which the shipment is originating.

8 Sender State 22 Alpha State code from which the shipment is originating.

9 Sender Postal Code 16 Alpha Postal code from which the shipment is originating. Must be numeric for U.S. Special characters allowed.

10 Sender FedEx Account Number 12 Numeric The FedEx account number assigned to the FedEx customer from which the shipment is originating.

11 Recipient Company 35 Alpha Name of the company that is receiving the shipment.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 203

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

12 Recipient Contact Name 35 Alpha Name of the person that is receiving the shipment.

13 Recipient Address Line 1 35 Alpha Primary address line of the person receiving the shipment.

14 Recipient Address Line 2 35 Alpha Secondary address line of the person receiving the shipment.

15 Recipient City FDXE-35 FDXG-20

Alpha City name of the person receiving the shipment.

16 Recipient State 2 Alpha State code of the person receiving the shipment.

17 Recipient Postal Code 16

Alpha Postal code of the person receiving the shipment. Must be numeric for U.S. Special characters allowed.

18 Recipient Phone Number 15 Alpha The phone number of the person receiving the shipment. The maximum length is 10 for US and CA, 15 for all other countries. Do not include embedded special characters.

20 Payer Account Number 12 Numeric Account number of company or person to be billed for payment of the shipment.

23 Pay Type 2 Numeric Method of payment for shipment. Valid payment types are:

1 = Bill sender (Prepaid) 2 = Bill recipient (Collect for FedEx Express; Bill for FedEx Ground) 3 = Bill third party 5 = Bill recipient for FedEx Ground

24 Ship Date 8 Numeric Date of shipment. Format: YYYYMMDD

25 Reference Information FDXE-40 FDXG-30

Alpha Customer reference information assigned to a package. This field CANNOT be used with Alcohol Shipping.

27 COD Flag 1 Alpha Must be Y for COD (Collect on Delivery) service, else defaulted to N.

29 Tracking Number 20 Alpha Tracking number assigned to a package.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 204

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

30 URSA Code 7 Alpha FedEx routing code.

32 Sender Contact Name 35 Alpha Name of the person from which the shipment is originating.

33 Service Commitment 2 Alpha Service commitment available for this area and service code. See the FedEx Service Guide for returned values.

38 Sender Department 10 Alpha Name of the department from which the shipment is originating.

40 Alcohol Type 1 Alpha The type of alcohol being shipped. Valid values:

B = Beer W = Wine S = Distilled Spirits A = Ale L = Light Wine

41 Alcohol Packaging 2 Alpha The packaging of the alcohol being shipped. Valid values:

BL = Barrel BT = Bottle CS = Case CN = Carton OT = Other

44 HAL Address 35 Alpha Primary address where a package will be held for pickup when shipping with the Hold At Location special service.

46 HAL City 35 Alpha City name where a package will be held for pickup when shipping with the Hold At Location special service.

47 HAL State 14 Alpha State code where a package will be held for pickup when shipping with the Hold At Location special service.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 205

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

48 HAL Postal Code 16 Alpha Postal code where a package will be held for pickup when shipping with the Hold At Location special service. Must be numeric for U.S. Special characters allowed.

49 HAL Phone Number 15 Alpha The phone number where a package will be held for pickup when shipping with the Hold At Location special service. The maximum length is 10 for US and CA, 15 for all other countries.

50 Recipient Country 2 Alpha Country name of the person receiving the shipment.

52 Alcohol Packages 3 Numeric Number of units (bottles, cases, etc.) of alcohol included in the package being shipped.

57 Dim Height 3 Numeric The height of a package.

58 Dim Width 3 Numeric The width of a package.

59 Dim Length 3 Numeric The length of a package.

65 ASTRA Barcode 32 Numeric

66 Broker Name 35 Alpha

67 Broker Phone Number 15 Alpha The maximum length is 10 for US and CA, 15 for all other countries. Do not include embedded special characters.

68 Customs/Declared Value Currency Type

3 Alpha Currency type used for customs value and declared/carriage value fields. The declared value currency indicated must be the same as the declared value currency of the origin country for Ground shipments.

70 Duties Pay Type 2 Numeric Payment type for duties and taxes. Valid values: 1 = Bill Sender 2 = Bill Recipient 3 = Bill Third Party

71 Duties Payer Account Number 12 Numeric FedEx account number billed for duties/taxes.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 206

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

72 Terms Of Sale 1 Numeric Valid values: 1 = FOB/FCA (Free or Freight On Board/Free Carrier) 2 = CIF/CIP (Cost-Insurance-Freight/Carriage Insurance Paid 3 = C&F/CPT (Cost and Freight, aka CFR/Carrier Paid To 4 = EXW (Ex Works) 5 = DDU (Delivered Duty Unpaid) 6 = DDP (Delivered Duty Paid)

73 Parties To Transaction 1 Alpha A Y is entered and required if the exporter and the consignee of the transaction are related. To determine if the parties are related, the company of the exporter and the company of the consignee have a parent/child relationship, or either the exporter or consignee must have at least 10% ownership in the other (e.g. subsidiaries, branches of same company etc.). SED Default: N

75 Weight Units 3 Alpha Valid units: • LBS • KGS U.S. Domestic Express must be LBS on a Domestic rate quote.

76 Commodity Number Of Pieces 5 Numeric

79 Description Of Contents Min: 31 Max: 450

Alpha Only a portion of this field will print on the label. Refer to Appendix C: Vague Commodity Descriptions for a list of inappropriate commodity descriptions.

80 Country Of Manufacture 2 Alpha Country code where commodity contents were produced or manufactured in their final form. See Appendix B: Country Codes.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 207

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

81 Harmonized Code 14 Alpha Unique alpha/numeric representing commodity item. Currently 10 digits, no decimals.

82 Unit Quantity 9 Alpha Number of units of a commodity in total number of pieces for this line item.

83 Export License Number 12 Alpha License number (A999999).

84 Export License Expiration Date 8 Numeric Date of expiration. Must be at least 1 day into future. The date that the Commerce Export License expires. Export License commodities may not be exported from the U.S. on an expired license. Format: CCYYMMDD

99 End Of Record Indicator Example: 99,””

113 Commercial Invoice Flag 1 Alpha Must be Y if “shipment” contains Commercial Invoice information in separate transaction

116 Total Package/Piece Count 4 Numeric Valid values are 1 to 9999. Total packages in a shipment include master transaction. For MPS shipments, 1 piece = 1 box. For International Freight MPS shipments, this is the total number of “units”. Units are the skids, pallets, or boxes that make up a freight shipment. Each unit within a shipment should have its own label. FDXE only applies to COD, MPS, and International.

117 Sender Country Code 2 Alpha Puerto Rico customers use US as Sender Country Code.

118 Recipient SSN/ EIN 15 Alpha No special characters allowed.

120 CI Marks And Numbers 15 Alpha An identifying mark or number used on the packaging of a shipment to help customers identify a particular shipment. Only used for the FedEx CI.

169 Importer Country 2 Alpha Country code for importer of shipment if other than recipient.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 208

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

170 Importer Name 35 Alpha Contact name for importer of shipment if other than recipient.

171 Importer Company 35 Alpha Company Name for importer of shipment if other than recipient.

172 Importer Address Line 1 35 Alpha Address Line 1 for importer of shipment if other than recipient.

173 Importer Address Line 2 35 Alpha Address Line 2 for importer of shipment if other than recipient.

174 Importer City 35 Alpha City name for importer of shipment if other than recipient.

175 Importer State 14 Alpha State code for importer of shipment if other than recipient. The maximum length is 2 for US and CA, 14 for all other countries.

176 Importer Postal Code 16 Alpha Postal code for importer of shipment if other than recipient. Must be numeric for U.S.; special characters allowed.

177 Importer Account Number 12 Numeric Account number for importer of shipment if other than recipient.

178 Importer Phone Number 15 Alpha Phone number for importer of shipment if other than recipient. The maximum length is 10 for US and CA, 15 for all other countries. No embedded dashes allowed.

180 Importer SSN/EIN 18 Alpha SSN/EIN for importer of shipment if other than recipient.

183 Sender Phone Number 10 for FedEx

Locator / 15 for other

trans-actions

Alpha For shipping, the maximum length is 10 for US and CA, 15 for all other countries. For FedEx Locator, the length must be 10 digits with valid area code and prefix.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 209

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

186 COD Add Freight Charges Flag 1 Alpha/Numeric

Required only if shipping COD. Accumulate these charges into the COD Amount for a single package:

1 = Add discounted rate to COD Amount 2 = Add list rate to COD Amount 3 = Add discounted COD Surcharge 4 = Add list COD Surcharge 5 = Add discounted **Customer Total Charge 6 = Add list **Customer Total Charge

Accumulate these charges into the COD Amount for a shipment:

7 = Add MTW Net Charge (shipment level) 8 = Add Discount Shipment Net Charge to last package in a Shipment 9 = Add List Shipment Net Charge to last package in a shipment.

Values 2, 4, 6 are only valid when Rate Indicator (tag 1529) = 2. Values 1, 3, 5, are valid when Rate Indicator (tag 1529) is not present or equals 1 or 2. Values 7-9 are only valid options for Ground MPS and have no dependency on the Rate Indicator.

188 Label Buffer Data Stream Variable Length

Alpha

190 Document (PIB) Shipment Flag 1 Alpha Y if document shipment, else N.

194 Delivery Day 3 Alpha Day of week – SUN, MON, TUE, WED, THU, FRI, SAT.

195 Destination Station ID 4 Alpha FedEx location identifier of the destination ramp. Not available for all origin-destination combinations. Puerto Rico to US and Canada destinations are populated.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 210

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

198 Destination Location ID 5 Alpha FedEx location identifier of the package destination.

409 Delivery Date 8 Alpha The above date format is the required format for printing on a label to current ASTRA specifications. Date Format: DDMMMYY (ex. 29NOV05) Note: The standard date format for all dates (except delivery date) will be passed in the CCYYMMDD format.

411 COD Return Label Buffer Data Stream 51200 Alpha

413 NAFTA Flag 1 Alpha Y if NAFTA shipment, else N.

414 Commodity Unit Of Measure 3 Alpha The following volume/dimensions of a commodity are valid for this tag: Unit of Measure codes:

AR – Carat CFT – Cubic Feet CG – Centigrams CM – Centimeters CM3 – Cubic Centimeters DOZ – Dozen DPR – Dozen Pair EA – Each G – Grams GR – Gross GAL – Gallon KG – Kilograms KGM – Kilogram L – Liter LB – Pound LFT – Linear Foot LNM – Linear Meters LTR – Liters

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 211

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

LYD – Linear Yard M – Meters MG – Milligram ML – Milliliter M2 – Square Meters M3 – Cubic Meters NO – Number OZ – Ounces PCS – Pieces PR – Pair PRS – Pairs SFT – Square Feet SQI – Square Inches SYD – Square Yard YD – Yard

418-# CI Comments 444 Alpha Maximum of 4 occurrences with a maximum field length of 111. Sum of field lengths of all occurrences must not exceed 444 characters.

431 Dim Weight Used Flag 1 Alpha Y if dim-weighted, else N.

439 COD Return Contact Name 35 Alpha

440 Residential Delivery Flag 1 Alpha Y if shipment is residential delivery, else N.

496 Freight Service Commitment 2 Alpha

498 Meter Number 10 Numeric

526 Form ID 4 Numeric FedEx assigned Form ID for labeling.

527 COD Return Form ID 4 Numeric FedEx assigned Form ID for COD return labeling.

535 COD Return ASTRA Bar Code 32 Alpha FedEx assigned bar code string for COD return labeling.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 212

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

536 COD Return Service Commitment 2 Alpha Service commitment for a COD return shipment. See FedEx Service Guide for a valid list of service commitments.

543 COD Return Collect Plus Freight Amount

8.2 Numeric Two explicit decimal positions. The total amount printed on the COD return label for COD service when field 186 is set to Y.

557 Message Type Code 2 Alpha/ Numeric

Optional. Valid codes include:

01 – Warning (any transaction) 02 – Informational (any transaction) 03 – Shipping Warning 04 – Shipping Info 05 – URSA Hard 06 – URSA Soft

558 Message Code 8 Alpha/ Numeric

Optional Message Code.

559 Message Text 255 Alpha/ Numeric

Optional Message Text.

612 HST Surcharge 18.2 Numeric Format: Two explicit decimal positions (ie. 5.00). Harmonized Sales Tax.

613 GST Surcharge 18.2 Numeric Format: Two explicit decimal positions (ie. 5.00). Global Sales Tax.

614 PST Surcharge 18.2 Numeric Format: Two explicit decimal positions (ie. 5.00). Provincial Sales Tax.

1005 Manifest/Invoice File Name 255 Alpha Name of the invoice/manifest file.

1006 Domain Name 255 Alpha Name of the domain for which the client will do an FTP to retrieve an invoice/manifest file.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 213

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1007 Close/Manifest Date 8 Numeric Date format: CCYYMMDD

1008 Package Ready Time 6 Numeric Time format: HHMMSS

1009 Company Close Time 6 Numeric Time format: HHMMSS

1032 Duties Payer Country Code 2 Alpha Country code associated with duties account number. (Returned in the 1301 transaction.)

1089 Rate Scale 5 Alpha Rate scale used to rate package.

1090 Rate Currency Type 3 Alpha Currency code identifier for the rated currency.

1092 Rate Zone 1 Alpha Zone used for rate if zone applies.

1096 Origin Location ID 5 Alpha/ Numeric

FedEx Express location identifier, station, BSC, Ramp, etc. Example: • COSA • COSB • EHTR • DENRT

1099 Volume Units 1 Alpha Cubic Inches or Centimeters

1115 Ship Time 6 Numeric Time format: HHMMSS

1116 Dim Units 1 Alpha Valid values: C = Centimeters I = Inches

U.S. Domestic Express must be in inches.

1117 Package Sequence 4 Numeric Sequence of package in the multiple-piece shipment. Multiple-piece shipments supported for all Ground, Express International and Domestic COD only.

1118 Release Authorization Number 10 Alpha FedEx assigned release number on file.

1119 Future Day Shipment 1 Alpha Y if shipment is future day.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 214

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1120 Inside Pickup Flag 1 Alpha Y if shipment is inside pickup. Applicable to U.S. Domestic freight service only.

1121 Inside Delivery Flag 1 Alpha Y if shipment is inside delivery. Applicable to U.S. Domestic freight service only.

1123 Master Tracking Number 20 Numeric Tracking number of the first package in a multiple-piece shipment.

1124 Master Form ID 4 Numeric Form ID of the first package in a multiple-piece shipment.

1137 URSA Uned Prefix 2 Alpha Prefix found from lookup; no rules applied.

1139 Sender SSN/ EIN 15 Numeric

1145 Recipient Department 10 Alpha

1159 Scan Description 80 Alpha Literal description of the Scan activity.

1160 Scan Location City 40 Alpha City name hosting the Station that is responsible for the scan.

1161 Scan Location State 2 Alpha State abbreviation hosting the Station that is responsible for the scan.

1162 Scan Date 8 Numeric Format: CCYYMMDD

1163 Scan Time 6 Numeric Format: HHMMSS

1164 Scan Location Country 2 Alpha Country code for where the scan occurred.

1167 Disp Exception CD 2 Alpha

1168 Status Exception CD 2 Alpha Extended definition of the scan type code’s specific type.

1171 Scan Type Code 3 Alpha Carrier’s scan code.

1174 BSO Flag 1 Alpha Y if Broker Select Option information included.

1178 URSA Suffix Code 5 Alpha

1179 Broker FDX Account Number 12 Numeric The FedEx assigned account number of the Broker who will be used to clear the shipment (if other than FedEx).

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 215

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1180 Broker Company 35 Alpha The company name of the Broker who will be used to clear the shipment (if other than FedEx).

1181 Broker Address Line 1 35 Alpha The address line 1 of the Broker who will be used to clear the shipment (if other than FedEx).

1182 Broker Address Line 2 35 Alpha The address line 2 of the Broker who will be used to clear the shipment (if other than FedEx).

1183 Broker City 35 Alpha The city name of the Broker who will be used to clear the shipment (if other than FedEx).

1184 Broker State 14 Alpha The state code of the Broker who will be used to clear the shipment (if other than FedEx). The maximum field length for US and CA is 2, 14 for all other countries.

1185 Broker Postal Code 16 Alpha The postal code of the Broker who will be used to clear the shipment (if other than FedEx). Must be numeric for U.S.; special characters allowed.

1186 Broker Country Code 2 Alpha The country code of the Broker who will be used to clear the shipment (if other than FedEx).

1187 Broker SSN/EIN 18 Alpha The SSN/EIN of the Broker who will be used to clear the shipment (if other than FedEx).

1089 Rate Scale 5 Alpha Rate scale used to rate package.

1092 Rate Zone 1 Alpha Zone 0 – A.

1193 Ship Delete Message 50 Alpha

1195 Payer Country Code 2 Alpha Country Code associated with bill to account number. (Returned in transaction 1301.)

1200 Hold At Location (HAL) Flag 1 Alpha Y if shipment is Hold At FedEx Location.

1201 Sender’s Email Address FDXE-120 FDXG-35

Alpha The e-mail address of the sender.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 216

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1202 Recipient’s Email Address FDXE-120 FDXG-35

Alpha The e-mail address of the recipient.

1203 Optional ShipAlert Message 120 Alpha Customer specified message to be included in the shipment notification.

1204 Email Notification Address FDXE-120 FDXG-35

Alpha Delivery Alert: • Maximum of three occurrences allowed for FDXE. ShipAlert: • Maximum of three occurrences allowed for FDXE. • Maximum of one occurrence allowed for FDXG.

1206 ShipAlert Notification Flag 1 Alpha Valid values: • Y • N Defaults to N.

1211 POD Address 35 Alpha

1213 Proactive Notification Flag 1 Alpha

1237 COD Return Phone 15 Numeric Required if the COD Flag is set to Y. Phone number of the COD remittance party. No embedded dashes.

1238 COD Return Company 35 Alpha/ Numeric

Company Name of the COD remittance party.

1239 COD Return Department 10 Alpha/ Numeric

Department code of the COD remittance party.

1240 COD Return Address 1 35 Alpha/ Numeric

Required if the COD Flag is set to Y. Address 1 of the COD remittance party.

1241 COD Return Address 2 35 Alpha/ Numeric

Address 2 of the COD remittance party.

1242 COD Return City 35 Alpha City name of the COD remittance party.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 217

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1243 COD Return State 14 Alpha State code of the COD remittance party.

1244 COD Return Postal Code 9 Alpha/ Numeric

Required if the COD Flag is set to Y. Postal code of the COD remittance party.

1253 Packaging List Enclosed Flag 1 Alpha Y if packaging list is enclosed.

1265 Hold At Location Contact Name 35 Alpha

1266 Saturday Delivery Flag 1 Alpha Y if shipment is Saturday delivery.

1267 Saturday Pickup Flag 1 Alpha Y is shipment is Saturday pickup.

1268 Dry Ice Flag 1 Alpha Y if shipment contains Dry Ice.

1271 Shipper’s Load And Count (SLAC) 5 Numeric Applicable to International Priority Freight (IPFS) and International Economy Freight (IEFS) only. SLAC = total shipment pieces i.e. 3 boxes and 3 pallets of 100 pieces each = SLAC of 303. Values must be 1-5 characters in length.

1272 Booking Number 12 Numeric Applicable to IPFS/IEFS only. The booking number for International Freight shipments. Values must be 8-12 characters in length.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 218

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1273 Packaging Type 2 Numeric FedEx Express shipping packaging types are: 01 – Other packaging 02 – FedEx Pak 03 – FedEx Box 04 – FedEx Tube 06 – FedEx Envelope *15 – FedEx 10kg Box (International only) *25 – FedEx 25kg Box (International only)

*Ground shipping packaging types are: 01 – Customer packaging

Defaults to 01 if not specified. *Not allowed with MPS shipments

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 219

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1274 Service Type 2 Numeric FedEx Express U.S. Domestic shipping service types are: 01 - FedEx Priority 03 - FedEx 2day 05 - FedEx Standard Overnight 06 - FedEx First Overnight 20 - FedEx Express Saver 70 - FedEx 1day Freight 80 - FedEx 2day Freight 83 - FedEx 3dayFreight

FedEx Express International shipping service types are: 01 - FedEx International Priority 03 - FedEx International Economy 06 - FedEx International First 70 - FedEx International Priority Freight 86 - FedEx International Economy Freight

FedEx Ground U.S. Domestic shipping service types are: 90 - FedEx Home Delivery 92 - FedEx Ground Service

FedEx Ground International shipping service types are: 92 - FedEx Ground Service

1297 Customer Invoice Number 15 Alpha

1300 Purchase Order Number 16 Alpha Customer assigned purchase order number.

1331 Dangerous Goods Type 1 Alpha I if inaccessible dangerous goods. A if accessible dangerous goods.

1332 Alcohol Flag 1 Alpha Y if shipment contains alcohol.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 220

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1333 Drop Off Type 1 Alpha Valid values: 1 if regular pickup 2 if request courier 3 if drop box 4 if drop at BSC 5 if drop at station

Only 1 (regular pickup), 2 (request courier), or 5 (drop at station) are allowed with International freight shipping. This field does not dispatch a courier.

1337 Package Content Information 40 Alpha Description of package contents.

1339 Estimated Delivery Date 8 Numeric Format: CCYYMMDD

1340 Estimated Delivery Time 6 Numeric Format: HHMMSS

1341 Sender Pager Number 15 Alpha The pager number of the sender.

1342 Recipient Pager Number 15 Alpha The pager number of the recipient.

1343 Broker Email Address 120 Alpha The e-mail address of the broker.

1344 Broker Fax Number 15 Alpha The fax number of the broker.

1352 Sender EIN/SSN Indicator

1 Alpha This identifier identifies value in field tag 1139. Valid values:

S = SSN E = EIN D = DUNS

1358 AES / FTSR Exemption Number 32 Alpha / Numeric

The full AES SED exemption legend is entered in this field. When all commodities in the shipment fall under an FTSR exemption, the full FTSR exemption legend is entered in this field.

1366 Close/Manifest Time 6 Numeric Time format: HHMMSS

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 221

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1367 Close/Manifest Data Buffer Variable Length

Alpha This buffer will contain the manifest report(s) for FedEx Ground shipments. Data/Manifest format: ASCII

1368 Label Type 4 Numeric Valid value: 2 = 2D Common

1369 Label Printer Type 4 Numeric Valid values: 1 = Laser printer 2 = Eltron Orion (EPL2) 3 = Eltron Eclipse (EPL2) 4 = Zebra ZPL 5 = Unimark

1370 Label Media Type 4 Numeric Valid values: 3 = Format 354 with doc tab information at bottom of label (4x6 ¾ thermal label) 4 = Format 435 without doc tab information (4x6 thermal label) 5 = Plain paper (PNG) - Supported for FedEx Ground and Express Shipping 6 = Format 354 with doc-tab information at top of label (4x6 ¾ thermal label)

1371 Manifest Only Request Flag 1 Alpha N or blank (default) = Close out current shipment cycle and create the manifest, MTW, Hazardous Materials Report. Y = Requesting a report generated from a previous Close. Must indicate report in tag 3014.

1372 Manifest Total 4 Numeric The number of manifest reports returned in a manifest data buffer.

1376 Rate Weight Unit Of Measure 3 Alpha Valid units: • LBS • KGS

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 222

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1377 Dim Weight Unit Of Measure 3 Alpha Valid units: LBS KGS

1392 Inbound Visibility Block Shipment Data Indicator

1 Alpha/ Numeric

Valid values: 1 = No – Do not block ship data. 2 = Yes – Block ship data

1394 Shipment Content Records Total 3 Numeric Zero or not present = No IV Receive Detail Data sets. 1 or more = indicates the Number of IV Receive Detail Data Sets. Maximum value = 50.

1395 Part Number 20 Alpha/ Numeric

1396 SKU/Item/UPC# 15 Alpha/ Numeric

1397 Receive Quantity 6 Alpha/ Numeric

1398 Description 80 Alpha/ Numeric

Description of item being shipped.

1399 AES Entry Number 15 Alpha/ Numeric

Applicable for FICE shipments Only. Only required for Commodities imported into the U.S. for Export to a third-party country of destination.

1401 Total Package Weight 6.1 Numeric One explicit decimal position.

1402 Billed Weight 6.1 Numeric One explicit decimal position. This is the weight used to render freight charges.

1403 Dim Weight 9.1 Numeric Dimensional weight calculated based on the height, width, and length of a package. One explicit decimal position.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 223

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1404 Total Volume 13.1 Numeric One explicit decimal position.

1405 Alcohol Volume 3.3 Numeric The quantity of alcohol being shipped. Unit of measurement is liters. Three explicit decimal positions.

1406 Dry Ice Weight 4.1 Numeric Required only if Dry Ice is selected. One explicit decimal position.

1407 Commodity Weight 9.1 Numeric One explicit decimal position.

1408 Commodity Unit Value 11.6 Numeric Value of each ‘Unit’ in Unit quantity. Six explicit decimal positions.

1410 Commodity Customs Value 8.6 Numeric Total customs of commodity line item (all pieces). Six explicit decimal positions.

1411 Total Customs Value 14.2 Numeric Two explicit decimal positions. This value includes the total value of the shipment along with freight, insurance, and miscellaneous charges. For Express International MPS, the Total Customs Value is in the Master transaction and all Child transactions.

1412 Freight Charge 16.2 Numeric Two explicit decimal positions.

1413 Insurance Charge 16.2 Numeric Two explicit decimal positions.

1414 Taxes/ Miscellaneous Charge

16.2 Numeric Two explicit decimal positions.

1415 Declared Value/Carriage Value 8.2 Numeric Two explicit decimal positions. The declared value of package contents. This value cannot exceed the total customs value.

1416 Base Rate Amount 11.2 Numeric Two explicit decimal positions.

1417 Total Surcharge Amount 11.2 Numeric Two explicit decimal positions.

1418 Total Discount Amount 11.2 Numeric Two explicit decimal positions.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 224

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1419 Net Charge Amount 11.2 Numeric Two explicit decimal positions.

1420 Total Rebate Amount 11.2 Numeric Two explicit decimal positions.

1421 COD Surcharge 11.2 Numeric Two explicit decimal positions (i.e. 5.00).

1422 List COD Surcharge 11.2 Numeric Two explicit decimal positions (i.e. 5.00).

1423 Saturday Pickup Surcharge 11.2 Numeric Two explicit decimal positions (i.e. 5.00).

1424 List Saturday Pickup Surcharge 11.2 Numeric Two explicit decimal positions (i.e. 5.00).

1425 Declared Value Surcharge 11.2 Numeric Two explicit decimal positions (i.e. 5.00).

1426 List Declared Value Surcharge 11.2 Numeric Two explicit decimal positions (i.e. 5.00).

1427 Variable Handling Charge 7.2 Numeric Contains amount (in the billing currency for the shipment) to be added to the Freight charge. Interpreted as a dollar amount if Variable Handling Type = 1. Interpreted as a percentage if Variable Handling Type = 2, 3, or 4. Format: 9999999.99 explicit decimal. 10 total length including decimal place.

1428 Variable Handling Charge Amount 7.2 Numeric Format: 9999999.99 explicit decimal. 10 total length including decimal place. Contains the Handling Charge amount (in billing currency for the shipment) that was calculated based on Discounted freight (either Freight or Net freight as specified by Variable Handling Charge Type field) plus the value input in Variable Handling Charge. If the Variable Handling Type = 1, this field will be equal to the Variable Charge.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 225

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1429 List Variable Handling Charge Amount 7.2 Numeric Format: 9999999.99 explicit decimal. 10 total length including decimal place. Contains Handling Charge amount (in billing currency for the shipment) that was calculated based on List freight (either Freight or Net Freight as specified by Variable Handling Charge Type field) plus the Variable Handling Charge. If the Variable Handling Type = 1, this field will be equal to the Variable Charge.

1430 Total Customer Charge 18.2 Numeric Format: 999999999999999999.99. 21 total length including decimal place. Includes 2 explicit decimal places. Contain Shippers discounted Net Freight Charge (in the billing currency) plus Variable Handling Charge Amount. Will contain piece level or shipment level dependent on the Variable Handling Charge Level field.

1431 List Total Customer Charge 18.2 Numeric Format: 999999999999999999.99. 21 total length including decimal place. Includes 2 explicit decimal places. Contains Shippers list Net Charge (in the billing currency) plus List Variable Handling Charge Amount. Will contain piece level or shipment level dependent on the Variable Handling Charge Level field.

1432 Customer COD Amount 10.2 Numeric The Customer input COD amount (prior to any accumulations). Two explicit decimals.

1433 COD Collect Amount 10.2 Numeric Two explicit decimals. The COD cash amount (after any accumulations) that must be collected upon delivery of a package shipped using the COD special service.

1434 Saturday Delivery Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00).

1435 List Saturday Delivery Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00).

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 226

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1436 Dangerous Goods Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express Accessible and Inaccessible Dangerous Goods only.

1437 List Dangerous Goods Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express Accessible and Inaccessible Dangerous Goods only.

1438 Out of Pickup Area / H3 Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to U.S. Domestic Express Freight only.

1439 List Out of Pickup Area / H3 Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to U.S. Domestic Express Freight only.

1440 Out of Delivery Area / H3 Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to U.S. Domestic Express Freight only.

1441 List Out of Delivery Area / H3 Surcharge

18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to U.S. Domestic Express Freight only.

1442 Inside Pickup Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express only.

1443 List Inside Pickup Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express only.

1444 Inside Delivery Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express only.

1445 List Inside Delivery Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express only.

1446 Residential Delivery Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express only.

1447 List Residential Delivery Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express only.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 227

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1448 Priority Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express only.

1449 List Priority Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express only.

1450 More Data Indicator 1 Alpha Y = more data available N = no more data available

1451 Sequence Number 4 Numeric Value will default to 1 if blank.

1452 Last Tracking Number 20 Numeric Customer should provide last returned tracking number to Request subsequent sets of track by reference data.

1453 Track Reference Type 2 Alpha/ Numeric

Valid values: 1 = Shipper/Customer Reference 2 = Ground PO 3 = Ground Invoice Number FDXE: Only value allowed is 1. FDXG: Values 2 and 3 allowed.

1454 Track Reference 35 – FDXE 30 – FDXG

Alpha/ Numeric

Track by Reference qualifier string.

1456 SPOD Request Type 1 Alpha/ Numeric

Valid values: F = SPOD Fax Letter L = SPOD Letter file

Case sensitive.

1457 SPOD Letter 1 Numeric Valid value: 1 = PNG

Defaults to 1 (PNG) if not present.

1458 SPOD Fax Recipient Name 35 Alpha/ Numeric

1459 SPOD Fax Recipient Number 15 Numeric Limit to 10 digit (Domestic) fax numbers only.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 228

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1460 SPOD Fax Sender Name 35 Alpha/ Numeric

1461 SPOD Fax Sender Phone Number 15 Numeric

1462 Language Indicator 3 Alpha Valid values: EN = English FR = Canadian French.

Case sensitive.

1463 SPOD Fax Mail Recipient Company Name

35 Alpha/ Numeric

1464 SPOD Fax Mail Recipient Address Line 1

35 Alpha/ Numeric

1465 SPOD Fax Mail Recipient Address Line 2

35 Alpha/ Numeric

1466 SPOD Fax Mail Recipient City 30 Alpha

1467 SPOD Fax Mail Recipient State 2 Alpha

1468 SPOD Fax Mail Recipient Postal Code 9 Alpha

1469 SPOD Fax Mail Recipient Country 2 Alpha/ Numeric

US or CA only.

1470 SPOD Fax Confirmation 20 Alpha/ Numeric

1471 SPOD Letter Alpha/ Numeric

Encoded PNG returned upon successful letter Request.

1472 SPOD Ground Recipient Name 35 Alpha/ Numeric

1473 SPOD Ground Recipient Company Name

35 Alpha/ Numeric

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 229

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1474 SPOD Ground Recipient Address Line 1

35 Alpha/ Numeric

1475 SPOD Ground Recipient Address Line 2

35 Alpha/ Numeric

1476 SPOD Ground Recipient City 30 Alpha

1477 SPOD Ground Recipient State/Province

2 Alpha

1478 SPOD Ground Recipient Postal Code 9 Numeric

1479 SPOD Ground Recipient Country 2 Alpha Valid values: • US • CA

1480 More Information 30 Alpha/ Numeric

1485 Alternate Sender / Return Address Contact Name

35 Alpha/ Numeric

Contact name for an Alternate Sender which prints on label in the “sender” area.

1486 Alternate Sender / Return Address Company Name

35 Alpha/ Numeric

Company Name for an Alternate Sender which prints on label in the “sender” area.

1487 Alternate Sender / Return Address Line 1

35 Alpha/ Numeric

Address line 1 for an Alternate Sender which prints on label in the “sender” area.

1488 Alternate Sender / Return Address Line 2

35 Alpha/ Numeric

Address line 2 for an Alternate Sender which prints on label in the “sender” area.

1489 Alternate Sender / Return Address City Name

FDXE-35 FDXG-20

Alpha City name for an Alternate Sender which prints on label in the “sender” area.

1490 Alternate Sender / Return Address State Code

2 Alpha State code for an Alternate Sender which prints on label in the “sender” area.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 230

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1491 Alternate Sender / Return Address Postal Code

16 Alpha/ Numeric

Postal code for an Alternate Sender which prints on label in the “sender” area. Special characters allowed.

1492 Alternate Sender / Return Address Phone Number

15 Alpha/ Numeric

Phone number for an Alternate Sender which prints on label in the “sender” area.

1507 List Total Surcharge Amount 11.2 Numeric Sum of total list surcharges

1525 Effective Net Discount 11.2 Numeric

1528 List Net Charge Amount 11.2 Numeric List net charge amount.

1529 Rate Indicator 1 Numeric Valid values: 1 = Discount Rate 2 = List and discounted rates

If tag 1529 is invalid or not present, discount Express rates and list Ground rates (pre-October ’02 behavior) will be returned.

1530 List Base Rate Amount 11.2 Numeric List base rate amount.

1531 List Total Discount Amount 11.2 Numeric List total discount amount (will always be 0).

1532 List total Rebate Amount 11.2 Numeric List total rebate amount (will always be 0).

1534 Detail Scan Indicator 1 Alpha N or not present – defaults to Summary/Profile data, which includes one single scan structure with the most recent scan. Y – returns Detail Scan Activity (multiple scan structure) for each package. Profile will return the last package status (most recent scan) and data elements other than the detail scan activity.

1535 Paging Token Variable Alpha/ Numeric

Indicator for availability of additional tracking data.

1536 Number of Relationships 3 Numeric Number of relationships the “Search String” that was input into the Request transaction participates in.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 231

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1537 Search / Relationship String 40 Alpha/ Numeric

The value to be tracked. Possible values: • Express MPS Master Tracking Number • Express Customer Reference • Ground PO • Ground Customer Reference • Ground Invoice • Ground Shipment ID

1538 Search / Relationship Type Code 3 Alpha/ Numeric

Identifies all relationships that the corresponding tracking number participates in. This field will correspond to the relationship string (field tag 1537). Valid values:

0 or not present – defaults to Tracking Number/Door Tag 1 – Express MPS Master Number 2 – Express Track By Reference 3 – Ground Track By Reference – PO 4 – Ground Track By Reference – Customer Reference 5 – Ground Track By Reference – Invoice 7 – Ground Track By Reference – Shipment ID 10 – Return Materials Authorization

1551 Delivery Notification Flag 1 Alpha Valid values: N for No, do not send a notification of delivery Y for Yes, send a notification of delivery

Defaults to N.

1552 Language Code 2 Alpha Valid values: en = English fr = French (shipper country must be CA)

Defaults to en. Must be in lower case.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 232

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1553 Shipper Delivery Notification Flag 1 Alpha Valid values: N for No, do not send shipper a notification of delivery Y for Yes, send shipper a notification of delivery

Defaults to N.

1554 Shipper ShipAlert Flag 1 Alpha Valid values: N for No, do not send shipper a notification of shipment Y for Yes, send shipper a notification of shipment

Defaults to N.

1555 Shipper Language Code 2 Alpha Valid values: en = English fr = French (shipper country must be CA)

Defaults to en. Must be in lower case.

1556 Recipient Delivery Notification Flag 1 Alpha Valid values: N for No, do not send recipient a notification of delivery Y for Yes, send recipient a notification of delivery

Defaults to N.

1557 Recipient ShipAlert Flag 1 Alpha Valid values: N for No, do not send recipient a notification of shipment Y for Yes, send recipient a notification of shipment

Defaults to N.

1558 Recipient Language Code 2 Alpha Valid values: en = English fr = French (shipper country must be CA)

Defaults to en. Must be in lower case.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 233

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1559 Broker Delivery Notification Flag 1 Alpha Valid values: N for No, do not send broker a notification of delivery Y for Yes, send broker a notification of delivery

Defaults to N.

1560 Broker ShipAlert Flag 1 Alpha Valid values: N for No, do not send broker a notification of shipment Y for Yes, send broker a notification of shipment

Defaults to N.

1561 Broker Language Code 2 Alpha Valid values: en = English fr = French (shipper country must be CA)

Defaults to en. Must be in lower case.

1562 FedEx Staffed Location Flag 1 Alpha Valid values: • N • Y

1563 FedEx Self-Service Location Indicator 1 Alpha Valid values: • N Y

1564 FASC (FedEx Authorized Shipping Center) Location Flag

1 Alpha Valid values: • N Y

1565 Latest Express Drop-off Flag 1 Alpha Valid values: • N Y

1566 Express Drop-off After Time 35 Alpha/ Numeric

Format: HH:MMPM/AM

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 234

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1567 FedEx Location Intersection/Street Address

35 Alpha/ Numeric

Free Form Field. Can contain street address or intersection. Ex. ‘5550 Main St.’ (street address) ‘Main and 22nd St.’ (intersection)

1568 Distance 15 Alpha/ Numeric

The distance from the search criteria to the FedEx location. Ex. 40 miles, 12.5 miles Free form field.

1569 Hours of Operation Mon-Fri

35 Alpha/ Numeric

Free form field. Ex. “9:00 AM – 6:45 PM”

1570 Hours of Operation Sat 35 Alpha/ Numeric

Free form field. Ex. “Sat 9:00 AM – 6:45” or “No Sat Pickup”

1571 Last Express Drop-off Time Mon-Fri 35 Alpha/ Numeric

Free form field. Ex. “5:00 PM”

1572 Last Express Drop-off Time Sat 35 Alpha/ Numeric

Free form field. Format may be returned in HH:MM PM/AM OR Free form text “No Sat pickup”

1573 Express Service Flag 1 Alpha Valid values: • N Y Y = Express Available

1574 Location Count 2 Numeric Number of locations returned. 1-10 valid.

1575 FedEx Location Business Name 35 Alpha/ Numeric

Free form text field. Examples: “Kinko’s”, “Business Edge”, “The Mail Center”, “Copymax”, “Postoffice”, “FedEx World Service Center”, “FedEx Drop Box”, “Self Service Location”.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 235

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1576 FedEx Location Business Type 35 Alpha/ Numeric

Free form text field Examples: “FedEx Authorized Ship Center”, “Self-Service Location”, “FedEx Staffed”.

1577 FedEx Location City 35 Alpha/ Numeric

1578 FedEx Location State 2 Alpha/ Numeric

1579 FedEx Location Postal Code 9 Alpha/ Numeric

1580 Dangerous Goods Flag 1 Alpha Valid values: • N Y

1581 Saturday Service Flag 1 Alpha Valid values: • N Y

1582 Begin Date 8 Numeric Begin date of shipments being tracked. Format: CCYYMMDD

1583 End Date 8 Numeric End date of shipments being tracked. Format: CCYYMMDD

1584 Tracking Groups 99 Numeric Number of Tracking Groups.

1585 Alternate Sender / Return Address Country Code

2 Alpha Required if Alternate Sender / Return Address Flag = Y.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 236

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1586 Alternate Sender / Return Address Flag

1 Alpha Valid values: • N Y If = Y Alternate Sender/Return Address prints on label in the “sender” area. Defaults to N, sender address prints on label in the “sender” area.

1587 Alternate Sender / Return Address Department

10 Alpha/ Numeric

Required if Alternate Sender / Return Address Flag = Y.

1588 Variable Handling Type 1 Alpha/ Numeric

Specifies what type of Variable Handling charges to assess and on which amount. Valid values:

0 – None (Default) 1 – add Fixed Amount to Net Freight Charges 2 – add variable % of Freight* Charges 3 – add variable % of Net Freight Charges 4** – add Variable % of Net Freight charges minus CA Taxes. (If 4 is requested by a non-Canadian origin customer, it will behave like value 3.)

For Ground, it is the freight charge. For Express, it is the freight charge minus any discounts. **Net Freight = (freight – discount + surcharges + taxes) Taxes will be included in the Net Charge where applicable for “CA” origin shipments.

1594 COD Report Buffer Alpha/ Numeric

Ground COD Report Buffer. Format: Base 64 encoded ASCII

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 237

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1606 Variable Handling Charge Level 1 Alpha/ Numeric

Apply fixed or variable handling charges at package or shipment level.

0 or not present – per package (default) 1 – per shipment

***Value 1 is applicable only on last piece of Ground or Express MPS shipment only. Note: Value 1 = Shipment level affects the entire shipment. Anything else sent in Child will be ignored.

1607 Doc Tab Header 1 23 (Refer to tag 2973)

Alpha/ Numeric

Free form text for doc-tab header on the shipping label.

1608 Doc Tab Header 2 23 (Refer to tag 2973)

Alpha/ Numeric

Free form text for doc-tab header on the shipping label.

1609 Doc Tab Header 3 23 (Refer to tag 2973)

Alpha/ Numeric

Free form text for doc-tab header on the shipping label.

1610 Doc Tab Header 4 23 (Refer to tag 2973)

Alpha/ Numeric

Free form text for doc-tab header on the shipping label.

1611 Doc Tab Header 5 23 (Refer to tag 2973)

Alpha/ Numeric

Free form text for doc-tab header on the shipping label.

1612 Doc Tab Header 6 23 (Refer to tag 2973)

Alpha/ Numeric

Free form text for doc-tab header on the shipping label.

1613 Doc Tab Header 7 23 (Refer to tag 2973)

Alpha/ Numeric

Free form text for doc-tab header on the shipping label.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 238

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1614 Doc Tab Header 8 23 (Refer to tag 2973)

Alpha/ Numeric

Free form text for doc-tab header on the shipping label.

1615 Doc Tab Header 9 23 (Refer to tag 2973)

Alpha/ Numeric

Free form text for doc-tab header on the shipping label.

1616 Doc Tab Header 10 23 (Refer to tag 2973)

Alpha/ Numeric

Free form text for doc-tab header on the shipping label.

1617 Doc Tab Header 11 23 (Refer to tag 2973)

Alpha/ Numeric

Free form text for doc-tab header on the shipping label.

1618 Doc Tab Header 12 23 (Refer to tag 2973)

Alpha/ Numeric

Free form text for doc-tab header on the shipping label.

1621 Customer Doc Tab Barcode 30 Alpha/ Numeric

Optional. Required if field tag 2973 (DocTab Type Indicator) has a value of 2. Maximum of 30 characters to be encoded as a bar code on the Doc Tab of supported shipping labels.

1624 Doc Tab Field 1 23 (Refer to tag 2973)

Alpha/ Numeric

This field will contain the CTS tag number of the data field to be printed in the designated doc-tab area on the shipping label.

1625 Doc Tab Field 2 23 (Refer to tag 2973)

Alpha/ Numeric

This field will contain the CTS tag number of the data field to be printed in the designated doc-tab area on the shipping label.

1626 Doc Tab Field 3 23 (Refer to tag 2973)

Alpha/ Numeric

This field will contain the CTS tag number of the data field to be printed in the designated doc-tab area on the shipping label.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 239

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1627 Doc Tab Field 4 23 (Refer to tag 2973)

Alpha/ Numeric

This field will contain the CTS tag number of the data field to be printed in the designated doc-tab area on the shipping label.

1628 Doc Tab Field 5 23 (Refer to tag 2973)

Alpha/ Numeric

This field will contain the CTS tag number of the data field to be printed in the designated doc-tab area on the shipping label.

1629 Doc Tab Field 6 23 (Refer to tag 2973)

Alpha/ Numeric

This field will contain the CTS tag number of the data field to be printed in the designated doc-tab area on the shipping label.

1630 Doc Tab Field 7 23 (Refer to tag 2973)

Alpha/ Numeric

This field will contain the CTS tag number of the data field to be printed in the designated doc-tab area on the shipping label.

1631 Doc Tab Field 8 23 (Refer to tag 2973)

Alpha/ Numeric

This field will contain the CTS tag number of the data field to be printed in the designated doc-tab area on the shipping label.

1632 Doc Tab Field 9 23 (Refer to tag 2973)

Alpha/ Numeric

This field will contain the CTS tag number of the data field to be printed in the designated doc-tab area on the shipping label.

1633 Doc Tab Field 10 23 (Refer to tag 2973)

Alpha/ Numeric

This field will contain the CTS tag number of the data field to be printed in the designated doc-tab area on the shipping label.

1634 Doc Tab Field 11 23 (Refer to tag 2973)

Alpha/ Numeric

This field will contain the CTS tag number of the data field to be printed in the designated doc-tab area on the shipping label.

1635 Doc Tab Field 12 23 (Refer to tag 2973)

Alpha/ Numeric

This field will contain the CTS tag number of the data field to be printed in the designated doc-tab area on the shipping label.

1636 Delivery Area Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express only.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 240

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1637 List Delivery Area Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express only.

1638 Fuel Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express only.

1639 List Fuel Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express only.

1640 FICE Surcharge 18.2 Numeric FedEx International Controlled Export. Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express only.

1642 Value Added Tax 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express only.

1644 Offshore Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express only.

1645 List Offshore Surcharge 18.2 Numeric Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express only.

1649 Other Surcharges 18.2 Numeric Accumulation of any Express surcharges that do not have a defined field. Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express only.

1650 List Other Surcharges 18.2 Numeric Accumulation of any Express surcharges that do not have a defined field. Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Express only.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 241

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1651 B13A Filing Option 1 Numeric Required field for Canadian Export non-document shipments destined to a country other than the U.S., Puerto Rico or the U.S. Virgin Islands. Valid values:

1 = No B13A Required 2 = Manual B13A Attached 3 = Filed Electronically 4 = Summary Reporting

1652 Export Statement Data 50 Alpha/ Numeric

This field is used to indicate Export required data for any country. If B13A filing option = 2, this field should contain the B13A Transaction Number. If B13A filing option = 3, this field should contain the B13A Authorization Code Number. If B13A filing option = 4, this field should contain the B13A Summary ID Number. For B13A Transaction Number, must be exactly 21 alpha/numeric characters. For Authorization Code Number, must be exactly 17 or 23 alpha/numeric characters. The Authorization Code Number is comprised of the B13A Authorization ID Number and the B13A Form ID Number. For Summary Reporting Number, must be exactly 7 alphanumeric characters. For Canada Export Declaration B13A, only alpha A-Z and numeric 0-9 characters are allowed.

1653 Export Permit Number 10 Alpha/ Numeric

Optional. Applicable for any Canada export (International) non-document shipment of any value to any destination: US, PR, US Virgin Islands or Rest of World other than Canada. No special characters allowed.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 242

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1704 Service Type Description 70 Alpha A description of what service was selected for the delivery of the package is returned.

1705 Deliver To Description 25 Alpha A description of where the package was delivered (Front Desk, Back Door, etc.) is returned.

1706 Signed For 25 Alpha If signature is required, the name of the person who signed for the package will be returned If signature is not required, the place the package was delivered (Front Desk, Back Door, etc.) is returned.

1707 Delivery Time 6 Alpha Time format: HHMMSS

1711 Status Exception Description 40 Alpha Most recent scan description.

1713 Cod Flag 1 Alpha This field is only used for the 402/502 Tracking transactions. All other transactions use field tag 27 to indicate COD. Y returned if COD. N if tag not returned.

1715 Number Of Track Activities 2 Numeric The number of track activities included in the Reply to a track Request.

1716 Delivery Reattempt Date 8 Alpha/ Numeric

Format: CCYYMMDD

1717 Delivery Reattempt Time 6 Alpha/ Numeric

Format: HHMMSS

1718 Package Type Description 40 Alpha/ Numeric

Packaging type (i.e. Pak, Box, Tube, etc.).

1720 Delivery Date 8 Numeric Format: CCYYMMDD

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 243

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1721 Tracking Activity Line 1 130 Alpha Format is as follows: - Scan Type/Exception Description 40 - Filler 1 - Scan Type Code 2 - Filler 1 - Scan City 30 - Filler 1 - Scan State 2 - Filler 1 - Scan Country Code 2 - Filler 1 - Scan Date 8 - Filler 3 - Scan Time 4 - Filler 3 - Scan Cage Comment 30 - Filler 1 Total characters: 130

1722 Tracking Activity Line 2 130 Alpha See field tag 1721 for field format.

1723 Tracking Activity Line 3 130 Alpha See field tag 1721 for field format.

1724 Tracking Activity Line 4 130 Alpha See field tag 1721 for field format.

1725 Tracking Activity Line 5 130 Alpha See field tag 1721 for field format.

1726 Tracking Activity Line 6 130 Alpha See field tag 1721 for field format.

1727 Tracking Activity Line 7 130 Alpha See field tag 1721 for field format.

1728 Tracking Activity Line 8 130 Alpha See field tag 1721 for field format.

1729 Tracking Activity Line 9 130 Alpha See field tag 1721 for field format.

1730 Tracking Activity Line 10 130 Alpha See field tag 1721 for field format.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 244

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

1731 Tracking Activity Line 11 130 Alpha See field tag 1721 for field format.

1732 Tracking Activity Line 12 130 Alpha See field tag 1721 for field format.

1733 Tracking Activity Line 13 130 Alpha See field tag 1721 for field format.

1734 Tracking Activity Line 14 130 Alpha See field tag 1721 for field format.

1735 Tracking Activity Line 15 130 Alpha See field tag 1721 for field format.

1958 Admissibility Package Type 3 Alpha/ Numeric

Required if field tag 1273 (FedEx Packaging Type) is set to 01 – Other (Express) or Customer (Ground) packaging. Applicable for all origins to Canada (excluding Intra-Canada), CA to US, CA to PR, MX to US, and MX to PR. Admissibility Package Types: • BAG • BBL • BSK • BOX • BXT • BDL • CAG • CTN • CAS • CHS • CNT • CRT • CYL • DRM • ENV • PKG • PAL • PLT

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 245

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

• PCL • PCS • REL • ROL • SAK • SHW • SKD • TNK • TBN • TBE • UNT • BOX

2208 Email Label User ID 10 Alpha/ Numeric

2210 RMA Number 20 Alpha/ Numeric

Optional. Unique Identifier for the return order.

2254 Recipient Fax Number 15 Numeric The recipient fax number for a specific shipment. The maximum length is 10 for US and CA, 15 for all other countries.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 246

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

2382 Return Shipment Indicator 1 Alpha/ Numeric

Using tag 2382 with Ground return shipments allows packages to be shipped from anywhere to anywhere. If tag 2382 is not used, the system assumes that the package is coming from the account origin destination and not any other location. If tag 2382 is not used with Ground return shipments, routing, tracking, rating and service will be incorrect for these shipments. Valid values:

0 or not present = Not a return shipment. 2 = Return Shipment, Return Manager

2387 URL Expiration date 8 Numeric Required. Date entered can be current date through current date plus thirty calendar days (inclusive) from the date the e-mail label is requested. Format: YYYYMMDD

2388 URL Email Message 200 Alpha/ Numeric

Optional. Goes with field 2392. Contains a customized message from the merchant to the return shipper.

2389 Merchant Contact Phone 10 Numeric Required. This phone number can differ from the merchant phone number for the shipment. This phone number is specific to the e-mail label and will be used in case the return shipper needs to contact the merchant/recipient.

2390 Email Label surcharge 21 Numeric

2391 *List Email Label Surcharge 21 Numeric

2392 URL Email Address 120 Alpha/ Numeric

URL for each label. Cannot contain single or double quotes

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 247

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

2393 Email Label URL 190 Alpha/ Numeric

URL for each label. Cannot contain single or double quotes

2394 Email Label Request Date Time 15 Numeric Date the E-mail Label was requested. Format: CCYYMMDDTHHMMSS

2396 Document Description Code Alpha/ Numeric

Valid values: 0 – Correspondence/No Commercial Value 1 – Accounting Documents 2 – Analysis Reports 3 – Applications (Completed) 4 – Bank Statements 5 – Bid Quotations 6 – Birth Certificates 7 – Bills of Sale 8 – Bonds 9 – Business Correspondence 10 – Checks (Completed) 11 – Claim Files 12 – Closing Statements 13 – Conference Reports 14 – Contracts 15 – Cost Estimates 16 – Court Transcripts 17 – Credit Applications 18 – Data Sheets 19 – Deeds 20 – Employment Papers 21 – Escrow Instructions 22 – Export Papers 23 – Financial Statements

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 248

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

24 – Immigration Papers 25 – Income Statements 26 – Insurance Documents 27 – Interoffice Memos 28 – Inventory Reports 29 – Invoices (Completed) 30 – Leases 31 – Legal Documents 32 – Letters and Cards 33 – Letter of Credit Packets 34 – Loan Documents 35 – Marriage Certificates 36 – Medical Records 37 – Office Records 38 – Operating Agreements 39 – Patent Applications 49 – Permits 41 – Photocopies 42 – Proposals 43 – Prospectuses 44 – Purchase Orders 45 – Quotations 46 – Reservation Confirmation 47 – Resumes 48 – Sales Agreements 49 – Sales Reports 50 – Shipping Documents 51 – Statements/Reports 52 – Statistical Data

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 249

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

53 – Stock Information 54 – Tax Papers 55 – Trade Confirmation 56 – Transcripts 57 – Warranty Deeds

2397 Purpose of Shipment Code 38 Alpha/ Numeric

Valid values: 01 – Sold 02 – Not Sold 03 – Gift 04 – Sample 05 – Repair and Return 06 – Personal Effects

2399 Signature Option 1 Alpha/ Numeric

Optional. Valid values:

1 = Deliver without Signature 2 = Indirect Signature 3 = Direct Signature 4 = Adult Signature

Note: • Alcohol shipments always require an Adult Signature and

a surcharge is applied. No other signature option is available for alcohol shipments.

• No signature option is available for Hold at Location shipments.

• COD, Dangerous Goods, Ground HazMat, FedEx Home Delivery with Appointment Delivery and shipments with an insurance value greater than $499 USD require a Direct Signature, and a surcharge is not applied. Adult Signature is available as an upgrade for U.S. Domestic FedEx

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 250

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

Ground and FedEx Express shipments, and a surcharge is applied if Adult Signature is selected. Indirect Signature and Deliver without Signature are not available for these types of shipments.

• All other non-residential U.S. Domestic FedEx Express and FedEx Ground shipments and all International shipments require an Indirect Signature. Direct Signature and Adult Signature are available as an upgrade for U.S. Domestic FedEx Express shipments. Direct Signature is available as an upgrade for U.S. Domestic and International FedEx Ground shipments. A surcharge will be applied if an upgrade is selected. Deliver without Signature is also available for U.S. Domestic FedEx Express shipments only.

• All other residential U.S. Domestic FedEx Express and FedEx Ground shipments are handled as Deliver without Signature. Indirect Signature, Direct Signature, and Adult Signature are available as an upgrade for U.S. Domestic FedEx Express shipments, and a surcharge will be applied if an upgrade is selected. Indirect Signature and Direct Signature are available as an upgrade for U.S. Domestic FedEx Ground shipments, and a surcharge will be applied if an upgrade is selected.

• Direct Signature is the only signature option available for FedEx 1Day, 2Day and 3Day Freight Services (U.S. Domestic FedEx Express Freight services).

2402 Signature Option Fee 11.2 Numeric Returned when field tag 2399 (Signature Option) has a value of 2, 3, or 4.

2403 List Signature Option Fee 11.2 Numeric Returned when field tag 2399 (Signature Option) has a value of 2, 3, or 4.

2405 MBG Ineligible 1 Alpha Y if a shipment does not qualify for MBG (Money Back Guarantee).

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 251

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

2900 Label Format 25 Alpha/ Numeric

Required by CLS. Existing values still apply: • PNG • ELTRON

2917 2D Barcode Data 300 Alpha/ Numeric

Required to indicate legacy ’96 Ground label. If GSE populates this field with the legacy bar code, then CLS will produce the legacy label. If the field is populated incorrectly, CLS will return an error to GSE.

2939 Return Reason Description 60 Alpha/ Numeric

Optional. Return Reason Description. Applicable only if RMA Number is provided. Will be ignored if RMA Number not provided.

2973 Doc Tab Type Indicator 1 Alpha/ Numeric

Valid values: 0 or not present – Ground Default Doc Tab. 1 – Zone 001 Doc Tab Format 2 – Barcoded Doc Tab (Code 128) Defaults to 0 (zero)

For the Zone 001 and the Ground Doc Tab Printing: • Header plus data combined can be up to 23 maximum

length. If no header, data can be 23. If no data, header can be 23.

• The header will be truncated (down to a minimum of 4 characters not including colon and space) as needed to accommodate printing the maximum characters of the associated data field.

2975 Mask Account Number Flag 1 Alpha/ Numeric

Optional. Valid values:

N – print the Account Number on label Y – do not print the Account Number on label (default)

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 252

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

3000 COD Collection Type 2 Numeric Valid values: 1 = Any payment type 2 = Guaranteed funds 3 = Currency

3001 FedEx Purchase Order 30 Alpha

3002 FedEx Invoice 30 Alpha

3003 FedEx Customer Reference 30 Alpha

3013 Multiweight Customer Total Charge 18.2 Numeric Explicit. Format: 999999999999999999.99.21 including decimal place. Includes 2 explicit decimal places. Shipper’s Freight charge plus Multiweight Variable Handling Charge Amount.

3014 Report Indicator 1 Alpha Valid values: 1 = Ground Manifest report 2 = Ground HazMat report 3 = Ground COD report 4 = MTW (pending)

3015 Hazardous Materials Flag 1 Alpha Y if shipment contains hazardous materials. Not allowed if Return Shipment Indicator = 1, 2, 3, or 4.

3018 Nonstandard Container Flag 1 Alpha Y if nonstandard container.

3020 FedEx Home Delivery Type 1 Alpha Valid values: 1 = Date Certain 2 = Evening 3 = Appointment

3021 FedEx Home Delivery Instructions 74 Alpha Specific Instructions for the delivery of package.

3023 FedEx Home Delivery Date 8 Numeric Date format: CCYYMMDD

3024 FedEx Home Delivery Phone Number 15 Alpha The maximum length is 10 for US and CA, 15 for all other countries.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 253

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

3025 Carrier Code 4 Alpha Valid carriers codes/names: FDXG – FedEx Ground FDXE – FedEx Express

3035 ShipAlert Fax Number 15 Alpha

3043 Multiweight Variable Handling 9 Numeric Explicit. Format: 9999999.99 explicit decimal. 9 total length. Handling charge returned to the customer calculated with multiweight freight.

3045 COD Return Reference Indicator 1 Alpha Indicator for what Ground COD Reference should print on the label.

0 or not present = GSE defaults to Tracking Number 1 = Reference 2 = PO# 3 = Invoice#

3048 Multiweight Report Content Buffer Base 64 encoded binary

Alpha/ Numeric

This buffer will contain the Multiweight report for FedEx Ground Shipments. Data/Manifest format: ASCII

3053 Multiweight Net Charge 11.2 Numeric Format: Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Ground only.

3054 Shipment Net Charge 11.2 Numeric Format: Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Ground only.

3058 Time in Transit 1 Alpha/ Numeric

The number of days a FedEx Ground or FedEx Home Delivery package will spend in transit from a given origin ZIP to a given Destination ZIP. Valid values:

1 = one day 2 = two days 3 = three days, etc.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 254

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

3066 Hazardous Materials – DOT Shipping Name of Material

50 Alpha/ Numeric

Required for OP-950. Optional if Hazardous Materials Flag is Y. (Can have blank or incorrect value.)

3067 D.O.T. Hazard class. OR Division Number

25 Alpha/ Numeric

Required for OP-950. Optional if Hazardous Materials Flag is Y. (Can have blank or incorrect value.)

3068 Hazardous Materials – DOT ID Number

11 Alpha/ Numeric

Optional if Hazardous Materials Flag is Y. (Can have blank or incorrect value.)

3069 Hazardous Materials – Packing Group 3 Alpha Optional if Hazardous Materials Flag is Y. (Can have blank or incorrect value.) Valid values: • i • ii • iii

3072 Hazardous Materials Type DOT Labels

50 Alpha/ Numeric

Optional. Type DOT Label(s) Required, Label(s) Required, Ltd., Qty., or Exemption Number. (Can have blank or incorrect value.)

3075 Hazardous Materials – Emergency Contact Phone Number

15 Numeric Required if Hazardous Materials Flag is Y. (Can have blank or incorrect value.)

3085 Hazardous Materials – DOT Shipping Name of Material

50 Alpha/ Numeric

Required for OP-950. Optional if Hazardous Materials Flag is Y. (Can have blank or incorrect value.)

3086 Hazardous Materials – DOT Shipping Name of Material

50 Alpha/ Numeric

Required for OP-950. Optional if Hazardous Materials Flag is Y. (Can have blank or incorrect value.)

3087 Hazardous Materials – Emergency Contact Name

50 Numeric Optional if Hazardous Materials Flag is Y. (Can have blank or incorrect value.)

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 255

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

3088 Hazardous Materials Quantity 6.2 Numeric Optional if Hazardous Materials Flag is Y. (Can have blank or incorrect value.)

3089 Hazardous Materials Unit of Measure 4 Alpha Required for OP-950. Optional if Hazardous Materials Flag is Y. Valid values: • oz • gal • lb • L • g • qt • kg • pt

3090 Last Ground Drop-off Time Mon-Fri 35 Alpha/ Numeric

Free form text field. Ex. “M-F 5:00 PM” or “N/A”

3091 Last Ground Drop-off Time Sat 35 Alpha/ Numeric

Free form text field. Ex. “Sat 3:00 PM” “N/A” “No Sat pickup”

3092 Ground Service Flag 1 Alpha/ Numeric

Valid values: • N • Y Y = Ground Available

3095 Appointment Delivery Surcharge 11.2 Numeric Format: Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Ground only.

3096 List Appointment Delivery Surcharge 11.2 Numeric Format: Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Ground only.

3101 Home Delivery Date Certain Surcharge

11.2 Numeric Format: Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Ground only.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 256

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

3102 List Home Delivery Date Certain Surcharge

11.2 Numeric Format: Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Ground only.

3103 Home Delivery Evening Delivery Surcharge

11.2 Numeric Format: Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Ground only.

3104 List Home Delivery Evening Delivery Surcharge

11.2 Numeric Format: Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Ground only.

3107 Additional Handling Charge (AHS) / Non Standard Container Surcharge

11.2 Numeric Format: Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Ground only.

3108 *List Additional Handling Charge (AHS) / Non Standard Container Surcharge

11.2 Numeric Format: Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Ground only.

3109 Hazardous Materials Surcharge 11.2 Numeric Format: Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Ground only.

3110 List Hazardous Materials Surcharge 11.2 Numeric Format: Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Ground only.

3111 Residential Surcharge 11.2 Numeric Format: Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Ground only.

3112 List Residential Surcharge 11.2 Numeric Format: Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Ground only.

3115 List Shipment Net Charge 11.2 Numeric Format: Two explicit decimal positions (i.e. 5.00). Applicable to FedEx Ground only.

3124 Oversize Classification 1 Alpha Classifications of Oversize shipment: 1 = Oversize 1 2 = Oversize 2 3 = Oversize 3

4003 Subscriber Contact Name 35 Alpha Name of the person subscribing for services.

Appendix A: Field Descriptions by Field Tag

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 257

Field Tag Field Name

Maximum Field

Length

Alpha-numeric / Numeric

Field Description

4004 Subscriber Password Reminder

4007 Subscriber Company Name 35 Alpha Name of the company subscribing for the services.

4008 Subscriber Address Line 1 35 Alpha Primary address line of the person subscribing for services.

4009 Subscriber Address Line 2 35 Alpha Secondary address line of the person subscribing for services.

4011 Subscriber City Name 35 Alpha City name of the person receiving the shipment.

4012 Subscriber State Code 14 Alpha State code of the subscriber's location. The maximum field length for US and CA is 2, 14 for all other countries.

4013 Subscriber Postal Code 16 Alpha Postal code of the subscriber's location. Must be numeric for U.S. Special characters allowed.

4014 Subscriber Country Code 2 Alpha Country code of the subscriber's location.

4015 Subscriber Phone Number 15 Alpha Phone number of the person subscribing for services. The maximum length is 10 for US and CA, 15 for all other countries.

4017 Subscriber Pager Number 15 Alpha Pager number of the person subscribing for services. The maximum length is 10 for US and CA, 15 for all other countries.

4018 Subscriber Email Address 120 Alpha E-mail address of the person subscribing for services.

4021 Subscription Service Name 21 Alpha Valid values: • FedEx Express Shipping • FedEx Ground Shipping

4022 Subscriber Fax Number 15 Alpha Fax number of the person subscribing for services. The maximum length is 10 for US and CA, 15 for all other countries.

Appendix B: Country Codes

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 259

Appendix B: Country Codes

Country Code Ship to: Country Code Ship

to: Country Code Ship to:

Afghanistan AF Y Bermuda BM Y China CN Y Albania AL Y Bhutan BT Y Christmas Island CX N Algeria DZ N Bolivia BO Y Cocos (Keeling) Islands CC N American Samoa AS Y Bonaire AN Y Colombia CO Y Andorra AD Y Bosnia-Herzegovina BA Y Comoros KM N Angola AO Y Botswana BW Y Congo CG Y Anguilla AI Y Bouvet Island BV N Congo Dem. Rep. Of CD Y Antarctica AQ N Brazil BR Y Cook Islands CK Y Antigua AG Y British Indian Ocean Territory IO N Costa Rica CR Y Argentina AR Y British Virgin Islands VG Y Croatia HR Y Armenia AM Y Brunei BN Y Cuba CU N Aruba AW Y Bulgaria BG Y Curacao AN Y Australia AU Y Burkina Faso BF Y Cyprus CY Y Austria AT Y Burundi BI Y Czech Republic CZ Y Azerbaijan AZ Y Cambodia KH Y Denmark DK Y Bahamas BS Y Cameroon CM Y Djibouti DJ Y Bahrain BH Y Canada CA Y Dominica DM Y Bangladesh BD Y Canary Islands ES Y Dominican Republic DO Y Barbados BB Y Cape Verde CV Y East Timor TL Y Barbuda AG Y Cayman Islands KY Y Ecuador EC Y Belarus BY Y Central African Republic CF N Egypt EG Y Belgium BE Y Chad TD Y El Salvador SV Y Belize BZ Y Channel Islands GB Y England GB Y Benin BJ Y Chile CL Y Equatorial Guinea GQ Y

Appendix B: Country Codes

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 260

Country Code Ship to: Country Code Ship

to: Country Code Ship to:

Eritrea ER Y Guyana GY Y Liberia LR Y Estonia EE Y Haiti HT Y Libya LY N Ethiopia ET Y Heard & McDonald Islands HM N Liechtenstein LI Y Faeroe Islands FO Y Holland NL Y Lithuania LT Y Falkland Islands FK N Honduras HN Y Luxembourg LU Y Fiji FJ Y Hong Kong HK Y Macau MO Y Finland FI Y Hungary HU Y Macedonia MK Y France FR Y Iceland IS Y Madagascar MG Y French Guiana GF Y India IN Y Malawi MW Y French Polynesia PF Y Indonesia ID Y Malaysia MY Y French Southern Territories TF N Iran IR N Maldives MV Y Gabon GA Y Iraq IQ Y Mali ML Y Gambia GM Y Ireland IE Y Malta MT Y Georgia GE Y Israel IL Y Marshall Islands MH Y Germany DE Y Italy IT Y Martinique MQ Y Ghana GH Y Ivory Coast CI Y Mauritania MR Y Gibraltar GI Y Jamaica JM Y Mauritius MU Y Grand Cayman KY Y Japan JP Y Mayotte YT N Great Britain GB Y Jordan JO Y Mexico MX Y Great Thatch Island VG Y Jost Van Dyke Islands VG Y Micronesia FM Y Great Tobago Islands VG Y Kazakhstan KZ Y Moldova MD Y Greece GR Y Kenya KE Y Monaco MC Y Greenland GL Y Kiribati KI N Mongolia MN Y Grenada GD Y Kuwait KW Y Montserrat MS Y Guadeloupe GP Y Kyrgyzstan KG Y Morocco MA Y Guam GU Y Laos LA Y Mozambique MZ Y Guatemala GT Y Latvia LV Y Myanmar / Burma MM N Guinea GN Y Lebanon LB Y Nambia NA Y Guinea Bissau GW N Lesotho LS Y Nauru NR N

Appendix B: Country Codes

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 261

Country Code Ship to: Country Code Ship

to: Country Code Ship to:

Nepal NP Y Qatar QA Y St. Christopher KN Y Netherlands NL Y Reunion RE Y St. Croix Island VI Y Netherlands Antilles AN Y Romania RO Y St. Eustatius AN Y New Caledonia NC Y Rota MP Y St. Helena SH N New Zealand NZ Y Russia RU Y St. John VI Y Nicaragua NI Y Rwanda RW Y St. Kitts and Nevis KN Y Niger NE Y Saba AN Y St. Lucia LC Y Nigeria NG Y Saipan MP Y St. Maarten AN Y Niue NU N Samoa WS Y St. Pierre PM N Norfolk Island NF N San Marino IT Y St. Thomas VI Y Norman Island VG Y Sao Tome & Principe ST N St. Vincent VC Y North Korea KP N Saudi Arabia SA Y Sudan SD N Northern Ireland GB Y Scotland GB Y Suriname SR Y Northern Mariana Islands MP Y Senegal SN Y Svalbard & Jan Mayen Is SJ N Norway NO Y Serbia & Montenegro CS Y Swaziland SZ Y Oman OM Y Seychelles SC Y Sweden SE Y Pakistan PK Y Sierra Leone SL N Switzerland CH N Palau PW Y Singapore SG Y Syria SY N Palestine PS Y Slovak Republic SK Y Tahiti PF Y Panama PA Y Slovenia SI Y Taiwan TW Y Papua New Guinea PG Y Solomon Islands SB N Tajikistan TJ N Paraguay PY Y Somalia SO N Tanzania TZ Y Peru PE Y South Africa ZA Y Thailand TH Y Philippines

PH Y South Georgia & South Sandwich Islands GS N

Tinian MP Y

Pitcairn PN N South Korea KR Y Togo TG Y Poland PL Y Spain ES Y Tokelau TK N Portugal PT Y Sri Lanka LK Y Tonga TO Y Puerto Rico PR Y St. Barthelemy GP Y Tortola Island VG Y

Appendix B: Country Codes

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 262

Country Code Ship to: Country Code Ship

to: Country Code Ship to:

Trinidad & Tobago TT Y Tunisia TN Y Turkey TR Y Turkmenistan TM Y Turks & Caicos Islands TC Y Tuvalu TV N U.S. Minor Outlying Islands UM N U.S. Virgin Islands VI Y Uganda UG Y Ukraine UA Y Union Island VC Y United Arab Emirates AE Y United Kingdom GB Y United States US Y Uruguay UY Y Uzbekistan UZ Y Vanuatu VU Y Vatican City IT Y Venezuela VE Y Vietnam VN Y Wales GB Y Wallis & Futuna Islands WF Y Western Sahara EH N Yemen YE Y Zambia ZM Y Zimbabwe ZW Y

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 263

Appendix C: Vague Commodity Descriptions

The following table is a list of commodity descriptions considered vague by U.S. Customs:

Vague Commodity Vague Commodity Description

"A/C Parts" "A/C Parts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Break Caliper for Aircraft." Clearance delays may result if the contents are not completely and accurately described.

"AC Parts" "AC Parts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Break Caliper for Aircraft." Clearance delays may result if the contents are not completely and accurately described.

"Accessories" "Accessories" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Advertising Material" "Advertising Material" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Plastic Advertising Signs." Clearance delays may result if the contents are not completely and accurately described.

"Aircraft Parts" "Aircraft Parts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Brake Caliper for Aircraft." Clearance delays may result if the contents are not completely and accurately described.

"Aircraft Spare Parts" "Aircraft Spare Parts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Brake Caliper for Aircraft." Clearance delays may result if the contents are not completely and accurately described.

"Aircraft spares" "Aircraft Spares" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Brake Caliper for Aircraft." Clearance delays may result if the contents are not completely and accurately described.

"Antibodies" "Antibodies" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Human Antibodies." Clearance delays may result if the contents are not completely and accurately described.

"Antibody" "Antibody" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Human Antibody." Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 264

Vague Commodity Vague Commodity Description

"Apparel" "Apparel" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Men's T-shirt." Clearance delays may result if the contents are not completely and accurately described.

"Appliance" "Appliance" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Industrial Dishwasher." Clearance delays may result if the contents are not completely and accurately described.

"Appliances" "Appliances" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Industrial Dishwasher." Clearance delays may result if the contents are not completely and accurately described.

"Art" "Art" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Water Color Painting." Clearance delays may result if the contents are not completely and accurately described.

"As Per Attached INV" "As Per Attached INV" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Assorted Merchandise" "Assorted Merchandise" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Auto Part" "Auto Parts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Used Auto Parts: Remanufactured Alternator." Clearance delays may result if the contents are not completely and accurately described.

"Auto Parts" "Auto Parts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Used Auto Parts: Remanufactured Alternator." Clearance delays may result if the contents are not completely and accurately described.

"Automotive Parts" "Automotive Parts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Used Auto Parts: Remanufactured Alternator." Clearance delays may result if the contents are not completely and accurately described.

"Autoparts" "Autoparts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Used Auto Parts: Remanufactured Alternator." Clearance delays may result if the contents are not completely and accurately described.

"Bag" "Bag" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 265

Vague Commodity Vague Commodity Description

"Battery" "Battery" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Car Battery." Clearance delays may result if the contents are not completely and accurately described.

"Bearing" "Bearing" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Ball Bearing." Clearance delays may result if the contents are not completely and accurately described.

"Belts" "Belts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Leather Belts." Clearance delays may result if the contents are not completely and accurately described.

"Box" "Box" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Brake Parts" "Brake Parts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Brake Caliper." Clearance delays may result if the contents are not completely and accurately described.

"Brake" "Brake" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Automobile Brake." Clearance delays may result if the contents are not completely and accurately described.

"Business Correspondence"

"Business Correspondence" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Legal Contract." Clearance delays may result if the contents are not completely and accurately described.

"Cable" "Cable" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Copper Cable." Clearance delays may result if the contents are not completely and accurately described.

"Cap" "Cap" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Baseball Caps." Clearance delays may result if the contents are not completely and accurately described.

"Caps" "Caps" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Baseball Caps." Clearance delays may result if the contents are not completely and accurately described.

"Carton" "Carton" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"CD" "CD" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Jazz Music CD." Clearance delays may result if the contents are not completely and accurately described.

"CDs" "CDs" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Jazz Music CDs." Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 266

Vague Commodity Vague Commodity Description

"Cell Line" "Cell Line" is an incomplete description and not accepted by Customs. Please specify the name of the material, reason for import and its origin: plant, animal, human. Clearance delays may result if the contents are not completely and accurately described.

"Cells" "Cells" is an incomplete description and not accepted by Customs. Please specify the name of the material, reason for import and its origin: plant, animal, human. Clearance delays may result if the contents are not completely and accurately described.

"Chemical" "Chemical" is an incomplete description and not accepted by Customs. Please provide the actual chemical name and UN HAZMAT #. Clearance delays may result if the contents are not completely and accurately described.

"Chemicals" "Chemicals" is an incomplete description and not accepted by Customs. Please provide the actual chemical name and UN HAZMAT #. Clearance delays may result if the contents are not completely and accurately described.

"Chip" "Chip" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Computer Integrated Circuit." Clearance delays may result if the contents are not completely and accurately described.

"Christmas Gifts" "Christmas Gift" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"CI Attached" "CI Attached" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Civil Aircraft Parts" "Civil Aircraft Parts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Brake Caliper for Aircraft." Clearance delays may result if the contents are not completely and accurately described.

"Civil Aircraft Spares" "Civil Aircraft Spares" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Brake Caliper for Aircraft." Clearance delays may result if the contents are not completely and accurately described.

"Clothes / Textiles" "Clothes / Textiles" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Men's T-shirts." Clearance delays may result if the contents are not completely and accurately described.

"Clothes" "Clothes" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Men's T-shirts." Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 267

Vague Commodity Vague Commodity Description

"Clothing and Accessories"

"Clothing and Accessories" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Men's T-shirts." Clearance delays may result if the contents are not completely and accurately described.

"Clothing" "Clothing" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Men's T-shirts." Clearance delays may result if the contents are not completely and accurately described.

"Comat" "Comat" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Office Correspondence." Clearance delays may result if the contents are not completely and accurately described.

"Commercial Invoice" "Commercial Invoice" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Components" "Components" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Computer Parts" "Computer Parts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "PC Cooling Motor for Motherboard." Clearance delays may result if the contents are not completely and accurately described.

"Computer Peripherals" "Computer Peripherals" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Computer CD Players." Clearance delays may result if the contents are not completely and accurately described.

"Connector" "Connector" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Cosmetic Products" "Cosmetic Products" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Women's Fragrance." Clearance delays may result if the contents are not completely and accurately described.

"Cosmetics" "Cosmetics" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Women's Fragrance." Clearance delays may result if the contents are not completely and accurately described.

"Culture" "Culture" is an incomplete description and not accepted by Customs. Please specify the name of the material, reason for import and its origin: plant, animal, human. Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 268

Vague Commodity Vague Commodity Description

"Dangerous Good" "Dangerous Good" is an incomplete description and not accepted by Customs. Please provide the actual chemical or product name and the UN HAZMAT #. Clearance delays may result if the contents are not completely and accurately described.

"Dangerous Goods" "Dangerous Goods" is an incomplete description and not accepted by Customs. Please provide the actual chemical or product name and the UN HAZMAT #. Clearance delays may result if the contents are not completely and accurately described.

"Data Processing Part" "Data Processing Part" is an incomplete description and not accepted by Customs. An example of an acceptable description is "PC Cooling Motor for Motherboard." Clearance delays may result if the contents are not completely and accurately described.

"Data Processing Parts" "Data Processing Parts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "PC Cooling Motor for Motherboard." Clearance delays may result if the contents are not completely and accurately described.

"Defective Goods" "Defective Goods" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"DESC N" "DESC N" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"DESCRI" "DESCRI" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"DG" "DG" is an incomplete description and not accepted by Customs. Please provide the actual chemical or product name and the UN HAZMAT #. Clearance delays may result if the contents are not completely and accurately described.

"DGs" "DGs" is an incomplete description and not accepted by Customs. Please provide the actual chemical or product name and the UN HAZMAT #. Clearance delays may result if the contents are not completely and accurately described.

"Disk" "Disk" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Business Correspondence on a Floppy Disk." Clearance delays may result if the contents are not completely and accurately described.

"Disks" "Disks" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Business Correspondence on Floppy Disks." Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 269

Vague Commodity Vague Commodity Description

"Display" "Display" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Liquid Crystal Display (LCD) - Desktop Projector ." Clearance delays may result if the contents are not completely and accurately described.

"DNA" "DNA" is an incomplete description and not accepted by Customs. Please specify the name of the material, reason for import and its origin: plant, animal, human. Clearance delays may result if the contents are not completely and accurately described.

"Doc" "Doc" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Office Correspondence." Clearance delays may result if the contents are not completely and accurately described.

"Document" "Document" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Birth Certificate." Clearance delays may result if the contents are not completely and accurately described.

"Documentation" "Documentation" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Office Correspondence." Clearance delays may result if the contents are not completely and accurately described.

"Documents" "Documents" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Birth Certificate." Clearance delays may result if the contents are not completely and accurately described.

"Drug" "Drug" is an incomplete description and not accepted by Customs. Please specify the name of the medication or product being shipped and its intended use. Clearance delays may result if the contents are not completely and accurately described.

"Drugs" "Drugs" is an incomplete description and not accepted by Customs. Please specify the name of the medication or product being shipped and its intended use. Clearance delays may result if the contents are not completely and accurately described.

"Dry Ice" "Dry Ice" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Pork Ribs in Dry Ice." Clearance delays may result if the contents are not completely and accurately described.

"DVD" "DVD" is an incomplete description and not accepted by Customs. An example of an acceptable description is "DVD Player." Clearance delays may result if the contents are not completely and accurately described.

"DVDs" "DVDs" is an incomplete description and not accepted by Customs. An example of an acceptable description is "DVD Movies." Clearance delays may result if the contents are not completely and accurately described.

"Electrical Parts" "Electrical Parts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Transistor." Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 270

Vague Commodity Vague Commodity Description

"Electronic Component" "Electronic Component" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Transistor." Clearance delays may result if the contents are not completely and accurately described.

"Electronic Components" "Electronic Components" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Capacitor." Clearance delays may result if the contents are not completely and accurately described.

"Electronic Equipment" "Electronic Equipment" is an incomplete description and not accepted by Customs. An example of an acceptable description is "DVD Player." Clearance delays may result if the contents are not completely and accurately described.

"Electronic Good" "Electronic Good" is an incomplete description and not accepted by Customs. An example of an acceptable description is "DVD Players." Clearance delays may result if the contents are not completely and accurately described.

"Electronic Goods" "Electronic Goods" is an incomplete description and not accepted by Customs. An example of an acceptable description is "DVD Players." Clearance delays may result if the contents are not completely and accurately described.

"Electronic Part" "Electronic Part" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Transistor." Clearance delays may result if the contents are not completely and accurately described.

"Electronic Parts" "Electronic Parts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Transistors." Clearance delays may result if the contents are not completely and accurately described.

"Electronic" "Electronic" is an incomplete description and not accepted by Customs. An example of an acceptable description is "DVD Player." Clearance delays may result if the contents are not completely and accurately described.

"Electronics" "Electronics" is an incomplete description and not accepted by Customs. An example of an acceptable description is "DVD Player." Clearance delays may result if the contents are not completely and accurately described.

"Equipment" "Equipment" is an incomplete description and not accepted by Customs. Specific Description of the Type of equipment and its intended use is required. Clearance delays may result if the contents are not completely and accurately described.

"Fabric Samples" "Fabric Samples" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Women's Fabric for Clothing - 100% Cotton." Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 271

Vague Commodity Vague Commodity Description

"Fabric" "Fabric" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Women's Fabric for Clothing - 100% Cotton." Clearance delays may result if the contents are not completely and accurately described.

"Fabrics" "Fabrics" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Women's Fabric for Clothing - 100% Cotton." Clearance delays may result if the contents are not completely and accurately described.

"FAC " "FAC " is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"FAK " "FAK " is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Flooring" "Flooring" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Ceramic Tiles." Clearance delays may result if the contents are not completely and accurately described.

"Food Items" "Food Items" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Canned Pasta." Clearance delays may result if the contents are not completely and accurately described.

"Food" "Food" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Homemade Cookies." Clearance delays may result if the contents are not completely and accurately described.

"Foodstuff" "Foodstuff" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Chocolate Bars." Clearance delays may result if the contents are not completely and accurately described.

"Foodstuffs" "Foodstuffs" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Chocolate Bars." Clearance delays may result if the contents are not completely and accurately described.

"Freight Of All Kinds" "Freight Of All Kinds" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"General Cargo" "General Cargo" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Gift" "Gift" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Book sent as a Christmas Gift." Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 272

Vague Commodity Vague Commodity Description

"Gifts" "Gifts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Books sent as a Christmas Gift." Clearance delays may result if the contents are not completely and accurately described.

"Goods" "Goods" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Personal Effects." Clearance delays may result if the contents are not completely and accurately described.

"Hardware" "Hardware" is an incomplete description and not accepted by Customs. An example of an acceptable description is "CD Player." Clearance delays may result if the contents are not completely and accurately described.

"Haz Mat" "Haz Mat" is an incomplete description and not accepted by Customs. Please provide the actual chemical or product name and the UN HAZMAT #. Clearance delays may result if the contents are not completely and accurately described.

"Haz Material" "Haz Material" is an incomplete description and not accepted by Customs. Please provide the actual chemical or product name and the UN HAZMAT #. Clearance delays may result if the contents are not completely and accurately described.

"Haz Materials" "Haz Materials" is an incomplete description and not accepted by Customs. Please provide the actual chemical or product name and the UN HAZMAT #. Clearance delays may result if the contents are not completely and accurately described.

"Hazardous Chemical" "Hazardous Chemical" Materials is an incomplete description and not accepted by Customs. Please provide the actual chemical or product name and the UN HAZMAT #. Clearance delays may result if the contents are not completely and accurately described.

"Hazardous Chemicals" "Hazardous Chemicals" Materials is an incomplete description and not accepted by Customs. Please provide the actual chemical or product name and the UN HAZMAT #. Clearance delays may result if the contents are not completely and accurately described.

"Hazardous Good" "Hazardous Good" is an incomplete description and not accepted by Customs. Please provide the actual chemical or product name and the UN HAZMAT #. Clearance delays may result if the contents are not completely and accurately described.

"Hazardous Goods" "Hazardous Goods" is an incomplete description and not accepted by Customs. Please provide the actual chemical or product name and the UN HAZMAT #. Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 273

Vague Commodity Vague Commodity Description

"Hazardous Material" "Hazardous Material" is an incomplete description and not accepted by Customs. Please provide the actual chemical or product name and the UN HAZMAT #. Clearance delays may result if the contents are not completely and accurately described.

"Hazardous Materials" "Hazardous Materials" is an incomplete description and not accepted by Customs. Please provide the actual chemical or product name and the UN HAZMAT #. Clearance delays may result if the contents are not completely and accurately described.

"HazMat" "HazMat" is an incomplete description and not accepted by Customs. Please provide the actual chemical or product name and the UN HAZMAT #. Clearance delays may result if the contents are not completely and accurately described.

"Household Goods" "Household Goods" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"HS #" "HS #" is an incomplete description and not accepted by Customs. Please provide the full digit Harmonized Code if available and the description of the product. Clearance delays may result if the contents are not completely and accurately described.

"HS NON" "HS NON" is an incomplete description and not accepted by Customs. Please provide the full digit Harmonized Code if available and the description of the product. Clearance delays may result if the contents are not completely and accurately described.

"HS#" "HS#" is an incomplete description and not accepted by Customs. Please provide the full digit Harmonized Code if available and the description of the product. Clearance delays may result if the contents are not completely and accurately described.

"I C" "I C" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Integrated Circuits - EEPROM." Clearance delays may result if the contents are not completely and accurately described.

"IC" "IC" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Integrated Circuits - EEPROM." Clearance delays may result if the contents are not completely and accurately described.

"ILLEDG" "ILLEDG" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Illegible" "Illegible" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 274

Vague Commodity Vague Commodity Description

"Implants" "Implants" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Dental Implants." Clearance delays may result if the contents are not completely and accurately described.

"Industrial Goods" "Industrial Goods" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Integrated Circuit" "Integrated Circuit" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Integrated Circuit - EEPROM." Clearance delays may result if the contents are not completely and accurately described.

"Integrated Circuits" "Integrated Circuits" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Integrated Circuits - EEPROM." Clearance delays may result if the contents are not completely and accurately described.

"Iron" "Iron" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Steam Iron." Clearance delays may result if the contents are not completely and accurately described.

"Items" "Items" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Jeans" "Jeans" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Ladies Denim Jeans." Clearance delays may result if the contents are not completely and accurately described.

"Jewelry" "Jewelry" is an incomplete description and not accepted by Customs. An example of an acceptable description is "18 Carat Gold Necklace." Clearance delays may result if the contents are not completely and accurately described.

"Laboratory Reagents" "Laboratory Reagents" is an incomplete description and not accepted by Customs. Please provide the actual chemical or product name and the UN HAZMAT #. Clearance delays may result if the contents are not completely and accurately described.

"Ladies Apparel" "Ladies Apparel" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Women's leather shoes." Clearance delays may result if the contents are not completely and accurately described.

"Leather Article" "Leather Article" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Leather Purse." Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 275

Vague Commodity Vague Commodity Description

"Leather Articles" "Leather Articles" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Leather Purse." Clearance delays may result if the contents are not completely and accurately described.

"Leather" "Leather" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Leather Belts." Clearance delays may result if the contents are not completely and accurately described.

"Letter" "Letter" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Personal Correspondence." Clearance delays may result if the contents are not completely and accurately described.

"Liquid" "Liquid" is an incomplete description and not accepted by Customs. Please provide the actual chemical or product name and the UN HAZMAT #. Clearance delays may result if the contents are not completely and accurately described.

"Luggage" "Luggage" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Machine Part" "Machine Part" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Remanufactured Alternator for a Farm Tractor." Clearance delays may result if the contents are not completely and accurately described.

"Machine Parts" "Machine Parts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Remanufactured Alternator for a Farm Tractor." Clearance delays may result if the contents are not completely and accurately described.

"Machinery" "Machinery" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Wood Cutting Machine." Clearance delays may result if the contents are not completely and accurately described.

"Machines" "Machines" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Wood Cutting Machine." Clearance delays may result if the contents are not completely and accurately described.

"Medical Equipment" "Medical Equipment" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Defibrillator." Clearance delays may result if the contents are not completely and accurately described.

"Medical Parts" "Medical Parts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Electric Wire for Medical Equipment." Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 276

Vague Commodity Vague Commodity Description

"Medical Spare Parts" "Medical Spare Parts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Electric Wire for Medical Equipment." Clearance delays may result if the contents are not completely and accurately described.

"Medical Supplies" "Medical Supplies" is an incomplete description and not accepted by Customs. Please provide the specific name of the medication or product being shipped and its intended use. Clearance delays may result if the contents are not completely and accurately described.

"Medicaments" "Medicaments" is an incomplete description and not accepted by Customs. Please provide the specific name of the medication or product being shipped and its intended use. Clearance delays may result if the contents are not completely and accurately described.

"Medication" "Medication" is an incomplete description and not accepted by Customs. Please provide the specific name of the medication or product being shipped and its intended use. Clearance delays may result if the contents are not completely and accurately described.

"Medications" "Medications" is an incomplete description and not accepted by Customs. Please provide the specific name of the medication or product being shipped and its intended use. Clearance delays may result if the contents are not completely and accurately described.

"Medicine" "Medicine" is an incomplete description and not accepted by Customs. Please provide the specific name of the medication or product being shipped and its intended use. Clearance delays may result if the contents are not completely and accurately described.

"Medicines" "Medicines" is an incomplete description and not accepted by Customs. Please provide the specific name of the medication or product being shipped and its intended use. Clearance delays may result if the contents are not completely and accurately described.

"Meds" "Meds" is an incomplete description and not accepted by Customs. Please provide the specific name of the medication or product being shipped and its intended use. Clearance delays may result if the contents are not completely and accurately described.

"Men’s Apparel" "Men’s Apparel" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Men's Summer T-Shirt." Clearance delays may result if the contents are not completely and accurately described.

"Metal Work" "Metal Work" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Copper Pipe." Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 277

Vague Commodity Vague Commodity Description

"Miscellaneous Items" "Miscellaneous Items" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"NAFTA" "NAFTA" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"New Goods" "New Goods" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"No CI" "No CI" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"NO COM" "NO COM" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"NO DES" "NO DES" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"NON G" "NON G" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Non-Hazardous" "Non-Hazardous" is an incomplete description and not accepted by Customs. Please provide the proper name of the goods, if chemical, proper name and the UN #. Clearance delays may result if the contents are not completely and accurately described.

"NOT GI" "NOT GI" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Packaging Supplies" "Packaging Supplies" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Bubble Plastic Wrap." Clearance delays may result if the contents are not completely and accurately described.

"Pants" "Pants" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Boy's Cotton Twill Pants." Clearance delays may result if the contents are not completely and accurately described.

"Paper" "Paper" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Legal Contract." Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 278

Vague Commodity Vague Commodity Description

"Paperwork" "Paperwork" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Legal Contract." Clearance delays may result if the contents are not completely and accurately described.

"Part" "Part" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Brake Caliper for Aircraft." Clearance delays may result if the contents are not completely and accurately described.

"Parts Of" "Parts Of" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Brake Calipers for Aircraft." Clearance delays may result if the contents are not completely and accurately described.

"Parts" "Parts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Brake Calipers for Aircraft." Clearance delays may result if the contents are not completely and accurately described.

"PC Hardware" "PC Hardware" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Computer CD Player." Clearance delays may result if the contents are not completely and accurately described.

"PCB" "PCB" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Printed Circuit Board with Components for Television Set." Clearance delays may result if the contents are not completely and accurately described.

"PCBA" "PCBA" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Printed Circuit Board Assembly for Computer." Clearance delays may result if the contents are not completely and accurately described.

"Peripheral" "Peripheral" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Computer Printer." Clearance delays may result if the contents are not completely and accurately described.

"Personal Effects" "Personal Effects" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Personal Item" "Personal Item" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Personal Items" "Personal Items" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Pharmaceuticals" "Pharmaceuticals" is an incomplete description and not accepted by Customs. Please provide the specific name of the medication or product being shipped and its intended use. Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 279

Vague Commodity Vague Commodity Description

"PIB" "PIB" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"PIBs" "PIBs" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Pipe" "Pipe" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Steel Pipe." Clearance delays may result if the contents are not completely and accurately described.

"Pipes" "Pipes" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Steel Pipes." Clearance delays may result if the contents are not completely and accurately described.

"Plastic Good" "Plastic Good" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Plastic Knive." Clearance delays may result if the contents are not completely and accurately described.

"Plastic Goods" "Plastic Goods" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Plastic Knives." Clearance delays may result if the contents are not completely and accurately described.

"Plastic Parts" "Plastic Parts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Plastic Knives." Clearance delays may result if the contents are not completely and accurately described.

"Plastic" "Plastic" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Women's Plastic Shoes." Clearance delays may result if the contents are not completely and accurately described.

"Polyurethane" "Polyurethane" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Polyurethane Medical Gloves." Clearance delays may result if the contents are not completely and accurately described.

"Power Supply" "Power Supply" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Power Supply Module for ADP Machines." Clearance delays may result if the contents are not completely and accurately described.

"Precious Metal" "Precious Metal" is an incomplete description and not accepted by Customs. An example of an acceptable description is "18 Carat Gold Necklace." Clearance delays may result if the contents are not completely and accurately described.

"Printed Circuit Board" "Printed Circuit Board" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Printed Circuit Board with Components for Television Set." Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 280

Vague Commodity Vague Commodity Description

"Printed Material" "Printed Material" is an incomplete description and not accepted by Customs. An example of an acceptable description is "TV Owner's Manual." Clearance delays may result if the contents are not completely and accurately described.

"Printed Materials" "Printed Materials" is an incomplete description and not accepted by Customs. An example of an acceptable description is "TV Owner's Manuals." Clearance delays may result if the contents are not completely and accurately described.

"Printed Matter" "Printed Matter" is an incomplete description and not accepted by Customs. An example of an acceptable description is "TV Owner's Manual" Clearance delays may result if the contents are not completely and accurately described.

"Printed Matters" "Printed Matters" is an incomplete description and not accepted by Customs. An example of an acceptable description is "TV Owner's Manuals" Clearance delays may result if the contents are not completely and accurately described.

"Promo Item" "Promo Item" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Promotional Inflatable Balloons not for resale." Clearance delays may result if the contents are not completely and accurately described.

"Promo Items" "Promo Items" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Promotional Inflatable Balloons not for resale." Clearance delays may result if the contents are not completely and accurately described.

"Promo Material" "Promo Material" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Promotional Inflatable Balloons not for resale." Clearance delays may result if the contents are not completely and accurately described.

"Promo Materials" "Promo Materials" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Promotional Inflatable Balloons not for resale." Clearance delays may result if the contents are not completely and accurately described.

"Promotional Item" "Promotional Item" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Promotional Inflatable Balloons not for resale." Clearance delays may result if the contents are not completely and accurately described.

"Promotional Items" "Promotional Items" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Promotional Inflatable Balloons not for resale." Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 281

Vague Commodity Vague Commodity Description

"Promotional Material" "Promotional Material" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Promotional Inflatable Balloons not for resale." Clearance delays may result if the contents are not completely and accurately described.

"Promotional Materials" "Promotional Materials" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Promotional Inflatable Balloons not for resale." Clearance delays may result if the contents are not completely and accurately described.

"Promotional" "Promotional" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Promotional Inflatable Balloons not for resale." Clearance delays may result if the contents are not completely and accurately described.

"Receivers" "Receivers" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Stereo Receiver." Clearance delays may result if the contents are not completely and accurately described.

"Records" "Records" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Office Correspondence." Clearance delays may result if the contents are not completely and accurately described.

"Report" "Report" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Business Correspondence - Annual Report." Clearance delays may result if the contents are not completely and accurately described.

"Rod" "Rod" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Fishing Rods." Clearance delays may result if the contents are not completely and accurately described.

"Rods" "Rods" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Aluminum Rods." Clearance delays may result if the contents are not completely and accurately described.

"Rubber Articles" "Rubber Articles" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Rubber Hoses." Clearance delays may result if the contents are not completely and accurately described.

"Rubber" "Rubber" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Rubber Tires." Clearance delays may result if the contents are not completely and accurately described.

"Said To Contain" "Said To Contain" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Sample" "Sample" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Plastic Bags - SAMPLE." Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 282

Vague Commodity Vague Commodity Description

"Samples" "Samples" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Plastic Bags - SAMPLE." Clearance delays may result if the contents are not completely and accurately described.

"Scrap" "Scrap" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Steel Scrap Billets." Clearance delays may result if the contents are not completely and accurately described.

"See Attached" "See Attached" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"SEE CO" "SEE CO" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"SEE IN" "SEE IN" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"See Invoice" "See Invoice" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Shirt" "Shirt" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Men's 100% Cotton Long Sleeve Shirt." Clearance delays may result if the contents are not completely and accurately described.

"Software" "Software" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Software Game on CD-ROM - "Halo 2"." Clearance delays may result if the contents are not completely and accurately described.

"Spare Parts for Machine" "Spare Parts for Machine" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Alternator - New." Clearance delays may result if the contents are not completely and accurately described.

"Spare Parts" "Spare Parts" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Alternator - Used." Clearance delays may result if the contents are not completely and accurately described.

"Spares" "Spares" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Alternator - New." Clearance delays may result if the contents are not completely and accurately described.

"Sportswear" "Sportswear" is an incomplete description and not accepted by Customs. An example of an acceptable description is "100% Cotton Men's Running Shorts." Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 283

Vague Commodity Vague Commodity Description

"STC " "STC " is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Steel" "Steel" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Stainless Steel Pots." Clearance delays may result if the contents are not completely and accurately described.

"Surgical Instruments" "Surgical Equipment" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Scalpels." Clearance delays may result if the contents are not completely and accurately described.

"Swatches" "Swatches" is an incomplete description and not accepted by Customs. An example of an acceptable description is "100% Cotton Fabric Sample Swatches." Clearance delays may result if the contents are not completely and accurately described.

"Tape" "Tape" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Jazz Music Video Tape." Clearance delays may result if the contents are not completely and accurately described.

"Tapes" "Tapes" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Jazz Music Video Tapes." Clearance delays may result if the contents are not completely and accurately described.

"Textile Samples" "Textile Samples" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Men's Shirt 100% Cotton - SAMPLE." Clearance delays may result if the contents are not completely and accurately described.

"Textile" "Textile" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Women's Dress - 100% Cotton - SAMPLE." Clearance delays may result if the contents are not completely and accurately described.

"Textiles Samples" "Textiles Samples" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Men's Shirt 100% Cotton - SAMPLE." Clearance delays may result if the contents are not completely and accurately described.

"Textiles" "Textiles" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Men's Shirt 100% Cotton - SAMPLE." Clearance delays may result if the contents are not completely and accurately described.

"Tile" "Tile" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Ceramic Tiles." Clearance delays may result if the contents are not completely and accurately described.

"Tiles" "Tiles" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Ceramic Tiles." Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 284

Vague Commodity Vague Commodity Description

"Tools" "Tools" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Power Drill." Clearance delays may result if the contents are not completely and accurately described.

"Toy" "Toy" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Plastic Doll House." Clearance delays may result if the contents are not completely and accurately described.

"Training Material" "Training Material" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Training Material for Basketball." Clearance delays may result if the contents are not completely and accurately described.

"Training Materials" "Training Materials" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Training Materials for Basketball." Clearance delays may result if the contents are not completely and accurately described.

"Tubes" "Tubes" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Glass Tubes." Clearance delays may result if the contents are not completely and accurately described.

"Unlist" "Unlist" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Used Goods" "Used Goods" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Various Goods" "Various Goods" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Video Tape" "Video Tape" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Jazz Music Video Tape." Clearance delays may result if the contents are not completely and accurately described.

"Video Tapes" "Video Tapes" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Jazz Music Video Tapes." Clearance delays may result if the contents are not completely and accurately described.

"Video" "Video" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Jazz Music Video Tapes." Clearance delays may result if the contents are not completely and accurately described.

"Videotape" "Videotape" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Jazz Music Video Tape." Clearance delays may result if the contents are not completely and accurately described.

Appendix C: Vague Commodity Descriptions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 285

Vague Commodity Vague Commodity Description

"Videotapes" "Videotapes" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Jazz Music Video Tapes." Clearance delays may result if the contents are not completely and accurately described.

"VISA MDR Table" "VISA MDR Table" is an incomplete description and not accepted by Customs. Please specify the description of the contents being shipped. Clearance delays may result if the contents are not completely and accurately described.

"Wafer" "Wafer" is an incomplete description and not accepted by Customs. An example of an acceptable description is "semiconductor wafers." Clearance delays may result if the contents are not completely and accurately described.

"Waste" "Waste" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Oil Waste for Testing." Clearance delays may result if the contents are not completely and accurately described.

"Wearing Apparel" "Wearing Apparel" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Women's Leather Sandals." Clearance delays may result if the contents are not completely and accurately described.

"Wire" "Wire" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Insulated Copper Wire." Clearance delays may result if the contents are not completely and accurately described.

"Wires" "Wires" is an incomplete description and not accepted by Customs. An example of an acceptable description is "Insulated Copper Wire." Clearance delays may result if the contents are not completely and accurately described.

Appendix D: Legal Terms and Conditions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 286

Appendix D: Legal Terms and Conditions Legal Terms Plain Paper and Thermal Label

In addition to creating and printing the waybill Label, you will need to print copies of the International Legal Terms and Conditions to accompany each Label with your International shipments. The following defines International handling instructions for the waybill labels and Legal Terms and Conditions document.

If International – U.S. export: Print 2 copies of the waybill Label to your laser printer, fold 1 copy in half and use as the shipping label. Place it in the waybill pouch and affix it to the shipment so that the bar code portion of the label can be read and scanned. Place the additional consignee copy of the waybill Label in the pouch.

If International – Shipments originating outside of the U.S.: Print 3 copies of the waybill Label to your laser printer, fold 1 copy in half and use as the shipping label. Place it in the waybill pouch and affix it to your shipment so that the bar code portion of the label can be read and scanned. Place the 2 consignee copies of the waybill Label in the pouch.

The following defines U.S. Domestic handling instructions for the waybill labels and Legal Terms and Conditions.

If U.S. Domestic shipment: Print 1 copy of the waybill Label to your laser printer, fold the printed page in half and use as the shipping label. Place it in the waybill pouch and affix it to your shipment so that the bar code portion of the label can be read and scanned.

NOTE:

The International and U.S. Domestic waybill Legal Terms and Conditions information must be supplied with test labels when completing the certification process.

WARNING: Use only the printed original labels for shipping to ensure the timely delivery of your package.

Appendix D: Legal Terms and Conditions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 287

Conditions of Contract

CONDITIONS OF CONTRACT Definitions: On this Air Waybill, "we", "our", "us", and "FedEx" refer to Federal Express Corporation, its subsidiaries and branches and their respective employees, agents, and independent contractors. The terms "you" and "your" refer to the shipper, its employees, principals and agents. If your shipment originates outside the United States, your contract of carriage is with the FedEx subsidiary, branch or independent contractor who originally accepts the shipment from you. The term "package" means any container or envelope that is accepted by us for delivery, including any such items tendered by you utilizing our automated systems, meters, manifests or waybills. The term "shipment" means all packages which are tendered to and accepted by us on a single Air Waybill. Agreement To Terms: By processing and giving us your shipment, you agree, regardless of whether you sign the front of this Air Waybill, for yourself and as agent for and on behalf of any other person having an interest in this shipment, to all terms on this NON-NEGOTIABLE Air Waybill, and as appropriate any FedEx transportation agreement between you and FedEx covering this shipment and in any applicable tariff, and in our current applicable Service Guide, or Standard Conditions of Carriage, copies of which are available upon request. If there is a conflict between this Air Waybill and any such document then in effect, the transportation agreement, tariff, Service Guide or Standard Conditions of Carriage will control in that order of priority. No one is authorized to alter or modify the terms of our agreement. This Air Way bill shall be binding on us when the shipment is accepted: we may mark this Air Waybill with an employee number as our signature, or our printed name shall be sufficient to constitute our signature of this Waybill. Your Obligations - Printed Signature: You acknowledge that if you process shipments to locations outside the country where your shipment originates, you must enter, to print in lieu of a manual signature on the Air Waybill, the name of the person completing the Air Waybill for all such shipments tendered to FedEx by you using this application. You further acknowledge that such printed name shall be sufficient to constitute your signature on the Air Waybill and acceptance of FedEx's terms and conditions of carriage for purposes of the Warsaw Convention, an International treaty related to International carriage by air and any amendments and protocols thereto, (collectively "Warsaw Convention") and for all other purposes. You warrant that each article in each shipment will be properly described on this Air Waybill and any export documents, is acceptable for transport by FedEx, and that the shipment will be properly marked, addressed and packed to ensure safe transportation with ordinary care in handling. You are responsible for all charges, including transportation charges and all duties, customs, assessments governmental penalties and fines, taxes and FedEx legal costs related to your shipment. Air Carriage Notice: IF THE CARRIAGE OF YOUR SHIPMENT BY AIR INVOLVES AN ULTIMATE DESTINATION OR STOP IN A COUNTRY OTHER THAN THE COUNTRY OF DEPARTURE, THE WARSAW CONVENTION MAY BE APPLICABLE, WHICH TREATY WOULD THEN GOVERN AND IN MOST CASES LIMIT FEDEX'S LIABILITY FOR LOSS, DELAY OF, SHORTAGE, MISDELIVERY, MISINFORMATION, DAMAGE OR FAILURE TO PROVIDE INFORMATION REGARDING YOUR SHIPMENT. In certain countries, the Warsaw convention limits FedEx's liability to U.S. $9.07 per pound (U.S. $20.38 per kilogram or equivalent local currency for the country of origin), unless a higher value for carriage is declared as described below and you pay any applicable supplementary charges. The interpretation and operation of the Warsaw convention's liability limits may vary in each country. There are no specific stopping places which are agreed to and FedEx reserves the right to route the shipment in any way FedEx deems appropriate. Road Transport Notice: Shipments transported partly or solely by road, be there an explicit agreement to do so or not, into or from a country which is a party to the Convention on the Contract for the International Carriage of Goods by Road (the "CMR") are subject to the terms and conditions of the CMR, notwithstanding any other provision of this Air Waybill to the contrary except that the higher limitations of liability as set forth in these conditions shall remain applicable as opposed to those set forth in the CMR. Limitation of Liability: If not governed by the Warsaw Convention, the CMR, or other International treaties, laws, other government regulations, orders, or requirements, FedEx's maximum liability for loss, damage, delay, shortage, misdelivery, or nondelivery of your shipment is limited by this Air Waybill to the greater of the amount of U.S. $100 or U.S. $9.07 per pound (U.S. $20.38 per kilo) (or equivalent local currency for the country of origin) (or in Canada, the amount of actual damages or CDN$100 per shipment, whichever is less)

Appendix D: Legal Terms and Conditions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 288

unless you declare, in advance, a higher value for carriage as described below and pay any applicable supplementary charges. FedEx does not provide cargo liability or all-risk insurance, but you may pay an additional charge for each additional U.S. $100 (or equivalent local currency for the country of origin) of declared value for carriage. If a higher value for carriage is declared and the additional charge is paid, FedEx's maximum liability will be the lesser of the declared value for carriage or your actual damages. Declared Value Limits: The highest declared value FedEx allows for a FedEx Letter/Envelope and FedEx Pak shipment is US$100 or US$9.07 per pound (US$20.38 per kilo)(or the equivalent in local currency), whichever is greater. In Canada, the maximum declared value allowed for customs and carriage per Air Waybill for each FedEx Letter and FedEx Pak is CAN$100. For other shipments, in particular shipments of extraordinary value, including, but not limited to jewelry, artwork, antiques, precious metals, and furs and fur clothing, the declared value of carriage is limited and depends on the contents and the destination of the shipment. Please check the applicable Service Guide, contract of carriage, tariff, or Standard Conditions for an explanation of the declared value limits. If you send more than one package using a single Air Waybill, the declared value for carriage of each package will be determined by dividing the total declared value for carriage by the number of packages in the shipment. Liabilities Not Assumed. IN ANY EVENT, SUBJECT TO THE SERVICE CONDITIONS ON THIS AIR WAYBILL, OR THE APPLICABLE SERVICE GUIDE, STANDARD CONDITIONS, TARIFF OR CONTRACT OF CARRIAGE, FEDEX WON'T BE LIABLE FOR ANY DAMAGES, WHETHER DIRECT, INDIRECT, INCIDENTAL, SPECIAL OR CONSEQUENTIAL, IN EXCESS OF THE DECLARED VALUE US$100 OR US$9.07 PER LB. (US$20.38 PER KILO) (OR THE EQUIVALENT IN LOCAL CURRENCY) WHICHEVER IS GREATER (OR IN CANADA IN EXCESS OF THE DECLARED VALUE FOR CARRIAGE) (INCLUDING BUT NOT LIMITED TO LOSS OF INCOME OR PROFITS) WHETHER OR NOT FEDEX HAD ANY KNOWLEDGE THAT SUCH DAMAGES MIGHT BE INCURRED. FedEx won't be liable for your acts or omissions, including but not limited to incorrect declaration of cargo, improper or insufficient packing, securing, marking or addressing of the shipment, or for the acts or omissions of the recipient or anyone else with an interest in the shipment. Also, FedEx won't be liable if you or the recipient violate any of the terms of our Agreement. FedEx won't be liable for damage, loss, delay, shortage, misdelivery, nondelivery, misinformation or failure to provide information regarding shipments of cash, currency or other prohibited items. FedEx won't be liable for loss, damage, delay, shortage, misdelivery, nondelivery, misinformation or failure to provide information (i) in connection with shipments of cash, currency, or other prohibited items; or, (ii) caused by events FedEx cannot control, including but not limited to acts of God, perils of the air, weather conditions, mechanical delays, acts of public enemies, war, strikes, civil commotions, or acts or omissions of public authorities (including customs and health officials) with actual or apparent authority. No Warranty: We make no warranties, express or implied. Claims for Loss, Damage or Delay: ALL CLAIMS MUST BE MADE IN WRITING AND WITHIN STRICT TIME LIMITS. SEE OUR TARIFF, APPLICABLE SERVICE GUIDE, OR STANDARD CONDITIONS OF CARRIAGE FOR DETAILS. The Warsaw Convention provides that written claims for damage must be received within 14 days from the date of receipt and within twenty-one days in the event of delay. FedEx may have expanded the claims periods in certain countries and the periods may differ from country to country. Moreover, the interpretation and operation of the Warsaw Convention's claims provisions may vary in each country. Contact the FedEx representative in the country of origin to determine the claims period for your shipment. In the event of nondelivery or misdelivery, we must receive written notice of the claim within 90 days after we accept the shipment. The right to damages against us shall be extinguished unless an action is brought within two years from the date of delivery of the shipment or from the date on which the shipment should have been delivered, or from the date on which the carriage stopped. Within 90 days after notification to us of the claim, it must be documented by sending us all relevant information about it. FedEx is not obligated to act on any claim until all transportation charges have been paid. The claim amount may not be deducted from the transportation charges. If the recipient accepts the shipment without noting any damage on the delivery record, FedEx will assume the shipment was delivered in good condition. In order for us to consider a claim for damage, the contents, original shipping carton and packing must be made available to us for inspection. Right to Inspect: Your shipments may, at FedEx's option, or at the request of customs or other regulatory or government authorities, be opened and inspected by FedEx or such authorities at any time. Responsibility For Payment: Even if you give FedEx different payment instructions, you will always be primarily responsible for all charges, including transportation charges, and all duties, custom assessments,

Appendix D: Legal Terms and Conditions

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 289

governmental penalties and fines, taxes, and FedEx's attorney fees and legal costs, related to shipments tendered under this Agreement. You also will be responsible for any costs FedEx may incur in returning your shipments to you or warehousing them pending disposition. Customs Clearance: By giving us this shipment, you hereby appoint FedEx, or its independent contractor as applicable, as your agent solely for performance of customs clearance and certify FedEx as the nominal consignee for the purpose of designating a customs broker to perform customs clearance. In some instances, local authorities may require additional documentation confirming FedEx's appointment. It is your responsibility to provide proper documentation and confirmation, where required. You are responsible for and warrant your compliance with all applicable laws, rules and regulations, including but not limited to customs laws, import and export laws and government regulations of any country to, from, through or over which your shipments may be carried. You agree to furnish such information and complete and attach to the shipments such documents as are necessary to comply with such laws, rules and regulations. FedEx assumes no liability to you or any other person for any loss or expense due to your failure to comply with this provision. You are also responsible for all charges, including transportation charges, and all duties, customs assessments, governmental penalties and fines, taxes, and FedEx lawyer's fees and legal costs, related to any shipment. Letter of Instruction: You do not complete all the documents required for carriage or if the documents submitted are not appropriate for the services or destination requested, you hereby instruct FedEx, or its independent contractor, as applicable, where permitted by law to complete, correct or replace the documents for you at your expense. However, FedEx is not obligated to do so. If a substitute form of air waybill is needed to complete delivery of your shipment and FedEx completes that document, the terms of this Agreement will continue to govern. FedEx is not liable to you or any other person for FedEx's actions on your behalf under this provision. Items Not Acceptable for Transportation: FedEx does not accept transportation of money (including, but not limited to, coins (except collectible) or negotiable instruments equivalent to cash such as endorsed stocks and bonds.) FedEx excludes all liability for shipments of such items accepted by mistake. Other items may be accepted for carriage only to limited destinations or under restricted conditions. FedEx reserves the right to reject packages based upon these limitations or for reasons of safety or security. You may consult the applicable Service Guide, contract of carriage, tariff or Standard Conditions for specific details. Export Control. You authorize FedEx, and its independent contractors, as applicable, to act as forwarding agent for you for export and customs purposes. You hereby certify that all statements and information contained on all Air Waybills, SEDs and accompanying documentation relating to exportation are true and correct. You further certify that all Commercial Invoice information submitted via API is true and correct. You expressly authorize FedEx and its independent contractors, as applicable, to forward all information of any nature regarding shipments to any and all governmental or regulatory agencies which request or require such information. Furthermore, you understand that civil and criminal penalties, including forfeiture and sale, may be imposed for making false or fraudulent statements or for the violation of any country laws on exportation, including but not limited to, for shipments originating in the U.S., 13 U.S.C. &sect;305; 22 U.S.C. &sect;401; 18 U.S.C. &sect;1001; and 50 U.S.C. App. 2410, and for shipments originating in Canada, the Export and Import Permits Act, R.S.C. E-17. Consult the laws in the country of origin for similar restrictions. You acknowledge that no shipments tendered by you from the United States using API will be sent to any entity listed on the Department of Commerce's Denied Parties List 15 C.F.R. Part 764, Supp. 2, or the list of Special Designated Nationals as published by the Office of Foreign Assets Control of the U.S. Department of the Treasury and that you are neither a denied party or a specially designated national. Consult the laws of the origin country of your shipment for similar provisions. Mandatory Law: Insofar as any provision contained or referred to in the Air Waybill may be contrary to any applicable international treaties, laws, governmental regulations, orders or requirements, such provision shall remain in effect as part of our agreement to the extent that it is not overridden. The invalidity or unenforceability of any provision shall not affect any other provision contained or referred to in the Air Waybill. Unless otherwise indicated, the shipper's address indicated on the face of the Air Waybill is the place of execution and the place of departure and the recipient's address listed on the face of the Air Waybill is the place of destination. Unless otherwise indicated, the first carrier of this shipment is Federal Express Corporation, P.O. Box 727, Memphis, TN 38194.

Glossary

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 290

Glossary

AES: Automatic Export System

AHS: Additional Handling Charge

API: Application Programming Interface

ASTRA: Advanced Sorting Tracking Routing Assistance

BSO: Broker Select Option

CAD: Canadian Dollars (also $CAD)

CCI: Canada Customs Invoice

CFR or C&F (Cost and Freight): (Destination port-paid to arrival at destination port) Title, risk and insurance cost pass to buyer when delivered on board the ship by seller who pays the transportation cost to the destination port. Used for sea or inland waterway transportation.

CI: Commercial Invoice

CIF (Cost, Insurance and Freight): (Destination port-same as CFR, but includes insurance) Title and risk pass to buyer when delivered on board the ship by seller who pays transportation and insurance cost to destination port. Used for sea or inland waterway transportation.

CIP (Carriage and Insurance Paid To): (Place at destination – CPT, but insurance). Title and risk pass to buyer when delivered to carrier by seller who pays transportation and insurance cost to destination. Used for any mode of transportation.

COD: Collect on Delivery

CPT (Carriage Paid To): (Place at destination – includes all destination port charges). Title, risk, and insurance cost pass to buyer when delivered to carrier or seller who pays transportation and insurance cost to destination. Used for any mode of transportation.

DDP (Delivered Duty Paid): (Consignee door – includes all charges origin to destination). Title and risk pass to buyer when seller delivers goods to named destination point cleared for import. Used for any mode of transportation.

Glossary

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 291

DDU (Delivered Duty Unpaid): (Consignee door-excluding duties and taxes). Title, risk and responsibility for vessel discharge and import clearance pass to buyer when seller delivers goods on board the ship to destination port. Used for sea or inland waterway transportation.

DG: Dangerous Goods

ECI: Electronic Commercial Invoice

ECOD: Electronic Collect on Delivery

EIN: Employer Identification Number

EXW (Ex Works): (Factory, mill, warehouse: your door) Title and risk pass to buyer including payment of all transportation and insurance cost from the seller's door. Used for any mode of transportation.

FASC: FedEx Authorized Shipping Center

FCA (Free Carrier): (Pick a place after your origin to start) Title and risk pass to buyer including transportation and insurance cost when the seller delivers goods cleared for export to the carrier. Seller is obligated to load the goods on the Buyer's collecting vehicle; it is the Buyer's obligation to receive the Seller's arriving vehicle unloaded.

FDXE: FedEx Express

FDXG: FedEx Ground

FHD: FedEx Home Delivery

FICE: FedEx International Controlled Export

FOB (Free On Board): (Port-same as FAS) Risk pass to buyer including payment of all transportation and insurance cost once delivered on board the ship by the seller. Used for sea or inland waterway transportation.

FTSR: Foreign Trade Statistics Regulations

Girth: Girth is the sum of the four smallest dimensions of a package. Girth = (2” Width + 2” Height).

GST: Global Sales Tax

HAL: Hold at Location

Glossary

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 292

HazMat: Hazardous Materials

HST: Harmonized Sales Tax

IEFS: International Economy Freight Service

IPFS: International Priority Freight Service

ITAR: International Traffic in Arms

KGS: Kilograms

LBS: Pounds

MBG: Money Back Guarantee

MPS: Multiple-Piece Shipment

MTW: Multiweight

NAFTA: North America Free Trade Agreement

OS: Oversize

Oversize Packages (Ground): A package whose Length plus Girth is greater than 84 inches is considered to be Oversize. Oversize packages are considered to have a minimum weight of 30 lbs. (or 50 lbs. if the Length plus the Girth is greater than 108 inches) for U.S. shipments and 50 lbs. for Canadian shipments. There is also a maximum allowable size of “Length plus Girth less than or equal to 130 inches,” as well as a maximum allowable single dimension of 108 inches.

PNG: Portable Network Graphic

PO: Priority Overnight OR Purchase Order

POD: Proof of Delivery

PST: Provincial Sales Tax

RMA: Return Merchandise Authorization

Glossary

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 293

SED: Shipper’s Export Declaration

SLAC: Shipper’s Load And Count

SPOD: Signature Proof of Delivery

SSN: Social Security Number

URSA: Universal Routing and Sorting Aid

USD: U.S. Dollars (also $USD)

UTI: Universal Transaction Identifier

Unit of Measure codes:

Unit of Measure Codes

AR – Carat GR – Gross LYD – Linear Yard CFT – Cubic Feet GAL – Gallon M – Meters CG – Centigrams KG – Kilograms MG – Milligram CM – Centimeters KGM – Kilogram ML – Milliliter CM3 – Cubic Centimeters L – Liter M2 – Square Meters DOZ – Dozen LB – Pound M3 – Cubic Meters DPR – Dozen Pair LFT – Linear Foot NO – Number EA – Each LNM – Linear Meters OZ – Ounces G – Grams LTR – Liters PCS – Pieces

ZIP (code): Zone Improvement Plan code

Index

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 294

Index 0 007: Close Request, 100 019: Service Availability Request, 18 021: Ship a Package Request, 55 022: Rate a Package Request, 26 023: Delete a Package Request, 96 025: Rate Available Services Request, 44 033: Cancel E-Mail Label Request, 152 037: E-Mail Label Request, 136 044: Call Tag Create Request, 156 045: Call Tag Cancel Request, 166 046: Express Tag Dispatch Create Request, 170 047: Express Tag Dispatch Cancel Request, 181 048: Express Tag Availability Request, 185

1 107: Close Reply, 103 119: Service Availability Reply, 22 121: Ship a Package Reply, 83 122: Rate a Package Reply, 34 123: Delete a Package Reply, 98 125: Rate Available Services Reply, 49 133: Cancel E-Mail Label Reply, 154 137: E-Mail Label Reply, 149 144: Call Tag Create Reply, 164 145: Call Tag Cancel Reply, 168 146: Express Tag Dispatch Create Reply, 178 147: Express Tag Dispatch Cancel Reply, 183 148: Express Tag Availability Reply, 188

2 211: Subscription/Registration Request, 13

3 311: Subscription/Registration Reply, 16

4 403: Track a Package Request, 106 405: Signature Proof of Delivery Request, 119 410: FedEx Locator Request, 127

5 503: Track a Package Reply, 110 505: Signature Proof of Delivery Reply, 124 510: FedEx Locator Reply, 132

C Call Tag Cancel Reply (145), 168 Call Tag Cancel Request (045), 166 Call Tag Create Reply (144), 164 Call Tag Create Request (044), 156 Cancel E-Mail Label Reply (133), 154 Cancel E-Mail Label Request (033), 152 Close Reply (107), 103 Close Request (007), 100 Conditions of Contract, 287 Country Codes table, 259

Index

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 295

D Delete a Package Reply (123), 98 Delete a Package Request (023), 96

E E-Mail Label Reply (137), 149 E-Mail Label Request (037), 136 Express Tag Availability Reply (148), 188 Express Tag Availability Request (048), 185 Express Tag Dispatch Cancel Reply (147), 183 Express Tag Dispatch Cancel Request (047), 181 Express Tag Dispatch Create Reply (146), 178 Express Tag Dispatch Create Request (046), 170

F FedEx Locator Reply (510), 132 FedEx Locator Request (410), 127 Field Descriptions by Field Tag, 202

G Glossary, 290

I Introduction, 5

L label data buffer, 195 label specifications

custom labels, 194 determining screen resolution, 193 label data buffer, 195 plain paper and thermal, 191

PNG plain paper label, 192 Sample C, 198 shipping label support, 195 using buffer data to print PNG or thermal labels, 196

Legal Terms and Conditions, 286

R Rate a Package Reply (122), 34 Rate a Package Request (022), 26 Rate Available Services Reply (125), 49 Rate Available Services Request (025), 44 Referenced Documents, 10

S Service Availability Reply (119), 22 Service Availability Request (019), 18 Ship a Package Reply (121), 83 Ship a Package Request (021), 55 Shipping Label Specifications, 191 Signature Proof of Delivery Reply (505), 124 Signature Proof of Delivery Request (405), 119 Subscription/Registration Reply (311), 16 Subscription/Registration Request (211), 13

T Tagged Transaction Layouts, 11 Track a Package Reply (503), 110 Track a Package Request (403), 106 transaction set

formatting, 5 general information, 5 Transaction Terminator, 5 Transaction Type, 5

Index

FedEx Ship Manager® API/Direct Tagged Transaction Guide, Jun05.0 296

U Universal Transaction Identifiers (UTI), 6

V Vague Commodity Descriptions, 263

W What’s New, 8