FedEx Ship Manager® Server
v 10.6.1
Developer Guide
Legal and Copyright Notices
Payment
You must remit payment in accordance with the FedEx Service Guide, tariff, service agreement or other terms or instructions provided to
you by FedEx from time to time. You may not withhold payment on any shipments because of equipment failure or for the failure of FedEx to
repair or replace any equipment.
Inaccurate Invoices
If you generate an inaccurate invoice, FedEx may bill or refund to you the difference according to the FedEx Service Guide, tariff service
agreement or other terms or instructions provided to you by FedEx from time to time. A request for refund on a FedEx shipment must be
made in accordance with the applicable Service Guide or terms or instructions provided by FedEx from time to time. A shipment given to
FedEx with incorrect information is not eligible for refund under any FedEx money-back guarantees. FedEx may suspend any applicable
money-back guarantees in the event of equipment failure or if it becomes inoperative.
Confidential and Proprietary
The information contained in this guide is confidential and proprietary to FedEx Corporate Services, Inc. and its affiliates (collectively
“FedEx”). No part of this 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 Automation Agreement. The information in this
document may be changed at any time without notice. Any conflict between this guide, the FedEx Automation Agreement and the FedEx
Service Guide shall be governed by the FedEx Automation Agreement and the FedEx Service Guide, in that order.
© 2010 FedEx. FedEx and the FedEx logo are registered service marks. All rights reserved. Unpublished.
Disclaimer
All Improper Transaction scenarios are for example only. They do not reflect all error condition scenarios.
Contents
ABOUT THIS DOCUMENT.............................................................................. XXVII
Organization ......................................................................................................................... xxvii
Audience............................................................................................................................... xxvii
Conventions.......................................................................................................................... xxvii
Resources............................................................................................................................ xxviii
Support ................................................................................................................................ xxviii
FedEx website ............................................................................................................. xxviii
FedEx Service Guide................................................................................................... xxviii
FedEx EEI Filing Options (U.S. only)........................................................................... xxviii
REVISION HISTORY ........................................................................................ XXIX
CHAPTER 1: INTRODUCTION TO FEDEX SHIP MANAGER SERVER
FedEx Ship Manager Server .................................................................................................
Overview................................................................................................................................
Architecture............................................................................................................................
FedEx Ship Manager Server Transaction Model...................................................................
Network and Internet Requirements ......................................................................................
Getting Started with FedEx Ship Manager Server.................................................................
1-1
1-2
1-2
1-4
1-4
1-4
CHAPTER 2: ABOUT FEDEX SHIP MANAGER SERVER TRANSACTIONS
FedEx Ship Manager Server Transaction Overview.............................................................. 2-1
Flexible Transaction Functions ...................................................................................... 2-1
Rule-Driven Transaction Logic....................................................................................... 2-2
Shipping Services from FedEx....................................................................................... 2-2
Before You Begin to Code ..................................................................................................... 2-2
Develop Knowledge of FedEx Services......................................................................... 2-2
Become Familiar with Resources .................................................................................. 2-2
FedEx Ship Manager Server Shipping Process and Workflow.............................................. 2-3
FedEx Ship Manager Server Transaction Request/Reply Pairs............................................ 2-5
List of FedEx Ship Manager Server Transaction Pairs .................................................. 2-5
004/104 Tracking Number Request/Reply..................................................................... 2-5
007/107 End-of-Day Close Request/Reply .................................................................... 2-6
020/120 Global Ship Request/Reply.............................................................................. 2-6
023/123 Global Delete Request/Reply........................................................................... 2-9
024/124 Shipment Query Request/Reply ...................................................................... 2-9
025/125 Rate Available Services Request/Reply ........................................................ 2-10
033/133 Delete E-Mail Label Request/Reply ............................................................... 2-11
035/135 Child Meter Registration Request/Reply........................................................ 2-11
049/149 Pre-Shipment Document Upload Request/Reply........................................... 2-11
050/150 Service Types and Special Services Request/Reply ..................................... 2-12
050/150 Versioning Request/Reply ............................................................................. 2-12
057/157 Demand Download Request/Reply................................................................ 2-13
v 10.6.1
FedEx Ship Manager® Server Developer Guide
iii
Contents
070/170 Meter Query Request/Reply ..........................................................................
095/195 Label Reprint Request/Reply.........................................................................
FedEx Web Services ...................................................................................................
Basic Shipping Data for FedEx Ship Manager Server Transactions ...................................
METER Number ..........................................................................................................
RECIPIENT Information...............................................................................................
SENDER/SHIPPER Information ..................................................................................
SERVICE Type............................................................................................................
PACKAGE Information ................................................................................................
Payment Type..............................................................................................................
Transaction Identifier ...................................................................................................
How to Build FedEx Ship Manager Server Transactions ....................................................
Key Elements of Information........................................................................................
Grouped Field Data for Key Elements .........................................................................
Shipment and Service Information...............................................................................
Select the Transaction Action......................................................................................
Transaction String Elements........................................................................................
Data Fields and Values................................................................................................
Single Piece versus Multiple Piece Transactions ................................................................
Single Piece.................................................................................................................
Multiple Piece ..............................................................................................................
Multiple Occurrence Fields ..........................................................................................
Single Shot versus Open Ship Shipping......................................................................
How to Read FedEx Ship Manager Server Transaction Coding Tables .............................
Table Conventions.......................................................................................................
Transaction Coding Reference Guide .........................................................................
Transactions Do More Than Ship........................................................................................
Rates, Rate Quotes and List Rates .............................................................................
Routing and Time-In-Transit ........................................................................................
Package and Shipment Tracking.................................................................................
Close Shipment at End-of-Day ....................................................................................
Submitting Transactions ......................................................................................................
Batching Transactions in a File....................................................................................
Monitoring Input Batch Files ........................................................................................
Error Messages and Troubleshooting .................................................................................
FedEx Ship Manager Server Log File..........................................................................
Next Steps ...........................................................................................................................
2-13
2-14
2-14
2-15
2-15
2-15
2-15
2-15
2-15
2-15
2-16
2-16
2-16
2-17
2-17
2-18
2-19
2-21
2-26
2-26
2-26
2-27
2-28
2-29
2-30
2-31
2-32
2-32
2-32
2-33
2-33
2-33
2-33
2-34
2-35
2-35
2-35
CHAPTER 3: FEDEX SHIP MANAGER SERVER LABEL AND FORM
TRANSACTIONS
FedEx Ground Hazardous Materials OP-900 Form/Report...................................................
Formats for Hazardous Materials OP-900 Label ...........................................................
Printing Information on Ground OP-900/OP-900B Forms/Reports................................
Printing the HazMat Class on the OP-900 Form ...........................................................
Coding Data on the Laser Form for Hazardous Materials OP-900 Form ......................
Fields for Laser Format for OP-900 Form......................................................................
iv
FedEx Ship Manager® Server Developer Guide
3-1
3-1
3-1
3-3
3-6
3-6
v 10.6.1
Contents
Designating a Printer Path for OP-900 Forms ............................................................... 3-8
Configure Hazardous Materials OP-900LL Report ........................................................ 3-8
Printing DOT HazMat Class and Subsidiary Risk .......................................................... 3-8
Formats for DOT HazMat Class and Subsidiary Risk Fields ......................................... 3-8
FedEx Hazardous Materials Form OP-900LG....................................................................... 3-9
FedEx Express Shipper’s Declaration for Dangerous Goods Form .................................... 3-11
About EPRRQ Labels .................................................................................................. 3-14
About FedEx Labels ............................................................................................................ 3-14
FedEx Standard Labels ............................................................................................... 3-14
Custom Labels............................................................................................................. 3-15
Label Types and Formats .................................................................................................... 3-15
Thermal Labels ............................................................................................................ 3-15
Laser Labels ................................................................................................................ 3-16
Multi-Ply Air Waybills ................................................................................................... 3-16
Label Formats.............................................................................................................. 3-16
Configuring Printers for Labels, Forms and Reports.................................................... 3-17
Print Label Options ...................................................................................................... 3-20
Labels and Doc-Tabs........................................................................................................... 3-26
Creating a Custom Doc-Tab Label .............................................................................. 3-27
Doc-Tab Settings ......................................................................................................... 3-27
Doc-Tab Fields............................................................................................................. 3-27
How to Configure Doc-Tabs......................................................................................... 3-35
How to Print Reference Information on Labels .................................................................... 3-36
Printing Reference Information on a Return Label....................................................... 3-36
Printing Reference Information on FedEx Ground Labels ........................................... 3-38
Printing Reference Information on FedEx Express Labels .......................................... 3-39
Printing Reference Information on FedEx SmartPost Labels ...................................... 3-42
How to Customize Labels .................................................................................................... 3-43
FedEx SmartPost Customizable Labels ...................................................................... 3-44
Customizing a Thermal Label ...................................................................................... 3-44
Submitting Custom Labels for FedEx Approval ........................................................... 3-47
Label Transaction Samples ................................................................................................. 3-48
Transaction Sample for Shipment 1234 to Indianapolis from Sam's Publishing.......... 3-48
Transaction Sample for Shipment 23456 to Indianapolis from Sam's Publishing........ 3-49
Transaction Sample for Shipment 34567 to Indianapolis from Sam's Publishing........ 3-49
FedEx Label Samples.......................................................................................................... 3-50
FedEx Express U.S. Label........................................................................................... 3-51
FedEx Home Delivery Label ........................................................................................ 3-52
FedEx Ground HazMat Label ...................................................................................... 3-53
FedEx SmartPost Label ............................................................................................... 3-54
FedEx International DirectDistribution Surface Solutions Labels................................. 3-55
CHAPTER 4: FEDEX SHIP MANAGER SERVER OPEN SHIP TRANSACTIONS
Open Ship for FedEx Ship Manager Server .......................................................................... 4-1
FedEx Services with Open Ship .................................................................................... 4-2
Open Ship Process and Workflow ......................................................................................... 4-2
v 10.6.1
FedEx Ship Manager® Server Developer Guide
v
Contents
About FedEx Ship Manager Server Open Ship Transactions ............................................... 4-4
Field 541 Open Ship Flags ............................................................................................ 4-4
Rules for Open Ship Transactions................................................................................. 4-5
Performing Pre-Ship Validation for Open Ship ...................................................................... 4-6
CREATE Open Ship Shipment Transaction .......................................................................... 4-7
CREATE Open Ship Shipment ...................................................................................... 4-8
CREATE Open Ship Print-As-You-Go Shipment........................................................... 4-9
ROUTE and Time-In-Transit Transaction............................................................................ 4-10
RATE Open Ship Shipment Transaction ............................................................................. 4-14
ADD Piece Transaction ....................................................................................................... 4-15
ADD Piece - Shipment and Package Level Fields....................................................... 4-18
Returned ADD Piece Fields......................................................................................... 4-25
EDIT Piece Transaction....................................................................................................... 4-25
EDIT Piece Fields........................................................................................................ 4-26
EDIT Open Ship Shipment Transaction .............................................................................. 4-27
EDIT Shipment Fields.................................................................................................. 4-28
DELETE Piece Transaction................................................................................................. 4-28
DELETE Piece - Prior To CONFIRM ........................................................................... 4-29
DELETE Piece - After CONFIRM ................................................................................ 4-30
DELETE Piece Fields .................................................................................................. 4-30
DELETE Shipment Transaction........................................................................................... 4-31
DELETE Open Ship Shipment Fields .......................................................................... 4-32
CONFIRM Piece and Print Label......................................................................................... 4-35
Steps for Package CONFIRM...................................................................................... 4-35
CONFIRM Package Fields .......................................................................................... 4-36
CONFIRM Piece and Shipment Transactions ..................................................................... 4-36
CONFIRM Open Ship Shipment Fields ....................................................................... 4-37
Confirming Open Ship and Printing Labels.................................................................. 4-39
Open Ship Print Options...................................................................................................... 4-39
Open Ship Print-At-The-End........................................................................................ 4-39
Open Ship Print-As-You-Go ........................................................................................ 4-39
Print-As-You-Go Package Association and Print Modes............................................. 4-40
Open Ship Print-As-You-Go Fields.............................................................................. 4-41
Open Ship PAYG Transaction Summary..................................................................... 4-43
FedEx Express U.S. Open Ship Transaction Samples ....................................................... 4-44
FedEx Express U.S. Export Open Ship Transactions ................................................. 4-45
FedEx Ground Open Ship Transaction Samples ................................................................ 4-47
FedEx SmartPost Open Ship Transaction Samples............................................................ 4-49
CHAPTER 5: CODING TRANSACTIONS FOR FEDEX EXPRESS U.S. SERVICE
About FedEx Express U.S. and FedEx Express U.S. Freight ...............................................
FedEx Express U.S. ......................................................................................................
FedEx Express U.S. Freight ..........................................................................................
Transaction Rules and Restrictions for FedEx Express U.S. ................................................
FedEx Priority Overnight................................................................................................
FedEx 2Day ...................................................................................................................
vi
FedEx Ship Manager® Server Developer Guide
5-1
5-1
5-1
5-2
5-2
5-2
v 10.6.1
Contents
FedEx Standard Overnight ............................................................................................ 5-3
FedEx First Overnight .................................................................................................... 5-3
FedEx Express Saver .................................................................................................... 5-3
Available Shipping Methods for FedEx Express U.S. .................................................... 5-3
Coding Guidelines for FedEx Express U.S............................................................................ 5-4
Transaction Fields for FedEx Express U.S. Shipments......................................................... 5-5
Deleting a FedEx Express Shipment ............................................................................. 5-9
Shipping Service Options for FedEx Express U.S................................................................. 5-9
FedEx Express U.S. Collect-on-Delivery Service ........................................................ 5-10
FedEx Delivery Signature Options - FedEx Express ................................................... 5-14
FedEx Express Future Day.......................................................................................... 5-17
FedEx Express Hold At FedEx Location...................................................................... 5-17
Saturday Pickup and Delivery Service......................................................................... 5-19
Inside Pickup and Delivery - FedEx Express U.S. Freight Only .................................. 5-21
Alcohol Shipping .......................................................................................................... 5-21
Shipping Dangerous Goods with FedEx Express U.S......................................................... 5-22
Shipping Dangerous Goods in Excepted Quantities.................................................... 5-22
Dangerous Goods Technical Name............................................................................. 5-24
Creating a Dangerous Goods Transaction .................................................................. 5-25
Adding Dangerous Goods Packages to Shipments..................................................... 5-27
FedEx Express Other Regulated Materials-Domestic ................................................. 5-30
About Excepted Package Radioactive Reportable Quantity (EPRRQ)........................ 5-32
Dry Ice.......................................................................................................................... 5-39
FedEx Express Domestic Billed Weight....................................................................... 5-42
FedEx Express U.S. Transaction Samples.......................................................................... 5-42
FedEx Express U.S. Shipping Transactions ................................................................ 5-42
FedEx Express U.S. Freight Shipping Transaction...................................................... 5-43
FedEx Express Dangerous Goods Transactions......................................................... 5-43
FedEx Express Return Transactions ........................................................................... 5-45
FedEx Delivery Signature Option Transactions ........................................................... 5-45
FedEx Express Basic Streamlined Transaction........................................................... 5-46
CHAPTER 6: CODING TRANSACTIONS FOR FEDEX GROUND U.S. SERVICES
About FedEx Ground U.S. Service Shipping Transactions ................................................... 6-1
Available Shipping Methods for FedEx Ground U.S. ..................................................... 6-1
Transaction Rules and Restrictions for FedEx Ground U.S. ................................................. 6-2
Coding Guidelines for FedEx Ground U.S. Transactions ...................................................... 6-3
Transaction Fields for FedEx Ground U.S............................................................................. 6-4
Package Size and Weight Rules for FedEx Ground and Home Delivery U.S. .............. 6-5
Non-Standard Packaging Rules for FedEx Ground ....................................................... 6-6
Additional Form and Label Information.......................................................................... 6-8
Deleting a FedEx Ground Shipment .............................................................................. 6-9
FedEx Home Delivery Premium Service Upgrades............................................................... 6-9
Home Delivery Service Upgrades................................................................................ 6-10
FedEx Home Delivery Fields ....................................................................................... 6-10
FedEx Home Delivery Service ..................................................................................... 6-11
v 10.6.1
FedEx Ship Manager® Server Developer Guide
vii
Contents
Shipping Service Options for FedEx Ground U.S................................................................
FedEx Ground Collect on Delivery Services................................................................
FedEx Ground Future Day...........................................................................................
FedEx Delivery Signature Services - FedEx Ground...................................................
Saturday Pickup and Delivery Fields - FedEx Home Delivery.....................................
Customized Time in Transit Field ................................................................................
FedEx Ground Multi-weight Pricing (U.S.)...................................................................
Hazardous Materials Shipments - FedEx Ground ...............................................................
General Shipping Information for all Hazardous Materials ..........................................
Shipping Rules for ORM-D ..........................................................................................
Shipping Rules for all other Hazardous Materials........................................................
FedEx Ground Tracking Numbers.......................................................................................
Allocation of FedEx Ground Tracking Numbers ..........................................................
FedEx Ground End-of-Day Reports ....................................................................................
FedEx Ground U.S. Transaction Samples ..........................................................................
Multiple and Single Piece Transaction Samples..........................................................
FedEx Ground and Home Delivery Return Transaction Samples ...............................
FedEx Ground Hazardous Materials Transaction Samples.........................................
FedEx Ground Open Ship Transaction Sample ..........................................................
FedEx Ground and FedEx Home Delivery Basic Streamlined Transactions...............
6-12
6-12
6-18
6-19
6-20
6-20
6-21
6-22
6-22
6-30
6-35
6-35
6-36
6-37
6-38
6-39
6-40
6-42
6-43
6-44
CHAPTER 7: CODING TRANSACTIONS FOR FEDEX SMARTPOST
FedEx SmartPost Service Types........................................................................................... 7-2
Configuring FedEx SmartPost ............................................................................................... 7-2
Configuring FedEx SmartPost Outbound Services........................................................ 7-3
Configuring FedEx SmartPost Returns Service............................................................. 7-3
Obtaining Tracking Numbers ......................................................................................... 7-6
Configuring Handling Charges in the Meter Settings Tab ............................................. 7-9
Setting Up FedEx SmartPost Rates ............................................................................ 7-12
FedEx SmartPost Doc-Tab Settings............................................................................ 7-13
Configuring FedEx SmartPost Reports........................................................................ 7-15
Printing FedEx SmartPost Reports.............................................................................. 7-18
Shipping to Military Locations.............................................................................................. 7-23
Invalid Transactions..................................................................................................... 7-24
FedEx SmartPost Returns Service...................................................................................... 7-24
How it Works................................................................................................................ 7-24
Features....................................................................................................................... 7-24
Pay Types.................................................................................................................... 7-25
Packaging.................................................................................................................... 7-25
Declared Value ............................................................................................................ 7-26
Other Regulated Materials - Domestic......................................................................... 7-26
Special Services .......................................................................................................... 7-27
FedEx SmartPost Labels..................................................................................................... 7-27
Print-As-You Go Labels for FedEx SmartPost............................................................. 7-27
Label Formats.............................................................................................................. 7-28
FedEx SmartPost Label Samples................................................................................ 7-28
viii
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Contents
Requesting a Rate Quote for FedEx SmartPost.................................................................. 7-33
Closing a FedEx SmartPost Shipment ................................................................................ 7-33
FedEx SmartPost Manifest .......................................................................................... 7-34
Closing with FedEx Ground as Carrier ........................................................................ 7-34
Delivery Confirmation Changes ........................................................................................... 7-34
Shipment and Delivery E-Mail Notifications......................................................................... 7-34
Tracking FedEx SmartPost Shipments................................................................................ 7-41
FedEx SmartPost Transactions ........................................................................................... 7-41
020/120 Global Ship Request/Reply............................................................................ 7-41
004 Tracking Number Request .................................................................................... 7-42
023 Delete Request ..................................................................................................... 7-42
024 Shipment Query Request...................................................................................... 7-42
033 Delete E-Mail Label Request ................................................................................ 7-42
035 Meter Registration Request .................................................................................. 7-42
057 Demand Download Request ................................................................................. 7-42
070 Meter Query or Configuration Request ................................................................. 7-42
095 Label Reprint Request .......................................................................................... 7-42
007/107 End-of-Day Close Request/Reply .................................................................. 7-43
Transaction Rules for FedEx SmartPost ............................................................................. 7-43
Future Day Shipping ............................................................................................................ 7-44
Coding a Basic FedEx SmartPost Shipping Transaction..................................................... 7-45
Coding a Basic FedEx SmartPost Print Returns Label Transaction.................................... 7-59
Coding a Basic FedEx SmartPost E-Mail Returns Shipping Transaction............................ 7-77
Creating a FedEx SmartPost Open Ship Transaction ......................................................... 7-88
Coding Pre-assigned Tracking Numbers............................................................................. 7-90
FedEx SmartPost Transaction Samples.............................................................................. 7-95
004 Tracking Number Request for FedEx SmartPost.................................................. 7-95
007 End-of-Day Close for FedEx SmartPost ............................................................... 7-95
107 End-of-Day Close Reply for FedEx SmartPost ..................................................... 7-95
020 Global Ship Request for FedEx SmartPost........................................................... 7-96
120 Global Ship Reply for FedEx SmartPost............................................................... 7-96
023/123 Global Delete Request/Reply for FedEx SmartPost ...................................... 7-97
FedEx SmartPost Open Ship Transactions ................................................................. 7-97
Print-As-You-Go Labels for FedEx SmartPost........................................................... 7-100
CHAPTER 8: CODING TRANSACTIONS FOR FEDEX INTERNATIONAL
SHIPPING
FedEx International Shipping Services..................................................................................
FedEx Special Options for International Service ...........................................................
Features of Electronic Trade Documents ......................................................................
FedEx International DirectDistribution Surface Solutions ..............................................
FedEx International DirectDistribution Services.............................................................
FedEx Global Trade Manager Online ....................................................................................
FedEx International Resource Center............................................................................
Processing an International Shipment ...................................................................................
Research Your Shipment...............................................................................................
v 10.6.1
FedEx Ship Manager® Server Developer Guide
8-1
8-2
8-3
8-3
8-4
8-5
8-5
8-5
8-6
ix
Contents
Pack and Process the Shipment.................................................................................... 8-7
Prepare the Label .......................................................................................................... 8-9
Print and/or Upload International Documents................................................................ 8-9
Confirm and Ship......................................................................................................... 8-10
International Shipping Documents....................................................................................... 8-10
Providing Detailed Descriptions of Goods ................................................................... 8-11
Customs Clearance Documents .................................................................................. 8-12
FedEx Trade Networks and Brokerage Services......................................................... 8-18
CHAPTER 9: CODING TRANSACTIONS FOR FEDEX EXPRESS
INTERNATIONAL SERVICES
About FedEx Express International Shipping Transactions .................................................. 9-1
Transaction Rules and Restrictions for FedEx Express International ................................... 9-1
Electronic Export Information......................................................................................... 9-2
FedEx Express International Service Options ....................................................................... 9-2
FedEx Delivery Signature Options................................................................................. 9-3
Saturday Pickup and Delivery........................................................................................ 9-3
Inside Pickup and Delivery ............................................................................................ 9-4
Dangerous Goods.......................................................................................................... 9-4
Future Day ..................................................................................................................... 9-5
Cut Flowers.................................................................................................................... 9-5
Coding Transactions for FedEx Express International .......................................................... 9-6
Fields for FedEx Express International Shipping........................................................... 9-6
Third Party Consignee................................................................................................... 9-9
FedEx Electronic Trade Documents Fields ................................................................. 9-11
Deleting a FedEx Express International Shipment ...................................................... 9-20
FedEx Express International List Rates and Surcharges ............................................ 9-20
FedEx Express International List Rates Fields ............................................................ 9-21
Surcharges for International Service Options .............................................................. 9-22
Returning Total Charges Without Added Canada Taxes............................................. 9-22
Transaction Scenarios for Requesting List Rates and Surcharges ............................. 9-24
Transaction Samples........................................................................................................... 9-26
Intra-Mexico FedEx Express Transaction Sample....................................................... 9-26
FedEx Electronic Trade Documents Sample Transactions ......................................... 9-26
CHAPTER 10: CODING TRANSACTIONS FOR FEDEX INTERNATIONAL
GROUND SERVICES
About FedEx International Ground Transactions ................................................................ 10-1
About FedEx International Ground Distribution and International Ground DirectDistribution 101
IGD/IGDD Settings Configuration ................................................................................ 10-2
IGD Configuration........................................................................................................ 10-2
IGD Transaction Coding .............................................................................................. 10-3
FedEx International Ground Distribution Transaction Rules ............................................... 10-4
FedEx International Ground DirectDistribution Transaction Rules ...................................... 10-5
x
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Contents
FedEx International Ground Importer Options..................................................................... 10-5
Rules for Electronic Commercial Invoice ..................................................................... 10-6
Bill Collect with Broker Information Selected ............................................................... 10-7
Dynamic Surcharge for Clearance Entry Fee .............................................................. 10-7
Coding Transactions for FedEx Ground International ......................................................... 10-8
Transaction Fields for International Ground................................................................. 10-8
FedEx Electronic Trade Documents Fields................................................................ 10-10
Deleting a FedEx International Ground Shipment ..................................................... 10-18
Signature Options for Canada Ground Shipments .................................................... 10-19
Applying Duty/Tax Payment to FedEx Ground International Shipments ................... 10-22
NAFTA Certificate of Origin ............................................................................................... 10-22
NAFTA Certificate of Origin Fields............................................................................. 10-22
NAFTA Certificate of Origin (COO) Preference Criterion........................................... 10-25
Printing the NAFTA Certificate of Origin .................................................................... 10-25
Generating a NAFTA Certificate of Origin.................................................................. 10-26
NAFTA Certificate of Origin Sample .......................................................................... 10-27
General Agency Agreement Form ..................................................................................... 10-30
Generating a General Agency Agreement Form ....................................................... 10-30
General Agency Agreement Form Sample ................................................................ 10-30
CHAPTER 11: CODING TRANSACTIONS FOR FEDEX INTERNATIONAL
DIRECTDISTRIBUTION SURFACE SOLUTIONS
About FedEx International DirectDistribution Surface Solutions Transactions .................... 11-1
Available Shipping Methods......................................................................................... 11-1
Transaction Rules for FedEx International DirectDistribution Surface Solutions................. 11-2
Transaction Fields for FedEx International DirectDistribution Surface Solutions ................ 11-3
Non FedEx Trade Networks Customs Broker............................................................ 11-12
Shipping Service Options for FedEx International DirectDistribution Surface Solutions ... 11-14
FedEx International DirectDistribution Surface Solutions List Rates ................................. 11-16
Downloading FedEx International DirectDistribution Surface Solutions List Rates ... 11-17
Downloading FedEx Ground Discounted Rates for FedEx International DirectDistribution
Surface Solutions Shipments............................................................................. 11-17
Creating a FedEx International DirectDistribution Surface Solutions Shipment ................ 11-17
Adding a Piece to a FedEx International DirectDistribution Surface Solutions Shipment.. 11-18
Deleting a FedEx International DirectDistribution Surface Solutions Package .......... 11-28
Confirming a FedEx International DirectDistribution Surface Solutions Shipment..... 11-29
Performing a FedEx International DirectDistribution Surface Solutions Open Ship End-ofDay Close .......................................................................................................... 11-30
Returning the CRN Count .......................................................................................... 11-30
Requesting FedEx International DirectDistribution Surface Solutions Rate/Route/Time-inTransit........................................................................................................................ 11-31
Requesting Shipment Route/Time-in-Transit Information.......................................... 11-31
Requesting Rate Quotes............................................................................................ 11-33
Requesting Delivery Time.......................................................................................... 11-37
Optional Commodity Fields for FedEx International DirectDistribution Surface Solutions
Master Shipment................................................................................................ 11-37
v 10.6.1
FedEx Ship Manager® Server Developer Guide
xi
Contents
FedEx International DirectDistribution Surface Solutions Labels ...................................... 11-38
FedEx International DirectDistribution Surface Solutions Label Formats .................. 11-38
FedEx International DirectDistribution Surface Solutions Reports .................................... 11-40
FedEx International DirectDistribution Surface Solutions Consolidated Commercial Invoice
11-40
FedEx Ground Pickup Manifest for FedEx International DirectDistribution Surface
Solutions ............................................................................................................ 11-41
FedEx Express Courier Report for FedEx International DirectDistribution Surface Solutions
11-42
FedEx International DirectDistribution Surface Solutions Error Messages ....................... 11-42
CHAPTER 12: CODING TRANSACTIONS FOR FEDEX INTERNATIONAL
PRIORITY DIRECTDISTRIBUTION
About FedEx International Priority DirectDistribution (IPD/IED/IDF) ................................... 12-1
IPD/IED/IDF Package and Shipment Restrictions ....................................................... 12-2
IPD/IED/IDF Package Size and Weight Restrictions ................................................... 12-2
Getting Started with IPD/IED/IDF ................................................................................ 12-3
Configuring IPD/IED/IDF ..................................................................................................... 12-3
IPD/IDF Settings Tab and Importer of Record............................................................. 12-5
IPD/IDF Report Configuration...................................................................................... 12-8
About FedEx IPD/IED/IDF Transactions ............................................................................. 12-8
Transaction Rules and Restrictions ............................................................................. 12-9
IPD/IED vs IDF .................................................................................................................. 12-10
IPD/IED/IDF Transaction Fields ........................................................................................ 12-11
IPD/IED/IDF International Air Waybill Fields.............................................................. 12-11
International Economy DirectDistribution Service Fields ........................................... 12-13
International Priority DirectDistribution Freight .......................................................... 12-14
Shipping Service Options for IPD/IED/IDF ........................................................................ 12-14
Hold at Location......................................................................................................... 12-14
Dry Ice ....................................................................................................................... 12-14
Dangerous Goods...................................................................................................... 12-15
Saturday Delivery and Pickup.................................................................................... 12-15
Concurrent Shipments and Future Day Processing .................................................. 12-15
Saturday Pickup for FedEx International Priority DirectDistribution........................... 12-15
Saturday Delivery for FedEx International Priority DirectDistribution and Freight ..... 12-16
FedEx International Priority DirectDistribution and FedEx International Priority
DirectDistribution Freight Shipping Options....................................................... 12-16
IPD/IED/IDF Transaction WorkFlow .................................................................................. 12-17
Transaction Shipping Methods for IPD/IED/IDF ........................................................ 12-18
Nested Occurrence Fields for IPD/IDF Transactions................................................. 12-20
FedEx IPD/IDF 020/120 Global Shipping Transaction Scenarios ..................................... 12-21
Scenario 1 - Single ADD Piece and Single Shot Open Ship ..................................... 12-21
Scenario 2 - Multiple Single Shot............................................................................... 12-21
Scenario 3 - One Single Shot .................................................................................... 12-22
Creating a IPD/IDF/IED Shipment Transaction ................................................................. 12-22
Master Air Waybill...................................................................................................... 12-31
xii
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Contents
Adding a Package with a Child Reference Number...................................................
Confirming the Shipment ...........................................................................................
Rounding Up Weights on IPD/IDF Shipments ...........................................................
Package Level Commodity Fields Affected by Field 4574.........................................
Deleting an IPD/IED/IDF Customer Reference Number ............................................
Deleting an IPD/IED/IDF Shipment............................................................................
Specifying IPD/IDF/IED Shipment Service Type ...............................................................
FedEx Customer Reference Number Report.....................................................................
Setting the Number of CRN per Page........................................................................
CRN-Level Country Weight Restriction Check ..........................................................
IPD/IDF Customs Packing List - Tax ID/Vat# Header................................................
IPD/IDF/IED Requests for Consolidated Commodity Information for EEI Filing ........
IPD/IED/IDF Transaction Samples ....................................................................................
12-33
12-47
12-51
12-52
12-54
12-56
12-57
12-59
12-59
12-60
12-61
12-61
12-62
CHAPTER 13: GENERATING FEDEX SHIPPING FORMS AND REPORTS
FedEx Shipping Reports...................................................................................................... 13-1
List of Available FedEx Shipping Reports.................................................................... 13-1
Common Reports......................................................................................................... 13-4
Custom Reports................................................................................................................... 13-5
FedEx Express U.S. Domestic Shipment Reports............................................................... 13-5
Domestic Courier Report - FedEx Express.................................................................. 13-6
Domestic Shipment Report - FedEx Express .............................................................. 13-6
Domestic Invoice Report - FedEx Express .................................................................. 13-7
Domestic End-Of-Day TransOut Report - FedEx Express........................................... 13-7
Dangerous Goods Shipper’s Declaration Form (1421C) - FedEx Express.................. 13-7
Domestic Shipping History - FedEx Express ............................................................... 13-7
International Reports ........................................................................................................... 13-7
FedEx Ground Pickup Manifest ................................................................................... 13-8
Multi-weight Package Detail - FedEx Ground .............................................................. 13-8
Multi-weight Shipment Detail by Postal Code - FedEx Ground ................................... 13-8
Multi-weight Shipment Detail by Zone - FedEx Ground............................................... 13-9
Multi-weight Shipment C.O.D. Detail - FedEx Ground................................................. 13-9
Multi-weight Shipment Declared Value Detail - FedEx Ground ................................... 13-9
OP-950 HazMat Certification Report ......................................................................... 13-10
FedEx Ground Commercial Invoice ........................................................................... 13-13
FedEx Ground Collect on Delivery Report................................................................. 13-13
Destination Control Statements ................................................................................. 13-13
New FedEx SmartPost Reports......................................................................................... 13-14
Detail Report.............................................................................................................. 13-15
Manifest Report.......................................................................................................... 13-15
Returns Report........................................................................................................... 13-15
FedEx Express International Reports ................................................................................ 13-17
International Courier Report - FedEx Express ........................................................... 13-17
International Invoice Report - FedEx Express ........................................................... 13-17
International End-Of-Day TransOut Report - FedEx Express.................................... 13-18
International Commercial Invoice (CI) - FedEx Express ............................................ 13-18
v 10.6.1
FedEx Ship Manager® Server Developer Guide
xiii
Contents
International Visa Manifest Report - FedEx Express ................................................. 13-18
International Dangerous Goods (1421C) - FedEx Express ....................................... 13-19
International Pro Forma Invoice................................................................................. 13-19
International Shipment Report - FedEx Express ....................................................... 13-19
International Shipping History - FedEx Express ........................................................ 13-19
#IPD/IED/IDF Reports ............................................................................................... 13-20
Certificate of Origin - FedEx Express and FedEx Ground ......................................... 13-20
FedEx International DirectDistribution Surface Solutions Reports .................................... 13-20
FedEx International DirectDistribution Surface Solutions Consolidated Commercial Invoice
13-21
FedEx International DirectDistribution Surface Solutions Commercial Invoices........ 13-22
CHAPTER 14: FEDEX SHIP MANAGER SERVER UTILITIES
About FedEx Ship Manager Server Utilities ........................................................................ 14-1
Custom Label Generator Utility ........................................................................................... 14-2
Demand Download Utility .................................................................................................... 14-3
GoToAssist Utility ................................................................................................................ 14-5
Ground Rates and Discounts Utility..................................................................................... 14-5
Opening the Ground Rates and Discounts Utility ........................................................ 14-6
Adding FedEx Ground Customer Profiles.................................................................... 14-7
Adding Base Discounts................................................................................................ 14-9
Adding Base Rates...................................................................................................... 14-9
Adding Extra Services / Discounted Accessorials ..................................................... 14-11
Adding Matrix Discounts ............................................................................................ 14-14
Adding Minimum Charges ......................................................................................... 14-15
Adding FedEx Ground Multi-weight Discounts .......................................................... 14-16
Adding Oversize Exceptions...................................................................................... 14-17
Label Reprint Utility ........................................................................................................... 14-18
Meter Registration Utility ................................................................................................... 14-20
Report Viewer Utility .......................................................................................................... 14-24
Ship Manager Server Console .......................................................................................... 14-32
xiv
FedEx Ship Manager® Server Developer Guide
v 10.6.1
List of Figures
Chapter 1: Introduction to FedEx Ship Manager Server
Figure 1-1: Communication Network Interface ..............................................1-3
Chapter 2: About FedEx Ship Manager Server Transactions
Figure 2-1: Key Elements of Transaction Information.................................. 2-16
Figure 2-2: Field Information for Key Elements ........................................... 2-17
Figure 2-3: Shipment plus Field Information for Key Elements.................... 2-18
Figure 2-4: Transaction String Elements ..................................................... 2-19
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Figure 3-1: OP-900 Form............................................................................... 3-2
Figure 3-2: OP-900B Form ............................................................................ 3-3
Figure 3-3: OP-900LL Form - Front (8-1/2" x 11") ......................................... 3-4
Figure 3-4: OP-900LL Form - Back (8-1/2" x 11").......................................... 3-5
Figure 3-5: FedEx Hazardous Materials OP-900LG Form........................... 3-10
Figure 3-6: FedEx Shipper’s Declaration for Dangerous Goods Form (FedEx
1421C Form) ......................................................................................... 3-12
Figure 3-7: FedEx Shipper’s Declaration for Dangerous Goods Form (FedEx
LZR DG DEC FORM)............................................................................ 3-13
Figure 3-8: FedEx SmartPost Enabled Doc-Tab Settings ........................... 3-35
Figure 3-9: FedEx Express U.S. Label ........................................................ 3-51
Figure 3-10: FedEx Home Delivery Label.................................................... 3-52
Figure 3-11: FedEx Ground HazMat Label .................................................. 3-53
Figure 3-12: FedEx SmartPost Label........................................................... 3-54
Figure 3-13: FedEx Express International DirectDistribution Label ............. 3-55
Figure 3-14: FedEx Ground International DirectDistribution Label .............. 3-56
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Figure 4-1: Open Ship Process Workflow...................................................... 4-3
Chapter 5: Coding Transactions for FedEx Express U.S. Service
v 10.6.1
FedEx Ship Manager® Server Developer Guide
xv
List of Figures
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Figure 6-1: FedEx Ground ORM-D Label ....................................................6-32
Figure 6-2: FedEx Ground Tracking Number...............................................6-35
Chapter 7: Coding Transactions for FedEx SmartPost
Figure 7-1: SmartPost Settings Tab with SmartPost Returns Enabled Checkbox
7-4
Figure 7-2: Add SmartPost Returns Dialog Box.............................................7-5
Figure 7-3: Tracking Numbers Tab ................................................................7-8
Figure 7-4: Handling Charges Dialog for FedEx SmartPost Service Type ..7-10
Figure 7-5: Demand Download Utility ..........................................................7-13
Figure 7-6: FedEx SmartPost Doc-Tab Settings Tab...................................7-15
Figure 7-7: FedEx SmartPost Report Settings Tab......................................7-16
Figure 7-8: FedEx SmartPost Detail Report Screen ....................................7-17
Figure 7-9: FedEx SmartPost Detailed Report, Page 1 of 2 ........................7-19
Figure 7-10: FedEx SmartPost Detail Report, Page 2 of 2 ..........................7-20
Figure 7-11: FedEx SmartPost Manifest Report ..........................................7-22
Figure 7-12: FedEx SmartPost Returns Report ...........................................7-23
Figure 7-13: FedEx SmartPost Media Service with USPS Delivery Confirmation
Label......................................................................................................7-29
Figure 7-14: FedEx SmartPost Integrated Label, Sample 1 ........................7-30
Figure 7-15: FedEx SmartPost Integrated Label, Sample 2 ........................7-31
Figure 7-16: FedEx SmartPost Label Stamp ...............................................7-32
Figure 7-17: Delivery Confirmation Number from Label...............................7-32
Chapter 8: Coding Transactions for FedEx International Shipping
Chapter 9: Coding Transactions for FedEx Express International
Services
Chapter 10: Coding Transactions for FedEx International Ground
Services
Figure 10-1: NAFTA Certificate of Origin Sample......................................10-27
Figure 10-2: NAFTA Statement for U.S. Goods Valued Under $1600 CAD ..1029
Figure 10-3: NAFTA Statement..................................................................10-29
xvi
FedEx Ship Manager® Server Developer Guide
v 10.6.1
List of Figures
Figure 10-4:General Agency Agreement Form..........................................10-31
Chapter 11: Coding Transactions for FedEx International DirectDistribution Surface Solutions
Figure 11-1: FedEx Express Priority Overnight - FedEx International DirectDistribution Surface Solutions Label Sample ........................................... 11-39
Chapter 12: Coding Transactions for FedEx International Priority
DirectDistribution
Figure 12-1: IPD/IED/IDF Settings Tab........................................................ 12-4
Figure 12-2. Clearance Facility Address - Auto Populated .......................... 12-6
Figure 12-3. Importer or Record Information ............................................... 12-7
Figure 12-4: IPD/IDF/IED Transaction Workflow ....................................... 12-17
Figure 12-5: Example IPD Transaction Fields ........................................... 12-58
Figure 12-6: Example IED Transaction Fields ........................................... 12-58
Figure 12-7: Example IED Transaction Fields ........................................... 12-58
Figure 12-8: Example Single Point of Clearance Field .............................. 12-59
Chapter 13: Generating FedEx Shipping Forms and Reports
Figure 13-1: New HazMat Certification Report ..........................................13-11
Figure 13-2: Report Settings Screen - FedEx SmartPost Reports Options ... 1316
Chapter 14: FedEx Ship Manager Server Utilities
Figure 14-1: Custom Label Generator Utility ............................................... 14-2
Figure 14-2: FedEx Demand Download Utility............................................. 14-4
Figure 14-3: Rates and Discounts Window.................................................. 14-6
Figure 14-4: Base Discount Window............................................................ 14-7
Figure 14-5: Ground Customer Profile Window ........................................... 14-8
Figure 14-6: Rate and Discounts Window ................................................. 14-10
Figure 14-7: Base Rate Window ................................................................ 14-11
Figure 14-8: Extra Services / Discounted Accessorials Window ............... 14-12
Figure 14-9: More Accessorials ................................................................. 14-13
Figure 14-10: Matrix Discount Window ...................................................... 14-14
Figure 14-11: Minimum Charge Window ................................................... 14-15
Figure 14-12: MultiWeight Window ............................................................ 14-16
Figure 14-13: Oversize Exceptions Window .............................................. 14-17
v 10.6.1
FedEx Ship Manager® Server Developer Guide
xvii
List of Figures
Figure 14-14: Reprint Label Utility Window................................................14-19
Figure 14-15: FedEx Meter Registration Utility Dialog...............................14-21
Figure 14-16: FedEx Meter Registration Utility ..........................................14-22
Figure 14-17: FedEx Meter Registration Status.........................................14-23
Figure 14-18: Report Viewer Utility ............................................................14-25
Figure 14-19: Report Viewer Navigation Tree View...................................14-26
Figure 14-20: FedEx Ground Manifest.......................................................14-28
Figure 14-21: FedEx Express Commercial Invoice....................................14-30
Figure 14-22: Report Viewing Controls......................................................14-31
Figure 14-23: Report Print Setup ...............................................................14-32
Figure 14-24: Ship Manager Console ........................................................14-33
xviii
FedEx Ship Manager® Server Developer Guide
v 10.6.1
List of Tables
Chapter 1: Introduction to FedEx Ship Manager Server
Chapter 2: About FedEx Ship Manager Server Transactions
Table 2-1: BEGIN, DATA and END Field Elements in Example Transaction ..220
Table 2-2: Field 0 Begins Transaction Strings ............................................. 2-21
Table 2-3: Field 99 Ends Transaction Strings.............................................. 2-21
Table 2-4: Transaction Coding Table Example............................................2-29
Table 2-5: Batch File Processing................................................................. 2-34
Table 2-6: FedEx Shipping Services............................................................ 2-36
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-1: Fields for Printing Information on the Ground OP-900/OP-900B
Forms ...................................................................................................... 3-2
Table 3-2: Fields for Printing HazMat Class on the OP-900 Form................. 3-3
Table 3-3: OP-900 Form First Line Data........................................................ 3-3
Table 3-4: OP-900 Form Second Line Data .................................................. 3-4
Table 3-5: OP-900 Laser Form Fields ........................................................... 3-6
Table 3-6: Fields for Laser Format for Hazardous Materials OP-900 Form... 3-6
Table 3-7: HazMat Class and Subsidiary Risk Fields: Example 1 ................. 3-8
Table 3-8: HazMat Class and Subsidiary Risk Fields: Example 2 ................. 3-9
Table 3-9: HazMat Class and Subsidiary Risk Fields: Example 3 ................. 3-9
Table 3-10. Commodity Mixtures for HazMat Packages.............................. 3-10
Table 3-11: FSM Server Label Types.......................................................... 3-15
Table 3-12: Fields for Identifying Thermal Printers ...................................... 3-18
Table 3-13: Fields for Identifying Laser Printers .......................................... 3-19
Table 3-14: Air Waybill Label Indicator Field ............................................... 3-21
Table 3-15: Fields for Printing Thermal Air Waybill Labels to File ............... 3-21
Table 3-16: Fields Required to Defer Label Printing.................................... 3-25
Table 3-17: Fields for Reprinting a Label for a Multiple-Piece Shipment..... 3-26
Table 3-18: Doc-Tab Fields ......................................................................... 3-27
Table 3-19: Reference Fields for FedEx Ground C.O.D. Return Labels...... 3-36
Table 3-20: Reference Fields for FedEx Ground Labels ............................. 3-38
v 10.6.1
FedEx Ship Manager® Server Developer Guide
xix
List of Tables
Table 3-21: Reference Fields for FedEx Express Reference Information....3-39
Table 3-22: Reference Fields for FedEx SmartPost Labels.........................3-42
Table 3-23: Label Format Value/Printer Type Indicator ...............................3-44
Table 3-24: Fields Used to Customize Thermal Labels ...............................3-45
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-1: Open Ship Creation ......................................................................4-3
Table 4-2: Open Ship Flag Positions for Field 541 ........................................4-4
Table 4-3: Fields for Open Ship Pre-Ship Validation .....................................4-6
Table 4-4: CREATE Open Ship Shipment Fields...........................................4-7
Table 4-5: Required Fields to CREATE an Open Ship Shipment..................4-8
Table 4-6: Open Ship Print-As-You-Go (PAYG) Fields ...............................4-10
Table 4-7: Required Fields for Open Ship ROUTE or Time-in-Transit Information.........................................................................................................4-11
Table 4-8: Required Fields to RATE an Open Ship Shipment.....................4-14
Table 4-9: Required Fields to ADD Package to Open Ship Shipment.........4-15
Table 4-10: Package Weight Field - Required before CONFIRM ................4-18
Table 4-11: Package Level Fields for ADD Package to Open Ship Shipment.419
Table 4-12: Returned Field for Add Piece to Open Ship Shipment .............4-25
Table 4-13: EDIT Piece Open Ship Fields ...................................................4-25
Table 4-14: Required Fields to EDIT an Open Ship Package .....................4-26
Table 4-15: Required Fields to EDIT an Open Ship Shipment ....................4-28
Table 4-16: Delete Piece Before CONFIRM ................................................4-29
Table 4-17: To Delete Piece After CONFIRM..............................................4-30
Table 4-18: Required Fields to DELETE an Open Ship Shipment ..............4-30
Table 4-19: DELETE Open Ship Shipment Fields .......................................4-32
Table 4-20: Fields for Deleting an Open Ship Shipment..............................4-32
Table 4-21: CONFIRM Piece and Print Label Fields ...................................4-35
Table 4-22: Required Fields to CONFIRM a Piece in a Shipment...............4-36
Table 4-23: Required Fields to CONFIRM an Open Ship Shipment............4-37
Table 4-24: Print-As-You-Go Package Association .....................................4-40
Table 4-25: Open Ship Print-As-You-Go (PAYG) Fields .............................4-41
Table 4-26: Open Ship Print-As-You-Go Transaction Summary .................4-43
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-1: Fields Required for FedEx Express U.S. Shipments ....................5-5
xx
FedEx Ship Manager® Server Developer Guide
v 10.6.1
List of Tables
Table 5-2: Fields for FedEx Express U.S. C.O.D......................................... 5-11
Table 5-3: Delivery Signature Field 2399..................................................... 5-15
Table 5-4: Delivery Signature Options for Special Services ........................ 5-16
Table 5-5: Future Day Ship Date Field ........................................................ 5-17
Table 5-6: Fields for FedEx Express Hold at Location Service ................... 5-18
Table 5-7: FedEx Express Saturday Pickup and Delivery Fields ................ 5-20
Table 5-8: Inside Delivery Flag Field ........................................................... 5-21
Table 5-9: Required Fields for Dangerous Goods in Excepted Quantities .. 5-23
Table 5-10: Allowed Values for Fields 1331 and 1669 ................................ 5-24
Table 5-11: Dangerous Goods Technical Name Field................................. 5-24
Table 5-12: Service Options for Dangerous Goods .....................................5-25
Table 5-13: Fields Required for FedEx Express Dangerous Goods Shipment526
Table 5-14: Fields for Adding Dangerous Goods to a FedEx Express Shipment
5-27
Table 5-15: EPRRQ Required Fields for FedEx Express Dangerous Goods
ORM-D Packages ................................................................................. 5-31
Table 5-16: Field 1331 - Code for Excepted Package Radioactive Reportable
Quantity ................................................................................................. 5-32
Table 5-17: EPRRQ Required Fields for FedEx Express Dangerous Goods
ORM-D Packages ................................................................................. 5-33
Table 5-18 Required 020 Transaction Fields for EPRRQ............................ 5-34
Table 5-19: EPRRQ Optional 020 Transaction Fields ................................. 5-37
Table 5-20: Dry Ice Surcharge and List Dry Ice Surcharge Fields .............. 5-40
Table 5-21: Ways to Request Dry Ice Surcharge ........................................ 5-41
Table 5-22: FedEx Express Domestic Billed Weight ................................... 5-42
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-1: FedEx Ground Fields.................................................................... 6-4
Table 6-2: FedEx Oversize Rules .................................................................. 6-5
Table 6-3: FedEx Ground Indicator for Oversized Packages ........................ 6-6
Table 6-4: Non-Standard Container Fields for FedEx Ground....................... 6-7
Table 6-5: Additional Reference Information Fields.......................................6-8
Table 6-6: FedEx Home Delivery Fields ...................................................... 6-10
Table 6-7: Service Type for Home Delivery ................................................. 6-12
Table 6-8: Fields for FedEx Ground U.S. C.O.D.......................................... 6-13
Table 6-9: FedEx Ground C.O.D. and E.C.O.D. Field ................................. 6-17
Table 6-10: Future Day Ship Date Field ...................................................... 6-19
v 10.6.1
FedEx Ship Manager® Server Developer Guide
xxi
List of Tables
Table 6-11: Home Delivery Saturday Pickup and Delivery Fields................6-20
Table 6-12: Custom Transit Time Field........................................................6-20
Table 6-13: Ground Multi-weight Delivery Details Report Field ...................6-22
Table 6-14: HazMat Package Hierarchy and Allowable Commodity Mixes .6-23
Table 6-15: HazMat Shipping Fields for Ground..........................................6-23
Table 6-16: Ground ORM-D Fields ..............................................................6-30
Table 6-17: Modified Fields for Dry Ice ........................................................6-33
Table 6-18: New Fields for Small Quantity Exception..................................6-34
Table 6-19: New Fields for Non-Hazardous Lithium Batteries.....................6-35
Table 6-20: Ground Tracking Number Settings ...........................................6-37
Table 6-21: FedEx Ground End-of-Day Reports..........................................6-38
Table 6-22: Ground End-of-Day Report Name Formats ..............................6-38
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-1: FedEx SmartPost Service Types..................................................7-2
Table 7-2: FedEx SmartPost Settings Fields .................................................7-6
Table 7-3: Handling Charges Fields.............................................................7-11
Table 7-4: APO, FPO, and DPO Military State Codes.................................7-24
Table 7-5: FedEx SmartPost Rate Quote Reply Fields................................7-33
Table 7-6: End-of-Day Close Fields for FedEx SmartPost Shipment ..........7-34
Table 7-7: E-Mail Notification Fields for FedEx SmartPost Shipments ........7-35
Table 7-8: Future Day Ship Date Field.........................................................7-44
Table 7-9: Fields (Required and Optional) for FedEx SmartPost 020 Transaction
7-45
Table 7-10: FedEx SmartPost Print Returns Label Fields ...........................7-59
Table 7-11: FedEx SmartPost E-Mail Returns Label Fields.........................7-77
Table 7-12: FedEx SmartPost Open Ship Flag Fields .................................7-89
Table 7-13: Parcel Select Transactions and Fields......................................7-91
Chapter 8: Coding Transactions for FedEx International Shipping
Table 8-1: FedEx International Shipping Services At-A-Glance ....................8-1
Table 8-2: FedEx International Shipping Services Special Options...............8-2
Table 8-3: FedEx International DirectDistribution Surface Solutions - FedEx Express and
FedEx Ground U.S. Services ..................................................................8-4
Table 8-4: FedEx International Direct-Distribution Services At-A-Glance......8-4
Table 8-5: Guidelines for FedEx Express International Shipment Preparation 87
xxii
FedEx Ship Manager® Server Developer Guide
v 10.6.1
List of Tables
Table 8-6: Guidelines for FedEx International Ground Shipment Preparation.88
Table 8-7: Basic Fields for International Shipping Documents .................... 8-11
Table 8-8: List of Information to Include on Commercial Invoice ................. 8-13
Chapter 9: Coding Transactions for FedEx Express International
Services
Table 9-1: Delivery Signature Options for U.S. and Canada ......................... 9-3
Table 9-2: Fields for FedEx Saturday Service ............................................... 9-3
Table 9-3: FedEx Express Cut Flowers Flag ................................................. 9-5
Table 9-4: Additional Required Fields for FedEx Express International Shipments....................................................................................................... 9-6
Table 9-5: Third Party Consignee Fields ..................................................... 9-10
Table 9-6: 049 Pre-Shipment Document Upload Request Fields ................ 9-11
Table 9-7: 049 Pre-Shipment Document Upload Reply Fields .................... 9-14
Table 9-8: 020 Global Ship Transaction Request Fields for Electronic Trade
Documents Upload and Shipping (in Addition to Basic 020 Global Ship
Transaction Fields)................................................................................ 9-17
Table 9-9: Available FedEx Express International List Rates ...................... 9-20
Table 9-10: Fields for Returning Express International List Rates............... 9-21
Table 9-11: Fields to Return Shipping Costs ............................................... 9-23
Table 9-12: Fields for FedEx Express U.S. Shipment Charges................... 9-23
Table 9-13: List Rates and Surcharge Transaction Scenarios .................... 9-24
Chapter 10: Coding Transactions for FedEx International Ground
Services
Table 10-1: Comparative Overview of International Ground Distribution and International Ground DirectDistribution .................................................... 10-2
Table 10-2: IGD Transaction Fields for 020 Global Ship Request............... 10-3
Table 10-3: IGD Transaction Fields Returned in 120 Global Ship Reply..... 10-3
Table 10-4: FedEx International Ground Broker Options............................. 10-6
Table 10-1: Basic Fields for International Ground Shipments ..................... 10-8
Table 10-2: Additional Fields for International Ground Shipments .............. 10-9
Table 10-3: 049 Pre-Shipment Document Upload Request Fields ............ 10-11
Table 10-4: 049 Pre-Shipment Document Upload Reply Fields ................10-13
Table 10-5: 020 Global Ship Transaction Request Fields for Electronic Trade
Documents Upload and Shipping (in Addition to Basic 020 Global Ship
Transaction Fields).............................................................................. 10-16
v 10.6.1
FedEx Ship Manager® Server Developer Guide
xxiii
List of Tables
Table 10-6: International Ground Distribution Fields..................................10-18
Table 10-7: Fields Returned for International Ground Distribution Transactions
10-19
Table 10-8: Canada Signature Options......................................................10-20
Table 10-9: Signature Option Fields for FedEx International Ground CA to U.S.
10-20
Table 10-10: Duty and Tax Payment Fields for FedEx Ground International 1022
Table 10-11: NAFTA Certificate of Origin Fields........................................10-23
Table 10-12: NAFTA Certificate of Origin ..................................................10-26
Chapter 11: Coding Transactions for FedEx International DirectDistribution Surface Solutions
Table 11-1: FedEx International DirectDistribution Surface Solutions Open Ship
Shipping Workflow.................................................................................11-2
Table 11-2: Required Fields for FedEx International DirectDistribution Surface
Solutions Shipping.................................................................................11-3
Table 11-3: Fields for non-FTN Customs Broker .......................................11-12
Table 11-4: FedEx Express and FedEx Ground Services Allowed by Package
Type.....................................................................................................11-14
Table 11-5: FedEx Express Special Services Allowed by Service Type....11-15
Table 11-6: FedEx Express Special Services Allowed by Service Type....11-15
Table 11-7: FedEx Ground Special Services Allowed by Service Type.....11-16
Table 11-8: Fields for Returning FedEx International DirectDistribution Surface
Solutions List Rates.............................................................................11-16
Table 11-9: Fields to CREATE a FedEx International DirectDistribution Surface
Solutions Shipment..............................................................................11-18
Table 11-10: Fields for Adding a Package to FedEx International DirectDistribution Surface Solutions Shipment .........................................................11-19
Table 11-11: Fields to DELETE Package from FedEx International DirectDistribution Surface Solutions Shipment .....................................................11-28
Table 11-12: Fields to CONFIRM a FedEx International DirectDistribution Surface Solutions Shipment......................................................................11-29
Table 11-13: Fields to Request ROUTE and Time-In-Transit ....................11-31
Table 11-14: Fields to Request Rate Quotes for FedEx International DirectDistribution Surface Solutions Shipments.................................................11-33
Table 11-15: Fields for Requesting Delivery Time.....................................11-37
Table 11-16 Optional Commodity Fields for FedEx International DirectDistribution Surface Solutions Shipment .........................................................11-37
Table 11-17: FedEx International DirectDistribution Surface Solution Labels11-
xxiv
FedEx Ship Manager® Server Developer Guide
v 10.6.1
List of Tables
38
Table 11-18: Error Messages for FedEx International DirectDistribution Surface
Solutions Transactions ........................................................................ 11-42
Chapter 12: Coding Transactions for FedEx International Priority
DirectDistribution
Table 12-1: IPD/IF Settings.......................................................................... 12-5
Table 12-2: IPD/IED vs. IDF ...................................................................... 12-10
Table 12-3: Fields with No Entry Values in CREATE MAWB .................... 12-11
Table 12-4: Optional Fields for Create IPD/IED/IDF Shipment with WAWB
Transaction.......................................................................................... 12-12
Table 12-5: International Economy DirectDistribution Service Transactions . 1213
Table 12-6: Saturday Pickup Flag Field..................................................... 12-15
Table 12-7: Saturday Delivery Flag Field................................................... 12-16
Table 12-8: Open Ship Transaction Types ................................................ 12-17
Table 12-9: Open Ship Process Workflow Details ..................................... 12-18
Table 12-10: IPD/IDF MPS Commodity Set Indicator Field ....................... 12-20
Table 12-11: CREATE a FedEx IPD/IED/IDF MAWB................................ 12-23
Table 12-12: Fields with No Entry Values in CREATE MAWB .................. 12-32
Table 12-13: Adding a Package with a Child Reference Number.............. 12-33
Table 12-14: Confirming the Shipment ...................................................... 12-47
Table 12-15: IPD/IDF Shipment Weights................................................... 12-51
Table 12-16: International Priority Direct Distribution Service Transactions.. 1252
Table 12-17: Fields to DELETE CRN in IPD/IED/IDF Shipment................12-54
Table 12-18: Fields to DELETE IPD/IED/IDF Shipment ............................ 12-56
Table 12-19: Field 2713 Number of CRNs on Report Page ...................... 12-60
Chapter 13: Generating FedEx Shipping Forms and Reports
Table 13-1: FedEx Domestic Reports.......................................................... 13-1
Table 13-2: FedEx International Reports..................................................... 13-2
Table 13-3: FedEx Ground Reports............................................................. 13-2
Table 13-4: FedEx Distributor (IDP/IDF) Reports ........................................ 13-3
Table 13-5: FedEx International DirectDistribution Surface Solutions Reports ..
13-3
Table 13-6: FedEx Dangerous Goods Reports............................................13-4
Table 13-7: FedEx SmartPost Reports ........................................................ 13-4
v 10.6.1
FedEx Ship Manager® Server Developer Guide
xxv
List of Tables
Table 13-8: Required Fields To Print HazMat OP-900LL Form.................13-12
Table 13-9: Fields for Printing Commerce Destination Control Statement 13-14
Chapter 14: FedEx Ship Manager Server Utilities
Table 14-1: At-A-Glance FedEx Ship Manager Server Utilities ...................14-1
Table 14-2: Package Size Criteria ...............................................................14-9
Table 14-3: Reprinting Labels....................................................................14-20
xxvi
FedEx Ship Manager® Server Developer Guide
v 10.6.1
ABOUT THIS DOCUMENT
This guide introduces FedEx Ship Manager® Server (FSMS) transactions and how to use them. It provides the detailed information you
need to understand, code and develop transactions for your business shipping needs and integrated solution applications. Tables of fields
and field properties are shown for each FedEx service and shipping function. The FSMS shipping process and methodoligies are also
explained. Each section of this guide includes a description of the business logic that supports valid field selection and coding. Use this
guide to understand FSMS transaction fundamentals and the shipping rules to which the transactions adhere. Use the detailed field property
information to determine which fields are valid for your transaction function and whether you have a complete set of fields for any single
transaction per your business requirements.
Organization
The FedEx Ship Manager® Server Developer Guide contains introductory chapters about the FSMS software installed on your local client
hardware and describes the fundamentals of creating FSMS transaction strings. You’ll find basic information about labels and including
fields that let you choose when you want to print them also. In addition to these topics, the guide provides both high-level and detailed field
information for developing Open Ship and other FSMS transactional shipping processes.
The remaining chapters describe FSMS transactions based on the FedEx service options you may want to choose to ship your packages
and commodities. They are organized as follows:
• FedEx Express® U.S. Service - see Chapter 5: Coding Transactions for FedEx Express U.S. Service
• FedEx Ground® U.S. Service - see Chapter 6: Coding Transactions for FedEx Ground U.S. Services
• FedEx SmartPost® - see Chapter 7: Coding Transactions for FedEx SmartPost
• FedEx International Service - see Chapter 8: Coding Transactions for FedEx International Shipping
• FedEx Express International Service - see Chapter 9: Coding Transactions for FedEx Express International Services
• FedEx International Ground® Service - see Chapter 10: Coding Transactions for FedEx International Ground Services
• FedEx® International DirectDistribution Surface Solutions, formerly known as FedEx® Transborder Distribution - see Chapter 11: Coding
Transactions for FedEx International DirectDistribution Surface Solutions
• FedEx International Priority DirectDistribution Freight® - see Chapter 12: Coding Transactions for FedEx International Priority
DirectDistribution
• FedEx International Economy DirectDistribution℠ Service - see Chapter 12: Coding Transactions for FedEx International Priority
DirectDistribution
• Information about tracking packages and generating reports using FSMS is included in Chapter 13: Generating FedEx Shipping Forms
and Reports.
Audience
The audience for this guide is a developer, software programmer, application architect or any user who wants to understand how to write
transaction code using FSMS to implement solutions that support the shipping needs of their company’s business operations.
Conventions
This guide uses the following conventions in the text.
• Information you need to enter in a field or transaction is formatted in bold.
• Sample transaction code is formatted in Courier New.
• Important notices begin with the word “Note:.”
v 10.6.1
FedEx Ship Manager® Server Developer Guide
xxvii
About this Document
• In task instructions, software user interface elements are shown in bold.
• Names of documents are shown in italics.
• Names of FSMS transactions are shown in italics, as for example, the 020/120 Global Ship Request/Reply Transaction.
• First occurrences of a term is italicized followed by a definition.
Resources
The following documents contain information related to this reference guide:
FedEx Ship Manager® Server Technical What’s New
FedEx Ship Manager® Server Services and Shipping Guide
FedEx Ship Manager® Server Installation and Configuration Guide
FedEx Ship Manager® Server Transaction Coding Reference Guide
FedEx Service Guide available at fedex.com.
Support
For FSMS technical support, call 1.877.339.2774 and state “FedEx Ship Manager Server” at the voice prompt.
Support hours are Monday through Friday, 7:00 a.m. to 9:00 p.m. CST, and Saturday, 9:00 a.m. to 3:00 p.m. CST.
For international customer support, call 1.800.GoFedEx 1.800.463.3339.
You can also contact FedEx on the web at fedex.com.
FedEx website
For the most recent information about FedEx, click fedex.com at the top of the FedEx Ship Manager screen to go to the FedEx website,
then click on any link to explore the most recent features and news from FedEx.
FedEx Service Guide
Within this guide, you may be asked to refer to the FedEx Service Guide at fedex.com for details about FedEx services, packaging, and
other information. To view or download the guide, go to fedex.com, enter FedEx Service Guide in the Search box at the top of the page, and
then click Go.
FedEx EEI Filing Options (U.S. only)
If you are a U.S. shipper and your US export shipments require EEI filing (Electronic Export Information, formerly known as Shipper's Export
Declaration, SED) refer to the FedEx EEI Filing Options Guide. To view or download the FedEx EEI Filing Options Guide, go to fedex.com,
enter FedEx EEI Filing Options Guide in the Search box at the top of the page, and then click Go. To order a printed copy, call
1.800.GoFedEx 1.800.463.3339.
xxviii
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Revision History
REVISION HISTORY
Error Description
Field 37. Should not have Field 421 in any
formula.
Release No.
Page No.
10.6.1
Description of Correction
Removed all references to “+Declared Value
Surcharge (Field 421)” from all formulas wherever Field 37 is used regardless if for FedEx Express or FedEx Ground.
Chapter 2. Added, “FedEx Ship Manager Server 10.6.1
can track packages by Delivery Confirmation
Number, which occurs after the shipment is confirmed to FedEx.” after first sentence in “10 Track Packages” section of workflow.
2-4
From 10.0.1 comments
Chapter 2. Changed 025/125 Rate Available Ser- 10.6.1
vices Request/Reply text.
2-10
You can use a single 025 Rate Available Services Request to receive the available FedEx services and corresponding rate quotes based on
your specified package, service and Meter- Account origin/destination information.
This transaction is available for FedEx Express
and FedEx Ground services with U.S., Canada
and Puerto Rico origins.
If Field 1274 (Service Type) and Field 1273
(Packaging Type) are not passed in the Request,
then all valid service/packaging combinations
for the origin/destination pair are returned in the
Reply. If only one of these fields is passed in the
Request, then the transaction functions as
though the field is not present and requests all
valid service/packaging combinations based on
the origin/destination pair.
By providing more information in the Request
transaction, you can receive a Reply transaction
with more specific information.
NOTE: The Shipper setting override fields are
not applicable on a rate quote. You cannot override the Meter-Account settings with field tags 4
thru 10.
Rate quote is a courtesy rate quote using the
Meter - Account origin/destination information.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
xxix
Revision History
Error Description
Release No.
Page No.
Description of Correction
Chapter 2. Add subsection under Rates, Rate
Quotes and List Rates
10.6.1
2-32
Earned Discount Pricing Program
The Earned Discounts Pricing Program awards
discounts to customers who meet predetermined
revenue levels and/or shipping criteria. You earn
additional discounts as you increase shipping activity or meet specific shipment characteristics.
To participate in the Earned Discounts Pricing
Program, contact your FedEx Account Executive. If you participate in the Earned Discounts
Pricing Program, all FSMS transactions with a
rate quote will return Field 1992 (Earned Discount Amount).
Earned Discounts will be returned in the 120 and
125 transactions for FSMS version 8.4 and higher.
Add Note about About FedEx Ship Manager
Server Open Ship Transactions
10.6.1
4-3
Added Note: IPD/IED/IDF in Open Ship processes differently, see Table: 12-9 step 1.
Field 2600. Value 3. Add note to all instances of 10.6.1
Field 2600.
4-9, 4-41, 5-14, 7-36
Added note, “For Open Ship Print-AsYou-Go (PAYG) shipments, you must CONFIRM
the shipment on the same date as CREATE, otherwise labels will have the incorrect ship date.”
From 10.0.1 comments
Field 2600. Value 4. Add phrase to end of last
sentence
10.6.1
4-9, 7-36
“...for FedEx SmartPost.”
From 10.0.1 comments
Chapter 4. Clarification of FedEx SmartPost
PAYG label information about CREATE and
CONFIRM needed.
Added note, “For Open Ship Print-As-You-Go
(PAYG) shipments, you must CONFIRM the
shipment on the same day as CREATE, otherwise labels will have the incorrect ship dates.”
10.6.1
4-8, 4-9, 4-13, 4-34, 4- Added to section, “Create an Open Ship Print36, 4-37, 4-43
As-You-Go Shipment” just before Table 4-6 (pg
4-8) and to Table 4-6 (pg 4-9), “ADD Piece Transaction” (pg 4-13), “CONFIRM Piece and Print Label” (pgs 4-33 and 4-34) “CONFIRM Piece and
Shipment Transactions” (pgs 4-35 and 4-36),
“Open Ship Print-As-You-Go” (pg 4-37), after
Table 4-26 (pg 4-43)
From 10.0.1 comments
Chapter 6. Added note, “FedEx Ground desig- 10.6.1
nates FedEx Home Delivery service as the carrier for residential deliveries under 70 pounds.
FedEx Ship Manager Server enforces this business rule.” to U.S. Ground intro chapter under
last bullet and to FedEx Ground U.S. section on
pg 6-2.
6-1, 6-2
From 10.0.1 comments
10.6.1
Chapter 7. Under “Configuring FedEx SmartPost, last sentence should end with “Pickup Carrier is designated USPS or FedEx Ground.”
Updated by replacing FedEx SmartPost with
USPS for this last part of the sentence.
7-2
Revised sentence.
xxx
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Revision History
Error Description
Release No.
Page No.
Description of Correction
Field 3063. GND UCC EAN bar code is returned 10.6.1
when doing Ground or Home Delivery. However,
FedEx SmartPost does not return that field, but
instead uses Field 2418 (Delivery Confirmation
Number). Best practice for generating the bar
code is a FedEx SmartPost custom label.
7-13, 7-53
From 10.0.1 comments
Chapter 7. Added, “...therefore, it is tracked and 10.6.1
delivered as a single shipment.” to “MultiplePiece Shipment” section under “Transaction
Methods for FedEx SmartPost” heading.
Added, “You cannot change from a FedEx
SmartPost carrier pickup to a Ground carrier
pickup without closing out all previous FedEx
SmartPost shipments, otherwise you will get a
close parameter error.” to end of the section,
“Transaction Rules for FedEx SmartPost.”
7-22
From 10.0.1 comments
Field 2417. Make sure all values are one digit on- 10.6.1
ly. The 1001 docs where inconsistent.
7-27, 7-52, 7-53.
Changed valid values to one digit entries.
Field 36 (Total Discount Amount) and Field 37
(Net Charge) required further explanation.
10.6.1.
7-33
Added note further explaining how all discounts
are calculated.
In section, “FedEx SmartPost Returns Service” 10.6.1
added note, “Field 2417 is also used in the 020
Request/Reply transactions.”
7-38
Added note
Chapter 7. Table 7-9 incorrectly stated that in a 10.6.1.
FedEx SmartPost Open Ship Transaction EDIT
piece may not be used.
7-95
Removed information regarding not being able to
EDIT a piece in a FedEx SmartPost Open Ship
Transaction.
Chapter 11. Change Field 176 from REQUIRED* 10.6.1.
to Optional. Change description.
11-6
Change Field from REQUIRED* to Optional. Remove text, “ * Required if destination is Canada.”
Chapter 11. Change Field 178 from REQUIRED* 10.6.1.
to Optional.
11-7
Change Field from REQUIRED* to Optional.
10.6.1
12-2
Sentence deleted.
Chapter 12. Remove “Restrictions for individual 10.6.1
package size, weight and commodity type are
the same as those for International Priority shipments. See IPD/IED/IDF Package Size and
Weight Restrictions on page 12-2 for details.
12-2
Sentence deleted.
Chapter 12. In the following sentence removed, 10.6.1
“/IED/IDF”
You can ship IPD/IED/IDF shipments to a single
point of clearance (SPOC) in the European
Union (EU).”
12-7
Words deleted.
Chapter 12. Remove, “In addition, countries
shipping to the European Union may also use
SPOC functionality with the IDF service.”
v 10.6.1
FedEx Ship Manager® Server Developer Guide
xxxi
Revision History
Error Description
Release No.
Page No.
Description of Correction
Chapter 12. Under “Customs and Shipping Doc- 10.6.1
uments,” updated text in first bullet to clarify that
one or more commodity totals more than $2,500
USD in the consolidated shipment. Also added
sentence, “You may file one AES filing for all
commodities in the shipment that must be reported to US CBP. You may also want to use the “EEI
Pre-determination Report” available from FXRS.
Check with the FedEx Regulator for details if you
have any questions on filing with AES” at the end
of the text.
12-7
Revised sentence and sentence added at the
end.
Chapter 12. Under “Customs and Shipping Doc- 10.6.1
uments,” add third bulleted item, “After receiving
your AES ITN, modify any information entered
during the CONFIRM transaction by setting Field
541 value 6 to Y and entering the ITN in Field
1358.”
12-7
Bulleted item added.
Chapter 12. Under “Exporter and Importer of Re- 10.6.1
cord”, add a third bullet listing clearance locations for countries with more than one.
12-8
Added third bullet with requested information.
10.6.1
12-9
Table added.
Chapter 12. Add: Note: This table applies to IPD/ 10.6.1.
IDF/IED only, for more information about OpenShip, see chapter 4.
12-17
Note added
Chapter 12. Table 12-11. In the note at the end of 10.6.1.
the description for Field 1358, removed “or CONFIRM.”
12-27
Removed “or CONFIRM” from note.
10.6.1
Chapter 12. Missing pages. After page 12-34
added, “Adding a Package with Child Reference
Number (CRN)” pages 261-265 from the FXRS
8.4.6. Developer Guide.
12-38
Section added.
Chapter 12. Missing pages. After the above add- 10.6.1
ed pages 269 - 270 “Confirming the Shipment.”
12-56
Section added.
10.6.1
Chapter 14. Table 14-2. Changed “Close” to
“Ship Time” in “International Shipment Detail Report.” Added note after table, “Ground ‘International Detail Report’ must be requested through
Field 2404.”
14-2
From 10.0.1 comments
10.6.1
Chapter 14. Table 14-3. Added “(international
shipments only)” to “Ground Shipment Detail Report” entry. Added note after table, “Ground ‘International Detail Report’ must be requested
through Field 2404.”
14-2
from 10.0.1 comments
Chapter 12. Add the IPD/IED vs IDF table from
FXRS 8.4.6, Developer Guide page 246, after
the Payment section on page 12-9.
xxxii
FedEx Ship Manager® Server Developer Guide
v 10.6.1
CHAPTER 1: INTRODUCTION TO FEDEX SHIP MANAGER
SERVER
FedEx Ship Manager® Server (FSMS) is the transaction processing interface to the FedEx services that ship your products and packages to
their final destinations every day. Run FSMS on a local client or integrate the application with your current shipping operations, bringing the
power of FedEx Services to your shipping station for local and worldwide deliveries.
This chapter provides an overview of FSMS features and describes the transaction model on which the application is based, and reviews
the requirements for system setup and network connections in the following sections:
• FedEx Ship Manager Server
• Overview
• Architecture
• FedEx Ship Manager Server Transaction Model
• Network and Internet Requirements
• Getting Started with FedEx Ship Manager Server
FedEx Ship Manager Server
FedEx Ship Manager Server is a transaction-based network shipping solution for high-volume shippers who want to integrate FedEx
shipping capabilities into their automated shipping operations. FedEx Ship Manager Server is best suited for technologically advanced
shippers who need speed and convenience to process, label, and ship extremely large numbers of packages and commodities each day.
The FSMS software allows full integration of FedEx shipping, tracking, rating and routing services with your existing business systems. The
application runs on a local client at your shipping site and requires a Microsoft Windows operating system and Internet connection.
Fast Dedicated Shipping Server
The advantage of FSMS-integrated applications is a fast, dedicated transaction-based connection to FedEx that provides reliable service for
getting shipments from origin to destination within time-critical requirements. It is a global solution, allowing you to ship from and to
anywhere FedEx shipping services are available. In addition, FedEx customers who integrate FSMS with their automated and warehouse
shipping software, enjoy the flexibility of being able to set up FSMS in ways that meet their individual business or compliance needs.
Adaptation to Change
FedEx Ship Manager Server gives you flexibility, which means you have the ability to change your FSMS shipping configuration as your
operational needs change. A single installation can support a large number of shipping origins, accounts and meters — if that is what you
need — regardless of location. You can also choose to dedicate individual and separate installations to multiple locations. It all depends on
what works best for you and how you want your FedEx shipping to integrate with your other business operations.
Implement Only What You Need
With FSMS, it is you, the FedEx shipper, who determines the required amount of resources (hardware and personnel) you need. Using
FedEx Ship Manager Server function-specific software modules, it is possible to develop, configure and activate a shipping solution that
effectively supports the day-to-day demands of your business and shipping needs. You implement only what you need.
FedEx Ship Manager Server is a free installation. Contact a FedEx support representative if you wish to expand your current FSMS
installation or want additional information.
See the FedEx Ship Manager® Server Services and Shipping Guide for more information about FSMS and integrated services from FedEx.
See the FedEx Service Guide for a comprehensive guide to all FedEx services.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
1-1
Chapter 1: Introduction to FedEx Ship Manager Server
Overview
To help you determine how best to integrate FedEx shipping with your current business, this Developer Guide describes how to create
integrated FedEx shipping solutions using the FSMS software and configured FedEx service modules. For example, it describes the
transactions that support FedEx Express U.S. shipping separately from those that support FedEx Ground® or FedEx Express® International
shipping. If your business ships primarily to Canada, you will find the transactions that support U.S.-Canada cross-border shipping services
located together in Chapter 11: Coding Transactions for FedEx International DirectDistribution Surface Solutions.
FedEx Shipping Rules
As you work with FSMS transactions, you will want to become more familiar with the FedEx shipping rules that govern each transaction.
These are different for each of the FedEx shipping services. Within each chapter you will find rules and guidelines for developing
transactions, as well as transaction tables that list the data fields required for the specific transaction described. Use these tables as
templates for coding your transactions.
Resources
For an overview of FedEx services and how to ship using FSMS, read the FedEx Ship Manager® Server Services and Shipping Guide. This
guide provides a summary of features and service details for each FedEx shipping service available through FSMS. At-A-Glance tables
assist you in quickly determining the best solution for your shipping requirements. Shipping rules and package restrictions described for
each service help you understand what you will need to consider before you begin to code.
Read this Developer Guide to learn about the different types of transactions you can code to implement FedEx services and how to
determine which fields are required for your specific transaction. For a detailed description of each field, see the FedEx Ship Manager®
Server Transaction Coding Reference Guide. Field descriptions include field properties and usage information for coding transactions.
The following sections of this chapter introduce you to the FSMS architecture and transaction processing model. They describe the
importance of a quality network connection to FedEx and provide a system overview to help you see the many different ways in which you
can implement FSMS as a flexible solution for your shipping.
Getting Assistance
Implementation of FSMS should be performed only by professional software developers, IT administrators and others with experience in
developing, staging and managing large enterprise network application systems. It should not be attempted by untrained end users. If you
need assistance, contact your FedEx account executive, customer integration consultant (CIC) or FedEx support.
Architecture
The FSMS architecture is an integrated solution designed to meet the unique shipping needs of small to medium and large enterprise
businesses. The architecture is flexible and can be configured to fit your specific operations setup. You, the shipper, decide how many
FSMS clients to install and whether to dedicate different printers for labels and reports. In all cases, make sure to precede any architectural
strategy you design with an in-depth study of your business practices and operations, shipping history, paper trail and compliance
requirements, physical shipping facilities and more.
The type of architecture you implement is your choice. Install FSMS on a single computer or network it to other computer stations in your
organization, or install FSMS on multiple computers located in physically separate locations throughout your office or global corporation.
The strategy you select should be optimized to support your business structure, and FedEx has many excellent consultants who can help
you determine what the best strategy may be for your business. Here is some general information that may help you make sense of what to
consider as you decide.
Networks and Connectivity
The FSMS software installs on a computer in your data center and is self-contained. That is, although it requires a network connection to
FedEx over a secure Internet (TCP/IP) for uploading and downloading of shipping data, it does not require a constant connection. All
shipping functionality is contained within the FSMS application.
1-2
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 1: Introduction to FedEx Ship Manager Server
You should set up your network connectivity in a way that makes sense for your shipping operations. See the FedEx Ship Manager® Server
Installation and Configuration Guide for the requirements for hardware, software, and network connections.
Meters
Each FSMS client is assigned its own meter number which identifies the hardware device and software you have installed. There are two
types of FedEx meters: parent and child.
The parent meter, also called the master meter, is typically the first meter that you receive when you register your FSMS installation with
FedEx. The parent meter, and all child meters you create, are associated with your company FedEx account and identify you as the Sender
in all Request transactions to FedEx.
Child meters are associated with a master meter. You must have registered and received a master meter before you can register for a child
meter. Child meters are useful when you have several shipping departments within a single organization or complex of buildings.
It is important that at the end of each shipping day you close all meters, both master and child, using the 007 End-of-Day Close transaction.
This action enables FedEx to receive information about the shipments you have processed during the day and to properly route and rate
your packages. This is critical to FedEx operations and to ensuring that you receive the highest quality of service from FedEx.
Secure Network Communication Interface
Figure 1-1 shows an example of how FSMS can be implemented using a single FSMS application accessed by multiple computers inside a
corporate fire wall. FedEx Ship Manager Server is connected to a shipping system that employs multiple printers to print labels and reports
throughout the shipping day. Communication with the FedEx corporate systems takes place over a secure TCP/IP Internet network and can
also be made available over a dial-up server.
Figure 1-1: Communication Network Interface
v 10.6.1
FedEx Ship Manager® Server Developer Guide
1-3
Chapter 1: Introduction to FedEx Ship Manager Server
FedEx Ship Manager Server Transaction Model
FedEx Ship Manager Server is a transaction-based network solution for FedEx shipping. The FSMS application processes transactions on
your local FSMS application and sends your shipping information to FedEx for routing, rating and other delivery processing. The transaction
processing requires only a part-time network connection with FedEx systems. This connection also enables you to obtain data required to
complete your shipping operations, such as receipt of delivery dates, rates, time-in-transit and tracking information.
The FSMS application provides different transactions for different types of shipping tasks. For example, when you need to enter data about
packages you are shipping, use the 020 Global Ship Request transaction. However, if you need to delete a package in a shipment, use the
023 Global Delete Request transaction.
This guide provides a complete list of FSMS transactions in Chapter 1: “Introduction to FedEx Ship Manager Server” on page 1-1.
FedEx Ship Manager Server transactions are grouped in Request/Reply pairs, also called transaction sets. With FSMS, a shipper sends a
Request transaction to FedEx that identifies the shipment and tells FedEx that the shipment is prepared and ready to ship. It also tells
FedEx who is sending the shipment and to whom it will be delivered. Depending on the origin of the shipment, its destination and its
contents, other data may be required to complete the transaction, such as declared customs value or hazardous materials data. When
FedEx receives the request from the shipper, the shipment is processed and FedEx returns a Reply transaction that contains the data
required by the shipper to complete his shipment. The shipper prints labels and FedEx routes the shipment, picks it up and delivers it.
In Chapter 2: About FedEx Ship Manager Server Transactions, you will learn how FSMS transactions are used, as well as how to construct
a transaction statement using FSMS data fields.
Network and Internet Requirements
FedEx Ship Manager Server software must communicate with FedEx directly through a network connection. To do this, the server running
FSMS must have:
• FedEx Ship Manager Server installed and configured
• Dedicated IP address
• Access to the Internet to communicate with FedEx
• Winsock loaded
See the FedEx Ship Manager® Server Installation and Configuration Guide for the FSMS system requirements.
Getting Started with FedEx Ship Manager Server
This guide assumes you have completed the research and planning that supports the implementation of FSMS integration with your
shipping process.
It also assumes that you have successfully installed and configured FSMS on a local client. If you have not installed FSMS, see the FedEx
Ship Manager® Server Installation and Configuration Guide for instructions. The Installation and Configuration guide contains checklists of
administrative tasks that help you to properly install FSMS on your local system. If you need assistance, contact your FedEx account
executive.
Before you start, read the FedEx Ship Manager® Server Services and Shipping Guide which explains the FedEx features and services you
can implement with FSMS.
To Get Started:
• Read Chapter 1 and 2 in this Developer Guide to get an overview of the FSMS product. These chapters describe how FSMS works and
explain the transaction model that it uses.
1-4
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 1: Introduction to FedEx Ship Manager Server
• Locate the sections in this guide that provide the information you need to complete your FSMS software integration. For example, if you
are implementing a FedEx Ground U.S. shipping solution, you will want to become familiar with the transaction syntax that supports that
service in Chapter 6: Coding Transactions for FedEx Ground U.S. Services.
• Become familiar with the FedEx shipping rules and restrictions that are part of every FSMS shipping transaction you code. This guide
describes shipping rules as they relate to a transaction function, such as rate quotes or weight limits allowed as data values. For a
comprehensive guide about FedEx shipping and services, read the FedEx Services Guide on fedex.com.
• Keep the FedEx Ship Manager® Server Transaction Coding Reference Guide available at all times. It is a complete reference guide for all
the transaction field elements that you use to code your FSMS transactions.
• For additional developer-centric information and resources that support your work, be sure to log on to fedex.com and register at the
Developer Resource Center.
• If you need to register a meter, review the Meter Registration Utility information in Chapter 14: FedEx Ship Manager Server Utilities.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
1-5
Chapter 1: Introduction to FedEx Ship Manager Server
THIS PAGE INTENTIONALLY LEFT BLANK.
1-6
FedEx Ship Manager® Server Developer Guide
v 10.6.1
CHAPTER 2: ABOUT FEDEX SHIP MANAGER SERVER
TRANSACTIONS
The FedEx Ship Manager® Server (FSMS) is a transaction-based interface to FedEx® shipping services. For this reason, each transaction
is based on shipping rules that support FedEx services and shipping operations. It is essential that, as a developer, you understand the
shipping logic for each transaction you code. This logic helps you to determine which fields to include in a transaction and is important for
developing successful replies that return the information you need for your shipping operations.
This chapter describes the types of FSMS transactions that you can develop and the rules for coding basic transactions in the following
sections:
• FedEx Ship Manager Server Transaction Overview
• Before You Begin to Code
• FedEx Ship Manager Server Shipping Process and Workflow
• FedEx Ship Manager Server Transaction Request/Reply Pairs
• Basic Shipping Data for FedEx Ship Manager Server Transactions
• How to Build FedEx Ship Manager Server Transactions
• Single Piece versus Multiple Piece Transactions
• How to Read FedEx Ship Manager Server Transaction Coding Tables
• Transactions Do More Than Ship
• Submitting Transactions
• Error Messages and Troubleshooting
• Next Steps
FedEx Ship Manager Server Transaction Overview
FedEx Ship Manager Server provides the speed and efficiency that allows large-volume shippers to move their products quickly from
shipping dock, warehouse or distribution center to their destinations using FedEx shipping services. It supports those shipping services
which are especially applicable for enterprise businesses that demand constant movement of product from manufacturing or warehouse
floor outbound to customer locations.
As your shipment moves from your shipping dock to its final destination, you can track its status and location on fedex.com using an
assigned tracking number.
See “FedEx Ship Manager Server Shipping Process and Workflow” for more information about steps for processing shipments.
Flexible Transaction Functions
Code FedEx Ship Manager Server transactions to meet the detailed requirements and demands of your shipping environment. Because it
gives you the ability to write code that integrates with your existing business or warehouse software, you can work in the way that is most
efficient for preparing and shipping your product or commodity.
You can code transactions to do almost anything you might need to accomplish as part of your shipping scenario. If FedEx provides the
service, in most cases, FSMS transactions can deliver that service as part of your integrated solution.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
2-1
Chapter 2: About FedEx Ship Manager Server Transactions
Rule-Driven Transaction Logic
In all instances, FSMS transactions are rule-driven. They support and enforce the FedEx shipping rules and restrictions that define the
FedEx services. To understand how to properly code a successful transaction, you must first understand the FedEx service and shipping
rules for the solution you want to implement. This requires research and knowledge transfer.
To assist you, the FedEx Ship Manager® Server Services and Shipping Guide describes the shipping rules for each FedEx service that is
available with FSMS. It also provides At-A-Glance tables to help you determine which solution best fits your shipping needs.
Be sure to contact your FedEx account executive. They can provide guidelines and assist you in making your implementation decisions.
Shipping Services from FedEx
This Developer Guide helps you code properly formed transactions. When your transactions are properly formed, you ensure that your
FSMS client receives the correct information from FedEx to correctly rate and complete your shipment. Likewise, when you adhere to FedEx
shipping rules, you ensure that appropriate forms and labels are printed for each shipment you process.
For example, if your shipping is primarily from a Canada location to the U.S., then when you tell FedEx the final destination for a package,
enter your broker contact, and select the FedEx® International DirectDistribution Surface Solutions service type. FedEx helps you to make
sure the package is the correct weight and size for the service specified and that all customs paperwork that must accompany the package
is completed for the shipment. This means that the U.S.-Canada customs rules required for cross-border shipping are met and that your
shipment is less likely to encounter delays during border crossing.
Use this guide to learn how to code FSMS transactions and determine which fields to include to adhere to FedEx shipping rules.
Before You Begin to Code
Before you begin coding transactions, it is important to understand the details about the shipping that your company does. If your shipping is
integrated with business operations, then the type of transactions you may need to code will be different than if your shipping is managed
from a warehouse center, or if it is managed by separate departments in remote office buildings.
Each FedEx customer shipping environment is unique. Therefore, it is important to approach creating FSMS transactions for your FedEx
shipping by asking two questions:
• What are the specific shipping needs of my business?
• What are the FedEx shipping options available to me?
Develop Knowledge of FedEx Services
An in-depth understanding of your business, combined with a knowledge of the shipping services provided by FedEx, results in a shipping
strategy that will fully support your day-to-day shipping operations.
FedEx Ship Manager Server is a recommended solution for high-volume customers shipping large numbers of packages/pallets each day
both within the United States and abroad. Through the FSMS transaction interface, you have the flexibility of selecting multiple function
modules that allow you to custom code shipping transactions that give you fast reliable service.
To help you understand what is available, FedEx provides a description of the FSMS shipping services in the FedEx Ship Manager® Server
Services and Shipping Guide. This guide provides At-A-Glance tables that can help you quickly decide which FedEx service best meets
your need. Other resources include the FedEx Services Guide and fedex.com.
Become Familiar with Resources
This Developer Guide provides the information you need to build each transaction to your specifications. It contains both field and
transaction syntax tables to help guide you through the transaction coding process. It also describes the shipping rules and restrictions that
define the transaction values to which you must code.
2-2
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 2: About FedEx Ship Manager Server Transactions
After you learn how easy it is to code a transaction, you will find the FSMS transaction coding tables in the FedEx Ship Manager® Server
Transaction Coding Reference Guide very useful. Use this reference guide to quickly look up or confirm specific field properties as you
create, finalize and test your completed transaction programs. It also contains a complete list of error codes and messages to help you
debug your programs as you work.
For additional assistance, register on fedex.com for the FedEx Ship Manager Server Developer Resource Center. This online website
provides the latest developer information for building and maintaining your FSMS integrated application and shipping solution.
FedEx Ship Manager Server Shipping Process and
Workflow
With FSMS, you can select how you want to ship and where in your operations you want shipping to integrate with your other business
practices. There are a few basic steps, however, that all shipping processes follow. The following are basic steps for processing a shipment
using FSMS:
1 — Prepare Your Shipment
Prepare and package your shipment prior to shipping. For certain shippers, this may be a warehouse pick and pack process that
results in pallet shipments. For other shippers, operations may require that products be packaged for shipping as individual orders are
received and invoices processed.
Follow the rules and restrictions for preparing packages and shipments on fedex.com. Check package weight and size to ensure it is
within the allowed limits for the service type you select.
2 — Log on to FedEx Ship Manager Server
Use the FSMS interface to submit transaction requests and receive data in transaction replies. See the FedEx Ship Manager® Server
Installation and Configuration Guide for information about configuring the software and logging on to FSMS.
3 — Request Tracking Numbers
You may request Pre-assigned tracking numbers for packages you plan to ship during the day. Use the 004 Tracking Number Request
transaction to receive a range of tracking numbers in a 104 Tracking Number Reply transaction that you can assign to individual
packages. This request is most commonly used by shippers who need to give customers tracking numbers before they ship their order.
Requesting tracking numbers is an optional step.
4 — Create Your FedEx Shipment
Use the 020 Global Ship Request transaction to create your shipment.
You can create a shipment in various ways, depending on how many packages are in the shipment.
–Single Package — code a single transaction that creates a one-package shipment that you can ship immediately.
–One or More Packages — code a multiple-piece shipment in either a single transaction or as an Open Ship transaction. Open Ship
creates a master shipment when you enter the first package and allows you to add packages to the “open” shipment throughout the
day. When the Open Ship shipment is complete, you must confirm that the shipment is complete prior to shipping.
The 020 Global Ship Request transaction must include the required fields that tell FedEx where to send the package, which service to
use, how many packages to ship, if the package contains alcohol, dry ice, dangerous goods or hazardous materials, and which special
service options to apply.
The 120 Global Ship Reply transaction returns data you need for your labels and documents, as well as tracking numbers and other
shipment information.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
2-3
Chapter 2: About FedEx Ship Manager Server Transactions
5 — Check Rates and Origin/Destination Addresses
You may use the 025 Rate Available Services Request transaction to check rates and services for specific origin -- destination address
combinations. If you are shipping from the U.S. to other countries, then checking FedEx service availability to addresses in these
countries is important. Checking rates and addresses is an optional step.
6 — Process and Complete Your Shipment
If you created an Open Ship shipment, you can continue to add packages as needed throughout the shipping period. When you are
ready to complete the shipment, use the 020 Global Ship Request transaction to confirm that the shipment is complete and ready for
FedEx pickup.
If you used a single transaction to create and complete the shipment, then the shipment is now ready for FedEx pickup.
If you must delete a shipment that you have completed and/or confirmed, use the 023/123 Global Delete Request/Reply transaction.
This transaction deletes one or more packages from a shipment or deletes the entire shipment.
7 — Print Labels
The 120 Global Ship Reply transaction includes data required for printing labels. Some of this data is coded based on pre-selected
options set by the shipper during the FSMS configuration process, such as the label type and printer ID.
You can choose to print your labels after your shipment is processed (at the end), print them for each package as it is processed (PrintAs-You-Go), or defer printing of labels by saving labels to a buffer file that you can send to the printer at a later time. If you need to
reprint any label, use the 095 Label Reprint Request transaction.
The 195 Label Reprint Reply transaction returns the label for printing on a printer that you have either pre-selected or designated in the
095 transaction.
8 — Print Customs and Shipping Documents
You can print or upload customs and shipping documents, such as commercial invoices, manifests and shipper declarations, any time
prior to pickup by FedEx. Some of the information that must print on custom forms is pre-configured on your FSMS client. Some of the
information must be passed in a 020 Global Ship Request transaction which identifies the report or document you want to generate and
print.
Note: FedEx® Electronic Trade Documents may be uploaded a maximum of ten days before shipment.
9 — Attach Labels and Prepare Packages for Pickup
Your package(s) must have a proper FedEx label attached before FedEx can pick up the package. If you are using a custom label that
is not a standard FedEx label, be sure to have the label approved by FedEx before you use it on your packages. Improperly designed
labels result in packages that cannot be handled by FedEx automation devices at FedEx service locations.
10 — Track Packages
This step is optional. FedEx Ship Manager Server can track packages by Delivery Confirmation Number, which occurs after the
shipment is confirmed to FedEx. You can receive information in real time about your package as it moves towards its destination.
Tracking is provided via the Web Services product. For information about transactions that track packages, see the Developer
Resource Center at fedex.com/developer.
11 — Close All Shipments for the Day
Use the 007 End-of-Day Close Request transaction to close the FedEx shipping meters on your FSMS client and send your shipment
information to FedEx. This is a critical step in the FedEx shipping process. When you close your shipping meters at end of day, you
enable FedEx to properly route and rate your shipments to provide you the most efficient shipping service and dependability.
12 — Exit the FedEx Ship Manager Server Application
When you exit the FSMS interface, be sure you leave your shipping station secure. No unauthorized personnel are able to access your
shipping data when you properly shut down FSMS at the end of your shipping day.
2-4
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 2: About FedEx Ship Manager Server Transactions
FedEx Ship Manager Server Transaction Request/Reply
Pairs
FedEx Ship Manager Server supports FedEx shipping services by designating specific transaction pairs to perform certain functions.
List of FedEx Ship Manager Server Transaction Pairs
• 004/104 Tracking Number Request/Reply — obtain tracking numbers for FedEx Express® FedEx Ground® and FedEx Home Delivery®.
• 007/107 End-of-Day Close Request/Reply — perform an end-of-day Close transaction or request the status of the End-of-Day Close.
• 020/120 Global Ship Request/Reply — ship packages and request FedEx Express, FedEx Ground and FedEx Home Delivery for
international, U.S. domestic and Canada shipments, FedEx Express routes and FedEx Ground and Home Delivery time-in-transit
information for shipments.
• 023/123 Global Delete Request/Reply — delete one or more packages from a shipment or to delete and entire shipment.
• 024/124 Shipment Query Request/Reply — locate a package in the FSMS database.
• 025/125 Rate Available Services Request/Reply — request rates and service options for specific origin/destination combinations.
• 033/133 Delete E-Mail Label Request/Reply — cancel an E-mail Label Request.
• 035/135 Child Meter Registration Request/Reply — request a new child meter using a transaction rather than the Meter Registration
Utility, which is the recommended method.
• 049/149 Pre-Shipment Document Upload Request/Reply — upload customs documents and invoices up to ten days prior to package
shipment for FedEx Express and FedEx Ground service U.S. to CA and CA to U.S.
• 050/150 Service Types and Special Services Request/Reply — request official service names for shippers who hard-code them.
• 050/150 Versioning Request/Reply — request your current FSMS software version information, check for software updates or update
your software.
• 057/157 Demand Download Request/Reply — perform the same functions as the FSMS Demand Download Utility.
• 095/195 Label Reprint Request/Reply — reprint any previously printed labels or forms, either to replace damaged labels or documents,
or for shipper records. Labels are available for up to 24 hours after the shipment is processed.
For shipping functions such as e-mail labels and dispatch requests, see the FedEx Web Services documentation available on fedex.com.
004/104 Tracking Number Request/Reply
Use the 004/104 Tracking Number Request/Reply transactions to obtain tracking numbers for FedEx Express®, FedEx Ground® and FedEx
Home Delivery®.
You can request tracking numbers in advance, if needed, using this transaction. Use the 004 transaction to request and receive a tracking
number that can then be assigned in the 020 Global Ship Request transaction. This is useful if a tracking number is needed prior to a
shipment being prepared.
104 Tracking Number Reply transaction is returned to the server which sent the 004 transaction and contains the requested tracking number
and also the form ID required for FedEx Express shipments.
Example
0,"004"1,"Step 009 Pre Assign Trk #"499,"1"99,""
v 10.6.1
FedEx Ship Manager® Server Developer Guide
2-5
Chapter 2: About FedEx Ship Manager Server Transactions
Pre-assigning Tracking Numbers
You can choose to Pre-assign tracking numbers to your shipments or have them assigned at ship time. FedEx Ship Manager Server
provides the 004/104 Tracking Number Request/Reply transaction to help you obtain tracking numbers for your FedEx packages and
shipments. Tracking numbers are allocated by FedEx for each meter configured on your FedEx account.
Use the 004 Tracking Number Request transaction to Pre-assign a tracking number to your shipment.
Typically, FedEx customers Pre-assign tracking numbers when they want to provide tracking information to their recipient before sending a
package, or they need to create a custom label with the tracking number printed.
When you request Pre-assigned tracking numbers before shipping packages using the 004 Tracking Number Request transaction, the
tracking number is returned in the 104 Tracking Number Reply transaction.
Transaction Rule for Request of Tracking Number
When using the 004 Tracking Number Request transaction to Pre-assign a tracking number, the meter number requesting the tracking
number must be included in the transaction.
Tracking numbers are assigned at the meter level, so the meter number is required for both the 004 Tracking Number Request and when
you ship using the 020 Global Ship Request transaction.
Also see Tracking FedEx SmartPost Shipments in Chapter 7: Coding Transactions for FedEx SmartPost.
007/107 End-of-Day Close Request/Reply
Use the 007/107 End-of-Day Close Request/Reply transaction to perform an End-of-Day Close transaction or to request the status of the
End-of-Day Close.
Submitting an End-of-Day Close request causes the server to upload all package and revenue data to FedEx and generates end-of-day
reports. An End-of-Day Close status request returns the status of the current End-of-Day Close transaction but does not cause an End-ofDay Close.
All shippers are required to perform an End-of-Day Close daily.
You must perform an End-of-Day Close request on FedEx Express, FedEx Ground and FedEx Home Delivery (or all simultaneously).
Example
0,"007"1,"FedEx7"498,"4147"3025,"FDXG"99,""
0,"107"1,"FedEx7"10,"123456789"498,"000004147"1939,"8"3025,"FDXG"99,""
020/120 Global Ship Request/Reply
The 020/120 Global Ship Request/Reply transaction pair are the primary shipping transactions for FSMS.
Shipping Requests
Use the 020 Global Ship Request transaction to ship packages using any of the four available shipping methods - single shot, single piece,
open ship and multiple-piece shipment (MPS). The 020 transaction must contain all the required field data for shipping the shipment. For
example, it must specify the Recipient information, FedEx service type, required shipment and package information and, as applicable,
special services and delivery options selected.
You can use the 020 transaction to ship FedEx Express and FedEx Ground shipments intra-U.S. and international.
The 020 Global Ship Request transaction contains the data that supports your entire shipping process, from preparation of the shipment
through to the confirmation to ship and printing of labels.
Example
0,"020"1,"Domestic Shipment"11,"Express Test"13,"100 Main St"15,"Anywhere"18,"9012369999"
16,"al"17,"35801"23,"1"50,"US"498,"400085"1273,"01"1274,"92"1670,"100"99,""
2-6
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 2: About FedEx Ship Manager Server Transactions
Rates, Routes and Time-in-Transit Requests
You can also use the 020 Global Ship Request transaction to request FedEx Express, FedEx Ground and FedEx Home Delivery rates (U.S.
and Canada), FedEx Express routes, and FedEx Ground and FedEx Home Delivery time-in-transit information for shipments.
Example
This example shows a single piece transaction that requests both rate and time-in-transit data for a FedEx Ground shipment.
0,"020"1,"Single Package Ground Rate Quote/Time in Transit"11,"Recipient Company"13,"20
Peachtree Rd."15,"Memphis"16,"TN"17,"38125"18,"9012639234"23,"1"50,"US"187,"199"498,""
537,"\\printserver\eltronlp"1234,"3"1273,"01"1274,"92"1282,"N"1660,"N"1670,"1500"3056,"PO
Number 0001"3062,"2"99,""
Pre-Ship Validation
You can pre-validate a shipping transaction for FedEx Express, FedEx Ground and FedEx Home Delivery to ensure that your shipping
information is correct prior to ship time. To pre-validate, include Field 184 (Pre-Ship Validation Flag) in a single shot or Open Ship
transaction (see Chapter 4: FedEx Ship Manager Server Open Ship Transactions).
Example
This code example shows a single shot multiple-piece FedEx Express shipment with pre-validation enabled.
0,"020"1,"Express single transaction MPS multiple ref fields"11,"Recipient Company"13,"20
Peachtree Rd."15,"Atlanta"16,"GA"17,"30052"18,"9012639234"23,"1"25,"CR001 Package 1"25-2,
"CR002 Package 2"25-3,"CR003 Package 3"25-4,"CR004 Package 4"25-5,"CR005 Package 5"50,"US"184,
"Y"187,"199"498,"3781"537,""541,"NNNNNNNNN"1234,""1273,"01"0,"01"1660,"Y"1670,"500"1670-2,
"500"1670-3,"500"1670-4,"500"1670-5,"500"3062,"2"99,""
Electronic Trade Documents
Examples:
Basic Single Piece Shipment for Commercial Invoice for Electronic Trade Documents for International Express Priority Shipment
with a Commodity Originating in U.S.
0,"020"1,"Single piece"11,"Company"12,"Name"13,"1 Main Street"15,"TORONTO"16,"ON"17,"M5K1V8"
18,"1234567890"23,"1"25,"Reference"26,"2501"50,"CA"70,"1"72,"1"74,"CA"75,"lbs"79,"BOOKS"80,"
US"116,"1"117,"US"119,"250100"187,"PNG"414,"IN"1090,"USD"1116,"IN"1139,"123456789"1273,"01"12
74,"92"1349,"S"1350,"123456789"1358,"30.37(i)"1670,"1000"1958,"BBL"2805,"Y"2818,"1 "2819,
"C:\yourETDuploadsample.txt"99,""
Basic MPS Shipment for Commercial Invoice for Electronic Trade Documents for International Express Priority Shipment with a
Commodity Originating in US
0,"020"1,"MPS"11,"Company"12,"Name"13,"1 Main Street"14,""15,"TORONTO"16,"ON"17,"M5K1V8"18,
"1234567890"23,"1"25,"Reference"26,"2501"50,"CA"70,"1"72,"1"74,"CA"75,"lbs"79,"BOOKS"80,"US"
116,"4"117,"US"119,"250100"187,"PNG"414,"IN"1090,"USD"1116,"IN"1139,"123456789"1273,"01"1274,
"92"1349,"S"1350,"123456789"1358,"30.37(i)"1670,"1500"1670-2,"1500"1958,"BBL"19582,"BBL"2805,
"Y"2818,"1"2818-2,"1"2819,"C:\yourETDuploadsample.txt"2819-2,"C:\yourETDuploadsample.txt"
99,""
v 10.6.1
FedEx Ship Manager® Server Developer Guide
2-7
Chapter 2: About FedEx Ship Manager Server Transactions
Open Ship Transaction for Commercial Invoice for Electronic Trade Documents for International Express Priority Shipment with a
Commodity Originating in U.S.
0,"020"1,"Open"11,"Company"12,"Name"13,"1 Main Street"14,""15,"TORONTO"16,"ON"17,"M5K1V8"18,
"1234567890"23,"1"25,"Reference"26,"25"50,"CA"70,"1"72,"1"74,"CA"75,"lbs"79,"BOOKS"80,"US"117
,"US"119,"250100"187,"PNG"414,"IN"541,"YNNNNNNNN"542,"Express"1090,"USD"1116,"IN"1139,"123456
789"1273,"01"1274,"01"1349,"S"1350,"123456789"1358,"30.37(i)"1670,"1500"1958,"BBL"2818,"1"281
9,"C:\yourETDuploadsample.txt"99,""
0,"120"1,"Open"10,"610366546"29,"940079202765"498,"115844"526,"0430"542,"Express"1678,"FDX0"
2817,"ID-14BFE5DD-C4C0-4E7B-BCA4-AB8335EBAC27"2818,"1"2819,"C:\yourETDuploadsample.txt"99,""
0,"020"1,"Add a piece"11,"Company"12,"Name"13,"1 Main Street"14,""15,"TORONTO"16,"ON"17,
"M5K1V8"18,"1234567890"23,"1"25,"Reference"26,"25"50,"CA"70,"1"72,"1"74,"CA"75,"lbs"79,"BOOKS
"80,"US"117,"US"119,"250100"187,"PNG"414,"IN"541,"NNNYNNNNN"542,"Express"1090,"USD"1116,"IN"1
139,"123456789"1273,"01"1274,"01"1349,"S"1350,"123456789"1358,"30.37(i)"1670,"1500"1958,"BBL"
2818,"1"2819,"C:\yourETDuploadsample.txt"99,""
0,"120"1,"Add a piece"10,"610366546"21,"15"26,"2500"29,"940079202776"57,""58,""59,""116,"2"
498,"115844"526,"0441"542,"Express"1117,"0002"1123,"940079202765"1124,"0430"2817,"ID1887A3B1-CD60-4154-A4D4-47CE41444921"2818,"1"2819,"C:\yourETDuploadsample.txt"99,""
0,"020"1,"Confirm"11,"Confirm"12,"Name"13,"1 Main Street"14,""15,"TORONTO"16,"ON"17,"M5K1V8"
18,"1234567890"23,"1"25,"Reference"26,"25"50,"CA"70,"1"72,"1"74,"CA"75,"lbs"79,"BOOKS"80,"US"
117,"US"119,"250100"187,"PNG"414,"IN"541,"NNNNNNNNY"542,"Express"1090,"USD"1116,"IN"1139,"123
456789"1273,"01"1274,"01"1349,"S"1350,"123456789"1358,"30.37(i)"1670,"1500"1958,"BBL"2818,"1"
2819,"C:\yourETDuploadsample.txt"99,""
0,"120"1,"Confirm"10,"610366546"30,"XV YOOA"33,"AA"34,"17663"35,"2914"36,"00"37,"20577"60,"
30"65,"40157099110000049400792027654301"65-2,"40157099110000049400792027764419"112,"30"116,
"2"119,"250100"194,""195,"YYZ"198,"YOOA "409,""431,"N"498,"115844"542,"Express"557,"02"558,
"5024"559,"Express Domestic/International List Rates are not available."650,"TRK#"650-2,"MPS#"
651,"0430"651-2,"0441"652,"## MASTER ##"652-2,"Mstr# 9400 7920 2765"653,"XV YOOA "654,""655,
"1 of 2"655-2,"2 of 2"656,"9400 7920 2765"656-2,"9400 7920 2776"657,""657-2,"0430"658,"AA"
659,"INTL PRIORITY"660,""661,"M5K 1V8"662,"ON-CA"663,"YYZ"665,"505C1/8B40/5FE8"1084,"JLNA
"1086,"0"1090,"USD"1092,"A"1125,"0"1136,"XV"1274,"01"1359,"NO EEI 30.37 (i)"1533,"20577"1596,
""1598,"20577"1947,"490"1948,"2914"1981,"10:30 AM"1992,""2399,"0"2817,"ID-6432E15B-3C52-40D8BC16-2E478DA7D7BE"2817-2,"ID-23DA98F4-7FBA-4E91-94C7-EE31B31F52E5"2818,"1"2818-2,"0"2819,
"C:\yourETDuploadsample.txt"2819-2,"C:\FedEx\Fedex_ETDLabels\940079202765.PDF"99,""
OpenShip Transaction for Commercial Invoice for Electronic Trade Documents for International Ground Shipment with a
Commodity Originating in U.S.
0,"020"1,"Open"11,"Company"12,"Name"13,"1 Main Street"14,""15,"TORONTO"16,"ON"17,"M5K1V8"18,
"1234567890"23,"1"25,"Reference"26,"2501"50,"CA"70,"1"72,"1"74,"CA"75,"lbs"79,"BOOKS"80,"US"1
17,"US"119,"250100"187,"PNG"414,"IN"541,"YNNNNNNNN"542,"GROUND"1090,"USD"1116,"IN"1139,"12345
6789"1273,"01"1274,"92"1349,"S"1350,"123456789"1358,"30.37(i)"1670,"1500"1958,"BBL"2818,"1"28
19,"C:\yourETDuploadsample.txt"99,""
0,"120"1,"Open"10,"610366546"29,"005974770000025"498,"115844"542,"GROUND"1678,"FDX0"2817,"IDC7BB2A94-7ED9-48EC-996A-1C13E1B9ABEB"2818,"1"2819,"C:\yourETDuploadsample.txt"99,""
0,"020"1,"Add a piece"11,"Company"12,"Name"13,"1 Main Street"14,""15,"TORONTO"16,"ON"17,
"M5K1V8"18,"1234567890"23,"1"25,"Reference"26,"2501"50,"CA"70,"1"72,"1"74,"CA"75,"lbs"79,"BOO
KS"80,"US"117,"US"119,"250100"187,"PNG"414,"IN"541,"NNNYNNNNN"542,"GROUND"1090,"USD"1116,"IN"
1139,"123456789"1273,"01"1274,"92"1349,"S"1350,"123456789"1358,"30.37(i)"1670,"1500"1958,"BBL
"2818,"1"2819,"C:\yourETDuploadsample.txt"99,""
2-8
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 2: About FedEx Ship Manager Server Transactions
0,"120"1,"Add a piece"10,"610366546"29,"005974770000032"498,"115844"1678,"FDX0"2817,"IDCB7F39C5-57DC-4F1F-AA94-745CAC0DD9F1"2818,"1"2819,"C:\yourETDuploadsample.txt"99,""
0,"020"1,"Confirm"11,"Company"12,"Name"13,"1 Main Street"14,""15,"TORONTO"16,"ON"17,"M5K1V8"
18,"1234567890"23,"1"25,"Reference"26,"2501"50,"CA"70,"1"72,"1"74,"CA"75,"lbs"79,"BOOKS"80,"U
S"117,"US"119,"250100"187,"PNG"414,"IN"541,"NNNNNNNNY"542,"GROUND"1090,"USD"1116,"IN"1139,"12
3456789"1273,"01"1274,"92"1349,"S"1350,"123456789"1358,"30.37(i)"1670,"1500"1958,"BBL"2818,"1
"2819,"C:\yourETDuploadsample.txt"99,""
0,"120"1,"Confirm"10,"610366546"34,"4720"35,"8745"36,"0"37,"13465"60,"30"112,"30"116,"2"498,"
115844"542,"GROUND"543,"0"1089,"0"1090,"USD"1092,"51"1274,"92"1359,"NO EEI 30.37 (i)"1596,"0"
1598,"13465"1690,"N"1942,"N"1943,"N"1944,"N"1947,"100"1947-2,"490"1947-3,"660"1948,"3640"
1948-2,"248"1948-3,"4857"1981,"End of Day"1992,"0"2399,"3"2399-2,"3"2405,"N"2703,"-1"2817,
"ID-DCB68BD8-85AE-4AC6-80A5-1147DD7E4504"2817-2,"ID-F16250C6-C153-4DAD-AD81-1F9331583062"
2818,"1"2818-2,"0"2819,"C:\yourETDuploadsample.txt"2819-2,"C:\FedEx\Fedex_ETDLabels
\005974770000025.PDF"3058,"4"3063,"9612022005974770000025"3063-2,"9612022005974770000032"
3065,"420M5K1V8"3073,"022"3073-2,"022"99,""
023/123 Global Delete Request/Reply
Use the 023/123 Global Delete Request/Reply transaction to delete one or more packages from a shipment or to delete an entire shipment.
The following rules apply to a 023/123 Global Delete transaction.
• Identify the package(s) you want deleted using Field 29 (Tracking Number).
• Deletion requests cannot be undone. If you accidentally remove a package from a shipment, you must use the 020 Global Ship Request
transaction to re-add it.
• If a tracking number from a FedEx international multiple-piece shipment (MPS) shipment or a U.S. C.O.D./MPS shipment is specified, the
entire shipment is deleted, as well as the individual tracking number.
• Deleted packages are uploaded as a separate cycle during the end-of-day processing.
Note: Do not use the 023 Global Delete Request transaction to delete International Priority DirectDistribution (IPD) shipments.
Examples
0,"023"1,"Global Delete"29,"545095170000927"498,"103942"99,""
0,"123"1,"Global Delete"29,"545095170000927"99,""
024/124 Shipment Query Request/Reply
Locate a package in the FSMS database by sending a 024 Shipment Query transaction and requesting information. This feature is available
for all FedEx shipping solutions except FedEx SmartPost®.
To search for a specific package by its tracking number, use the following fields:
• Field 29 (Tracking Number) to identify the package you want to query
• Fields IDs 1063 (International Shipment Flag), 1064 (Domestic Shipment Flag), 1176 (Deleted Shipment Flag), 1361 (Shipment Status),
and 1689 (Shipment Query Code) are optional; however, using these fields speeds up the query if the transaction is directed to look in a
specific database rather than all FSMS databases.
To narrow the search for all packages that have been processed for a specific meter, use Fields 116 (Package Total), 1063 (International
Shipment Flag), 1064 (Domestic Shipment Flag), 1123 (Master Tracking Number), and 1176 (Deleted Shipment Flag) to target specific
databases or specific package criteria. All tracking numbers processed for a specified meter return in the 124 Shipment Query Reply, along
with the Recipient contact, Recipient address line 1, Recipient state, Reference information, and Shipper contact for each tracking number.
Example
0,"024"29,"447997341520"498,""99,""
v 10.6.1
FedEx Ship Manager® Server Developer Guide
2-9
Chapter 2: About FedEx Ship Manager Server Transactions
Electronic Trade Documents
The minimum 124 Shipment Query Reply fields for an Electronic Trade Documents single-piece shipment with the Document Reference ID
and ETD Status Code are shown in the following example.
Example
0,"124"1,"Global Shipment Query"11,"Recipient Company"12,"Auto Step 004"13,"387 Main Street"
14,"Single piece"15,"QUEBEC"16,"ON" 17,"M1M1M1"18,"1234567890"22,"01"23,"49"24,"20100320"25,
"Single piece"29,"876543289054"34,"2360"35,"7408"36,"472"37,"9296"50,"CA"53,"0"57,"0"58,"0"
59,"0"60,"15"75,"LBS"1086,"0"1087,"0"2817,"ETDDOCUMENTEFERENCE"2822,"01" 99,""
025/125 Rate Available Services Request/Reply
You can use a single 025 Rate Available Services Request to receive the available FedEx services and corresponding rate quotes based on
your specified package, service and Meter- Account origin/destination information.
This transaction is available for FedEx Express and FedEx Ground services with U.S., Canada and Puerto Rico origins.
If Field 1274 (Service Type) and Field 1273 (Packaging Type) are not passed in the request, then all valid service/packaging combinations
for the origin/destination pair are returned in the Reply. If only one of these fields is passed in the request, then the transaction functions as
though the field is not present and requests all valid service/packaging combinations based on the origin/destination pair. By providing more
information in the Request transaction, you can receive a Reply transaction with more specific information.
Note: The Shipper setting override fields are not applicable on a rate quote. You cannot override the Meter-Account settings with Field
Tags 4 thru 10.
Rate quote is a courtesy rate quote using the Meter-Account origin/destination information.
Example
0,"025"1,"Rate All Services—weight"15,"MEMPHIS"16,"TN"17,"38115"50,"US"23,"1"117,"US" 1090,
"USD"1670,"1500" 3062,"2"99,""
0,"125"1,"Rate All Services—Weight, Field 3062=2"10,"199084747"33,"A1"33-2,"A1"33-3,"A1"33-4,
"A1"33-5,"A1"33-6,"A1"33-7,"A1"33-8,"A1"33-9,"A1"33-10,"A1"33-11,"A1"33-12,"A1"33-13,"A1"3314"A1"33-15,"A1"34,""34-2,""34-3,""34-4,""34-5,""34-6,""34-7,""34-8,""34-9,""34-10,""34-11,""
34-12,""34-13,""34-14,""34-15,""34-16,"582"34-17,"582"35,""35-2,""35-3,""35-4,""35-5,""35-6,
""35-7,""35-8,""35-9,""35-10,""35-11,""35-12,""35-13,""35-14,""35-15,""35-16,"22"35-17,"204"
36,""36-2,""36-3,""36-4,""36-5,""36-6,""36-7,""36-8,""36-9,""36-10,""36-11,""36-12,""36-13,""
36-14,""36-15,""36-16,"0"36-17,"0"37,""37-2,""37-3,""37-4,""37-5,""37-6,""37-7,""37-8,""37-9,
""37-10,""37-11,""37-12,""37-13,""37-14,""37-15,""37-16,"604"37-17,"786"60,""60-2,""60-3,""
60-4,""60-5,""60-6,""60-7,""60-8,""60-9,""60-10,""60-11,""60-12,""60-13,""60-14,""60-15,""6016,"15"60-17,"15"112,"15"116,"1"194,"TUE"194-2,"TUE"194-3,"TUE"194-4,"TUE"194-5,"THU"194-6,
"THU"194-7,"WED"194-8,"WED"194-9,"WED"194-10,"WED"194-11,"TUE"194-12,"TUE"194-13,"TUE"194-14,
"TUE"194-15,"TUE"409,"31Jan06"409-2,"31Jan06"409-3,"31Jan06"409-4,"31Jan06"409-5,"02Feb06"
409-6,"02Feb06"409-7,"01Feb06"409-8,"01Feb06"409-9,"01Feb06"409-10,"01Feb06"409-11,"31Jan06"
409-12,"31Jan06"409-13,"31Jan06"409-14,"31Jan06"409-15,"31Jan06"431,""431-2,""431-3,""431-4,
""431-5,""431-6,""431-7,""431-8,""431-9,""431-10,""431-11,""431-12,""431-13,""431-14,""43115,""431-16,"N"431-17,"N"498,"6040"543-16,"0"543-17,"0"1086-16,"0"1086-17,"0"1090,"USD"10902,"USD"1090-3,"USD"1090-4,"USD"1090-5,"USD"1090-6,"USD"1090-7,"USD"1090-8,"USD"1090-9,"USD"
1090-10,"USD"1090-11,"USD"1090-12,"USD"1090-13,"USD"1090-14,"USD"1090-15,"USD"1090-16,"USD"
1090-17,"USD"1133,"17"1273,"01"1273-2,"02"1273-3,"03"1273-4,"04"1273-5,"01"1273-6,"02"1273-7,
"01"1273-8,"02"1273-9,"03"1273-10,"04"1273-11,"01"1273-12,"02"1273-13,"03"1273-14,"04"127315,"01"1274,"01"1274-2,"01"1274-3,"01"1274-4,"01"1274-5,"20"1274-6,"20"1274-7,"03"1274-8,"03"
1274-9,"03"1274-10,"03"1274-11,"05"1274-12,"05"1274-13,"05"1274-14,"05"1274-15,"06"1274-16,
"92"1274-17,"90"1507,"614"1511,"0"1519,"5585"1520,"614"1525,"6199"1528,"6199"1596-16,"0"159617,"0"1598-16,"604"1598-17,"786"1599,"786"3018-16,"N"3018-17,"N"3058-16,"1"3058-17,"1"3084,
"175"99,""
2-10
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 2: About FedEx Ship Manager Server Transactions
033/133 Delete E-Mail Label Request/Reply
Note: This transaction cancels an E-mail Label Request.
This transaction will be invalid if the customer has already generated the label.
Example of 033 Transaction Input
0,"033"1,"Global Delete Package"29,"401202752160"498,"400085"99,""99,""
Example of 133 Transaction Output
0,"133"1,"033 Sample Transaction"10,"214877600"29,"041493670000390"498,"400085"99,""
035/135 Child Meter Registration Request/Reply
Use this transaction to register a child meter. The following business rules apply:
• The postal code is required for countries that are postal aware. If the country registering for a new child meter is not postal aware, no
input is required. For a list of postal aware countries, see Appendix C in the FedEx Ship Manager® Server Transaction Coding Reference
Guide.
• State and/or province are required for U.S., Canada and Puerto Rico only. No input is required if the countries outside these regions.
• You must have a parent meter configured on the system running FSMS.
After registration is complete, the new child meter number is displayed on the meter level lists in the FSMS Configuration Utility. You can
control whether or not a child meter can be requested for a master meter number using the FSMS Configuration Utility.
Example of 035 Transaction Input
0,"035"1,"Online Regn for Child Meters"4,"CompanyTest"5,"ABC Road"6,"ABCComplex."7,"Fair
banks"8,"AK"9,"99771"10,"106254079"25,"US Origin"32,"Kamini"117,"US"183,"9448107172"1053,
"NNNNNNNNYNNNNNNNNNNNNNNNNN"1148,"FXRS"1149,"0760"1151,"1"1153,"C"1156,"02"1591,"02"9746,"076
0"99,""
Example of 035 Transaction Output
0,"135"1,"Online Regn for Child Meters"497,"000409082"498,"100002496"1155,"000000000000000
000000"1201,""1590,""3028,"0000000"99,""
049/149 Pre-Shipment Document Upload Request/Reply
The 049/149 Pre-Shipment Document Upload Transaction allows customs documents to be electronically uploaded to brokers before the
shipment has left its origin. This allows for errors to be discovered and corrected before the shipment arrives, thus streamline the customs
process.
Pre-Shipment Document Upload is available for FedEx Express and FedEx Ground CA to U.S. and U.S. to CA.
Examples
U.S. based customer shipping a commodity with a Commercial Invoice using Electronic Trade Documents for a Single Piece shipment to
Canada
049 Pre-Shipment Upload Document Request: Commercial Invoice for Electronic Trade Documents for International Express
Priority shipment with a commodity originating in U.S.
0,"049"1,"Single piece"11,"Company"12,"Name"13,"1 Main Street"15,"TORONTO"16,"tn"17,"38135"
18,"1234567890"23,"1"25,"Reference"26,"2501"50,"us"116,"1"117,"US"119,"250100"187,"288"414,"I
N"1090,"USD"1116,"IN"1139,"123456789"1273,"01"1274,"01"1349,"S"1350,"123456789"1358,"30.37(i)
v 10.6.1
FedEx Ship Manager® Server Developer Guide
2-11
Chapter 2: About FedEx Ship Manager Server Transactions
"1670,"1500"1670-2,"1500"1958,"BBL"2805,"Y"2817,"test049"2818,"1"2819,
"C:\yourETDuploadsample.txt"99,""
0,"149"10,"610366546"50,"US"117,"US"498,"000115844"2817,"test049"2818,"1"2819,"C:\yourETDuplo
adsample.txt"2821,"C"99,""
149 Pre-Shipment Upload Document Reply: Commercial Invoice for Electronic Trade Documents for International Express
shipment with a commodity originating in U.S.
0,"149"2,"5040"3,"c:\filename.doc"10,"610366546"50,"CA"117,"US"498,"000115844"2817,"4"2818,"1
"2819,"C:\CI_935073550415.rtf"2821,"C"99,""
Note: Whenever using the 049/149 Transaction, you must also use the 020/120 Transaction to complete the transaction.
050/150 Service Types and Special Services Request/Reply
The 050 Service Types and Special Services Request transaction returns the FedEx service branded names, service short names, special
service names, accessorial names and packaging types depending on your input request.
This transaction includes the supported codes, a brief description of the product or service, the official full name of the product and service,
weight limits and delivery commitments as applicable.
Control (service type) information is available for FedEx Express and Ground for the following shipment areas:
• Domestic U.S.
• International
• Intra-Canada
You may also use this transaction to return software version information or update your software (see “050/150 Versioning Request/Reply”
in this chapter).
Example
0,"050"1,"Service Types and Special Services"498,""1274,"01"1989,"03"99,""
0,"150"1,"Service Types and Special Services"9,"38017"10,"410885743"17,""50,""117,"US"498,
"103942"1274,"01"1274-2,"01"1274-3,"01"1987,"Priority Overnight"1987-2,"International
Priority"1987-3,"International Priority"1988,"FedEx Priority Overnight"1988-2,"FedEx
International Priority"1988-3,"FedEx International Priority"1989,"03"1991,"Fedex Envelope"
1991-2,"FedEx Pak"1991-3,"FedEx Box"1991-4,"FedEx Tube"1991-5,"FedEx 10kg Box"1991-6,"FedEx
25kg Box"1991-7,"Customer Package"1993,"D"1993-2,"I"1993-3,"I"1997,"1"1997-2,"1"1997-3,"1"
99,""
050/150 Versioning Request/Reply
Use the 050/150 Versioning Request/Reply transaction to perform these tasks:
• Return FSMS software version for your implementation, such as FXRS1001, including number, FSMS build date, CRS version number,
and CLS version number.
• Check for software updates. For example, if your software version is FSMS0840 and delta is available to upgrade to FXRS1001, then this
information is returned in the reply.
• Update your software version. If you code Field 1989 (Transaction Function) to update now, the delta download is started.
You can also use the 050/150 transaction to return service types and special services information.
Example
0,"050"1,"Step 00001-01"4,"MPHASIS-BFL"5,"PSDT TEST LAB"6,"A1 AREA"11,"FEDEX CORPORATION"
12,"TESTER"13,"CSCS TEST LAB"14,"PM AREA"15,"California"16,"CA"17,"90034"18,"8501117777"
25,"Step 00001-01"32,"SEETHA"38,"FIE"50,"US"117,"US"183,"9012631111"1145,"CSCS"1273,"01"1274,
"01"1989,"01"99,""
2-12
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 2: About FedEx Ship Manager Server Transactions
0,"150"1,"Step 00001-01"9,"94404"10,"410253240"17,"90034"50,"US"117,"US"498,"409063"1274,
"01"1987,"Priority Overnight"1988,"FedEx Priority Overnight"1989,"01"1993,"D"1997,"1"99,""
057/157 Demand Download Request/Reply
The 057/157 Demand Download Request/Reply transactions perform the same functions as the FSMS Demand Download utility.
You can use Field 1053 (Download Flag) to specify the type of data you want to download. FedEx provides updates, if available, for any
selected flag. You can also perform a demand upload by including Field 2423 (Upload Flag).
The Demand Download Utility is described in Chapter 14: FedEx Ship Manager Server Utilities.
Example
0,"057"1,"Demand Download Request"10,"410885743"498,"103941"1053,
"YNNNNNNNNNNNNNNNNNNNNNNNNN"99,""
0,"057"1,"001DOM PO YP"26,"100"44,"Test"46,"New York"47,"NY"48,"10015"49,"2636716"50,"US"
75,"lbs"117,"US"187,"PNG"498,""999,"ABC Co"1116,"IN"1200,"Y"1273,"01"1274,"01"99,""
070/170 Meter Query Request/Reply
You can use this transaction to determine all the meter numbers on your FSMS server for a given account number, or determine the sender
information for a given meter.
You can also use this transaction to configure a meter, rather than using the FSMS Configuration Utility. See the FedEx Ship Manager®
Installation and Configuration Guide.
The following business rules apply to the meter configuration function:
• The new configuration transaction does not allow adding or deleting a meter.
• Each meter must send a separate 070 transaction for configuration. For example, if you have one parent meter and three child meters,
then four separate 070 transactions must be entered to make configuration changes for all meters.
• The following fields from the FSMS Configuration Utility can be configured using the 070 transaction:
–All fields on the Doc-Tab screen
–FedEx Express DG Printer ID
–FedEx Express DG Printer Form Type
–FedEx Ground HazMat Printer ID
–FedEx Express/FedEx Ground Commercial Invoice
–FedEx Ground Hazardous Materials Certification
–Client Name or Client Version
–Middleware Name
–Middleware Version
–Time Zone
–Late Drop-Off
–Sender E-mail ID
–Variable Handling fields
Example
0,"070"1,"Meter Info Query"498,"103942"556,"2"99,""
v 10.6.1
FedEx Ship Manager® Server Developer Guide
2-13
Chapter 2: About FedEx Ship Manager Server Transactions
095/195 Label Reprint Request/Reply
Use the 095/195 Label Reprint Request/Reply to reprint any previously printed label. You can also print labels that you save to a buffer file
and have not yet printed.
You may use this transaction to reprint customs documents such as a commercial invoice, Proforma invoice, certificate of origin or shipment
detail report.
The following rules apply:
• The ability to reprint a label is available for at least 24 hours, up to a maximum of 48 hours, based on the ship date and time. For
example: you ship a two-package FedEx international shipment on 07/02/05 at 16:30. You may reprint the labels from this shipment up to
22:59 on 07/03/05. The time frame in this example is 34 hours and 30 minutes.
• Future Day shipments may be reprinted based on the create date and not the actual ship date. Therefore, if you ship a multiple-piece
shipment (MPS) on 07/02/05 at 16:30 with a ship date of 07/10/05, you still have until 07/03/05 at 22:59 to reprint the label.
Example
0,"095"1,"Label Reprint"29,"449690373662"537,"\\FedEx_133\FedEx Ship Manager Server"99,""
FedEx Web Services
In addition to the FSMS transactions, you can use FedEx Web Services for real-time response from FedEx. You may use Web Services
transactions to perform the following Web Services functions:
• Address Validation
• Tracking and Visibility
You will find information about Web Services on the Developer Resource Center at fedex.com/us/developer.
2-14
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 2: About FedEx Ship Manager Server Transactions
Basic Shipping Data for FedEx Ship Manager Server
Transactions
For any transaction processed by FSMS, you must include basic shipping information fields.
METER Number
Before FedEx can accept your shipment, FSMS must verify that you are a registered FedEx customer and must check that the services you
request are appropriate for the services you've contracted with FedEx. If you have multiple meters configured, you must always provide your
FedEx meter number in each transaction you process, or if not provided, FSMS defaults to the parent/master meter.
RECIPIENT Information
Getting your package from one place to another requires that you tell FedEx who to ship the package to. This information appears in the
“To:” section of the shipping label.
FedEx Ship Manager Server creates a shipment only if you provide this information. Therefore, a basic requirement of a shipping
transaction are fields that provide the Recipient name, address and phone number.
SENDER/SHIPPER Information
You or a FedEx technical consultant configures Shipper information during a FSMS installation. FedEx Ship Manager Server maintains this
information and you do not need to enter it into a transaction each time you create a shipment. When you enter your meter number in a
transaction, FSMS correlates the meter number with your Shipper information and prints this information on the shipping label and other
required documentation.
If you want to use information that is different from the configured Shipper information, you must provide the Sender name, address and
phone number in a shipping transaction in the appropriate fields.
SERVICE Type
The FedEx service type you select determines how a package is shipped and identifies the restrictions for such items as package size or
weight and where you can ship. Be sure to research FedEx service options in the FedEx Ship Manager® Service and Shipping Guide and/or
in the FedEx Service Guide available on fedex.com.
PACKAGE Information
You may choose to ship individual packages in single transactions or you may choose to bundle them together in a multiple-piece shipment
(MPS) if they are going to the same recipient.
Regardless of the shipping method you choose, each package has required information that you must provide in a shipping transaction.
Depending on the FedEx service type you select, the service contract agreement(s) you have with FedEx and the type of package(s) you
are shipping, the amount and type of information you must provide about the package(s) you ship is different. At the minimum, you may
need to supply the weight of the package (or shipment weight) and the packaging type. International and cross-border shipments require
more detailed package and commodity information to properly complete customs and broker documents.
Payment Type
FedEx Ship Manager Server calculates the rate and returns the shipping amount in the 120 Global Ship Reply transaction. You must,
however, tell FSMS who to bill for the service. You can bill one of three entities:
• 1 — person or company sending the shipment (called the Sender)
v 10.6.1
FedEx Ship Manager® Server Developer Guide
2-15
Chapter 2: About FedEx Ship Manager Server Transactions
• 2 — person or company receiving the shipment (called the Recipient)
• 3 — third-party person or company who must be identified
When the recipient or a 3rd party is billed, FedEx Express shipments do not return a rate.
Transaction Identifier
Each transaction is identified by a unique number called a Customer Transaction Identifier. The person who codes the transaction creates
this number and ensures that it is not reused in his transaction program. In the case of large bulk shipments or batch transaction files,
including the Customer Transaction Identifier (Field 1) in the Request transaction allows you to link the Reply transaction back to the
Request transaction. For example, if you enter the identifier “SS4404” in Field 1 (1,”SS4404”) in the Request transaction, FSMS
returns 1,”SS4404” in the Reply transaction allowing you to see that the two transactions are related.
FedEx Ship Manager Server does not require this field, but it is available and recommended for customer use.
How to Build FedEx Ship Manager Server Transactions
Building a FSMS transaction is a process that begins with collecting information about your shipment.
When you build a FSMS transaction, you provide information to FSMS that tells FedEx how to get your package shipped from you to its
destination. The information must say what the package is and how you want it shipped.
FedEx determines the best route for getting it to its final destination and returns the rate and tracking information you need to bill and close
the shipment.
Key Elements of Information
To make the shipping operation happen, the FSMS transaction that creates the master shipment must contain three key elements of
information related to the 1) Package, 2) Sender and 3) Recipient.
Figure 2-1: Key Elements of Transaction Information
The Sender and Recipient information must include contact information and address locations that tell a FedEx courier where to pick up the
package and where to deliver it. The Package information must inform FedEx of the physical characteristics of the item to be shipped so that
FedEx knows whether it is a freight shipment or overnight delivery of a legal document.
As the Sender, it is your responsibility to provide FedEx with this information and also to fulfill all legal, domestic and international
requirements or regulations that may be related to your Package. There is a FSMS transaction field for each of these.
When you provide your FedEx meter number in a transaction, you tell FedEx who you are (as Sender) and where the package will originate:
that is, if you are shipping it from your registered place of business.
Note: This information is configured as part of your FSMS installation. FedEx Ship Manager Server transactions automatically use the
defaults for the Sender information configured in the FSMS Configuration Utility. If you are shipping from a location that is different, you must
include the Sender address in the transaction.
If you are shipping from a location that is different from your place of business, you must include the Sender address in the transaction.
2-16
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 2: About FedEx Ship Manager Server Transactions
Grouped Field Data for Key Elements
Figure 2-2 shows some of the fields you might include to construct a basic FSMS transaction based on information required for SENDER,
PACKAGE and RECIPIENT. Required or conditionally required fields are shown in bold.
Figure 2-2: Field Information for Key Elements
If you are sending multiple packages and must account for total weight of the shipment, then you must include the package weight in
Field 1670 for each package you send, as separate occurrences of the field. Recipient information is a requirement of all shipping request
transactions. At a minimum, you must identify the company name, contact name and country code.
Shipment and Service Information
There is additional information, shown in Figure 2-3, you must provide related to the Shipment itself. Each FSMS transaction must also
identify the specific FedEx service you’ve selected to use to ship your Package, such as FedEx Standard Overnight® or FedEx International
Priority®, and other special service options, such as whether to require a Delivery Signature or to send the package as Collect on Delivery. If
you've decided to use the Open Ship method to build a shipment of multiple packages over some shipping period, then you must tell FedEx
that you will be confirming packages which belong to a larger master shipment over the course of your shipping day.
In addition, you may want to consider printing extra information on your FedEx shipping label or print reports for invoicing or company
records. All these activities occur only when you send the appropriate field data in a shipping transaction.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
2-17
Chapter 2: About FedEx Ship Manager Server Transactions
Figure 2-3: Shipment plus Field Information for Key Elements
Select the Transaction Action
Each field you choose must be specific to the final shipping action you want to create. When you use the FedEx Express, FedEx Ground or
FedEx SmartPost services, the Request transaction you send to FedEx initiates the FedEx operations that deliver the FedEx shipping
services you selected.
FedEx Ship Manager Server provides different types of transactions for different shipment-related tasks. We've used the 020 Global Ship
Request transaction as the example, but there are other transactions which register new child meters, query shipping databases, track
shipments locally and globally, delete shipments and return FSMS software information.
To properly construct a FSMS transaction, you must understand what you want to accomplish and how, whether that's shipping packages or
collecting a day's worth of data for reports. Each FSMS-related task requires a specific array of fields that you code within the appropriate
transaction type for that task.
You'll find information in this Developer Guide to assist you in determining which fields to use for which tasks. Also use the FedEx Ship
Manager® Server Transaction Coding Reference Guide to find specific information about specific fields you want to include in a transaction.
Fields are listed by transaction type, field ID and field name in that guide.
2-18
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 2: About FedEx Ship Manager Server Transactions
Transaction String Elements
Transaction records are null-terminated strings that do not contain carriage returns or line feeds. Each FSMS transaction record consists of
the elements shown in Figure 2-4.
Figure 2-4: Transaction String Elements
Begin and End Fields
Each transaction has a “BEGIN” field and an “END” field. These two fields tell FSMS where the transaction begins and where it ends.
• BEGIN = Transaction Code Field
The first field of any transaction is Field 0 (Transaction Code). Start all Request transactions, such as the 020 Global Ship Request,
with the following:
0,"<request_transaction_id>"
• END = End of Record Indicator
The last field of any transaction is Field 99 (End of Record Indicator). End all transactions with the following:
99,""
Note: Do not use spaces or extra characters between the quotation marks in the 99,"" code.
Note: When FSMS returns the Reply transaction, the Field 0 (Transaction Code) value is the Reply transaction ID. For example, if you send
a 020 Global Ship Request transaction, FedEx Ship Manager Server returns a transaction that begins with 0,”120” to indicate it is a 120
Global Ship Reply transaction.
Data Fields
Between the BEGIN and END fields are the DATA fields. Each DATA field consists of a field/value pair separated by a comma. Each field/
value pair consists of the following information:
• Field number — one for each piece of data received or sent in a transaction
• Field value — value associated with the field ID and enclosed in double quotation marks (" ")
For example, if you are coding data Field 15 (Recipient City) and you want to assign Memphis as the value, the format for this field is as
follows:
15,"Memphis"
The transaction string is made up of an array of DATA field/value pairs that contain information required for a specific transaction. Each
transaction string is started by a BEGIN field and terminated by an END field.
Example of a FedEx Ship Manager Server Transaction
This is an example of a FSMS transaction statement that contains data for a shipment request of a single package using FedEx Express.
0,"020"1,"Express single package"11,"ACE Bikes"13,"20 Peachtree Rd."15,"Atlanta"16,"GA"17,
"30052"18,"9012639234"23,"1"25,"CR001 Package 1"50,"US"187,"199"498,"999999999"1273,"01"
1274,"01"1670,"350"3062,"2"99,""
Table 2-1 lists a vertical representation of the string above that shows the DATA fields added between the BEGIN field and the END field.
The DATA fields consist of a field number and field value separated by a comma. The field value is always given in double quotes ("").
v 10.6.1
FedEx Ship Manager® Server Developer Guide
2-19
Chapter 2: About FedEx Ship Manager Server Transactions
Table 2-1: BEGIN, DATA and END Field Elements in Example Transaction
0,"020"
BEGIN
Start of 020 Global Ship Request transaction
1,"Express single package"
DATA
Field 1 Customer Transaction Identifier
11,"ACE Bikes"
DATA
Field 11 Recipient Company
13,"20 Peachtree Rd."
DATA
Field 13 Recipient Address Line 1
15,"Atlanta"
DATA
Field 15 Recipient City
16,"GA"
DATA
Field 16 Recipient State/Province
17,"30052"
DATA
Field 17 Recipient Postal Code
18,"9012639234"
DATA
Field 18 Recipient Phone Number
23,"1"
DATA
Field 23 Pay Type 1=Bill Sender
25,"CR001 Package 1"
DATA
Field 25 Reference Information
50,"US"
DATA
Field 50 Recipient Country
187,"199"
DATA
Field 187 Label Format Value/Printer Type Indicator
199=Eltron LP2348/LP2443 4" x 6" doc-tab
498,"999999999"
DATA
Field 498 Meter Number
1273,"01"
DATA
Field 1273 Packaging Type 01=Customer Packaging
1274,"01"
DATA
Field 1274 Service Type 01=FedEx Express Priority Overnight®
1670,"350"
DATA
Field 1670 Package Weight/Shipment Weight
Note: Value accepts two implied decimal places, therefore 350
means 3.5 pounds.
3062,"2"
DATA
Field 3062 Rate Quote Type 2=List Rates and Discount Rates
99,""
END
Ends the 020 Global Ship Request transaction
The DATA fields inserted in this example transaction string are specific to the request by the shipper (identified by Field 498) to send a
package (identified by Field 25) to a recipient (identified by company name and address) using a FedEx service (identified in Field 1274).
The transaction also requests the return of a rate quote for the shipment (identified in Field 3062).
Beginning a Transaction String
Each transaction begins with the Field 0 (Transaction Code). This “BEGIN” field tells FSMS where to start looking for the data it needs to
perform your shipping request.
Field 0 must contain a value that indicates the specific Request transaction to perform. The field always appears at the beginning of a
transaction string with one of the following values:
004 or 04 or 4 — 004 Tracking Number Request: 0,"004"
007 or 07 or 7 — 007 End-of-Day Close Request: 0,"007"
020 or 20 — 020 Global Ship Request: 0,"020"
023 or 23— 023 Global Delete Request: 0,"023"
024 or 24 — 024 Shipment Query Request: 0,"024"
025 or 25 — 025 Rate Available Services Request: 0,"025"
033 or 33 — 033 Delete E-Mail Label Request: 0,"033"
035 or 35 — 035 Child Meter Registration Request: 0,"035"
050 or 50 — 050 Versioning or Service Types and Special Services Request: 0,"050"
057 or 57 — 057 Demand Download Request: 0,"057"
2-20
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 2: About FedEx Ship Manager Server Transactions
070 or 70 — 070 Meter Query Request: 0,"070"
095 or 95 — 095 Label Reprint Request: 0,"095"
Table 2-2 describes how to use the Transaction Code Field 0.
Table 2-2: Field 0 Begins Transaction Strings
Action
Field ID
Field Name
Description
Transactions: ALL
To begin a transaction string
Begin each transaction string with Field 0 (Transaction Code) followed by the
transaction request or reply identifier enclosed in double quotation marks.
For example, 0,"023" indicates that fields which follow in the string adhere to rules
for the 023 Global Delete Request transaction.
Use…
Field Level: Shipment
REQUIRED.
Indicates the start of a transaction.
For example, 0,"020" or 0,"20" signifies the start of the 020 Global Ship Request
transaction.
Field 0
Transaction Code
Ending a Transaction String
Each transaction ends with the Field 99 (End of Record Indicator). This “END” field tells FSMS that the transaction has sent all data required
for the requested action.
Field 99 does not take a value. The field always appears at the end of a transaction string with a null value which looks like this: 99.""
Table 2-3 describes how to use the End of Record Indicator Field 99.
Table 2-3: Field 99 Ends Transaction Strings
Action
Field ID
Field Name
Description
Transactions: ALL
To end a transaction statement
Use…
Field 99
End each transaction string with Field 99 followed by a null value in double quotation
marks.
For example, 99,"" indicates that this is the end of the transaction string.
End of Record Indicator Field Level: Shipment
REQUIRED.
Indicates the end of a transaction. The format is 99,"" — 99 followed by a comma
and two quotation marks. All FSMS transactions must end with 99,"".
Data Fields and Values
The data fields in a FSMS transaction string provide the information that FedEx requires to perform multiple shipping and operational tasks.
For example, fields contain information that tells FedEx:
• Where to pick up the package or shipment unit
• Who and where to deliver it
• If there is a time-critical restriction associated with the package
• If it contains dangerous goods or hazardous materials
v 10.6.1
FedEx Ship Manager® Server Developer Guide
2-21
Chapter 2: About FedEx Ship Manager Server Transactions
• If it requires an adult signature
• Who will pay for the shipping and delivery
• And more
Fields also contain important tracking, shipping invoice and rate information. You can request information from your shipping database to be
placed in reports, or ask to have the most recent list rates uploaded to your FSMS client. The information you request is returned by FedEx
in a Reply transaction that contains data fields with the information you requested. Because all fields are identified by a number, called a
Field ID, you must decipher the meaning of each field and its frequently coded value.
The FedEx Ship Manager® Server Transaction Coding Reference Guide contains a list of all FSMS fields. Appendix A lists all fields by their
identification number from 0 to 9999. Appendix B lists all fields by their coded field name. To understand what a field ID means or to identify
the ID number for a field you want to code, use this guide as your reference for all field-related information.
How to determine which fields in the Transaction Coding Reference you need to include in a specific transaction is described in “How to
Build FedEx Ship Manager Server Transactions”.
Field / Value Pairs
FedEx Ship Manager Server relies on well-formed transaction statements consisting of field/value pairs. In a field/value pair, the field
identification number (ID) is associated with a data value. A data value, also referred to as a field value, can be a number, a word or phrase
of words. You can identify each FSMS field by its unique identification number, called a Field ID.
For example, Field 11 is the data field for Recipient company name. You can use Field 11 in a 020 Global Ship Request transaction to tell
FedEx who to send a package to. If the company name is MacroDynamic Inc., the field/value pair would be coded as
11,"MacroDynamic Inc.".
In the above example, the field/value pair provides the data (company name) required to perform a shipping function (ship package to
recipient). But field/value pairs can also act as flags to enable specific FSMS functions, such printing to a laser printer or enabling the
DELETE package function in an Open Ship shipment workflow.
It can also flag FedEx service options, such as Collect on Delivery or dangerous goods. For example, in the Saturday Pickup Flag field
(1646), the data value is either Y (Yes) or N (No) to indicate selection of the Saturday Pickup service option.
See “Transaction String Elements” to learn how field/value pairs are used to create transactions.
Field Data Types
An FSMS transaction field allows only the following data types:
• Alpha — (A) allows alphabetic characters only, such as Y.
–Numeric — (N) allows numeric characters only, such as 1234.
–Alphanumeric — (A/N) allows both alphabetic and numeric characters, such as a street address: 102 Tempe Road. Alphanumeric
fields accept letters, numbers, blank spaces, and some special characters.
• Any Keyboard Entry — (AKE) allows all alphabetic and numeric characters including special characters.
The following special characters cannot be included in a transaction: double quotation marks ("), single quotation marks/apostrophes (‘) and
carets (^).
As you code transactions, make sure each field value you enter is correct for the field's data type.
Each field’s data type is described in the FedEx Ship Manager® Server Transaction Coding Reference Guide in the Data Type column of
each field table.
Field Types and Value Formats
Specific editing rules apply to each of the following field types:
Date Fields
Date fields must be eight digits in length, with all zeros included, in CCYYMMDD format. For example, code March 1, 2005 as follows:
"20050301"
2-22
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 2: About FedEx Ship Manager Server Transactions
Numeric Fields
Numeric fields must not contain commas, decimal points, blanks, or other non-numeric characters. Field lengths display in the FedEx Ship
Manager® Server Transaction Coding Reference Guide as the total number of characters in the field plus any implied decimal places
(described in the following paragraph). For example, Field 119 (Total Customs Value) specifies a field length of 14.2: 14 specifies that the
total field length is 14 numeric characters and 2 specifies that the last two numbers are interpreted as the decimal value.
Some fields are fractional fields that allow entries in decimal format. The format can be in either implicit decimals or explicit decimals. An
example of an implicit decimal would be "500" for $5USD when the field has two implicit decimals. The explicit decimal format displays the
actual decimal, such as "256.5" for 256 ½, when the field length specifies one explicit decimal.
For example, if the value of Field 119 (Total Customs Value) is $125,000USD, the recommended coding is as follows:
119,"12500000"
The field could also be coded with leading zeros as:
119,"00000012500000"
The leading zeros are disregarded by the server, but they do slow down processing.
You only need to include significant digits. Do not add leading zeroes to the beginning of a numeric field data value unless the field’s data
definition specifically requires you to do so.
Note: Spaces are not allowed.
The following example shows a field with a maximum length of 6.2 coded as:
"123456"
It is interpreted as follows:
1234.56
The following example shows a field with a maximum length of 6.0 or 6 coded as:
"123456"
It is interpreted as follows:
123456
Postal Codes
Postal codes can consist of 5, 6, or 10 alphanumeric characters, depending on the destination country, with no special characters. For
example, you must code L5N-5R6 as follows:
"L5N5R6"
The following example shows postal code 38115-1096 coded correctly as:
"381151096"
Note: All postal codes for postal aware countries are validated by FSMS prior to shipment confirmation. If the postal code is invalid, FSMS
returns an error message.
Weights
Field 1670 (Weight) specifies two implied decimals on all shipments regardless of whether the weight type entered in Field 75 (Weight Units)
is LBS or KGS. You can code both 25 pounds and 25 kilograms as follows:
"2500"
The system rounds any fractional value up to the next highest whole pound or half kilogram. For example, 25.5 pounds is coded as follows:
"2550"
and is rounded up to 26 pounds.
In another example, 12.4 kilograms is coded as follows:
"1240"
and is rounded up to 12.5 kilograms.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
2-23
Chapter 2: About FedEx Ship Manager Server Transactions
Printer ID Fields
Printer Field 537 (Thermal Printer Identifier) and 545 (Form Printer ID) cannot contain blank spaces. However, underscores are allowed. For
example, the following printer ID entry is coded correctly:
537,"FedEx_162\FedEx Ship Manager Server"
Rules for Coding Field/Value Pairs
Follow these rules when coding field/value pairs in a FSMS transaction:
• Left Justify Within Double Quotation Marks
Field values must be left justified within double quotation marks. Do not include leading or trailing spaces.
Use of Double Quotation Marks
You can use two accent marks (``) to give the appearance of a double quotation mark, as follows:
12,"Robert ``Bob`` Shipper"
In another example, an entry with an apostrophe is incorrect, such as:
12,"Robert O’Brien"
You can use a single accent mark (`) to give the appearance of an apostrophe, such as:
12,"Robert O`Brien"
• No Spaces Between Fields
Spaces between fields are not allowed. For example, you can format Field 12 (Recipient Contact Name) with a space inside the
quotation marks as follows:
12,"Bob Shipper"
However, if you add Field 13 (Recipient Address Line 1) to the transaction string, you cannot put any spaces between the end of
Field 12 and the beginning of Field 13. The following example shows the correct syntax:
12,"Bob Shipper"13,"1 Shipper Road"
Required and Optional Fields
To code a well-formed FSMS transaction, you must include all fields that are required to complete the logic for that transaction. You may, in
addition to these required fields, include optional fields, such as delivery instructions or reference label information, which may provide
information that is important to you. If an optional field is removed, a transaction processes successfully. If a required field is missing, FSMS
returns an error code and message.
All required fields are clearly identified in the FedEx Ship Manager® Server Transaction Coding Reference Guide tables.
Identifying Optional Fields
When you see the word “Optional” in a field description, it means that you can choose to include or not include the field in the transaction. It
is not required for the transaction to successfully complete.
Identifying Required Fields
When you see the word “REQUIRED” in a field description, it means that you must include this field in the transaction. If the field is omitted,
the transaction will fail.
When you see the word “REQUIRED*” with an asterisk (*), it means that the field is conditionally required for the transaction. Look for the
asterisk note in the description. It will tell you under which circumstances the field is required.
Identifying Defaulted Fields
Certain fields have a default value that is automatically inserted in the transaction if you do not include the field: in other words, if the field is
not present. These defaulted fields are similar to REQUIRED fields, in that their values are required for the transaction to complete.
2-24
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 2: About FedEx Ship Manager Server Transactions
Typically, defaulted field values are pre-configured during the FSMS installation and setup. If you want to override the configured value, you
must include the field in the transaction and specify a new value.
See the FedEx Ship Manager® Server Transaction Coding Reference Guide for descriptions of each field available for coding FSMS
transaction. You'll find the required or optional designation for a field in the Description column of each field table. Default values are also
indicated where applicable in a field description.
Package and Shipment Level Fields
When you create a single shipment that includes multiple packages, you must distinguish between shipment-level and package-level fields
when you create transaction strings.
Shipment-level field values apply to all packages in the shipment. Package-level field values apply only to a particular package.
Shipment-Level Field
Shipment level indicates that in a multiple-piece shipment (MPS) the value of the field applies to all packages in the shipment. Use
shipment-level fields for single transaction MPS shipments. Follow these guidelines:
• Use shipment-level fields only as a single occurrence in a single transaction that creates, confirms and ships an MPS shipment.
• Do not repeat the field for each package in a single-transaction MPS shipment.
• Do not place a shipment-level field in each ADD PIECE transaction of an Open Ship shipment.
Package-Level Field
Package level indicates that, in a multiple-piece shipment (MPS), the field value applies only to a particular package. To apply the value to
several packages, you must repeat the field for each subsequent package. Follow these guidelines:
• For single transaction multiple-piece shipments, use only one occurrence of each package-level field in the transaction.
• If you want to create an Open Ship shipment that includes multiple packages, be sure to include the package-level fields in the CREATE
transaction string.
• For any MPS Open Ship shipment that uses package-level fields, repeat each field for each package in the CREATE and ADD PIECE
transactions.
Note: Proper use of shipment-level and package-level fields apply to all FedEx shipping services.
How to Distinguish Field Level
Any field with MPS shipment-level or package-level properties is identified in the FedEx Ship Manager® Server Transaction Coding
Reference Guide.
To distinguish MPS shipment-level or package-level attributes:
1.
Use the field ID number or field name to find the field in a Transaction Coding Reference field table.
2.
Go to the Description column.
3.
If a field is required at the shipment or package level, then the first line in the Description reads Field Level: Shipment or Field Level:
Package. If there is no attribute shown, then the field has no field-level usage rules.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
2-25
Chapter 2: About FedEx Ship Manager Server Transactions
Single Piece versus Multiple Piece Transactions
Whether you include one package or multiple packages in your shipment changes the options you may have for coding a shipping
transaction.
Single Piece
The term single piece refers to a single package or single handling unit that comprises the shipment. In FSMS, single pieces are always
shipped in a single 020 Global Ship Request transaction.
For example, this transaction is a single-piece shipment with the FedEx Ground® Electronic C.O.D. (E.C.O.D.) service option selected. All
shipping information required to create the shipment and deliver the package is included in a single transaction string.
0,"020"1,"Ground E.C.O.D. w/o 3rd Party Return"11,"Recipient Company"12,"Someone"13,"20
Peachtree Rd."15,"Memphis"16,"TN"17,"38125"18,"9012639234"23,"1"50,"US"53,"100"187,"199"498,
""537,"C:\2D Bar Code"1273,"01"1274,"92"1282,"B"1660,"Y"1670,"1600"3000,"1"3014,"Y"3056,
"PO Number 0001"3062,"2"99,""
Multiple Piece
The term multiple piece refers to two or more packages or handling units that are added to a shipment to create a multiple-piece shipment
(MPS).
For FedEx Express and FedEx Ground package services, you can ship multiple pieces as a multiple-piece shipment if the pieces:
• Use the same service, bill-to instructions, packaging type and delivery instructions. For example, they must all be shipped using the
FedEx Express OR FedEx Ground package service, and if a service option is selected, such as Saturday pickup or delivery or FedEx
Home Delivery premium service, it must apply to all pieces in the shipment.
• Move together and ship on the same day from one Sender to one Recipient.
• Meet all size, weight and acceptance guidelines for the selected service.
Individual packages in a multiple-piece shipment may have different weights, dimensions and declared values. Within the U.S. only,
individual packages in a multiple-piece shipment processed through FedEx electronic shipping solutions may contain different designations
of dangerous goods (for FedEx Express) or hazardous materials (for FedEx Ground).
Each individual piece or single handling unit must have an address label showing the complete Sender and Recipient addresses.
Each piece in a multiple-piece FedEx Express Freight shipment must be palletized, stackable, banded, shrink-wrapped and able to be
moved with a forklift to form single handling units.
When a multiple-piece shipment that uses a U.S. package service attains a total shipment weight of 100 LBS for FedEx Express or 200 LBS
for FedEx Ground (with FedEx Ground Multi-weight contract rates), it is rated on a price-per-package and a price-per-total shipment-weight
basis. You are billed the lower of the two rates.
For FedEx Express, a 10-pound average minimum package weight for the shipment applies. For FedEx Ground, an average minimum
package weight for the shipment applies and varies by contract.
For FedEx Express and FedEx Ground multiple-piece shipments, you may form your FSMS transaction in two ways:
• Single transaction — in which fields that contain package data occur multiple times within the same transaction, but only once for each
individual package. This method, called Single Shot, provides a single one-shot transaction that sends complete shipment information to
FedEx in a single 020 Global Ship Request transaction.
The following is an example of a Single Shot transaction for a multiple-piece FedEx Ground shipment. Field 1670 (Package
Weight\Shipment Weight) is a multiple occurrence field. Individual packages are numbered sequentially as 1670-2, 1670-3, and so
forth.
2-26
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 2: About FedEx Ship Manager Server Transactions
0,"20"1,"5 Package Ground Single Transaction MPS"11,"Recipient Company"13,"20 Peachtree
Rd."15,"Pottstown"16,"PA"17,"19464"18,"9012639234"1670,"15"1670-2,"15"1670-3,"5"1670-4,"5"
1670-5,"5"23,"1"50,"US"187,"199"498,""537,"\\printserver\eltronlp"1273,"01"1274,"92"1282"N"
3002,"Shipment Invoice Number"3056,"Package PO 001"3056-2,"Package PO 002"3056-3,"Package
PO 003"3056-4,"Package PO 004"3056-5,"Package PO 005"3062,"2"99,""
• Multiple transactions — which create a shipping workflow in which the first transaction creates the shipment and the following
transactions add packages and confirm the shipment after all packages are added. This method is called Open Ship because the
transactions create an “open” shipment to which you can add multiple pieces over a period of time.
For examples of an Open Ship transaction, see Chapter 4: FedEx Ship Manager Server Open Ship Transactions.
International Multiple-Piece Shipments
In an international FedEx Express or FedEx Ground shipment, the weight of each individual piece cannot exceed the specified limits for the
destination country, and you cannot ship more than ten (10) commodities on one FedEx international air waybill. Each individual piece (or
single handling unit) must have a separate address label with complete Sender and Recipient addresses.
FedEx Express international multiple-piece shipments are billed based on total shipment weight.
Multiple Occurrence Fields
You can use multiple occurrence fields several times within a single transaction. You can specify a different value for each occurrence. Using
multiple occurrence fields eliminates the need to code the same field over and over simply because the input values change.
The format for a multiple occurrence field is
x–#
where
x is the field ID number that you are repeating, such as 1670.
- (dash, also known as minus sign) separates the field number from the number of repetitions.
# is the number of the repetition, such as 1, 2, 3, and so on. The maximum number of repeated fields is 999 unless otherwise noted
within a specific transaction format. If you need to use a multiple occurrence field more than 500 times in a transaction, contact your
FedEx customer support representative.
Example
For example, Field 1670 (Package Weight\Shipment Weight) is a multiple occurrence field. If the first package you add in a multiple-piece
shipment weighs 2 pounds, and the next two packages you add weigh 3 pounds and 5 pounds, then you would code Field 1670 as follows:
1670-1,"200"1670-2,"300"1670-3,"500"
This entry allows three different packages to be entered using the same field number followed by an occurrence indicator (1, 2, and 3).
You can eliminate the dash and the occurrence indicator for the first multiple occurrence field in any transaction. For example, you can
correctly code the previous example as follows:
1670,"200"1670-2,"300"1670-3,"500"
Note: Field 1670 has two implicit decimals. In the above example, 200 equals 2 pounds.
Using the Field 1670 (Package Weight\Shipment Weight) example cited previously:
Code the third occurrence as follows:
1670-3,"###"
Code the 25th occurrence of the field as follows:
1670-25,"###"
Code the 999th occurrence of the field as follows:
1670-999,"###"
v 10.6.1
FedEx Ship Manager® Server Developer Guide
2-27
Chapter 2: About FedEx Ship Manager Server Transactions
Note: When coding a multiple occurrence field, do not use any leading zeros in the occurrence indicator. Examples of incorrect coding
include the following:
1670-003,"###" and 1670-03,"###"
Single Shot versus Open Ship Shipping
You can ship single packages at one time or multiple packages in one single master shipment called a multiple-piece shipment (MPS).
Within the FedEx shipping system, multiple-piece shipments have special considerations and rules. For example, when you ship multiple
pieces in the same shipment, all the pieces in that shipment must be addressed to the same recipient.
There are two ways to ship a multiple-piece shipment (MPS):
• Single Shot — process all packages in one single FSMS transaction using the same fields repeatedly for each package.
• Open Ship — create a single 'open' master shipment and process the packages for that shipment over the course of a shipping period,
up to 7 days.
Single Shot Shipping Method
If you ship using the Single Shot method, then you must know ahead of time exactly how many pieces will be included in the shipment. The
Single Shot method requires that you use multiple-occurrence fields to provide data about each package.
For example, if you have five (5) packages to ship, then you must assign each package a number and use that number to associate the data
fields for that package. For example, to enter the package length for five separate pieces, enter the length for the first package using Field
59 (Package Length). For the second piece, use Field 59-2; for the third piece you use Field 59-3, and so forth until you enter data for the
fifth package as 59-5.
The result is a sequence of data fields that occur multiple times in the transaction, one time for each piece you include in the shipment. The
transaction code looks like this:
59,"12"59-2,"24"59-3,"18"59-4,"12"59-5"18"
where the value is the length of the piece given in inches.
Other restrictions for Single Shot also apply. For example, FedEx International Priority DirectDistribution® (IPD) and FedEx International
Priority DirectDistribution® Freight (IDF) single shot transactions must be associated with an existing FedEx International Priority
DirectDistribution or FedEx International Priority DirectDistribution Freight open shipment. See the chapters for these services for more
information.
Open Ship Shipping Method
If you use the Open Ship multiple-piece-shipment (MPS) shipping method, then the Open Ship workflow requires that you use several
transactions to create, add packages, edit and confirm the shipment. Like Single Shot, all pieces in the shipment must be sent to the same
recipient.
The Open Ship shipping method requires two fields — one to identify the Open Ship function to perform and the other to identify the
shipment to which the function applies. It is typical to have several Open Ship shipments being actively processed on the same shipping
floor. Therefore, it is important to distinguish which “open” shipment you are adding packages to throughout your shipping day.
Chapter 4: FedEx Ship Manager Server Open Ship Transactions describes the Open Ship shipping method in detail.
2-28
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 2: About FedEx Ship Manager Server Transactions
How to Read FedEx Ship Manager Server Transaction
Coding Tables
This guide contains transaction coding tables that describe the transaction fields required to code transactions. In certain cases, the table
will offer you alternative ways to perform the same functions. In most cases, however, the table is a basic description of one or more fields
and their properties, as shown in Table 2-4.
Table 2-4: Transaction Coding Table Example
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Description
Customs Currency Type
68
Max=3
N
I
FDXE
INTL
Field Level: Shipment
REQUIRED*.
Indicates the currency in which the customs value is expressed.
*Required for FedEx Express international shipments only; for FedEx
Express U.S. domestic shipments the value defaults to USD and for CA
origins to CAD.
Note: The value for this field is applied to Field 119 (Total Commodity
Customs Value) and Field 1030 (Commodity Line Item Unit Value).
For this shipment, use any method.
FDXE
FDXG
US
INTL
Freight
Field Level: Shipment for FedEx Express international shipments
Field Level: Package FedEx Express - U.S. and FedEx Ground
REQUIRED*
Total dollar amount declared or carriage value of the shipment. This field
supports the 14.2 numeric format and has two implied decimal places.
*Required for all U.S. shipments insured with FedEx.
Values must contain only numeric characters (no commas, "." or "$").
Note: All currency fields for FedEx Express Freight must be in USD.
When used to create/print a Bill of Lading (BOL) for FedEx Express
Freight, declared value cannot exceed $100,000 USD.
Note: Carriage Value cannot exceed the Customs Value.
Note: If you need to use a 14.2 numeric format, use Field 69 instead of
Field 26.
See the FedEx Service Guide for allowable limits.Carriage value per
package.
For this shipment, use any method.
If the Declared Value Per Unit is in the wrong currency, FSMS returns
Error Message 2458, 'Declared Value Per Unit in Freight Shipment Detail
- Invalid Currency.”
If the Declared Value Per Unit is the wrong amount, FSMS returns
Error Message 2459, 'Declared Value Per Unit in Freight Shipment Detail
- Invalid Amount.”
Declared Value/Carriage Value
69
v 10.6.1
Max=14.2 N
I
FedEx Ship Manager® Server Developer Guide
2-29
Chapter 2: About FedEx Ship Manager Server Transactions
In Table 2-4, Field 69 (Declared Value/Carriage Value) is available when coding both FedEx Express and FedEx Ground shipments. This is
indicated by FDXE and FDXG in the Service column. Field 68 (Customs Currency Type) is required for FedEx Express international
shipments only. Both fields have conditional requirements as indicated by an asterisk after the word REQUIRED*. The “Table Conventions”
section below describes standard annotations, acronyms and other conventions used in a transaction coding reference table.
Table Conventions
Field indicators, symbols and acronyms used in the Transaction Coding Reference tables are:
• Field ID column — contains the field identifier (ID number) for the field name shown in the row above. If the field ID indicates a hyphen
and number sign (-#), this indicates that you may use the field two or more times in the same transaction as a multiple-occurrence field.
Replace the # sign with a number to identify a specific package in the sequence of packages you add to the shipment. See “Multiple
Occurrence Fields” on page 2-27 for more information.
• Field Length column — indicates the number of characters in the field. The field length is shown as the maximum (Max) number of
characters allowed. For certain fields, the minimum (Min) field length is also shown.
• Data Type column — shows the type of data allowed for the field value. Indicators are:
–A — alphabetic characters only
–N — numeric characters only
–A/N — alphanumeric; both alpha and numeric characters allowed
–AKE — alpha, numeric, and special characters, such as the ampersand (&), allowed
• Input/Output column — tells you if a field can be included in an FSMS request transaction or is returned in an FSMS reply transaction:
–I — input in a request transaction
–O — output in a reply transaction
–I/O — field can be input in a request or output in a reply
• Service column — lists the FedEx services allowed for use with the field. Acronyms are:
–FDXE — FedEx Express
–FDXG — FedEx Ground
–FHD — FedEx Home Delivery
–FDXS — FedEx SmartPost
–All — all services
Note: FedEx Home Delivery (FHD) is the residential delivery service for FedEx Ground services. If only FHD is shown in the Service
column, then the field ID is used for FedEx Home Delivery. If FDXG is shown, then FHD is inclusive and the field also can be used in
shipping transactions to residential addresses.
• Valid For column — lists the geographical shipping regions and special services, including contract-only service, that apply to the FedEx
services listed in the Services column.
–US — United States
–CA — Canada
–MX — Mexico
–PR — Puerto Rico
–INTL — International. if INTL, may include these FedEx international services:
– FedEx International First® (IF)
– FedEx International Priority® (IP)
– FedEx International Economy® (IE)
– FedEx International Ground® (IG)
2-30
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 2: About FedEx Ship Manager Server Transactions
– FedEx International Priority® Freight (IPF)
– FedEx International Economy® Freight (IEF)
– All — U.S. domestic (US) and international (INTL) services, including Canada, Mexico and Puerto Rico
–INTL — DS (International Distribution Services):
– FedEx® International DirectDistribution Surface Solutions (IDD Surface)
– FedEx International Ground® Distribution (IGD)
– FedEx International Ground DirectDistribution® (IGDD)
– FedEx International Priority® Freight (IPD)
– FedEx International Priority DirectDistribution® Freight (IDF)
– FedEx International Economy DirectDistribution℠ Service (IED)
– All — U.S. domestic (US) and international (INTL) services, including Canada, Mexico and Puerto Rico
• Description column — contains a brief description of the field and includes valid values and conditional requirements The following
indicators are used:
–REQUIRED indicates a mandatory field for the transaction
–REQUIRED* indicates a “required if” condition
–Field Level tells you when a field/value applies to a package or an entire shipment.
–Optional indicates that the field is not required in a particular transaction. Certain fields may be either optional or required depending
on transaction context.
–Field descriptions may also include a list of the transaction methods appropriate with the use of the field. Transaction shipping
methods are:
– Single Shot — all packages are processed together in one single transaction
– Single Piece — one package in a transaction
– Open Ship — an open shipment transaction to which multiple pieces can be added throughout a shipping period
– MPS — Multiple-Piece Shipment information.
Note: In any column, “--” (double dash) indicates “not applicable”. For example, Field 1148 (Middleware Product Name) identifies a
middleware vendor’s product. Because no FedEx service is associated with this field, the Service column is marked with a double-dash as
not being applicable.
Transaction Coding Reference Guide
The FedEx Ship Manager® Server Transaction Coding Reference Guide contains reference coding tables which describe the fields for
FSMS transactions. Use the transaction coding tables in the Transaction Coding Reference Guide to help you identify which transaction
fields you need to use when developing transactions that create, ship, rate and route FedEx shipments.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
2-31
Chapter 2: About FedEx Ship Manager Server Transactions
Transactions Do More Than Ship
The concepts up to this point in this chapter primarily describe the shipping transaction 020/120 Global Ship Request/Reply. FedEx Ship
Manager Server transactions are versatile and flexible and do much more than ship.
Rates, Rate Quotes and List Rates
Calculate your rate using the instructions in the FedEx Services Guide and by using the Rate Tools at http://fedex.com/us/rates2009/. You
can get rate quotes and view rates by service or delivery zone. As a FedEx account holder, you can log on for an account-specific courtesy
rate quote or a customized rate guide.
You can also request both account-specific and courtesy list rates for FedEx Express, FedEx Ground and FedEx® International
DirectDistribution Surface Solutions shipments using the FSMS 020 Global Ship Request transaction or 025 Rate Available Services
Request Transaction.
As part of its revenue management, FSMS supports a variety of rating options, such as list rates for FedEx Express and FedEx Ground,
international courtesy rating, bundling, dim weight calculations and Multi-weight discounts. These are described in each chapter by service.
Earned Discount Pricing Program
The Earned Discounts Pricing Program awards discounts to customers who meet predetermined revenue levels and/or shipping criteria.
You earn additional discounts as you increase shipping activity or meet specific shipment characteristics. To participate in the Earned
Discounts Pricing Program, contact your FedEx Account Executive. If you participate in the Earned Discounts Pricing Program, all FSMS
transactions with a rate quote will return Field 1992 (Earned Discount Amount).
Note: Earned Discounts will be returned in the 120 and 125 transactions for FSMS version 8.4 and higher.
Routing and Time-In-Transit
FedEx Ship Manager Server returns route and time-in-transit information when you request it using the 020 Global Ship Request
transaction. In FSMS, the term route is used specifically for FedEx Express service, and the term time-in-transit for returned information for
the FedEx Ground service.
FedEx Ship Manager Server returns the following information:
• FedEx Express — Route to and from any origin and destination pair for any FedEx Express shipment. A Route Request also returns the
service commitment.
• FedEx Ground or FedEx Home Delivery — Time-in-Transit from origin to destination for any FedEx Ground or FedEx Home Delivery
shipment.
You request route or time-in-transit information in two ways:
• Use Field 1234 (Rate/Route/Time-in-Transit Flag) in a 020 Global Ship Request
• Use Field 541 (Open Ship Flags) in an Open Ship 020 Global Ship Request
For instructions on how to get rates using Field 541 in an Open Ship transaction, see Chapter 4: FedEx Ship Manager Server Open Ship
Transactions in this guide.
Note: Performing a route request for a FedEx Express shipment or a time-in-transit for a FedEx Ground shipment returns all the necessary
information needed to add information to a FedEx label and create a custom label if a Pre-assigned tracking number is included in the
Request transaction.
2-32
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 2: About FedEx Ship Manager Server Transactions
Package and Shipment Tracking
The tracking number assigned to your shipment or individual packages is your way to uniquely identify it as it moves through your shipping
process and the FedEx shipping system.
Tracking numbers are assigned separately to your FedEx account for FedEx Express and FedEx Ground services. You can Pre-assign
tracking numbers to packages if you need to send them to customers ahead of shipping their order.
Close Shipment at End-of-Day
When you end your shipping day, you must perform an 007 End-of-Day Close Request transaction to transmit shipping data to FedEx. You
can use the 007 End-of-Day Close Request transaction to either start the Close operation for a meter or to query the meter’s Close status,
depending on the value you set in Field 548 (Close Status Request Flag).
You can perform a separate Close Request for FedEx Ground and FedEx Express shipments. You can also close all meters with one 007
transaction using Field 2413 (Close All Meters Flag).
Example 1 — End-of-Day Close Request Transaction
The following example shows an 007 End-of-Day Close Request transaction for a FedEx Ground shipment:
0,"007"1,"FedEx7"498,"4147"3025,"FDXG"99,""
Example 2 — End-of-Day Close Reply Transaction
The following example transaction shows the corresponding 107 End-of-Day Close Reply:
0,"107"1,"FedEx7"498,"4147"3025,"FDXG"99,""
Submitting Transactions
Batching Transactions in a File
Batch processing is the batch execution of transaction strings in files or programs that, once started, run and complete without human
intervention. Batch processing allows a shipper to build FedEx Ship Manager shipment transactions and send them together in a single file
or in several batch files to the back-end FedEx shipping server. The back-end server processes the transactions together as a single batch
and returns the output to your local FSMS client.
If you choose to batch transaction files, then you can configure the FSMS application to process transactions during scheduled periods.
FedEx Ship Manager Server can be set up to automatically check for and process new transaction files.
Enabling Batch Processing
Complete the following steps to enable batch processing.
To enable batch processing:
1.
Edit the client.ini file located in FedEx\FedEx_Cfg directory.
2.
In the TRANSFILE section, edit the Path=<entry> to include the name of the directory where you want to store transactions.
For example, if the directory is C:\batch\, code the complete Path=<entry> as follows:
Path=C:\batch\
The actual name of the transaction file is not needed, only the name of directory where you want to store transactions. The transaction
file can have any file name, but must end with the .in extension, as follows:
Trans.in
v 10.6.1
FedEx Ship Manager® Server Developer Guide
2-33
Chapter 2: About FedEx Ship Manager Server Transactions
The input batch file can be stored on the FSMS client or on any system you designate.
3.
Save and exit the client.ini file.
4.
Edit the server.ini file located in the FedEx\FedEx_Cfg directory.
5.
In the DNLD section, change the value of the interval entry to 10000 (this value represents the number of milliseconds the given
directory is checked for files with a .in extension). The complete interval entry must be coded as follows: interval=10000
6.
Save and exit the server.ini file.
Restarting FedEx Admin Service
After you enable batch processing, be sure to restart the FedEx Admin Service.
To restart the FedEx Admin Service:
1.
Right-click the My Computer icon and click Manage. The Computer Management screen displays.
2.
Click Services and Applications.
3.
Click Services. All Services display in the right panel of the window.
4.
Click the FedEx Admin service. The line highlights.
5.
Do one of the following:
a. If the service is running, click Restart the service.
b. If the service is not running, click Start the service.
Disabling Batch Processing
Follow these steps to disable batch processing on your FSMS system.
To disable batch processing:
1.
Edit the server.ini file.
2.
Edit the interval entry in the DNLD section back to 0000. The complete interval entry must be coded as:
interval=0000
3.
Save and exit the server.ini file.
4.
Restart the FedEx Admin Service as described in the preceding section.
Monitoring Input Batch Files
After you complete the preceding steps, the FedEx Admin Service monitors the directory you designated in the client.ini file every ten
seconds for any input transaction files.
When FSMS detects an input batch file, it processes the file and creates an output file and a copy of the original in the same directory.
Table 2-5 shows the input file, the output file, and a copy of the original:
Table 2-5: Batch File Processing
batch1.in
Input file processed by FSMS, resulting in the output file batch1.out
batch1.out
Output file generated by FSMS from batch1.in
batch1.old
FSMS copies the original input file (batch1.in) to this file
2-34
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 2: About FedEx Ship Manager Server Transactions
Note: Make sure that input files do not contain an extra line or space at the end of the transactions. This causes processing errors. The last
field at the end of the input file must be:
99,""
Error Messages and Troubleshooting
If FSMS returns an error condition in a transaction, you may look up the error code in the Error Code section of the FedEx Ship Manager®
Server Transaction Coding Reference Guide.
FedEx Ship Manager Server Log File
To help you troubleshoot an error, FSMS creates a log file of all transactions processed, and logs the date and time of each transaction.
Non-critical transaction events are logged to an Application Event log file named FXRS_LogFile.log located in
C:\FedEx\FedEx_EventLogs. The maximum size of the log file is 1MB. If the log file exceeds 1MB, FSMS renames the file to
<current_date_time>.log and creates a new FXRS_LogFile.log file for logging messages.
Note: The FSMS log file is separate from the Application Log of the Event Viewer. The Event Viewer Utility provides information in the
Application Log, Security Log and System Log.
You can determine how long log files are stored on your local FSMS client by selecting a retention period in the FSMS Configuration Utility.
Log files older than a configured retention period are automatically deleted. The retention period of a log file can be set from a minimum of
seven (7) days to a maximum of thirty (30) days.
Note: If you do not set a retention period, then FSMS deletes any FSMS transaction log file that is older than three (3) days. Only log files
created by the same FSMS version are deleted.
To enable the FedEx Ship Manager Server log file:
1.
Open the FSMS Configuration Utility.
2.
Click the System Settings tab.
3.
Check the Transaction Log box to enable logging of transactions.
4.
Use the drop-down box to select how many days (1, 2, or 3) the log file will record transaction data.
5.
Click Apply to apply your changes or click Apply & Exit to apply your changes and close the utility window.
To set retention period for Application Event log file:
1.
Open the FSMS Configuration Utility.
2.
Click the Advanced Settings tab.
3.
In FedEx Ship Manager Server Logging Retention Period, select the number of days you want the log file to run.
4.
Click Apply to apply your changes or click Apply & Exit to apply your changes and close the utility window.
For additional assistance, contact FedEx Support at 1.800.GoFedEx 1.800.463.3339 or see your FedEx account executive.
Next Steps
FedEx Ship Manager Server allows you to develop transactions for almost every shipping need your integration requires. The information in
this chapter gets you started by explaining what an FSMS transaction is and how FSMS fields are used to define the shipping requests your
application submits to FedEx.
Now that you are familiar with FSMS transaction basics, you can begin building transactions for your application.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
2-35
Chapter 2: About FedEx Ship Manager Server Transactions
The following chapters in this guide describe the service rules and transaction syntax that must be adhered to in order to develop integrated
applications for FedEx shipping operations. The information is presented for each of the FedEx services supported by FSMS.
To begin building your application, go to the chapter in this guide related to the specific FedEx service(s) that your company will be using to
ship. If the service you plan to use supports the Open Ship shipping method, be sure to read Chapter 4: FedEx Ship Manager Server Open
Ship Transactions.
Table 2-6: FedEx Shipping Services
To learn about FedEx shipping for...
Read...
FedEx Express U.S. services
Chapter 5: Coding Transactions for FedEx Express U.S. Service
FedEx Ground U.S. services
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
FedEx SmartPost
Chapter 7: Coding Transactions for FedEx SmartPost
FedEx Express international services
Chapter 9: Coding Transactions for FedEx Express International Services
FedEx International Ground services
Chapter 10: Coding Transactions for FedEx International Ground Services
FedEx® International DirectDistribution Surface Chapter 11: Coding Transactions for FedEx International DirectDistribution Surface
Solutions
Solutions
FedEx International Priority DirectDistribution
Chapter 12: Coding Transactions for FedEx International Priority DirectDistribution
To learn about FedEx labels, continue to Chapter 3: FedEx Ship Manager Server Label and Form Transactions.
2-36
FedEx Ship Manager® Server Developer Guide
v 10.6.1
CHAPTER 3: FEDEX SHIP MANAGER SERVER LABEL
AND FORM TRANSACTIONS
Every package tendered to FedEx® must have an attached label. Labels move with the shipped unit and must be human and machinereadable. For this reason, FedEx provides standard labels and requires a strict adherence to label specifications for all custom-designed
labels. Many of the FedEx shipping operations use automated devices and require that labels be correct and exact to all FedEx label
requirements. This ensures efficient handling and routing of your shipments and prevents delays.
This chapter provides a basic introduction to FedEx labels as they relate to FedEx Ship Manager® Server (FSMS) in the following sections:
• FedEx Ground Hazardous Materials OP-900 Form/Report
• FedEx Hazardous Materials Form OP-900LG
• FedEx Express Shipper’s Declaration for Dangerous Goods Form
• About FedEx Labels
• Label Types and Formats
• Labels and Doc-Tabs
• How to Print Reference Information on Labels
• How to Customize Labels
• Label Transaction Samples
• FedEx Label Samples
FedEx Ground Hazardous Materials OP-900 Form/Report
The OP-900 is a laser printed form. The OP-900B is a dot-matrix printed form.
If a shipper sends either or both the Dangerous Goods HazMat Technical Name field and the Subsidiary Risk field, the values provided by
the shipper print on the OP-900 form(s). All information provided in a field will print on the OP-900 form(s) without truncation. FedEx Ship
Manager Server automatically prints the parentheses around the Dangerous Goods HazMat Technical Name value on the OP-900 form(s).
Note: Hazardous materials customers need to enter the Subsidiary Risk in the correct format for printing on the OP-900 form. For the
Subsidiary Risk field, there may be 2 Subrisks for the UN ID: Subrisk 1 and Subrisk 2. This information must be separated by a comma
when you enter it in the field. FedEx Ship Manager Server does not validate the format for these fields.
Formats for Hazardous Materials OP-900 Label
FedEx supports two printed formats:
• OP-900 “Laser” — for laser printer
• OP-900/OP-900B “Form Feed” — for dot matrix printer
Select the form type “laser” when you want to print the OP-900 form label and select “formfeed” to print the OP-900B label.
Note: You must enable “Ground HazMat” on the Meter Settings tab in the FedEx Configuration Utility before you can print hazardous
materials labels.
Printing Information on Ground OP-900/OP-900B Forms/Reports
To ship a FedEx Ground® domestic North America regulated shipment, pass the 020 Global Ship Request fields listed in Table 3-1.
v 10.6.1
FedEx Ship Manager® Server Installation and Configuration Guide
3-1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-1: Fields for Printing Information on the Ground OP-900/OP-900B Forms
Field Name
Field ID Values
Response
Dangerous Goods
Regulations Indicator
1900
Value set to N to designate the shipment as a North America regulated
shipment (FedEx Ground only).
Prints specific information
on OP-900/OP-900B form.
UN Identification
Number
451
Enter valid UN ID number
Required if 1493 = Y and printing the FedEx Ground Hazardous Materials
Shipping Paper, OP-900.
Dangerous Goods
Packing Type
461
Enter packing type used for the dangerous goods shipment. See Section
5 of the IATA DG Regulations.
Offeror Name
4939
Designates an Offeror Name (entity or person) or Shipper Contact Name Prints specific information
to be used by FedEx Ground Operations and the U.S. DOT as a contact on OP-900/OP-900B form in
in case of an emergency situation with a Hazardous Materials Package. versions 10.6.1. and higher.
A recent U.S. Department of Transportation regulatory change requires that the Offeror Name (Shipper) print on the HazMat forms. The
offeror name is the entity or person to be contacted during shipping in case of emergency. All FSMS versions 10.6.1 and newer allow the
passing of the Offeror Name (entity of person) (Field 4939) in the 020/120 Global Ship Request/Reply Transaction. Existing Ground HazMat
customers may either upgrade to version 10.6.1 or write on the existing OP-900 Form(s) the Offeror Name (entity or person) or Shipper
Contact Name to be notified in case of emergency.
While the OP-900 and OP-900B forms have not been modified, FSMS (10.6.1. and higher) allows the offeror name to be passed in the
020/120 Global Ship Request/Reply using Field 4939.
Note: Failure to provide the accurate information for the Offeror/Shipper Name, whether passed in the transaction, defaulted along with the
Emergency Contact Number, or written in, may result in fines being incurred by the customer from the U.S. Department of Transportation.
The Offeror Name (entity or person) will print in the “FedEx GROUND SHIPPER NUMBER” area of the OP-900 and OP-900B Forms. See
Table 3-2, Figure 3-1 and Figure 3-2. To configure the OP-900 form as shown, use the Report Settings tab on the FSMS Configuration
Utility. See “Designating a Printer Path for OP-900 Forms” on page 3-8.
Figure 3-1: OP-900 Form
3-2
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Figure 3-2: OP-900B Form
Printing the HazMat Class on the OP-900 Form
To print the HazMat Class on the OP-900 form, pass the fields listed in Table 3-2 in a 020 Global Ship Request transaction.
Table 3-2: Fields for Printing HazMat Class on the OP-900 Form
Field Name
Field ID
Values
Response
DOT Hazard Class or 492
Division Number
Required for printing the FedEx Ground
Hazardous Materials Shipping Paper, OP900.
HazMat Class, Subsidiary Risk 1, and Subsidiary 2
print on the OP-900 form for FedEx Ground. Total
maximum length of 14 characters.
Subsidiary Risk
Subsidiary Risk 1, and Subsidiary Risk 2
1902
Hazardous Materials OP-900 Laser Form
The OP-900 Laser form prints the following FSMS field values in the first line of the Hazardous Materials Description and Quantity box. If a
field is passed without a value, that field is not printed.
Fields print in the following order separated by commas:
First Line
Table 3-3: OP-900 Form First Line Data
v 10.6.1
Order
Field Name
Field ID
1
HazMat Package Quantity and Type
4903
2
Identification Number
451
3
DOT Shipping Name of Material
1903
4
DOT HazMat Class or Division Number
492
5
Packing Group
489
FedEx Ship Manager® Server Installation and Configuration Guide
3-3
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Second or Separate Line
Table 3-4: OP-900 Form Second Line Data
Order
Field Name
Field ID
1
HazMat Quantity
466
2
HazMat Unit of Measure
471
3
Type DOT Label(s) Required, LTD. QTY. or
Exemption Number
3072
Note: There is no comma between Quantity and Unit of Measure when these values print on the label.
The OP-900LL form has been modified to add a “SHIPPER NAME” area in the upper right corner. When printing, FSMS shall add the
Offeror Name or the Shipper Company Name in the new area, whichever data is used/defaulted in the 020/120 Global Ship Request/Reply
Transaction. If the Offeror Name is not provided in the transaction, the package shall be defaulted to the Shipper Company
Name. If the Shipper Company Name is not provided in the transaction, then the package shall be defaulted to the default Shipper Company
Name in the FedEx configuration. Figure 3-3 and Figure 3-4 show the front and back of the OP900LL Form.
Figure 3-3: OP-900LL Form - Front (8-1/2" x 11")
3-4
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Figure 3-4: OP-900LL Form - Back (8-1/2" x 11")
v 10.6.1
FedEx Ship Manager® Server Installation and Configuration Guide
3-5
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Coding Data on the Laser Form for Hazardous Materials OP-900 Form
The fields listed in Table 3-5 map to information on the OP-900 Laser Form.
Table 3-5: OP-900 Laser Form Fields
Field Description
Field ID
Account Number
10
Signature1
32
Tracking Number
29
Ship Date
24
HazMat Emergency Contact Number
484
U.S. Department of Transportation (DOT) Shipping Name of Material
1903
DOT Hazard Class or Division Number
492
HazMat Package Quantity and Type
4903
Identification Number
451
HazMat Packing Group
489
Type DOT Label(s) Required, Ltd. Qty., or Exemption Number
3072
HazMat Quantity
466
HazMat Unit of Measure
471
Offeror Name
4939
Note: If the FSMS transaction does not pass in the Sender Name, the Signature field will be blank on the form and require a manual
signature.
Fields for Laser Format for OP-900 Form
Use the 020 Global Ship Request transaction to pass fields that specify the laser format for the Hazardous Materials OP-900 Form, as
described in Table 3-6.
Report Code ‘041 (Ground OP-900)’ value with Field 1680 set to 02 (laser) specifies the OP-900LL form. Field 4903 (HazMat Package
Quantity and Type) describes the number and type of packaging used in the hazardous materials shipment.
Table 3-6: Fields for Laser Format for Hazardous Materials OP-900 Form
Transaction: 020/120 Global Ship Request/Reply
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I/O
Description
Report Code
1373
3-6
Max=3
FDXG
All
Optional
Detailed package content information for Priority Alert Service.
Maximum of two occurrences.
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-6: Fields for Laser Format for Hazardous Materials OP-900 Form (Continued)
Transaction: 020/120 Global Ship Request/Reply
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
DG Printer Form Type
1680
Max=2
N
I/O
FDXG
All
Optional
Indicates the type of printer used to print dangerous goods (DG)/
hazardous materials (HazMat) forms.
You must match the field occurrence number (for example, 1680-1) with
the occurrence number of Field 1373 (Report Code) for the type of form
you request.
Valid values are:
01 — Form Feed (default)
02 — Laser
Note: While you can designate a printer to print DG or HazMat forms
using Field 568 (Report Directory), Field 1680 allows you to designate a
separate printer for this form type if you use a pin-feed or laser printer
specifically designated as your “Dangerous Godson “HazMat Form”
printer. Setting up a separate printer using Field 1680 eliminates the need
to change paper stock in your report printer.
For U.S. dangerous goods shipments, use this field in single shot and
Open Ship transactions. For international dangerous goods shipments,
use in single piece transactions. For a hazardous materials shipment, use
in single piece transactions only.
HazMat Package Quantity and Type
4903-#
Min=1
Max=20
A/N
I/O
FDXG
All
Field Level: Package.
Number and type of packaging used for the hazardous materials
(HazMat) shipment.
Valid value is free-form text.
AKE
I/O
FDXG
US
Field Level: Package
Optional
Designates an Offeror Name (entity or person) or Shipper Contact Name
to be used by FedEx Ground Operations and the U.S. DOT as a contact
in case of an emergency situation with a Hazardous Materials Package.
Offeror Name
4939-#
Min=1
Max=35
Note: Failure to provide the accurate information for the Offeror/Shipper
Name, whether passed in the transaction or defaulted along with the
Emergency Contact Number, may result in fines being incurred by the
customer from the U.S. Department of Transportation.
If this field is not passed in a HazMat transaction or is passed in blank,
FSMS uses Field 32 (Sender Contact Name) associated with the meter
at ship time and customers receive informational Message 3101, “This
type of regulated shipment requires the Offeror Name (entity or person)
that is registered with the Emergency Response Information provider.
Since Offeror Name (entity or person), Tag 4939, was not provided, the
Shipper Name will be used,” and the shipment will be successful.
v 10.6.1
FedEx Ship Manager® Server Installation and Configuration Guide
3-7
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Designating a Printer Path for OP-900 Forms
Designate a printer path in the 070/170 Configuration /Meter Query Request transaction by passing Field 538 (Report Printer ID) with other
required fields for:
• OP-900LL form — when ‘Laser’ is designated as the Form Type
• OP-900B form — when it is designated as the Report Type
Note: Only one hazardous materials OP-900 form type may be active at a time. The OP-900LL, OP-900B and OP-900 forms are
independent of each other.
Configure Hazardous Materials OP-900LL Report
To configure the HazMat OP-900LL Report
1.
Open the FedEx Configuration Utility.
2.
Click the Report Settings tab.
3.
In the left pane, expand DG.
4.
Select Ground OP-900.
5.
In the Form Type field, use the drop-down menu and select one of the following options:
–FormFeed (default)
–Laser
6.
In the Printer field, if you selected ‘FormFeed’, choose a dot matrix printer device. If you selected ‘Laser’, choose a laser printer device.
Use the Printer button on the right to browse for available printers on your system.
7.
Click Apply or Apply & Exit.
Printing DOT HazMat Class and Subsidiary Risk
The DOT HazMat Class (Field 492) and Subsidiary Risk (Field 1902) information print together on the OP-900 in the following order:
• First — Information in the U.S. Department of Transportation (DOT) HazMat Class field
• Second — Information in the Subsidiary Risk field enclosed in parentheses
Note: Hazardous materials customers need to enter the DOT HazMat Class.
Formats for DOT HazMat Class and Subsidiary Risk Fields
The following tables show both correct and incorrect ways to specify the format for U.S. Department of Transportation (DOT) HazMat Class
and Subsidiary Risk fields in a 020 Global Ship Request transaction. All examples assume that the UN identification number is UN1045, the
Class is 2.3, Subrisk 1 is 5.1 and Subrisk 2 is 8.
Example 1: Correct Format — Information prints as 2.3(5.1,8)
492,"2.3"1902,"5.1,8"
Table 3-7: HazMat Class and Subsidiary Risk Fields: Example 1
3-8
Field ID
Field Name
Format
492
DOT HazMat Class
492,"2.3"
1902
Subsidiary Risk
1902,"5.1,8"
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Example 2: Correct Format — Information prints as 2.3((5.1),(8))
492,"2.3"1902,"(5.1),(8)"
Table 3-8: HazMat Class and Subsidiary Risk Fields: Example 2
Field ID
Field Name
Format
492
DOT HazMat Class
492,"2.3"
1902
Subsidiary Risk
1902,"(5.1),(8)"
Example 3: Incorrect Format — Information prints as 23(518)
492,"23"1902,"518"
Table 3-9: HazMat Class and Subsidiary Risk Fields: Example 3
Field ID
Field Name
Format
492
DOT HazMat Class
492,"23"
1902
Subsidiary Risk
1902,"518"
FedEx Hazardous Materials Form OP-900LG
The new HazMat form allows the shipper to list up to three commodities per package. It is available in dot matrix, tractor feed and multi-part
formats. The format and size is different from other OP-900 forms. The OP-900LG form can be set up on the Report Settings tab for each
meter that will print this form.
Note: Three commodities per package only applies to HazMat commodities. ORM-D, Dry Ice, SQE, and non-hazardous lithium batteries are
unlimited quantities per package.
Form OP-900LG also supports an electronic signature field. See Figure 3-5.
The OP-900LG form has been modified to change the “PACKAGE REFERENCE” area to “SHIPPER NAME.” Ground will accept Offeror
Name (entity or person) or Shipper Contact Name data printed in the “PACKAGE REFERENCE” section until old form supplies are
exhausted.
A shipment can contain a mix of multiple commodities in a package. The overriding definition of the shipment contents follows a hierarchy
based on contents. The hierarchy is:
• HazMat
• ORM-D
• SQE
• Dry Ice
• Non-hazardous Lithium Battery
Note: This is only for MPS shipments since these commodities cannot be shipped together. See Table 3-10 on the bottom of page 3-12.
Note: The presence of a non-hazardous lithium battery still must be identified by the customer in addition to the requirements listed above.
v 10.6.1
FedEx Ship Manager® Server Installation and Configuration Guide
3-9
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Figure 3-5: FedEx Hazardous Materials OP-900LG Form
A shipment containing at least one HazMat commodity is considered a HazMat shipment, taking precedence over other types of
commodities, which impacts the following:
• Shipping Label — HazMat Service Code and bolded information will print on the label.
• OP-900 Form — shall be produced for HazMat commodity.
• OP-950 Report — shall contain information about the HazMat commodities in the piece.
• Signature Service — HazMat signature service rules will be applied to the package.
Table 3-10 shows how the mixed commodities can be packaged.
Table 3-10. Commodity Mixtures for HazMat Packages
Package Classification
HazMat
ORM-D
Dry Ice
Small Qty Exception
Non-hazardous Lithium Battery
HazMat
Yes
No
Yes
No
Yes
ORM-D
No
Yes
Yes
No
Yes
Dry Ice
Yes
Yes
Yes
Yes
Yes
Small Qty Exception
No
No
Yes
Yes
Yes
Non-hazardous Lithium Battery
Yes
Yes
Yes
Yes
Yes
Note: HazMat and ORM-D and/or HazMat and Small Quantity Exception are not allowed within the same piece. However, all five commodity
types are allowed as separate pieces in a Multi-Piece-Shipment.
A ground HazMat shipment may not be held at location upon delivery.
The OP-900LG form is available on the Report Settings tab at the User, User View, Field, Support and Development access levels under the
DG drop down menu. The “Copy To All Meters” and “Copy To All Reports” buttons are available to all HazMat enabled meters. The
OP-900LG is available in all four format options: RTF, TXT, PDF, and DOC. The Printer free form text entry path is also available for the
OP-900LG form.
3-10
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
FedEx Express Shipper’s Declaration for Dangerous
Goods Form
FedEx Ship Manager Server provides the ability to print the Shipper’s Declaration for Dangerous Goods form. You can print the Shipper’s
Declaration for Dangerous Goods form as a multi-ply form (FedEx 1421C form) or on plain paper with red hatchings (FedEx LZR DG DEC
FORM). The multi-ply form is printed on a pin-feed printer. The plain paper form can be printed on 8-1/2' x 11' or A4 paper.
The FedEx Express® Shipper’s Declaration for Dangerous Goods Form (FedEx 1421C or FedEx LZR DG DEC FORM) is required for all
dangerous goods shipping (both domestic and international). If you choose to use the Open Ship shipping method and print the Shipper’s
Declaration for Dangerous Goods Form (FedEx 1421C or FedEx LZR DG DEC FORM), only the dangerous goods information that is
associated with the CREATE function will print. The Shipper’s Declaration for Dangerous Goods Form (FedEx 1421C or FedEx LZR DG
DEC FORM) is printed at the shipment level and generated when the shipment is confirmed and/or processed by FSMS. FedEx Ship
Manager Server gives you the ability to print multiple pages.
Only one Shipper’s Declaration for Dangerous Goods Form (FedEx 1421C or FedEx LZR DG DEC FORM) is allowed per shipment. The
information on the form is taken from the first dangerous goods package within the shipment. The data entered on the form includes:
• Shipper
• Consignee
• Air Waybill Number
• Number of Pages in Form
• Shipper’s Reference Number
• Transport Details (section)
–Airport of Departure
–Airport of Destination
–For aircraft type — Enter “Passenger and Cargo Aircraft Only” or “Cargo Aircraft Only”
• Shipment Type (section)
• Additional Handling Information
• Nature and Quantity of Dangerous Goods (section)
• Emergency Response Telephone Number
• Name and Title of Signatory
• Signature
• Place and Date
To configure the Shipper’s Declaration for Dangerous Goods Form (FedEx 1421C or FedEx LZR DG DEC FORM), use the Report Settings
window of the FSMS Configuration Utility.
See the FedEx Ship Manager® Server Installation and Configuration Guide for instructions. See also “Configuring Printers for Labels, Forms
and Reports” on page 3-17 in this guide.
Figure 3-6 shows the Shipper’s Declaration for Dangerous Goods Form (FedEx 1421C form).
v 10.6.1
FedEx Ship Manager® Server Installation and Configuration Guide
3-11
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Figure 3-6: FedEx Shipper’s Declaration for Dangerous Goods Form (FedEx 1421C Form)
Note: The back of the FedEx 1421C form contains guidelines for completing the form.
Figure 3-7 is a sample of the FedEx LZR DG DEC FORM. Shipping information is printed by the laser printer on this blank form.
3-12
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Figure 3-7: FedEx Shipper’s Declaration for Dangerous Goods Form (FedEx LZR DG DEC FORM)
v 10.6.1
FedEx Ship Manager® Server Installation and Configuration Guide
3-13
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
About EPRRQ Labels
EPRRQ labels are required for dangerous goods Excepted Package Radioactive (EPRRQ) shipments. No Dangerous Goods Human
Readable Indicators (IDG or ADG) are printed in the ASTRA section of the label for EPRRQ shipments that are not considered to be a
dangerous goods shipment.
Excepted package radio actives must have a reportable quantity (RQ) and require a modified version of the Shipper’s Declaration in order to
ship. EPRRQ commodities are only permitted when and where “inaccessible dangerous goods” are permitted and IATA Validation occurs.
Ship EPRRQ commodities using these FedEx Express services: FedEx® International DirectDistribution Surface Solutions (CA and MX),
International Priority DirectDistribution and International Priority DirectDistribution Freight.
For shipments “All Packed in One,” calculation and printing of Field 1331 “Q” value (Q — Excepted Package Radioactive Reportable
Quantity [EPRRQ]) will be excluded from the Shipper’s Declaration for Dangerous Goods Form (FedEx 1421C or FedEx LZR DG DEC
FORM) if:
• One of the commodities is Dry Ice (UN 1845) or
• Columns H, J, and L indicate “No limit” or
• Only one commodity qualifies for calculation
Shipper’s Declaration for Dangerous Goods Form (FedEx 1421C or FedEx LZR DG
DEC FORM) for EPRRQ
FedEx Ship Manager Server prints the FedEx Shipper’s Declaration for Dangerous Goods Form (FedEx 1421C or FedEx LZR DG DEC
FORM) for EPRRQ shipments.
To print the Shipper’s Declaration for Dangerous Goods Form (FedEx 1421C or FedEx LZR DG DEC FORM):
You must set up the 1421C form in the Report Settings tab of the FSMS Configuration Utility and pass Field 1493 (DG/HazMat Form Print
Flag) set to Y in the 020 Global Ship Request transaction.
You may use the Shipper’s Declaration for Dangerous Goods Form (FedEx Form 1421C or FedEx LZR DG DEC FORM) for EPRRQ with
the two standard form types: form feed (FedEx 1421C) and laser (FedEx LZR DG DEC FORM).
About FedEx Labels
FedEx Ship Manager Server supports the configuration and printing of labels for shipping packages as part of a shipment.
FedEx allows two types of labels to be used:
• FedEx standard label — service-specific labels provided by FedEx
• Custom labels — customer-designed labels that must be approved by FedEx prior to use
FedEx Standard Labels
FedEx labels are designed to detailed specifications and should not be altered. Standard labels are readable by FedEx automation devices
and ensure the efficient processing of your shipments to their final destination.
If you need to print business or shipping-related information on a label, FedEx allows you to customize certain sections of a standard label.
You may customize reference information on a standard label. You may also set up the doc-tab area of a label to print information specific to
your shipping needs.
3-14
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Custom Labels
Creating a custom label requires an in-depth knowledge of FedEx label specifications. After you design a label, you must submit your labels
to FedEx for detailed review and testing as part of a standard approval process before you are authorized to use them on your shipments.
If you want to create custom labels, contact your FedEx account executive.
For information about Open Ship labels, see Chapter 4: FedEx Ship Manager Server Open Ship Transactions.
Label Types and Formats
FedEx Ship Manager Server supports the label types listed in Table 3-11.
Table 3-11: FSM Server Label Types
Label Type
Description
Thermal
Print shipping labels for all shipping types (FedEx Express®, FedEx Ground®, and international) using a
variety of thermal label printers. The following thermal label sizes are supported by FSMS: 4" x 6", 4" x 8", 4"
x 9" Thermal labels are available with document tabs (doc-tabs) that can be configured with shipment details.
Laser
FSMS generates a laser printable label. Labels printed with a laser printer are generated by FSMS in PDF
format and do not need to be scaled or resized. Laser labels are available for both FedEx Express and FedEx
Ground shipping and may be written to a label buffer.
Custom
Customize the shipping label with your own graphic or create a custom label by using the FSMS Custom Label
Generator Utility. “Customizing a Thermal Label” on page 3-44. A custom label must meet FedEx label
specifications.
Multi-Ply Air Waybills
Print preprinted multi-ply labels for FedEx Express International shipping. This feature is supported by FSMS
since some countries do not allow a thermal or laser air waybill package to be processed through their
customs clearance.
Thermal Labels
FedEx Ship Manager Server provides a graphic file of the FedEx Express and FedEx Ground thermal shipping label that you can position on
your shipping documentation instead of creating a custom label.
For example, if you generate a packing list, you may use the top portion of the form for packing information and position both a 4" x 6"
shipping label and a 4" x 6" return label on the bottom portion of the form by requesting a thermal label graphic.
The thermal label graphic can be generated for the 4" x 6", 4" x 8", and 4" x 9" thermal label formats and can be received as either a PNG
(Portal Network Graphics) or a PDF (Portable Document Format) file type.
Depending on whether you choose the PNG or PDF format, sizing requirements may apply.
There are two ways to configure printers for printing thermal labels.
• Configure settings on the Label Settings tab of the FSMS Configuration Utility. The printer you select becomes the default printer for
printing thermal labels.
• Specify the printer ID and type in shipping transactions. This overrides the default printer setting. See “Specifying Thermal Printers in
Transactions” on page 3-18 in this guide.
See the FedEx Ship Manager® Server Installation and Configuration Guide for information about thermal printers supported by FedEx and
how to set up a default thermal printer using the FSMS Configuration Utility.
v 10.6.1
FedEx Ship Manager® Server Installation and Configuration Guide
3-15
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Laser Labels
You can print FedEx labels on a laser printer. FedEx Ship Manager Server generates a laser printable label in PDF format which does not
need to be scaled or resized. Laser labels are available for both FedEx Express and FedEx Ground shipping and may be written to a label
buffer.
There are two ways to configure laser printers for your FSMS meter.
• Configure settings on the Label Settings tab of the FSMS Configuration Utility. The printer you select becomes the default printer for
printing laser labels.
• Specify the printer ID and type in shipping transactions. This overrides the default printer setting. See “Specifying Laser Printers in
Transactions” on page 3-19.
See the FedEx Ship Manager® Server Installation and Configuration Guide for information about FedEx supported laser printers and how to
set up a default laser printer using the FSMS Configuration Utility.
Multi-Ply Air Waybills
FedEx Ship Manager Server supports printing preprinted multi-ply labels for FedEx Express International shipping. This feature is supported
by FSMS because some countries do not allow a thermal or laser air waybill to be processed through Customs Clearance. The multi-ply air
waybill is available in three types:
• Form 306 — FedEx International Air Waybill with preprinted tracking numbers
• Form 307 — FedEx International Air Waybill without preprinted tracking numbers
• Form 362 — French language FedEx International Air Waybill without tracking numbers
Label Formats
FedEx Ship Manager Server provides these graphic file formats for printing labels or creating images that you can position on your shipping
documentation:
• PNG — thermal and laser labels
• PDF — thermal and laser labels
• DIB — laser labels
PNG Labels
FedEx Ship Manager Server provides PNG (Portable Network Graphics) for FedEx Express and FedEx Ground labels by passing a value of
PNG in Field 187 (Label Format Value). This image is saved to the C:/FedEx/FedEx_Temp directory by default. If you store labels in
C:\FedEx\FedEx_Temp or your desired path, then you may want to perform clean-up in the path. To override this setting, use Field 537
(Thermal Label Printer ID). Set Field 187 (Label Format Value) to the appropriate size.
• PNG — Portable Network Graphics
• 46L — 4" x 6" PNG
• 48L — 4" x 8" PNG
• 49L — 4" x 9" PNG
This format replaces the previously supported GIF format. See Table 3-12 and Table 3-13 for information about fields to use in a transaction.
Scaling PNG label images
When you view the PNG (Portal Network Graphics) label image on your screen, the bar code dots per inch (dpi) is reduced to your screen
resolution, far less than required. To correct the dpi, you must use FedEx software label extensions or you must scale (or resize) the image
before printing. Scaling instructions vary by screen resolution and dimensions (inches or pixels).
3-16
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
To scale the PNG image for a 4" x 6" label in inches
Set to 4" width and 6" length exactly.
To scale the PNG image for a 4" x 6" label in pixels:
1.
If your screen resolution is 96 dpi, set the image size to:
–Width = 384 pixels (96 ÷ 200 x 800 = 384)
–Height = 576 pixels (95 ÷ 200 x 1200 = 576)
2.
If your screen resolution is 72 dpi, set to:
–Width = 288 pixels (72 ÷ 200 x 800 = 288)
–Height = 432 pixels (72 ÷ 200 x 1200 = 432)
3.
If your screen resolution is not 96 or 72 dpi, set to:
–Width = Your screen dpi ÷ 200 x 800
–Height = Your screen dpi ÷ 200 x 1200
PDF Labels
FedEx Ship Manager Server provides Portable Document Format (PDF) label images for FedEx Express and FedEx Ground labels when
you specify a value of PDF in Field 187 (Label Format Value). This produces an image of a laser label. Images of thermal labels may be
captured by setting Field 187 to the appropriate thermal label size desired:
• PDF — Portable Document Format
• 46P — 4" x 6" PDF
• 48P — 4" x 8" PDF
• 49P — 4" x 9" PDF
These images are saved in the C:/FedEx/FedEx_Temp directory (as the default location). To change this location, you can override
with another valid directory path in Field 537 (Thermal Label Printer ID). With PDF labels, there is no need to resize (scale) the label to fit the
paper or label stock. See Table 3-12 and Table 3-13 for information about fields to use in a transaction.
DIB Labels
Device Independent Bitmap (DIB) labels can be produced using the Windows Print Manager. Field 187 (Label Format Value/Printer Type
Indicator) must be set to DIB. This is a laser label. In addition to the plain paper label that is produced, you can use Field 187 to indicate
other label image sizes:
• DIB — Device Independent Bitmap
• 46D — 4"x 6" DIB
• 48D — 4" x 8" DIB
• 49D — 4" x 9" DIB
You must include Field 537 (Label Printer ID) in a transaction and set the value to the UNC (Uniform Naming Convention) printer name. See
Table 3-13 for more details.
DIB labels are available for FedEx Express and FedEx Ground shipments and may be stored in a label buffer file.
Configuring Printers for Labels, Forms and Reports
The Label Settings window in the FSMS Configuration Utility is used to configure printers for printing laser and thermal shipping labels as
well as for multi-ply air waybills.
The Report Settings window in the same utility is used to configure FedEx Express dangerous goods (DG) forms and FedEx Ground
hazardous materials forms.
v 10.6.1
FedEx Ship Manager® Server Installation and Configuration Guide
3-17
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Note: When printing the FedEx Ground Hazardous Materials form OP-900, use the Windows Generic/Text only printer driver and not the
Lexmark printer driver. This allows you to use the custom form OP-900 defined in the Windows Print Server.
See the FedEx Ship Manager® Server Installation and Configuration Guide for information about how to configure printers for printing FedEx
shipping labels.
Specifying Thermal Printers in Transactions
To specify a thermal printer in a transaction, include the fields in Table 3-12 in the 020 Global Ship Request or 095 Label Reprint Request
transaction.
Table 3-12: Fields for Identifying Thermal Printers
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Label Format Value/Printer Type Indicator
187
Max=3
A
I
FDXE
FDXG
All
REQUIRED*
Enter the value that corresponds to the label format to print or label buffer
to save. Each label format / printer type combination has a specific code.
*Required if Field 1282 specifies value T (Thermal label), F (Thermal
label buffer to multiple files) or S (Thermal label buffer to single file).
The label buffer string is returned in Field 188 (Label Buffer String).
Specify one of the following valid values:
399 — Eltron/Zebra EPL 4" x 8"
499 — Eltron/Zebra EPL 4" x 9"
388 — Zebra 4" x 8"
488 — Zebra 4" x 9"
FDXE=
INTL
FDXG=
US
REQUIRED*
Thermal printer identifier or path to label buffer file. Share name for a
network printer may be used.
*Required for network printing of a thermal or laser label using the UNC
format or saving the thermal label buffer, PNG image or 2D bar code data
to a file other than the default.
Default thermal and laser printers are configured in the FSMS
Configuration Utility.
Default label buffer, PNG or PDF image, and 2D bar code file path:
C:\FedEx\FedEx_Temp. If you store labels in
C:\FedEx\FedEx_Temp or your desired path, you may want to
perform cleanup in the path.
Use Field 187 (Label Format Value/Printer Type Indicator) to identify the
type of label format/printer type.
Thermal Printer Identifier/Label Buffer File Path
537
3-18
Max=255 N
I
FDXE
FDXG
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Specifying Laser Printers in Transactions
To specify a laser printer in a transaction, include the fields in Table 3-13 in the 020 Global Ship Request or 095 Label Reprint Request
transaction.
Table 3-13: Fields for Identifying Laser Printers
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Label Format Value/Printer Type Indicator
187
Max=3
A
I
FDXE
FDXG
All
REQUIRED*
Enter the value that corresponds to the label format to print or label buffer
to save. Each label format / printer type combination has a specific code.
*Required for printing labels to an FSMS-supported laser printer using the
Uniform Naming Convention (UNC) format or for indicating the label
buffer type to be saved to a file.
The label buffer string is returned in Field 188 (Label Buffer String).
Specify one of the following valid values:
DIB — Laser Labels
46D — 4" x 6" DIB
48D — 4" x 8" DIB
49D — 4" x 9" DIB
PDF — Portable Document Format
46P — 4" x 6" PDF
48P — 4" x 8" PDF
49P — 4" x 9" PDF
PNG — Portable Network Graphics
46L — 4" x 6" PNG
48L — 4" x 8" PNG
49L — 4" x 9" PNG
CLS — Laser Labels
FDXE=
INTL
FDXG=
US
REQUIRED*
Printer identifier or path to label buffer file. Share name for a network
printer may be used.
*Required for network printing of a thermal or laser label using the UNC
format or saving the thermal label buffer, PNG image or 2D bar code data
to a file other than the default.
Default thermal and laser printers are configured in the FSMS
Configuration Utility.
Default label buffer, PNG or PDF image, and 2D bar code file path:
C:\FedEx\FedEx_Temp.
Use Field 187 (Label Format Value/Printer Type Indicator) to identify the
type of label format/printer type.
Thermal Printer Identifier/Label Buffer File Path
537
Max=255 A
I
FDXE
FDXG
Note: Most laser printers support the FedEx laser label types. If you have questions about laser printers, contact FedEx support at
fedex.com/us/customersupport/ or 1.800.GoFedEx 1.800.463.3339.
v 10.6.1
FedEx Ship Manager® Server Installation and Configuration Guide
3-19
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Print Label Options
You can print labels directly on a printer, print the label to a file, or defer printing of the label to a later time. The topics in this section describe
print options:
• Print a thermal label to a file
• Print an air waybill label to printer or file
• Save labels to a table for deferred printing
• Reprint labels for a multiple-piece shipment
Printing Thermal Labels to File
FedEx Ship Manager Server provides a feature called “Print-to-File”. The Print-to-File feature applies to thermal air waybills (TAWB) only
and allows you to return a label to a specified file instead of in a Reply transaction. This feature allows you to control label printing and
eliminates the need for printing labels on a network.
You can return a label to a file when you ship using these FedEx services:
• FedEx Express
• FedEx Ground
• FedEx International multiple-package shipments (MPS)
Thermal label buffers are saved to the FSMS database prior to printing to allow for label reprinting up to 48 hours after shipment processing.
This impacts the speed at which thermal labels are printed. To increase the label print speed, use a value of F or S in Field 1282 (Printer
Type Indicator) and indicate the printer path in Field 537 (Thermal Printer Identifier/Label Buffer File Path). This causes the label buffer to be
sent directly to the printer and not saved to the FSMS database.
Note: Labels produced this way are not available for reprinting.
You must use Field 537 (Thermal Label Printer ID) to designate the directory where you want the label stored. The file name for the label is
the master air waybill tracking number. All labels associated with a master air waybill are written to the same file name. For example, if you
have a master shipment with twenty (20) associated packages, all labels for this multiple-piece shipment are written to the same file.
Table 3-14 describes the fields required to print a thermal airway bill label to a file using the 020 Global Ship Request transaction.
Printing an Air Waybill Label
Use the Air Waybill Label Indicator (Field 3130) to print or reprint the Thermal Air Waybill (AWB) Label.
Shippers are able to reprint one copy (per request) of the Thermal AWB or DIB Plain Paper label designated as a copy for the shipper.
This feature provides the following features:
• Ability to reprint a duplicate of the Thermal AWB ONLY and not reprint the Thermal ASTRA copy.
• On the reprinted Thermal AWB ONLY or on a DIB Plain Paper Label (Laser Label Reprint Equivalent on FSMS), the Shipper AWB copy
is identified by printing "SHIPPER AWB COPY" on the label.
The Thermal Air Waybill is available for all FedEx Express International shipments:
• International Priority
–FedEx International Priority®
–FedEx International Priority® Freight
–FedEx International Priority DirectDistribution®
–FedEx International Priority DirectDistribution® Freight
3-20
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
• International Economy
–FedEx International Economy®
–FedEx International Economy® Freight
–FedEx International Economy DirectDistribution℠ Service
Table 3-14 describes the Field 3130 (Air Waybill Label Indicator).
Table 3-14: Air Waybill Label Indicator Field
Transactions: 020/120 Global Ship Request/Reply
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Air Waybill Label Indicator
3130
Max=1
N
I
FDXE
INTL
IPD
IED
IDF
Field Level: Package
REQUIRED.
Indicates shipper requirement for printing or reprinting an international air
waybill label.
Valid values are:
1 — Shipper AWB Copy
2
— Print all three (3) labels
Printing Thermal Air Waybill Labels to File
When using the multi-ply air waybill, you can set up the printer in the FSMS Configuration Utility, or you can specify the printer within the
transaction. If the printer is set up in the FSMS Configuration Utility, this printer becomes the default for all multi-ply air waybills produced on
the configured meter.
Table 3-15 lists the fields needed to print thermal air waybill labels to a file.
Table 3-15: Fields for Printing Thermal Air Waybill Labels to File
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Label Format Value/Printer Type Indicator
187
v 10.6.1
Max=3
A
I
FDXE
FDXG
All
REQUIRED*
Enter the value that corresponds to the label format to print or label buffer
to save. Each label format / printer type combination has a specific code.
*Required if Field 1282 specifies value T (Thermal label), F (Thermal
label buffer to multiple files) or S (Thermal label buffer to single file).
The label buffer string is returned in Field 188 (Label Buffer String).
Specify one of the following valid values:
399 — Eltron/Zebra EPL 4" x 8"
499 — Eltron/Zebra EPL 4" x 9"
388 — Zebra 4" x 8"
488 — Zebra 4" x 9"
FedEx Ship Manager® Server Installation and Configuration Guide
3-21
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-15: Fields for Printing Thermal Air Waybill Labels to File (Continued)
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Thermal Printer Identifier/Label Buffer File Path
537
Max=255 A
I
FDXE
FDXG
FDXE=
INTL
FDXG=
US
REQUIRED*
Thermal printer identifier or path to label buffer file. Share name for a
network printer may be used.
*Required for network printing of a thermal or laser label using the UNC
format or saving the thermal label buffer, PNG image, or 2D bar code data
to a file other than the default.
Default thermal and laser printers are configured in the FSMS
Configuration Utility.
Default label buffer, PNG or PDF image, and 2D bar code file path:
C:\FedEx\FedEx_Temp.
Use Field 187 (Label Format Value/Printer Type Indicator) to identify the
type of label format/printer type.
I
FDXE
FDXG
All
REQUIRED*
Indicates the printer
*Required to save a thermal label buffer to a file.
Valid values:
N — No label
T — Thermal label
B — 2D bar code request for producing custom labels
If the field value is set to B:
• Field 537 (Thermal Printer Identifier/Label Buffer File Path) should be
used if using a directory other than the default directory:
C:\FedEx\FedEx_Temp.
• Field 1660 (Custom Label Flag) must be set to Y.
Printer Type Indicator
1282
3-22
Max=1
A
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-15: Fields for Printing Thermal Air Waybill Labels to File (Continued)
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Printer Type Indicator
1282
(cont.)
Max=1
A
I
FDXE
FDXG
All
F — Thermal Label Buffer
Multiple files: each label buffer is saved to an individual file.
• The package’s tracking number will be used as the file name. Note that
FedEx Ground C.O.D. label file names begin with CR.
• For FedEx international MPS shipments, the master air waybill (MAWB)
buffer will be saved to the same file as the buffer for the first package.
• For Open Ship shipments, place this field and its value in the CONFIRM
transaction.
S — Thermal Label Buffer
Single files: all label buffers are saved to a single file.
• For FedEx international MPS shipments only. Does not include IPD/IDF*
or IDD Surface* — use F for these shipment types.
• MPS buffers separated by a carriage return.
• For FedEx international MPS shipments, the master air waybill (MAWB)
number is the file name.
• For Open Ship shipments, place this field and its value in the CONFIRM
transaction.
Note: Thermal label buffers are saved to the FSMS database prior to
printing to allow for label reprinting up to 48 hours after shipment
processing. This impacts the speed at which thermal labels are printed.
To increase the label print speed, use a value of F or S in Field 1282 and
indicate the printer path in Field 537. Doing this will cause the label buffer
to be sent directly to the printer and not saved to the FSMS database.
Labels produced this way will not be available for reprinting.
*IPD/IDF is the acronym for FedEx International Priority
DirectDistribution/FedEx International DirectDistribution Freight.
* IDD Surface is the acronym for FedEx® International DirectDistribution
Surface Solutions, formerly known as TD for FedEx® Transborder
Distribution.
Number of Label Copies - Shipper
1311
v 10.6.1
Max=1
N
I
FDXE
FDXG
INTL
Optional
Number of additional copies of the shipper label to print. The copies print
in addition to the normal number of labels.
Use Field 1311 to override the International Shipper Label Copies field on
the Label Settings tab of the FSMS Configuration Utility.
Valid values are:
0 — One copy (default)
1 — One copy
2 — Two copies
3 — Three copies
Note: Field 1311 set to 0 (zero) no longer suppresses printing of a label.
If you set this field to 0, one label prints.
FedEx Ship Manager® Server Installation and Configuration Guide
3-23
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-15: Fields for Printing Thermal Air Waybill Labels to File (Continued)
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Number of Label Copies - Customs
1312
Max=1
N
I
FDXE
FDXG
INTL
Optional
Number of additional copies of the Customs label to print. The copies
print in addition to the normal number of labels.
Use Field 1312 to override the International Customs Label Copies field
on the Label Settings tab of the FSMS Configuration Utility.
Valid values are:
0 — One copy (default)
1 — One copy
2 — Two copies
3 — Three copies
Note: Field 1312 set to 0 (zero) no longer suppresses printing of a label.
If you set this field to 0, one label prints.
FDXE
FDXG
INTL
Optional
Number of additional copies of the Manifest label to print. The copies print
in addition to the normal number of labels.
Use Field 1313 to override the International Manifest Label Copies field
on the Label Settings tab of the FSMS Configuration Utility.
Valid values are:
0 — One copy (default)
1 — One copy
2 — Two copies
3 — Three copies
Note: Field 1313 set to 0 (zero) no longer suppresses printing of a label.
If you set this field to 0, one label prints.
Number of Label Copies - Manifest
1313
Max=1
N
I
Deferring Print Label
You can save shipping labels to a label table from which you can print the label later.
Table 3-16 describes the fields you must include in a 095 Reprint Label Request transaction if you want to defer printing labels.
If you include Field 537 (Thermal Printer Identifier/Label Buffer File Path) with Field 187 (Label Format Value/Printer Type Indicator) set to
CLS, the printer path is ignored.
3-24
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-16: Fields Required to Defer Label Printing
Transaction: 095 Label Reprint Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Label Format Value/Printer Type Indicator
187
Max=3
A
I
FDXE
FDXG
All
REQUIRED*
Indicates the label buffer type to save.
*Required if Field 1282 specifies value T (Thermal label), F (Thermal
label buffer to multiple files) or S (Thermal label buffer to single file).
Must be set to the following value:
CLS — Deferred Label
A
I/O
FDXE
FDXG
All
REQUIRED*
If set to Y, stores the label data received in the 095 transaction in a label
table.
*Must be set to Y to defer printing the label.
Valid values:
Y — Defer printing of label
N — Do not defer printing of label (default)
Deferred Label Flag
2406
Max=1
Reprinting Labels for Multiple-Piece Shipments
You can reprint labels for multiple-piece shipments (MPS) in two ways:
• Use the Label Reprint Utility. See Chapter 14: FedEx Ship Manager Server Utilities for information.
• Send a request using the 095 Label Reprint Request transaction. See Chapter 2: About FedEx Ship Manager Server Transactions for
information.
Services Allowing Label Reprint
Label reprint for multiple-piece shipments is available for:
• FedEx Express International
• FedEx Ground
Rules for Reprinting Multiple-Piece Shipment Labels
• You can reprint labels up to a maximum of 48 hours after the ship date with the restriction that the calendar day for the reprint cannot be
greater than the day after the ship date. For example, if you ship a 2-package FedEx Express International package on 12/15/05 at 16:30
(4:30 PM), you have until 22:59 (10:59 PM) of the entire next day (12/16/05) to reprint the label.
• The package for which you are requesting a Label Reprint must be part of an MPS shipment — either FedEx Express International or
FedEx Ground.
• For the Future Day option, you can reprint shipment labels using the same reprint time frame: that is, you may reprint a Future Day
shipment label until the ship date. Then, if you need additional time, you have up to a maximum of 48 hours from the ship date/time (up to
the next calendar day from the ship date) to reprint the label.
v 10.6.1
FedEx Ship Manager® Server Installation and Configuration Guide
3-25
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-17: Fields for Reprinting a Label for a Multiple-Piece Shipment
Transaction: 095 Label Reprint Request
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
A
I/O
Description
Tracking Number
29
Min=12
Max=25
FDXE
FDXG
FDXE=
INTL
FDXG=
US
REQUIRED*
FedEx tracking number that is assigned to the package.
*Required for reprint of thermal or laser MPS labels.
You may use Field 29 as a multiple occurrence field. This allows all child
tracking numbers to be returned in the Reply transaction.
Returned if a tracking by number results in a duplicate.
Thermal Printer Identifier/Label Buffer File Path
537
Max=255 A
I
FDXE
FDXG
FDXE=
INTL
FDXG=
US
REQUIRED*
Thermal printer identifier or path to label buffer file. Share name for a
network printer may be used.
*Required for network printing of a thermal or laser label using the UNC
format or saving the thermal label buffer, PNG image, or 2D bar code data
to a file other than the default.
Default thermal and laser printers are configured in the FSMS
Configuration Utility.
Default label buffer, PNG or PDF image, and 2D bar code file path:
C:\FedEx\FedEx_Temp.
Use Field 187 (Label Format Value/Printer Type Indicator) to identify the
type of label format/printer type.
I
FDXE
FDXG
FDXE=
INTL
FDXG=
US
REQUIRED*
Laser printer ID in UNC format used for printing the Laser Air Waybills.
*Required for reprint of laser MPS labels.
Laser Printer ID
544
Max=255
A
For more information about the 095 Label Reprint Request transaction, see the FedEx Ship Manager® Server Transaction Coding
Reference Guide.
Labels and Doc-Tabs
The term doc-tab refers to a peel-off strip at the top or bottom of a FedEx thermal label on which you can print user-defined shipping
information. You can remove the doc-tab section of a label and keep it with your back-office shipping records.
The following labels include doc-tab areas:
• 6" thermal label
• 9" thermal label
3-26
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Creating a Custom Doc-Tab Label
Use the doc-tab area of a FedEx thermal label to print information you want to retain with your shipping records. To create doc-tabs for
FedEx Express and FedEx Ground labels use the 020 Global Ship Request transaction. The following table lists the fields you may include
in a transaction to specify the text you want printed in the doc-tab area of a label.
Doc-Tab Settings
In addition, labels are now available with or without doc-tabs in all U.S. FedEx SmartPost® shipments. The default doc-tab can be used or it
can be customized with the available field tags.
FedEx Ship Manager Server allows Field 1619 (Doc-Tab Type) to be passed in the 070/170 Meter Query Request/Reply Transaction with
the new value of “SP” to configure a Doc-Tab for FedEx SmartPost shipments. See Chapter 7: Coding Transactions for FedEx SmartPost for
more information.
The default doc-tab includes the following information:
• Position 1 - Invoice: Invoice Number
• Position 2 - Customer: Customer Reference
• Position 3 - Phone: Phone Number
• Position 4 - Dept.: Recipient Department Name
• Position 5 - Date: Ship Date
• Position 6 - Weight: Weight
• Position 7 - Shipping: Net Charge
• Position 8 - Special: Total Surcharge Amount
• Position 9 - Handling: Total Customer Handling Charge
• Position 10 - Total: Total Customer Charge Amount
• Tab Portion
–Ground Tracking Number: 15 characters with no spaces
–FedEx SmartPost Tracking Number: 20 characters with additional spaces after every 4 characters
Doc-Tab Fields
When FedEx SmartPost is enabled, Doc-Tab Settings can be configured by the customer for all FedEx SmartPost shipments. Table 3-18
lists the fields to include in the transaction. When FedEx SmartPost is selected as the shipping type on the Doc-Tab Settings Screen, the
following FedEx SmartPost specific fields are available in the “values” drop down:
Table 3-18: Doc-Tab Fields
Transaction: 020/120 Global Ship Request/Reply
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Label Format Value/Printer Type Indicator
187
v 10.6.1
Max=3
A
I
FDXE
FDXG
All
REQUIRED*
Enter the value that corresponds to the label format to print. Each label
format / printer type combination has a specific code.
*Required for printing labels to an FSMS supported thermal printer or a
laser printer.
FedEx Ship Manager® Server Installation and Configuration Guide
3-27
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-18: Doc-Tab Fields (Continued)
Transaction: 020/120 Global Ship Request/Reply
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Label Format Value/Printer Type Indicator
187
(cont.)
Max=3
A
I
FDXE
FDXG
All
To print a doc-tab label, specify one of the following values:
199 — Eltron LP2348/LP2443 4" x 6" doc-tab
188 — Zebra* DA402 4" x 6" doc-tab
DIB — Laser Labels
46D — 4" x 6" DIB
PDF — Portable Document Format
46P — 4" x 6" PDF
PNG — Portable Network Graphics
46L — 4" x 6" PNG
CLS — Deferred Label
I
FDXE
FDXG
All
Field Level: Shipment
Optional
Text for custom doc-tab Field 1.
Text on label truncates to 12 characters.
I
FDXE
FDXG
All
Field Level: Shipment
Optional
Text for custom doc-tab Field 2.
Text on label truncates to 12 characters.
I
FDXE
FDXG
All
Field Level: Shipment
Optional
Text for custom doc-tab Field 3.
Text on label truncates to 12 characters.
I
FDXE
FDXG
All
Field Level: Shipment
Optional
Text for custom doc-tab Field 4.
Text on label truncates to 12 characters.
I
FDXE
FDXG
All
Field Level: Shipment
Optional
Text for custom doc-tab Field 5.
Text on label truncates to 12 characters.
Custom Doc-Tab Field 1
581
Max=75
A
Custom Doc-Tab Field 2
582
Max=75
A
Custom Doc-Tab Field 3
583
Max=75
A
Custom Doc-Tab Field 4
584
Max=75
A
Custom Doc-Tab Field 5
585
3-28
Max=75
A
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-18: Doc-Tab Fields (Continued)
Transaction: 020/120 Global Ship Request/Reply
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Custom Doc-Tab Field 6
586
Max=75
A
I
FDXE
FDXG
All
Field Level: Shipment
Optional
Text for custom doc-tab Field 6.
Text on label truncates to 12 characters.
I
FDXE
FDXG
All
Field Level: Shipment
Optional
Text for custom doc-tab Field 7.
Text on label truncates to 12 characters.
I
FDXE
FDXG
All
Field Level: Shipment
Optional
Text for custom doc-tab Field 8.
Text on label truncates to 12 characters.
I
FDXE
FDXG
All
Field Level: Shipment
Optional
Text for custom doc-tab Field 9.
Text on label truncates to 12 characters.
I
FDXE
FDXG
All
Field Level: Shipment
Optional
Text for custom doc-tab Field 10.
Text on label truncates to 12 characters.
I
FDXE
FDXG
All
Field Level: Shipment
Optional
Text for custom doc-tab Field 11.
Text on label truncates to 12 characters.
I
FDXE
FDXG
All
Field Level: Shipment
Optional
Text for custom doc-tab Field 12.
Text on label truncates to 12 characters.
Custom Doc-Tab Field 7
587
Max=75
A
Custom Doc-Tab Field 8
588
Max=75
A
Custom Doc-Tab Field 9
589
Max=75
A
Custom Doc-Tab Field 10
590
Max=75
A
Custom Doc-Tab Field 11
591
Max=75
A
Custom Doc-Tab Field 12
592
v 10.6.1
Max=75
A
FedEx Ship Manager® Server Installation and Configuration Guide
3-29
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-18: Doc-Tab Fields (Continued)
Transaction: 020/120 Global Ship Request/Reply
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
Description
Label Orientation
1370
Max=3
FDXE
FDXG
All
Optional
Indicates position of doc-tab on the label.
Valid values are:
3 — Doc-tab at Bottom
4 — Doc-tab at Top
Overrides setting in the FSMS Configuration Utility.
Print On Consignee Labels Flag
1374
Max=1
A
I
FDXE
FDXG
All
Field Level: Shipment
Optional
Flag to turn on/off Print Doc-Tab fields on Consignee Labels.
Valid values:
Y — Enables printing on consignee label
N — Disables printing
Available for international shipments only.
A/N
I
FDXE
FDXG
All
Optional
Data bar coded on the doc-tab.
Use this Field (1621) to override all doc-tab selections configured in the
or passed in the transaction.
Data must be alphanumeric characters only; no special characters
allowed.
A
I
FDXE
FDXG
All
Optional
Header text that describes the data encoded in the doc-tab bar code.
Data entered in Field 1621 (Doc-Tab Bar Code) follows the Header in
human readable form, and the values print below the bar code.
Example: Store Number: (Data from Field 1621)
Doc-Tab Bar Code
1621
Max=30
Doc-Tab Header
1959
3-30
Max=20
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-18: Doc-Tab Fields (Continued)
Transaction: 020/120 Global Ship Request/Reply
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Ancillary Endorsements
2416
v 10.6.1
Max=2
N
Description
Transactions: 020 Global Ship Request
I
FDXS
US
Optional
Special endorsements or delivery options specific to FedEx SmartPost.
Valid values are:
1 — Carrier Leave If No Response
2 — Address Service Requested
3 — Forwarding Service Requested
4 — Return Service Requested
5 — Change Service Requested
For shipping, use Open Ship or MPS.
If FSMS has defaulted the value in Field 2416 to the value of 2 (based on
the conditions described for Field 2417), the following informational
message (Message Code 5042) will be returned to the customer, “Your
ancillary endorsement has been changed to 2 (Address Service
Requested). Please note that ancillary endorsement can only be 2
(Address Service Requested) or 4 (Return Service Requested) for FedEx
SmartPost Standard Mail shipments with Delivery Confirmation.”
If a customer processes a 020 Shipping transaction with Field 2417
(Service Type) set to 1 (FedEx SmartPost Standard Mail) with Delivery
Confirmation, and Field 2416 (Ancillary Endorsement) is not sent in,
blank, or set to any value other than 2 (Address Service Requested) or 4
(Return Service Requested), then FSMS defaults the value for Field 2416
to 2 (Address Service Requested).
If Field 2417 (FedEx SmartPost Service Type) is passed in the 020
Shipping transaction and set to 1 (FedEx SmartPost), 3 (Bound Printed
Matter) or 5 (FedEx SmartPost Media), and if Delivery Confirmation
exception is not set in CHEERS (internal system), then Delivery
Confirmation will be ‘Y’.
The customer will not be able to turn Delivery Confirmation on or off at the
shipment level. Delivery Confirmation must be read from CHEERS at the
account-level.
If a customer is processing an 020 Shipping transaction and passes in
Field 2417 (Service Type) set to 1 (Standard Mail), Field 3204 (Delivery
Confirmation) set to Y, and either does not pass Field 2416 (Ancillary
Endorsement) or passes it in blank or with a value of 1 (Carrier Leave if
no Response), 3 (Forwarding Service Requested), or 5 (Change Service
Requested), then Field 2416 will be automatically reset to value 2
(Address Service Requested. The shipment will be successful and the
customer will receive Message 5042,“Your ancillary endorsement has
been changed to 2 (Address Service Requested). Please note that the
ancillary endorsement can only be 2 (Address Service Requested) or 4
(Return Service Requested) for FedEx SmartPost Standard Mail
shipments with Delivery Confirmation.”
FedEx Ship Manager® Server Installation and Configuration Guide
3-31
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-18: Doc-Tab Fields (Continued)
Transaction: 020/120 Global Ship Request/Reply
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
SmartPost Service Type/Postal Indicia
2417
Max=2
N
I
Description
Transactions: 020 Global Ship Request
FDXS
US
REQUIRED*
FedEx SmartPost service type you use to ship the package. Indicates
type of shipment and postal information placed in the “stamp” area of the
label.
* Required for FedEx SmartPost.
Valid values are:
1 — Standard Mail
3 — Bound Printed Matter
4 — Obsolete
5 — Media
6 — Parcel Select
7 — SmartPost Returns
If customer ships a FedEx SmartPost shipment with Field 2417 (Service
Type) set to 1 (Standard Mail) and passes in Field 2416 set either to
position 1, 3, 5, or left blank, the position of Field 2416 defaults to 4
(Return Service Requested). The customer then receives the
informational message, “Your ancillary endorsement has been changed
per USPS regulation.”
If FSMS has defaulted the value in Field 2416 to the value of 2 (based on
the conditions described for Field 2417), the following informational
message (Message Code 5042) will be returned to the customer, “Your
ancillary endorsement has been changed to 2 (Address Service
Requested). Please note that ancillary endorsement can only be 2
(Address Service Requested) or 4 (Return Service Requested) for FedEx
SmartPost Standard Mail shipments with Delivery Confirmation.”
If a customer processes a 020 Shipping transaction with Field 2417
(Service Type) set to 1 (FedEx SmartPost Standard Mail) with Delivery
Confirmation, and Field 2416 (Ancillary Endorsement) is not sent in,
blank, or set to any value other than 2 (Address Service Requested) or 4
(Return Service Requested), then FSMS defaults the value for Field 2416
to 2 (Address Service Requested).
If Field 2417 (FedEx SmartPost Service Type) is passed in the 020
Shipping transaction and set to 1 (FedEx SmartPost), 3 (Bound Printed
Matter) or 5 (FedEx SmartPost Media), and if Delivery Confirmation
exception is not set in CHEERS (internal system), then Delivery
Confirmation will be ‘Y’.
The customer will not be able to turn Delivery Confirmation on or off at the
shipment level. Delivery Confirmation must be read from FedEx at the
account-level.
For shipping, use Open Ship or MPS.
See FedEx SmartPost Service Types in the FedEx Ship Manager®
Server Developer Guide for more information.
3-32
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-18: Doc-Tab Fields (Continued)
Transaction: 020/120 Global Ship Request/Reply
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Delivery Confirmation Bar Code
2418
Max=30
A/N
O
Description
Transactions: 120 Global Ship Reply
FDXE
FDXG
FDXS
US
Delivery Confirmation Number (DCN) generated by FSMS based upon
setup in FSMS Configuration utility.
This number prints on the FedEx SmartPost label under the DCN bar
code.
Explanation of DCN:
Digits 1-3 — Identifier (420)
Digits 4-8 — ZIP code
Digits 9-10 — Application ID (91)
Digits 11-12 — Service Type Code
Digits 13-21 — DUNS #
Digits 22-29 — Package/Parcel ID
Digit 30 — MOD 10 check digit.
The last 20 digits are the tracking number and are also found in Field 29
(Tracking Number).
Note: GND UCC/EAN bar code is returned when doing Ground or Home
Delivery. However, FedEx SmartPost does not return that field, but
instead uses Field 2418 (Delivery Confirmation Bar Code). Best practice
for generating the bar code is a FedEx SmartPost custom label.
Note: The Delivery Confirmation Number does not duplicate within a 12
month period.
SmartPost Customer ID
2425
Max=5
N
Transactions: 020 Global Ship Request
I
FDXS
List Non-Machinable Surcharge
2800
Optional
Five-digit FedEx SmartPost customer account number.
If not passed in, it defaults to the FedEx SmartPost Customer ID set
during configuration.
For shipping, use Open Ship or MPS.
Transactions: 120 Global Ship Reply
Min=1
N
O
FDXS
Max=4
N
I/O
FDXS
Hub ID
2801
US
Optional
Contains the list surcharge amount for a non-machinable package.
Transactions: 020/120 Global Ship Request/Reply
REQUIRED*
*Required if user is allowed to use multiple hubs and wants to use a
different HUB ID other than the default HUB ID.
If customer passes in this field with a value other than the value in their
list of allowed HUB IDs, an error message, “Invalid Hub ID entered for
FedEx SmartPost shipment,” is returned and the transaction fails.
v 10.6.1
FedEx Ship Manager® Server Installation and Configuration Guide
3-33
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-18: Doc-Tab Fields (Continued)
Transaction: 020/120 Global Ship Request/Reply
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Non-Machinable
2802
Max=1
Transactions: 020/120 Global Ship Request/Reply
A
I/O
FDXS
O
FDXS
Non-Machinable Surcharge
2803
Min=1
N
Max=11.2
Min=1
N
Max=11.2
O
FDXS
I
FDXS
Delivery Confirmation Flag
3204
Max=1
A/N
Optional
Identifies a non-machinable package.
Valid values are:
Y — Yes
N — No
Transactions: 120 Global Ship Reply
Delivery Confirmation Service Surcharge
2804
Description
The surcharge amount for the non-machinable package.
If Field 1234 (Rate/Route/Time in Transit) is passed in set to position 1
(Rate), or if Field 541 (Open Ship) is passed in set to position 3 (Rate)
and Field 2802 is passed in, or if the package dimensions indicate nonmachinable, and rating is successful, the correct non-machinable
surcharge is returned.
Transactions: 120 Global Ship Reply
The surcharge amount for Delivery.
Transactions: 020 Global Ship Request
US
Obsolete field.
Optional
Indicates if Delivery Confirmation is used or not.
Valid values are:
Y — Delivery Confirmation
N — No Delivery Confirmation
FedEx SmartPost delivery confirmation will default to the value set on the
configuration screen, if Field 2417 is set to position 1, 3, or 5. If Field 2417
is set to position 6, then it will default to Y.
Preassigned Delivery Confirmation Tracking
Number
Transactions: 020/120 Global Ship Request/Reply
4926
US
Min=1
Max=30
N
I/O
FDXG
Optional
Returns the Pre-assigned USPS Delivery Confirmation tracking number
for a FedEx SmartPost package when FedEx Ground is configured as the
pickup carrier.
Delivery Confirmation Tracking Number
Transactions: 120 Global Ship Reply
4927
US
Min=1
Max=30
N
O
FDXG
Optional
Returns the USPS Delivery Confirmation tracking number for a FedEx
SmartPost package when FedEx Ground is configured as the pickup
carrier.
Note: Field 3063 (GND UCC EAN Bar Code Data) is returned when doing Ground or Home Delivery; however, FedEx SmartPost does not
return that field but instead uses Field 2418 (Delivery Confirmation Number). Best practice for generating the bar code is a FedEx
SmartPost custom label.
3-34
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
How to Configure Doc-Tabs
Configure doc-tabs in two ways:
1.
Use the Doc-Tab Settings tab of the FSMS Configuration Utility.
–The FSMS Configuration Utility includes doc-tab options to print on the Leading Edge or Trailing Edge of the label.
2.
Use the 070 Meter Query or Configuration Request Transaction. See the FedEx Ship Manager® Server Transaction Coding Reference
Guide for more information about this transaction.
Note: For more information, See FedExShip Manager® Server Installation and Configuration Guide.
Figure 3-8 illustrates the Doc-Tab Settings tab in theFSMS Configuration Utility.
Figure 3-8: FedEx SmartPost Enabled Doc-Tab Settings
v 10.6.1
FedEx Ship Manager® Server Installation and Configuration Guide
3-35
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
How to Print Reference Information on Labels
This section describes the FSMS fields required when printing reference information on a label. It includes these topics:
• Printing Reference Information on a Return Label
• Printing Reference Information on FedEx Ground Labels
• Printing Reference Information on FedEx Express Labels
• Printing Reference Information on FedEx SmartPost Labels
Printing Reference Information on a Return Label
Table 3-19 describes the transaction shipment-level fields and rules required to print reference information on a FedEx Ground C.O.D.
Return label.
Table 3-19: Reference Fields for FedEx Ground C.O.D. Return Labels
Transaction: 020/120 Global Ship Request/Reply - Single Piece, Single Shot, Open Ship (regular and IDD Surface Canada only)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Shipment Purchase Order Number
3001
Max=30
A
I
FDXG
C.O.D.
IDD
Surface
Field Level: Shipment
Optional
Specifies the purchase order number for the shipment.
Use Field 3001 to print the purchase order number on a Returns label.
Use only for shipments of two or more packages to the same recipient.
This value prints on the thermal label. It is displayed in the P.O. # field on
the FedEx Ground invoice.
This field can only be used for shipments of two or more packages to the
same recipient. Use in Single Shot and Open Ship transactions.
This field can be used in the same transaction with the other two shipment
level reference number Fields: 3002 (Shipment Invoice Number) and
3003 (Shipment Customer Reference Information).
I/O
FDXG
C.O.D.
IDD
Surface
Field Level: Shipment
Optional
Specifies the invoice number of the shipment.
Use to Field 3002 to print the invoice number on a Returns label. Use only
for shipments of two or more packages to the same recipient.
This value prints on the thermal label.
Use this field for shipments of two or more packages to the same
recipient. Use in Single Shot and Open Ship transactions.
This field can be used in the same transaction with the other two shipment
level reference number Fields: 3001 (Shipment Purchase Order Number)
and 3003 (Shipment Customer Reference Information).
Shipment Invoice Number
3002
3-36
Max=30
A
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-19: Reference Fields for FedEx Ground C.O.D. Return Labels (Continued)
Transaction: 020/120 Global Ship Request/Reply - Single Piece, Single Shot, Open Ship (regular and IDD Surface Canada only)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Shipment Customer Reference Information
3003
Max=30
A
I/O
FDXG
C.O.D.
IDD
Surface
Field Level: Shipment
Optional
Specifies additional customer information for the shipment.
Use Field 3003 to print customer reference information in the Customer
Reference area of the invoice. Use only for shipments of two or more
packages to the same recipient.
This field can only be used for shipments of two or more packages to the
same recipient. Use in single shot and Open Ship transactions.
This field can be used in the same transaction with the other two shipment
level reference number Fields: 3001 (Shipment Purchase Order Number)
and 3002 (Shipment Invoice Number).
This value is displayed in the Customer Reference field of the invoice.
C.O.D.
IDD
Surface
Optional
Requests reference information to print in the Reference Number field of
the Ground C.O.D. Return Label.
Valid values are:
0 — Tracking number (default)
1 — Reference (requires Field 3003)
2 — Purchase Order number (requires Field 3001)
3 — Invoice number (requires Field 3002)
If any value other than 0, 1, 2, or 3 is entered, the value defaults to the
FedEx tracking number.
Ground C.O.D. Return Reference Indicator
3045
v 10.6.1
Max=1
A/N
I/O
FDXG
FedEx Ship Manager® Server Installation and Configuration Guide
3-37
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Printing Reference Information on FedEx Ground Labels
Table 3-20 describes the transaction package-level fields and rules required to print reference information on a FedEx Ground label.
Table 3-20: Reference Fields for FedEx Ground Labels
Transaction: 020/120 Global Ship Request/Reply
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Reference Information
25-#
Max=39
A
I/O
FDXG
All
Field Level: Package
Optional
Use this field for customer reference number CRN (FedEx Ground).
This field must not be used if a shipment-level customer reference
number (CRN) has been assigned in Field 3003 (Shipment Customer
Reference Information).
If this field is used simultaneously with Field 3003, then Field 3003 is
ignored. Package level fields take precedence.
This field value prints on the Customer Reference field on the FedEx
Ground invoice and on the shipping label $AW.
Use this field in single piece, single shot or Open Ship transaction.
FDXG
All
Field Level: Package
Optional
When used to create or print a bill of lading (BOL), this prints in the
Purchase Order # section of the BOL. Each additional BOL order number
prints directly below each article description. Field 3056 is the only field
that supplies the full set for the BOL.
For FedEx Ground domestic and international: this field prints the
package purchase order number to a thermal label.
For intra-U.S., intra-CA, and intra-MX this is displayed in the P.O. # field
on the FedEx Ground invoice.
Note: This field is a package level field and should not be used if a
shipment level purchase order number has been assigned in Field 3001
(Shipment Purchase Order Number). If this field is used simultaneously
with Field 3001, then Field 3001 is ignored. Package level fields take
precedence.
Use this field in a single piece, single shot or Open Ship transaction.
Package Purchase Order Number
3056
3-38
Max=30
AKE
I/O
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-20: Reference Fields for FedEx Ground Labels (Continued)
Transaction: 020/120 Global Ship Request/Reply
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Package Invoice Number
3057
Max=30
A
I/O
FDXG
All
Field Level: Package
Optional
Prints the package invoice number on the thermal label.
For intra-U.S., intra-CA and intra-MX this is displayed on the FedEx
Express laser and image labels. It is displayed in the Ref. #3 field on the
FedEx Express invoice.
Field 3057 is a package level field and must not be used if a shipment
level invoice number has been assigned in Field 3002 (Shipment Invoice
Number). If this field is used simultaneously with Field 3002, then
Field 3002 is ignored. Package level fields take precedence.
Printing Reference Information on FedEx Express Labels
If you need to display additional information for your shipment on the shipping label or the FedEx invoice, the 020 Global Ship Request
transaction fields in Table 3-21 may be added to your shipping transaction.
Table 3-21: Reference Fields for FedEx Express Reference Information
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Reference Information
25-#
v 10.6.1
Max=39
A/N
I
FDXE
All
Field Level: Package for all services except for FedEx Express
international MPS which is shipment level.
Optional
Use this field for optional notes (FedEx Express) and customer reference
number CRN (FedEx Ground).
For FedEx Express International MPS, this is a shipment-level field.
For al other services, this field is a package-level field and must not be
used if a shipment-level customer reference number (CRN) has been
assigned in Field 3003 (Shipment Customer Reference Information).
If this field is used simultaneously with Field 3003, then Field 3003 is
ignored. Package-level fields take precedence.
This field prints on the FedEx Express shipping label, various reports, and
the FedEx Express Shipper’s Declaration for Dangerous Goods 1421C
form (FedEx Express 1421C or LZR DG DEC FORM. This value also is
displayed in the Customer Reference field on the FedEx Ground invoice.
FedEx Ship Manager® Server Installation and Configuration Guide
3-39
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-21: Reference Fields for FedEx Express Reference Information (Continued)
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Sender/Origin Department
38
Max=30
A
I
FDXE
All
Field Level: Shipment
Optional
Department name of Sender or shipping origin. Use to override the
default origin department setting in the FSMS Configuration Utility.
When used in the 020 Global Ship Request transaction, the name prints
on all shipping details.
For FedEx Ground shipments, it prints on the invoice.
I
FDXE
US
CA
MX
Field Level: Shipment
Optional
Specifies the purchase order number for the shipment.
Use Field 3001 to print the purchase order number on a Returns label.
Use only for shipments of two or more packages to the same recipient.
This value prints on the thermal label. For intra-U.S., intra-CA, and intraMX this is displayed on the FedEx Express laser and image labels. It is
displayed in the Ref. #2 field on the FedEx Express invoice and P.O. #
field on the FedEx Ground invoice.
This field can only be used for shipments of two or more packages to the
same recipient. Use in single shot and Open Ship transactions.
This field can be used in the same transaction with the other two shipment
level reference number Fields: 3002 (Shipment Invoice Number) and
3003 (Shipment Customer Reference Information).
I
FDXE
US
CA
MX
Field Level: Shipment
Optional
Specifies the invoice number of the shipment.
Use to Field 3002 to print the invoice number on a Returns label. Use only
for shipments of two or more packages to the same recipient.
This value prints on the thermal label. For intra-U.S., intra-CA, and intraMX this is displayed on the FedEx Express laser and image labels. It is
displayed in the Ref. #3 field on the FedEx Express invoice.
Use this field for shipments of two or more packages to the same
recipient. Use in single shot and Open Ship transactions.
This field can be used in the same transaction with the other two shipment
level reference number Fields: 3001 (Shipment Purchase Order Number)
and 3003 (Shipment Customer Reference Information).
Shipment Purchase Order Number
3001
Max=30
A
Shipment Invoice Number
3002
3-40
Max=30
A
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-21: Reference Fields for FedEx Express Reference Information (Continued)
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Package Purchase Order Number
3056
Max=30
AKE
I
FDXE
US
CA
MX
Field Level: Package
Optional
When used to create or print a bill of lading (BOL), this prints in the
Purchase Order # section of the BOL. Each additional BOL order number
prints directly below each article description. Field 3056 is the only field
that supplies the full set for the BOL.
For FedEx Ground domestic and international: this field prints the
package purchase order number to a thermal label.
For intra-U.S., intra-CA, and intra-MX this is displayed on the FedEx
Express laser and image labels. It is displayed in the Ref. #2 field on the
FedEx Express invoice and P.O. # field on the FedEx Ground invoice.
Note: This field is a package level field and should not be used if a
shipment level purchase order number has been assigned in Field 3001
(Shipment Purchase Order Number). If this field is used simultaneously
with Field 3001, then Field 3001 is ignored. Package level fields take
precedence.
I
FDXE
US
CA
MX
Field Level: Package
Optional
Invoice number for the package.
You cannot use Field 3067 if a shipment level invoice number has been
assigned in Field 3002 (Shipment Invoice Number).
If you use Field 3067 with Field 3002, then Field 3002 is ignored. Package
level fields take precedence. The package invoice number prints on the
thermal label. For intra-U.S., intra-CA, and intra-MX, this is displayed on
the FedEx Express laser and image labels. It is displayed in the Ref. #3
field on the FedEx Express invoice.
Package Invoice Number
3067
Max=30
A
Note: These fields can also be configured to print on the thermal label doc-tab.
v 10.6.1
FedEx Ship Manager® Server Installation and Configuration Guide
3-41
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Printing Reference Information on FedEx SmartPost Labels
Table 3-22 describes reference fields that can be configured for FedEx SmartPost labels.
Table 3-22: Reference Fields for FedEx SmartPost Labels
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Reference Information
25-#
Max=39
A/N
I
FDXE
A
I
FDXE
FDXG
FDXS
All
Field Level: Package for all services except for FedEx Express
international MPS which is shipment level.
Optional
Use this field for optional notes (FedEx Express) and customer reference
number CRN (FedEx Ground).
For FedEx Express International MPS, this is a shipment-level field.
For al other services, this field is a package-level field and must not be
used if a shipment-level customer reference number (CRN) has been
assigned in Field 3003 (Shipment Customer Reference Information).
If this field is used simultaneously with Field 3003, then Field 3003 is
ignored. Package-level fields take precedence.
This value prints on the FedEx Express shipping label, various reports,
and the FedEx Express Shipper’s Declaration for Dangerous Goods
1421C form. This value also is displayed in the Customer Reference field
on the FedEx Ground invoice and on the shipping label $AW.
RMA Number
2210
Max=20
Optional
Specify the Return Materials Authorization (RMA) number.
If used, the RMA number is printed on the label and uploaded to FedEx
systems. It is then available for tracking and will be included on the
customer invoice.
Note: Used for FedEx SmartPost Returns only.
3-42
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-22: Reference Fields for FedEx SmartPost Labels (Continued)
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Package Purchase Order Number
3056
Max=30
AKE
I
FDXE
US
CA
MX
Field Level: Package
Optional
When used to create or print a bill of lading (BOL), this prints in the
Purchase Order # section of the BOL. Each additional BOL order number
prints directly below each article description. Field 3056 is the only field
that supplies the full set for the BOL.
For FedEx Ground domestic and international: this field prints the
package purchase order number to a thermal label.
For intra-U.S., intra-CA, and intra-MX this is displayed on the FedEx
Express laser and image labels. It is displayed in the Ref. #2 field on the
FedEx Express invoice and P.O. # field on the FedEx Ground invoice.
Note: This field is a package level field and should not be used if a
shipment level purchase order number has been assigned in Field 3001
(Shipment Purchase Order Number). If this field is used simultaneously
with Field 3001, then Field 3001 is ignored. Package level fields take
precedence.
I
FDXE
US
CA
MX
Field Level: Package
Optional
Invoice number for the package.
You cannot use Field 3067 if a shipment level invoice number has been
assigned in Field 3002 (Shipment Invoice Number).
If you use Field 3067 with Field 3002, then Field 3002 is ignored. Package
level fields take precedence. The package invoice number prints on the
thermal label. For intra-U.S., intra-CA, and intra-MX, this is displayed on
the FedEx Express laser and image labels. It is displayed in the Ref. #3
field on the FedEx Express invoice.
Package Invoice Number
3067
Max=30
A
How to Customize Labels
FedEx Ship Manager Server provides two options for customizing your shipping label. You can:
• Place the PNG 4" x 6" label graphic into your label stock. For example, you may create a packing list on an 8-1/2" x 11" form. As part of
this form, you may also place the 4" x 6" PNG label graphic instead of creating a custom label of your own.
• Add a graphic or text file to the 4" x 8" or 4" x 9" thermal label. This label size provides 1.5" of blank space.
However, if neither of these options meets your custom label requirements, you may use FSMS to create a custom label. You can do this in
two ways.
• Capture label information, including the 2D bar code, from the 120 Global Ship Reply transaction and create a custom label on your own
OR
• Use the FSMS Custom Label Generator Utility to create a custom label.
v 10.6.1
FedEx Ship Manager® Server Installation and Configuration Guide
3-43
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
FedEx SmartPost Customizable Labels
Customizable labels are now available with all FedEx SmartPost U.S. outbound shipments. Labels can also be printed in a new size: 4" x 8"
with or without doc-tabs. See Table 3-23 below to see the fields used to produce customizable labels.
Labels can be printed in the following formats and sizes:
• Sizes
–4" x 6" and 4" x 8" thermal labels with and without Doc-Tab.
–4" x 8" Customizable thermal labels
–8-1/2" x 11" in Plain Paper only
• Formats
–Portable Network Graphic (PNG)
–Device Independent Bitmap (DIB)
–Portable Document Format (PDF)
Customizing a Thermal Label
Use a customizable section of the 4" x 8" or 4" x 9" thermal label to customize the label. The 4" x 9" label has a doc-tab, but the 4" x 8" label
does not.
Using this method to customize a label eliminates the need to build a label from scratch. Also, you are not required to submit a thermal label
with a customized section for FedEx validation. Only the ASTRA label is customizable in this way.
This is only applicable to the thermal label printed on a thermal printer set to 203 dpi (dots per inch) and the feature is available for FedEx
Ship Manager Server version 8.2 (or higher).
Table 3-23 describes the label types supporting this feature.
Table 3-23: Label Format Value/Printer Type Indicator
Transactions: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
Description
Label Format Value/Printer Type Indicator
187
Max=3
A
I
FDXE
FDXG
All
REQUIRED*
Enter the value that corresponds to the label format to print or label buffer
to save. Each label format / printer type combination has a specific code.
*Required if Field 1282 specifies value T (Thermal label), F (Thermal
label buffer to multiple files) or S (Thermal label buffer to single file).
The label buffer string is returned in Field 188 (Label Buffer String).
Specify one of the following valid values:
399 — Eltron/Zebra EPL 4" x 8"
499 — Eltron/Zebra EPL 4" x 9"
388 — Zebra 4" x 8"
488 — Zebra 4" x 9"
The label buffer string is returned in Field 188 (Label Buffer String).
In the 4" x 1.5" customizable section of the 4" x 8" or 4" x 9" label you can enter a line, a bar code, text or a graphic image. FedEx does not
validate the appearance of the customizable section nor the fields used to create that portion of the label.
3-44
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-24 describes the transaction fields used to input data for the customizable label section. All fields listed in this table are multipleoccurrence fields.
Table 3-24: Fields Used to Customize Thermal Labels
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Service Valid For
Description
Custom Label Type Indicator
2429-#
Max=2
N
I
FDXE
FDXG
All
Optional
Use to identify type of data element for the customizable portion of the
4" x 8" or 4" x 9" thermal label.
Maximum of twelve (12) occurrences allowed.
Valid values are
01 — Line
02 — Graphic
03 — Text Entry
04 — Bar code
I
FDXE
FDXG
All
REQUIRED*
Defines the X-coordinate for the placement of the beginning of the
customizable entry.
*Required when using Field 2429 (Custom Label Type Indicator) with
valid value.
Valid values: non-negative integer only.
Occurrence # must match occurrence # of Field 2429.
N
I
FDXE
FDXG
All
REQUIRED*
Defines the Y-coordinate for the placement of the beginning of the
customizable entry. Valid values: non-negative integer only.
*Required when using Field 2429 (Custom Label Type Indicator) with
valid value.
Occurrence # must match occurrence # of Field 2429.
A
I
FDXE
FDXG
All
REQUIRED*
Text string to be printed in the customizable section. It can also include
format specifiers.
*Required when using Field 2429 (Custom Label Type Indicator) with
value of 03 or 04.
Occurrence # must match occurrence # of Field 2429.
Alphanumeric with no special characters.
Custom Label X Position
2430-#
Max=5
N
Custom Label Y Position
2431-#
Max=5
Text String
2432-#
v 10.6.1
Max=35
FedEx Ship Manager® Server Installation and Configuration Guide
3-45
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-24: Fields Used to Customize Thermal Labels (Continued)
Transaction: 020 Global Ship Request
Field ID
Data
Type
Input/ FedEx Shipping
Output Service Valid For
A
I
FDXE
FDXG
All
REQUIRED*
Enter a comma delimited list of tags.
*Required when using Field 2429 (Custom Label Type Indicator) with
value of 03 or 04.
Occurrence # must match occurrence # of Field 2429.
Alphanumeric with no special characters.
A
I
FDXE
FDXG
All
REQUIRED*
Logical font that will be translated to the appropriate printer font.
*Required when using Field 2429 (Custom Label Type Indicator) with
value of 03.
Occurrence # must match occurrence # of Field 2429.
Max=3
A
I
FDXE
FDXG
All
REQUIRED*
Logical memory location where the graphic is stored.
*Required when using Field 2429 (Custom Label Type Indicator) with
value of 02.
Occurrence # must match occurrence # of Field 2429.
Max=5
N
I
FDXE
FDXG
All
REQUIRED*
Defines the X-coordinate for the end of the customizable entry.
*Required when using Field 2429 (Custom Label Type Indicator) with
value of 01.
Valid values: non-negative integer only.
Occurrence # must match occurrence # of Field 2429.
Max=5
N
I
FDXE
FDXG
All
REQUIRED*
Defines the Y-coordinate for the end of the customizable entry.
*Required when using Field 2429 (Custom Label Type Indicator) with
value of 01.
Valid values: non-negative integer only.
Occurrence # must match occurrence # of Field 2429.
N
I
FDXE
FDXG
All
REQUIRED*
Height of the bar code in inches divided by the vertical printer DPI (dots
per inch).
Required when using Field 2429 (Custom Label Type Indicator) with
value of 04.
Valid values: non-negative integer only.
Occurrence # must match occurrence # of Field 2429.
Field
Length
Description
Arguments
2433-#
Max=25
Thermal Font ID
2434-#
Max=3
Graphic Location
2436-#
Ending X
2437-#
Ending Y
2438-#
Bar Code Height
2439-#
3-46
Max=5
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Table 3-24: Fields Used to Customize Thermal Labels (Continued)
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Service Valid For
Description
Thin Bar Width/Milspec
2440-#
Max=5
N
I
FDXE
FDXG
All
REQUIRED*
Width in dots of the thinnest bar in the bar code. The thinnest bar code
value entered can be divided by the printer's dpi (dots per inch) to derive
milspec.
*Required when using Field 2429 (Custom Label Type Indicator) with
value of 04.
Valid values: non-negative integer only.
Occurrence # must match occurrence # of Field 2429.
N
I
FDXE
FDXG
All
REQUIRED*
Type of bar code requested on the customizable portion of the label.
*Required when using Field 2429 (Custom Label Type Indicator) with
value of 04.
Occurrence # must match occurrence # of Field 2429.
Valid values are:
01 — (reserved for future use)
02 — Code128B
03 — Code128C
07 — Code39
Bar Code Type
2441-#
Max=2
Submitting Custom Labels for FedEx Approval
Before you can produce custom labels in a production environment, FedEx must first test your custom labels to ensure that FedEx can scan
them for routing and delivery.
To request the certification paperwork, contact Web Support at websupport@fedex.com or call 1.877.339.2774 (voice prompter: Web
Services).
FedEx Express Label Approval
Submit custom FedEx Express labels to:
FedEx World Headquarters
Attention: Bar Code/Label Analyst
3630 Hacks Cross Road, Building I
Memphis, TN 38125
You must submit one label sample for each FedEx service, such as FedEx Priority Overnight®, FedEx International Priority, and so forth.
After FedEx approves your labels you can proceed with custom label deployment.
v 10.6.1
FedEx Ship Manager® Server Installation and Configuration Guide
3-47
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
FedEx Ground/FedEx Home Delivery Label Approval
Submit custom FedEx Ground and FedEx Home Delivery® labels to:
FedEx Ground
Attention: Bar Code Analyst
1000 FedEx Drive
Moon Township, PA 15108
You must submit five label samples for each FedEx Ground and/or FedEx Home Delivery service type you want to use. Additionally, ten
consecutive incremental labels are required from each production printer you want to use. After FedEx approves your labels you can
proceed with custom label deployment.
Label Transaction Samples
All bar code strings required for creating custom FedEx Express or FedEx Ground labels are returned in the 120 Global Ship Reply for each
Open Ship transaction.
The following transaction sample shows which fields to include in a 020 Global Ship Request Open Ship transaction in order to return bar
code strings from custom labels.
Transaction Sample for Shipment 1234 to Indianapolis from Sam's
Publishing
Shows Open Ship CREATE shipment transaction (541 = YNNNNNNNN) submitted with Field 1282 = B and Field 1660 = Y to indicate
a custom label. A pre-assigned tracking number in Field 1222 is optional and is not shown in this transaction sample.
0,"020"1,"CREATE shipment and ADD first package"11,"Sam’s Publishing"12,"Recipient
Name"13,"201 West 103rd St"15,"Indianapolis"16,"IN"17,"46290"
18,"1234567890"23,"1"25,"Package CR001"50,"US"498,""541,"YNNNNNNNN"
542,"12345"1273,"01"1274,"92"1282,"B"1660,"Y"1670,"300"3001,"Shipment PO10001"3057,"Package
IN001"3062,"2"99,""
Shows Open Ship ADD piece (541 = NNNYNNNNN) transaction submitted with Field 1282 = B and 1660 = Y to indicate a custom
label.
0,"020"1,"ADD/RATE Second Package"25,"Package CR002"50,"US"498,""541,"NNNYNNNNN"542,"12345"
1273,"01"1274,"92"1282,"B"1660,"Y"1670,"500"3057,"Package IN002"3062,"2"99,""
Shows Open Ship Edit piece (541 = NNNNYNNNN) transaction submitted with Field 1282 = B and 1660 = Y to indicate a custom
label.
0,"020"1,"EDIT Second Package"29,"192746389462591"50,"US"498,""541,"NNNNYNNNN"542,"12345"
1273,"01"1274,"92"1282,"B"1660,"Y"1670,"800"99,""
Shows an Open Ship CONFIRM shipment transaction. Field 1282 and Field 1660 must be included in the CONFIRM transaction.
0,"020"1,"CONFIRM Open Shipment"50,"US"498,""541,"NNNNNNNNY"542,"12345"1274,"92"1282,"B"
1660,"Y"99,""
3-48
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Transaction Sample for Shipment 23456 to Indianapolis from Sam's
Publishing
Shows Open Ship CREATE shipment and simultaneous RATE shipment transaction (541 = YNYNNNNNN) submitted with Field
1282 = B and Field 1660 = Y to indicate a custom label.
0,"020"1,"CREATE and ADD First package, Pre-assigned Tracking Number"11,"Sam’s Publishing"
12,"Recipient Name"13,"201 West 103rd St"15,"Indianapolis"16,"IN"17,"46290"18,"1234567890"
23,"1"25,"Package CR001"50,"US"498,""541,"YNYNNNNNN"542,"23456"1222,"918273670100831"1273,
"01"1274,"92"1282,"B"1660,"Y"1670,"300"3001,"Shipment PO10001"3057,"Package IN001"3062,"2"
99,""
Shows Open Ship ADD package and simultaneous RATE shipment transaction (541 = NNYYNNNNN) submitted with a preassigned tracking number in Field 1222.
0,"020"1,"ADD/RATE Second Package, Pre-assigned Tracking Number"25,"Package
CR002"50,"US"498,""
541,"NNYYNNNNN"542,"23456"1222,"918273670100848"1273,"01"1274,"92"1282,"B"1660,"Y"1670,"500"
3057,"Package IN002"3062,"2"99,""
Shows Open Ship CONFIRM shipment transaction (541 = NNNNNNNNY) submitted with Field 1282 = B and Field 1660 = Y to
indicate a custom label.
0,"020"1,"CONFIRM Open Shipment"50,"US"498,""541,"NNNNNNNNY"542,"23456"1274,"92"1282,"B"
1660,"Y"99,""
Transaction Sample for Shipment 34567 to Indianapolis from Sam's
Publishing
Shows Open Ship CREATE shipment transaction (541 = YNNNNNNNN) submitted with Field 1282 = B and Field 1660 = Y to indicate
a custom label.
0,"020"1,"CREATE and ADD First package, Express C.O.D."11,"Sam’s Publishing"12,"Recipient
Name"13,"201 West 103rd St"15,"Indianapolis"16,"IN"17,"46290"18,"1234567890"23,"1"25,"Package
CR001"27,"Y"50,"US"53,"15000"186,"Y"440,"Y"498,""541,"YNNNNNNNN"542,"34567"1273,"01"1274,"01"
1282,"B"1660,"Y"1670,"450"3062,"2"99,""
Shows Open Ship ADD piece (541 = NNNYNNNNN) transaction submitted with Field 1282 = B and 1660 = Y to indicate a custom
label.
0,"020"1,"ADD Second Package"25,"Package CR002"50,"US"498,""
541,"NNNYNNNNN"542,"34567"1273,"01"1274,"01"1282,"B"1660,"Y"1670,"500"3057,"Package IN002"
3062,"2"99,""
Shows Open Ship CONFIRM transaction (541=NNNNNNNNY) submitted with Field 1282 = B and Field 1660 = Y to indicate a custom
label.
0,"020"1,"CONFIRM Open Shipment"50,"US"498,""541,"NNNNNNNNY"542,"34567"1274,"01"1282,"B"
1660,"Y"99,""
v 10.6.1
FedEx Ship Manager® Server Installation and Configuration Guide
3-49
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
FedEx Label Samples
• This section shows samples of different FedEx labels required for FedEx shipping. All label illustrations shown are smaller than actual
size. They include:
• FedEx Express U.S. Label (see Figure 3-9).
• FedEx Home Delivery Label (see Figure 3-10).
• FedEx Ground HazMat Label (see Figure 3-11).
• FedEx SmartPost Label (see Figure 3-12).
• FedEx International DirectDistribution Surface Solutions Labels (see Figure 3-13 and Figure 3-14).
3-50
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
FedEx Express U.S. Label
As shown in Figure 3-9, the upper portion of the label is blank and is folded before insertion in the shipping pouch attached to the package.
Figure 3-9: FedEx Express U.S. Label
v 10.6.1
FedEx Ship Manager® Server Installation and Configuration Guide
3-51
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
FedEx Home Delivery Label
Figure 3-10: FedEx Home Delivery Label
3-52
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
FedEx Ground HazMat Label
Figure 3-11: FedEx Ground HazMat Label
v 10.6.1
FedEx Ship Manager® Server Installation and Configuration Guide
3-53
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
FedEx SmartPost Label
See “FedEx SmartPost Labels” on page 7-27 in Chapter 7: Coding Transactions for FedEx SmartPost for more information on FedEx
SmartPost labels.
Figure 3-12: FedEx SmartPost Label
3-54
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
FedEx International DirectDistribution Surface Solutions Labels
Figure 3-13: FedEx Express International DirectDistribution Label
v 10.6.1
FedEx Ship Manager® Server Installation and Configuration Guide
3-55
Chapter 3: FedEx Ship Manager Server Label and Form Transactions
Figure 3-14: FedEx Ground International DirectDistribution Label
3-56
FedEx Ship Manager® Server Installation and Configuration Guide
v 10.6.1
CHAPTER 4: FEDEX SHIP MANAGER SERVER OPEN
SHIP TRANSACTIONS
The Open Ship shipping method lets you create an open shipment and add packages to the shipment over a period of time, giving you a
flexible way to prepare your shipment throughout the day until you are ready to ship.
This chapter describes the procedure for creating and building an Open Ship shipment using FedEx Ship Manager® Server (FSMS) and the
020/120 Global Ship Request/Reply Transaction in the following sections.
Read Chapter 2: About FedEx Ship Manager Server Transactions as a prerequisite for this chapter.
• Open Ship for FedEx Ship Manager Server
• Open Ship Process and Workflow
• About FedEx Ship Manager Server Open Ship Transactions
• Performing Pre-Ship Validation for Open Ship
• CREATE Open Ship Shipment Transaction
• ROUTE and Time-In-Transit Transaction
• RATE Open Ship Shipment Transaction
• ADD Piece Transaction
• EDIT Piece Transaction
• EDIT Open Ship Shipment Transaction
• DELETE Piece Transaction
• DELETE Shipment Transaction
• CONFIRM Piece and Print Label
• CONFIRM Piece and Shipment Transactions
• Open Ship Print Options
• FedEx Express U.S. Open Ship Transaction Samples
• FedEx Ground Open Ship Transaction Samples
• FedEx SmartPost Open Ship Transaction Samples
Open Ship for FedEx Ship Manager Server
Open Ship is a highly flexible shipping feature unique to the FSMS application.
Open Ship allows you to create and enter information for a shipment as it is received throughout the day, rather than entering all of the
shipping information only when the shipment is ready to be processed. The shipment remains "open" accepting each package as it is
entered and closing only when you confirm over a seven day period.
You can print labels for each piece as you need them or wait until the shipment is confirmed and print all labels prior to ship. This printing
preference is called Open Ship Print-As-You-Go (PAYG) and is enabled in an Open Ship transaction.
Open Ship shipments are often multiple-piece shipments (MPS) but can also be shipments that contain single packages, referred to as
single-piece shipments.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
4-1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
FedEx Services with Open Ship
You can use the Open Ship shipping method for the following FedEx services:
• FedEx Express® U.S. domestic
• FedEx Ground® U.S. domestic
• FedEx Home Delivery®
• FedEx SmartPost®
• FedEx International Priority DirectDistribution® (IPD)
• FedEx International Economy DirectDistribution℠ Service (IED)
• FedEx International Priority DirectDistribution® Freight (IDF)
• FedEx International Ground® Distribution (IGD)
• FedEx International Ground DirectDistribution® (IGDD)
• FedEx® International DirectDistribution Surface Solutions (IDD Surface)
Open Ship Process and Workflow
An Open Ship shipment typically requires multiple transactions: one to CREATE the shipment, one or more to ADD or EDIT the packages in
the shipment, and one to CONFIRM the shipment. Figure 4-1 illustrates the work flow for processing an Open Ship shipment.
4-2
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Figure 4-1: Open Ship Process Workflow
Table 4-1: Open Ship Creation
Workflow Item
Description
 CREATE Shipment
To CREATE a shipment requires the 020 Global Ship Request transaction with Field 541 (Open Ship Flags)
set to Y in the first position: Field 541 = "YNNNNNNNN".
A tracking number for the shipment is assigned by FSMS. No labels are printed for the Open Ship CREATE
shipment transaction.
- ADD Piece*
Packages are processed individually by sending an Open Ship ADD piece transaction. A shipping label with
a unique tracking number prints for each piece (aka package) processed.
To ADD a piece to a shipment, use the 020 Global Ship Request Transaction with Field 541 (Open Ship Flags)
set to Y in the 4th (fourth): 541, "NNNYNNNNN".
*not to exceed 999 pieces
per shipment
v 10.6.1
FedEx Ship Manager® Server Developer Guide
4-3
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-1: Open Ship Creation (Continued)
Workflow Item
Description
 CONFIRM Shipment
You must ADD a minimum of 2 (two) pieces before you can CONFIRM an Open Ship shipment.
To CONFIRM the shipment, send the 020 Global Ship Request Transaction with Field 541 (Open Ship Flags)
set to Y in the 9th (ninth) position: 541, "NNNNNNNNY".
Package labels and all other reports are printed to designated printers. No master is printed for FedEx®
International DirectDistribution Surface Solutions.
Package labels may be printed at the time of shipping, called Print-At-The-End (PATE) or when you CREATE,
ADD, or EDIT packages, called Print-As-You-Go (PAYG). FSMS prints reports when you perform the Open
Ship CONFIRM shipment and end-of-day Close transactions.
Note: For Open Ship Print-As-You-Go (PAYG) shipments, you must CONFIRM the shipment on the same
day as CREATE, otherwise labels will have the incorrect ship date.
Note: IPD/IED/IDF in Open Ship processes differently, see Table 12-9 step 1.
About FedEx Ship Manager Server Open Ship Transactions
Open Ship transactions consist of five steps that perform these functions:
1.
CREATE shipment
2.
ADD packages
3.
DELETE packages or EDIT information about them (optional)
4.
EDIT information about the shipment (optional)
5.
CONFIRM package and/or CONFIRM shipment
Field 541 Open Ship Flags
Each step in the process is turned off or on by an Open Ship flag that is designated in Field 541 (Open Ship Flags).
Field 541 consists of nine (9) digits that can be set to either Y (Enabled) or N (Disabled). Each position in the nine digit sequence is assigned
a function related to the Open Ship step process, such as CREATE or ADD. At least one position in the nine-digit sequence must be set to
Y. Table 4-2 lists the Open Ship flag positions, identifies the function for each position and shows the value to enter.
Table 4-2: Open Ship Flag Positions for Field 541
4-4
Position
Description
Syntax
1
CREATE the Shipment
YNNNNNNNN
2
ROUTE/Time-in-Transit
NYNNNNNNN
3
RATE the Shipment
NNYNNNNNN
4
ADD a Piece/Package
NNNYNNNNN
5
EDIT a Piece/Package
NNNNYNNNN
6
EDIT the Shipment
NNNNNYNNN
7
DELETE a Piece/Package
NNNNNNYNN
8
DELETE the Shipment
NNNNNNNYN
9
CONFIRM the Piece/Package
NNNNNNNNY
9
CONFIRM the Shipment
NNNNNNNNY
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Shipment versus Package Level Flags
Flags are specifically set to shipment or package level. In other words, you can EDIT information either for a package or a shipment, but you
must select the correct flag depending on what you want to do. You must also distinguish between shipment and package when you
CONFIRM.
Multiple Flags in Single Transaction Strings
You can use some of the Open Ship flags with each other. For example, you can CREATE a shipment and CONFIRM the shipment with one
transaction (assuming all required information to ship a package is received), or ADD a package and CONFIRM, or even EDIT data, ADD a
package, and CONFIRM.
Rules for Open Ship Transactions
Use the Open Ship method when you want to add multiple packages to a shipment over a period of time but do not know how many
packages you plan to add or when the shipment will be complete. Using Open Ship gives you the flexibility to create the shipment first and
add packages as needed. Read the rules for Open Ship transactions carefully.
Important: You must complete an Open Ship shipment within seven (7) days after the CREATE transaction. After seven (7) days, FSMS
deletes the entire shipment.
Open Ship Rules
The following rules apply to Open Ship transactions:
• Open Ship requires two fields - Field 541 (Open Ship Flags) to specify the Open Ship function (CREATE, ADD, EDIT, RATE, ROUTE or
CONFIRM) and Field 542 (Open Ship Index) to identify the Open Ship index number that tells FSMS on which shipment to perform the
function. However, Field 542 is not used for IPD open shipping. Instead use Field 1355 (IOR Facility Code) with Field 24 (Ship Date) and
Field 1274 (Service Type) to form a unique shipment.
• You can use some of the Open Ship flags with each other. For example, you can CREATE a shipment and CONFIRM the shipment with
one transaction (assuming all required information to ship a package is received), or ADD a package and CONFIRM, or even EDIT data,
ADD a package, and CONFIRM.
• You can CREATE several Open Ship shipments within the same day, but each must contain its own unique shipment index number in
Field 542. This number is used to access the shipment for future editing. After you CONFIRM the shipment, the Open Ship ID number
loses its association with the shipment and may be reused.
• You have 7 days to CONFIRM an Open Ship shipment after a Close (End-of-Day) transaction. After the 7th day, FSMS deletes the entire
shipment if you do not CONFIRM the shipment. This is not available with Print-As-You-Go (PAYG). It is only available with Print-At-TheEnd (PATE).If you do not CONFIRM a shipment on the same day you CREATE it, or if a Future Day ship date is not specified during the
CREATE transaction, then you must change the Ship Date to the current day or later.
• To ship a multiple-piece shipment (MPS) to a single consignee, use Open Ship to ADD individual packages to the shipment.
• You can choose to print labels as you CREATE, ADD and EDIT packages in a shipment. This feature is called Print-As-You-Go (PAYG)
and is available for FedEx U.S. Domestic Express (including U.S. Domestic Express C.O.D.), FedEx U.S. Domestic Ground, and FedEx
SmartPost services. For Open Ship Print-As-You-Go (PAYG) shipments, you must CONFIRM Open Ship shipments on the same day as
CREATE, otherwise labels will have the incorrect ship date.
• An Open Ship shipment (non-PAYG) must have at least one package at all times prior to CONFIRM. If a package is confirmed and is the
only package in the shipment, the entire shipment is confirmed and you can not add any more packages to the shipment.
• You can also choose to print labels at the end when you CONFIRM the shipment. This feature is called Print-At-The-End (PATE).
v 10.6.1
FedEx Ship Manager® Server Developer Guide
4-5
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Performing Pre-Ship Validation for Open Ship
You can verify a FedEx Express, FedEx Ground or FedEx Home Delivery shipment prior to label preparation and shipping to help ensure
that all package and shipment information is correctly uploaded to FedEx.
Use the 020 Global Ship Request transaction with the three fields described in Table 4-3 to pre-validate an Open Ship.
Table 4-3: Fields for Open Ship Pre-Ship Validation
Transaction: 020 Global Ship Request - Single Shot, Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Pre-Ship Validation Flag
184
Max=1
A
I
FDXE
FDXG
All
Optional
Use this field to pre-validate shipping information prior to processing the
shipping transaction.
This can be used in Open Ship shipments or in a single transaction for
FedEx Express and FedEx Ground shipping.
Valid values are:
Y — Data validated (for any shipping method, but for Open Ship after
shipment is committed to the database)
P — Data validated (for Open Ship only — before shipment is committed
to database)
N — Ships and label produced
Use with Field 541 (Open Ship Flags) set to NNNNNNNNN.
A
I
FDXE*
FDXG
FDXS
US
INTL
For FDXE:
IPD
IED
IDF
IDD
Surface
For FDXG:
IGD
IGDD
IDD
Surface
REQUIRED*
Nine one-byte Open Ship flags that identify the Open Ship function to be
performed.
Set ALL positions to N (NNNNNNNNN) to pre-validate a shipment.
*Required for Open Ship.
Open Ship Flags
541
Max=9
*C.O.D.
4-6
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-3: Fields for Open Ship Pre-Ship Validation (Continued)
Transaction: 020 Global Ship Request - Single Shot, Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
Description
Open Ship Index
542
Max=9
FDXE*
FDXG
FDXS
*C.O.D.
US
INTL
For FDXE:
IPD
IED
IDF
IDD
Surface
For FDXG:
IGD
IGDD
IDD
Surface
REQUIRED*
Include field in transaction but do not enter a value. In other transactions,
this field contains the unique number per Open Ship shipment per meter
and represents the Open Ship Index.
*Required for Open Ship.
Note: However, Field 542 is not used for IPD open shipping. Instead use
Field 1355 (IOR Facility Code) with Field 24 (Ship Date) and Field 1274
(Service Type) to form a unique shipment.
CREATE Open Ship Shipment Transaction
The first step in processing an Open Ship shipment is to create the shipment. This is achieved by coding a transaction string that includes
the Field 541 (Open Ship Flags) CREATE shipment flag (YNNNNNNNN).
After you CREATE a shipment, you can ADD one or more packages in additional transaction strings and continue to modify the shipment
until you are ready to CONFIRM and ship.
The CREATE shipment function is indicated by setting the first position flag in Field 541 (Open Ship Flags) to Y — requests FSMS to
CREATE an Open Ship shipment.
Note: When position 1 flag is set to N, no shipment is created.
In your transaction string, this looks like: 541,"YNNNNNNNN".
Both Field 541 (Open Ship Flags) and 542 (Open Ship Index) are required for the Open Ship CREATE shipment transaction using the 020
Global Ship Request transaction. Table 4-4 lists the tasks required to create an Open Ship shipment and identifies which fields to use in a
transaction to perform them. See “CREATE Open Ship Shipment” on page 4-8 for detailed information about these fields.
Table 4-4: CREATE Open Ship Shipment Fields
Action
Field ID
Field Name
Description
Transaction: 020 Global Ship Request
To create an Open Ship shipment
Set the first position of the Open Ship flag to Y.
For example, YNNNNNNNN.
Use…
Contains a nine-digit flag that specifies the action(s) is to be performed on the Open
Ship shipment.
Field 541
Open Ship Flags
To distinguish an Open Ship shipment
v 10.6.1
Assign an Open Ship index number to the shipment and include Field 542 and this
number in the CREATE shipment transaction and all subsequent transaction strings
related to the shipment, as for example each time you add a package.
FedEx Ship Manager® Server Developer Guide
4-7
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-4: CREATE Open Ship Shipment Fields (Continued)
Action
Field ID
Field Name
Description
Use…
Field 542
Open Ship Index
The Open Ship index number is a unique number that you create and include in the
CREATE Shipment transaction. You then use the number to identify which shipment
to perform an ADD, EDIT or DELETE action against. The Open Ship Index value
must be a unique number per Open Ship shipment per meter.
CREATE Open Ship Shipment
The Open Ship CREATE shipment transaction requires two fields:
• 541 — Open Ship flag set to position 1 (YNNNNNNNN)
• 542 — Shipment index number unique to the shipment to be created
Table 4-5 describes these two fields in detail.
Table 4-5: Required Fields to CREATE an Open Ship Shipment
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I
Description
Open Ship Flags
541
4-8
Max = 9
FDXE*
FDXG
FHD
FDXS
US
INTL
For FDXE:
IPD
IED
*includes IDF
C.O.D.
IDD
Surface
For FDXG:
IGD
IGDD
IDD
Surface
Field Level: Shipment
REQUIRED*
Nine one-byte flags which are set to Y to indicate Open Ship function.
Flag must be either Y or N; you cannot enter all Ns.
To CREATE a shipment, set the 1st position of the flag to Y.
For example, YNNNNNNNN requests to create an Open Ship shipment
to which packages will be added.
*Required for Open Ship.
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-5: Required Fields to CREATE an Open Ship Shipment (Continued)
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
Description
Open Ship Index
542
Max = 9
FDXE*
FDXG
FHD
FDXS
US
INTL
For FDXE:
IPD
IED
*includes IDF
C.O.D.
IDD
Surface
For FDXG:
IGD
IGDD
IDD
Surface
REQUIRED*
Set to the unique number passed in the CREATE transaction. The value
is a unique number per Open Ship shipment per meter and represents
the Open Ship Index.
*Required for Open Ship.
Note: Field 542 is not required if you are simultaneously performing a
CREATE or ADD transaction.
Examples of simultaneous transactions are: YYNNNNNNN which
performs a shipment level CREATE and Route/Time in Transit
transaction or NYNYNNNNN which performs a package level ADD and
shipment level Route/Time in Transit together in the same transaction.
Note: However, Field 542 is not used for IPD open shipping. Instead use
Field 1355 (IOR Facility Code) with Field 24 (Ship Date) and Field 1274
(Service Type) to form a unique shipment.
CREATE Open Ship Print-As-You-Go Shipment
Open Ship Print-As-You-Go (PAYG) shipping gives FedEx customers the ability to print labels as they CREATE, ADD and EDIT shipment
pieces rather than waiting until the shipment is confirmed.
Open Ship Print-As-You-Go shipping is available for the following FedEx services:
• FedEx Express — U.S. Domestic (Package and Freight)
• FedEx Express C.O.D. — U.S. Domestic
• FedEx Ground — U.S. Domestic
• FedEx SmartPost
Note: Open Ship Print-As-You-Go (PAYG) is not available for International FedEx Express shipments. Use the 020 Global Ship Request
transaction with Field 2600, as shown in Table 4-6 to enable the Print-As-You-Go (PAYG) mode for your Open Ship shipment.
Note: For Open Ship Print-As-You-Go (PAYG) shipments, you must CONFIRM the shipment on the same day as CREATE, otherwise labels
will have the incorrect ship date.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
4-9
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-6: Open Ship Print-As-You-Go (PAYG) Fields
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Package Association and Print Mode
2600
Max=2
N
I
FDXE
FDXG
FDXS
US
Optional
Specifies the type of package association and print label mode to use —
that is, whether labels “print-at-end” or “print-as-you-go”.
Valid values are for FedEx Express and FedEx Ground only:
1 — (default) Domestic MPS non-associated, FedEx Express C.O.D.
MPS associated, FedEx Express International MPS associated. Prints
labels using package or shipment confirmation rules.
2 — Domestic U.S. MPS for FedEx Express and FedEx Ground services.
Package association. Prints labels with each shipment Confirm
transaction (Print-At-The-End).
3 — Domestic U.S, MPS for FedEx Express and FedEx Ground services.
Package association. Prints labels for each Create/Add Package
transaction (Print-As-You-Go).
Note: For Open Ship Print-As-You-Go (PAYG) shipments, you must
CONFIRM the shipment on the same date as CREATE, otherwise labels
will have the incorrect ship date.
4 — Package not-associated and labels printed with each Create/Add
Piece transaction for Domestic MPS; Print-As-You-Go (PAYG-NA) for
FedEx SmartPost.
ROUTE and Time-In-Transit Transaction
FedEx Ship Manager Server returns FedEx Express routing or FedEx Ground time-in-transit information for an Open Ship shipment in the
120 Global Ship Reply transaction.
To receive route or time-in-transit information, you must first enter the minimum required fields in a 020 Global Ship Request and enable
FedEx to process the FedEx Express route or calculate the FedEx Ground transit time. For a list of minimum required fields, see “020/120
Global Ship Request/Reply Transaction” in the FedEx Ship Manager® Server Transaction Coding Reference Guide.
Table 4-7 describes the required fields to request FedEx routing or time-in-transit information.
4-10
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-7: Required Fields for Open Ship ROUTE or Time-in-Transit Information
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Recipient Postal Code
17
Max=16
N
I
All
US
INTL
For FDXE:
IPD
IED
IDF
IDD
Surface
For FDXG:
IGD
IGDD
IDD
Surface
Field Level: Shipment
REQUIRED.
Postal code for the city and state or province code of the Recipient
address.
For FedEx international shipments: Canada (CA), Puerto Rico (PR) and
U.S. must always use valid postal codes.
For a list of countries that use postal codes, see Appendix C in the FedEx
Ship Manager® Server Transaction Coding Reference Guide.
A
I
All
US
INTL
For FDXE:
IPD
IED
IDF
IDD
Surface
For FDXG:
IGD
IGDD
IDD
Surface
Field Level: Shipment
REQUIRED*
Two-digit code indicating the country of the Recipient address.
*Required for FedEx International Priority DirectDistribution (IPD), FedEx
International Economy DirectDistribution (IED) and FedEx International
Priority DirectDistribution Freight (IDF) shipments.
*Required for FedEx SmartPost.
*Required for ADD Piece Open Ship function.
See Appendix C in the Transaction Coding Reference Guide for country
codes.
Recipient Country
50
v 10.6.1
Max=2
FedEx Ship Manager® Server Developer Guide
4-11
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-7: Required Fields for Open Ship ROUTE or Time-in-Transit Information (Continued)
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
All
All
Field Level: Shipment
REQUIRED* or Defaulted.
Unique number assigned to a FedEx shipping account (used in each
transaction to identify the revenue/shipping activity of a shipment).
Defaults to the master meter number.
*Required if the meter number is different than the meter number
configured as the default.
Note: If a one-to-one relationship exists between meter numbers and
account numbers (in other words, there is no more than one meter
number per account number), then the meter number or the account
number alone may be used in the transaction.
Note: In FSMS version 10.0.1, meter numbers are expanded to ninedigits in length. Your assigned meter number may be any length up to
nine-digits.
A
I
All
US
INTL
For FDXE:
IPD
IED
IDF
IDD
Surface
For FDXG:
IGD
IGDD
IDD
Surface
Field Level: Shipment
REQUIRED*
Nine one-byte flags which are set to Y to indicate Open Ship function.
Flag must be either Y or N; you cannot enter all Ns.
To ROUTE a shipment, set the 2nd position of the flag to Y.
For example, NYNNNNNNN requests the FedEx Express routing or
FedEx Ground time-in-transit information.
*Required for Open Ship.
Description
Meter Number
498
Min=7
Max=9
Open Ship Flags
541
4-12
Max=9
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-7: Required Fields for Open Ship ROUTE or Time-in-Transit Information (Continued)
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I
Description
Open Ship Index
542
Max=9
All
US
INTL
For FDXE:
IPD
IED
IDF
IDD
Surface
REQUIRED*
Set to the unique number passed in the CREATE transaction. The value
is a unique number per Open Ship shipment per meter and represents
the Open Ship Index.
*Required for Open Ship.
Note: Field 542 is not required if you are simultaneously performing a
CREATE or ADD transaction.
Examples of simultaneous transactions are: YYNNNNNNN which
performs a shipment level CREATE and Route/Time in Transit
transaction or NYNYNNNNN which performs a package level ADD and
shipment level Route/Time in Transit together in the same transaction.
Note: However, Field 542 is not used for IPD open shipping. Instead use
Field 1355 (IOR Facility Code) with Field 24 (Ship Date) and Field 1274
(Service Type) to form a unique shipment.
Service Type
1274
Min=2
Max=3
N
I
All
US
INTL
For FDXE:
IPD
IED
IDF
IDD
Surface
For FDXG:
IGD
IGDD
IDD
Surface
Field Level: Shipment
REQUIRED.
Service type provided by the shipper.
Valid service types for Open Ship are:
FedEx Express U.S.:
01 — FedEx Priority Overnight
03 — FedEx 2Day
05 — FedEx Standard Overnight
06 — FedEx First Overnight
20 — FedEx Express Saver
For FedEx SmartPost shipping, reference Field 2417 in Chapter 7 of
Developer Guide.
FedEx International Services (including U.S. export):
01 — FedEx International Priority
03 — FedEx International Economy
17 — FedEx International Economy DirectDistribution Service
18 — FedEx International Priority DirectDistribution
70 — FedEx International Priority Freight
84 — FedEx International Priority Direct Distribution Freight
121 — FedEx International Ground Distribution (IGD)
Note: For FedEx SmartPost shipping, reference Field 2417 in Table 7-9
on page 7-49.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
4-13
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
RATE Open Ship Shipment Transaction
To request rates for an Open Ship shipment, use the 020 Global Ship Request transaction with the following two fields:
• 541 — position 3 set to Y (NNYNNNNNN) which sets the flag to the shipment level “Rate the Shipment” function.
• 542 — set to the unique number passed in the CREATE transaction.
Table 4-8 lists the fields required to code a RATE request for a FedEx Open Ship shipment using a 020 Global Ship Request transaction.
Table 4-8: Required Fields to RATE an Open Ship Shipment
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Method
A
I
FDXE
FDXG
FDXS
US
INTL
FDXE:
IPD
IED
IDF
IDD
Surface
FDXG:
IGD
IGDD
IDD
Surface
Field Level: Shipment
REQUIRED*
Nine one-byte flags which are set to Y to indicate Open Ship function.
Flag must be either Y or N; you cannot enter all Ns.
To RATE a shipment, set the 3rd position of the flag to Y.
For example, NNYNNNNNN requests the rate for the Open Ship
shipment.
*Required for Open Ship.
N
I
FDXE
FDXG
FDXS
US
INTL
FDXE:
IPD
IED
IDF
IDD
Surface
FDXG:
IGD
IGDD
IDD
Surface
REQUIRED*
Set to the unique number passed in the CREATE transaction. The value
is a unique number per Open Ship shipment per meter and represents
the Open Ship Index.
*Required for Open Ship.
Note: Field 542 is not required if you are simultaneously performing a
CREATE or ADD transaction.
Examples of simultaneous transactions are: YNYNNNNNN which
performs a shipment level CREATE and RATE transaction, or
NNYYNNNNN which performs a package level ADD and shipment level
RATE together in the same transaction.
Description
Open Ship Flags
541
Max = 9
Open Ship Index
542
4-14
Max = 9
Note: However, Field 542 is not used for IPD open shipping. Instead use
Field 1355 (IOR Facility Code) with Field 24 (Ship Date) and Field 1274
(Service Type) to form a unique shipment.
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
ADD Piece Transaction
FedEx Ship Manager Server first creates a master Open Ship shipment and then allows you to add pieces (aka packages) to the "open"
shipment.
You can add the first package to the shipment in the initial 020 Global Ship Request transaction when you CREATE the Open Ship
shipment, or you can add it in a separate ADD piece 020 transaction. You must send a separate ADD piece transaction for each of your
packages as you prepare your shipment throughout the day.
You can choose to print labels for packages as you ADD each package to the shipment, or you can wait until the shipment is confirmed and
print labels at the end. Use the method that is most efficient for your shipping operation.
To ADD a piece (aka package) to an Open Ship shipment in a 020 Global Ship Request Transaction, use the fields described in Table 4-9:
Required Fields to ADD Package to Open Ship Shipment, on page 4-15.
Note: For Open Ship Print-As-You-Go (PAYG) shipments, you must CONFIRM the shipment on the same day as CREATE, otherwise labels
will have the incorrect ship date.
Table 4-9: Required Fields to ADD Package to Open Ship Shipment
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I
Description
Recipient Country
50
Max = 2
FDXE
FDXG
FHD
All
Field Level: Shipment
REQUIRED*
Two-digit code indicating the country of the Recipient address.
*Required for FedEx International Priority DirectDistribution (IPD), FedEx
International Economy DirectDistribution (IED) and FedEx International
Priority DirectDistribution Freight (IDF) shipments.
*Required for FedEx SmartPost.
*Required for ADD Piece Open Ship function.
See Appendix C in the FedEx Ship Manager® Server Transaction Coding
Reference Guide for country codes.
Open Ship Flags
541
v 10.6.1
Max = 9
A
I
FDXE
FDXG
US
INTL
FDXE:
IPD
IED
IDF
IDD
Surface
FDXG:
IGD
IGDD
IDD
Surface
Field Level: Package
REQUIRED*
Nine one-byte flags which are set to Y to indicate Open Ship function.
Flag must be either Y or N; you cannot enter all Ns.
To ADD a package, set the 4th position of the flag to Y.
For example, NNNYNNNNN requests to add a package to an Open Ship
shipment.
*Required for Open Ship.
FedEx Ship Manager® Server Developer Guide
4-15
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-9: Required Fields to ADD Package to Open Ship Shipment (Continued)
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
Description
Open Ship Index
542
Max = 9
FDXE
FDXG
US
INTL
FDXE:
IPD
IED
IDF
IDD
Surface
FDXG:
IGD
IGDD
IDD
Surface
REQUIRED*
Set to the unique number passed in the CREATE transaction. The value
is a unique number per Open Ship shipment per meter and represents
the Open Ship Index.
*Required for Open Ship.
Note: Field 542 is not required if you are simultaneously performing a
CREATE or ADD transaction.
Examples of simultaneous transactions are: YYNNNNNNN which
performs a shipment level CREATE and Route/Time in Transit
transaction or NYNYNNNNN which performs a package level ADD and
shipment level Route/Time in Transit together in the same transaction.
All
Field Level: Package
REQUIRED
Note: However, Field 542 is not used for IPD open shipping. Instead use
Field 1355 (IOR Facility Code) with Field 24 (Ship Date) and Field 1274
(Service Type) to form a unique shipment.
Packaging Type
1273
Max=2
N
I
FDXE
Available for FedEx Express® (U.S. domestic and international):
01 — Customer packaging
02 — FedEx Pak
03 — FedEx Box
04 — FedEx Tube
06 — FedEx Envelope
4-16
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-9: Required Fields to ADD Package to Open Ship Shipment (Continued)
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
Description
Service Type
1274
Min=2
Max=3
FDXE
FDXG
All
Field Level: Shipment
REQUIRED.
Service type provided by the shipper.
Valid service types for Open Ship are:
FedEx Express U.S.:
01 — FedEx Priority Overnight
03 — FedEx 2Day
05 — FedEx Standard Overnight
06 — FedEx First Overnight
20 — FedEx Express Saver
FedEx International Services (including U.S. export):
01 — FedEx International Priority
03 — FedEx International Economy
17 — FedEx International Economy DirectDistribution Service
18 — FedEx International Priority DirectDistribution
70 — FedEx International Priority Freight
84 — FedEx International Priority Direct Distribution Freight
121 — FedEx International Ground Distribution (IGD)
Note: For FedEx SmartPost shipping, reference Field 2417 in Table 7-9
on page 7-49.
Package Weight
If you are shipping FedEx Express® or FedEx Ground U.S. domestic packages, you are also required to pass Field 1670 (Package Weight/
Shipment Weight) in a transaction before you send the CONFIRM transaction. You must also include Field 1670 in the initial ADD package
transaction, but it is not required.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
4-17
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-10: Package Weight Field - Required before CONFIRM
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Package Weight\Shipment Weight
1670
Max = 8.2 A
I
All
All
Field Level: Shipment for all FedEx services
REQUIRED*
Weight of package or shipment.
*Required for U.S. domestic shipping (including FedEx Ground HazMat
shipments) to specify individual package weights. FSMS will perform the
weight summation and package count.
*Required if Field 1493 is Y.
*Required to receive rate quotes.
This weight field supports two implied decimals for ALL shipments and
does not require any distinction between FedEx Express, FedEx Ground
or FedEx International shipping.
For U.S. Domestic Shipping:
You must enter individual package weights only. FSMS performs the
weight summation and package count. This method is optional for all
FedEx International shipping including U.S. Export.
For all FedEx International and intra-Canada Shipping:
You may enter the total shipment weight rather than the individual
package weights. If you enter the total shipment weight, you must also
use Field 116 (Package Total) to indicate the total number of packages in
the shipment.
Maximum weights allowed are:
FedEx Express (non-Freight) — 150 LBS
FedEx Ground — 150 LBS
FedEx Home Delivery — 70 LBS
ADD Package to Open Ship Print-As-You-Go Shipment
To Add a package to a US Domestic FedEx Express or FedEx Ground shipment that has the Open Ship Print-As-You-Go (PAYG) option
enabled, use the 020 Global Ship Request transaction and include this required field:
• 541 — position 4 set to Y (NNNYNNNNN) which sets the flag to the package level “Add a Package” function.
Note: Field 2600 is not required.
ADD Piece - Shipment and Package Level Fields
When you ADD the first package to an Open Ship shipment, the fields that you pass in the initial ADD transaction may be applied to all
subsequent packages you add to the shipment.
Other fields are applied at the package level and can be different for each package you ADD or EDIT in an Open Ship shipment. Table 4-11
lists fields that can differ from the shipment’s initial package.
4-18
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-11: Package Level Fields for ADD Package to Open Ship Shipment
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Reference Information
25-#
Max=39
A
I
FDXE
FDXG
All
Field Level: Package for all services except for FedEx Express
international MPS which is shipment level.
Optional
Use this field for optional notes (FedEx Express) and customer reference
number CRN (FedEx Ground).
For FedEx Express International MPS, this is a shipment-level field.
For all other services, this field is a package-level field and must not be
used if a shipment-level customer reference number (CRN) has been
assigned in Field 3003 (Shipment Customer Reference Information).
If this field is used simultaneously with Field 3003, then Field 3003 is
ignored. Package-level fields take precedence.
This value prints on the FedEx Express shipping label, various reports,
and the FedEx Express Shipper’s Declaration for Dangerous Goods
1421C form. This value also is displayed in the Customer Reference field
on the FedEx Ground invoice.
A
I
FDXE
FDXG
US
Field Level: Shipment level for FedEx Express; Package level for FedEx
C.O.D. only Ground
REQUIRED*
When set to Y, indicates that a package or shipment is being shipped
Collect on Delivery (C.O.D.), and "C.O.D." prints in the box beside the
recipient name on the bill of lading. Multiple-occurrence field.
*Required for C.O.D.
Valid values are:
Y — Package is C.O.D. at the shipment level for FedEx Express and at
the package level for FedEx Ground.
N — Package is NOT sent C.O.D. (default)
S — Package is sent C.O.D. at the Shipment level for FedEx Ground.
I
FDXE
FDXG
All
Field Level: Shipment level for FedEx Express; Package level for FedEx
C.O.D. only Ground.
REQUIRED.
C.O.D. Flag
27
Max=1
C.O.D. Collect Amount
53
Max=10.2 N
Amount of payment that must be collected upon delivery of the FedEx
Collect on Delivery (C.O.D.) package.
Maximum of $25,000 for FedEx Ground if guaranteed funds and
maximum of $750 if cash.
Multiple-occurrence field.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
4-19
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-11: Package Level Fields for ADD Package to Open Ship Shipment (Continued)
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
FDXE
FDXG
All
Field Level: Package
REQUIRED*
Height measurement per package.
No implied decimal places.
*Required for shipping FedEx Express Freight.
Recommended if using customer packaging to ensure accurate billing as
dimensional weighting or oversize conditions may apply.
For FedEx SmartPost: field is optional; always enter in inches.
Minimum FedEx Express dimensions are in inches: 1" x 1" x 1" (L x W x
H); or in centimeters:1 cm. x 1 cm. x 1 cm. (L x W x H).
See the FedEx Service Guide for service details related to Dim Weighting
for FedEx Express and oversize conditions for FedEx Express and FedEx
Ground.
Note: FSMS does not sort dimensions. For correct dimensional weight
calculations, the longest dimension must be placed in Field 59 (Package
Length).
N
I
FDXE
FDXG
All
Field-Level: Package
REQUIRED*
Width measurement per package.
No implied decimal places.
*Required for shipping FedEx Express Freight.
Recommended if using customer packaging to ensure accurate billing as
dimensional weighting or oversize conditions may apply.
For FedEx SmartPost: field is optional; always enter in inches.
Minimum FedEx Express dimensions are in inches: 1" x 1" x 1" (L x W x
H); or in centimeters:1 cm. x 1 cm. x 1 cm. (L x W x H).
Note: FSMS does not sort dimensions. For correct dimensional weight
calculations, the longest dimension must be placed in Field 59 (Package
Length).
N
I
FDXE
FDXG
All
Field Level: Package
REQUIRED*
Length measurement per package.
No implied decimal places.
*Required for shipping FedEx Express Freight.
Recommended if using customer packaging to ensure accurate billing as
dimensional weighting or oversize conditions may apply.
For FedEx SmartPost: field is optional; always enter in inches.
Minimum FedEx Express dimensions are in inches: 1" x 1" x 1"
Description
Package Height
57
Max=3
Package Width
58
Max=3
Package Length
59
4-20
Max=3
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-11: Package Level Fields for ADD Package to Open Ship Shipment (Continued)
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
Description
Package Length
59
(cont.)
Max=3
FDXE
FDXG
Declared Value/Carriage Value
69
Max=14.2 N
Al
(L x W x H); or 1 cm. x 1 cm. x 1 cm. (L x W x H).
Note: FSMS does not sort dimensions. For correct dimensional weight
calculations, the longest dimension must be placed in Field 59 (Package
Length).
Transactions: 020 Global Ship Request
I
FDXE
FDXG
US
INTL
Freight
Field Level: Shipment for FedEx Express international shipments;
Package for FedEx Express - U.S. domestic and FedEx Ground
REQUIRED*
Total dollar amount declared or carriage value of the shipment. This field
supports the 14.2 numeric format and has two implied decimal places.
*Required for all U.S. shipments insured with FedEx.
Values must contain only numeric characters (no commas, "." or "$").
Note: All currency fields for FedEx Express Freight must be in USD.
When used to create/print a bill of lading (BOL) for FedEx Express
Freight, declared value cannot exceed $100,000 USD.
Note: Carriage Value cannot exceed the Customs Value.
Note: If you need to use a 14.2 numeric format, use Field 69 instead of
Field 26.
See the FedEx Service Guide for allowable limits.Carriage value per
package.
For this shipment, use any method.
FDXE
FDXG
All
DG and
HazMat
service
only
Field Level: Shipment
REQUIRED*
Indicates dangerous goods (DG) and/or hazardous materials (HazMat)
are contained in the shipment.
*Required if shipping FedEx Express Dangerous Goods, ORM-D or
Ground HazMat. Not allowed for Ground ORM-D.
Set to Q to indicate shipment contains EPRRQ commodity.
Valid values are:
A — Accessible Dangerous Goods (ADG)
I — Inaccessible Dangerous Goods (IDG)
E — Excepted Quantities
Q — Excepted Package Radioactive Reportable Quantity (EPRRQ)
Y — Shipment contains Dangerous Goods/HazMat
N — Shipment contains no Dangerous Goods/HazMat
Note: Values are not case-sensitive; “Q” and “q” both indicate EPRRQ.
Dangerous Goods/HazMat Flag
1331
v 10.6.1
Max=1
A
I
FedEx Ship Manager® Server Developer Guide
4-21
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-11: Package Level Fields for ADD Package to Open Ship Shipment (Continued)
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Dangerous Goods/HazMat Flag
1331
(cont)
Max=1
A
I
FDXE
FDXG
All
DG and
HazMat
service
only
For “All Packed in Ones,” calculation and printing of Q on the 1421C from
shall be excluded if:
• One of the commodities is Dry Ice (UN ID 1845) or
• If columns H, J, and L on 1421C indicate “No Limit” or
• When only one commodity qualified for the calculation
Package Weight/Shipment Weight
1670
Max = 8.2 A
I
FDXE
FDXG
All
Field Level: Shipment for international and intra-Canada, Package for
U.S. domestic.
REQUIRED*
Weight of package or shipment.
*Required for U.S. domestic shipping (including FedEx Ground HazMat
shipments) to specify individual package weights. FSMS will perform the
weight summation and package count.
*Required if Field 1493 is Y.
*Required to receive rate quotes.
This weight field supports two implied decimals for ALL shipments and
does not require any distinction between FedEx Express, FedEx Ground
or FedEx International shipping.
For U.S. Domestic Shipping:
You must enter individual package weights only. FSMS performs the
weight summation and package count. This method is optional for all
FedEx International shipping including U.S. Export.
For all FedEx International and intra-Canada Shipping:
You may enter the total shipment weight rather than the individual
package weights. If you enter the total shipment weight, you must also
use Field 116 (Package Total) to indicate the total number of packages in
the shipment.
Maximum weights allowed are:
FedEx Express (non-Freight) — 150 LBS
FedEx Ground — 150 LBS
FedEx Home Delivery — 70 LBS
I
FDXE
FDXG
US
CA
REQUIRED*
Specifies dry ice weight in the same unit of measure as the package
weight (LBS or KGS). Two implied decimal places regardless of weight
type.
Dry Ice Weight
1684-#
4-22
Max=10.2 N
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-11: Package Level Fields for ADD Package to Open Ship Shipment (Continued)
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I
Description
E.C.O.D. Flag
3014
Max=1
FDXG
All
Field Level: Package for FedEx Ground.
REQUIRED*
When set to Y, indicates that a package is being shipped Electronic
Collect on Delivery (E.C.O.D.). Multiple-occurrence field.
*Required for FedEx Ground Electronic Collect on Delivery service.
Valid values are:
N — Package is NOT sent E.C.O.D. (default)
Y — Package is sent E.C.O.D. at the shipment level for FedEx Express
and at the package level for FedEx Ground.
S — Package is sent E.C.O.D. at the shipment level for FedEx Ground.
Note: FSMS defaults to C.O.D. To enable E.C.O.D. you must check the
E.C.O.D. checkbox on the Meter Settings tab of the FSMS Configuration
Utility.
FDXE
FDXG
All
Optional
Indicates nonstandard packaging is used.
Nonstandard packaging is a container that meets one of these criteria:
• Greater than 60" on any one side (not to exceed 108")
• Not fully enclosed/encased in an outer shipping container
• Encased in an outer container made of metal, wood, hard plastic or
foamed material
Valid values are:
Y — nonstandard packaging used
N — standard packaging used (default)
If you enter dimensions or dimensional criteria that are nonstandard,
FSMS sets this flag to Y automatically.
FDXE
FDXG
Freight
US
CA
MX
INTL
Field Level: Package
Optional
When used to create/print a bill of lading (BOL), this prints in the
Purchase Order # section of the BOL. Each additional BOL order number
prints directly below each article description. Field 3056 is the only field
that supplies the full set for the BOL.
For Domestic FedEx Ground and International: this field prints the
package purchase order number to a thermal label.
For intra-U.S., intra-CA, and intra-MX this is displayed on the FedEx
Express laser and image labels. It is displayed in the Ref. #2 field on the
FedEx Express invoice and P.O. # field on the FedEx Ground invoice.
Additional Handling Surcharge
3018
Max=1
A
I
Package Purchase Order Number
3056
v 10.6.1
Max=30
AKE
I
FedEx Ship Manager® Server Developer Guide
4-23
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-11: Package Level Fields for ADD Package to Open Ship Shipment (Continued)
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Package Purchase Order Number
3056
(cont.)
Max=30
AKE
I
FDXE
FDXG
Freight
US
CA
MX
INTL
Note: This field is a package level field and should not be used if a
shipment level purchase order number has been assigned in Field 3001
(Shipment Purchase Order Number). If this field is used simultaneously
with Field 3001, then Field 3001 is ignored. Package level fields take
precedence.
I
FDXE
FDXG
US
CA
MX
INTL
Field Level: Package
Optional
Prints the package invoice number on the thermal label.
For intra-U.S, intra-CA, and intra-MX this is displayed on the FedEx
Express laser and image labels. It is displayed in the Ref. #3 field on the
FedEx Express invoice.
Field 3057 is a package level field and must not be used if a shipment
level invoice number has been assigned in Field 3002 (Shipment Invoice
Number). If this field is used simultaneously with Field 3002, then Field
3002 is ignored. Package level fields take precedence.
FDXG
FDXS
US
CA
Field Level: Package
Optional
Indicates if a FedEx Ground or FedEx Home Delivery package meets an
oversize condition.
FedEx Ground package oversize values are:
1 — if length+girth is > 84" and <109" and weight is >30 LBS
2 — if length+girth is >108" and <131" and weight is <50 LBS
3 — if length+girth is >108" and <131" and weight is <50 LBS
FedEx Home Delivery package oversize values are:
1 — if length+girth is > 84" and <109" and weight is <30 LBS
2 — if length+girth is >108" and <131" and weight is <50 LBS
3 — if length+girth is >130" and <166" and weight is <70 LBS
If you enter dimensions or dimensional criteria that meet oversize
guidelines, FSMS sets this value automatically.
Note: A $30 surcharge will be applied to packages that meet the OS 3
requirements. This surcharge is currently not supplied in the rate quote.
To apply this surcharge code to your application, add the surcharge when
this field returns a value of 3 in the 120 Global Ship Reply transaction.
Package Invoice Number
3057
Max=30
A
FedEx Ground Oversize Indicator
3124
4-24
Max=1
A
I
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Returned ADD Piece Fields
The 120 Global Ship Reply to an Open Ship ADD package transaction includes the tracking number of the newly added package.
Table 4-12: Returned Field for Add Piece to Open Ship Shipment
Transaction: 120 Global Ship Request - Open Ship MPS
Field
ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I/O
Description
Tracking Number
29
Min=12
Max=25
FDXE
FDXG
FDXS
All
REQUIRED*
Tracking number of the package or piece in a multiple-piece shipment
(MPS).
*Required with Field 541 to identify the package to ADD, EDIT or
DELETE in an Open Ship 020/120 Global Ship transaction.
EDIT Piece Transaction
To edit information about a package in an Open Ship shipment, including the Master piece (first package added), you must include the fields
listed in Table 4-13 in a 020 Global Ship Request transaction.
Table 4-13: EDIT Piece Open Ship Fields
Action
Field ID
Field Name
Description
Transaction: 020 Global Ship Request
To edit a piece in a shipment
Set position 5 to Y (NNNNYNNNN) which sets the flag at the package level to the
EDIT package function.
Use…
Contains a nine-digit flag that specifies the action(s) is to be performed on the Open
Ship shipment.
Field 541
Open Ship Flags
To distinguish an Open Ship shipment
Include the Open Ship index number that you assigned to the shipment when you
created it.
Use…
The Open Ship index number is a unique number that you specify in the CREATE
shipment transaction. You then use the number to identify which shipment to perform
the EDIT action against. The Open Ship Index value must be a unique number per
Open Ship shipment per meter.
Field 542
Open Ship Index
To specify tracking number for the piece
Enter the package tracking number to ensure the correct piece gets edited in the
Open Ship shipment.
Use…
Tracking number of the package or piece in a multiple-piece shipment (MPS).
*Required with Field 541 to identify the package to ADD, EDIT or DELETE.
Field 29
Tracking Number
Note: Editing an Open Ship PAYG shipment results in different label printing and tracking behaviors. See the following topics for details.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
4-25
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
EDIT Piece Fields
Table 4-14 lists the minimum fields required to EDIT a package that has been added to an Open Ship shipment using the 020 Global Ship
Request transaction.
Table 4-14: Required Fields to EDIT an Open Ship Package
Transaction: 020 Global Ship Request - Open Ship MPS
Field
ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I/O
Description
Tracking Number
29
Min=12
Max=25
FDXE*
FDXG
FDXS
All
REQUIRED*
Tracking number of the package or piece in a multiple-piece shipment
(MPS).
*Required with Field 541 to identify the package to ADD, EDIT or
DELETE in an Open Ship 020/120 Global Ship transaction.
All
Field Level: Shipment
REQUIRED* or Defaulted.
Unique number assigned to a FedEx shipping account (used in each
transaction to identify the revenue/shipping activity of a shipment).
Defaults to the master meter number. This field ensures the tracking
number obtained is from the range assigned in the requesting meter.
*Required if the meter number is different than the meter number
configured as the default.
*Required for reprinting reports.
*includes
C.O.D.
Meter Number
498
Max=9
N
I
FDXE*
FDXG
FDXS
*includes
C.O.D.
Note: If a one-to-one relationship exists between meter numbers and
account numbers (in other words, there is no more than one meter
number per account number), then the meter number or the account
number alone may be used in the transaction.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Meter numbers may be any length up to nine-digits.
Open Ship Flags
541
Max = 9
A
I
FDXE*
FDXG
FDXS
*includes
C.O.D.
4-26
All
Field Level: Package
REQUIRED*
Nine one-byte flags which are set to Y to indicate Open Ship function.
Flag must be either Y or N; you cannot enter all Ns.
To EDIT a package, set the 5th position of the flag to Y.
For example, NNNNYNNNN requests to edit a package that was
previously added to an Open Ship shipment.
*Required for Open Ship.
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-14: Required Fields to EDIT an Open Ship Package (Continued)
Transaction: 020 Global Ship Request - Open Ship MPS
Field
ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
Description
Open Ship Index
542
Max = 9
FDXE*
FDXG
FDXS
*includes
C.O.D.
All
REQUIRED*
Set to the unique number passed in the CREATE transaction. The value
is a unique number per Open Ship shipment per meter and represents
the Open Ship Index.
*Required for Open Ship.
Note: Field 542 is not required if you are simultaneously performing a
CREATE or ADD transaction.
Examples of simultaneous transactions are: YYNNNNNNN which
performs a shipment level CREATE and Route/Time in Transit
transaction, or NYNYNNNNN which performs a package level ADD and
shipment level Route/Time in Transit together in the same transaction.
Note: However, Field 542 is not used for IPD open shipping. Instead use
Field 1355 (IOR Facility Code) with Field 24 (Ship Date) and Field 1274
(Service Type) to form a unique shipment.
Domestic FedEx Express PAYG - Editing an Open Ship Piece
For FedEx Express U.S. C.O.D. PAYG pieces, you can edit a piece (aka package) in an Open Ship shipment prior to a CONFIRM
transaction. To do this, you must set Field 541 to Y in the 6th position (NNNNNYNNN) which sets the flag to the shipment level EDIT
function. FedEx Ship Manager Server prints new labels for all pieces that you edit in this way and preserves the tracking numbers. Printed
labels use the Label Type and Printer ID assigned to the Master piece, which is the original CREATE, ADD or EDIT piece.
About FedEx Express C.O.D. PAYG Sequence and Tracking Numbers
When you edit or delete a FedEx Express U.S. C.O.D. PAYG shipment prior to a CONFIRM shipment, the 120 Global Ship Reply transaction
returns a new Master tracking number in Field 1123 (Master Tracking Number), and a package level tracking number in multiple occurrence
in Field 29. Field 116 (Package Total) returns the total number of pieces in the shipment.
All new labels are generated with new sequence numbers. The new sequence numbers reflect the new sequence position of the package.
For example, the 5th package added out of a total of 5 pieces in a shipment is given the new sequence number 5-5, indicating it is the 5th of
a total of 5 packages.
EDIT Open Ship Shipment Transaction
Use the 020 Global Ship Request transaction with the following two fields to EDIT shipment level data for an Open Ship shipment:
• 541 — position 6 set to Y (NNNNNYNNN) which sets the flag to the shipment level “Edit the Shipment” function.
• 542 — set to the unique number passed in the CREATE transaction.
When you CREATE an Open Ship shipment, send all common shipment level information in the original Open Ship CREATE transaction.
Next, add information unique to each package with every new ADD package Open Ship transaction. This method eliminates duplication of
existing data and increases the processing speed of the transaction.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
4-27
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
EDIT Shipment Fields
Table 4-15 lists the fields required to use the 020 Global Ship Request transaction to EDIT an Open Ship shipment.
Table 4-15: Required Fields to EDIT an Open Ship Shipment
Transaction: 020 Global Ship Request - Open Ship MPS
Field
ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I
FDXE
FDXG
All
Field Level: Shipment
REQUIRED*
Nine one-byte flags which are set to Y to indicate Open Ship function.
Flag must be either Y or N; you cannot enter all Ns.
To EDIT a shipment, set the 6th position of the flag to Y.
For example, NNNNNYNNN requests to add or edit data for an Open
Ship shipment.
*Required for Open Ship.
N
I
FDXE
FDXG
All
REQUIRED*
Set to the unique number passed in the CREATE transaction. The value
is a unique number per Open Ship shipment per meter and represents
the Open Ship Index.
*Required for Open Ship.
Note: Field 542 is not required if you are simultaneously performing a
CREATE or ADD transaction.
Examples of simultaneous transactions are: YYNNNNNNN which
performs a shipment level CREATE and Route/Time in Transit
transaction or NYNYNNNNN which performs a package level ADD and
shipment level Route/Time in Transit together in the same transaction.
Description
Open Ship Flags
541
Max = 9
Open Ship Index
542
Max = 9
Note: However, Field 542 is not used for IPD open shipping. Instead use
Field 1355 (IOR Facility Code) with Field 24 (Ship Date) and Field 1274
(Service Type) to form a unique shipment.
DELETE Piece Transaction
There are two ways to delete a package from an Open Ship shipment:
• Delete the piece before you CONFIRM using the 020 Global Ship Request transaction.
• Delete the piece after you CONFIRM using the 023 Global Delete Request transaction.l
For more information about deleting a package in an Open Ship shipment, see the following topics.
4-28
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
DELETE Piece - Prior To CONFIRM
Use the 020 Global Ship Request transaction with the following fields to specify deletion of a package from an Open Ship shipment prior to
sending a CONFIRM transaction:
• 541 — position 7 set to Y (NNNNNNYNN) which sets the flag to the package level DELETE piece function.
• 542 — set to the unique number passed in the Open Ship Create transaction.
• 29 — enter the tracking number of the package to delete.
• 1274 — specify the code for the FedEx Service you plan to use to ship.
Table 4-16 provides instructions for using these fields.
Table 4-16: Delete Piece Before CONFIRM
Action
Field ID
Field Name
Description
Transaction: 020 Global Ship Request
To DELETE a piece from a shipment
Set the 7th position of the Open Ship flag to Y.
For example, NNNNNNYNN sets the flag to the package-level DELETE piece
function.
Use…
Contains a nine-digit flag that specifies the action(s) is to be performed on the Open
Ship shipment.
Field 541
Open Ship Flags
To identify a specific Open Ship shipment
Include the Open Ship index number that you assigned to the shipment when you
created it. You must include this number to ensure that the package is deleted from
the correct shipment.
Use…
The Open Ship index number is a unique number that you specify in the CREATE
Shipment transaction. You then use the number to identify which shipment to
perform the DELETE action against. The Open Ship Index value must be a unique
number per Open Ship shipment per meter.
Field 542
Open Ship Index
To specify tracking number for the piece
Enter the package tracking number to ensure the correct piece gets deleted from the
Open Ship shipment.
Use…
Tracking number of the package or piece in a multiple-piece shipment (MPS).
Required with Field 541 to identify the package to ADD, EDIT or DELETE.
Field 29
Tracking Number
To specify the FedEx shipping service to use for the
package
Enter the code number for the service to use to ship the package. See “FedEx
Services with Open Ship” on page 4-2 for a list of services you can use when
shipping an Open Ship shipment.
Use…
Service type provided by the shipper.
See the description of Field 1274 in Table 4-23 for a list of valid service types for
Open Ship.
v 10.6.1
Field 1274
Service Type
FedEx Ship Manager® Server Developer Guide
4-29
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
DELETE Piece - After CONFIRM
To delete an Open Ship Shipment after you CONFIRM the shipment but before you close it, use the 023 Global Delete Request transaction
and Field 1123 (Master Tracking Number) with a valid Master tracking number.
Table 4-17: To Delete Piece After CONFIRM
Action
Field ID
Field Name
Description
Transaction: 023 Global Delete Request
To identify the package you want to delete
Include the master tracking number assigned to the package in the transaction.
Use…
Master tracking number assigned by FedEx to the package.
This number accompanies all MPS or child packages within the shipment.
Field 1123
Master Tracking Number
DELETE Piece Fields
To delete an entire Open Ship shipment prior to a CONFIRM transaction, you must submit a 020 Global Ship Request transaction that
passes the fields listed inTable 4-18
Table 4-18: Required Fields to DELETE an Open Ship Shipment
Transaction: 020 Global Ship Request - Open Ship MPS
Field
ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I/O
FDXE
FDXG
FDXS
A
I
FDXE*
FDXG
FDXS
Description
Tracking Number
29
Min=12
Max=25
All
REQUIRED*
Tracking number of the package or piece in a multiple-piece shipment
(MPS).
*Required with Field 541 to identify the package to ADD, EDIT or
DELETE in an Open Ship 020/120 Global Ship transaction.
Open Ship Flags
541
4-30
Max = 9
US
INTL
For FDXE:
IPD
*includes IED
C.O.D. IDF
IDD
Surface
For FDXG:
IGD
IGDD
IDD
Surface
Field Level: Package
REQUIRED*
Nine one-byte flags which are set to Y to indicate Open Ship function.
Flag must be either Y or N; you cannot enter all Ns.
To DELETE a package, set the 7th position of the flag to Y.
For example, NNNNNNYNN requests to delete a package from an Open
Ship shipment.
*Required for Open Ship.
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-18: Required Fields to DELETE an Open Ship Shipment (Continued)
Transaction: 020 Global Ship Request - Open Ship MPS
Field
ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
Description
Open Ship Index
542
Max = 9
FDXE*
FDXG
FDXS
US
INTL
For FDXE:
IPD
*includes IED
C.O.D. IDF
IDD
Surface
For FDXG:
IGD
IGDD
IDD
Surface
REQUIRED*
Set to the unique number passed in the CREATE transaction. The value
is a unique number per Open Ship shipment per meter and represents
the Open Ship Index.
*Required for Open Ship.
Note: Field 542 is not required if you are simultaneously performing a
CREATE or ADD transaction.
Examples of simultaneous transactions are: YYNNNNNNN which
performs a shipment level CREATE and Route/Time in Transit
transaction or NYNYNNNNN which performs a package level ADD and
shipment level Route/Time in Transit together in the same transaction.
FDXE
FDXG
FDXS
REQUIRED.
Service type provided by the shipper.
Valid service types for Open Ship are:
FedEx Express U.S.:
01 — FedEx Priority Overnight
03 — FedEx 2Day
05 — FedEx Standard Overnight
06 — FedEx First Overnight
20 — FedEx Express Saver
FedEx International Services (including U.S. export):
01 — FedEx International Priority
03 — FedEx International Economy
70 — FedEx International Priority Freight
121 — FedEx International Ground Distribution (IGD)
Note: However, Field 542 is not used for IPD open shipping. Instead use
Field 1355 (IOR Facility Code) with Field 24 (Ship Date) and Field 1274
(Service Type) to form a unique shipment.
Service Type
1274
Min=2
Max=3
N
I
All
Note: For FedEx SmartPost shipping, reference Field 2417 in Table 7-9
on page 7-45.
DELETE Shipment Transaction
To delete an entire Open Ship shipment prior to a CONFIRM transaction, you must submit a 020 Global Ship Request transaction that
passes the required Field 541 (Open Ship Flags) with position set to 8 and Field 542 (Open Ship Index).
To delete an Open Ship Shipment after you CONFIRM the shipment but before you close it, use the 023 Global Delete Request transaction
and Field 1123 (Master Tracking Number) with a valid Master tracking number.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
4-31
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
The DELETE shipment function is indicated by setting the position 8 flag in Field 541 (Open Ship Flags) to Y — requests FSMS to DELETE
an Open Ship shipment.
Note: When position 8 flag is set to N, no shipment is deleted.
In your transaction statement, this looks like: 541,"NNNNNNNYN".
Both Field 541 (Open Ship Flags) and 542 (Open Ship Index) are required for the Open Ship DELETE shipment transaction using the 020
Global Ship Request transaction.
Table 4-19: DELETE Open Ship Shipment Fields
Action
Field ID
Field Name
Description
Transaction: 020 Global Ship Request
To create an Open Ship shipment
Set the eighth (8) position of the Open Ship flag to Y.
For example, NNNNNNNYN.
Use…
Contains a nine-digit flag that specifies the action(s) is to be performed on the Open
Ship shipment.
Field 541
Open Ship Flags
To distinguish an Open Ship shipment
Assign an Open Ship index number to the shipment and include Field 542 and this
number in the DELETE shipment transaction.
Use…
The Open Ship index number is a unique number that you create and include in the
CREATE Shipment transaction. You then use the number to identify which shipment
to perform an ADD, EDIT or DELETE action against. The Open Ship Index value
must be a unique number per Open Ship shipment per meter.
Field 542
Open Ship Index
DELETE Open Ship Shipment Fields
When you delete an Open Ship shipment prior to a CONFIRM, you must specify the Open Ship index assigned to the shipment when it was
created. FedEx Ship Manager Server identifies which shipment to delete based on the index identifier you supply.
Use a 020 Global Ship Request transaction to pass Field 541 (Open Ship Flags) with position 8 (DELETE shipment) set to Y and Field 542
(Open Ship Index).
If you need to delete a shipment after a CONFIRM, then you must pass Field 29 (Tracking Number) with the master tracking number
returned when the shipment was created.
Table 4-20: Fields for Deleting an Open Ship Shipment
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I/O
Description
Tracking Number
29
4-32
Min=12
Max=25
FDXE
FDXG
FDXS
All
REQUIRED*
Tracking number of the package or piece in a multiple-piece shipment
(MPS).
*Required in the 023 Global Delete transaction to identify the package to
delete.
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-20: Fields for Deleting an Open Ship Shipment (Continued)
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I
FDXE*
FDXG
FDXS
US
INTL
For FDXE:
IPD
*includes IED
C.O.D. IDF
IDD
Surface
For FDXG:
IGD
IGDD
IDD
Surface
Field Level: Shipment
REQUIRED*
Nine one-byte flags which are set to Y to indicate Open Ship function.
Flag must be either Y or N; you cannot enter all Ns.
To DELETE a shipment, set the 8th position of the flag to Y.
For example, NNNNNNNYN requests to delete an Open Ship shipment.
*Required for Open Ship.
N
I
FDXE*
FDXG
FDXS
REQUIRED*
Set to the unique number passed in the CREATE transaction. The value
is a unique number per Open Ship shipment per meter and represents
the Open Ship Index.
*Required for Open Ship.
Note: Field 542 is not required if you are simultaneously performing a
CREATE or ADD transaction.
Examples of simultaneous transactions are: YYNNNNNNN which
performs a shipment level CREATE and Route/Time in Transit
transaction, or NYNYNNNNN which performs a package level ADD and
shipment level Route/Time in Transit together in the same transaction.
Description
Open Ship Flags
541
Max=9
Open Ship Index
542
Max=9
US
INTL
For FDXE:
IPD
*includes IED
C.O.D. IDF
IDD
Surface
For FDXG:
IGD
IGDD
IDD
Surface
Note: However, Field 542 is not used for IPD open shipping. Instead use
Field 1355 (IOR Facility Code) with Field 24 (Ship Date) and Field 1274
(Service Type) to form a unique shipment.
Deleting an Entire Shipment Prior to CONFIRM of Shipment
If you want to delete an entire Open Ship shipment prior to CONFIRM of the shipment, then you must use 020 Global Ship Request
transaction with the Field 541 (Open Ship Flags) DELETE shipment function flagged.
To delete the entire shipment prior to CONFIRM
1.
Create a 020 Global Ship Request transaction.
2.
Set Field 541 (Open Ship Flags) position 8 (DELETE a Shipment) to ‘Y’, NNNNNNNYN.
3.
Pass a value in Field 542 (Open Ship Index) to identify which Open Ship shipment to delete.
4.
Include the master Tracking Number generated in Field 29 during the Open Ship CREATE shipment transaction.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
4-33
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Deleting an MPS Shipment Prior to CONFIRM of Shipment
If you want to delete a multiple-piece shipment (MPS) prior to CONFIRM, then you must use the 023 Global Delete Request transaction and
Field 541 (Open Ship Flags) DELETE shipment function flagged.
To delete the entire MPS shipment only (not any other pieces) prior to CONFIRM
1.
Create a 020 Global Ship Request transaction.
2.
Set Field 541 position 8 (Delete a Shipment) to Y; for example, 541,"NNNNNNNYN".
3.
Pass in the FIRST tracking number generated from the Single Shot IPD/IDF MPS transaction in Field 1123 as if it were the Master
Tracking Number.
Deleting a Single Piece Shipment Prior to CONFIRM of Shipment
If you want to delete a single piece of a shipment prior to CONFIRM, then you must use the 020 Global Ship Request transaction with the
Field 541 (Open Ship Flags) DELETE piece function flagged.
To delete the Single Piece from Open Shipment prior to CONFIRM
1.
Create a 020 Global Ship Request transaction.
2.
Set Field 541 position 7 (Delete a Piece) to Y; for example, 541,"NNNNNNYNN".
3.
Pass in the individual tracking number in Field 29 generated during the Open Ship ADD Piece transaction.
Deleting the Entire Shipment After CONFIRM
If you want to delete the entire Open Ship shipment after CONFIRM before CLOSE, then you must use the 023 Global Delete Request
transaction.
To delete the ENTIRE shipment AFTER CONFIRM BEFORE CLOSE
1.
Create a 023 Global Delete Request transaction.
2.
Pass in the master tracking number in Field 29 generated during the CREATE shipment transaction.
Deleting an Open Ship PAYG Shipment
You can delete any Open Ship PAYG Shipment prior to an Open Ship CONFIRM shipment transaction.
You may delete a piece of a Domestic Express (including Express C.O.D.) and Ground Open Ship PAYG shipment after a CONFIRM
shipment transaction, but you cannot delete the shipment.
Use the 023 Global Delete Request transaction to delete any piece in a shipment after a CONFIRM.
Deleting FedEx Express C.O.D. Shipment
New labels, when requested, are printed for Express C.O.D. shipments after the DELETE pieces transaction completes. The new labels will
print new tracking and sequence numbers.
Express C.O.D. Tracking and Sequence Numbers
New Master and child tracking numbers are assigned for Express C.O.D. shipments and packages when a piece is deleted prior to a
CONFIRM transaction.
If the Master package is deleted, the Master tracking number is reassigned to the next deleted package in sequence in the shipment. All
sequence numbers are decreased by the number of deleted packages.
For example, if the original sequence is 1-3, 2-3, 3-3, and the third piece is deleted prior to a CONFIRM, the revised sequence numbers are
1-2, 2-2.
4-34
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
The 120 Global Ship Reply transaction returns a new Master tracking number in Field 1123, and a package level tracking number in multiple
occurrence in Field 29. Field 116 returns the total number of pieces in the shipment.
Note: For all Open Ship PAYG shipments, you cannot edit a piece or edit a shipment after a CONFIRM transaction.
CONFIRM Piece and Print Label
For FedEx Express, FedEx SmartPost, and FedEx Ground Open Ship U.S. domestic shipments only, you may CONFIRM an individual
package in the shipment and print the label before you CONFIRM the entire shipment. Use a 020 Global Ship Request transaction that
includes the fieldsTable 4-21.
Table 4-21: CONFIRM Piece and Print Label Fields
Action
Field ID
Field Name
Description
Transaction: 020 Global Ship Request
To confirm a piece in an Open Ship shipment
Set the last position of the Open Ship flag to Y.
For example, NNNNNNNNY.
Use…
Contains a nine-digit flag that specifies the action(s) is to be performed
on the Open Ship shipment.
Field 541
Open Ship Flags
To specify tracking number for the piece
Enter the package tracking number to ensure the correct piece gets
confirmed.
Use…
Tracking number of the piece in a multiple-piece shipment (MPS).
Field 29-#
Tracking Number
Note: Consider the following when creating a CONFIRM Piece transaction:
• Do not code Field 542 (Open Ship Index) in an Open Ship CONFIRM transaction; if you do, the entire shipment will be confirmed.
• Enter the required printer information into Fields 187 (Label Format Value/Printer Type Indicator), 537(Thermal Printer Identifier/Label
Buffer File Path) and 1282 (Printer Type Indicator) if you are not using the default configuration printer.
• An Open Ship shipment (non-PAYG) must have at least one package at all times prior to CONFIRM. If a package is confirmed and is the
only package in the shipment, the entire shipment is confirmed and you can not add any more packages to the shipment.
• A CONFIRM piece transaction prior to a CONFIRM shipment is allowed only for FedEx Express. It is not supported for FedEx Express
U.S. C.O.D. packages.
Note: For Open Ship Print-As-You-Go (PAYG) shipments, you must CONFIRM the shipment on the same day as CREATE, otherwise labels
will have the incorrect ship date.
Steps for Package CONFIRM
To print and CONFIRM packages (aka pieces) and maintain the ability to add more packages, perform the following steps:
1.
CREATE the Open Ship shipment and ADD one piece (Package A).
2.
ADD a second piece (Package B).
3.
CONFIRM the first piece (Package A).
4.
ADD the third piece (Package C).
5.
CONFIRM the second piece (Package B).
6.
ADD the fourth piece (Package D).
7.
CONFIRM the third piece (Package C).
v 10.6.1
FedEx Ship Manager® Server Developer Guide
4-35
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
8.
Continue adding and confirming pieces until the shipment is complete.
9.
CONFIRM the shipment.
Note: For Open Ship Print-As-You-Go (PAYG) shipments, you must CONFIRM the shipment on the same day as CREATE, otherwise labels
will have the incorrect ship date.
CONFIRM Package Fields
Table 4-22 lists the minimum fields required to complete a basic 020 Global Ship Request transaction for a FedEx Express U.S. or Freight
shipment.
Table 4-22: Required Fields to CONFIRM a Piece in a Shipment
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\
Output
FedEx Shipping
A
I/O
FDXE*
FDXG
FDXS
Services Valid For
Description
Tracking Number
29-#
Min=12
Max=25
All
REQUIRED*
Tracking number of the package(s) for which you want to print the label.
*Required with Field 541 (Open Ship Flags).
*includes
C.O.D.
Open Ship Flags
541
Max=9
A
I
FDXE*
FDXG
FDXS
US
INTL
For FDXE:
IPD
*includes IED
C.O.D. IDF
IDD
Surface
For FDXG:
IGD
IGDD
IDD
Surface
Field Level: Package
REQUIRED*
Nine one-byte flags which are set to Y to indicate Open Ship function.
Flag must be either Y or N.
To CONFIRM a package (aka piece), set the 9th position of the flag to Y.
For example, NNNNNNNNY requests to confirm a package in an Open
Ship shipment. The shipment must contain more than one package,
otherwise the entire shipment is confirmed.
*Required for Open Ship
CONFIRM Piece and Shipment Transactions
An Open Ship shipment (non-PAYG) must have at least one package at all times prior to CONFIRM. If a package is confirmed, and it is the
only package in the shipment, then the entire shipment is confirmed and you can not add any more packages to the shipment.
To print and CONFIRM packages and maintain the ability to add more packages, perform the following procedure:
1.
CREATE shipment (and ADD Piece #1)
2.
ADD Piece #2
4-36
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
3.
CONFIRM Piece #1
4.
ADD Piece #3
5.
CONFIRM Piece #2
6.
ADD Piece #4
7.
CONFIRM Piece #3
8.
ADD Piece #X
9.
CONFIRM Piece #X
10. CONFIRM Shipment
Note: For Open Ship Print-As-You-Go shipments, you must confirm the shipment.
A “Confirm package” transaction prior to a CONFIRM shipment is allowed only for FedEx Express U.S. and not supported for FedEx
Express U.S. C.O.D. packages.
Note: For Open Ship Print-As-You-Go (PAYG) shipments, you must CONFIRM the shipment on the same day as CREATE, otherwise labels
will have the incorrect ship date.
CONFIRM Open Ship Shipment Fields
After you add all packages to an Open Ship shipment, and the appropriate information has been passed, you may CONFIRM the shipment
by passing in the fields inTable 4-23 in a 020 Global Ship Request transaction.
In addition, include Field 187 (Label Format Value), Field 537 (Thermal Printer ID) or Field 544 (Laser Printer ID), and Field 1282 (Printer
Type Indicator) if you are using a printer other than the configured default printer.
Table 4-23: Required Fields to CONFIRM an Open Ship Shipment
Transaction: 020 Global Ship Request
Field
ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I
Description
Open Ship Flags
541
v 10.6.1
Max = 9
FDXE*
FDXG
FDXS
US
INTL
For FDXE:
IPD
*includes IED
C.O.D.
IDF
IDD
Surface
For FDXG:
IGD
IGDD
IDD
Surface
Field Level: Shipment
REQUIRED*
Nine one-byte flags which are set to Y to indicate Open Ship function.
Flag must be either Y or N; you cannot enter all Ns.
To CONFIRM a shipment, set the 9th position of the flag to Y.
For example, NNNNNNNNY requests to confirm an Open Ship shipment
to which you've added at least one package.
*Required for Open Ship.
FedEx Ship Manager® Server Developer Guide
4-37
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-23: Required Fields to CONFIRM an Open Ship Shipment (Continued)
Transaction: 020 Global Ship Request
Field
ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
Description
Open Ship Index
542
Max = 9
FDXE*
FDXG
FDXS
US
INTL
For FDXE:
IPD
*includes IED
C.O.D.
IDF
IDD
Surface
For FDXG:
IGD
IGDD
IDD
Surface
REQUIRED*
Set to the unique number passed in the CREATE transaction. The value
is a unique number per Open Ship shipment per meter and represents
the Open Ship Index.
*Required for Open Ship.
Note: Field 542 is not required if you are simultaneously performing a
CREATE or ADD transaction.
Examples of simultaneous transactions are: YYNNNNNNN which
performs a shipment level CREATE and Route/Time in Transit
transaction or NYNYNNNNN which performs a package level ADD and
shipment level Route/Time in Transit together in the same transaction.
FDXE
FDXG
Field Level: Shipment
Optional
Service type provided by the shipper.
Valid service types for Open Ship are:
FedEx Express U.S.:
01 — FedEx Priority Overnight
03 — FedEx 2Day
05 — FedEx Standard Overnight
06 — FedEx First Overnight
20 — FedEx Express Saver
FedEx International Services (including U.S. export):
01 — FedEx International Priority
03 — FedEx International Economy
17 — FedEx International Economy DirectDistribution Service
18 — FedEx International Priority DirectDistribution
70 — FedEx International Priority Freight
84 — FedEx International Priority Direct Distribution Freight
121 — FedEx International Ground Distribution (IGD)
Note: However, Field 542 is not used for IPD open shipping. Instead use
Field 1355 (IOR Facility Code) with Field 24 (Ship Date) and Field 1274
(Service Type) to form a unique shipment.
Service Type
1274
Min=2
Max=3
N
I
All
Note: For FedEx SmartPost shipping, reference Field 2417 in Table 7-9
on page 7-49.
4-38
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Confirming Open Ship and Printing Labels
To confirm an Open Ship PAYG shipment, use the 020 Global Ship Request transaction with the Field 541 position 9 set to Y
(NNNNNNNNY). This action sets the flag for the shipment level “Confirm Shipment” function.
If you selected to print labels as you added packages, all labels for pieces in the shipment should already be printed; no additional piece
labels are printed.
If you selected to print labels after adding all packages, then a label for each piece is returned and prints as a result of the CONFIRM
transaction.
For U.S. domestic shipments only, you may CONFIRM an individual package of an Open Ship shipment and print the label before you
confirm the whole shipment by sending a CONFIRM Piece transaction. Use a 020 Global Ship Request transaction that includes Field 541
(Open Ship Flags) and Field 29 (Tracking Number).
For FedEx Express U.S. C.O.D. shipments, a C.O.D. Return Label is printed with the last package in the shipment.
Note: For Open Ship Print-As-You-Go (PAYG) shipments, you must CONFIRM the shipment on the same day as CREATE, otherwise labels
will have the incorrect ship date.
Open Ship Print Options
Open Ship has two print label options:
• Print-At-The-End (PATE) — print all labels at the end after the shipment is confirmed.
• Print-As-You-Go (PAYG) — print labels for each piece as you need them without waiting until the shipment is confirmed.
Both options are explained further below. For information about FSMS labels, see Chapter 3: FedEx Ship Manager Server Label and Form
Transactions.
Open Ship Print-At-The-End
You can choose to print labels for packages in your Open Ship shipment at the end, when you CONFIRM the shipment.
For U.S. Domestic shipments only, you may CONFIRM an individual package of an Open Ship shipment and print the label before you
confirm the whole shipment by sending a CONFIRM Piece transaction. Use a 020 Global Ship Request transaction that includes the
Field 541 (Open Ship Flags) and Field 29 (Tracking Number).
Note: Consider the following when creating a CONFIRM Piece transaction:
• Do not code Field 542 in an Open Ship CONFIRM transaction; if you do, the entire shipment will be confirmed.
• Enter the required printer information into Fields 187 (Label Format Value/Printer Type Indicator), 537 (Thermal Printer Identifier/Label
Buffer File Path), and 1282 (Printer Type Indicator) if you are not using the default configuration printer.
Open Ship Print-As-You-Go
Open Ship Print-As-You-Go (PAYG) shipping gives FedEx customers the ability to print labels as they CREATE, ADD and EDIT shipment
pieces rather than waiting until they CONFIRM the shipment.
Open Ship PAYG shipping is available for the following FedEx services:
• FedEx Express U.S. domestic, including Collect on Delivery (C.O.D.)
• FedEx Ground
• FedEx SmartPost
To print labels for packages as you prepare an Open Ship shipment, include the fields in Table 4-24 in a 020 Global Ship Request
transaction.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
4-39
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Note that the first three fields in Table 4-25 (Fields 27-#, 53, and 116) are required for FedEx Express and FedEx SmartPost (PAYG-NA),
including FedEx Express U.S. domestic C.O.D. (PAYG-A). The last three (Fields 541, 542, and 2600) are required for FedEx Express U.S.
domestic C.O.D. only.
Note: For Open Ship Print-As-You-Go (PAYG) shipments, you must CONFIRM the shipment on the same day as CREATE, otherwise labels
will have the incorrect ship date.
Note: For more information about FedEx SmartPost Print-As-You-Go, See Chapter 7: Coding Transactions for FedEx SmartPost in this
document (Developer Guide).
Print-As-You-Go Package Association and Print Modes
Table 4-24 describes the Print-As-You-Go package associations and print modes for FedEx services. There are two types of package
association when using Print-As-You-Go: associated and non-associated.
• Associated: Each package is numbered in series and also lists the total number of packages in the shipment. For example 1 of 5, 2 of 5,
3 of 5, 4 of 5 and 5 of 5.
• Non-associated: Each package is numbered in series with no further information. Package 1, 2, 3, 4 and 5. You cannot tell from any one
package in the shipment how many total pieces are included.
Table 4-24: Print-As-You-Go Package Association
FedEx Service
Data Entry Method
Package Association
Print Mode
FedEx Express
U.S. domestic
Open Ship
MPS
Neither association or sequence numbers
Print-As-You-Go Non-Associated (PAYGNA) mode. Labels are printed for all pieces
when they are added or edited.
FedEx Express
C.O.D. (U.S.)
Open Ship
MPS
Sequence numbers assigned to packages;
each package added increments the
sequence number. The first piece created is
the Master piece for the shipment. The
piece tracking number of the CREATE piece
becomes the Master tracking number for
the shipment.
Print-As-You-Go Associated (PAYG-A)
mode. Labels are printed for all pieces when
they are added or edited. The C.O.D.
Return Label is printed with the last piece in
the shipment.
FedEx Ground
U.S. domestic
Open Ship
MPS
Neither association or sequence numbers
Print-As-You-Go Non-Associated (PAYGNA) mode. Labels are printed for all pieces
when they are added or edited.
FedEx SmartPost
Open Ship
MPS
Neither association or sequence numbers
Print-As-You-Go Non-Associated (PAYGNA) mode. Labels are printed for all pieces
when they are added or edited.
4-40
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Open Ship Print-As-You-Go Fields
Table 4-25: Open Ship Print-As-You-Go (PAYG) Fields
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I
Description
C.O.D. Flag
27-#
Max=1
FDXE*
FDXG
US
Field Level: Shipment level for FedEx Express; Package level for FedEx
Ground
REQUIRED*
When set to Y, indicates that a package or shipment is being shipped
Collect on Delivery (C.O.D.), and “C.O.D.” prints in the box beside the
recipient name on the bill of lading. Multiple-occurrence field.
*Required for C.O.D.
Valid values are:
Y — Package is C.O.D. at the shipment level for FedEx Express and at
the package level for FedEx Ground.
N — Package is NOT sent C.O.D. (default)
S — Package is sent C.O.D. at the Shipment level for FedEx Ground.
US
Field Level: Shipment level for FedEx Express; Package level for FedEx
Ground.
REQUIRED.
Amount of payment that must be collected upon delivery of the Collect on
Delivery (C.O.D.) package.
Maximum of $25,000 for FedEx Ground if guaranteed funds and
maximum of $750 if cash.
Multiple-occurrence field.
US
Field Level: Shipment
REQUIRED*
Total number of packages in a shipment, including the master package.
*Required for a multiple-piece shipment (MPS).
For all MPS shipments, the software performs the package count
summation based on the number of occurrences of Field 1670-#
(Package Weight/Shipment Weight) and overrides any input value.
*includes
C.O.D.
C.O.D. Collect Amount
53
Max=10.2 N
I
FDXE*
FDXG
FDXS
*includes
C.O.D.
Package Total
116
Max=3
N
I
FDXE*
FDXG
FDXS
*includes
C.O.D.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
4-41
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-25: Open Ship Print-As-You-Go (PAYG) Fields (Continued)
Transaction: 020 Global Ship Request - Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I
Description
Open Ship Flags
541
Max=9
FDXE*
FDXG
FDXS
US
REQUIRED*
Identifies transaction functions using nine one-byte flags which are set to
Y to indicate shipment level or package level flags.
To enable Print-As-You-Go mode, specify Y in one of the following
positions:
1 — CREATE an Open Shipment
4 — ADD a piece/package
5 — EDIT a piece/package
6 — EDIT/ADD data to the entire shipment
*Required for Open Ship.
US
REQUIRED*
Set to the unique number passed in the CREATE transaction. The value
is a unique number per Open Ship shipment per meter and represents
the Open Ship Index.
*Required for Open Ship.
Note: Field 542 is not required if you are simultaneously performing a
CREATE or ADD transaction.
Examples of simultaneous transactions are: YYNNNNNNN which
performs a shipment level CREATE and Route/Time in Transit
transaction, or NYNYNNNNN which performs a package level ADD and
shipment level Route/Time in Transit together in the same transaction.
*includes
C.O.D.
Open Ship Index
542
Max=9
N
I
FDXE*
FDXG
FDXS
*includes
C.O.D.
Note: However, Field 542 is not used for IPD open shipping. Instead use
Field 1355 (IOR Facility Code) with Field 24 (Ship Date) and Field 1274
(Service Type) to form a unique shipment.
Package Association and Print Mode
2600
Max=2
N
I
FDXE*
FDXG
FDXS
*includes
C.O.D.
4-42
US
Optional
Identifies the package association and Print-As-You-Go (PAYG) option
for a FedEx Express C.O.D. U.S. shipment. Requires value set to:
03 — Package association and print labels with each CREATE/ADD
piece transaction for intra-U.S. multiple-piece shipments (MPS) using
Print-As-You-Go (PAYG-A) mode.
For Open Ship Print-As-You-Go (PAYG) shipments, you must CONFIRM
the shipment on the same date as CREATE, otherwise labels will have
the incorrect ship date.
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Open Ship PAYG Transaction Summary
Table 4-26 summarizes the transaction fields and associated print modes for the Open Ship Print-As-You-Go function in FSMS.
Note: For all Open Ship PAYG shipments, you cannot EDIT a piece or EDIT a shipment after a CONFIRM transaction.
Note: For Open Ship Print-As-You-Go (PAYG) shipments, you must CONFIRM the shipment on the same day as CREATE, otherwise labels
will have the incorrect ship date.
Table 4-26: Open Ship Print-As-You-Go Transaction Summary
FedEx Express U.S., FedEx Ground U.S.
FedEx SmartPost
Non-associated
FedEx Express U.S.,FedEx Ground U.S.
Collect on Delivery (C.O.D.)
Associated
CREATE Shipment
Transaction: 020 Global Ship Request
Fields:
541 — set to CREATE flag
2600 — set to value 4
Labels printed.
Rate returned when requested by 541 set with
RATE flag.
Transaction: 020 Global Ship Request
Fields:
541 — set to CREATE flag
2600 — set to value 3
116 — returns total pieces
Label printed with Master tracking and package
sequence numbers.
Rate returned when requested by 541 set with
RATE flag.
ADD Piece
Transaction: 020 Global Ship Request
Fields:
541 — set to ADD flag
Labels printed.
Rate returned when requested by 541 set with
RATE flag.
Transaction: 020 Global Ship Request
Fields:
541 — set to ADD flag
Label printed with Master tracking and package
sequence numbers.
Rate returned when requested by 541 set with
RATE flag.
EDIT Piece before CONFIRM
Transaction: 020 Global Ship Request
Fields:
541 — set to EDIT Piece flag
New labels printed for all edited pieces. Tracking
numbers are not changed.
Rate returned when requested by 541 set with
RATE flag.
Transaction: 020 Global Ship Request
Fields:
541 — set to EDIT Piece flag
New label printed with Master tracking (reused)
and package sequence numbers (reused).
Rate returned when requested by 541 set with
RATE flag.
EDIT Shipment before CONFIRM
Transaction: 020 Global Ship Request
Fields:
541 — set to EDIT Shipment flag
New labels printed for all pieces. Tracking
numbers are preserved.
Rate returned when requested by 541 set with
RATE flag.
Transaction: 020 Global Ship Request
Fields:
541 — set to Edit Shipment flag
New labels printed for all pieces with a new
Master tracking number.
Package sequence numbers are reused and
reflect the new tracking number.
Rate returned when requested by 541 set with
RATE flag.
Open Ship Function
v 10.6.1
FedEx Ship Manager® Server Developer Guide
4-43
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Table 4-26: Open Ship Print-As-You-Go Transaction Summary (Continued)
Open Ship Function
DELETE Piece before CONFIRM
FedEx Express U.S., FedEx Ground U.S.
FedEx SmartPost
Non-associated
FedEx Express U.S.,FedEx Ground U.S.
Collect on Delivery (C.O.D.)
Associated
Transaction: 020 Global Ship Request
Fields:
541 — set to Delete Piece flag
29 — piece tracking number.
Transaction: 020 Global Ship Request
Fields:
541 — set to DELETE Piece flag
New labels printed for all pieces with a new
Master tracking number and new sequence
numbers.
Rate returned when requested by 541 set with
RATE flag.
DELETE Shipment before CONFIRM Transaction: 020 Global Ship Request
Fields:
541 — set to DELETE Shipment flag
Transaction: 020 Global Ship Request
Fields:
541 — set to DELETE Shipment flag
CONFIRM Shipment
Transaction: 020 Global Ship Request
Fields:
541 — set to CONFIRM Shipment flag
No additional shipping labels printed.
Rate returned with 120 Reply for CONFIRM
Shipment.
Transaction: 020 Global Ship Request
Fields:
541 — set to CONFIRM Shipment flag
No additional shipping labels printed.
C.O.D. Return Label is printed with the last
package in the shipment.
Rate returned with 120 Reply for CONFIRM
Shipment.
CONFIRM Piece
Transaction: 020 Global Ship Request
Fields:
541 — set to CONFIRM Package flag
29 — valid tracking number
Labels not reprinted.
Not supported.
DELETE a Piece or Shipment after
CONFIRM
Transaction: 023 Global Delete Request
You may delete any piece in the shipment.
Transaction: 023 Global Delete Request
Deleting one piece deletes the entire shipment.
You can re-add the shipment as a separate
transaction.
Note: For Open Ship Print-As-You-Go (PAYG) shipments, you must CONFIRM the shipment on the same day as CREATE, otherwise labels
will have the incorrect ship date.
FedEx Express U.S. Open Ship Transaction Samples
The following Open Ship code examples are for FedEx Express shipments with origin/destination addresses within the United States.
Example A shows how to create a FedEx Express shipment and add five packages. The example transactions also show how to request
rate information for each package as it is added.
Example B shows how to create a FedEx Express Freight shipment and add five pallets before confirming the shipment.
4-44
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Example A - FedEx Express Open Ship shipment of five packages to Indianapolis
0,"020"1,"Create and Add First package, Residential Express"11,"Sam's Publishing"12,"Recipient
Name"13,"201 West 103rd St"15,"Indianapolis"16,"IN"17,"46290"18,"1234567890"23,"1"25,"Package
CR001"50,"US"440,"Y"498,""541,"YNYNNNNNN"542,"EAD200"1273,"01"1274,"01"1670,"450"3062,"2"99,"
"
0,"020"1,"Add/Rate Second Package"25,"Package CR002"50,"US"498,""541,"NNYYNNNNN"542,"EAD200"
1273,"01" 1274,"01"1670,"550"3062,"2"99,""
0,"020"1,"Add/Rate Third Package"25,"Package CR003"50,"US"498,""541,"NNYYNNNNN"542,"EAD200"
1273,"01" 1274,"01"1670,"230"3062,"2"99,""
0,"020"1,"Add/Rate Fourth Package"25,"Package CR004"50,"US"498,""541,"NNYYNNNNN"542,"EAD200"
1273,"01" 1274,"01"1670,"400"3062,"2"99,""
0,"020"1,"Add/Rate Fifth Package"25,"Package CR005"50,"US"498,""541,"NNYYNNNNN"542,"EAD200"
1273,"01" 1274,"01"1670,"450"3062,"2"99,""
0,"020"1,"Confirm Open Shipment"50,"US"187,"199"498,""537,""541,"NNNNNNNNY"542,"EAD200" 1274,
"01"1660,"Y"99,""
Example B - FedEx Express Freight Open Ship shipment of five pallets to Indianapolis
0,"020"1,"Create and Add First Express Freight Pallet"11,"Sam's Publishing"12,"Recipient
Name"13,"201 West 103rd St"15,"Indianapolis"16,"IN"17,"46290"18,"1234567890"23,"1"25,"Package
CR001"50,"US"57,"18"58,"36"59,"40"440,"Y"498,""541,"YNYNNNNNN"542,"EAD200"1273,"01"1274,"80"1
670,"45000"3062,"2"99,""
0,"020"1,"Add/Rate Second Pallet"25,"Package CR002"50,"US"57,"18"58,"24"59,"36"498,""541,
"NNYYNNNNN" 542,"EAD200"1273,"01"1274,"01"1670,"20000"3062,"2"99,""
0,"020"1,"Add/Rate Third Pallet"25,"Package CR003"50,"US"57,"18"58,"24"59,"36"498,""541,
"NNYYNNNNN" 542,"EAD200"1273,"01"1274,"01"1670,"20000"3062,"2"99,""
0,"020"1,"Add/Rate Fourth Pallet"25,"Package CR004"50,"US"57,"18"58,"24"59,"36"498,""541,
"NNYYNNNNN" 542,"EAD200"1273,"01"1274,"01"1670,"20000"3062,"2"99,""
0,"020"1,"Add/Rate Fifth Pallet"25,"Package CR005"50,"US"57,"18"58,"24"59,"36"498,""541,
"NNYYNNNNN" 542,"EAD200"1273,"01"1274,"01"1670,"20000"3062,"2"99,""
0,"020"1,"Confirm Open Shipment"50,"US"187,"199"498,""537,""541,"NNNNNNNNY" 542,"EAD200"
1274,"80"1660,"Y"99,""
FedEx Express U.S. Export Open Ship Transactions
The following Open Ship code example shows how to code FedEx Express transactions for destinations outside of the United States.
Example A is a FedEx Express Open Ship shipment of five packages destined for Brussels, Belgium. The transaction adds a new
commodity to the shipment and edits the information for that commodity.
Example B is a FedEx Express Freight Open Ship shipment of five pallets shipped to the same address in Belgium. The transaction
requests that a FedEx commercial invoice be printed for the shipment.
Example C shows the transaction strings required for a FedEx Express five-package shipment to Japan and does not print a FedEx
commercial invoice.
Example A - FedEx Express Open Ship shipment with five packages containing multiple
commodities shipped from U.S. to Brussels, Belgium with a FedEx commercial invoice printed
0,"020"1,"IP Open Ship Create, Multiple Commodities, FedEx CI"11,"Belgian Electronics"12,
"Louis Desjardin"13,"243 Rue Elysees"15,"Brussels"17,"1009"18,"9012631234"23,"1"25,"Open
Shipment to BE"26,"100"50,"BE"68,"USD"72,"1"74,"BE"75,"KGS"77,"25"77-2,"25"77-3,"15"77-4,"45"
77-5,"10"79,"Capacitors"79-2,"Resistors"79-3,"Diodes"79-4,"Integrated Circuits"79-5,"Drive
Motors"80,"US"80-2,"US"80-3,"US"80-4,"US"80-5,"US"81,"8518290000"81-2,"8524400000"81-3,
"8518300000"81-4,"8519920000"81-5,"8518290000"82,"1000"82-2,"1000"82-3,"10000"82-4,"50"82-5,
"25"113,"Y"183,"9011234567"414,"EA"414-2,"EA"414-3,"EA"414-4,"EA"414-5,"EA"498,""541,
"YNNNNNNNN"542,"400"1030,"250000000"1030-2,"350000000"1030-3,"325000000"1030-4,"125000000"
v 10.6.1
FedEx Ship Manager® Server Developer Guide
4-45
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
1030-5,"50000000"1090,"USD"1139,"123456789"1273,"01"1274,"01"1349,"S"1350,"1029384756973"
1358,"NO EEI 30.37(a)"1670,"1300"99,""
0,"020"1,"Add Package Two"50,"BE"74,"BE"498,""541,"NNNYNNNNN"542,"400"1273,"01"1274,"01"
1670,"1550"99,""
0,"020"1,"Add Package Three"50,"BE"74,"BE"498,""541,"NNNYNNNNN"542,"400"1273,"01"1274,"01"
1670,"1500"99,""
0,"020"1,"Add Package Four"50,"BE"74,"BE"498,""541,"NNNYNNNNN"542,"400"1273,"01"1274,"01"
1670,"1000"99,""
0,"020"1,"Add Package Five"50,"BE"74,"BE"498,""541,"NNNYNNNNN"542,"400"1273,"01"1274,"01"
1670,"1250"99,""
0,"020"1,"Add Commodity to Shipment"29,"987654321234"50,"BE"77,""79,"Zener Diode"80,"US"
81,"8518300000"82,"75"414,"EA"541,"NNNNNNNNN"542,"400"1030,"25000000"1274,"01"1677,"1"99,""
0,"020"1,"Edit Commodity #1"50,"BE"77,""79,"Zener Diode"80,""81,""82,"100"414,"EA"
541,"NNNNNNNNN"542,"400"1030,"250000"1274,"01"1677,"1"1678,"FDX0"99,""
0,"020"1,"Confirm Open Shipment"50,"BE"187,"199"537,"C:\FedEx\Label Buffers"541,"NNNNNNNNY"
542,"400"1273,"01"1274,"01"1282,"F"99,""
Example B - FedEx Express Freight Open Ship shipment of five pallets shipped from U.S. to
Brussels, Belgium with a FedEx commercial invoice printed
0,"020"1,"IP Open Ship Create Express Freight, Multiple Commodities, FedEx CI"11,"Belgian
Electronics"12,"Louis Desjardin"13,"243 Rue Elysees"15,"Brussels"17,"1009"18,"9012631234"23,
"1"25,"Open Shipment to BE"26,"100"50,"BE"57,"15"58,"20"59,"35"68,"USD"72,"1"74,"BE"75,"KGS"
77,"25"77-2,"25"77-3,"15"77-4,"45"77-5,"10"79,"Capacitors"79-2,"Resistors"79-3,"Diodes"79-4,
"Integrated Circuits"79-5,"Drive Motors"80,"US"80-2,"US"80-3,"US"80-4,"US"80-5,"US"81,
"8518290000"81-2,"8524400000"81-3,"8518300000"81-4,"8519920000"81-5,"8518290000"82,"1000"822,"1000"82-3,"10000"82-4,"50"82-5,"25"113,"Y"183,"9011234567"414,"EA"414-2,"EA"414-3,"EA"4144,"EA"414-5,"EA"498,""541,"YNNNNNNNN"542,"400"1030,"250000000"1030-2,"350000000"1030-3,
"325000000"1030-4,"125000000"1030-5,"50000000"1090,"USD"1139,"123456789"1273,"01"1274,"86"
1349,"S"1350,"1029384756973"1358,"NO EEI 30.37(a)"1670,"10000"99,""
0,"020"1,"Add Pallet Two"50,"BE"57,"45"58,"60"59,"40"74,"BE"498,""541,"NNNYNNNNN"542,"400"
1273,"01"1274,"01"1670,"1550"99,""
0,"020"1,"Add Pallet Three"50,"BE"57,"45"58,"60"59,"40"74,"BE"498,""541,"NNNYNNNNN"542,"400"
1273,"01"1274,"01"1670,"1550"99,""
0,"020"1,"Add Pallet Four"50,"BE"57,"45"58,"60"59,"40"74,"BE"498,""541,"NNNYNNNNN"542,"400"
1273,"01"1274,"01"1670,"1550"99,""
0,"020"1,"Add Pallet Five"50,"BE"57,"45"58,"60"59,"40"74,"BE"498,""541,"NNNYNNNNN"542,"400"
1273,"01"1274,"01"1670,"1550"99,""
0,"020"1,"Confirm Open Shipment"50,"BE"187,"PNG"537,"C:\PNG"541,"NNNNNNNNY"542,"400"1273,"01"
1274,"01"1282,"F"99,""
Example C - FedEx Express Open Ship shipment of five packages shipped from U.S. to Japan with
no commercial invoice
0,"020"1,"IP Open Ship Create, No FedEx CI"11,"Japan Electronics Corp"12,"Hiro Kanagawa"13,"
1-18-9 Nihombashi, Chuo-ku"15,"Tokyo"17,"1200015"18,"9012631234"23,"1"25,"Open Shipment to
JP" 26,"100"50,"JP"68,"USD"72,"1"74,"JP"75,"KGS"79,"Electronic Components"80,"US"113,"N"119,
"235000"183,"9011234567"187,"288"498,"98765"537,"\\FedEx Ship Manager Server\Z4M"541,""542,""
1090,"USD"1139,"123456789"1273,"01"1274,"01"1282,"T"1349,"S"1350,"1029384756973"1670,"1300"99
,""
0,"020"1,"Add Package Two"50,"JP"74,"JP"498,""541,"NNNYNNNNN"542,"200"1273,"01"1274,"01"
1670,"1250"99,""
0,"020"1,"Add Package Three"50,"JP"74,"JP"498,""541,"NNNYNNNNN"542,"200"1273,"01"1274,"01"
1670,"230"99,""
0,"020"1,"Add Package Four"50,"JP"74,"JP"498,""541,"NNNYNNNNN"542,"200"1273,"01"1274,"01"
1670,"150"99,""
4-46
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
0,"020"1,"Add Package Five"50,"JP"74,"JP"498,""541,"NNNYNNNNN"542,"200"1273,"01"1274,"01"
1670,"150"99,""
0,"020"1,"Confirm Open Shipment"50,"JP"187,"199"537,"C:\FedEx\Label Buffers"541,"NNNNNNNNY"
542,"200"1273,"01"1274,"01"1282,"F"99,""
FedEx Ground Open Ship Transaction Samples
The following Open Ship code examples show how to code FedEx Ground shipping transactions.
Example A shows the basic shipping transaction sequence for creating a shipment and adding five packages. The shipment is identified by
the Open Ship Index "200" in Field 542 which is passed with the CREATE flag.
Example B ships multiple commodities in one shipment to an address in Canada. The transactions include adding and editing the
commodities in the shipment.
Example C ships five packages to a commercial recipient in the United States and requests the rate for each package as it is added to the
shipment.
Example A - FedEx Ground hazardous materials shipment to U.S. address
CREATE a FedEx Ground Open Ship shipment using 020 Global Ship Request transaction and ADD the first package.
0,"020"1,"Create and Add First Package, HazMat"11,"EGC Inc."12,"Recipient Name"13,"201 West
103rd St"15,"Indianapolis"16,"IN"17,"46290"18,"1234567890"23,"1"25,"Package CR001"26,"100"
50,"US"451,"1234"466,"10"471,"GAL"484,"9012631234"489,"III"492,"3"498,""541,"YNYNNNNNN"542,"2
00"1273,"01"1274,"92"1331,"Y"1493,"Y"1670,"2300"1903,"Toluene"3001,"Shipment PO10001"3057,
"Package IN001"3062,"2"3072,"Flammable Liquid"99,""
ADD second package.
0,"020"1,"Add Second Package"25,"Package CR002"50,"US"451,"2078"466,"10"471,"GAL"484,
"9012631234"489,"II"492,"6.1"498,""541,"NNYYNNNNN"542,"200"1273,"01"1274,"92"1331,"Y"1493,
"Y"1670,"2700"1903,"Toluene diisocyanate"3057,"Package IN002"3062,"2"3072,"Poison"99,""
ADD third package.
0,"020"1,"Add Third Package"25,"Package CR003"50,"US"451,"1708"466,"10"471,"GAL"484,
"9012631234"489,"II"492,"6.1"498,""541,"NNYYNNNNN"542,"200"1273,"01"1274,"92"1331,"Y"1493,
"Y"1670,"3750"1903,"Toludines"3057,"Package IN003"3062,"2"3072,"Poison"99,""
ADD fourth package.
0,"020"1,"Add Fourth Package"25,"Package CR004"50,"US"451,"1709"466,"10"471,"GAL"484,
"9012631234"489,"III"492,"6.1"498,""541,"NNYYNNNNN"542,"200"1273,"01"1274,"92"1331,"Y"1493,"Y
"1670,"4300"1903,"Toluylenediamine"3057,"Package IN004"3062,"2"3072,"Keep Away From Food"
99,""
ADD fifth package.
0,"020"1,"Add Fifth Package"25,"Package CR005"50,"US"451,"2586"466,"10"471,"GAL"484,
"9012631234"489,"II"492,"8"498,""541,"NNYYNNNNN"542,"200"1273,"01"1274,"92"1331,"Y"1493,
"Y"1670,"2100"1903,"Alkyl sulfonic acid"3057,"Package IN005"3062,"2"3072,"Corrosive"99,""
CONFIRM shipment.
0,"020"1,"Confirm Open Shipment"50,"US"187,"199"498,""537,""541,"NNNNNNNNY"542,"200"
1274,"92"1660,"Y"99,""
v 10.6.1
FedEx Ship Manager® Server Developer Guide
4-47
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
Example B - FedEx Ground shipment to Canada address
CREATE a FedEx Ground open shipment and ADD first package.
0,"020"1,"Ground Open Ship Create, Multiple Commodities, FedEx CI"11,"Canadian Electronics"
12,"Louis Desjardin"13,"243 Rue Elysees"15,"Calgary"16,"AB"17,"T2A6P1"18,"9012631234"23,"1"
25,"Carton 1"26,"100"38,"Electrical Components Division"50,"CA"72,"1"74,"CA"75,"KGS"77,"25"
77-2,"25"77-3,"15"77-4,"45"77-5,"10"79,"Capacitors"79-2,"Resistors"79-3,"Diodes"79-4,
"Integrated Circuits"79-5,"Drive Motors"80,"US"80-2,"US"80-3,"US"80-4,"US"80-5,"US"81,
"8518290000"81-2,"8524400000"81-3,"8518300000"81-4,"8519920000"81-5,"8518290000"82,"1000"
82-2,"1000"82-3,"10000"82-4,"50"82-5,"25"113,"Y"183,"9011234567"414,"EA"414-2,"EA"414-3,"EA"
414-4,"EA"414-5,"EA"498,""541,"YNNNNNNNN"542,"400"1030,"250000000"1030-2,"350000000"10303,"325000000"1030-4,"125000000"1030-5,"50000000"1090,"USD"1139,"123456789"1273,"01"1274,"92"
1349,"S"1350,"1029384756973"1358,"NO EEI 30.37(a)"1670,"1300"3062,"2"99,""
ADD second package.
0,"020"1,"Add Package Two"25,"Carton 2"50,"CA"74,"CA"498,""541,"NNNYNNNNN"542,"400"1273,"01"
1274,"92"1670,"1550"3062,"2"99,""
ADD third package.
0,"020"1,"Add Package Three"25,"Carton 3"50,"CA"74,"CA"498,""541,"NNNYNNNNN"542,"400"
1273,"01"1274,"92"1670,"1550"3062,"2"99,""
ADD fourth package.
0,"020"1,"Add Package Four"25,"Carton 4"50,"CA"74,"CA"498,""541,"NNNYNNNNN"542,"400"1273,"01"
1274,"92"1670,"1550"3062,"2"99,""
ADD fifth package.
0,"020"1,"Add Package Five"25,"Carton 5"50,"CA"74,"CA"498,""541,"NNNYNNNNN"542,"400"1273,"01"
1274,"92"1670,"1550"3062,"2"99,""
Add commodity to shipment.
0,"020"1,"Add Commodity to Shipment"29,"123456789876"50,"CA"77,""79,"Zener Diode"80,"US"81,"
8518300000"82,"75"414,"EA"541,"NNNNNNNNN"542,"400"1030,"25000000"1677,"1"99,""
Edit commodity.
0,"020"1,"Edit Commodity #1"50,"CA"77,""79,"Zener Diode"80,""81,""82,"100"414,"EA"541,
"NNNNNNNNN"542,"400"1030,"250000"1677,"1"1678,"FDX0"99,""
CONFIRM shipment.
0,"020"1,"Confirm Open Shipment"50,"CA"187,"199"537,"C:\FedEx\Label Buffers"541,"NNNNNNNNY"
542,"400"1273,"01"1274,"92"1282,"F"3062,"2"99,""
Example C - FedEx Ground shipment to U.S. commercial address
CREATE FedEx Ground open U.S. shipment and ADD first package.
0,"020"1,"Ground 5 Package Open Shipment: Create and Add First Package"11,"Sam's Publishing"
12,"Recipient Name"13,"201 West 103rd St"15,"Indianapolis"16,"IN"17,"46290"18,"1234567890"
1670,"35"23,"1"25,"Package CR001"50,"US"440,"Y"498,""541,"YNYNNNNNN"542,"200"1273,"01"
1274,"92"3001,"Shipment PO10001"3057,"Package IN001"3062,"2"99,""
4-48
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
ADD and RATE second package.
0,"020"1,"Add/Rate Second Package"1670,"20"25,"Package CR002"50,"US"498,""541,"NNYYNNNNN"
542,"200"1273,"01"1274,"92"3057,"Package IN002"3062,"2"99,""
ADD and RATE third package.
0,"020"1,"Add/Rate Third Package"1670,"15"25,"Package CR003"50,"US"498,""541,"NNYYNNNNN"
542,"200"1273,"01"1274,"92"3057,"Package IN003"3062,"2"99,""
ADD and RATE fourth package.
0,"020"1,"Add/Rate Fourth Package"1670,"25"25,"Package CR004"50,"US"498,""541,"NNYYNNNNN"
542,"200"1273,"01"1274,"92"3057,"Package IN004"3062,"2"99,""
ADD and RATE fifth package.
0,"020"1,"Add/Rate Fifth Package"1670,"10"25,"Package CR004"50,"US"498,""541,"NNYYNNNNN"
542,"200"1273,"01"1274,"92"3057,"Package IN004"3062,"2"99,""
CONFIRM shipment.
0,"020"1,"Confirm Open
Shipment"1670,"23"50,"US"187,"199"498,""537,"\\printserver\eltronlp"541,"NNNNNNNNY"542,"200"1
274,"92"1282,"T"99,""
FedEx SmartPost Open Ship Transaction Samples
The following code examples are specific to shipping a FedEx SmartPost shipment using the Open Ship shipping method.
ADD Standard Mail package without delivery confirmation and with address service requested
0,"020"1,"STANDARD MAIL SHIPMENT"10,""11,"RECIP COMPANY"12,"ROGER RECIPIENT"13,"123 Main
Street"14,"Suite
200"15,"Portland"16,"ME"17,"04101"18,"8005551212"20,""23,"1"24,""25,"STANDARD MAIL
SHIPMENT"26,"100"50,"US"75,"lbs"117,"US"187,"PNG"498,""541,"NNNYNNNNN"542,"556"1670,"75"2416,
"02"2417,"1"99,""
ADD a Bound Printed Matter package with returns service requested
0,"020"1,"BOUND PRINTED MATTER SHIPMENT"10,""11,"RECIP COMPANY"12,"ROGER RECIPIENT"13,"123
Main Street"
14,"Suite 200"15,"Portland"16,"ME"17,"04101"18,"8005551212" 20,""23,"1"24,""25,"BOUND PRINTED
MATTER SHIPMENT"
26,"100"50,"US"75,"lbs"117,"US"187,"PNG" 498,""541,"NNNYNNNNN"542,"556"1670,"850"2416,"04"
2417,"3"99,""
v 10.6.1
FedEx Ship Manager® Server Developer Guide
4-49
Chapter 4: FedEx Ship Manager Server Open Ship Transactions
THIS PAGE INTENTIONALLY LEFT BLANK.
4-50
FedEx Ship Manager® Server Developer Guide
v 10.6.1
CHAPTER 5: CODING TRANSACTIONS FOR FEDEX
EXPRESS U.S. SERVICE
FedEx Express® U.S. domestic service refers to those FedEx Express package and freight services available to the 50 United States.
This chapter describes how to code FedEx Express U.S. package and freight shipping transactions for FedEx Ship Manager® Server
(FSMS) using the 020 Global Ship Request/Reply Transaction. These transactions must be formatted according to rules specified in the
transaction field tables in this guide and in the FedEx Ship Manager® Server Transaction Coding Reference Guide.
See the FedEx Ship Manager® Server Services and Shipping Guide for information about FedEx Express U.S. service features and details
before you begin to code.
This chapter includes the following sections:
• About FedEx Express U.S. and FedEx Express U.S. Freight
• Transaction Rules and Restrictions for FedEx Express U.S.
• Coding Guidelines for FedEx Express U.S.
• Transaction Fields for FedEx Express U.S. Shipments
• Shipping Service Options for FedEx Express U.S.
• Shipping Dangerous Goods with FedEx Express U.S.
• FedEx Express U.S. Transaction Samples
About FedEx Express U.S. and FedEx Express U.S. Freight
Before you code FedEx Express U.S. package transactions, become familiar with basic shipping rules for this service. This topic lists the
transaction rules for FedEx Express U.S. and FedEx Express U.S. Freight services.
FedEx Express U.S.
When coding FedEx Express U.S. transactions, follow these package rules:
• You can ship FedEx Express U.S. packages to any of the 50 United States.
• FedEx provides custom packaging for FedEx Express shipments. You may choose to ship using the FedEx Envelope®, FedEx Pak®,
FedEx Box, and FedEx Tube®. You may also ship using your own packaging.
• Both commercial and residential shipments may be shipped. Residential packages must be identified in your shipping transaction.
• You may bill the shipping costs to your FedEx account, to the recipient’s FedEx account, or to a third party FedEx account number.
• Maximum size limit for a FedEx Express U.S. package is 150 pounds and 119 inches in length, or 165 inches in length and girth.If your
package exceeds 150 pounds or is larger more than 119 inches in length or 165 inches in length and girth, you must use FedEx Express
U.S. Freight as your shipping service.
FedEx Express U.S. Freight
When coding FedEx Express U.S. Freight transactions, follow these freight rules.
• When package weights exceed 150 pounds or dimensions are greater than 119 inches long or 80 inches wide, FSMS allows you to ship
these packages as FedEx Express U.S. Freight. Before you create a FedEx Express Freight ship transaction, keep the following rules in
mind:
v 10.6.1
FedEx Ship Manager® Server Developer Guide
5-1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
–FedEx 1Day® Freight requires a booking number from Freight Customer Services before the shipment is tendered to FedEx.
–Enter your 1Day Freight booking number in Field 1272 (Booking Number) in the 020 Global Ship Request Transaction. The booking
number, when included in the 020 transaction, prints on the shipping label.
More information on freight packaging, including packing skids, is available when you call FedEx Express Freight Customer Service at 1800-332-0807.
Transaction Rules and Restrictions for FedEx Express U.S.
Rules for transaction field entries vary according to the FedEx Express U.S. special service you select when you ship a package. The
following rules apply to all FedEx Express U.S. shipping transactions:
• Use Field 1274 (Service Type) to specify FedEx Express U.S. service for the package or shipment. You must enter the code for a FedEx
Express special service option. See the transaction restrictions for each service in this topic:
–FedEx Priority Overnight® ("01")
–FedEx 2Day® ("03")
–FedEx Standard Overnight® ("05")
–FedEx First Overnight® ("06")
–FedEx Express Saver® ("20")
• Shipper and Recipient addresses for FedEx Express U.S. shipments must be U.S. locations.
• If a package weight exceeds 150 LBS or its dimensions are greater than 119" in length or 80" in width, then do not ship the package using
a FedEx Express U.S. shipping transaction. Instead, use the FedEx Express U.S. Freight service.
FedEx Priority Overnight
The following transaction rules apply when shipping FedEx Express U.S. packages using FedEx Priority Overnight service.
• Use Field 1274 set to 01 when you need next-business-day delivery by 10:30 a.m., by 5 p.m. in remote areas or by 1:30 on Saturdays.
Delivery to and from many areas of Alaska and Hawaii may take 1 or 2 business days.
• Check whether this service is available to your Recipient address before creating the transaction. Priority Overnight is available to and
from all 50 United States, but not all areas of Alaska and Hawaii.
• When estimating time-in-transit and delivery date, delivery days are Monday through Friday, with Saturday pickup only.
• You can include Saturday pickup and delivery in a transaction. Check to make sure this service is available for the area to which you are
shipping. There is an additional charge for Saturday pickup service.
• You can code these special service options in a FedEx Priority Overnight transaction: Saturday pickup, Saturday delivery, dangerous
goods, Collect-on-Delivery (C.O.D.) service, FedEx Delivery Signature options, Hold at FedEx Location and Saturday Hold at Location.
FedEx 2Day
The following transaction rules apply when shipping FedEx Express U.S. packages using FedEx 2Day service.
• Use Field 1274 set to 03 when you need to get a package to its destination in 2 business days (by 4:30 p.m. to most areas and by 7 p.m.
to residences). Delivery to some rural areas of Alaska and postal codes in Hawaii may be 3 business days.
• There are no restrictions on U.S. origin and destination addresses. FedEx 2Day service is available to and from all 50 United States.
• When estimating time-in-transit and delivery date, delivery days are Monday through Friday, with Saturday pickup only.
5-2
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
• You can include Saturday pickup and delivery in a transaction. Check to make sure this service is available for the area to which you are
shipping. There is an additional charge for Saturday pickup service.
• You can code these special service options in a FedEx 2Day transaction: Saturday pickup, Saturday delivery, dangerous goods
(inaccessible items only), Collect-on-Delivery (C.O.D.) service, FedEx Delivery Signature options, Hold at FedEx Location and Saturday
Hold at Location.
FedEx Standard Overnight
The following transaction rules apply when shipping FedEx Express U.S. packages using FedEx Standard Overnight service.
• Use Field 1274 set to 05 when you need next-business-day delivery by 3 p.m. and to rural areas by 4:30 p.m. Delivery to and from many
areas of Alaska and Hawaii may take 1 or 2 business days.
• Check whether this service is available to your Recipient address before creating the transaction. Standard Overnight is available to and
from all 50 United States, but not all areas of Alaska and Hawaii.
• When estimating time-in-transit and delivery date, delivery days are Monday through Friday, with Saturday pickup only.
• You can include Saturday pickup in a transaction. Check to make sure this service is available for the area to which you are shipping.
There is an additional charge for Saturday pickup service.
• You can code these special service options in a FedEx Standard Overnight transaction: Saturday pickup, dangerous goods (inaccessible
items only), Collect-on-Delivery (C.O.D.) service, FedEx Delivery Signature options and Hold at FedEx Location.
FedEx First Overnight
The following transaction rules apply when shipping FedEx Express U.S. packages using FedEx First Overnight service.
• Use Field 1274 set to 06 when you need early morning delivery of a package.
• Enter Shipper and Recipient addresses within the contiguous 48 United States and Shipper addresses from Alaska only. FedEx First
Overnight service is not available from or to Hawaii or to Alaska.
• You can code for these options: Saturday pickup, FedEx Delivery Signature and dangerous goods for dry ice only.
FedEx Express Saver
The following transaction rules apply when shipping FedEx Express U.S. packages using FedEx Saver service.
• Use Field 1274 set to 20 when you require delivery to a business address in 3 days by 4:30 p.m. or to a residential address in 3 days by
7 p.m.
• Check whether this service is available from your shipping address to your Recipient address before creating the transaction. Express
Saver is available to and from all 48 contiguous United States. It is not available to or from Alaska and Hawaii.
• You can code these special service options in a FedEx Express Saver transaction: Saturday pickup, dangerous goods (inaccessible
items only), Collect-on-Delivery (C.O.D.) service, FedEx Delivery Signature options, and Hold at FedEx Location.
Available Shipping Methods for FedEx Express U.S.
The shipping methods available for FedEx Express U.S. packages are:
• Single Piece
• Multiple-Piece Shipment (MPS)
• Single Shot MPS
• Open Ship
v 10.6.1
FedEx Ship Manager® Server Developer Guide
5-3
Chapter 5: Coding Transactions for FedEx Express U.S. Service
FedEx Express U.S. Multiple-Piece Shipping
A multiple-piece shipment (MPS) consists of two or more packages shipped to the same recipient.
To create an MPS shipment, you can choose from one of the following options to create an MPS transaction:
• Single transaction with multiple occurrence fields (referred to as a Single Shot)
• Open Ship transactions with CREATE shipment, ADD piece and CONFIRM shipment functions
FedEx Express U.S. multiple-piece shipments, however, do not have a master tracking number that links the packages together in a single
shipment. The lack of a master tracking number affects how packages are counted and package information appears on labels.
To distinguish packages in a FedEx Express shipment, you can label the packages with the package count (for example: 1 of 3, 2 of 3, and
3 of 3).
FedEx Express U.S. Open Ship Transaction Fields
You can use the Open Ship shipping method to ship multiple-piece shipments for FedEx Express U.S.
For information about how to process an Open Ship shipment, see Chapter 4: FedEx Ship Manager Server Open Ship Transactions.
Coding Guidelines for FedEx Express U.S.
When you code a FedEx Express U.S. transaction, follow these rules:
• Use the 020 Global Ship Request transaction to request all FedEx Express U.S. shipping functions. Replies are returned in the 120
Global Ship Reply transaction.
• Always begin each transaction with the Transaction Code Field 0 and enter the value "020" or "20". For example, 0,"020".
• Always include Field 1 Customer Transaction Identifier in each transaction. This field lets you link transaction “replies” back to the
transaction “requests” in those instances where you are performing multiple shipment transactions for bulk shipments.
• Always include the meter number (Field 498) of the client/device on which you are running the FSMS transactions.
• Include Field 1274 (Service Type) and select the code that specifies the type of FedEx Express U.S. service you want to use. There is no
general code for FedEx Express U.S.; you must select one of these services:
–01 — FedEx Priority Overnight
–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 3Day® Freight
• You must provide “Ship To” information in the transaction. Include in Field 11 (Recipient Company) the recipient name and in Field 12
(Recipient Contact Name) the contact information for the company or person to whom you are sending the shipment.
• Your “Ship From” information is entered as part of your FSMS configuration. If the “Ship From” information is different, you must include
the shipper name and contact information in the transaction.
• Always include Field 23 (Pay Type). You may have the shipping costs billed to your FedEx account, to the recipient of the shipment or to
a third party.
• You must specify the packaging type for your shipment; that is, whether the package is prepared by the shipper or uses a FedEx box,
envelope, tube or pak. Pass Field 1273 (Packaging Type) with this information.
• You must specify the weight of the package in Field 1670 (Package Weight/Shipment Weight). This field must contain individual package
weights only. FedEx Ship Manager Server performs the weight summation and package count.
5-4
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
• You can use the Open Ship method to ship FedEx Express U.S. Open Ship requires that you use Field 541 (Open Ship Flags) to specify
the shipping function and use Field 542 (Open Ship Index) to identify the shipment index associated with the flagged function in Field
541.
• Add more fields if you wish to send the package using any of the FedEx Express U.S. special options, such as Hold At Location, Collect
on Delivery and Saturday Pickup. Each of these options has a special flag field and each is described in this guide.
• Always end each transaction with the End of Record Indicator Field 99. Do not enter a value in this field. The field should always look like
this: 99,""
Transaction Fields for FedEx Express U.S. Shipments
Table 5-1 lists the transaction fields required to ship a FedEx Express U.S. package or shipment. See other special service options, such as
Hold At Location and Saturday Pickup, for additional fields.
Table 5-1: Fields Required for FedEx Express U.S. Shipments
Transaction: 020 Global Ship Request - Single Piece, Single Shot, Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
N
I
Description
Transaction Code
0
Max=3
FDXE
All
Field Level: Shipment
REQUIRED.
Indicates the start of a transaction.
For example, 0,"020" or 0,"20" signifies the start of the 020 Global Ship
Request transaction.
Customer Transaction Identifier
1
Max=30
A
I
FDXE
All
Field Level: Shipment
Optional
The transaction identifier (ID) lets you link transaction “replies” back to the
transaction “requests” in the case of a bulk shipment. FSMS does not
require this field, but it is available and recommended for customer use.
A
I
FDXE
All
Field Level: Shipment
REQUIRED*
Company name of the Recipient.
*Required if shipment is being sent to a company.
If this field is not applicable, Field 12 (Recipient Name) must be
completed.
I
FDXE
All
Field Level: Shipment
REQUIRED*
Contact name at the Recipient company.
*Required if a recipient company is not provided.
*Required for all C.O.D. (U.S. domestic service only), alcohol, bill
recipient, and bill third party.
*Required for Hold at Location service.
Recipient Company
11
Max=35
Recipient Contact Name
12
v 10.6.1
Max=35
A
FedEx Ship Manager® Server Developer Guide
5-5
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-1: Fields Required for FedEx Express U.S. Shipments (Continued)
Transaction: 020 Global Ship Request - Single Piece, Single Shot, Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Description
Recipient Address Line 1
13
Max=35
A
I
FDXE
All
Field Level: Shipment
REQUIRED.
Primary address line of Recipient address. This is the address to which
the shipment is sent.
A
I
FDXE
All
Field Level: Shipment
REQUIRED*
Second address line of Recipient address. This is the address to which
the shipment is sent.
*Required if the address contains secondary address elements such as
apartment number, suite number, floor building, and so forth in addition to
the street name and street number provided in Field 13 (Recipient
Address Line 1).
A
I
FDXE
All
Field Level: Shipment
REQUIRED.
City name for the Recipient address. This is the city to which the shipment
is sent.
Minimum of 3 characters required for city name.
I
FDXE
All
Field Level: Shipment
REQUIRED*
State or province code of the Recipient address.
Field length is 2 for U.S.
*Required for U.S. domestic
Recipient Address Line 2
14
Max=35
Recipient City
15
Max=35
Recipient State/Province
16
Min= 2
A
See Appendix C in the FedEx Ship Manager® Server Transaction Coding
Reference Guide for a list of state codes.
Recipient Postal Code
17
Max=10
A
I
FDXE
All
Field Level: Shipment
REQUIRED*
Postal code for the city and state or province code of the Recipient
address.
I
FDXE
All
Field Level: Shipment
REQUIRED.
Phone number of the Recipient address. This number is used for FedEx
Collect on Delivery (C.O.D.), Hold at FedEx Location (HAL) and alcohol
shipments.
Note: Do not include non-numeric characters such as a parenthesis or
dash.
Recipient Phone Number
18
5-6
Max=15
A
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-1: Fields Required for FedEx Express U.S. Shipments (Continued)
Transaction: 020 Global Ship Request - Single Piece, Single Shot, Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Max=1
N
I
FDXE
All
Field Level: Shipment
REQUIRED.
Code for payment type.
FedEx Express payment types are:
1 — Bill Sender
2 — Bill Recipient or Consignee
3 — Bill Third Party
A
I
FDXE
All
Field Level: Shipment
REQUIRED*
Two-digit code indicating the country of the Recipient address.
*Required for FedEx International Priority DirectDistribution (IPD), FedEx
International Economy DirectDistribution (IED) and FedEx International
Priority DirectDistribution Freight (IDF) shipments.
*Required for FedEx SmartPost.
*Required for ADD Piece Open Ship function.
See Appendix C in the Transaction Coding Reference Guide for country
codes.
NULL
Value
I
FDXE
All
Field Level: Shipment
REQUIRED
Indicates the end of a transaction. The format is 99,"" (99 followed by a
comma and two quotation marks). All FSMS transactions must end with
99,"".
N
I
FDXE
All
Field Level: Shipment
REQUIRED* or Defaulted.
Unique number assigned to a FedEx shipping account (used in each
transaction to identify the revenue/shipping activity of a shipment).
Defaults to the master meter number.
*Required if the meter number is different than the meter number
configured as the default.
Note: If a one-to-one relationship exists between meter numbers and
account numbers (in other words, there is no more than one meter
number per account number), then the meter number or the account
number alone may be used in the transaction.
Note: In FSMS version 10.0.1, meter numbers are expanded to ninedigits in length. Your assigned meter number may be any length up to
nine-digits.
Description
Pay Type
23
Recipient Country
50
Max=2
End of Record Indicator
99
Max=0
Meter Number
498
v 10.6.1
Max=7
FedEx Ship Manager® Server Developer Guide
5-7
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-1: Fields Required for FedEx Express U.S. Shipments (Continued)
Transaction: 020 Global Ship Request - Single Piece, Single Shot, Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
N
I
FDXE
All
Field Level: Package
REQUIRED.
Available for Express (U.S. domestic and international):
01 — Customer packaging
02 — FedEx Pak
03 — FedEx Box
04 — FedEx Tube
06 — FedEx Envelope
N
I
FDXE
All
Field Level: Shipment
REQUIRED.
Service type provided by the shipper.
Valid service types are:
FedEx Express U.S.:
01 — FedEx Priority Overnight
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 3Day Freight
Description
Packaging Type
1273
Max=2
Service Type
1274
Max=2
Note: For FedEx SmartPost shipping, reference Field 2417 in Table 7-9
on page 7-49.
5-8
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-1: Fields Required for FedEx Express U.S. Shipments (Continued)
Transaction: 020 Global Ship Request - Single Piece, Single Shot, Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Description
Package Weight/Shipment Weight
1670
Max=8.2
N
I
FDXE
All
Field Level: Shipment for international and intra-Canada, Package for
U.S. domestic.
REQUIRED*
Weight of package or shipment.
*Required for U.S. domestic shipping (including FedEx Ground® HazMat
shipments) to specify individual package weights. FSMS will perform the
weight summation and package count.
*Required if Field 1493 is Y.
*Required to receive rate quotes.
This weight field supports two implied decimals for ALL shipments and
does not require any distinction between FedEx Express, FedEx Ground
or FedEx International shipping.
For U.S. Domestic Shipping:
You must enter individual package weights only. FSMS performs the
weight summation and package count. This method is optional for all
FedEx International shipping including U.S. Export.
For all FedEx International and intra-Canada Shipping:
You may enter the total shipment weight rather than the individual
package weights. If you enter the total shipment weight, you must also
use Field 116 (Package Total) to indicate the total number of packages in
the shipment.
Maximum weights allowed are:
FedEx Express (non-Freight) — 150 lbs.
FedEx Ground — 150 lbs.
FedEx Home Delivery® — 70 lbs.
Deleting a FedEx Express Shipment
Use the 023 Global Delete Request transaction to delete a single piece or all pieces in a FedEx Express U.S. domestic multiple-package
shipments.
Note: If you enter a tracking number associated with a multiple-piece shipment, then FSMS deletes all pieces in this shipment.
Shipping Service Options for FedEx Express U.S.
FedEx Ship Manager Server supports most FedEx shipping services and options.
The following sections describe options available with FedEx Express U.S. and Freight shipping.
FedEx Express U.S. shipping service options include these delivery and shipment services:
• Alerts — FedEx Ship Alert
• Collect on Delivery — FedEx Express C.O.D.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
5-9
Chapter 5: Coding Transactions for FedEx Express U.S. Service
• FedEx Delivery Signature Options
• Future Day Shipment
• Hold at Location — FedEx Hold at Location
• Residential Delivery
• Saturday Service — Saturday Delivery, Saturday Pickup
• FedEx shipping service options include shipping for
• Alcohol
• Dangerous Goods
• Dry Ice
FedEx Express U.S. Collect-on-Delivery Service
FedEx offers Collect-on-Delivery service for FedEx Express with flexible payment options. This service is available within the U.S. only and
is available for both FedEx Express and freight shipments.
Use the FedEx Express C.O.D. service option to designate the amount of money that the FedEx Express courier collects from the recipient
upon shipment delivery. Enrollment is not required. C.O.D. checks are returned to the shipper via FedEx Standard Overnight shipping
schedule plus 90-minutes. Two labels (one outbound and one inbound) print at the time of shipping for automation customers.
C.O.D. service is not available with FedEx Same Day or FedEx First Overnight. In addition, C.O.D. service is not available to and from
extended service areas for FedEx Express Freight Services. Also, C.O.D. service is not available to and from Puerto Rico or other
international locations. C.O.D. service is available for FedEx Express service in Canada.
FedEx contacts your recipient before delivery so payment is ready. Your recipient can pay by personal check, money order, cashier’s check,
company check, official check, or certified check. FedEx returns payment to you the next business day by FedEx Standard Overnight (where
available; otherwise, FedEx 2Day).
Transaction Shipping Rules
The following shipping rules apply to FedEx C.O.D. shipments:
• You can set the C.O.D. flag to Y if Field 1274 (Service Type) is set to one of these FedEx Express services:
–01 for FedEx Priority Overnight
–05 for FedEx Standard Overnight
–03 for FedEx 2Day
–20 for FedEx Express Saver
–70, 80, 83 or 111 for FedEx Express Freight
• You cannot set Field 1274 to 06 for FedEx First Overnight. Collect-on-Delivery service is not available for this service.
• Do not set Field 1274 to an international service. C.O.D. is not available for international shipments.
• Dangerous goods (Field 1331 Dangerous Goods/HazMat Flag) may be shipped as C.O.D.
• You may include Field 1200 (Hold at Location Flag). C.O.D. service is available for Hold at Location.
• Use Field 54 (C.O.D. Cashiers Check or Money Order) to choose between Secured Payment (cashier’s check, official check or money
order) and Unsecured Payment (personal check, money order, cashier’s check, company check, official check, or certified check).
• Always provide a contact name for the C.O.D. delivery in Field 12.
• Always provide C.O.D. Return information in the event the shipment is refused by the recipient.
5-10
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
C.O.D. Field Descriptions
You can configure how C.O.D. charges are assessed through the 020 Global Ship Request transaction. Use the FSMS fields in Table 5-2 to
code C.O.D. shipments.
Table 5-2: Fields for FedEx Express U.S. C.O.D.
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Description
Recipient Contact Name
12
Max=35
A
I
FDXE
US
Field Level: Shipment
REQUIRED*
Contact name at the Recipient company.
*Required if a recipient company is not provided.
*Required for all C.O.D. (U.S. domestic service only), alcohol, bill
recipient, and bill third party.
*Required for Hold at Location service.
*Required for FedEx SmartPost®.
C.O.D. Flag
27-#
Max=1
A
I
FDXE
US
Field Level: Shipment level for FedEx Express
REQUIRED*
When set to Y, indicates that shipment is being shipped Collect on
Delivery (C.O.D.), and “C.O.D.” prints in the box beside the recipient
name on the bill of lading. Multiple-occurrence field.
*Required for C.O.D.
Valid values are:
Y — Package is C.O.D.
N — Package is NOT sent C.O.D. (default)
I
FDXE
US
Field Level: Shipment level for FedEx Express
REQUIRED
C.O.D. Collect Amount
53-#
Max=10.2 N
Amount of payment that must be collected upon delivery of the FedEx®
Collect on Delivery (C.O.D.) package.
Multiple-occurrence field.
C.O.D. Cashiers Check or Money Order
54
v 10.6.1
Max=1
A
I
FDXE
US
Field Level: Shipment
REQUIRED*
Indicates whether payment on the FedEx Collect on Delivery (C.O.D.)
package requires a cashier’s check or money order.
*Required if cashier's check or money order is required.
Valid values are:
Y — Requires cashier’s check or money order for payment
N — Does not require cashier’s check or money order for payment
FedEx Ship Manager® Server Developer Guide
5-11
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-2: Fields for FedEx Express U.S. C.O.D. (Continued)
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Description
C.O.D. Add Freight Charges Flag
186
Max=1
A
I
FDXE
US
CA
Field Level: Shipment
Optional
Indicates whether freight charges are added to an intra-U.S. or intra-CA
C.O.D. shipment and if so, the type of charge.
Valid values are:
Y — Add discounted net charge
N — No additional charges added to the C.O.D. amount (default)
1 — Add discounted net charge (same as Y)
2 — Add list net charge
3 — Add discounted C.O.D. charge
4 — Add list C.O.D. surcharge
5 — Add discounted Customer Total Charge
6 — Add list Customer Total Charge
I
FDXE
US
Field Level: Shipment
Optional
Name of a Collect on Delivery (C.O.D.) remit payer to be passed in the
transaction, if different from Sender.
FDXE
US
REQUIRED*
Field used by the “Pre-assign tracking number” function.
*Required if pre-assigning a tracking number to a C.O.D. return shipment.
Tracking number of the C.O.D. return package should be populated when
the C.O.D. package tracking number is pre-assigned using Field 1222
(Preassigned Tracking Number/ProNumber).
I
FDXE
US
Optional
Identifies the type of shipment.
Use only for routing.
Valid values are:
0201 — Domestic (default)
0301 — Master C.O.D.
0321 — C.O.D. Return
0261 — C.O.D. MPS*
*MPS is the acronym for multiple-piece shipment.
I
FDXE
US
Field Level: Shipment
Optional
Telephone number for return of Collect-on-Delivery (C.O.D.) package.
Default is configured in FSMS Configuration Utility.
C.O.D. Remit Payor Name
439
Max=30
A
Preassigned C.O.D. Return Tracking Number
1224
Max=15
N
I
Preassigned C.O.D. Return Form ID
1225
Max=4
N
C.O.D. Return Phone Number
1237
5-12
Max=10
A
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-2: Fields for FedEx Express U.S. C.O.D. (Continued)
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Description
C.O.D. Return Company Name
1238
Max=35
A
I
FDXE
US
Field Level: Shipment
Optional
Name of company for return of Collect on Delivery (C.O.D.) package.
Default is configured in FSMS Configuration Utility.
I
FDXE
US
Optional
Department name for return of Collect-on-Delivery (C.O.D.) package.
I
FDXE
US
Field Level: Shipment
Optional
First line of return address for Collect-on-Delivery (C.O.D.) package.
A
I
FDXE
US
Field Level: Shipment
Optional
Second line of return address for Collect-on-Delivery (C.O.D.) package.
Default is configured in FSMS Configuration Utility.
A
I
FDXE
US
Field Level: Shipment
Optional
City of the return address for Collect-on-Delivery (C.O.D.) package.
Default is configured in FSMS Configuration Utility.
A
I
FDXE
US
Field Level: Shipment
Optional
State code of return address for Collect-on-Delivery (C.O.D.) package.
Default is configured in FSMS Configuration Utility.
C.O.D. Return Department
1239
Max=12
A
C.O.D. Return Address Line 1
1240
Max=35
A
C.O.D. Return Address Line 2
1241
Max=35
C.O.D. Return City
1242
Max=35
C.O.D. Return State
1243
Max=2
See Appendix C in the FedEx Ship Manager® Server Transaction Coding
Reference Guide for a list of state codes.
C.O.D. Return Postal Code
1244
v 10.6.1
Max=10
A
I
FDXE
US
Field Level: Shipment
Optional
Postal code of return address for Collect-on-Delivery (C.O.D.) package.
Default is configured in FSMS Configuration Utility.
FedEx Ship Manager® Server Developer Guide
5-13
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-2: Fields for FedEx Express U.S. C.O.D. (Continued)
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Description
Package Association and Print Mode
2600
Max=2
A
I
FDXE
US
Optional
Field specifies package association and Print-As-You-Go (PAYG) option
for US Domestic Express C.O.D. Requires value set to:
03 — Package association and print labels with each Create/Add Piece
transaction for Domestic MPS; Print-As-You-Go (PAYG-A).
Note: For Open Ship Print-As-You-Go (PAYG) shipments, you must
CONFIRM the shipment on the same date as CREATE, otherwise labels
will have the incorrect ship date.
FedEx Delivery Signature Options - FedEx Express
Use FedEx Delivery® Signature Options to specify the level of signature required for FedEx Express and Freight shipments using the 020
Global Ship Request transaction with Field 2399 (Signature Required Type).
To have FedEx obtain a signature when your package is delivered, choose from one of four FedEx signature options:
• Deliver Without Signature
–No signature is required for delivery. Select this option by coding the field as 2399,"1" to deliver the shipment without collecting
a signature. This is the default for all residential deliveries. This signature level is not available to commercial addresses. No
surcharge is applied.
• Indirect Signature Required
–A signature can be obtained from any individual at the address specified on the package, from a signed door tag, or from an individual
at a neighboring address. Select this option by coding the field as 2399,"2" to deliver the shipment when an indirect signature is
obtained. FedEx charges a fee for this service when shipments are delivered to residential addresses. This service option is available
for FedEx Express. Address corrections are permitted.
• Direct Signature Required
–A signature can be obtained from any individual at the address specified on the package. Select this option by coding the field as
2399,"3" to deliver the shipment with when a direct signature is obtained. FedEx charges a fee for this service. This service
option is available for FedEx Express. Address corrections are permitted.
• Adult Signature Required
–A signature can only be obtained from an individual 21 years of age or older at the address specified on the package. Select this
option by coding the field as 2399,"4" to deliver the shipment only when an adult signature is obtained. A government-issued,
photo ID is required for age verification. This service option incurs a fee for all deliveries. This service option is available for FedEx
Express. Address corrections are not permitted.
5-14
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Delivery Signature Field Description
Table 5-3 describes Field 2399 (Delivery Signature) and the types of shipments that require delivery signatures.
Table 5-3: Delivery Signature Field 2399
Transactions: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Signature Required Type
2399-#
v 10.6.1
Max=1
N
Description
Transactions: 020/120 Global Ship Request/Reply
I
FDXE
All
Field Level: Package level except for FedEx Express C.O.D. which is
applied at the shipment level.
REQUIRED*
Valid values are:
0 — Not Present
1 — Deliver without Signature
2 — Indirect
3 — Direct
4 — Adult
• 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.
• C.O.D. or dangerous goods 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 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 shipments and
all international shipments require an Individual Signature. Direct
Signature and Adult Signature are available as an upgrade for U.S.
domestic
FedEx Express shipments. A surcharge is 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 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 is applied if an upgrade is selected.•
Direct Signature is the only signature option available for FedEx 1Day
and 2Day Freight Services (U.S. domestic FedEx Express Freight
services).
FedEx Ship Manager® Server Developer Guide
5-15
Chapter 5: Coding Transactions for FedEx Express U.S. Service
FedEx Delivery Signature Options Restrictions - FedEx Express
Signature options are supported for all FedEx Express U.S. domestic packages and FedEx Express C.O.D. shipments.
The following rules and restrictions apply:
• If you are an international customer and are shipping a package to a U.S. recipient, then you must include a delivery signature option
(Field 2399 Signature Required Type) for your shipment.
• When indicating a delivery signature option, use Field 2399 at the package level for FedEx Express U.S. service and at the shipment
level for FedEx Express U.S. C.O.D. service.
• If you include Field 1332 (Alcohol Flag) to indicate an alcohol shipment, always include the required Adult signature field (2399,"4").
• No signature option is allowed for Hold at FedEx location shipments.
• C.O.D. or dangerous goods and shipments with an insurance value greater than $499 USD require a direct signature (2399,"3") and
a surcharge is not applied. However, if you upgrade to the adult signature option (2399,"4"), a surcharge will be applied. Indirect
signature and delivery without a signature are not available options for these types of shipments.
• Direct Signature (2399,"3") is the only option available for FedEx 1Day Freight and FedEx 2Day Freight Services.
• When creating a multiple-piece shipment (MPS) C.O.D. shipment using Open Ship, use Field 2399 in the CREATE transaction.
• When creating a FedEx Express MPS C.O.D. shipment using a single transaction with multiple occurrence fields, use a single
occurrence of Field 2399.
FedEx Delivery Signature Options for Special Services
This topic describes signature options and requirements for special services. Coding special services transactions with Field 2399
(Signature Required Type) missing or incorrect can result in an error or an override by the transaction processing system. Table 5-4 lists
FedEx Delivery Signature Options for special services.
Table 5-4: Delivery Signature Options for Special Services
Special Service
Signature Levels
Description
Alcohol
4 — Adult
Signature level 4 is the only accepted level
and any other value defaults to 4.
HAL
0 — Unspecified
Signature levels 0 — 4 default to 0.
C.O.D., ECOD, or Express DG
0 — Unspecified
1 — None
2 — Indirect
3 — Direct
4 — Adult
Signature levels 0 — 3 default to 0 and do not
incur a surcharge. Signature level 4 incurs a
surcharge.
Declared/Carriage Value greater than $499
USD
0 — Unspecified
1 — None
2 — Indirect
3 — Direct
4 — Adult
Signature levels 0 — 3 default to 3 and do not
incur a surcharge. Signature level 4 incurs a
surcharge.
All Other Cases (any other special service/
scenario, including no special services)
0 — Unspecified
1 — None
2 — Indirect
3 — Direct
4 — Adult
Signature levels 0 and 1 default to 0 and do
not incur a surcharge. Signature levels 2, 3,
and 4 do incur a surcharge.
5-16
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
FedEx Express Future Day
Use Future Day shipping to prepare a FedEx Express shipment up to ten (10) days from the actual ship date. A label prints when the
shipment is processed, but the shipment can be held until the specified day becomes current before tendering the package to the courier.
Future Day is allowed for all FedEx Express shipping services. A FedEx Express label appears on the specified ship date. To specify a
Future Day shipment, include Field 24 (Ship Date) in the 020 Global Ship Request transaction with the specified shipping date. Table 5-5
describes Field 24 (Ship Date).
Table 5-5: Future Day Ship Date Field
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Ship Date
24
Max=8
Description
Transactions: 107 End-of-Day Close Reply, 020 Global Ship Request, 024 Shipment Query Request
N
I
FDXE
All
Field Level: Shipment
REQUIRED*
Date of shipment.
*Required for Future Day shipping. Format: CCYYMMDD
Default: Current meter date.
For example, July 1, 2005 is coded as: 20050701
For FedEx Express, ship date can be set in advance up to the number of
days allowed by date range in the URSA file; includes Returns services.
Deleting a Future Day Shipment
You can delete a Future Day shipment before the shipping day is closed using the 023/123 Global Delete Request/Reply transaction. This
deletes the future ship date from the FSMS shipment history database on the local FSMS client. These shipments are not uploaded to
FedEx.
However, after you close your shipping day, Future Day shipments are uploaded to FedEx and kept in a reserve file. Therefore, a 023 Global
Delete Request transaction must be uploaded to FedEx to cancel Future Day shipments after Close.
FedEx Express Hold At FedEx Location
FedEx Express Hold at Location (HAL) service is available to customers who want to pick up a package at a designated FedEx location
rather than have it delivered. For example, approved wine shippers may want to use the FedEx Express Hold at Location (HAL) service for
consumers who prefer to pick up their wine shipments from a FedEx Office or FedEx Express Station counter location. HAL is also useful
when shipping to a recipient who does not have a residential or office address. An additional charge is assessed for this service.
If your transaction specifies Hold At Location (Field 1200 set to Y), you must specify the Hold at Location pickup address for the nearest
FedEx location offering the HAL service option. Select the FedEx pickup location (designated FedEx Kinko’s Office and Print Centers®,
FedEx Kinko’s® Ship Centers, or FedEx World Service Center®) by using the Web Services Drop-Off Locator (contact your FedEx customer
integration consultant if you need assistance).
When you include this option, FedEx Express labels display “Hold at Location” to indicate packages will not be delivered by a FedEx courier.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
5-17
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Transaction Rules for FedEx Express Hold at Location
Follow these rules to successfully code the Hold at Location service option for FedEx Express.
• To specify you want a package held at a FedEx pickup location, include Field 1200 (Hold at Location Flag) set to the value Y.
• Be sure to include a contact name (Field 12) and phone number (Field 18) for the recipient. After a HAL package is received at the FedEx
location, the recipient is notified by FedEx personnel that the package is available for pickup.
• Always include the address and phone number for the FedEx pickup location you select.
• For shipments within the U.S., the Recipient address state must be the same state as the HAL pickup location address.
• You can turn on the Hold at Location flag if you are also coding for one of these FedEx Express services:
–FedEx Priority Overnight (Saturday service available) - Field 1274 set to 01
–FedEx 2Day (Saturday service available) - Field 1274 set to 03
–FedEx Standard Overnight - Field 1274 set to 05
–FedEx Express Saver - Field 1274 set to 20
–FedEx Express 1Day Freight U.S.- Field 1274 set to 70
–FedEx Express 2Day Freight U.S. - Field 1274 set to 80
–FedEx Express 3Day Freight U.S. - Field 1274 set to 83
• You must include all required fields listed in Table 5-6.
Table 5-6: Fields for FedEx Express Hold at Location Service
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Recipient Contact Name
12
Max=35
A
I
FDXE
All
REQUIRED*
Contact name at the Recipient company.
*Required if a recipient company is not provided.
*Required for Hold at Location service.
Max=35
A
I
FDXE
All
Optional
Line 1 of the return address of the FedEx location where the package is
held for pickup.
Default is Recipient information.
Max=35
A
I
FDXE
All
Optional
City of the FedEx location where package is held for pickup.
Default is Recipient information.
A
I
FDXE
All
Optional
State code of the FedEx location where package is held for pickup.
Default is Recipient information.
HAL Address
44
HAL City
46
HAL State
47
Max=2
See Appendix C in FedEx Ship Manager® Server Transaction Coding
Reference Guide for a list of state codes.
5-18
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-6: Fields for FedEx Express Hold at Location Service (Continued)
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I
FDXE
All
Optional
Postal code of the FedEx location where package is held for pickup.
Default is Recipient information.
A
I
FDXE
All
Optional
Recipient phone number is used if you do not provide a number.
I
FDXE
All
REQUIRED*
Indicates whether the shipment is to be held at a designated location
other than the recipient’s address.
*Required for all Hold At FedEx Location shipments.
Valid values are:
Y — Hold at designated location
N — Do not hold at location
Description
HAL Postal Code
48
Max=10
HAL Phone Number
49
Max=15
Hold at Location Flag
1200
Max=1
A
Saturday Pickup and Delivery Service
Saturday shipping pickup and delivery services are available for FedEx Express U.S. domestic package shipments. Saturday service is
available to limited locations in Alaska. It is not available to Hawaii. An additional charge is assessed for this service. Charges are not
applied to shipments rated as FedEx Express Multi-weight.
Saturday Pickup
For U.S. package shipments, Saturday pickup is available with these FedEx Express services for an additional charge:
• FedEx First Overnight
• FedEx Priority Overnight
• FedEx Standard Overnight
• FedEx 2Day
• FedEx Express Saver
Saturday Delivery ─ FedEx Express U.S. Package Shipments
Saturday delivery is available for an additional charge for the following FedEx Express services:
• FedEx Priority Overnight
• FedEx 2Day
Saturday Delivery ─ FedEx Express U.S. Freight Shipments
For FedEx Express U.S. freight shipments, Saturday pickup is available with the following services to several U.S. markets for an additional
charge:
• FedEx 1Day Freight
• FedEx 2Day Freight
v 10.6.1
FedEx Ship Manager® Server Developer Guide
5-19
Chapter 5: Coding Transactions for FedEx Express U.S. Service
To determine if a Saturday delivery is available to your destination, go to fedex.com/us/expressfreight and select Use Service Area
Locator or call 1.800.332.0807.
The Hold At FedEx Location service is not available with Saturday delivery for FedEx Express U.S. freight shipments. Do not code the
FSMS fields for these two services together in the same transaction set.
Saturday Pickup and Delivery Fields - FedEx Express
When coding for Saturday service, use Field 24 (Ship Date), Field 1266 (Saturday Delivery Flag), and Field 1267 (Saturday Pickup Flag) as
described in Table 5-7.
Table 5-7: FedEx Express Saturday Pickup and Delivery Fields
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
N
I
FDXE
All
Field Level: Shipment
REQUIRED*
Date of shipment.
*Required for Future Day shipping. Format: CCYYMMDD
Default: Current meter date.
For example, July 1, 2005 is coded as: 20050701
For FedEx Express, ship date can be set in advance up to the number of
days allowed by date range in the URSA file; includes Returns services.
I
FDXE
All
REQUIRED*
Specify Y if the shipment is to be delivered on a Saturday.
*Required for Saturday Delivery service.
Valid values:
Y — Saturday Delivery
N — No Saturday Delivery
Note: Saturday Delivery FedEx Express Freight shipments are only
allowed within the U.S. or U.S. inbound.
For shipping, use any transaction method.
I
FDXE
All nonFreight
US
CA
INTL
REQUIRED*
Specify Y if the shipment is to be picked up on a Saturday.
*Required for Saturday pickup service.
Valid values:
Y — Saturday Pickup
N — No Saturday Pickup
Not valid for FedEx Express Freight.
For this shipment, use any method.
Description
Ship Date
24
Max=8
Saturday Delivery Flag
1266
Max=1
A
Saturday Pickup Flag
1267
5-20
Max=1
A
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Inside Pickup and Delivery - FedEx Express U.S. Freight Only
For those FedEx customers who do not have the necessary equipment to move freight shipments from or to their loading area, FedEx
provides an inside pickup and delivery service to move shipments to areas adjacent to the loading area. The adjacent loading area is
defined as a pickup site that is directly accessible from the curb and is no more than 50 feet inside the outermost door.
You may add an Inside Pickup or Inside Delivery request to the following FedEx Express Freight services. No special service contract is
required.
• FedEx 1Day Freight
• FedEx 2Day Freight
• FedEx 3Day Freight
If additional breakdown of the shipment is required (for example, to fit the shipment through a doorway), additional charges may be
assessed. FedEx does not provide package count or package verification when a breakdown of a freight shipment occurs at delivery site.
Inside Delivery Charge
When requested, FedEx may move shipments to positions beyond the adjacent loading area. When a FedEx courier delivers a shipment per
this request, FedEx assesses an inside delivery charge in addition to all other applicable charges. To flag a transaction for this charge, you
must include Field 1121 (Rate Return Code) in a 020 Global Ship Request transaction; for example, 1121,"Y".
Inside Delivery Flag
Table 5-8 describes the attributes of the Inside Delivery Flag field that you must use to specify an inside delivery for a FedEx Express U.S.
freight shipment.
Table 5-8: Inside Delivery Flag Field
Transactions: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Inside Delivery Flag
1121
Max=1
Description
Transactions: 020 Global Ship Request
A
I
FDXE
U.S.
Freight:
F1DAY
F2DAY
F3DAY
Optional
Specify Y if the shipper requests FedEx to move the shipment to an area
inside or adjacent to the delivery area.
Valid values are:
Y — Delivered an inside-delivery area
N — Not delivered to an inside-delivery area
Alcohol Shipping
FedEx accepts shipments of alcohol (beer, wine, and spirits) within the U.S. and for both U.S. import and export when the shipper and the
recipient are licensed to import and export alcohol.
Alcohol Shipping Rules
Before you can ship alcohol with FedEx, you must meet the following requirements:
• You must complete a Wine Shippers Agreement with FedEx. This agreement is available from your FedEx account executive.
• The shipper should identify the shipment as containing wine or alcohol by entering $AW in the Your Reference field for all shipments. If
the shipper does identify Field 1332 as containing alcohol, FedEx will overlay this field with $AW.
• FedEx packaging cannot be used for alcohol shipments.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
5-21
Chapter 5: Coding Transactions for FedEx Express U.S. Service
• You must select 4 — Adult Signature as the signature type in Field 2399 (Signature Required Type). Field 51 (Signature Release) is not
allowed for alcohol shipments.
• Every package containing wine is required to have a label affixed to it by the shipper identifying it as such. Your FedEx account executive
can order these labels for you.
• If you have questions regarding your eligibility to ship alcohol, contact your FedEx customer support representative.
Shipping Dangerous Goods with FedEx Express U.S.
You can use FSMS transactions to ship dangerous goods (DG) for FedEx Express under International Air Transport Association (IATA) and
49 CFR Air regulations for Other Regulated Materials-Domestic (ORM-D). While any FedEx Express dangerous goods shipment can be
shipped under IATA regulations, only the following destination shipments are shipped under ORM-D regulations:
• Intra-U.S. (Domestic)
• Puerto Rico — inbound and outbound
• U.S. Territories — inbound and outbound
Identify Dangerous Goods Item Before You Ship
Many common items are considered dangerous goods, including aerosol sprays, car batteries, fireworks, lighters, matches, paints and
perfumes.
If you are not sure whether your commodity meets the criteria for dangerous goods or what dangerous goods identification and classification
applies to your shipment, contact the U.S. Department of Transportation or FedEx Dangerous Goods Hotline.
Note: You can contact the U.S. Department of Transportation at 1.800.467.4922. If you have further questions about shipping dangerous
goods with FedEx, call the FedEx Dangerous Goods/Hazardous Material Hotline — call 1.800.GoFedEx 1.800.463.3339 and say
“dangerous goods”.
Note: See the FedEx Service Guide for limitations for dangerous goods shipments to Alaska, Hawaii and many international destinations.
Dangerous Goods Shipping Restrictions
You must prepare U.S. and international FedEx Express dangerous goods shipments as single piece shipments only. If you use Open Ship,
any dangerous goods information entered after the CREATE transaction is ignored. If you print the 1421C form, Shipper’s Declaration for
dangerous goods, only the dangerous goods information associated with the CREATE prints, and the remaining pages of the form are
blank.
Shipping Dangerous Goods in Excepted Quantities
If shipping dangerous goods (DG) defined by the International Air Transport Association (IATA) as Dangerous Goods in Excepted
Quantities, the full dangerous goods validation is not required.
If shipping Dangerous Goods in Excepted Quantities, then only Field 1331 (Dangerous Goods/HazMat Flag) and Field 1669 (Excepted
Quantities Flag) are required. Field 1331 must be set to a value of E and Field 1669 must be set to a value of Y.
Dangerous Goods in Excepted Quantities shipments are not assessed a dangerous goods surcharge and no Shippers Declaration for
Dangerous Goods Form (FedEx 1421C or FedEx LZR DG DEC FORM) is printed.
5-22
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Required Fields for Dangerous Goods in Excepted Quantities
Table 5-9 lists the fields to include in a 020 Global Ship Request Transaction when shipping dangerous goods in excepted quantities.
Table 5-9: Required Fields for Dangerous Goods in Excepted Quantities
Transaction: 020 Global Ship Request - Single Piece, Open Ship
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Description
Dangerous Goods/HazMat Flag
1331
Max=1
A
I
FDXE
All
Field Level: Shipment
REQUIRED*
Indicates dangerous goods (DG) and/or hazardous materials (HazMat)
are contained in the shipment.
*Required if shipping hazardous materials (HazMat) or dangerous goods
ORM-D.
Set to Q to indicate shipment contains Excepted Package Radioactive
Reportable Quantity (EPRRQ) commodity.
Valid values are:
A — Accessible Dangerous Goods (ADG)
I — Inaccessible Dangerous Goods (IDG)
E — Excepted Quantities
Q — Excepted Package Radioactive Reportable Quantity (EPRRQ)
Y — Shipment contains DG/HazMat
N — Shipment contains no DG/HazMat
Note: Values are not case-sensitive; “Q” and “q” both indicate EPRRQ.
For “All Packed in Ones,” calculation and printing of Q on the 1421C from
shall be excluded if:
• one of the commodities is Dry Ice (UN ID 1845) or
• if columns H, J, and L on 1421C indicate “No Limit” or
when only one commodity qualified for the calculation
Excepted Quantities Flag
1669
v 10.6.1
Max=1
A
I
FDXE
US
INTL
Indicates whether excepted quantities exist in shipment.
Valid values are:
Y — Excepted quantities exist
N — No excepted quantities (default)
Note: Error 3094, “Excepted Quantities are not allowed with other
Dangerous Goods” returns when Field 1669 is set to Y AND Field 1331
(Dangerous Goods/HazMat Flag) is equal to one of these values:
A — Accessible DG
I — Inaccessible DG
Y — Shipment contains DG/HazMat
FedEx Ship Manager® Server Developer Guide
5-23
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-10 shows the allowed combinations of values in Fields 1331 and 1669.
Table 5-10: Allowed Values for Fields 1331 and 1669
1331
1669
Results
Y
Y
Error
I
Y
Error
A
Y
Error
N
Y
Successful
I
N
Successful
A
N
Successful
E
Y or N
Successful
Example of Dangerous Goods Excepted Quantities Transaction
0,"020"1," DG -EPRRQ1"11,"Shipping Co. Inc."13,"1154 Elm Lane"15,"Portland"16,"OR"17,"97006"
18,"4132445657"23,"1"25,"Example Transaction"50,"US"187,"199"451,"1869"456,"1"461,"Metal
Container"466,"500"471,"KG"476,"Y419"484,"9015551212"485,"DG Signatory"489,"iii"498,""537,""
1273,"01"1274,"1"1331,"q"1493,"Y"1660,"Y"1669,"Y"1670,"2500"1900,"I"1903,"Magnesium alloys"
1904,"N"1918,"EI DuPont"1922,"Warehouse"1932,"1"99,""
Dangerous Goods Technical Name
Use Field 446 (Dangerous Goods Technical Name) to specify the technical name for any dangerous goods shipped using FedEx Express.
Table 5-11 describes Field 446 for FedEx Express shipping.
Table 5-11: Dangerous Goods Technical Name Field
Transactions: 020 Global Ship Request - Single Piece, Single Shot, Open Ship
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Dangerous Goods Technical Name
446
Min=1
AN
Max=255
I
Description
Transactions: 020 Global Ship Request
FDXE
All
Field Level: Shipment
REQUIRED*
Technical name of the hazardous materials (HazMat) or dangerous
goods (DG) being shipped.
*Required if the proper shipping name ends in '*' in the International Air
Transport Association (IATA) Dangerous Goods (DG) Regulations
manual. Otherwise, the field is optional and not required for shipping.
*Required If a customer attempts to ship a Ground HazMat shipment,
Field 1274 set to 92, Field 1331 set to Y with a valid UN ID number in
Field 451 that contains the symbol “G” (i.e. UN3098).
*Not required if DG class is radioactive.
Note: Maximum of 999 field occurrences is allowed.
See Section 8.1.3.1 of the IATA DG Regulations.
Note: This field is used for both FedEx Ground® hazardous materials and FedEx Express dangerous goods.
5-24
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Dangerous Goods Shipping Rules
Shipments with dangerous goods must be tendered to FedEx Express in accordance with current International Air Transport Association
(IATA) regulations for air transport and the FedEx Express Terms and Conditions. This is required regardless of the routing and whether they
end up physically moving by air transportation, ground transportation, or any combination of these.
Note: The federal government requires every shipper to have job-specific dangerous goods training before tending a dangerous goods
shipment to any air carrier. Register at fedex.com for government-mandated training. FedEx Express offers a full three-day course, a oneday refresher course for experienced shippers, and private seminars at your location. Call 1-800-GoFedEx 1-800-463-3339 and say
“dangerous goods” for more information or see fedex.com.
You may ship accessible and inaccessible dangerous goods within the U.S. using the FedEx Express shipping services listed in Table 5-12.
When shipping, be aware that many FedEx drop-off locations cannot accept dangerous goods.
Table 5-12: Service Options for Dangerous Goods
FedEx Express Dangerous Goods U.S. Service Options1
Accessible Dangerous Goods
•
FedEx Priority Overnight
•
FedEx 1Day Freight
Inaccessible Dangerous Goods
•
FedEx Priority Overnight
•
FedEx Standard Overnight
•
FedEx 2Day
•
FedEx Express Saver
•
FedEx 1Day Freight
•
FedEx 2Day Freight
•
FedEx 3Day Freight
1
Dangerous goods service is not available for FedEx First Overnight.
It is the shipper’s responsibility to identify, classify, package, mark, label and complete documentation for dangerous goods according to all
national and international governmental regulations. In addition, FedEx can only accept Shipper’s Declarations for Dangerous Goods in
typed or computer-generated formats, not hand-written. The shipper must provide three copies of the completed Shipper’s Declaration for
Dangerous Goods for each shipment.
Note: Dry Ice, UN 1845 does not require a Shipper’s Declaration for Dangerous Goods form in the IATA DG Regulations if dry ice is the only
DG in the shipment.
Creating a Dangerous Goods Transaction
To help you complete FedEx Express dangerous goods shipments, FSMS includes an IATA spreadsheet in the
C:\FedEx\FedEx_Tables\iata_03_2008.xls file. Refer to this spreadsheet when preparing FedEx Express dangerous
goods shipments.
The input requirements for non-U.S. origin FedEx Express shipments containing dangerous goods were recently relaxed. Only two fields are
required: Field 1331 (Dangerous Goods/HazMat Flag) and Field 492 (Dangerous Goods Class/DOT Hazard Class or Division Number).
If you want FSMS to print the Shipper’s Declaration of Dangerous Goods Form (either FedEx 1421C or FedEx LZR DG DEC FORM), you
must include the reference fields described later in this section. The Shipper’s Declaration of Dangerous Goods Form can be printed as a
multi-ply form using a DOT matrix printer (FedEx 1421C form) or on a laser printer (FedEx LZR DG DEC FORM). The latter is plain white
paper with a border of red hatchings). The FedEx LZR DG DEC FORM can be obtained from your FedEx supply source.
The Shipper’s Declaration for Dangerous Goods form is produced at the time of shipment confirmation. See Chapter 3: FedEx Ship
Manager Server Label and Form Transactions for an example of the Shipper’s Declaration for Dangerous Goods Form, both the FedEx
1421C and the FedEx LZR DG DEC FORM.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
5-25
Chapter 5: Coding Transactions for FedEx Express U.S. Service
For U.S. and international FedEx Express dangerous goods shipments, you can ship up to 999 unique UN ID Numbers under a single
tracking number. You can prepare a shipment as a single transaction with required multiple occurrence fields repeated up to 999 times.
Fields Required for FedEx Express Dangerous Goods
Table 5-13 shows the required fields for a dangerous goods transaction request.
Table 5-13: Fields Required for FedEx Express Dangerous Goods Shipment
Transaction: 020 Global Ship Request - Single Shot up to 999 UN IDs
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Description
Dangerous Goods Class/DOT Hazard Class or Division Number
492
Max=5
A
I
FDXE
All
REQUIRED*
Government classification of the dangerous goods (DG) item. This class/
division determines whether the DG is categorized as accessible or
inaccessible by FedEx Express.
*Required for radioactive materials.
*Required if Field 451 (Dangerous Goods UN Number/Identification
Number) has multiple names (i.e. UN1263, Paint). If customer sends in a
HazMat ship request without Field 492 and Field 1331 is set to Y and the
UN ID has multiple names, Error Message 0799 will be returned - “The
Dangerous Goods Class cannot be left blank.” and the transaction fails.
See the FedEx Service Guide for more details.
FDXE
All
Field Level: Shipment
REQUIRED*
Indicates dangerous goods (DG) and/or hazardous materials (HazMat)
are contained in the shipment.
*Required if shipping hazardous materials (HazMat) or dangerous goods
ORM-D.
Set to Q to indicate shipment contains EPRRQ commodity.
Valid values are:
A — Accessible Dangerous Goods (ADG)
I — Inaccessible Dangerous Goods (IDG)
E — Excepted Quantities
Q — Excepted Package Radioactive Reportable Quantity (EPRRQ)
Y — Shipment contains DG/HazMat
N — Shipment contains no DG/HazMat
Note: Values are not case-sensitive; “Q” and “q” both indicate EPRRQ.
For “All Packed in Ones,” calculation and printing of Q on the 1421C from
shall be excluded if:
Dangerous Goods/HazMat Flag
1331
Max=1
A
I
• one of the commodities is Dry Ice (UN ID 1845) or
• if columns H, J, and L on 1421C indicate “No Limit” or
• when only one commodity qualified for the calculation
5-26
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Adding Dangerous Goods Packages to Shipments
Use these fields when adding dangerous goods packages to a FedEx Express shipment. You may add only up to 999 UN ID numbers in a
single shot transaction with multiple-occurrence fields.
See the FedEx Ship Manager® Server Transaction Coding Reference Guide for a complete list of dangerous goods (DG) fields, including
fields required for radioactive and infectious goods (DG Class 6.2).
Table 5-14: Fields for Adding Dangerous Goods to a FedEx Express Shipment
Transaction: 020 Global Ship Request - Single Shot up to 999 UN IDs
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Description
Dangerous Goods Technical Name
446-#
Max=50
N
I
FDXE
All
Field Level: Shipment
REQUIRED*
Technical name of the hazardous materials (HazMat) or dangerous
goods (DG) being shipped.
*Required if the proper shipping name ends in '*' in the International Air
Transport Association (IATA) Dangerous Goods (DG) Regulations
manual. Otherwise, the field is optional and not required for shipping.
*Required If a customer attempts to ship a Ground HazMat shipment,
Field 1274 set to 92, Field 1331 set to Y with a valid UN ID number in
Field 451 that contains the symbol “G” (i.e. UN3098).
*Not required if DG class is radioactive.
Note: Maximum of 999 field occurrences is allowed.
See Section 8.1.3.1 of the IATA DG Regulations.
Dangerous Goods UN Number/Identification Number
451
Max=4
N
I
FDXE
All
Field Level: Shipment
REQUIRED*
UN number of the dangerous goods shipment.
*Required for dangerous goods shipments if Field 1900 is set to I — IATA.
*Required if Field 1493 (DG/HazMat Form Print Flag) is set to Y and
printing the FedEx Ground Hazardous Materials Shipping Paper, OP900.
See Table 4.2 column A of the IATA DG Regulations for non-radioactive
DG and Section 10.4.1 for radioactive DG.
The IATA regulations limit the EPRRQ designation to a small subset of
UN numbers.
FDXE
All
REQUIRED
Specify the number of dangerous goods packages within the shipment.
Dangerous Goods Number of Units
456-#
v 10.6.1
Max=5
N
I
FedEx Ship Manager® Server Developer Guide
5-27
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-14: Fields for Adding Dangerous Goods to a FedEx Express Shipment (Continued)
Transaction: 020 Global Ship Request - Single Shot up to 999 UN IDs
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Description
Dangerous Goods Packing Type
461-#
Max=35
A
I
FDXE
All
Field Level: Shipment
REQUIRED*
Specify packing type used for the dangerous goods shipment.
*Required for dangerous goods shipments, unless the DG class is
radioactive. Not required if DG class is radioactive.
See Section 5 of the IATA DG Regulations.
FDXE
US
Field Level: Shipment
REQUIRED*
Specify the net quantity of the dangerous goods shipment being shipped.
Use with Field 471 to specify the unit of measure.
*Not required if DG class is radioactive.
Dangerous Goods/HazMat Quantity
466-#
Max=6.2
N
I
Dangerous Goods/HazMat Unit of Measure (UOM)
471-#
Max=4
A
I
FDXE
US
Field Level: Shipment
REQUIRED*
Specify the unit of measure of the dangerous goods (DG) quantity (Field
466). Must match the selected DG per the IATA DG Regulations.; for
example, ml, L, g, kg, kg G.
Note: Lbs may be used if Field 1900 (Dangerous Goods Regulation
Indicator) is set to O.
See Appendix B.2.2 of the IATA DG Regulations for acceptable
abbreviations.
*Not required if DG class is radioactive.
FDXE
US
Field Level: Shipment
Optional
Specify packing instruction number from column G, I, or K of the IATA DG
Regulations manual. Use plain text.
Not required if DG class is radioactive or “Not Restricted”.
FDXE
US
Field Level: Shipment
REQUIRED*
Authorization of the dangerous goods being shipped.
*Not required if DG class is radioactive.
Use this field in a single shot or Open Ship transaction for a U.S.
shipment.
Dangerous Goods Packing Instructions
476-#
Max=4
A
I
Dangerous Goods Authorization
483-#
5-28
Max=148 A
I
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-14: Fields for Adding Dangerous Goods to a FedEx Express Shipment (Continued)
Transaction: 020 Global Ship Request - Single Shot up to 999 UN IDs
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Description
Dangerous Goods Emergency Phone Number
484
Max=15
A
I
FDXE
US
Field Level: Shipment
REQUIRED*
Specify the emergency telephone number to be contacted for the
shipment unless the packing instruction has a Y prefix or has one of the
following UN #’s: 1845, 2807, 2857, 2969, 3166, 3171, 3358, 8000.
*Required for dangerous goods shipments if Field 1900 is set to I — IATA.
Note: If a customer attempts to ship a Ground HazMat shipment,
Field 1274 set to 92, Field 1331 set to Y with a valid UN ID number in
Field 451, but does not pass in Field 484, Emergency Contact Number,
the customer receives Error Message 3001 - “The Emergency Phone
Number is required” and the transaction fails.
See Table 4.2 column A of the IATA DG Regulations for non-radioactive
DG and Section 10.4.1 for radioactive DG.
The IATA regulations limit the EPRRQ designation to a small subset of
UN numbers.
Dangerous Goods Title of Signatory
485
Max=35
A
I
FDXE
US
Field Level: Shipment
REQUIRED*
Specify the title of the signatory for the shipment.
*Required for dangerous goods shipment if Field 1900 is set to
I — IATA.
See Table 4.2 column A of the IATA DG Regulations for non-radioactive
DG and Section 10.4.1 for radioactive DG.
Dangerous Goods Additional Handling Information
486
Max=175 A
I
FDXE
US
Field Level: Shipment
REQUIRED*
Additional handling information that may apply to the dangerous goods
shipment; DG only.
*Not required if DG class is radioactive.
I
FDXE
US
REQUIRED*
Indicates whether the dangerous goods (DG) item is only allowed for
cargo aircraft.
Valid values are:
Y — Cargo aircraft only
N — Multiple aircraft - passenger or cargo aircraft
This field is necessary only if multiple aircraft types (passenger versus
cargo aircraft) exist for the shipment and the maximum net quantities are
different. If the multiple aircraft types exist along with multiple packing
groups, this flag determines which packing group and aircraft type
combination will be used.
DG Cargo Aircraft Only Flag
488-#
v 10.6.1
Max=1
A
FedEx Ship Manager® Server Developer Guide
5-29
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-14: Fields for Adding Dangerous Goods to a FedEx Express Shipment (Continued)
Transaction: 020 Global Ship Request - Single Shot up to 999 UN IDs
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Description
DG Cargo Aircraft Only Flag
488-#
(cont.)
Max=1
A
I
FDXE
US
*Required if a cargo aircraft packing instruction from the IATA DG
Regulations is used.See Table 4.2 column K of the IATA DG Regulations.
See the FedEx Service Guide for more information or dial
1.800.GoFedEx 1.800.463.3339 and press 81 for dangerous goods.
US
Field Level: Shipment
REQUIRED*
Specify the appropriate packing group for the dangerous goods (DG)
being shipped.
*Required if a customer sends in a ship request when the UN ID has
multiple entries (i.e. UN ID 1263, Paint). Error Message 3034, “The
Packing Group is required” is displayed.
*Required if 1493 (DG/HazMat Form Print Flag) is set to Y and you are
printing the FedEx Ground Hazardous Materials Shipping Paper, OP900.
*Not required if DG class is radioactive.
Valid values are:
I — Packing Group I
II — Packing Group II
III — Packing Group III
This field can be entered as one blank (spacebar) for dangerous goods
that do not have a packing group. Entries must be made as Roman
Numerals.
Dangerous Goods/HazMat Packing Group
489-#
Max=3
A
I
FDXE
FedEx Express Other Regulated Materials-Domestic
If you ship FedEx Express DG ORM-D packages within the U.S., then you must include the Dangerous Goods Packing Type (Field 461) in
the 020 Global Ship Request transaction. This new ORM-D rule applies to all FedEx Express U.S. domestic dangerous goods ORM-D
shipments.
Ship FedEx Express dangerous goods using the Open Ship or Single Piece shipping method. You may not use the Single Shot method.
Field 461 (Dangerous Goods Packing Type) for ORM-D shipments prints the packaging type on the Shipper’s Declaration for Dangerous
Goods form (FedEx 1421C and FedEx LZR DG DEC FORM), and includes the number of pieces, net quantity, and unit of measure.
Table 5-15 lists the required fields for a successful FedEx Express DG ORM-D transaction.
5-30
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-15: EPRRQ Required Fields for FedEx Express Dangerous Goods ORM-D Packages
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Dangerous Goods/HazMat Flag
1331-#
Max=1
A
I
Description
Transactions: 020 Global Ship Request
FDXE
All
Field Level: Shipment
REQUIRED*
Indicates dangerous goods (DG) and/or hazardous materials (HazMat)
are contained in the shipment. Can be entered manually on the BOL.
Set to:
Y — Shipment contains DG/HazMat
For U.S. dangerous goods, use this field in a Single Shot or Open Ship
transaction. For an international dangerous goods shipment, use this field
in a Single Piece transaction only. For hazardous materials, use this field
only in Single Piece transactions.
Dangerous Goods Regulation Indicator
Transactions: 020 Global Ship Request
1900
FDXE:
US
INTL
Max=1
A
I
FDXE
Field Level: Shipment
REQUIRED
Set to:
O — ORM-D (49 CFR) regulations apply (U.S. and Puerto Rico only)
Note: If the ORM-D regulations apply, then the only DG fields that will be
required are 456 (Dangerous Goods Number of Units), 466 (Dangerous
Goods/HazMat Quantity), 471 (Dangerous Goods/HazMat Unit of Measure (UOM)), 488 (DG Cargo Aircraft Only Flag), 1311 (Number of Label
Copies - Shipper), 1903 (Dangerous Goods Proper Shipping Name /
Department of Transportation (DOT) Shipping Name of Material), and
1932 (Dangerous Goods Commodity Count).
Note: Field 1903 can only be “Consumer Commodity,” “Cartridges, Small
Arms,” or “Cartridges, Power Devices.”). All other DG fields within this
transaction can be ignored.
For U.S. dangerous goods shipments, use this field in Single Shot and
Open Ship transactions. For international dangerous goods shipments,
use in Single Piece transactions.
Dangerous Goods Packing Type
461
v 10.6.1
Max=35
A
I
Transactions: 020 Global Ship Request
FDXE
US
INTL
Field Level: Shipment
REQUIRED*
Specify packing type used for the dangerous goods shipment.
*Required for dangerous goods shipments, unless the DG class is
radioactive. Not required if DG class is radioactive.
See Section 5 of the IATA DG Regulations.
Use this field in a Single Shot or Open Ship transaction for a U.S.
dangerous goods shipment. For an international dangerous goods
shipment, use this field in a Single Piece transaction.
For shipping, use Single Shot, Open Ship, or Single Piece
FedEx Ship Manager® Server Developer Guide
5-31
Chapter 5: Coding Transactions for FedEx Express U.S. Service
About Excepted Package Radioactive Reportable Quantity (EPRRQ)
Excepted package radio actives must have a reportable quantity (RQ) and require a modified version of the Shipper’s Declaration in order to
ship.
The ability to ship EPRRQ commodities is supported by all FedEx Express services where dangerous goods are currently allowed. These
include:
• FedEx® International DirectDistribution Surface Solutions origins: Canada (IDD CA) and Mexico (IDD MX)
• FedEx International Priority DirectDistribution®
• FedEx International Priority DirectDistribution® Freight
Note: EPRRQ commodities are only permitted when and where “inaccessible dangerous goods” commodities are permitted and IATA
Validation occurs.
Shipping EPRRQ Commodities
Excepted Package Radioactive Reportable Quantity (EPRRQ) commodities can be shipped using the 020/120 Global Ship Request/Reply
transaction with these shipping methods:
• Single Piece
• Open Ship Print-As-You-Go (PAYG) mode (intra-U.S. only)
• Open Ship (regular, FedEx International DirectDistribution Surface Solutions, FedEx® International Priority DirectDistribution and FedEx
International Priority DirectDistribution Freight)
Note: Single Shot is not supported. All multiple-piece dangerous goods shipments must be shipped using the Open Ship shipping method.
To indicate that a shipment contains ERPPQ commodities
Use the flag code “Q” for EPRRQ in Field 1331 (Dangerous Goods/HazMat Flag).
Table 5-16: Field 1331 - Code for Excepted Package Radioactive Reportable Quantity
Transactions: 020/120 Global Ship Reply/Request ─ Single Piece, Open Ship
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Dangerous Goods/HazMat Flag
1331
5-32
Max=1
A
I/O
Description
Transactions: 020 Global Ship Request
FDXE
All
Field Level: Shipment
REQUIRED*
Indicates dangerous goods (DG) and/or hazardous materials (HazMat)
are contained in the shipment.
*Required if shipping hazardous materials (HazMat) or dangerous goods
ORM-D.
Set to Q to indicate shipment contains EPRRQ commodity.
Valid values are:
A — Accessible Dangerous Goods (ADG)
I — Inaccessible Dangerous Goods (IDG)
E — Excepted Quantities
Q — Excepted Package Radioactive Reportable Quantity (EPRRQ)
Y — Shipment contains DG/HazMat
N — Shipment contains no DG/HazMat
Note: Values are not case-sensitive; “Q” and “q” both indicate EPRRQ.
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-16: Field 1331 - Code for Excepted Package Radioactive Reportable Quantity (Continued)
Transactions: 020/120 Global Ship Reply/Request ─ Single Piece, Open Ship
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Dangerous Goods/HazMat Flag
1331
(cont.)
Max=1
A
I/O
Description
Transactions: 020 Global Ship Request
FDXE
All
For “All Packed in Ones,” calculation and printing of Q on the 1421C from
shall be excluded if:
• One of the commodities is Dry Ice (UN ID 1845) or
• If columns H, J, and L on 1421C indicate “No Limit” or
When only one commodity qualified for the calculation
EPRRQ Required Transaction Fields
If the 020 Global Ship Request transaction passes Field 1331 (Dangerous Goods/HazMat Flag) as set to “Q” or “q”, the fields listed in Table
5-17 are required.
Table 5-17: EPRRQ Required Fields for FedEx Express Dangerous Goods ORM-D Packages
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Dangerous Goods/HazMat Flag
1331-#
v 10.6.1
Max=1
A
I
Description
Transactions: 020 Global Ship Request
FDXE
All
Field Level: Shipment
REQUIRED*
Indicates dangerous goods (DG) and/or hazardous materials (HazMat)
are contained in the shipment. Can be entered manually on the BOL.
Set to:
Y — Shipment contains DG/HazMat
For U.S. dangerous goods, use this field in a Single Shot or Open Ship
transaction. For an international dangerous goods shipment, use this field
in a Single Piece transaction only. For hazardous materials, use this field
only in Single Piece transactions.
FedEx Ship Manager® Server Developer Guide
5-33
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-17: EPRRQ Required Fields for FedEx Express Dangerous Goods ORM-D Packages
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Description
Dangerous Goods Regulation Indicator
Transactions: 020 Global Ship Request
1900
FDXE:
US
INTL
Max=1
A
I
FDXE
Field Level: Shipment
REQUIRED
Set to:
O — ORM-D (49 CFR) regulations apply (U.S. and Puerto Rico only)
Note: If the ORM-D regulations apply, then the only DG fields that will be
required are 456 (Dangerous Goods Number of Units), 466 (Dangerous
Goods/HazMat Quantity), 471 (Dangerous Goods/HazMat Unit of Measure (UOM)), 488 (DG Cargo Aircraft Only Flag), 1311 (Number of Label
Copies - Shipper), 1903 (Dangerous Goods Proper Shipping Name /
Department of Transportation (DOT) Shipping Name of Material), and
1932 (Dangerous Goods Commodity Count).
Note: Field 1903 can only be “Consumer Commodity,” “Cartridges, Small
Arms,” or “Cartridges, Power Devices.”). All other DG fields within this
transaction can be ignored.
For U.S. dangerous goods shipments, use this field in Single Shot and
Open Ship transactions. For international dangerous goods shipments,
use in Single Piece transactions.
Dangerous Goods Packing Type
461
Max=35
A
I
Transactions: 020 Global Ship Request
FDXE
US
INTL
Field Level: Shipment
REQUIRED*
Specify packing type used for the dangerous goods shipment.
*Required for dangerous goods shipments, unless the DG class is
radioactive. Not required if DG class is radioactive.
See Section 5 of the IATA DG Regulations.
Use this field in a Single Shot or Open Ship transaction for a U.S.
dangerous goods shipment. For an international dangerous goods
shipment, use this field in a Single Piece transaction.
For shipping, use Single Shot, Open Ship, or Single Piece
Table 5-18 Required 020 Transaction Fields for EPRRQ
Transaction EPRRQ Required Fields
Valid Values
020 /120 Global Ship Request/Reply Shipping Transaction - Single Piece, Open Ship
1331-#
5-34
Dangerous Goods/HazMat Flag
Field Level: Shipment
REQUIRED*
When set to Q, indicates shipment contains Excepted Package
Radioactive Reportable Quantity (EPRRQ) commodity.
*Required if shipping dangerous goods.
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-18 Required 020 Transaction Fields for EPRRQ (Continued)
Transaction EPRRQ Required Fields
Valid Values
020 /120 Global Ship Request/Reply Shipping Transaction - Single Piece, Open Ship
1331-#
(cont.)
Dangerous Goods/HazMat Flag
Valid value for EPRRQ is:
Q — Excepted Package Radioactive Reportable Quantity (EPRRQ)
Note: Values are not case-sensitive; “Q” and “q” both indicate EPRRQ.
For “All Packed in Ones,” calculation and printing of Q on the 1421C from
shall be excluded if:
• one of the commodities is Dry Ice (UN ID 1845) or
• if columns H, J, and L on 1421C indicate “No Limit” or
when only one commodity qualified for the calculation
1900
Dangerous Goods Regulation Indicator
Field Level: Shipment
REQUIRED.
Set to “I” to indicate IATA regulations apply (1900,"I").
Valid value is:
I — IATA regulations apply (default)
451
Dangerous Goods UN Number/
Identification Number
Field Level: Shipment
REQUIRED*
UN number of the dangerous goods shipment.
*Required for dangerous goods shipments if Field 1900 is set to
I — IATA.
*Required if Field 1493 (DG/HazMat Form Print Flag) is set to Y and
printing the FedEx Ground Hazardous Materials Shipping Paper, OP-900.
See Table 4.2 column A of the IATA DG Regulations for non-radioactive
DG and Section 10.4.1 for radioactive DG.
The IATA regulations limit the EPRRQ designation to a small subset of UN
numbers.
484
Dangerous Goods Emergency Phone
Number
Field Level: Shipment
REQUIRED*
Specify the emergency telephone number to be contacted for the
shipment unless the packing instruction has a Y prefix or has one of the
following UN #’s: 1845, 2807, 2857, 2969, 3166, 3171, 3358, 8000.
*Required for dangerous goods shipments if Field 1900 is set to
I — IATA.
Note: If a customer attempts to ship a Ground HazMat shipment,
Field 1274 set to 92, Field 1331 set to Y with a valid UN ID number in
Field 451, but does not pass in Field 484, Emergency Contact Number,
the customer will receive Error Message 3001, “The Emergency Phone
Number is required,” and the transaction will fail.
See Table 4.2 column A of the IATA DG Regulations for non-radioactive
DG and Section 10.4.1 for radioactive DG.
The IATA regulations limit the EPRRQ designation to a small subset of UN
numbers.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
5-35
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-18 Required 020 Transaction Fields for EPRRQ (Continued)
Transaction EPRRQ Required Fields
Valid Values
020 /120 Global Ship Request/Reply Shipping Transaction - Single Piece, Open Ship
5-36
485
Dangerous Goods Title of Signatory
Field Level: Shipment
REQUIRED*
Specify the title of the signatory for the shipment.
*Required for dangerous goods shipment if Field 1900 is set to
I — IATA.
See Table 4.2 column A of the IATA DG Regulations for non-radioactive
DG and Section 10.4.1 for radioactive DG.
1903-#
Dangerous Goods Proper Shipping Name / Field Level: Shipment
Department of Transportation (DOT)
REQUIRED*
Shipping Name of Material
Specify the proper shipping name from the IATA DG Regulations for the
dangerous goods shipment being shipped. This name cannot have
“waste” included in it.
*Required for dangerous goods shipments if Field 1900 is set to
I — IATA.
*Required if Field 451 (Dangerous Goods UN Number/Identification
Number) has multiple names (i.e. UN1263, Paint).
Note: Only the first 50 characters print on the FedEx Ground HazMat OP900 report.
See Table 4.2 column B of the IATA DG Regulations for non-radioactive
DG and Section 10.4.1 for radioactive DG.
1918
Dangerous Goods Name of Signatory
Field Level: Shipment
REQUIRED*
Specify the name of the signatory for the shipment.
*Required for shipment if Field 1331 = Q.
1922
Dangerous Goods Place of Signatory
Field Level: Shipment
REQUIRED*
Specify the place of the signatory for the shipment. Minimum requirement
is the name of the city.
*Required for shipment if Field 1331 = Q.
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
EPRRQ Optional Transaction Fields
Table 5-19 lists optional fields when Field 1331 is set to “Q” or “q” for Excepted Package Radioactive Reportable Quantity (EPRRQ). This list
is not inclusive.
Table 5-19: EPRRQ Optional 020 Transaction Fields
Transaction
EPRRQ Required Fields
Valid Values
020/120 Global Ship Request/Reply Shipping Transaction - Single Piece, Open Ship
476-#
Dangerous Goods Packing Instructions
Field Level: Shipment
Optional
Specify packing instruction number from column G, I, or K of the
IATA DG Regulations manual. Use plain text.
Not required if DG class is radioactive or “Not Restricted”.
466-#
Dangerous Goods/HazMat Quantity
Field Level: Shipment
Specify the net quantity of the dangerous goods shipment being
shipped. Use with Field 471 to specify the unit of measure.
*Not required if DG class is radioactive.
446-#
Dangerous Goods Technical Name
Field Level: Shipment
REQUIRED*
Technical name of the hazardous materials (HazMat) or
dangerous goods (DG) being shipped.
*Required if the proper shipping name ends in '*' in the
International Air Transport Association (IATA) Dangerous Goods
(DG) Regulations manual. Otherwise, the field is optional and not
required for shipping.
*Required If a customer attempts to ship a Ground HazMat
shipment, Field 1274 set to 92, Field 1331 set to Y with a valid
UN ID number in Field 451 that contains the symbol “G” (i.e.
UN3098).
*Not required if DG class is radioactive.
Note: Maximum of five (5) field occurrences is allowed.
See Section 8.1.3.1 of the IATA DG Regulations.
461-#
Dangerous Goods Packing Type
471-#
Dangerous Goods/HazMat Unit of Measure Field Level: Shipment
(UOM)
REQUIRED*
Specify the unit of measure of the dangerous goods (DG) quantity
(Field 466). Must match the selected DG per the IATA DG
Regulations.; for example, ml, L, g, kg, kg G.
Note: Lbs may be used if Field 1900 (Dangerous Goods
Regulation Indicator) is set to O.
See Appendix B.2.2 of the IATA DG Regulations for acceptable
abbreviations.
*Not required if DG class is radioactive.
v 10.6.1
Field Level: Shipment
REQUIRED*
Specify packing type used for the dangerous goods shipment.
*Required for dangerous goods shipments, unless the DG class is
radioactive. Not required if DG class is radioactive.
See Section 5 of the IATA DG Regulations.
FedEx Ship Manager® Server Developer Guide
5-37
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-19: EPRRQ Optional 020 Transaction Fields (Continued)
Transaction
EPRRQ Required Fields
Valid Values
020/120 Global Ship Request/Reply Shipping Transaction - Single Piece, Open Ship
483-#
Dangerous Goods Authorization
Field Level: Shipment
REQUIRED*
Authorization of the dangerous goods being shipped.
*Not required if DG class is radioactive.
486
Dangerous Goods Additional Handling
Information
Field Level: Shipment
REQUIRED*
Additional handling information that may apply to the dangerous
goods shipment; DG only.
*Not required if DG class is radioactive.
489-#
Dangerous Goods/HazMat Packing Group Field Level: Shipment
REQUIRED*
Specify the appropriate packing group for the dangerous goods
(DG) being shipped.
*Required if a customer sends in a ship request when the UN ID
has multiple entries (i.e. UN ID 1263, Paint). Error Message 3034,
“The Packing Group is required” is displayed.
*Required if 1493 (DG/HazMat Form Print Flag) is set to Y and
you are printing the FedEx Ground Hazardous Materials Shipping
Paper, OP-900.
*Not required if DG class is radioactive.
Valid values are:
I — Packing Group I
II — Packing Group II
III — Packing Group III
This field can be entered as one blank (spacebar) for dangerous
goods that do not have a packing group. Entries must be made as
Roman Numerals.
1679
DG Printer ID
5-38
Optional
UNC ID of the printer used to print dangerous goods forms if
different than the printer in the FSMS Configuration Utility or if no
printer is configured.
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-19: EPRRQ Optional 020 Transaction Fields (Continued)
Transaction
EPRRQ Required Fields
Valid Values
020/120 Global Ship Request/Reply Shipping Transaction - Single Piece, Open Ship
1680
DG Printer Form Type
Optional
Indicates the type of printer used to print dangerous goods (DG)
forms.
You must match the field occurrence number (for example, 16801) with the occurrence number of Field 1373 (Report Code) for the
type of DG form you request.
Valid values are:
01 — Form Feed (default)
02 — Laser
Note: While you can designate a printer to print DG forms using
Field 568 (Report Directory), Field 1680 allows you to designate a
separate printer for this form type if you use a pin-feed or laser
printer specifically designated as your “Dangerous Goods” printer.
Setting up a separate DG printer using Field 1680 eliminates the
need for changing paper stock in your report printer.
1904
Dangerous Goods A1, A2, A51, A109 Flag Field Level: Shipment
Optional
Indicates dangerous goods (DG) are being shipped under one of
the special provisions (A1, A2, A51, A109) listed in the
International Air Transport Association (IATA) DG Regulations
Manual.
Valid values are:
Y — Shipping under special provision
N — Not shipping under special provision
1919
Dangerous Goods Percentage Number
Field Level: Shipment
REQUIRED*
Specify the percentage of dangerous goods concentration.
*Required if the dangerous goods UN Number is 2031, 1796,
1826, or 1873.
*Not required if DG class is radioactive.
EPRRQ Labels
No Dangerous Goods Human Readable Indicators (IDG or ADG) are printed in the ASTRA section of the label for EPRRQ. Excepted
Package Radioactive (EPRRQ) shipments are not considered to be a dangerous goods shipment.
See “About EPRRQ Labels” on page 3-14 for information about printing EPRRQ labels.
Dry Ice
FedEx Ship Manager Server allows you to ship packages containing dry ice as long as the specifics for the shipment are included in the
shipping transaction.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
5-39
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Dry Ice Shipping Transaction Rules
The following shipping rules apply:
• Use a 020/120 Global Ship Request/Reply transaction to ship dry ice using FedEx Express U.S.
• Use Field 75 (Weight Units) to specify the unit of weight for the shipment weight. All package weights, including the dry ice weight, must
use the same weight units.
• Check to make sure that the weight you enter for the dry ice in Field 1684 (Dry Ice Weight) is less than the total weight of the shipment.
To provide transactional consistency, Field 1684 has two implied decimal parameters and is accepted in either pounds or kilograms
depending on the weight type chosen for the entire shipment in Field 75.
• Do not use a dangerous goods flag when shipping dry ice. Dry Ice is considered a packing material and does not require any dangerous
goods fields for shipping.
Dry Ice Surcharge Applicable Services
The Dry Ice Surcharge is applied as appropriate for non-return shipments for the following services:
• FedEx Express -- U.S. Domestic1
–FedEx First Overnight
–FedEx Standard Overnight
–FedEx Priority Overnight
–FedEx 2Day
–FedEx Express Saver
1
Applies to the U.S. Domestic portion of FedEx® International DirectDistribution Surface Solutions shipments Canada (CA) to U.S. and U.S.
to Canada. U.S. Domestic includes U.S. to Puerto Rico (PR) and Puerto Rico to U.S. shipments.
Returned Dry Ice Surcharge Fields
FedEx Express shipments that include packages that contain dry ice have a Dry Ice Surcharge applied. Dry ice surcharges are assessed
only for shipments that do not contain other dangerous goods. If a shipment contains both dry ice and dangerous goods (accessible/
inaccessible), only the dangerous goods fees are assessed.
The following shipping methods are appropriate:
• FedEx Express intra-U.S./Domestic--Single Piece, Single Piece CONFIRM in Open Ship, and MPS Single Shot/Open Ship
• FedEx Express International-- Single Piece, Single Piece CONFIRM in Open Ship, and MPS Single Shot/Open Ship
Table 5-20 describes the returned fields that contain the dry ice surcharge.
Table 5-20: Dry Ice Surcharge and List Dry Ice Surcharge Fields
Transaction: 120 Global Ship Reply
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Description
Dry Ice Surcharge
4914-#
Max=11.2 A
O
FDXE
FDXG
All
Field Level: Package
Returned value is the Dry Ice Surcharge amount.
O
FDXE
FDXG
All
Field Level: Package
Returned value is the list Dry Ice Surcharge amount.
List Dry Ice Surcharge
4915-#
5-40
Max=11.2 A
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Dynamic Surcharging for Dry Ice
The two Dynamic Surcharge fields, Field 1947 Dynamic Surcharge Code and Field 1945 List Dynamic Surcharge Code, include a code for
dry ice: 680 — Dry Ice
When you enable dynamic surcharging for dry ice, FedEx supports new surcharges within FSMS without requiring that you upgrade to
newer versions of FSMS. This ability is not supported with individual field surcharging. New surcharges show up as another occurrence of
the dynamic surcharge multiple occurrence field with the dry ice code.
The dynamic dry ice surcharge returns in a 120 Global Ship Reply transaction.
Returning the Dry Ice Surcharge in Transactions
Before you can return Dry Ice Surcharge amounts, you must configure your FSMS client system to successfully download list rates. Choose
from one of the following options to set up dry ice surcharge rates on your system:
• Check the List Rates checkbox on the Meter Setting tab of the FSMS Configuration Utility
• Include Field 3062 (Rate Quote Type) set to 2 — List rates and discount rates in a 020 Global Ship Request transaction
The Dry Ice Surcharge amount is returned in the 120 Global Ship Reply transaction using Field 4914 (Dry Ice Surcharge) and Field 4915
(List Dry Ice Surcharge).
If the shipper configures an FSMS client for Dynamic Surcharges, then the 120 Global Ship Reply transaction returns the Dry Ice code 680
in Field 1947 (Dynamic Surcharge Code), as well as the Dry Ice code 680 in Field 1945 (List Dynamic Surcharge Code).
Note: It is critical that List Rates be downloaded to a device and/or implemented prior to requesting the above surcharges. List Rates cannot
be returned by a 120 Global Ship Reply transaction when List Rates are not properly implemented on the shipper’s device. List rates are
courtesy rates only and reflect rates listed in FedEx rate tables on fedex.com.
Table 5-21 summarizes the different ways to request the Dry Ice Surcharge using the 020 Global Ship Request, 025 Rate All Services
Request or 050 Service Type and Special Services transaction. These transactions assume that there is data present in the Request
transaction that requires the Dry Ice Surcharge.
Table 5-21: Ways to Request Dry Ice Surcharge
Transaction
EPRRQ Required Fields
Valid Values
020 Global Ship Request
Rating Transaction: Single Piece, Single Shot, MPS Single Shot, Open Ship
Returns Fields 4914 and 4915 for Dry Ice Surcharge or 1947 and 1945 for Dynamic Surcharges in 120 Global Ship Reply transaction
3062
Rate Quote Type
Use to indicate the type of rates to return in the 125 Global Ship Reply
transaction. Set value to:
2 — List rates and discount rates
1234
Rate/Route/Time-in-Transit Flag
Set to one of these values:
1 — Rate quote
3 — Rate quote and Route/Time-in-Transit
Open Ship Flags
Position 3 (Rate) set to Y
NNYNNNNNN
OR
541
025 Rate All Services Request
Rating Transaction
Returns Fields 4914 and 4915 for Dry Ice Surcharge or 1947 and 1945 for Dynamic Surcharges in 125 Rate All Services Reply
transaction
1234
v 10.6.1
Rate/Route/Time-in-Transit Flag
Set to one of these values:
1 — Rate quote
3 — Rate quote and Route/Time-in-Transit
FedEx Ship Manager® Server Developer Guide
5-41
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Table 5-21: Ways to Request Dry Ice Surcharge (Continued)
Transaction
EPRRQ Required Fields
Valid Values
050 Service Type and Special Services Request
Rating Transaction
Returns Fields 4914 and 4915 for Dry Ice Surcharge or 1947 and 1945 for Dynamic Surcharges in 150 Service Type and Special
Services Reply transaction
1989
Transaction Function
01 — Service Type
02 — Special Service/Acessorial Type
FedEx Express Domestic Billed Weight
When shippers use the 020/120 Global Ship Request/Reply transaction to ship and rate packages, if they use Pay Type Field 23 and select
Bill Recipient (23,"2") or Bill Third Party (23,"3"), then FSMS will return the shipper's list billed weight in Field 60 (Billed Weight).
Note: To return FedEx Express billed weight, you must enable list rates in the FSMS Configuration Utility by checking the list rates checkbox
in the Meters Settings screen and successfully downloading the list rates.
Table 5-22: FedEx Express Domestic Billed Weight
Transactions: 020/120 Global Ship Request/Reply and 025/125 Rate Available Services Request/Reply
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Service Valid For
Billed Weight
60
Max=9.1
For USD
Max=9.0
Description
Transactions: 120 Global Ship Reply, 125 Rate Available Services Reply
N
I/O
FDXE
US
CA
Returned value is the billed weight for packages in the shipment. This
weight is used in rating calculations (dim weight if greater than actual
weight).
Only available for shipments with U.S. and Canada (CA) origins.
Two implied decimal places for weight in KGS. No implied decimal place
for LBS.
FedEx Express U.S. Transaction Samples
The following sections include transaction samples for FedEx Express U.S. services:
FedEx Express U.S. Shipping Transactions
The following sample code shows 020 Global Ship Request FedEx Express transactions for both single and multiple-piece shipments that
have their shipping origin and destination within the United States.
Single Shot Multiple-Piece FedEx Express Shipment with Reference Fields
0,"020"1,"Express single transaction MPS multiple ref fields"11,"Recipient Company"13,"20
Peachtree Rd."15,"Atlanta"16,"GA"17,"30052"18,"9012639234"23,"1"25,"CR001 Package 1"25-2,
"CR002 Package 2"25-3,"CR003 Package 3"25-4,"CR004 Package 4"25-5,"CR005 Package 5"50,"US"
187,"199"498,"3781"537,""1234,"" 1273,"01"1274,"01"1660,"Y"1670,"500"1670-2,"500"1670-3,"500"
1670-4,"500"1670-5,"500"3062,"2"99,""
5-42
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Single Piece FedEx Express U.S. Domestic Shipment
0,"020"1,"Express single transaction single package"11,"Recipient Company"13,"20 Peachtree
Rd."15,"Atlanta"16,"GA"17,"30052"18,"9012639234"23,"1"25,"CR001 Package 1"50,"US"187,"199"
498,""537,"\\printserver\eltronlp"1234,""1273,"01"1274,"01"1282,"N"1660,"N"1670,"350"3062,"2"
99,""
Single Piece FedEx Express U.S. Shipment with ShipAlert and Sender Delivery Notification
0,"020"1,"Express single transaction ShipAlert/POD"11,"Recipient Company"13,"20 Peachtree
Rd."15,"Atlanta"16,"GA"17,"30052"18,"9012639234"23,"1"25,"CR001 Package 1"50,"US"187,"199"
498,""537,"\\printserver\eltronlp"1201,"sender@shipper.com"1202,"recipient@customer.com"1234,
""1273,"01" 1274,"01"1282,"N"1553,"Y"1557,"Y"1660,"N"1670,"700"3062,"2"99,""
Single Piece FedEx Express U.S. Shipment with Collect on Delivery and Third-Party Return Address
0,"020"1,"Express C.O.D. 3rd Party Return"11,"Recipient Company"12,"Mr. Recipient"13,"20
Peachtree Rd."15,"Atlanta"16,"GA"17,"30052"18,"9012639234"23,"1"25,"CR001 Package 1"27,"Y"
50,"US"53,"10000"186,"Y" 187,"199"498,""537,"\\printer\eltronlp"1234,""1237,"9012639234"
1238,"C.O.D. Manager Inc" 1239,"Collections"1240,"30 FedEx Parkway"1241,"1st Floor Horiz"
1242,"Collierville"1243,"TN"1244,"38017"1273,"01"1274,"01"1660,"N"1670,"750"3062,"2"99,""
Single Piece FedEx Express U.S. with Collect on Delivery
0,"020"1,"Step 007 DOM PO YP"10,""11,"Express COD"12,"Express COD"13,"387 Main Street"
14,"FEDEX PARKWAY"15,"New York"16,"NY"17,"10001"18,"1234567890"20,""23,"1"24,""25,"Step 007
DOM PO YP"26,"100"27,"Y"50,"US"53,"2000"75,"lbs"117,"US"187,"PNG"498,""999,"ABC Co"
1116,"IN"1273,"01"1274,"01"1670,"100"99,""
FedEx Express U.S. Freight Shipping Transaction
This code example shows how to ship a package in a single transaction (Single Shot method) when requesting the FedEx Express Freight
service.
Example A
0,"020"1,"Express Freight single transaction single package"11,"Recipient Company"13,"20
Peachtree Rd."1,"Atlanta"16,"GA"17,"30052"18,"9012639234"23,"1"25,"CR001 Package 1"50,"US"
57,"24"58,"36"59,"18"187,"199"498,""537,"\\printserver\eltronlp"1234,""1273,"01"1274,"80"1660
,"N"1670,"20000"3062,"2"99,""
Example B
0,"020"1,"Express Freight single transaction MPS"11,"Recipient Company"13,"20 Peachtree Rd."
15,"Atlanta"16,"GA"17,"30052"18,"9012639234"23,"1"25,"CR001 Package 1"25-2,"CR002 Package 2"
25-3,"CR003 Package 3"25-4,"CR004 Package 4"25-5,"CR005 Package 5"50,"US"57,"18"57-2,"18"57-3,
"18"57-4,"18"57-5,"18"58,"36"58-2,"36"58-3,"36"58-4,"36"58-5,"36"59,"40"59-2,"40"59-3,"40"594,"40"59-5,"40"187,"199"498,""537,"\\printserver\eltronlp"1234,""1273,"01"1274,"80"1660,"Y"
1670,"20000"1670-2,"20000"1670-3,"20000"1670-4,"20000"1670-5,"20000"3062,"2"99,"“
FedEx Express Dangerous Goods Transactions
The following 020 Global Ship Request transactions ship dangerous goods shipments using FedEx Express U.S. domestic service.
Single Dangerous Goods Package with Service Options
This transaction fields for FedEx Express service options, such as Dry Ice and Hold at Location, which are turned off (set to N) in this
transaction.
Chapter 5: Coding Transactions for FedEx Express U.S. Service
0,"020"1,"1000130361"4,"FEDEX"5,"SENDER ADDRESS1"6,"SENDER ADDRESS2"7,"MEMPHIS"8,"TN"9,
"38152"11,"MPHASIS"12,"RECIPIENT NAME"13,"RECIPIENT ADDRESS1"14,"RECIPIENT ADDRESS2"15,
"MEMPHIS"16,"TN"17,"38115"18,"9012639433"23,"1"24,""27,"N"32,"CONTACT NAME"50,"US"51,"N"
69,"10000"75,"LBS"116,"1"117,"US"183,"1111111111"187,"PNG"440,"N"446,"DG TECHNICAL NAME"451,
"3192"456,"1"461,"DG PACKAGINGTYPE"466,"50"471,"KG"476,"417"484,"9012634556"485,"DG TITLE"
486,"DG ADDTIONAL INFO"488,"Y"489,"II"492,"4.2"1116,"I"1120,"N"1121,"N"1200,"N"1209,"N"
1266,"N"1267,"N"1268,"N"1273,"01"1274,"01"1331,"A"1332,"N"1392,"N"1493,"Y"1670,"2000"1900,
"IATA"1903,"SELF-HEATING SOLID, CORROSIVE, INORGANIC, N.O.S."1918,"DG NAME"1922,"DG PLACE"
1932,"1"99,""
Single Dangerous Goods Package with Custom Label
0,"020"1,"Non-rad DG 1"11,"Shipping Co. Inc."13,"1154 Elm Lane"15,"Portland"16,"OR"17,
"97006"18,"4132445657"23,"1"25,"Example Transaction"50,"US"187,"199"451,"1869"456,"1"
461,"Metal Container"466,"500"471,"KG"476,"Y419"484,"9015551212"485,"DG Signatory"489,"III"
537,""1273,"01"1274,"1"1331,"Y"1493,"Y"1660,"Y"1670,"2500"1900,"I"1903,"Magnesium alloys"
1904,"N"1918,"EI DuPont"1922,"Warehouse"1932,"1"99,""
Single Package Containing Nitric Acid in a Metal Container Without Custom Label
0,"020"1,"Non-rad DG 2"11,"Shipping Co. Inc."13,"1154 Elm Lane"15,"Portland"16,"OR"
17,"97006"18,"4132445657"23,"1"25,"Example Transaction"50,"US"187,"199"451,"2031"456,"1"
461,"Metal Container"466,"50"471,"L"476,"813"484,"9015551212"485,"DG Signatory"489,"II"
537,"\\printserver\eltronlp"1273,"01"1274,"1"1282,"N"1331,"Y"1493,"Y"1660,"N"1670,"2500"1900,
"I"1903,"Nitric Acid"1904,"N"1918,"EI DuPont"1919,"10"1922,"Warehouse"1932,"1"99,""
Dangerous Goods Radioactive Type B Material Shipment
0,"020"1,"Radioactive DG 1"11,"Shipping Co. Inc."13,"1154 Elm Lane"15,"Portland"16,"OR"
17,"97006"18,"4132445657"23,"1"25,"Example Transaction"50,"US"187,"199"451,"2917"456,"1"
466,"500"471,"KG"484,"9015551212"485,"DG Signatory"492,"7"537,""1273,"01"1274,"01"1331,"Y"
1493,"Y"1660,"Y"1670,"210"1900,"I"1903,"Radioactive material, Type B(M) package"1904,"N"
1905,"U-238"1906,"50000"1907,"Bq"1908,"type b(m)"1909,"50"1910,""1911,"50"1916,"Solid"
1917,"U-238"1918,"EI DuPont"1922,"Warehouse"1932,"1"3062,"2"99,""
Dangerous Goods Radioactive Material Shipment
0,"020"1,"Radioactive DG 2"11,"Shipping Co. Inc."13,"1154 Elm Lane"15,"Portland"16,"OR"17,
"97006"18,"4132445657"23,"1"25,"Example Transaction"50,"US"187,"199"451,"2911"456,"1"466,
"500"471,"KG"484,"9015551212"485,"DG Signatory"492,"7"537,"\\printserver\eltronlp"1273,"01"
1274,"01"1282,"N"1331,"Y"1493,"Y"1660,"N"1670,"2500"1900,"I"1903,"Radioactive material,
excepted package—instruments"1904,"N"1905,"U-238"1906,"50000"1907,"Bq"1908,"industrial ip1"
1909,"50"1910,""1911,"50"1916,"Solid"1917,"U-238"1918,"EI DuPont"1922,"Warehouse"1932,"1"
99,""
Single Infectious Dangerous Goods Package — 1
0,"020"1,"Infectious DG 1"11,"Shipping Co. Inc."13,"1154 Elm Lane"15,"Portland"16,"OR"17,
"97006"18,"4132445657"23,"1"25,"Example Transaction"50,"US"187,"199"451,"3172"456,"1"461,
"Metal Container"466,"1"471,"L"476,"Y609"484,"9015551212"485,"DG Signatory"489,"II"537,
"\\printserver\eltronlp"1273,"01"1274,"1"1282,"N"1331,"Y"1493,"Y"1660,"N"1670,"1200"1900,"I"
1903,"Toxins, extracted from living sources, liquid, n.o.s."1904,"N"1918,"EI DuPont"1920,
"Mendeleev"1921,"6061234567"1922,"Warehouse"1932,"1"99,""
5-44
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 5: Coding Transactions for FedEx Express U.S. Service
Single Infectious Dangerous Goods Package — 2
0,"020"1,"Infectious DG 2"11,"Shipping Co. Inc."13,"1154 Elm Lane"15,"Portland"16,"OR"
17,"97006"18,"4132445657"23,"1"25,"Example Transaction"50,"US"187,"199"451,"3172"456,"1"
461,"Metal Container"466,"1"471,"L"476,"603"484,"9015551212"485,"DG Signatory"488,"Y"489,"I"
537,"printserver\eltronlp"1273,"01"1274,"1"1282,"N"1331,"Y"1493,"Y"1660,"N"1670,"7500"1900,"I
"1903,"Toxins, extracted from living sources, liquid, n.o.s."1904,"N"1918,"EI DuPont"
1920,"Mendeleev"1921,"6061234567"1922,"Warehouse"1932,"1"99,""
Single Infectious Dangerous Goods Package — 3
0,"020"1,"Infectious DG 3"11,"Shipping Co. Inc."13,"1154 Elm Lane"15,"Portland"16,"OR"17,
"97006"18,"4132445657"23,"1"25,"Example Transaction"50,"US"187,"199"451,"3172"456,"1"461,
"Metal Container"466,"1"471,"L"476,"611"484,"9015551212"485,"DG Signatory"488,"Y"489,"II"
537,"C:\2D Bar Code"1273,"01"1274,"1"1331,"Y"1493,"Y"1660,"Y"1670,"4500"1900,"I"1903,"Toxins,
extracted from living sources, liquid, n.o.s."1904,"N"1918,"EI DuPont"1920,"Mendeleev"1921,
"6061234567"1922,"Warehouse"1932,"1"99,"",
FedEx Express Return Transactions
This sample shows a single piece shipment with Return address to Sender using FedEx Express U.S. domestic service.
0,"020"1,"Auto Step 013 Exp Print return"4,"Print Return"5,"Auto Step 013"7,"Auto Step 013"
8,"TN" 9,"38125"10,""11,"FXRS0771.02.20070503"12,"Auto Step 013"13,"387 Main Street"14,"FEDEX
PARKWAY"15,"New York"16,"NY"17,"10001"18,"1234567890"20,""21,"1"23,"1"24,""25,"SMOKE Auto
Step 013 Exp Print return"26,"100"32,""50,"US"75,"lbs"117,"US"183,"901263684949"187,"PNG"
498,""537,""999,"ABC Co" 1116,"IN"1273,"01"1274,"01"2382,"2"99,""
FedEx Delivery Signature Option Transactions
The following code samples show FedEx Express shipping transactions for three delivery signature options: Indirect Signature
(2399,"2"), Direct Signature (2399,"3") and Adult Signature (2399,"4")
FedEx Express Priority Overnight with Saturday Pickup and Indirect Signature Options
0,"20"1,""11,"Indirect Signature"12,"TEST"13,"1 FedEx parkway"15,"COLLIERVILLE"16,"TN"17,
"38017"18,"9012633035"20,"123456789"23,"1"24,"Saturday"32,"testing"38,"RTC"50,"US"69,"100"116
,"1"117,"US"183,"9012633035"440,"Y"498,""1145,"RTC"1267,"Y"1273,"1"1274,"1"1670,"100"2399,"2"
99,""
FedEx Express Priority Overnight with Direct Signature
0,"20"1,""11,"Direct Signature"12,"TEST"13,"3 FedEx parkway"15,"NEW ORLEANS"16,"LA"17,"70119"
18,"9012633035"20,"123456789"23,"1"32,"testing"38,"RTC"50,"US"69,"300"116,"1"117,"US"183,"901
2633035"498,""1145,"RTC"1273,"1"1274,"1"1670,"300"2399,"3"99,""
FedEx Express Priority Overnight with Adult Signature
0,"20"1,""11,"Adult Signature"12,"TEST"13,"2 FedEx parkway"15,"ANCHORAGE"16,"AK"17,"99501"
18,"9012633035"20,"123456789"23,"1"24,"Friday"32,"testing"38,"RTC"50,"US"69,"200"116,"1"117,"
US"183,"9012633035"498,""1145,"RTC"1266,"Y"1273,"1"1274,"1"1670,"200"2399,"4"99,""
v 10.6.1
FedEx Ship Manager® Server Developer Guide
5-45
Chapter 5: Coding Transactions for FedEx Express U.S. Service
FedEx Express Basic Streamlined Transaction
This FedEx Express transaction receives sender and other shipment information from the meter configuration in the FSMS Configuration
Utility. For this reason, the number of fields required to complete the transactions is minimal.
FedEx Express Sample
0,"020"1,"Open Shipment"11,"Test"13,"100 Main St"15,"Anywhere"18,"9012369999"16,"al"
17,"35801"23,"1"50,"US"498,"4000085"1273,"01"1274,"01"1670,"100"99,""
5-46
FedEx Ship Manager® Server Developer Guide
v 10.6.1
CHAPTER 6: CODING TRANSACTIONS FOR FEDEX
GROUND U.S. SERVICES
When selecting a ground delivery service, choose FedEx Ground® U.S. for economical delivery to U.S. business addresses and choose
FedEx Home Delivery® for delivery to U.S. residences. Both services are available throughout the 50 United States and offer day-definite
delivery based on the distance to destination.
This chapter describes how to code FedEx Ground U.S. and FedEx Home Delivery shipping transactions for FedEx Ship Manager® Server
(FSMS) in the following sections:
• About FedEx Ground U.S. Service Shipping Transactions
• Transaction Rules and Restrictions for FedEx Ground U.S.
• Coding Guidelines for FedEx Ground U.S. Transactions
• Transaction Fields for FedEx Ground U.S.
• FedEx Home Delivery Premium Service Upgrades
• Shipping Service Options for FedEx Ground U.S.
• Hazardous Materials Shipments - FedEx Ground
• FedEx Ground Tracking Numbers
• FedEx Ground Tracking Numbers
• FedEx Ground End-of-Day Reports
• FedEx Ground U.S. Transaction Samples
Note: FedEx Ground designates FedEx Home Delivery service as the carrier for residential deliveries under 70 pounds. FedEx Ship
Manager Server enforces this business rule.
About FedEx Ground U.S. Service Shipping Transactions
FedEx Ship Manager Server transactions must be formatted according to rules specified in the transaction code reference tables described
in the FedEx Ship Manager® Server Transaction Coding Reference Guide.
Use the 020/120 Global Ship Request/Reply transactions to create FedEx Ground® and FedEx Home Delivery® shipment transactions.
Use the 023/123 Global Delete Request/Reply transactions to delete FedEx Ground and FedEx Home Delivery shipments.
See the FedEx Ship Manager® Server Services and Shipping Guide for information about FedEx Ground U.S. and FedEx Home Delivery
service features and details.
Available Shipping Methods for FedEx Ground U.S.
The transaction shipping methods available for FedEx Ground U.S. packages are:
• Single Shot
• Multiple-Piece Shipment (MPS)
• Open Ship
For information about FSMS transaction shipping methods, See Chapter 2: About FedEx Ship Manager Server Transactions.
FedEx Ground U.S. Open Ship
You can use the FSMS Open Ship shipping method to ship FedEx Ground U.S. shipments.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
6-1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
For information about how to process an Open Ship shipment, See Chapter 4: FedEx Ship Manager Server Open Ship Transactions.
FedEx Ground U.S. Multiple-Piece Shipments
A multiple-piece shipment (MPS) consists of two or more packages shipped to the same recipient. To create an MPS shipment, you can use
a single transaction with multiple occurrence fields (referred to as a “single shot” transaction).
You can label the packages with the package count: for example: 1 of 3, 2 of 3, and 3 of 3. This type of labeling process is available for the
Print-As-You-Go process. For Open Ship transactions, this requires that no labels be printed prior to a CONFIRM shipment.
See Chapter 4: FedEx Ship Manager Server Open Ship Transactions for information about Print-As-You-Go.
Enabling Multiple Package Count for FedEx Ground
The appearance of the multiple package count is optional for FedEx Ground and is enabled by the Multi-Pack Piece Count checkbox in the
Meter Settings tab of the FSMS Configuration Utility. When checked, the package count appears on a FedEx Ground or FedEx Home
Delivery MPS label if the shipment was either created using a single transaction with multiple occurrence fields, or in an Open Ship
transaction (if no labels were printed prior to the CONFIRM Shipment transaction). If any label of an Open Ship transaction is printed prior to
a CONFIRM shipment, then package counts are removed because the final package total is unknown.
To disable multiple package count for FedEx Ground and FedEx Home Delivery, uncheck the Multi-Pack Piece Count checkbox, and no
package count will appear on shipping labels.
Transaction Rules and Restrictions for FedEx Ground U.S.
FedEx Ship Manager Server transaction rules are dependent on the type of FedEx service you’ve selected and the shipping rules and
options specific to that service. This topic lists the transaction rules for FedEx Ground and FedEx Home Delivery services.
FedEx Ground U.S.
The following rules apply to FedEx Ground shipping transactions:
• Use Field 1274 (Service Type) with value "92" to specify FedEx Ground U.S. service for the package or shipment.
• When shipping FedEx Ground U.S. packages, you must enter a valid shipping address for a commercial or business location within the
50 United States.
• When shipping packages to residential addresses within the U.S., use the FedEx Home Delivery service.FedEx Ground designates
FedEx Home Delivery service as the carrier for residential deliveries under 70 pounds. FedEx Ship Manager Server enforces this
business rule.
• Shipper address and Recipient address for FedEx Ground shipments must contain a U.S. city and state.
• Do not enter a USPS post office box number as an address for delivery.
• Do not include fields for Saturday delivery or pickup. This service option is not available for FedEx Ground.
• When estimating time-in-transit or ship dates, consider FedEx Ground delivery days: Monday through Friday (8 a.m. to close of business
day).
• Do not include packages over 150 lbs. (Field 1670) in a FedEx Ground U.S. shipment.
• Do not include HazMat packages over 70 lbs. (Field 1670) in a FedEx Ground U.S. shipment.
• Do not include ORM-D packages over 66 lbs. (Field 1670) in a FedEx Ground U.S. shipment.
• Do not include special accessorial Hold at Location (Field 1200) with a HazMat or ORM-D shipment.
• Do not include packages which exceed 108" in length or 165" in length plus girth (L + 2W + 2H).
• Before you ship hazardous materials, you must be certified to do so. See fedex.com for certification and training information.
• Do not include hazardous materials packages for FedEx Ground shipments to or from Alaska and Hawaii. However, non-hazardous
lithium batteries can ship to Alaska and Hawaii.
6-2
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
FedEx Home Delivery
The following rules apply to FedEx Home Delivery shipping transactions:
• Use Field 1274 (Service Type) with value "90" to specify FedEx Ground U.S. service for the package or shipment.
• Shipper and Recipient addresses must be within the 50 United States.
• Do not include packages over 70 Lbs (Field 1670) in a FedEx Home Delivery shipment.
• Package size is limited up to 108 inches; or 165 inches in combined length plus girth (L+2W+2H). (Fields 57, 58 and 59)
• Do not ship hazardous materials, except for Other Regulated Materials-Domestic (ORM-D) packages.
• Do not use a USPS post office box as either the Shipper or Recipient address.
• Follow rules and restrictions for FedEx Ground alcohol shipments.
• If you need to schedule a specific time or date for delivery, use the FedEx Home Delivery premium service upgrade options.
• Keep in mind delivery days and hours when providing additional instructions in Field 3021 or estimating delivery date and time-in-transit.
Home delivery is available on Saturday and Tuesday through Friday 9 a.m. to 8 p.m.
• You can include these service options for Home Delivery shipments:
–Delivery Signature (Field 2399)
–Proof of Delivery
–Return Shipping
Coding Guidelines for FedEx Ground U.S. Transactions
FedEx Ground shipping transactions are 020/120 Global Ship transactions that use Field 1274 (Service Type) to specify either:
• FedEx Ground — for business and commercial delivery
• FedEx Home Delivery — for residential delivery
• When you code a FedEx Ground or Home Delivery transaction, be sure to do the following:
• Use the 020 Global Ship Request transaction to request all FedEx Ground U.S. and Home Delivery shipping functions. Replies are
returned in the 120 Global Ship Reply transaction.
• Always begin each transaction with the Transaction Code Field 0 and enter the value "020" or "20". For example, 0,"020".
• Always include Field 1 (Customer Transaction Identifier) in each transaction. This field lets you link transaction “replies” back to the
transaction “requests” in those instances where you are performing multiple shipment transactions for bulk shipments.
• Always include the meter number (Field 498) of the client/device on which you are running the FSMS transactions.
• Include Field 1274 (Service Type) and select one of the following service codes:
–92 — FedEx Ground U.S. for commercial addresses
–90 — FedEx Home Delivery for residential addresses
• You must provide “Ship To” information in the transaction. Include in Field 11 (Recipient Company) the recipient name and in Field 12
(Recipient Contact Name) the contact information for the company or person to whom you are sending the shipment.
• Your “Ship From” information is entered as part of your FSMS configuration. If the “Ship From” information is different, you must include
the shipper name and contact information in the transaction.
• Always include Field 23 (Pay Type). You may prepay the shipping costs or bill them to the recipient of the shipment or a third party. You
can also send the package Collect on Delivery.
• You must specify the packaging type for your shipment; only packages prepared by the shipper are accepted. Pass Field 1273
(Packaging Type) with a value of "01".
v 10.6.1
FedEx Ship Manager® Server Developer Guide
6-3
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
• You can use the Open Ship method to ship your packages. FedEx Ground Open Ship requires that you use Field 541 (Open Ship Flags)
to specify the shipping function and use Field 542 (Open Ship Index) to identify the shipment index associated with the flagged function in
Field 541.
• Add more fields if you wish to send the package using any of the FedEx Ground special options, such as Collect on Delivery. Each option
has a special flag field.
• Always end each transaction with the End of Record Indicator Field 99. Do not enter a value in this field. The field should always look like
this: 99,""
• When adding packages to a transaction, be aware of package size and weight restrictions:
–FedEx Ground — up to 150 LBS; up to 108 inches in length and 165 inches in length and girth
–FedEx Home Delivery — up to 70 LBS; up to 108 inches in length and 165 inches in length and girth
Transaction Fields for FedEx Ground U.S.
The basic FedEx Ground shipping transaction uses the same basic fields required for FedEx Express shipment transactions. For a list of
basic shipping fields, see “020/120 Global Ship Request/Reply Transactions” in the FedEx Ship Manager® Server Transaction Coding
Reference Guide.
Several fields, however, require FedEx Ground-specific field values and are described in Table 6-1.
Table 6-1: FedEx Ground Fields
Transaction: 020 Global Ship Request - Single Piece, Single Shot, Open Ship
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Payor Account Number
20
Max=20
N
I
FDXG
All
Field Level: Shipment
REQUIRED*
Nine-digit FedEx account number of company or person to be billed for
the shipment.
*Required for FedEx Ground when you want to bill your recipient or a
third-party account number.
Max=1
N
I
FDXG
All
Field Level: Shipment
REQUIRED
Code for payment type.
FedEx Ground payment types are:
1 — Prepaid
2 — Collect (not for C.O.D.)
3 — Bill Third Party
5 — Bill Recipient
N
I
FDXG
All
Field Level: Package
REQUIRED
Available for FedEx Ground:
01 — Customer packaging
Pay Type
23
Packaging Type
1273
6-4
Max=2
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-1: FedEx Ground Fields (Continued)
Transaction: 020 Global Ship Request - Single Piece, Single Shot, Open Ship
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
Description
Service Type
1274
Max=2
FDXG
All
Field Level: Shipment
REQUIRED
Service type provided by the shipper.
FedEx Ground U.S.:
90 — FedEx Home Delivery
92 — FedEx Ground
Note: Field length of 3 is only applicable for FedEx Express Freight bill of
lading and International Ground Distribution.
Note: For FedEx SmartPost shipping, reference Field 2417 in Table 7-9
on page 7-49.
Note: Additional fields available for Ground and Home Delivery are described in the FedEx Ship Manager® Server Transaction Coding
Reference Guide.
Package Size and Weight Rules for FedEx Ground and Home Delivery
U.S.
If you are shipping a package that exceeds the size and weight restrictions as described in the service details below, FSMS returns
Field 3124 (FedEx Ground Oversize Indicator) in a 120 Global Ship Reply transaction with the appropriate oversize (OS) indicator for the
package.
FedEx Ground Oversize Rules
Table 6-2 lists the conditions used by FedEx to qualify a package as “oversize” for FedEx Ground shipping. Table 6-3 describes the returned
FedEx Ground Oversize Indicator Field 3124.
Table 6-2: FedEx Oversize Rules
FedEx Ground Oversize Package Conditions
Value
If Length Plus Girth is
OS Code Returned
Greater Than
Less Than
Less Than
1
> 84"
< 109"
< 30 Lbs
> 108"
< 131"
< 50 Lbs
> 130"
< 166"
< 150 Lbs
2
3
1
And Weight is
FedEx Home Delivery Oversize Package Conditions
1
> 84"
< 109"
< 30 Lbs
2
> 108"
< 131"
< 50 Lbs.
31
> 130"
< 166"
< 70 Lbs
1
Packages that conform to oversize rule 3 require a $30 surcharge. This surcharge is currently not supplied in your rate quote. You must add
this surcharge when the 120 Global Ship Reply transaction returns Field 3124 with a value of 3.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
6-5
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-3: FedEx Ground Indicator for Oversized Packages
Transactions: 120 Global Ship Reply - Single Piece, Single Shot, Open Ship
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Service Valid For
Description
FedEx Ground Oversize Indicator
3124
Max=1
N
O
FDXG
FDXS
US
CA
Indicates if a FedEx Ground or FedEx Home Delivery package meets an
oversize condition.
FedEx Ground package oversize values are:
1 — if length+girth is > 84" and < 109" and weight is > 30 Lbs
2 — if length+girth is > 108" and < 131" and weight is < 50 Lbs
3 — if length+girth is > 108" and < 131" and weight is < 50 Lbs
FedEx Home Delivery package oversize values are:
1 — if length+girth is > 84" and < 109" and weight is < 30 Lbs
2 — if length+girth is > 108" and < 131" and weight is < 50 Lbs
3 — if length+girth is > 130" and < 166" and weight is < 70 Lbs
If you enter dimensions or dimensional criteria that meet oversize
guidelines, FSMS sets this value automatically.
OS3 Surcharge
A $30 surcharge will be applied to packages that meet the OS 3 requirements. This surcharge is currently not supplied in the rate quote. To
apply this surcharge code to your application, add the surcharge when Field 3124 returns a value of 3 in the 120 Global Ship Reply
transaction.
Non-Standard Packaging Rules for FedEx Ground
If you ship a package that FedEx Ground has regulated as “non-standard”, you must identify the package in a 020 Global Ship Transaction
using Field 3018 (Additional Handling Surcharge).
FedEx Ship Manager Server returns the surcharge for the non-standard package in Field 3013 (Nonstandard Container Surcharge) in
the120 Global Ship Reply transaction.
A non-standard FedEx Ground package is any package that:
• Measures greater than 60 inches in length but is equal to or less than 108 inches in length
• Is not fully encased in an outer shipping container
• Is encased in an outer shipping container made of metal or wood
• Any drum or pail (less than 5 gallons) that is not fully encased in an outer shipping container made of corrugated cardboard
If your package meets any of these criteria, set Field 3018 to Y to receive the correct surcharge for your shipment. If you enter dimensions
for the package that are greater that 60" on any one container side, the Additional Handling Surcharge (Field 3018) is automatically applied
to that shipment.
6-6
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Non-Standard Container Fields for FedEx Ground
Table 6-4 lists the fields for indicating that a FedEx Ground shipment uses a non-standard container. A surcharge for use of non-standard
containers is returned in the 120 Reply Transaction.
Table 6-4: Non-Standard Container Fields for FedEx Ground
Transaction: 020/120 Global Ship Request/Reply - Single Piece, Single Shot, Open Ship
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Nonstandard Container Surcharge
3013
Max=11.2 N
O
FDXG
All
Returns the surcharge applied to a FedEx Ground package with a nonstandard container.
Two implied decimal places.
FDXG
All
Field Level: Package
Optional
Indicates nonstandard packaging is used.
Nonstandard packaging is a container that meets one of these criteria:
• Greater than 60" on any one side (not to exceed 108")
• Not fully enclosed/encased in an outer shipping container
• Encased in an outer container made of metal, wood, hard plastic or
foamed material
Valid values are:
Y — nonstandard packaging used
N — standard packaging used (default)
If you enter dimensions or dimensional criteria that are nonstandard,
FSMS sets this flag to Y automatically.
Additional Handling Surcharge
3018
v 10.6.1
Max=3
N
I
FedEx Ship Manager® Server Developer Guide
6-7
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Additional Form and Label Information
If you need to display additional information for your shipment on the shipping label or the FedEx invoice, you may add the 020 Global Ship
Request transaction fields described in Table 6-5 to your shipping transaction.
Table 6-5: Additional Reference Information Fields
Transaction: 020/120 Global Ship Request/Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Reference Information
25-#
Max=39
A
I
FDXG
All
Field Level: Package for all FedEx Ground services
Optional
Use this field for customer reference number CRN (FedEx Ground).
This field is a package-level field and must not be used if a shipment-level
customer reference number (CRN) has been assigned in Field 3003
(Shipment Customer Reference Information).
If this field is used simultaneously with Field 3003, then Field 3003 is
ignored. Package-level fields take precedence.
This value prints on the Customer Reference field on the FedEx Ground
invoice.
FDXG
US
Returned FedEx tracking number for a FedEx Collect on Delivery
(C.O.D.) package.
Output data returned in 120 Global Ship Reply transaction.
Prints on the shipping label.
I
FDXG
All
Field Level: Shipment
Optional
Specifies the purchase order number for the shipment.
Use Field 3001 to print the purchase order number on a Returns label.
Use only for shipments of two or more packages to the same
recipient.This value prints on the thermal label.
This field can be used in the same transaction with other shipment level
reference number Fields: 3002 (Shipment Invoice Number) and 3003
(Shipment Customer Reference Information).
I
FDXG
All
Field Level: Shipment
Optional
Specifies the invoice number of the shipment.
Use Field 3002 to print the invoice number on a Returns label. Use only
for shipments of two or more packages to the same recipient.This value
prints on the thermal label.
This field can be used in the same transaction with other shipment level
reference number Fields: 3001 (Shipment Purchase Order Number) and
3003 (Shipment Customer Reference Information).
C.O.D. Return Tracking Number
28
Max=15
N
I/O
Shipment Purchase Order Number
3001
Max=30
A
Shipment Invoice Number
3002
6-8
Max=30
A
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-5: Additional Reference Information Fields (Continued)
Transaction: 020/120 Global Ship Request/Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Package Purchase Order Number
3056
Max=30
AKE
I
FDXG
All
Field Level: Package
Optional
When used to create/print a bill of lading (BOL), this prints in the
Purchase Order # section of the BOL. Each additional BOL order number
prints directly below each article description. Field 3056 is the only field
that supplies the full set for the BOL.
For Domestic FedEx Ground and International, this field prints the
package purchase order number to a thermal label.
Note: This field is a package level field and should not be used if a
shipment level purchase order number has been assigned in Field 3001
(Shipment Purchase Order Number). If this field is used simultaneously
with Field 3001, then Field 3001 is ignored. Package level fields take
precedence.
I
FDXG
All
Field Level: Package
Optional
Prints the package invoice number on the thermal label.
Field 3057 is a package level field and must not be used if a shipment
level invoice number has been assigned in Field 3002 (Shipment Invoice
Number). If this field is used simultaneously with Field 3002, then
Field 3002 is ignored. Package level fields take precedence.
Package Invoice Number
3057
Max=30
A
Note: You can also configure these fields to print on the thermal label doc-tab. See Chapter 3: FedEx Ship Manager Server Label and Form
Transactions.
Deleting a FedEx Ground Shipment
Use the 023 Global Delete Request transaction to delete a single piece or all pieces in a FedEx Ground U.S. domestic (including C.O.D.)
multiple-piece shipment (MPS).
Note: If you enter a tracking number associated with a multiple-piece shipment, FSMS deletes all pieces in this shipment.
FedEx Home Delivery Premium Service Upgrades
You can use FedEx Home Delivery to ship packages to residential addresses within the 50 United States.
Use the required FedEx Ground transaction fields (see Table 6-1) to create the base transaction for FedEx Home Delivery shipments. To
specify FedEx Home Delivery, enter the code "90" for the Home Delivery service type in Field 1274 (Service Type), for example,
1274,"90". See “FedEx Home Delivery Service” on page 6-11.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
6-9
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Home Delivery Service Upgrades
Customize delivery to suit your recipient by choosing from three premium service upgrades.
• FedEx Date Certain Home Delivery
• FedEx Evening Home Delivery
• FedEx Appointment Home Delivery
Use Field 3020 (FedEx Home Delivery Type) to select the upgrade. Valid values for this field are:
1 — FedEx Date Certain Home Delivery®
Select this service option if you want to specify a delivery date for home delivery. For example, if your recipient is available to accept
packages on Thursdays, enter Thursday in Field 3023 (FedEx Home Delivery Date) as the delivery date in your shipping transaction.
2 — FedEx Evening Home Delivery®
Select this service option to specify delivery between 5 p.m. and 8 p.m., based on the recipient’s local time zone.
3 — FedEx Appointment Home Delivery®
Select this service option if you need to specify an appointment for delivery. The recipient is contacted by their local FedEx Home
Delivery terminal to set up the delivery appointment.
FedEx Home Delivery Fields
Table 6-6 describes optional fields that you may want to include in the 020 Global Ship Request transaction for FedEx Home Delivery
shipments.
Table 6-6: FedEx Home Delivery Fields
Transaction: 020 Global Ship Request - Single Piece, Single Shot, Open Ship
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Signature Required Type
2399
6-10
Max=1
N
I
FDXE
FDXG
FHD
US
Field Level: Package
Indicates type of signature service for delivery.
Valid values:
0 — Not Present
1 — Deliver without Signature
2 — Indirect Signature
3 — Direct Signature
4 — Adult Signature
• 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 Ground 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 residential U.S. domestic FedEx Ground shipments are
handled as Deliver without Signature. 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.
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-6: FedEx Home Delivery Fields (Continued)
Transaction: 020 Global Ship Request - Single Piece, Single Shot, Open Ship
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
FedEx Home Delivery Type
3020
Max=1
N
I
FHD
US
Field Level: Shipment
Optional
Type of FedEx Home Delivery service.
Valid values:
1 — Date Certain
2 — Evening
3 — Appointment
Valid days are Tuesday through Saturday.
Special Instructions/FedEx Home Delivery Instructions
3021
Max=74
A
I
FHD
US
Field Level: Shipment
Optional
Specify specific delivery instructions.
I
FHD
US
Field Level: Shipment
REQUIRED* or Optional
Date the delivery is to be made.
*Required if Field 3020 (FedEx Home Delivery Type) is set to 1.
Optional if Field 3020 (FedEx Home Delivery Type) is set to 2 or 3.
Format: CCYYMMDD.
Valid days are Monday through Saturday.
FHD
US
Field Level: Shipment
REQUIRED* or Optional
Phone number used to contact the recipient to arrange a time for delivery.
*Required if Field 3020 (FedEx Home Delivery Type) is set to 1 or 3.
Optional if Field 3020 (FedEx Home Delivery Type) is set to 2.
FedEx Home Delivery Date
3023
Max=8
N
FedEx Home Delivery Phone Number
3024
Max=15
A
I
FedEx Home Delivery Service
FedEx Home Delivery service delivers packages to every residential address in the 50 United States using the FedEx residential-only
delivery network. To specify a Home Delivery shipment, enter the Home Delivery service type code in Field 1274.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
6-11
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-7: Service Type for Home Delivery
Transactions: 020/120 Global Ship Request/Reply, 025/125 Rate Available Services Request/Reply - Single Piece, Single Shot, Open Ship
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Service Type
1274
Max=2
Description
Transactions: 020/120 Global Ship Request/Reply, 025/125 Rate Available Services Request/Reply
N
I/O
FHD
US
Field Level: Shipment
REQUIRED.
Service type provided by the shipper.
FedEx Ground U.S.:
90 — FedEx Home Delivery
Note: For FedEx SmartPost shipping, reference Field 2417 in Table 7-9
on page 7-49.
Shipping Service Options for FedEx Ground U.S.
FedEx Ground U.S. provides the special shipping services described in this section. They include:
• FedEx Ground Collect on Delivery Services
• FedEx Ground Future Day
• FedEx Delivery Signature Services - FedEx Ground
• Saturday Pickup and Delivery Fields - FedEx Home Delivery
• Customized Time in Transit Field
• FedEx Ground Multi-weight Pricing (U.S.)
• Hazardous Materials Shipments - FedEx Ground
FedEx Ground Collect on Delivery Services
FedEx Ground U.S. domestic shipments offer collect on delivery options with features designed to meet your unique shipping needs:
• FedEx Ground® C.O.D. — provides three payment collection options for FedEx Ground shipments.
• FedEx Ground® Electronic C.O.D. (E.C.O.D.) — provides direct deposit of collect-on-delivery payments for FedEx Ground shipments.
FedEx Home Delivery C.O.D. and E.C.O.D. are not available for international FedEx Ground shipments.
You can use FSMS to ship either C.O.D. or E.C.O.D., but you cannot use both services simultaneously under the same meter number.
FedEx Ground C.O.D.
Use the FedEx Ground C.O.D. service option to designate the amount of money that the FedEx Ground contractor collects from the
recipient upon shipment delivery. If the FedEx Ground contractor collects guaranteed funds, or a company/personal check, the payment is
sent directly to the shipper via U.S. mail. If cash is collected, on the next business day FedEx Ground delivers a check to the shipper in the
amount of the cash collected. The FedEx issued check is sent to the shipper via U.S. mail. The shipper must designate the type of payment
to be collected by FedEx Ground.
6-12
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
FedEx Ground C.O.D. can be used with the following service options:
• FedEx® Delivery Signature Options
• Prepaid or third party billing only
• Declared Value
• Hazardous Materials
• Residential Surcharge
• Additional Handling
FedEx Ground E.C.O.D.
Use the FedEx Ground E.C.O.D. service option to receive funds within 24 to 48 hours after shipment delivery. Shippers receive monies via
electronic funds transfer. Contact your FedEx Account Executive for more information about E.C.O.D.
E.C.O.D. is not available for FedEx Home Delivery service.
• Available services with FedEx Ground E.C.O.D.:
• Signature Services
• Prepaid or third party billing only
• Declared Value
• Hazardous Materials
• Residential Surcharge
• Additional Handling
C.O.D. and E.C.O.D. Labels
Shipping a FedEx Ground E.C.O.D. package requires three thermal labels. Label 1 must be affixed to the outside shipping container. Labels
2 and 3 must be placed in a FedEx Ground C.O.D. pouch (OP-013 POUCH) and affixed to the outside shipping container.
For more information about using the FedEx Ground E.C.O.D. service, contact your FedEx account executive.
Transaction Fields for FedEx Ground Collect on Delivery
Table 6-8 lists the fields — required and optional — available for coding information about your FedEx Ground Collect on Delivery
transaction.
Table 6-8: Fields for FedEx Ground U.S. C.O.D.
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Recipient Contact Name
12
v 10.6.1
Max=35
A
I
FDXG
US
Field Level: Shipment
REQUIRED*
Contact name at the Recipient company.
*Required if a recipient company is not provided.
*Required for all C.O.D. (U.S. domestic service only), alcohol, bill
recipient, and bill third party.
FedEx Ship Manager® Server Developer Guide
6-13
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-8: Fields for FedEx Ground U.S. C.O.D. (Continued)
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I
FDXG
US
Field Level: Package level for FedEx Ground
REQUIRED*
When set to Y, indicates that a package or shipment is being shipped
FedEx Collect on Delivery (C.O.D.), and “C.O.D.” prints in the box beside
the recipient name on the bill of lading. Multiple-occurrence field.
*Required for C.O.D.
Valid values are:
Y — Package is C.O.D. at the package level for FedEx Ground.
N — Package is NOT sent C.O.D. (default)
S — Package is sent C.O.D. at the shipment level for FedEx Ground.
I
FDXG
US
Field Level: Package level for FedEx Ground
REQUIRED.
Amount of payment that must be collected upon delivery of the FedEx
Collect on Delivery (C.O.D.) package.
Maximum of $25,000 for FedEx Ground if guaranteed funds and
maximum of $750 if cash.
Multiple-occurrence field.
I
FDXG
US
CA
Field Level: Shipment
Optional
Indicates whether freight charges are added to an intra-U.S. or intra-CA
C.O.D. shipment and if so, the type of charge.
Valid values are:
Y — Add discounted net charge
N — No additional charges added to the C.O.D. amount (default)
1 — Add discounted net charge (same as Y)
2 — Add list net charge
3 — Add discounted C.O.D. charge
4 — Add list C.O.D. surcharge
5 — Add discounted Customer Total Charge
6 — Add list Customer Total Charge
I
FDXG
US
Field Level: Shipment
Optional
Telephone number for return of the FedEx Collect on Delivery (C.O.D.)
package.
Default is configured in FSMS Configuration Utility.
Description
C.O.D. Flag
27-#
Max=1
C.O.D. Collect Amount
53-#
Max=10.2 N
C.O.D. Add Freight Charges Flag
186
Max=1
A
C.O.D. Return Phone Number
1237
6-14
Max=10
A
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-8: Fields for FedEx Ground U.S. C.O.D. (Continued)
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
C.O.D. Return Company Name
1238
Max=35
A
I
FDXG
US
Field Level: Shipment
Optional
Name of company for return of the FedEx Collect on Delivery (C.O.D.)
package.
Default is configured in FSMS Configuration Utility.
I
FDXG
US
Field Level: Shipment
REQUIRED*
Required if Field 6103 (C.O.D. Remit Payor)=3.
C.O.D. Return Address Line 1
1240
Max=35
A
First line of the return address for the FedEx® Collect on Delivery
(C.O.D.) package.
*Required for Bill of Lading if Field 6103 (C.O.D. Remit Payor) is 3.
C.O.D. Return Address Line 2
1241
Max=35
A
I
FDXG
US
Field Level: Shipment
Optional
Second line of return address for the FedEx Collect on Delivery (C.O.D.)
package.
Default is configured in FSMS Configuration Utility.
A
I
FDXG
US
Field Level: Shipment
REQUIRED*
* Required if Field 6103 (C.O.D. Remit Payor) is set to 3.
City of the return address for the FedEx Collect on Delivery (C.O.D.)
package.
Default is configured in FSMS Configuration Utility.
A
I
FDXG
US
Field Level: Shipment
REQUIRED*
*Required if Field 6103 (C.O.D. Remit Payor) is set to 3.
State code of the return address for the FedEx Collect on Delivery
(C.O.D.) package.
Default is configured in FSMS Configuration Utility.
C.O.D. Return City
1242
Max=35
C.O.D. Return State
1243
Max=2
See Appendix C in the FedEx Ship Manager® Server Transaction Coding
Reference Guide for a list of state codes.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
6-15
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-8: Fields for FedEx Ground U.S. C.O.D. (Continued)
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
C.O.D. Return Postal Code
1244
Max=10
A
I
FDXG
US
Field Level: Shipment
REQUIRED*
*Required if Field 6103 (C.O.D. Remit Payor) is set to 3.
Postal code of the return address for the FedEx Collect on Delivery
(C.O.D.) package.
Default is configured in FSMS Configuration Utility.
Accumulate Shipment Charges Indicator
1593
Max=2
A
I
FDXG
US
Optional
Indicates if all charges are added to the FedEx Collect on Delivery
(C.O.D.) amount of the final or only C.O.D. package in shipment.
Valid value is:
Y — All freight charges, surcharges and handling charges are added to
the C.O.D. amount
Note: Valid for intra-U.S. and intra-Canada only.
N
I
FDXG
US
Field Level: Shipment
REQUIRED*
*Required for FedEx Ground C.O.D./E.C.O.D. shipments.
*Required if the C.O.D. Flag (Field 27) is set to Y.
Valid values are:
1 — Any Payment
2 — Guaranteed Funds
3 — Currency (maximum Cash amount is $750)
A
I
FDXG
US
Field Level: Package.
REQUIRED*
When set to Y, indicates that a package is being shipped Electronic
Collect on Delivery (E.C.O.D.). Multiple-occurrence field.
*Required for Electronic Collect on Delivery service for FedEx Ground.
Valid values are:
N — Package is NOT sent E.C.O.D. (default)
Y — Package is sent E.C.O.D. at the shipment level for FedEx Express
and at the package level for FedEx Ground.
S — Package is sent E.C.O.D. at the shipment level for FedEx Ground.
Note: FSMS defaults to C.O.D. To enable E.C.O.D. you must check the
E.C.O.D. checkbox on the Meter Settings tab of the FSMS Configuration
Utility.
C.O.D. Collection Type
3000
Max=2
E.C.O.D. Flag
3014-#
6-16
Max=1
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Fields for FedEx Ground C.O.D. and E.C.O.D. Transactions
Configure how FedEx Collect on Delivery (C.O.D.) and Electronic Collect on Delivery (E.C.O.D.) charges are assessed through the 020
Global Ship Request transaction. Use the fields described in Table 6-9 to code C.O.D. and E.C.O.D. shipments for FedEx Ground service.
Table 6-9: FedEx Ground C.O.D. and E.C.O.D. Field
Transaction: 020 Global Ship Request - Single Shot, Open Ship
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I
Description
C.O.D. Flag
27
Max=1
FDXG
US
Field Level: Package level for FedEx Ground
REQUIRED*
When set to Y, indicates that a package or shipment is being shipped
FedEx Collect on Delivery (C.O.D.), and “C.O.D.” prints in the box beside
the recipient name on the bill of lading. Multiple-occurrence field.
*Required for C.O.D.
Valid values are:
Y — Package is C.O.D. at the package level for FedEx Ground.
N — Package is NOT sent C.O.D. (default)
S — Package is sent C.O.D. at the shipment level for FedEx Ground.
FDXG
US
CA
Field Level: Shipment
Optional
Indicates whether freight charges are added to an intra-U.S. or intra-CA
C.O.D. shipment and if so, the type of charge.
Valid values are:
Y — Add discounted net charge
N — No additional charges added to the C.O.D. amount (default)
1 — Add discounted net charge (same as Y)
2 — Add list net charge
3 — Add discounted C.O.D. charge
4 — Add list C.O.D. surcharge
5 — Add discounted Customer Total Charge
6 — Add list Customer Total Charge
FDXG
US
Total cost for C.O.D. shipping when adding package freight charges to
the C.O.D. remit amount.
Prints on the C.O.D. shipping label.
US
CA
Optional
Indicates if all charges are added to the FedEx Collect on Delivery
(C.O.D.) amount of the final or only C.O.D. package in shipment.
Valid value is:
Y — All freight charges, surcharges, and handling charges are added to
the C.O.D. amount
Note: Valid for intra-U.S. and intra-Canada only.
C.O.D. Add Freight Charges Flag
186
Max=1
N
I
Freight + Remit C.O.D. Charges
543
Max=11.2 N
I
Accumulate Shipment Charges Indicator
1593
v 10.6.1
Max=1
A
I
FDXG
FedEx Ship Manager® Server Developer Guide
6-17
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-9: FedEx Ground C.O.D. and E.C.O.D. Field (Continued)
Transaction: 020 Global Ship Request - Single Shot, Open Ship
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
C.O.D. Collection Type
3000
Max=2
N
I
FDXG
US
Field Level: Shipment
REQUIRED*
*Required for FedEx Ground C.O.D./E.C.O.D. shipments.
*Required if the C.O.D. Flag (Field 27) is set to Y.
Valid values are:
1 — Any Payment
2 — Guaranteed Funds
3 — Currency (maximum Cash amount is $750)
A
I
FDXG
US
Field Level: Package.
REQUIRED*
When set to Y, indicates that a package is being shipped Electronic
Collect on Delivery (E.C.O.D.). Multiple-occurrence field.
*Required for Electronic Collect on Delivery service for FedEx Ground.
Valid values are:
N — Package is NOT sent E.C.O.D. (default)
Y — Package is sent E.C.O.D. at the shipment level for FedEx Express
and at the package level for FedEx Ground.
S — Package is sent E.C.O.D. at the shipment level for FedEx Ground.
Note: FSMS defaults to C.O.D. To enable E.C.O.D. you must check the
E.C.O.D. checkbox on the Meter Settings tab of the FSMS Configuration
Utility.
E.C.O.D. Flag
3014-#
Max = 1
FedEx Ground Future Day
Use Future Day shipping to prepare a FedEx Ground shipment up to ninety (90) days from the actual ship date. A label prints when the
shipment is processed, but the shipment can be held until the specified day becomes current before tendering the package to the courier.
To specify a Future Day shipment, include Field 24 (Ship Date) in the 020 Global Ship Request transaction with the specified shipping date.
Table 6-10 describes Field 24.
Note: FedEx Ground does not ship on Saturday. Only FedEx Home Delivery supports Saturday pickup and delivery service.
6-18
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-10: Future Day Ship Date Field
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Ship Date
24
Max=8
Description
Transactions: 107 End-of-Day Close Reply, 020 Global Ship Request, 024 Shipment Query Request
N
I
FDXG
All
Field Level: Shipment
REQUIRED*
Date of shipment.
*Required for Future Day shipping. Format: CCYYMMDD
Default: Current meter date.
For example, July 1, 2005 is coded as: 20050701
FedEx Ground and FedEx Home Delivery ship dates can be set up to 90
days in advance, and the ship date can be set to unlimited using the
Extend 90 Day limit — FedEx Ground checkbox in the Systems Settings
tab of the FSMS Configuration Utility.
Deleting a Future Day Shipment
You can delete a Future Day shipment before the shipping day is closed using the 023/123 Global Delete Request/Reply transaction. This
deletes the future ship date from the FSMS shipment history database on the local FSMS client. These shipments are not uploaded to
FedEx.
However, after you close your shipping day, Future Day shipments are uploaded to FedEx and kept in a reserve file. Therefore, a 023 Global
Delete Request transaction must be uploaded to FedEx to cancel Future Day shipments after Close.
FedEx Delivery Signature Services - FedEx Ground
Signature Services are available for FedEx Ground and FedEx Home Delivery using the 020 Global Ship Request transaction with
Field 2399 (Signature Required Type).
FedEx Delivery Signature Options Restrictions - FedEx Ground
Signature options are supported for all FedEx Ground U.S. domestic package services.
The following rules and restrictions apply to 020 Global Ship Request transactions for FedEx Ground and FedEx Home Delivery service
(Field 1274 Service Type set to 92 or 90):
• If you are an international customer and are shipping a package to a U.S. recipient, you must include a delivery signature option
(Field 2399 Signature Required Type) for your shipment.
• If you include Field 1332 (Alcohol Flag) to indicate an alcohol shipment, always include the required Adult signature field (2399,"4").
• No signature option is allowed for Hold at FedEx location shipments.
• C.O.D., HazMat, FedEx Home Delivery with Appointment Delivery, and shipments with an insurance value greater than $499 USD
require a direct signature (2399,"3") and a surcharge is not applied. However, if you upgrade to the adult signature option
(2399,"4"), a surcharge will be applied. Indirect signature and delivery without a signature are not available options for these types of
shipments.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
6-19
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Saturday Pickup and Delivery Fields - FedEx Home Delivery
Saturday service is available for FedEx Home Delivery. FedEx Ground does support Saturday pickup and delivery service.
When coding for Saturday service, use Field 24 (Ship Date), Field 1266 (Saturday Delivery Flag), and Field 1267 (Saturday Pickup Flag) as
described in Table 6-11.
Table 6-11: Home Delivery Saturday Pickup and Delivery Fields
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
Description
Ship Date
24
Max=8
FDXG
FHD
All
Field Level: Shipment
REQUIRED*
Date of shipment.
*Required for Future Day shipping. Format: CCYYMMDD
Default: Current meter date.
For example, July 1, 2005 is coded as: 20050701
Customized Time in Transit Field
The Customized Time in Transit (Field 2703) returns the number of days a package will spend in transit. You must enable the Ground
Custom Transit Time option in the FSMS Configuration Utility to receive Field 2703 in the 120 Global Ship Reply transaction.
Table 6-12 describes Field 2703 (Customized Time in Transit).
Table 6-12: Custom Transit Time Field
Transactions: 120 Global Ship Reply ─ Single Piece, Single Shot MPS, Open Ship MPS, OpenShip Rate/Route
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Customized Time in Transit
2703
Min=0
Max=2
N
Description
Transactions: 120 Global Ship Reply
I
FDXG
All
Field Level: Shipment
Output.
Number of days a FedEx Ground or FedEx Home Delivery package will
spend in transit from the origin to the destination when the customer has
customized transit times. 120 Global Ship Reply transaction returns a
customized transit time.
Requires that the Custom Transit Time Indicator checkbox in the Meter
Settings tab of the FSMS Configuration Utility is checked.
You can include this field in these types of transactions: single piece,
single shot MPS, Open Ship MPS, and Open Ship RATE and ROUTE.
To configure Custom Transit Time
1.
Open the FSMS Configuration Utility.
2.
Click the Meter Settings tab.
6-20
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
3.
In the Ground Options section, check the Custom Transit Data Key checkbox and type the custom transit data key (0-10 characters)
in the textbox.
4.
Check the Custom Transit Exclusion File checkbox to indicate that a zip/postal exclusion file is used when providing customized
transit times to the shipper.
5.
Type or browse to the directory path and file name of the exclusion file.
6.
Click Apply or Apply&Exit.
U.S. or Canada shippers who set up customized FedEx Ground transit times are responsible for meeting all terms and conditions of their
agreement with FedEx related to getting the customized transit time. These conditions include any factors external to FSMS including, but
not limited to, cut-off times, volume requirements and sorting requirements. FedEx Ship Manager Server quotes customized transit times
when specified but cannot consider these external factors when providing the customized transit time.
FedEx Ground Multi-weight Pricing (U.S.)
FedEx Ground Multi-weight pricing is ideal for multiple-package shipments weighing 200 LBS or more moving as one unit to the same
destination on the same day. This pricing option allows you to combine packages for a Multi-weight rate.
Pricing
The FedEx Ground Multi-weight pricing option allows you to combine packages for a Multi-weight rate. Pricing is based on the combined
weight of your packages.
Note: FedEx Ground Multi-weight shipment rates are available by contract only. Contact your FedEx account executive for more information.
FedEx Ground multiple-piece shipments may receive per-pound rates if the total shipment weighs 200 LBS or more. A shipment average
minimum package weight applies and varies by contract.
Transaction Rules for Multi-weight
Use the base transaction fields for a FedEx Ground shipment (see Table 6-1: FedEx Ground Fields, on page 6-4) when coding a FedEx
Ground Multi-weight 020/120 Global Ship transaction.
• FedEx Ground Multi-weight transactions must include multiple packages which follow the restrictions described below.
• Be sure the total weight of your multiple-package shipment is 200 pounds or more to qualify for Multi-weight pricing and optimal service.
• Average package weight should be between 15-25 pounds.
• For single packages, do not enter more than 150 lbs for the package weight or 108" in length plus girth for the package dimensions.
• Restrict delivery days to Monday through Friday when specifying delivery dates for packages.
Delivery Details Report for Multi-weight
FedEx shippers can configure a Delivery Details Report to be generated when they perform an End-of-Day Close for FedEx Ground Multiweight shipment(s). The report includes the date of shipment, company name, consignee name and address, original and destination postal
codes, service, and pickup, account and system numbers. The report also prints the total package count. You can print the report in these
formats: RTF, TXT, DOC and PDF.
To configure the FedEx Ground Multi-weight Delivery Details Report
1.
Open the FSMS Configuration Utility.
2.
Click the Report Settings tab.
3.
In the list of reports on the left, click the + (plus) indicator next to Ground to expand the report list.
4.
Click MWGT Delivery Detail to select this report.
5.
Click Apply or Apply&Exit.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
6-21
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
To print the Delivery Details Report
You can print a Delivery Details Report at End-of-Day Close for Ground Multi-weight shipments by specifying the "063" Delivery Details
report code in Field 1373 (Report Code); example: 1373,"063".
Table 6-13: Ground Multi-weight Delivery Details Report Field
Transactions: 007/107 End-of-Day Close Request/Reply
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Report Code
1373
Max=3
Description
Transactions: 020 Global Ship Request, 070 Meter Query Configuration
Request, 095 Label Reprint Request
N
O
FDXG
US
Optional
Specify the "063" report code in Field 1373 to print the Ground
Multiweight Delivery Details report in a 007 End-of-Day Close Request
transaction.
Note: Configure each report you want to print at end of day in the FSMS
Configuration Utility.
Hazardous Materials Shipments - FedEx Ground
FedEx Ship Manager Server supports FedEx Ground shipping of hazardous materials (HazMat) under the Code of Federal Regulations
(CFR) 49,Transportation. Shipments that are intra-U.S. or to or from U.S. territories can be shipped under Other Regulated Materials-D
(ORM-D) regulations.
Hazardous Materials are substances regulated by the U.S. Department of Transportation (DOT). The U.S. DOT classifies hazardous
materials into nine classes. For more information on which substances can be shipped with FedEx, go to fedex.com/hazmat and click on
“Hazardous materials (FedEx Ground).
When shipping hazardous materials with FedEx Ground, a hazardous materials shipping form and a hazardous materials certification report
(OP-950) must be included along with adherence to specific requirements for marking, labeling and packaging.
HazMat shipments can contain up to three HazMat commodities per package (tracking number), depending upon the forms used.
General Shipping Information for all Hazardous Materials
HazMat Commodity Package Mixtures
Different Hazardous Materials commodities may be packaged together in a shipment. But the shipping rules vary depending upon the
commodities contained in the package. Not all commodities may be mixed within a package. Packages are classified as one of the following
types based upon their contents, and prioritized in the following order.
• True HazMat
• ORM-D
• Dry Ice
• Small Quantity Exception
• Non-Hazardous Lithium Battery Package
6-22
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-14: HazMat Package Hierarchy and Allowable Commodity Mixes
Package Type Hierarchy
HAZ
ORM-D
Dry Ice
Small Quantity
Exception
Non Hazardous
Lithium Battery
HazMat Package
Yes
No
Yes
No
Yes
ORM-D Package
No
Yes
Yes
No
Yes
Dry Ice Package
Yes
Yes
Yes
Yes
Yes
Small Quantity Exception Package
No
No
Yes
Yes
Yes
Non Hazardous Lithium Battery Package
Yes
Yes
Yes
Yes
Yes
The commodity which is higher in the hierarchy determines the package type and also determines the business rules and edits which are
applied to the package/shipment. For instance, a package containing Dry Ice and a Non-Hazardous Lithium Battery will follow the business
rules and edits pertaining to Dry Ice.
UN ID Number Validations
A UN ID table and Segregation Loading Chart are provided for automated validation of HazMat information when shipping a HazMat
shipment. Both tables can be manually downloaded by selecting the existing “Shipping Tables” checkbox option located on the Demand
Download Utility. This data is downloaded for the Master Meter and used for all enabled meters on the FedEx Ship Manager Server
system. System-level data is only available for the Master Meter via download.
In addition, you may find the HazMat Shipping Tables on the web at http://images.fedex.com/us/services/pdf/
HazmatShippingTable.pdf.
Hazardous Materials Labels, Forms, and Shipping Documents
See Table 6-15 for the fields which can be used in a HazMat Ground shipment.
Table 6-15: HazMat Shipping Fields for Ground
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
Description
Dangerous Goods Technical Name
446-#
Min=1
A/N
Max=255
I
FDXG
US
Field Level: Shipment
REQUIRED*
Technical name of the hazardous materials (HazMat) or dangerous
goods (DG) being shipped.
*Required if the proper shipping name ends in ' * ' in the International Air
Transport Association (IATA) Dangerous Goods (DG) Regulations
manual. Otherwise, the field is optional and not required for shipping.
*Not required if DG class is radioactive.
*Required if a customer attempts to ship a Ground HazMat shipment,
Field 1274 is set to 92, Field 1331 is set to Y with a valid UN ID number
in Field 451 that contains the symbol G (i.e. UN3098),
Note: Maximum of five (5) field occurrences is allowed.
See Section 4.1.2 of the IATA DG Regulations.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
6-23
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-15: HazMat Shipping Fields for Ground (Continued)
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
Description
Dangerous Goods Technical Name
446-#
(cont.)
Min=1
A/N
Max=255
I
FDXG
US
For U.S. dangerous goods shipments, use this field in a Single Shot or
Open Ship transaction. For international dangerous goods shipments,
use this field in a Single Piece transaction only. For hazardous materials
shipments, use only in Single Piece transactions.
Dangerous Goods UN Number/Identification Number
451
Max=4
N
I
FDXG
US
Field Level: Package
REQUIRED*
UN number of the dangerous goods or hazardous materials shipment.
*Required for hazardous materials shipment if Field 1493 (DG/HazMat
Form Print Flag) is set to Y and printing the FedEx Ground Hazardous
Materials Shipping Paper, OP-900.
See Column 4 of the HazMat table in the FedEx Ground Shipping
Hazardous Materials Guide.
For hazardous materials shipments, use this field only in Single Piece
transactions.
FDXG
US
Field Level: Shipment
REQUIRED*
Specify the net quantity of the hazardous materials shipment being
shipped. Use in conjunction with Field 471 to specify the unit of measure.
For a hazardous materials shipment, only use the Single Piece
transaction.
Dangerous Goods/HazMat Quantity
466
Max=6.2
N
I
Dangerous Goods/HazMat Unit of Measure (UOM)
471
Max=4
A
I
FDXG
US
Field Level: Shipment
REQUIRED
Specify the unit of measure of the dangerous goods (DG) quantity (Field
466). Must match the selected DG per the IATA DG Regulations.; for
example, ml, L, g, kg, kg G.
For hazardous materials shipments, use only in Single Piece
transactions.
US
Field Level: Shipment
REQUIRED*
Specify the emergency telephone number to be contacted for the
shipment unless the packing instruction has a Y prefix or has one of the
following UN #’s: 1845, 2807, 2857, 2969, 3166, 3171, 3358, 8000. For
hazardous materials shipments, use only in Single Piece transactions.
If a customer attempts to ship a Ground HazMat shipment, Field 1274 set
to 92, Field 1331 set to Y with a valid UN ID number in Field 451, but does
not pass in Field 484 (Emergency Contact Number), the customer
receives error message 3001, “The Emergency Phone Number is
required,” and the transaction fails.
Dangerous Goods Emergency Phone Number
484
6-24
Max=15
A
I
FDXG
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-15: HazMat Shipping Fields for Ground (Continued)
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
Description
Dangerous Goods/HazMat Packing Group
489
Max=3
A
I
FDXG
US
Field Level: Shipment
REQUIRED*
Specify the appropriate packing group for the hazardous material being
shipped.
*Required if 1493 (DG/HazMat Form Print Flag) is set to Y and you are
printing the FedEx Ground Hazardous Materials Shipping Paper, OP900.
*Required if a customer sends in a ship request when the UN ID has
multiple entries (i.e. UN ID 1263, paint). Error message 3034, “The
Packing Group is required,” is displayed.
Valid values are:
I — Packing Group I
II — Packing Group II
III — Packing Group III
This field can be entered as one blank (spacebar) for dangerous goods
that do not have a packing group. Entries must be made as Roman
Numerals.
For a hazardous materials shipment, only use the Single Piece
transaction.
Dangerous Goods Class/DOT Hazard Class or Division Number
492
Max=5
A
I
FDXG
Dry Ice Flag
1268
v 10.6.1
Max=1
US
REQUIRED*
Government classification of the dangerous goods (DG) item. This class/
division determines whether the DG is categorized as accessible or
inaccessible by FedEx Express.
*Required if Field 1493 (DG/HazMat Form Print Flag) is set to Y and
printing the FedEx Ground Hazardous Materials Shipping Paper, OP900.
*Required if Field 451 (Dangerous Goods UN Number/Identification
Number) has multiple names (i.e. UN1263, Paint). If customer sends in a
HazMat ship request without Field 492, and Field 1331 is set to Y, and the
UN ID has multiple names, error message 0799 is returned, “The
Dangerous Goods Class cannot be left blank,” and the transaction fails.
See the FedEx Service Guide for more details.
For hazardous material shipments, use this field only in Single Piece
transactions.
Transactions: 020 Global Ship Request
A
I
FDXE
FDXG
FHD
REQUIRED*
Indicates whether the shipment contains dry ice.
*Required if shipment contains dry ice.
Valid values are:
Y — Shipment contains dry ice
N — Shipment does not contain dry ice
FedEx Ship Manager® Server Developer Guide
6-25
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-15: HazMat Shipping Fields for Ground (Continued)
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
Description
Dangerous Goods/HazMat Flag
1331
Max=1
A
I
FDXG
US
Field Level: Shipment
REQUIRED*
Indicates hazardous materials (HazMat) are contained in the shipment.
*Required if shipping HazMat.
Set to Q to indicate shipment contains EPRRQ commodity.
Valid values are:
N — Shipment contains no HazMat
Note: Values are not case-sensitive; “Q” and “q” both indicate EPRRQ.
Note: This field must equal ‘N’ when shipping a FedEx Ground ORM-D
shipment, and have designated Field 1900 as ‘O’.
For hazardous materials, use this field only in Single Piece transactions.
Note: Do not use Field 1331 for FedEx Ground ORM-D
DG/HazMat Form Print Flag
1493
Max=1
A
I
FDXG
US
REQUIRED*
Enables printing of a hazardous materials (HazMat) form.
*Required to print the FedEx Ground HazMat OP-900.
Valid values are:
Y — Enables printing of HazMat form
N — Disables printing of HazMat form
For hazardous materials, use this field only in Single Piece transactions.
Max=255 A
I
FDXG
US
Optional
UNC ID of the printer used to print hazardous materials forms if different
than the printer in the FSMS Configuration Utility or if no printer is
configured.
For hazardous materials shipments, use in Single Piece transactions
only.
DG Printer ID
1679
6-26
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-15: HazMat Shipping Fields for Ground (Continued)
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
Description
DG Printer Form Type
1680
Max=2
N
I
FDXG
US
Optional
Indicates the type of printer used to print forms.
You must match the field occurrence number (for example, 1680-1) with
the occurrence number of Field 1373 (Report Code) for the type of form
you request.
Valid values are:
01 — Form Feed (default)
02 — Laser
Note: While you can designate a printer to print HazMat forms using
Field 568 (Report Directory), Field 1680 allows you to designate a separate printer for this form type if you use a pin-feed or laser printer specifically designated as your "HazMat Form" printer. Setting up a separate
printer using Field 1680 eliminates the need for changing paper stock in
your report printer.
For hazardous materials shipments, use in Single Piece transactions
only.
US
Field Level: Shipment
REQUIRED
N — North America regulated shipment (FedEx Ground only)
Note: 1903 can only be ‘Consumer Commodity’ or ‘Cartridges, Small
Arms’). All other DG fields within this transaction can be ignored.
For U.S. dangerous goods shipments, use this field in Single Shot and
Open Ship transactions.
Dangerous Goods Regulation Indicator
1900
Max=1
A
I
FDXG
Note: If shipping FedEx Ground ORM-D with field set to “O”, Field 1300
must be set to “N”.
Department of Transportation (DOT) Shipping Name of Material
1903
Max=50
A/N
I
FDXG
US
Field Level: Shipment
REQUIRED*
*Required if Field 451 (Dangerous Goods UN Number/Identification
Number) has multiple names (i.e. UN1263, Paint).
Specify the proper shipping name of the hazardous material. This name
cannot have "waste" included in it.
Note: Only the first 50 characters print on the FedEx Ground HazMat
OP-900 report.
For hazardous materials, use this field only in Single Piece transactions.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
6-27
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-15: HazMat Shipping Fields for Ground (Continued)
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
Description
Type DOT Label(s) Required, Ltd. Qty., or Exemption Number
3072
Max=50
A
I
FDXG
SQE Indicator
4937-#
Max=1
US
REQUIRED*
*Required if Field 1493 (DG/HazMat Form Print Flag) is set to Y and you
print the FedEx Ground HazMat OP-900.
See Column 6 of the hazardous materials table in the FedEx Ground
Shipping Hazardous Materials Guide.
For hazardous materials, use this field only in Single Piece transactions.
Transactions: 020 Global Ship Request
N
I/O
FDXG
FDH
Field Level: Package
Optional
Denotes whether package contains a SQE (Small Quantity Exception)
commodity. Default position is 2 = No.
Valid values are:
1 — Yes
2 — No
Shipping Methods: Single Piece, Single Shot - MPS, Open Ship - MPS,
Open Ship - PAYG - MPS
Note: A SQE commodity may not be combined with a HazMat commodity in one shipment. If a customer attempts to ship via the 020 transaction in a Ground HazMat shipment, with Field 1274 set to 92, Field 1331
set to Y, and Field 451 passed in with a valid HazMat UN ID, and customer also sends in Field 4937 SQE Indicator set to "1" for Yes, the customer receives error message 3100, “Commodities in package cannot
be combined.”
Non Hazardous Lithium Battery Indicator
4938-#
6-28
Max=1
N
I/O
Transactions: 020 Global Ship Request
FDXG
FDH
Field Level: Package
Optional
Denotes whether package contains a Non Hazardous Lithium Battery.
Default position is 2 = No.
Valid values are:
1 — Yes
2 — No
Shipping Methods: Single Piece, Single Shot - MPS, Open Ship - MPS,
Open Ship - PAYG - MPS
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-15: HazMat Shipping Fields for Ground (Continued)
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
Offeror Name
4939-#
Min=1
Max=35
Description
Transactions: 020/120 Global Ship Request/Reply
AKE
I/O
FDXG
US
Field Level: Package
Optional
Designates an Offeror Name or Shipper Contact Name to be used by
FedEx Ground Operations and the DOT as a contact in case of an
emergency situation with a Hazardous Materials Package.
Note: Failure to provide the accurate information for the Offeror/Shipper
Name whether passed in the transaction or defaulted along with the
Emergency Contact Number may result in fines being incurred by the
customer from the Department of Transportation.
If this field is not passed in a HazMat transaction or passed in blank,
FSMS will use Field 32 (Sender Contact Name) associated with the meter
at ship time and customers will receive an information message and the
shipment will be successful.
Improper Transaction Scenarios
The following transaction messages are examples of improper transaction scenarios.
Proper Shipping Name
If the customer is attempting to ship a Ground hazardous materials package, and has not passed in Field 1903 (DOT Shipping Name of
Material/Proper Shipping Name), and the UN ID has multiple entries in the UN ID table, such as Paint UN ID 1263, then the error message
“The Proper Shipping Name cannot be found” is returned.
Invalid Dangerous Goods Commodity Count
The number of hazardous materials (HazMat) commodities in one piece cannot exceed three commodities. If the customer attempts to ship
a FedEx Ground HazMat shipment using the 020 Global Shipping Transaction, and Field 1274(Service Type) is set to 92 (FedEx Ground),
and Field 1331 (Dangerous Goods/HazMat Flag) is set to Y, and Field 451(Dangerous Goods UN Number/Identification Number) in used in
more than three occurrences with valid HazMat UN IDs, then the error message “Dangerous goods commodity count invalid” is returned and
the transaction fails.
Missing Hazard Class
If the customer is attempting to ship a FedEx Ground hazardous materials package with the hazardous materials Field 1331 (Dangerous
Goods/HazMat Flag) set to Y with a valid UN ID number, but does not pass in the Hazard Class Field 492 (DOT Hazard Class or Division
Number), then the error message, “The Dangerous Goods Class cannot be left blank” is returned.
Packing Group
If the customer is attempting to ship a FedEx Ground hazardous materials package with Field 1331 (Dangerous Goods/HazMat Flag) set to
Y with a valid UN ID number, and the UN ID number has multiple entries, and a valid Packing Group is not specified, then the error
message, “The Packing Group is required” is returned.
Required Emergency Phone Number
If a customer attempts to ship a Ground HazMat shipment, and Field 1274 (Service Type) is set to 92 (FedEx Ground), and Field 1331
(Dangerous Goods/HazMat Flag) is set to Y with a valid UN ID number in Field 451, but does not pass in Field 484 (Emergency Contact
Number), then error message 3001 “The Emergency Phone Number is required” is returned and the transaction fails.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
6-29
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Offeror Name
If the customer attempts to ship a FedEx Ground HazMat package via the 020 Global Ship Transaction and Field 4939 (Offeror Name) is not
passed in or is passed in blank, FSMS defaults Field 4939 to the value passed in Field ID 32 (Sender Contact Name) or the Sender/Shipper
Contact Name associated with the meter at ship time. The error message “This type of regulated shipment requires the Offeror Name that is
registered with the Emergency Response Information provider. Since Offeror Name, Field 4939, was not provided, the Shipper Name shall
be used” is returned, and the shipment is processed.
If the customer attempts to ship any other type of package that is not a Ground HazMat package and passes in Field 4939 and all other
shipping data is valid, the Offeror Name shall be ignored, and the shipment will succeed.
Shipping Rules for ORM-D
ORM-D materials may be shipped by either FedEx Ground or FedEx Home Delivery within the 48 contiguous U.S. States.
Customers who need to process Ground ORM-D shipments, must use the correct Field Tags when building the 020 Transaction. Do not use
Express ORM-D guidelines when building Ground ORM-D transactions. Failure to use the proper Field Tags may result in overcharges.
Follow these guidelines (see Table 6-16 below):
• Field ID 1900 (DG Regulations Indicator) should be set to 'O' for ORM-D
• Field ID 451 (DG/Haz Mat UN ID #) must show the correct UN ID # so it will be identified as ORM-D in the database.
• The maximum shipment weights vary depending upon the commodity. See specific weight limitations in the following sub-sections.
• The reverse-print human readable text, “NOAIR” prints on the label of an ORM-D shipment, as shown in Figure 6-1.
• A Ground ORM-D shipment shall not have signature service option.
• Customers on automation must identify whether a ground shipment is ORM-D or not. The default is “No.”
NOTE: Ground ORM-D functionality is available only in FXRS 100x and above.
Table 6-16: Ground ORM-D Fields
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
Description
Dangerous Goods Regulation Indicator
Transactions: 020 Global Ship Request
1900
FDXG:
US
Max=1
A
I
FDXG
Field Level: Shipment
REQUIRED
Select which of the following applies to the dangerous goods (DG)
shipment:
O — ORM-D (49 CFR) regulations apply (U.S. and Puerto Rico only)
Note: Field 1903 can only be “Consumer Commodity,” “Cartridges, Small
Arms,” or “Cartridges, Power Devices.”). All other DG fields within this
transaction can be ignored.
For U.S. dangerous goods shipments, use this field in Single Shot and
Open Ship transactions.
6-30
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-16: Ground ORM-D Fields (Continued)
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
Description
Dangerous Goods UN Number/Identification
Number
Transactions: 020 Global Ship Request
451
US
Max=4
N
I
FDXG
Field Level: Shipment if dangerous goods
REQUIRED*
UN number of the dangerous goods or hazardous materials shipment.
*Required for hazardous materials shipment if Field 1493 (DG/HazMat
Form Print Flag) is set to Y, and printing the FedEx Ground Hazardous
Materials Shipping Paper, OP-900.
See Column 4 of the HazMat table in the FedEx Ground Shipping
Hazardous Materials Guide.
The number of HazMat commodities in one piece cannot exceed three. If
a customer attempts to ship via the 020 Request/Reply Transaction in a
Ground HazMat shipment, Field 1274 set to 92, Field 1331 set to Y, and
Field 451 in multiple occurrence passed in with more than three valid
HazMat UN IDs, the customer receives error message 4027, “Dangerous
Goods/HazMat commodity count invalid” and the transaction fails.
Note: If a customer passes in an invalid UN ID number in Field 451, they
receive error message 3020, “The UN ID # was not found” and the transaction fails.
Note: If a customer attempts to ship via the 020 Request/Reply Transaction in a Ground HazMat shipment using a VALID UN ID that is not
accepted by FedEx Ground (i.e. UN3397), the customer receives error
message 3101, “The selected hazardous material is not accepted by
FedEx Ground” and the transaction fails.
Dangerous Goods UN Number/Identification
Number
Transactions: 020 Global Ship Request
451
(cont.)
US
Max=4
N
I
FDXG
Note: If a customer attempts to ship a Ground HazMat shipment, Field
1274 set to 92, Field 1331 set to Y with a valid UN ID number in Field
451 that contains the symbol “G” (i.e. UN3098), but does not pass in
Field 446 DG/HZ Technical Name or passes this in blank, they receive
error message 0787, “Dangerous Goods technical name is required for
the specified UN number” and the transaction fails.
Field Level: Shipment if dangerous goods
REQUIRED*
Note: For U.S. dangerous goods shipments, use this field in a Single
Shot or Open Ship transaction. For international dangerous goods shipments, use this field in a Single Piece transaction only. For hazardous
materials shipments, use only in Single Piece transactions.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
6-31
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Figure 6-1: FedEx Ground ORM-D Label
6-32
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Dry Ice
There is no limit on the number of Dry Ice commodities within a shipment.
Weight Limits
If FedEx Ground is the selected service, then the weight of the Dry Ice, along with the weight of the remaining contents of package, or the
packaging itself, must comply with the FedEx Ground maximum weight limit of 150 lbs. (68.04 kgs). If the shipment is a FedEx Home
Delivery shipment, then the maximum weight limit must comply with the standard FedEx Home Delivery maximum weight limit of 70 lbs.
(31.75 kgs).
Excessive Weight - FedEx Ground
If the customer attempts to ship a package via the 020 Global Ship Transaction, and the Dry Ice Flag (Field 1268) is set to Y, and Field 1670
(Package Weight/Shipment Weight) = 151.00 with Field 75 (Weight Units) set to lbs., or Field 1670 = 69.00 with Field 75 set to kgs, then the
system returns Error Message270, “The weight limit for this service type has been exceeded,” and the transaction fails.
Excessive Weight - FedEx Home Delivery
If the customer attempts to ship a package via the 020 Global Ship Transaction, and the Dry Ice Flag (Field 1268) is set to Y, and Field 1670
(Package Weight/Shipment Weight) = 71.00 with Field 75 (Weight Units) set to lbs., or Field 1670 = 32.00 with Field 75 set to kgs, then the
system returns Error Message 0270, “The weight limit for this service type has been exceeded,” and the transaction fails.
Table 6-17: Modified Fields for Dry Ice
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
A
I
Description
Dry Ice Flag
1268
Max=1
FDXE
FDXG
FHD
REQUIRED*
Indicates whether the shipment contains dry ice.
*Required if shipment contains dry ice.
Valid values are:
Y — Shipment contains dry ice
N — Shipment does not contain dry ice
Small Quantity Exception
Weight Limits
The weight maximum for FedEx Ground and FedEx Home Delivery Small Quantity Exception shipments is 64 lbs. (29.09 kgs).
Excessive Weight
If the customer attempts to ship a Ground SQE or FedEx Home Delivery SQE package, and Field 4937 (SQE Indicator) is set to 1 for Yes,
and Field 1670 (Package Weight/Shipment Weight) = 65.00 with Field 75 (Weight Units) set to lbs., or Field 1670 = 30.00 with Field 75 set to
kgs, then the system returns Error Message 0270, “The weight limit for this service type has been exceeded,” and the transaction fails.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
6-33
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-18: New Fields for Small Quantity Exception
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
N
I/O
Description
SQE Indicator
4937-#
Max=1
FDXG
FDH
Field Level: Package
Optional
Denotes whether package contains a SQE (Small Quantity Exception)
commodity. Default position is 2 = No.
Valid values:
• 1 = Yes
• 2 = No
Shipping Methods: Single Piece, Single Shot - MPS, Open Ship - MPS,
Open Ship - PAYG - MPS
Non-Hazardous Lithium Battery
Non-Hazardous Lithium Batteries can now be shipped via FedEx Ground and FedEx Home Delivery within all 50 States.
Weight Limits
If FedEx Ground is the selected service, then the weight of the Non Hazardous Lithium Battery, along with the weight of the remaining
contents of the package, or the packaging itself, must comply with the FedEx Ground maximum weight limit of 150 lbs. (68.04 kgs).
If FedEx Home Delivery is the selected service, then the weight of the Non Hazardous Lithium Battery, along with the weight of the
remaining contents of the package, or the packaging itself, must comply with the standard FedEx Home maximum weight limit of 70 lbs.
(31.75 kgs).
Excessive Weight - FedEx Ground
If the customer attempts to ship a FedEx Ground package via the 020 Global Ship Transaction with Field 4938 (Non Hazardous Lithium
Battery Indicator) set to 1 for Yes, and Field 1670 (Package Weight) = 151.00 with Field 75 (Weight Units) set to lbs., or Field 1670 = 69.00
with Field 75 set to kgs, then the system returns Error Message 0270, “The weight limit for this service type has been exceeded,” and the
transaction fails.
Excessive Weight - FedEx Home Delivery
If the customer attempts to ship a FedEx Home Delivery package via the 020 Global Ship Transaction with Field 4938 (Non Hazardous
Lithium Battery Indicator) set to 1 for Yes, and Field 167 (Package Weight) = 71.00 with Field 75 (Weight Units) set to lbs., or
Field 1670 = 32.00 with Field 75 set to kgs, then the system returns Error Message 0270, “The weight limit for this service type has been
exceeded,” and the transaction fails.
6-34
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-19: New Fields for Non-Hazardous Lithium Batteries
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
Description
Non Hazardous Lithium Battery Indicator
4938-#
Max=1
N
I/O
FDXG
FDH
Field Level: Package
Optional
Denotes whether package contains a Non Hazardous Lithium Battery.
Default position is 2 = No.
Valid values:
1 = Yes
2 = No
Shipping Methods: Single Piece, Single Shot - MPS, Open Ship - MPS,
Open Ship - PAYG - MPS
Shipping Rules for all other Hazardous Materials
The maximum weight for HazMat shipments (excluding ORM-D) is 70 lbs. (31.75 kgs).
Weight Limit Exceeded
If the customer attempts to ship a FedEx Ground HazMat package via the 020 Global Ship Transaction and Field 1670 = 71 lbs. (Package
Weight) with Field 75 (Weight Units) set to lbs., or Field 1670 = 32 kgs. with Field 75 set to kgs, then the customer receives Error
Message 0270, “The weight limit for this service type has been exceeded,” and the transaction fails.
FedEx Ground Tracking Numbers
The FedEx Ground tracking number range for all FSMS Ground shipping accounts/meters is 7000001-9999999.
A FedEx Ground shipper does not need to download FedEx Ground tracking numbers. The Ground Tracking Number range is automatically
populated when FSMS is installed or upgraded. The range is available to the customer when the Master Meter is properly configured by a
FedEx Customer Support representative or customer consultant.
A FedEx Ground tracking number is composed of three parts: the customer's 7-digit FedEx Ground account number, the 7-digit tracking
number visible in the Tracking Numbers tab, and a check digit. This 15-digit tracking number is used to track FedEx Ground packages
(see Figure 6-2).
Figure 6-2: FedEx Ground Tracking Number
When a customer’s FedEx Ground tracking number range (on the master meter) is depleted, the range automatically rolls over and begins
again at 7010001.
Note: FedEx Ship Manager Server does not allow a value of zero (0) or null for the first digit in the Ground Tracking Number Range fields.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
6-35
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Allocation of FedEx Ground Tracking Numbers
FedEx Ship Manager Server allocates the ground tracking number range as follows for each FedEx Ground account number that has
multiple meters tied to that account.
Example 1: Shared Meter Account Number
In this scenario, a company has one FedEx Ground account number with two meter numbers:
• Ground account number 1234567 with meter 44444
• Ground account number 1234567 with meter 55555
If ten (10) packages are shipped using alternate meters, the tracking number assignment is as follows:
12345677000001
12345677000006
12345677000002
12345677000007
12345677000003
12345677000008
12345677000004
12345677000009
12345677000005
12345677000010
Example 2: Unique Meter Account Numbers
In this scenario, a company has two FedEx Ground account numbers, each with a single assigned meter number.
• Ground account number 1234567 with meter 44444
• Ground account number 9876543 with meter 55555
The range for each meter could be the same entire allocation range for FSMS such as:
7000001 - 9999999.
If ten (10) packages are shipped using alternating meters, the tracking number assignment is as follows:
12345677000001
98765437000004
98765437000001
12345677000003
98765437000002
12345677000004
98765437000003
98765437000005
12345677000002
98765437000006
Note: Prior to this FSMS release, the allocation of numbers in this same scenario has been as follows:
12345677000001
98765437000006
98765437000002
12345677000007
98765437000003
12345677000008
98765437000004
98765437000009
12345677000005
98765437000010
6-36
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Monitoring FedEx Ground Tracking Numbers
You can use the FSMS Configuration Utility to monitor the FedEx Ground tracking numbers you assign.
To monitor FedEx Ground tracking numbers
1.
Open the FedEx Configuration Utility.
2.
Click the Tracking Numbers tab.
3.
Select the master Meter Number in the upper left corner.
4.
Find the Ground Tracking Numbers Prefixes section in the middle of the screen. This section shows the FedEx Ground accounts and
tracking number ranges for the meter number you selected above in Step 3. The FedEx Ground tracking number range field (Start,
End, Current) values must be specific to each FedEx Ground account on your system. Use the setting descriptions in Table 6-20 to
guide your entries.
Table 6-20: Ground Tracking Number Settings
Configuration Setting
Descriptions
GRD Account #
Ground-enabled account numbers.
This field is pre-populated with tracking numbers for each Ground account number configured on
your FSMS system. Displays only account numbers for accounts tied to Ground-enabled meters.
If the meter you select is not Ground-enabled, no accounts display
Start
Tracking number at start of range. Valid number for first digit is 1–9.
Default = 7000001
End
Tracking number at end of range. Valid number for first digit is 1–9.
Default = 9999999
Current
Last tracking number assigned for the account. Valid number for first digit is 1–9.
Note: You cannot edit account or tracking numbers.
5.
When you are ready, click Exit to close the FedEx Configuration Utility.
Note: The Ground Tracking Numbers Prefixes is password protected. If you wish to change your account or tracking numbers, see your
FedEx field personnel. Your field person can perform the following tasks:
–Copy Range to All Accounts — Copy a specified Ground Tracking Number range to all of the Ground Accounts on the system.
–Edit — Edit the Ground Tracking Number range for a selected Ground Account Number.
–Reset Range to Default — Reset the Ground Tracking Number range to the default range for a selected Ground Account Number.
FedEx Ground End-of-Day Reports
Shippers can create two new FedEx Ground End-of-Day (EOD) report files:
• Ground Domestic EOD TransOut Report
• Ground International EOD TransOut Report
FedEx Ship Manager Server creates both reports as part of the End-of-Day Close request triggered by the 007/107 End-of-Day Close
Request/Reply transaction. You must include Field 1373 (Report Code) in the End-of-Day transaction request with one of the report codes
listed inTable 6-21.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
6-37
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Table 6-21: FedEx Ground End-of-Day Reports
FedEx Ground End-of-Day Report
Field 1373 Report Code
FedEx Ground Domestic EOD TransOut Report
Valid value is "061". Prints to file only. See following table.
FedEx Ground International EOD TransOut Report
Valid value is "062". Prints to file only. See following table.
FedEx SmartPost Detail Report
Valid value is "067".
FedEx SmartPost Returns Report
Valid value is "068".
FedEx SmartPost Manifest Report
Valid value is "069".
The generated report files (.txt files) are saved to the directory configured in the Report Settings screen of the FSMS Configuration Utility.
Table 6-22 shows the naming format for the reports:
Table 6-22: Ground End-of-Day Report Name Formats
Ground End-of-Day Report
File Name
FedEx Ground Domestic EOD TransOut Report
xxxxxx_yyyy_zzzz_Ground Domestic EodTransOut.txt
FedEx Ground International EOD TransOut Report
xxxxxx_yyyy_zzzz_Ground International EodTransOut.txt
Where
xxxxxx is the meter number
yyyy is the beginning cycle count number
zzzz is the ending cycle count number
To configure the Ground report directory
1.
Open the FSMS Configuration Utility.
2.
Click the Report Settings tab.
3.
In the Directory field, type the path or browse to the directory where you want to save the reports.
FedEx Ground U.S. Transaction Samples
Each transaction sample includes required fields for shipping FedEx Ground U.S. packages plus examples of the following field usage:
• Multiple-occurrence fields
• Custom labels
• Label save to butter file
• Reference fields
• Rate quotes and time in transit information
• Alternate return address
• Delivery to residential address
• FedEx Collect on Delivery (C.O.D.) service option
6-38
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
• Electronic Collect on Delivery (E.C.O.D.) service option
• Hazardous materials service option
• Open Ship shipment
Multiple and Single Piece Transaction Samples
A FedEx Ground or FedEx Home Delivery multiple-piece shipment (MPS) consists of two or more packages shipped to the same recipient.
An MPS shipment uses a single transaction with multiple occurrence fields (called Single Shot) or an Open Ship transaction.
Single Shot Multiple-Piece Shipment (MPS) with Multiple Occurrence Fields
0,"20"1,"5 Package Ground Single Transaction MPS"11,"Recipient Company"13,"20 Peachtree Rd."
15,"Pottstown"16,"PA"17,"19464"18,"9012639234"1670,"15"1670-2,"15"1670-3,"5"1670-4,"5"
1670-5,"5"23,"1"50,"US"187,"199"498,""537,"\\printserver\eltronlp"1273,"01"1274,"92"1282,"N"
3002,"Shipment Invoice Number"3056,"Package PO 001"3056-2,"Package PO 002"3056-3,"Package PO
003"3056-4,"Package PO 004"3056-5,"Package PO 005"3062,"2"99,""
Single Shot Multiple-Piece Shipment (MPS) with Custom Label
0,"020"1,"5 package Ground single transaction MPS, Custom Label"11,"Recipient Company"13,"20
Peachtree Rd."15,"Pottstown."16,"PA"17,"19464"18,"9012639234"23,"1"38,"Pricing"38-2,"Pricing"
38-3,"Pricing"38-4,"Pricing"38-5,"Pricing"50,"US"187,"199"498,""537,"C:\2D Bar Code"1234,""
1273,"01"1274,"92" 1282,"B"1660,"Y"1670,"500"1670-2,"550"1670-3,"600"1670-4,"1000"1670-5,
"1050"3002,"Shipment Invoice Number"3056,"PO 001"3056-2,"PO 002"3056-3,"PO 003"3056-4,"PO
004"3056-5,"PO 005"3062,"2"99,""
• Single Shot Multiple-Piece Shipment (MPS) with Multiple Occurrence Reference Fields
0,"020"1,"Ground single transaction MPS multiple ref fields"11,"RecipientCompany"13,"20
Peachtree Rd."15,"Atlanta"16,"GA"17,"30052"18,"9012639234"23,"1"25,"CR001 Package 1"25-2,
"CR002 Package 2"25-3,"CR003 Package 3"25-4,"CR004 Package 4"25-5,"CR005 Package 5"50,"US"
187,"199"498,""537,"\\printserver\eltronlp" 1234,""1273,"01"1274,"92"1282,"N"1660,"N"1670,
"500"1670-2,"550"1670-3,"600"1670-4,"1000"1670-5,"1050"3001,"Shipment PO: ABC123EAD"3057,
"Package 1 AB01"3057-2,"Package 2 BC02"3057-3,"Package 3 CD03"3057-4,"Package 4 DE04"30575,"Package 5 EF05"3062,"2"99,""
Single Piece FedEx Ground Shipment with Request for Both Rate and Time in Transit
0,"020"1,"Single Package Ground Rate Quote/Time in Transit"11,"Recipient Company"13,"20
Peachtree Rd."15,"Memphis"16,"TN"17,"38125"18,"9012639234"23,"1"50,"US"187,"199"498,""537,
"\\printserver\eltronlp"1234,"3"1273,"01"1274,"92"1282,"N"1660,"N"1670,"1500"3056,"PO Number
0001"3062,"2"99,""
Single Piece with Alternate Return Address
0,"020"1,"Single Package Ground Alternate Return Address"11,"Recipient Company"13,"20
Peachtree Rd."15,"Memphis"16,"TN"17,"38125"18,"9012639234"23,"1"50,"US"187,"199"498,""
537,"\\printserver\eltronlp"1234,""1273,"01"1274,"92"1282,"N"1485,""1486,"Data Processing
Inc"1487,"1533 Main Street"1488,"Suite 2000"1489,"Waco"1490,"TX"1491,"76701"1492,"8561239876"
1585,"US"1586,"Y"1660,"N"1670,"1500"3056,"PO Number 0001"3062,"2"99,""
Single Piece with Collect on Delivery Service Option and Return to Third Party
0,"020"1,"Ground C.O.D. 3rd Party Return"11,"Recipient Company"12,"Someone"13,"20 Peachtree
Rd."15,"Memphis"16,"TN"17,"38125"18,"9012639234"23,"1"27,"Y"50,"US"53,"100"186,"Y"187,"199"49
8,""537,"\\printserver\eltronlp"1237,"9012639234"1238,"C.O.D. Manager Inc"1239,"Collections"
1240,"30 FedEx Parkway"1241,"1st Floor Horiz"1242,"Collierville"1243,"TN"1244,"38017"1273,
"01"1274,"92"1282,"N"1660,"N" 1670,"1500"3000,"1"3056,"PO Number 0001"3062,"2"99,""
v 10.6.1
FedEx Ship Manager® Server Developer Guide
6-39
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Single Piece with Electronic Collect on Delivery Service Option
0,"020"1,"Ground E.C.O.D. w/o 3rd Party Return"11,"Recipient Company"12,"Someone"13,"20
Peachtree Rd."15,"Memphis"16,"TN"17,"38125"18,"9012639234"23,"1"50,"US"53,"100"187,"199"
498,""537,"C:\2D Bar Code"1273,"01"1274,"92"1282,"B"1660,"Y"1670,"1600"3000,"1"3014,"Y"
3056,"PO Number 0001"3062,"2"99,""
Single Piece with Dimensional Height, Width and Length To Be Delivered to Residential Address
0,"020"1,"Ground Residential with Dims"11,"Recipient Company"13,"20 Peachtree Rd."15,"Atlanta"
16,"GA"17,"30052"18,"9012639234"23,"1"50,"US"57,"12"58,"10"59,"65"187,"199"440,"Y"498,""537,"
C:\2D Bar Code"1273,"01"1274,"92"1282,"B"1660,"Y"1670,"300"3062,"2"99,""
Single Piece with Label Saved to Buffer File for Printing Later
0,"020"1,"Single transaction MPS, label buffer saved to file"11,"Recipient Company"13,"20
Peachtree Rd."15,"Pottstown"16,"PA"17,"19464"18,"9015551212"23,"1"50,"US"187,"199"498,""537,
"C:\Label Buffer"1234,""1273,"01"1274,"92"1282,"S"1670,"500"1670-2,"500"1670-3,"500"1670-4,
"500"1670-5,"500"3002,"Shipment Invoice Number"3056,"PO 001"3056-2,"PO 002"3056-3,"PO 003
"3056-4,"PO 004"3056-5,"PO 005"3062,"2"99,""
Single Piece with Required Fields for Hazardous Materials Shipment
0,"020"1,"Ground HazMat, Print OP-900"11,"Recipient Company"13,"20 Peachtree Rd."15,"Memphis"
16,"TN"17,"38125"18,"9015551212"23,"1"50,"US"187,"199"451,"1234"466,"10"471,"GAL"484,"9012631
234"489,"III"492,"3"498,""537,"\\FedEx Ship Manager ServerTEST\EltronLP"1273,"01"1274,"92"
1282,""1331,"Y"1493,"Y"1660,"N"1670,"300"1903,"Toluene"3056,"PO Number 0001"3062,"2"3072,
"Flammable Liquid"99,""
Single Piece for U.S. Delivery with Electronic Collect on Delivery and Thermal Label
0,"020"1,"Step 008 Dom Ground ECOD"10,""11,"Ground ECOD"12,"Ground ECOD"13,"387 Main Street"
14,"FEDEX PARKWAY"15,"New York"16,"NY"17,"10001"18,"1234567890"20,""21,"1"24,""25,"Step 008
Dom Ground ECOD"26,"100"50,"US"53,"2000"75,"lbs"117,"US"187,"PNG"498,""537,1116,"IN"1273,
"01"1274,"92"1670,"100"3014,"Y"99,""
FedEx Ground and Home Delivery Return Transaction Samples
These code samples show 020 Global Ship Request transactions for Return shipments using FedEx Ground and Home Delivery services.
Return Shipment Prepaid for FedEx Ground Service
0,"020"1,"Ground Return shipment Prepaid"4,""5,"904 Main St"6,""7,"Jackson"8,"SC"9,"29831"23,
"1"32,"Mr. Customer"50,"US"117,"US"183,"9012639234"187,"199"498,""537,"\\printserver\eltron
lp"1234,""1273,"01"1274,"92"1282,"N"1660,"N"1670,"320"2382,"2"3056,"PO Number 0001"3062,"2"
99,""
Return Shipment with Third-Party Payer for FedEx Ground Service
0,"020"1,"Ground Return 3rd Party Billing"4,""5,"904 Main St"6,""7,"Jackson"8,"SC"9,"29831"
20,"123456789" 23,"3"32,"Mr. Customer"50,"US"117,"US"183,"9012639234"187,"199"498,""537,
"\\printserver\eltronlp"1234,""1273,"01"1274,"92"1282,"N"1660,"N"1670,"1500"2382,"2"3056,"PO
Number 0001"3062,"2"99,""
6-40
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Return Shipment with Alternate Return Address for FedEx Ground
0,"020"1,"Ground Return alternate return address"4,""5,"904 Main St"6,""7,"Jackson"8,"SC"9,"
29831"11,"Product Returns"12,"Return Manager"13,"1685 Briarwood Lane"14,""15,"Pottstown"
16,"PA"17,"19464"18,"6105551212"23,"1"32,"Mr. Customer"50,"US"117,"US"183,"9012639234"187,
"199"498,""537,"C:\2D Bar Code"1234,""1273,"01"1274,"92"1282,"B"1660,"Y"1670,"2000"2382,"2"
3056,"PO Number 0001"3062,"2"99,""
Return Shipment Prepaid for FedEx Home Delivery Service
0,"020"1,"FHD Return shipment Prepaid"4,""5,"904 Main St"6,""7,"Jackson"8,"SC"9,"29831"
1670,"15"23,"1" 32,"Mr. Customer"50,"US"117,"US"183,"9012639234"187,"99"498,""537,""1234,""
1273,"01"1274,"90"1660,"Y" 2382,"2"3056,"PO Number 0001"3062,"2"99,""
Return Shipment with Third Party Payer for FedEx Home Delivery
0,"020"1,"FHD Return shipment 3rd Party Billing"4,""5,"904 Main St"6,""7,"Jackson"8,"SC"9,
"29831"20,"123456789"23,"3"32,"Mr. Customer"50,"US"117,"US"183,"9012639234"187,"199"498,""
537,""1234,""1273,"01" 1274,"90"1660,"Y"1670,"1000"2382,"2"3056,"PO Number 0001"3062,"2"99,""
Return Shipment for FedEx Home Delivery with Label File Saved to Buffer File for Later Printing
0,"020"1,"FHD Return, label buffer saved to file"4,""5,"904 Main St"6,""7,"Jackson"8,"SC"
9,"29831" 23,"1"32,"Mr. Customer"50,"US"117,"US"183,"9012639234"187,"199"498,""537,"C:\Label
Buffer"1234,"" 1273,"01"1274,"90"1282,"S"1660,"N"1670,"300"2382,"2"3056,"PO Number
0001"3062,"2"99,""
FedEx Home Delivery (FHD) Transaction — Samples
These samples are 020 Global Ship Request transactions for FedEx Home Delivery service with the following special options:
• Appointment Delivery
• Date Certain
• Evening Delivery
• Delivery Signature
• ShipAlert Notification
• Single Piece FedEx Home Delivery with Appointment Delivery Service Option
0,"020"1,"FHD Appointment Delivery"12,"Mr. John Recipient"13,"123 Main St."15,"Memphis"16,"TN"
17,"38125" 18,"9015551212"23,"1"50,"US"187,"199"498,""537,"\\printserver\eltronLP"1273,"01"
1274,"90"1282,"N"1660,"N"1670,"100"3020,"3"3024,"9012631234"3056,"PO Number 0001"3062,"2"
99,""
Single Piece FedEx Home Delivery with Date Certain Service Option
0,"020"1,"FHD Date Certain"12,"Mr. John Recipient"13,"20 Peachtree Rd."15,"Memphis"16,"TN"
17,"38125" 18,"9012631234"23,"1"50,"US"187,"199"498,""537,"\\printserver\eltronlp"1273,"01"
1274,"90"1282,"N"1660,"N"1670,"200"3020,"1"3023,"20021111"3024,"9012639234"3056,"PO Number
0001"3062,"2"99,""
Single Piece FedEx Home Delivery with Evening Delivery Service Option
0,"020"1,"FHD Evening Delivery"12,"Mr. John Recipient"13,"20 Peachtree Rd."15,"Memphis"16,"TN"
17,"38125"18,"9012631234"23,"1"50,"US"187,"PNG"498,""537,"C:\PNG "1273,"01"1274,"90"1660,"N"
1670,"350"3020,"2"3021,"Leave at back door"3024,"9012639234"3056,"PO Number 0001"3062,"2"99,""
Single Piece FedEx Home Delivery with Evening Delivery and Signature Required
0,"020"1,"FHD Evening Delivery w/Sig Required"12,"Mr. John Recipient"13,"20 Peachtree
Rd."15,"Memphis" 16,"TN"17,"38125"18,"9012639234"23,"1"50,"US"187,"199"498,""537,
v 10.6.1
FedEx Ship Manager® Server Developer Guide
6-41
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
"\\printserver\eltronlp"1273,"01"1274,"90"1282,"N"1660,"N"1670,"900"2399,"2"3020,"2"3021,
"Leave at back door"3024,"9012639234"3056,"PO Number 0001"3062,"2"99,""
Single Shot Transaction for Multiple-Piece Shipment by FedEx Home Delivery Service to Residential Address
0,"020"1,"5 package FHD single transaction MPS"12,"Mr. John Recipient"13,"20 Peachtree
Rd."15,"Pottstown" 16,"PA"17,"19464"18,"9011234567"23,"1"50,"US"187,"199"498,""537,
"\\printserver\eltronlp"1234,""1273,"01"1274,"90"1282,"N"1660,"N"1670,"600"1670-2,"600"16703,"600"1670-4,"600"1670-5,"600"3002,"Shipment Invoice Number"3056,"PO 001"3056-2,"PO 002"
3056-3,"PO 003"3056-4,"PO 004"3056-5,"PO 005"3062,"2"99,""
Single Piece FedEx Home Delivery with Appointment Delivery Option and ShipAlert Notification
0,"020"1,"FHD Appointment Delivery with ShipAlert e-mail"12,"Mr. John Recipient"13,"123 Main
St." 15,"Memphis"16,"TN"17,"38125"18,"9012639234"23,"1"50,"US"187,"199"498,""537,
"\\printserver\eltronLP" 1204,"someone@fedex.com"1206,"Y"1273,"01"1274,"90"1282,"N"1660,"N"
1670,"150"3020,"3"3024,"9012639234" 3056,"PO Number 0001"3062,"2"99,""
FedEx Ground Hazardous Materials Transaction Samples
Sample 020 Global Ship Request transaction for a FedEx Ground Hazardous Materials Shipment.
0,"020"1,"158-TC128"4,"Bar Code Department"5,"100000 FedEx Gnd Drive fourth floor "6,"West
Wing"7,"Pittsuburgh"8,"PA"9,"15108"11,"SHIP TO COMPANY NAME WITH LG30"12,"SHIP TO CONTACT NAME
WITH LG30"13,"SHIP TO STREET ADDRESS LINEONE"15,"RECIPIENT CITY USA20"16,"MA"17,"02747"
18,"(412)123-4567"20,"258420748"23,"3"32,"TC128-JAN07 Ground Label Evaluation"50,"US"116,"1"
117,"US"183,"4122224444"187,"PNG"451,"UN1263"456,"8"475,"gal"484,"(412) 452-5555"498,""537,""
1273,"01"1274,"92"1331,"Y"1670,"100"1932,"1"1958,"PKG"2210,"RMA# field is twenty"2399,"4"
3003,"Customer Ref# thirty character"3018,"Y"99,""
FedEx Ground HazMat Shipment that Prints the Shipper Offeror Name on the OP-900LG Form for a Single Piece Shipment
0,"020"1,"Ground HazMat, Print OP-900"5,"1234 Dallas Pkwy"7,"Dallas"8,"TX"9,"75201"11,
"RecipientCompany"13,"10 FedEx Parkway"15,"Collierville"16,"TN"17,"38107"18,"9015551212"23,
"1"50,"US"187,"188"446,"Tetraethyl silicate"451,"1292"466,"10"471,"GAL"484,"9012631234"489,
"III"492,"3"537,"\\FEDEX-745D6B10F\ZebraZP5"1273,"01"1274,"92"1282,"S"1331,"Y"1493,"Y"1660,
"N"1670,"300"1679,"\\FEDEX-745D6B10F\HPlaserJ1"1900,"N"1903,"Tetraethyl silicate"1932,"1"
3056,"PO Number 0001"3062,"2"3072,"FLAMMABLE LIQUID"4903,"Freeform"4939,"John Smith"99,""
0,"120"1,"Ground HazMat, Print OP-900"10,"104658989"29,"060332970000301"34,"603"35,"2532"36,
"0"37,"3135"60,"3"112,"3"116,"1"188,""428,"2500"431,"N"446,"Tetraethyl silicate"451,"1292"
466,"10"471,"GAL"484,"9012631234"488,"N"489,"III"492,"3"498,"118463"542,""543,"0"1086,"0"1089
,"0"1090,"USD"1092,"4"1133,"0"1274,"92"1393,"32"1507,"2532"1519,"603"1520,"32"1526,"2500"1528
,"3135"1596,"0"1598,"3135"1599,"3135"1690,"Y"1901,"N"1903,"Tetraethyl silicate"1904,"N"1923,
"N"1924,"N"1926,"N"1928,"N"1932,"1"1942,"N"1943,"N"1944,"N"1981,"End of Day"1992,"0"2399,"3"
2405,"Y"3018,"N"3058,"2"3063,"9612302060332970000301"3065,"42038107"3073,"302"4903,"Freeform"
99,""
FedEx Home Delivery Shipment with ORM-D for Single Piece
0,"020"1,"Ground HazMat, HM3"5,"1234 Dallas Pkwy"7,"San Diego"8,"CA"9,"92126"11,"Acme Inc"13,
"10 World Parkway"15,"Binghampton"16,"NY"17,"13901"18,"9015551212"23,"1"25,"HM3 - Signature
2399 = 4"50,"US"187,"DIB"451,"1292"484,"9012631234"537,"\\FEDEX-745D6B10F\hplaserj"1273,"01"
1274,"92"1282,"S"1331,"N"1493,"Y"1660,"N"1670,"300"1900,"O"1932,"1"3056,"PO Number 0001"3062,
"2"4939,"John Offeror"99,""
0,"120"1,"Ground HazMat, HM3"10,"104658989"29,"060332970000486"34,"736"35,"439"36,"0"37,
"1175"60,"3"112,"3"116,"1"431,"N"498,"118463"542,""543,"0"1086,"0"1089,"0"1090,"USD"1092,"8"1
133,"0"1274,"92"1393,"39"1507,"439"1519,"736"1520,"39"1528,"1175"1596,"0"1598,"1175"1599,"117
6-42
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
5"1690,"N"1942,"N"1943,"N"1944,"N"1981,"End of Day"1992,"0"2400,"400"2401,"400"2405,"Y"3018,
"N"3058,"4"3063,"9612307060332970000486"3065,"42013901"3073,"307"99,""
FedEx Ground Shipment with Dry Ice for Single Piece
0,"020"1,"Ground HazMat, HM3"5,"1234 Dallas Pkwy"7,"San Diego"8,"CA"9,"92126"11,"Acme Inc"13,
"10 World Parkway"15,"Binghampton"16,"NY"17,"13901"18,"9015551212"23,"1"25,"HM6"50,"US"187,
"DIB"451,"1292"484,"9012631234"537,"\\FEDEX-745D6B10F\hplaserj"1268,"Y"1273,"01"1274,"92"
1282,"s"1331,"N"1493,"Y"1660,"N"1670,"300"1684,"2"1900,"N"1932,"1"3056,"PO Number 0001"3062,"
2"4939,"John Offeror"99,""
0,"120"1,"Ground HazMat, HM3"10,"104658989"29,"060332970000561"34,"736"35,"39"36,"0"37,"775"
60,3"112,"3"116,"1"431,"N"498,"118463"542,""543,"0"1086,"0"1089,"0"1090,"USD"1092,"8"1133,"0"
1274,"92"1393,"39"1507,"39"1519,"736"1520,"39"1528,"775"1596,"0"1598,"775"1599,"775"1690,"N"1
942,"N"1943,"N"1944,"N"1981,"End of Day"1992,"0"2399,"0"2405,"Y"3018,"N"3058,"4"3063,
"9612019060332970000561"3065,"42013901"3073,"019"99,""
FedEx Ground Shipment with SQE for Single Piece Shipment
0,"020"1,"Ground HazMat, HM3"5,"1234 Dallas Pkwy"7,"San Diego"8,"CA"9,"92126"11,"Acme Inc"13,
"10 World Parkway"15,"Binghampton"16,"NY"17,"13901"18,"9015551212"23,"1"25,"HM6 SQE"50,"US"
187,"DIB"451,"1292"484,"9012631234"537,"\\FEDEX-745D6B10F\hplaserj"1273,"01"1274,"92"1282,"s"
1331,"N"1493,"Y"1660,"N"1670,"300"1900,"N"1932,"1"2399,"3"3056,"PO Number 0001"3062,"2"4937,
"1"4939,"John Offeror"99,""
0,"120"1,"Ground HazMat, HM3"10,"104658989"29,"060332970000677"34,"736"35,"339"36,"0"37,
"1075"60,"3"112,"3"116,"1"431,"N"498,"118463"542,""543,"0"1086,"0"1089,"0"1090,"USD"1092,"8"1
133,"0"1274,"92"1393,"39"1507,"339"1519,"736"1520,"39"1528,"1075"1596,"0"1598,"1075"1599,"107
5"1690,"N"1942,"N"1943,"N"1944,"N"1981,"End of Day"1992,"0"2399,"3"2400,"300"2401,"300"2405,
"Y"3018,"N"3058,"4"3063,"9612015060332970000677"3065,"42013901"3073,"015"99,""
FedEx Ground Open Ship Transaction Sample
The following sample shows an Open Ship transaction scenario for entering and confirming a five package multiple-piece shipment.
CREATE an Open Ship shipment Using 020 Global Ship Request Transaction.
0,"020"1,"Create Shipment and ADD First Package"11,"Sam’s Publishing"12,"Recipient Name"
13,"201 West 103rd St"15,"Indianapolis"16,"IN"17,"46290"18,"1234567890"1670,"3500"23,"1"
26,"100"50,"US"498,""541,"YNNNNNNNN"542,"300"1273,"01"1274,"92"99,""
Open Ship shipment Confirmed by 120 Global Ship Reply Transaction
0,"120"1,"Create Shipment and ADD First Package"29,"123456770002179"542,"300"99,""
‘ADD Second Package’ Request Transaction
0,"020"1,"ADD Second Package"1670,"2000"50,"US"498,""541,"NNNYNNNNN"542,"300"1273,"01"1274,
"92"99,""
Second Package Confirmed by 120 Reply Transaction
0,"120"1,"ADD Second Package"29,"123456770002186"99,""
‘ADD Third Package’ Request Transaction
0,020"1,"ADD Third Package"1670,"1500"50,"US"498,""541,"NNNYNNNNN"542,"300"1273,"01"1274,"92"99,""
v 10.6.1
FedEx Ship Manager® Server Developer Guide
6-43
Chapter 6: Coding Transactions for FedEx Ground U.S. Services
Third Package Confirmed by 120 Reply Transaction
0,120"1,"ADD Third Package"29"123456770002193"99,""
‘ADD Fourth Package’ Request Transaction
0,020"1,"ADD Fourth Package"1670,"2500"50,"US"498,""541,"NNNYNNNNN"542,"300"1273,"01"1274,
"92"99,""
Fourth Package Confirmed by 120 Reply Transaction
0,120"1,"ADD Fourth Package"29"123456770002209"99,""
‘ADD Fifth Package’ Request Transaction
0,020"1,"ADD Fifth Package"1670,"1000"50,"US"498,""541,"NNNYNNNNN"542,"300"1273,"01"1274,"92"
99,""
Fifth Package Confirmed by 120 Reply Transaction
0,120"1,"ADD Fifth Package"29"123456770002216"99,""
Request for CONFIRM of Shipment
0,"020"1,"CONFIRM Open Ship Shipment,"1670,"2300"50,"US"187,"N"498,""541,"NNNNNNNNY"542,"300"
1274,"92"99,""
Open Ship Shipment CONFIRMED in 120 Request Transaction
0,"120"1,"Confirm Open Ship Shipment"34,"3508"35,"0"36,"0"37,"3508"60,"105"112,"105"116,"5"
421,"0"428,"0"429,"0"430,"0"542,"300"1089,"0"1274,"92"3058,"2"
3063,"9612019123456770002179"
3063-2,"9612019123456770002186"
3063-3,"9612019123456770002193"
3063-4,"9612019123456770002209"
3063-5,"9612019123456770002216"
3064,"[)>-01 9646290 840 019 123456770002179 RPSB 1/5 35.0 N 201 West 103rd St Indianapolis IN"
3064-2,"[)>-01 9646290 840 019 123456770002186 RPSB 2/5 20.0 N 201 West 103rd St Indianapolis IN"
3064-3,"[)>-01 9646290 840 019 123456770002193 RPSB 3/5 15.0 N 201 West 103rd St Indianapolis IN"
3064-4,"[)>-01 9646290 840 019 123456770002209 RPSB 4/5 25.0 N 201 West 103rd St Indianapolis IN"
3064-5,"[)>-01 9646290 840 019 123456770002216 RPSB 5/5 10.0 N 201 West 103rd St Indianapolis IN"
3065,"42046290"3073,"019"3073-2,"019"3073-3,"019"3073-4,"019"3073-5,"019"99,""
FedEx Ground and FedEx Home Delivery Basic Streamlined
Transactions
These transactions receive sender and other shipment information from the meter configuration in the FSMS Configuration Utility. For this
reason, the number of fields required to complete the transactions is minimal.
FedEx Ground Sample
0,"020"1,"Open Shipment"11,"Test"13,"100 Main St"15,"Anywhere"18,"9012369999"16,"al"17,
"35801"23,"1"50,"US"498,"4000085"1273,"01"1274,"92"1670,"100"99,""
FedEx Home Delivery Sample
0,"020"1,"Open Shipment"11,"Test"13,"100 Main St"15,"Anywhere"18,"9012369999"16,"al"17,
"35801"23,"1"50,"US"498,"4000085"1273,"01"1274,"90"1670,"100"99,""
6-44
FedEx Ship Manager® Server Developer Guide
v 10.6.1
CHAPTER 7: CODING TRANSACTIONS FOR FEDEX
SMARTPOST
FedEx SmartPost® is a contract-only service that helps you consolidate and deliver low-weight, less time-sensitive business-to-consumer
packages to residences. FedEx® picks up, sorts, line hauls, tracks and delivers your packages to the United States Postal Service® (USPS)
post office closest to you. The USPS makes final delivery to the residence.
FedEx SmartPost services include:
• FedEx SmartPost® Standard Mail
• FedEx SmartPost® Parcel Select
• FedEx SmartPost® Bound Printed Matter
• FedEx SmartPost® Media
• FedEx SmartPost® Returns
FedEx has expanded FedEx SmartPost by leveraging the FedEx Ground® network to provide cost-effective pickup and origin processing
services to reach customers with lower volumes (less than 499 package average daily volume) of residential shipments. This service is
available to all FedEx SmartPost customers who originate shipments in the 48 contiguous United States. Return Service is available to the
48 contiguous U.S. states and from all 50 states, U.S. territories, P.O. Boxes, and APO/FPO/DPO locations. The U.S. territories include
American Samoa (AS), Micronesia (FM), Guam (GU), Marshall Islands (MH), Northern Mariana Islands (MP), Republic of Palau (PW), and
US Virgin Islands (VI). The US territories and Puerto Rico while currently considered International destinations by FedEx, will be treated as
domestic locations for FedEx SmartPost Returns shipments.
This chapter assists developers who are integrating the FedEx SmartPost service with their business shipping solution using FedEx Ship
Manager® Server (FSMS) in the following sections:
• FedEx SmartPost Service Types
• Configuring FedEx SmartPost
• Shipping to Military Locations
• FedEx SmartPost Returns Service
• FedEx SmartPost Labels
• Requesting a Rate Quote for FedEx SmartPost
• Closing a FedEx SmartPost Shipment
• Delivery Confirmation Changes
• Shipment and Delivery E-Mail Notifications
• Tracking FedEx SmartPost Shipments
• FedEx SmartPost Transactions
• Transaction Rules for FedEx SmartPost
• Future Day Shipping
• Coding a Basic FedEx SmartPost Shipping Transaction
• Coding a Basic FedEx SmartPost Print Returns Label Transaction
• Coding a Basic FedEx SmartPost E-Mail Returns Shipping Transaction
• Creating a FedEx SmartPost Open Ship Transaction
• Coding Pre-assigned Tracking Numbers
• FedEx SmartPost Transaction Samples
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-1
Chapter 7: Coding Transactions for FedEx SmartPost
See the FedEx Service Guide on fedex.com for further service details and restrictions related to shipping with FedEx SmartPost. To start
using FedEx SmartPost, contact your FedEx customer service representative or FedEx account executive.
FedEx SmartPost Service Types
For FedEx SmartPost shipping, FSMS requires Field 2417 (SmartPost Service Type/Postal Indicia) instead of Field 1274 (Service Type).
Dimensions are not required for FedEx SmartPost shipping. You can enter additional dimension information in Field 57 (Package Height),
Field 58 (Package Width), and Field 59 (Package Length), but these fields are Optional.
Table 7-1 describes the different service options for FedEx SmartPost based on package weight and dimensions:
Table 7-1: FedEx SmartPost Service Types
Service Type
Field
Value
Weight
Minimum
Weight
Maximum
Standard Mail
1
.01 pounds.
<1 pound
Sum of length plus girth cannot exceed 84'
Minimum: 6"(L) x 4"(W) x 1"(H)
Bound Printed Matter
3
.01 pounds
15 pounds
Sum of length plus girth cannot exceed 84'
Minimum: 6"(L) x 4"(W) x 1"(H)
Media
5
.01 pounds
70 pounds
Sum of length plus girth cannot exceed 84'
Minimum: 6"(L) x 4"(W) x 1"(H)
Parcel Select
6
1 pound
70 pounds
Sum of length plus girth cannot exceed 130'
Minimum: 6"(L) x 4"(W) x 1"(H)
FedEx SmartPost Returns
7
.01 pounds
70 pounds
Sum of length plus girth cannot exceed 130'
Minimum: 6"(L) x 4"(W) x 1"(H)
Dimensions
The dimensions noted in Table 7-1 are USPS standards. FedEx Ship Manager Server accepts only whole numbers with no implied decimals
for package dimensions. Therefore the minimum dimension is 1 for Field 57 (Package Height), Field 58 (Package Width) and Field 59
(Package Length).
FedEx Ship Manager Server does not sort the dimensions. Enter the longest dimension in Field 59 (Package Length) and height and width
in the other two fields.
Note: If a weight less than one Lb. is entered for Bound Printed Matter or Media, it is automatically rounded up to one Lb.
Configuring FedEx SmartPost
FedEx SmartPost is an optional contract service for shippers of high volume, low weight, and less time-sensitive packages that uses the
U.S. Postal Service (USPS) for final delivery. FedEx SmartPost configuration settings are made on the FedEx SmartPost Settings and
Tracking Numbers tabs. Configuration and rates for the contractual FedEx SmartPost services will be enabled and maintained on the FedEx
central system and downloaded to the device through a DLL process. FedEx SmartPost configuration settings can be enabled and/or
disabled with User Level Access.
Note: If shipping both FedEx SmartPost outbound and FedEx SmartPost Returns you MUST have two account numbers, two Mailer IDs,
and two meters for the outbound SmartPost shipment and the Return shipment.
FedEx SmartPost configuration settings are on the SmartPost Settings tab of the FSMS Configuration Utility. If you have had FedEx
SmartPost enabled by your customer account representative, then you will have access to configure the FedEx SmartPost Options on
SmartPost Settings tab, as shown in Figure 7-1. Both FedEx SmartPost outbound services and FedEx SmartPost Returns services must be
enabled independently. You must have one of the following access privileges to configure FedEx SmartPost settings:
7-2
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
• User Level View
• Field
• Support
• Development
Note: Shipping both FedEx SmartPost outbound and FedEx SmartPost Returns requires 2 separate accounts and meters configured for the
outbound FedEx SmartPost shipment and the return shipment.
Configuring FedEx SmartPost Outbound Services
In releases of FedEx Ship Manager Server prior to V 10.6.1, FedEx Authorized Technical contacts were required to manually configure the
devices to setup the pickup carrier, to enable FedEx SmartPost services, and to load the FedEx SmartPost rate and ZIP to zone files.
Starting with v 10.6.1 release, all configuration and rate information is maintained on the FedEx central server and information is
automatically downloaded to the customer devices using the DLL process.
Note: This is accomplished with the Demand Download Utility. You must download FedEx Express Domestic Rates and SmartPost Rates.
This initiates the data download within the SmartPost settings tab. If you do not download FedEx Express Domestic rates, a manual
configuration of FedEx SmartPost settings will be required.
Note: Another option to download rates is to run the 057 Demand Download Request Transaction.
Configuring FedEx SmartPost Returns Service
You must download the “update features” from the Demand Download Screen before configuring a new meter for FedEx SmartPost
Returns.
1.
Start the FSMS Configuration Utility.
2.
Click the “Access Privileges” button.
3.
Enter password and click “OK”.
4.
Click the FedEx SmartPost Settings tab. See Table 7-1.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-3
Chapter 7: Coding Transactions for FedEx SmartPost
Figure 7-1: SmartPost Settings Tab with SmartPost Returns Enabled Checkbox
5.
SmartPost Outbound settings shown are read-only and the settings are downloaded from FedEx central server/system.
6.
To setup a FedEx SmartPost Returns account, click “Add” and a pop-up window displays, as shown in Table 7-2.
7-4
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Figure 7-2: Add SmartPost Returns Dialog Box
7.
Enter a Returns Account number.
8.
Click Get Address to get the Returns Account information.
9.
FedEx Ship Manager Server validates that the Returns Account is part of the same National Account and auto-populates the following
information:
a. Company Name
b. Contact Name
c. Address Line 1
d. Address Line 2
e. City
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-5
Chapter 7: Coding Transactions for FedEx SmartPost
f. State
g. ZIP
h. Phone Number
Note: The contact name and phone number fields are the only editable fields.
10. Use the Modify/Delete buttons to update the returns account information.
11. Click “Add” to add the returns account number to the FSMS database. Then the account information will display in the bottom portion
of the FedEx SmartPost Settings tab.
12. Click “Apply.”
Obtaining Tracking Numbers
In order to obtain tracking numbers and Delivery Confirmation Numbers, proceed with Step 1.
Note: Each returns account must have its own tracking number range. If the Delivery Confirmation ranges need to be deactivated, then
FSMS will deactivate the Delivery Confirmation Numbers (DCN) range at reconcile. See Table 7-3.
1.
Download the DCNs from the Demand Download Screen when the FedEx SmartPost Delivery Confirmation Numbers checkbox is
checked.
Use Table 7-2 to guide your selections.
The information entered in the fields in Table 7-2 is automatically provided according to your account setup for FedEx SmartPost. These
fields are for reference only and may not be edited.
Table 7-2: FedEx SmartPost Settings Fields
Settings
Description
Customer ID
Your unique FedEx SmartPost Customer ID. This is an alphanumeric text box with a maximum of 5
characters. The Customer ID is critical for the electronic manifest of FedEx SmartPost shipments.
Mailer ID
A Mailer ID is used by the United States Postal Service to identify mail owners and mailing agents
or other service providers, such as consolidators. The Mailer ID used on packages tendered to
FedEx SmartPost is a 9-digit number issued by FedEx and is embedded within the FedEx
SmartPost tracking number.
Customer Distribution Center
This two-digit number indicates the distribution center that supports your shipping location
according to the Mailer ID. This is entered during configuration and is part of the electronic FedEx
SmartPost shipping manifest file.
PickUp Carrier
Identifies the FedEx service that is used by FedEx to deliver the item to the United States Postal
Service (USPS) for final delivery.
Hub ID
Select the Hub ID for the FedEx SmartPost Hub city to which you want to send the shipment. A new
HUB ID field appears for each meter setting configured on your system. You must associate a Hub
ID with each meter number.
The Hub ID is a unique four-digit number that identifies a specific city where a FedEx SmartPost
hub is located. For example, Hub ID 5531 identifies New Berlin as a FedEx SmartPost hub.
If the FedEx SmartPost enabled option is checked, you must select a Hub ID. If you do not select
an ID, the following error message appears: “FedEx SmartPost Hub ID Field cannot be left blank”.
Postal Classes Allowed
There are four main USPS postal classes. Based on your FedEx SmartPost contract, your system
is enabled for a certain class.
Delivery Confirmation Default
An optional service available for each postal class. Delivery confirmation is included by default at
the account level for all FedEx SmartPost shipments. Exceptions can be requested only at the
account level.
7-6
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-2: FedEx SmartPost Settings Fields (Continued)
Settings
Description
Auto Close Time
Available if you enabled Ground Enabled in the Ground Options section of the FedEx SmartPost
Settings tab and you selected FedEx Ground as the PickUp Carrier.
View
Allows users to view current accounts.
Add
Allows user to add additional account information.
Modify and Delete
Use the Modify and Delete buttons to update the Returns account information.
2.
Click the Tracking Numbers tab.
a. The Tracking Numbers tab shows the Delivery Confirmation Number (DCN) ranges, as shown in Figure 7-3. The Tracking Numbers
tab includes:
– FedEx SmartPost Delivery Confirmation Numbers — displays current range of Delivery Confirmation Numbers (DCN) in the
Start, End, and Current fields. See the Developer Guide for information on setting the future range of DCN to the current range.
– FedEx SmartPost Future Delivery Confirmation Numbers — contains the Start and End numbers that are received from FSMS
for a Future Range of DCNs.
– Edit Tracking Number — allows a FedEx representative (Field Level access or higher) to edit the FedEx SmartPost Delivery
Confirmation Numbers in an emergency situation.
– FedEx SmartPost Returns Tracking Numbers Prefixes — displays the Associated Returns Account tracking numbers. When
downloaded, the Associated Returns Account tracking numbers are stored in this section of the Tracking Numbers tab.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-7
Chapter 7: Coding Transactions for FedEx SmartPost
Figure 7-3: Tracking Numbers Tab
3.
Locate the FedEx SmartPost Delivery Confirmation Numbers section.
Current and future ranges of Delivery Confirmation Numbers can now be downloaded with either Field 1053 (new position 23) or with
the Demand Download Utility.
If a customer passes in a request for DCNs and a current range already exists, then the Start and End range text boxes in the FedEx
SmartPost Future Delivery Confirmation Numbers area will be populated with the new range of numbers.
In addition, at reconcile, if more than 80% of the current range has been used, then a future range will automatically download and
populate the Future range Start and End text boxes.
If the current range of DCNs is exhausted and the Future range Start and End text boxes are populated, then the Future range will
automatically move over to the Current range.
7-8
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
FedEx Express® tracking numbers and FedEx SmartPost delivery confirmation numbers are grouped under the Tracking Numbers
checkbox on the Demand Download Utility and can be selected individually when this checkbox is expanded. See Figure 7-5 to see the
new options for FedEx SmartPost DCNs.
If the current range of DCNs is less than 80% used, then the option to download FedEx SmartPost Delivery Confirmation numbers will
be grayed out.
The eight-digit delivery confirmation number is embedded in the Delivery Confirmation Bar Code printed on the FedEx SmartPost label.
A delivery confirmation number does not repeat within a 12-month period.
Configuring Handling Charges in the Meter Settings Tab
Handling charges are fixed and/or variable amounts and are a percentage of the shipping charges and/or surcharges. The Meter Settings
tab has been updated to include a new drop-down choice for handling charges for FedEx SmartPost shipments.
Configure fixed and variable handling charges for FedEx SmartPost shipments.
To configure FedEx SmartPost Handling Charges:
1.
Start the FSMS Configuration Utility.
2.
Click the “Access Privileges” button.
3.
Enter password and click “OK.” (At least User Level-View Access is needed.)
4.
Click the Meter Settings tab.
5.
On the top right of the screen, click the Handling Charges button to display the Handling Charges Dialog, as shown in Figure 7-4.
Select the Meter, Service Type, Handling Charge Calculation, Handling Charge Level, and Handling Charge Amount.
6.
Click the OK or the Copy to all Meters button.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-9
Chapter 7: Coding Transactions for FedEx SmartPost
Figure 7-4: Handling Charges Dialog for FedEx SmartPost Service Type
For U.S. outbound shipments, the handling charges will be returned in the 120 Global Ship Reply Transaction. Use the following fields in the
transaction: See Table 7-3.
• Request
–1588 - Handling Charge Type
–1595 - Handling Charge Amount or Percentage
–1606 - Handling Charge Application Point
• Reply
–1596 - Handling Charge
7-10
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-3: Handling Charges Fields
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
Handling Charge Amount or Percentage
1595-#
Max=7.2
N
I
Transactions: 020 Global Ship Request
FDXE
FDXG
FDXS
All
Handling Charge
1596
Max=11.2 N
v 10.6.1
Max=1
Optional
Handling charge as dollar amount or percentage.
If Field 1588 (Handling Charge Type) is set to 1 (Fixed handling charge
amount), Field 1595 contains a currency amount. For example, a value
of 500 means $5.00.
If Field 1588 is set to 2, 3 or 4, Field 1595 contains a percentage. For
example, a value of 500 means 5%.
Field allows up to seven (7) numeric characters, two of which are implied
decimal entries.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Transactions: 120 Global Ship Reply, 125 Rate Available Services
Reply
O
FDXE
FDXG
FDXS
Handling Charge Application Point
1606-#
Handling Charges Fields
Description
N
I
All
Charge applied by customer to the shipment. It may be either a fixed or
variable charge.
Format: 9999999.99
Decimal place is implicit.
Transactions: 020 Global Ship Request
FDXE
FDXG
FDXS
All
Optional
Specifies at which level (package or shipment) FedEx handling charges
apply.
Valid values are:
0 or blank — Handling charge applied at the package level
1 — Handling charge applied at the shipment level
Only repeat if used at the package level.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
FedEx Ship Manager® Server Developer Guide
7-11
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-3: Handling Charges Fields (Continued)
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
Handling Charge Type
1588-#
Max=1
N
Handling Charges Fields
Description
Transactions: 020 Global Ship Request
I
FDXE
FDXG
FDXS
All
Optional
Indicates the type of handling charge to be added to the net charge of the
shipment.
Valid values are:
0 — No handling charge
1 — Fixed handling charge amount
2 — Variable handling charge based on percentage of gross
transportation charge
3 — Variable handling charge based on percentage of net charge
4 — Variable handling charge based on percentage of net charge minus
Canada taxes (CA origin only)
Note: For FedEx Ground multiple-piece shipments (MPS), a value of 1,
2, 3, or 4 must be on the first package to enable variable handling charge
on any subsequent package of the MPS.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Note: You may also choose to configure a recurring handling charge type
in the FSMS Configuration Utility for your Transaction Distribution
shipments.
Setting Up FedEx SmartPost Rates
Rates and Earned Discounts can be automatically downloaded with User Level Access.
Manually Downloading FedEx SmartPost Rates
1.
Open the FedEx Demand Download Utility, as shown in Figure 7-5.
2.
Expand the Rates checkbox.
3.
Choose either FedEx SmartPost Rates and/or FedEx SmartPost Earned Discount Rates.
Note: Earned Discounts apply to all FedEx SmartPost services. New rates are downloaded and implemented only at reconcile. Earned
Discounts can also be downloaded using the Meter Registration Utility (MRU) or the Auto Configuration Utility (ACU).
4.
Ensure the correct Meter/Account is selected.
5.
Select Start.
6.
After the FedEx SmartPost files have been loaded, go to the Services window (Start > Control Panel > Administrative Tools >
Services) and locate the FedEx Rating.
7.
Right-click on the FedEx Rating and choose STOP.
8.
Locate and right-click on FedEx OpenShip and choose STOP.
9.
Go back and right-click on the FedEx Rating and choose START.
10. Locate and right-click on FedEx OpenShip and choose START.
Note: Figure 7-5 shows the Update Features checkbox, which allows customers to request FedEx SmartPost updates.
7-12
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Figure 7-5: Demand Download Utility
FedEx SmartPost Doc-Tab Settings
FedEx SmartPost is a FedEx contract-only service that can be configured on the FedEx SmartPost Settings tab within the FSMS
Configuration Utility. A minimum of User Level - View access is required to view the FedEx SmartPost settings tab. You can print
customizable labels using the 4" x 8" thermal label size with and without doc-tabs for FedEx SmartPost shipments.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-13
Chapter 7: Coding Transactions for FedEx SmartPost
FedEx SmartPost Shipping Label Default Doc-Tab Fields
Set Field 1619 (Doc-Tab Type) to value SP in the 070/170 Meter Query Request/Reply Transaction to configure a Doc-Tab for FedEx
SmartPost shipments on the Doc-Tab Settings tab. See Table 3-18 for descriptions of doc-tab fields for U.S. Domestic Outbound shipping
labels that will be printed in the doc-tab portion of the FedEx SmartPost label.
Configuring Customizable Doc-Tab Labels
When FedEx SmartPost is enabled, you can configure Doc-Tab labels for U.S. outbound shipments.
To configure custom FedEx SmartPost Doc-Tab labels:
1.
From the FedEx Configuration Utility, click Doc-Tab Settings.
2.
Under Shipping Type, select SmartPost, as shown in Figure 7-6.
3.
In the Doc-Tab Orientation section, select either Top or Bottom to designate how the doc-tab portion of the label exits the printer. Top
means the doc-tab exits the printer last, after the rest of the label has printed; Bottom means that the doc-tab exits the printer first,
before the rest of the label.
4.
In the Label Stock Type section, choose the type of label stock you use.
5.
Use the Doc-Tab Fields section to define information to be printed on the doc-tab. Click the drop-down menu under the Values column
and then select an item in the list. The selected value appears in the Values column and the defined heading for this value appears in
the Headings column. You may specify your own heading text by typing up to 12 characters (including spaces) in the Heading box.
When SmartPost is selected as the Shipping Type, the following fields are available in the Values drop-down list:
Field 2801 - Hub-ID
Field 2802 - Non-Machinable
Field 2803 - Non-Machinable Surcharge
Field 2800 - List Non-Machinable Surcharge
Field 2804 - Delivery Confirmation Service Surcharge
Field 2417 - SmartPost Service Type/Postal Indicia
Field 2416 - Ancillary Endorsements
Field 2418 - Delivery Confirmation Bar Code
Field 2425 - SmartPost Customer ID
Field 4926 - Preassigned Delivery Confirmation Tracking Number
Field 4927 - Delivery Confirmation Tracking Number
You can enable the Reference checkbox to have this field included on the label when it is printed. Normally, doc-tab fields are printed
on the doc-tab section of the label, which is removed before shipping. A Reference field enables you to include any FedEx field on the
label itself so that the recipient will be able to see the information.
Note: The Reference fields do not apply to Freight and are disabled.
6.
Optionally, click Copy to All Meters to copy the Doc-Tab Settings information for the selected meter to all meters in the same origin
country.
7.
Click Apply or Apply and Exit to save your selections.
7-14
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Figure 7-6: FedEx SmartPost Doc-Tab Settings Tab
Configuring FedEx SmartPost Reports
To configure FedEx SmartPost Detail report and a Manifest report, see “Printing FedEx SmartPost Reports” on page 7-18 for information on
how to configure these reports.
To configure a FedEx SmartPost Detail or Returns report:
1.
From the FedEx Configuration Utility shown in Figure 7-7, click Report Settings.
2.
Under the Report > SmartPost list, click the Detail option or the Returns option, as shown in Figure 7-7.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-15
Chapter 7: Coding Transactions for FedEx SmartPost
Figure 7-7: FedEx SmartPost Report Settings Tab
To configure a FedEx SmartPost Manifest Report:
3.
7-16
Click the Manifest option, as shown in Figure 7-8.
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Figure 7-8: FedEx SmartPost Detail Report Screen
When the FedEx SmartPost Detail, Manifest or Returns Report option is selected, the following fields display on the FedEx SmartPost
Report Settings Screen:
• Copy To All Meters checkbox
• Copy To All Reports checkbox
• Report Format drop down
• Printer field and icon
• Directory field and icon
4.
Select the Headings and values to print in the Doc-Tab portion of the label.
5.
Click Apply or Apply & Exit.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-17
Chapter 7: Coding Transactions for FedEx SmartPost
Printing FedEx SmartPost Reports
FedEx SmartPost Detail Report
Print this report in a
• 007/107 End-of-Day Close transaction for FedEx SmartPost, and set Field 3025 (Carrier Code) to FDXS.
• 095/195 Label Reprint transaction, and set Field 1373 (Report Code) to 67.
Print this report in the following formats:
• Word document (.doc)
• Rich Text File (.rtf)
• Text only (.txt)
• Portable Document Format (.pdf)
Figure 7-9 shows a FedEx SmartPost Detailed Report.
7-18
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Figure 7-9: FedEx SmartPost Detailed Report, Page 1 of 2
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-19
Chapter 7: Coding Transactions for FedEx SmartPost
Figure 7-10: FedEx SmartPost Detail Report, Page 2 of 2
7-20
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
FedEx SmartPost Manifest Report
The Manifest Report shows FedEx SmartPost shipments in which Ground only is the pickup carrier, and it only includes the FedEx
SmartPost Delivery Confirmation Numbers.
Print this report in a:
• 007/107 End-of-Day Close transaction for FedEx SmartPost, and set Field 3025 (Carrier Code) to FDXS.
• 095/195 Label Reprint transaction, and set Field 1373 (Report Code) to 69.
Print this report in the following formats:
• Word document (.doc)
• Rich Text File (.rtf)
• Text only (.txt)
• Portable Document Format (.pdf)
Note: The layout of this report is the same as the Ground Pickup Manifest.
Figure 7-11 shows a FedEx SmartPost Manifest Report.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-21
Chapter 7: Coding Transactions for FedEx SmartPost
Figure 7-11: FedEx SmartPost Manifest Report
7-22
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
FedEx SmartPost Returns Report
Print this report:
• On demand using the Report Viewer Utility.
For information about the Report Viewer Utility, see Chapter 14: FedEx Ship Manager Server Utilities.
• In an 095/195 Label Reprint transaction, and set Field 1373 (Report Code) to 69.
Print this report in the following formats:
• Word document (.doc)
• Rich Text File (.rtf)
• Text only (.txt)
• Portable Document Format (.pdf)
Figure 7-12 shows a FedEx SmartPost® Returns Report.
Figure 7-12: FedEx SmartPost Returns Report
Ground, FSMS generates the FedEx Ground Pickup Manifest and closes the shipment.
Shipping to Military Locations
For FedEx SmartPost shipments, you can ship to the following military locations:
• Army/Air Force Post Office (APO)
• Fleet Post Office (FPO)
• Diplomatic/Defense Post Office (DPO)
FSMS now validates the Recipient City and State Fields as follows for shipments to these locations.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-23
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-4: APO, FPO, and DPO Military State Codes
Field
Field Name
Allowed Value
15
Recipient City
FSMS shall allow Field ID 15 (Recipient City) to be
passed in the 020 Global Shipping Request
transaction with a value of *PO (ex: APO, FPO, or
DPO) if one of the APO/FPO/DPO state codes is
passed in for SmartPost shipments.
16
Recipient State/Province
AA — Armed Forces Americas
AE — Armed Forces Europe
AP — Armed Forces Pacific
Because packages shipped to the APO/FPO/DPO locations are potentially dutiable, the USPS is requiring ALL customers to use the
appropriate form when shipping APO/FPO/DPO packages, regardless of weight. To learn more about the customs/USPS requirements and
to complete/print the forms online, go to the USPS website: http://webapps.usps.com/customsforms/.
Invalid Transactions
• If a customer is attempting to process a FedEx SmartPost shipment to one of the AA, AE, or AP state codes and if the recipient city
(Field 15) begins with any value other than *PO, then Error Message 2731, “The city name must begin with APO, FPO, or DPO for this
destination” is returned, and the transaction fails.
If a customer is attempting to process a FedEx SmartPost shipment to one of the AA, AE, or AP state codes, and if the recipient postal code
(Field 17) is not in the FSMS database, then Error Message 0254, “Invalid ZIP code or no service offered to destination” is returned, and the
transaction fails.
FedEx SmartPost Returns Service
FedEx SmartPost® Returns service provides your customers with the convenience of U.S. Postal Service® access points for returns, as well
as free package pickup from their home or business address.
FedEx SmartPost Returns is contract-only service and is ideal for customers with high-volume returns (100 average daily volume) and
provides your customers with a convenient returns method for low-weight residential packages. It’s a cost-effective, reliable solution that
utilizes the strength of the FedEx® network and all public access points of the U.S. Postal Service® (USPS). In addition, FedEx SmartPost
Returns provides visibility throughout the returns process to your customer service and operations departments, as well as to the return
shipper.
How it Works
When FedEx SmartPost Returns service is chosen, you will include a prepaid Print Returns Label in your original shipment, or E-mail the
link to the Returns Label along with return instructions. The customer puts the label on the package and drops off the package at USPS
access points. Once your customers’ returns packages are picked up by the USPS, they’ll be consolidated into larger shipments at local
post offices and picked up by FedEx for shipment to you.
Features
• A prepaid USPS® integrated return shipping label. This means your customers don’t have to stand in line at a shipping location to obtain
the proper documentation and they don’t incur any out-of-pocket expenses.
7-24
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
• USPS daily pickup options of Monday through Saturday. This means your customer can drop off their package at a local post office, a
postal collection box or their own mailbox; or they can go to www.usps.gov/pickup to request a free USPS package pickup at their home
or business address.
• Coverage to every residential address in the U.S., including APO and FPO destinations.
• Transit times of 2 to 7 business days. This means you can quickly and efficiently cycle returned products back into inventory for faster
redeployment into the market — generating revenue and reducing the effects of product depreciation.
• Maximum package weight of 70 lbs.
• No residential or Saturday pickup surcharges.
• Inbound shipment visibility via FedEx InSight®. FedEx InSight e-mail notifications provide timely and automatic status information about
your incoming FedEx SmartPost return packages and include an estimated delivery date — assigned when the FedEx SmartPost origin
hub receives the package — enabling you to plan accordingly. Visibility via FedEx InSight also provides your customers with an up-tothe-minute view of their return, so they’re not spending time calling your customer service department for shipment-status updates.
• Customer reports via FedEx® Reporting Online.
• Limit of liability is $100.
To use the returns service, set the SmartPost Service Type /Postal Indicia (Field 2417) to value 7 (FedEx SmartPost Returns).
The following services do not apply for FedEx SmartPost Returns shipments:
• Delivery Confirmation
• Ancillary Endorsements
For FedEx SmartPost Returns, FedEx Ship Manager Server:
• SupportsFedEx SmartPost® Print ReturnProvides the ability to request Delivery and Shipment E-mail Notifications.
A FedEx SmartPost Returns shipment (print return) may be deleted prior to close via the 023/123 Delete Transaction Request/Reply. To
delete a FedEx SmartPost Returns shipment (E-mail Label), set Field 3025 (Carrier Code) to FDXS in the 033/133 Delete E-Mail Label
Request/Reply Transaction.
Note: Field 2417 is also used in the 020 Request/Reply transactions.
Pay Types
The pay type for FedEx SmartPost Returns is either the sender or the account.
• If a customer is processing an 020 Global Ship Request for a FedEx SmartPost Returns shipment with Field 2417 (Smart Post Service
Type/Postal Indicia) set to value 7, and the shipper account number is the same as the returns account number, then Field 23 (Pay Type)
will be set to value 1 (Bill Shipper).
• If a customer is processing an 020 Global Ship Request for a FedEx SmartPost Returns shipment with Field 2417 (FedEx SmartPost
Service Type/Postal Indicia) set to value 7, and the shipper account is not the same as the returns account number, then Field 23 (Pay
Type) will be set to 6 (Bill Associated Account).
Packaging
Only customer packaging may be used in FedEx SmartPost Returns.
Maximum Number of Packages
The maximum number of packages for FedEx SmartPost Returns is 999. The maximum number of packages allowable for E-mail label is
25.
• If a customer is processing an 020 Global Ship Request for a FedEx SmartPost Returns shipment, and passes in Field 2417 (FedEx
SmartPost Service Type/Postal Indicia) set to 7 (Returns) and has greater than 999 pieces, then Error Message 216, “Total package
count cannot exceed 999” is returned, and the transaction fails.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-25
Chapter 7: Coding Transactions for FedEx SmartPost
•
Package Size
The minimum package size must be 6" L x 4" W x 1" H. The maximum package size cannot exceed 130”, which is the sum of the length plus
girth (2 x height + 2 x width.
Note: Setting package dimensions are not required.
• If a customer is processing an 020 Global Ship Request for a FedEx SmartPost Returns shipment, and sets Fields 57 (Height), 58
(Width), and 59 (Length) with values that are less than the minimum required 6" L x 4" W x 1" H, then Error Message 0338, “Must equal
or exceed the minimums for Length, Height, or Length + Girth” is returned, and the transaction fails.
• If a customer is processing an 020 Global Ship Request for a FedEx SmartPost Returns shipment, and sets Fields 57 (Height), 58
(Width), and 59 (Length) with values that make the sum of the length plus the girth (2 x height + 2 x width) exceed 130", then Error
Message 0421, “Length & Girth combined cannot be greater than the maximum allowed,” is returned, and the transaction fails.
• If a customer is processing an 020 Global Ship Request for a FedEx SmartPost Returns shipment, and sets Fields 57 (Height), 58
(Width), and 59 (Length) to any value that exceeds 60", then Error Message 2646, “Dimensions cannot exceed 60 inches for FedEx
SmartPost package,” is returned, and the transaction fails.
Package Weight
Weight return limit is the same as outbound shipments - 70 lbs. The actual package weight is captured and passed in the return shipment
request.
• If a customer is processing an 020 Global Ship Request for a FedEx SmartPost Returns shipment, and sets Field 1670 (Package Weight/
Shipment Weight) to 7001 or greater with Field 75 (Weight Units) set to LBS, then Error Message 0270, “The weight limit for this service
type has been exceeded,” is returned, and the transaction fails.
Declared Value
Declared value does not apply to FedEx SmartPost shipments.
If a customer is processing an 020 Global Ship Request for a FedEx SmartPost Returns shipment, and sets Fields 26 (Declared Value/
Carriage Value) or 69 (Declared Value/Carriage Value) and all other shipping data is valid, then the shipment will be successful, but the tags
will be ignored.
Other Regulated Materials - Domestic
Other Regulated Materials (ORM) does not apply to FedEx SmartPost shipments.
If a customer is processing an 020 Global Ship Request for a FedEx SmartPost Returns shipment, and sets Field 1268(Dry Ice) to Y and all
other shipping data is valid, then the shipment will be successful, but the tag will be ignored.
7-26
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Special Services
Special Services, such as HAL, COD, DG, and so on, are not available with any FedEx SmartPost shipments.
• If a customer is processing an 020 Global Ship Request for a FedEx SmartPost Returns shipment, and sets Field 1200 (Hold at Location)
to Y and all other HAL fields and all other shipping data is valid, then the shipment will be successful, but the tag will be ignored.
• If a customer is processing an 020 Global Ship Request for a FedEx SmartPost Returns shipment, and sets Field 2399 (Signature
Required Type) to 1, 2, 3, or 4 and all other Signature Services fields and all other shipping data is valid, then the shipment will be
successful, but the tag will be ignored.
• If a customer is processing an 020 Global Ship Request for a FedEx SmartPost Returns shipment, and sets Fields 1960 (Exception
Notification Flag), 1961 (Shipper Exception Notification Flag), or 1962 (Recipient Exception Notification Flag) to Y and all other Exception
Notification fields and all other shipping data is valid, then the shipment will be successful, but the tag will be ignored.
• If a customer is processing an 020 Global Ship Request for a FedEx SmartPost Returns shipment and sets any of the editable fields
received from the system for an Associated Returns Account with data other than what is stored in the FSMS database, then the editable
fields passed in the transaction will take precedence and the shipment will succeed.
• If a customer is processing an 020 Global Ship Request for a FedEx SmartPost Returns shipment and passes in any of the non-editable
fields received from the system for an Associated Returns Account with data other than what is stored in the FSMS database, the noneditable fields passed in the transaction will be ignored and defaulted back to the FedEx SmartPost configuration and the shipment will
succeed.
• If a customer is processing an 020 Global Ship Request for a FedEx SmartPost Returns shipment and the return address being used
cannot be found in the FSMS database, then Error Message 2742, “The recipient account number is not a valid FedEx SmartPost
Returns account number,” is returned, and the transaction fails.
Note: See Table 7-10 on page 7-59 and Table 7-11 on page 7-77 for more information about Return Labels.
FedEx SmartPost Labels
Print-As-You Go Labels for FedEx SmartPost
FedEx SmartPost customers can now generate shipping labels using both the FSMS Open Ship and Print-As-You-Go (PAYG) features.
However, when using the FSMS Open Ship and PAYG FedEx SmartPost features, Print-As-You-Go-Labels can only be non-associated;
that is, there can be no association between the individual package number and the total number of packages, such as 1 of 3, 2 of 3, 3 of 3.
The following examples show how to print labels as you process packages in 020 Global Ship Request transactions, rather than waiting for
the final confirmation.
1.
This example shows how to create and print a label:
0,"020"1,"Print As You Go - create/print"11,"COMPANY"12,"ROGER RECIPIENT"13,"123 Main
Street"14,"Suite 200"15,"Memphis"16,"TN"17,"38116"18,"8005551212"23,"1"25,"Bound Printed
Matter"50,"US"75,"lbs"117,"US"187,"188"498,"124765"537,"\\127.0.0.1\ZP5"541,"YNNNNNNNN"542,
"AA8822"1670,"75"2416,"01"2417,"3"2600,"4"99,""
2.
This example shows how to add a package and print a label:
0,"020"1,"Print As You Go - add/print"11,"COMPANY"12,"ROGER RECIPIENT"13,"123 Main
Street"14,"Suite 200"15,"Memphis"16,"TN"17,"38116"18,"8005551212"23,"1"25,"Bound Printed
Matter"26,"100"50,"US"75,"lbs"117,"US"187,"188"498,"124765"537,"\\127.0.0.1\ZP5"541,"NNNYNN
NNN"542,"AA8811"1670,"50"2416,"01"2417,"3"2600,"4"99,""
3.
This example shows how to add another package and print a label:
0,"020"1,"Bound PM - Print As You Go - add another and print"11,"COMPANY"12,"ROGER
RECIPIENT"13,"123 Main Street"14,"Suite
200"15,"Memphis"16,"TN"17,"38116"18,"8005551212"23,"1"25,"Bound Printed
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-27
Chapter 7: Coding Transactions for FedEx SmartPost
Matter"26,"100"50,"US"75,"lbs"117,"US"187,"188"498,"124765"537,"\\127.0.0.1\ZP5"541,"NNNYNN
NNN"542,"AA8811"1670,"40"2416,"01"2417,"3"2600,"4"99,""
4.
This example confirms a Print-As-You-Go FedEx SmartPost shipment transaction:
0,"020"1,"Print As You Go - confirm"11,"COMPANY"12,"FXRS"13,"123 Main Street"14,"Suite
200"15,"Memphis"16,"TN"17,"38116"18,"8005551212"25,"Bound Printed
Matter"50,"US"75,"lbs"116,"2"117,"US"187,"188"498,"124765"537,"\127.0.0.1ZP5"541,"NNNNNNNNY
"542,"AA8811"2416,"3"2417,"3"2600,"4"99,""
Label Formats
The type of label that prints for your FedEx SmartPost shipment is determined by the configured carrier type within your FSMS system
integration.
There are two types of labels, each shown in Figure 7-13 and Figure 7-14.
• FedEx SmartPost label — FedEx SmartPost is the pickup carrier.
• Parcel Select Integrated label — FedEx Ground is the pickup carrier.
FedEx SmartPost labels can only be produced on printers that are supported by FSMS. The following label formats are supported for FedEx
SmartPost:
• 4" x 6" and 4" x 8" thermal labels with and without Doc-Tab.
• 4" x 8" Customizable thermal labels
• 4" x 6" Portable Network Graphic (PNG)
• 8-1/2" x 11" Plain paper labels (laser labels) using Device Independent Bitmap (DIB)
• Portable Document Format (.pdf)
FedEx SmartPost Label Samples
The following samples show the two types of labels available for FedEx SmartPost shipping.
FedEx SmartPost Label
The FedEx SmartPost label is the label type that FSMS uses when FedEx SmartPost is the pickup carrier. FedEx SmartPost label is shown
in Figure 7-13. This sample label is for Media service with USPS delivery confirmation. Refer to the following Delivery Confirmation and Bar
Code Reference topics for an explanation of the data in these sections of the label.
7-28
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Figure 7-13: FedEx SmartPost Media Service with USPS Delivery Confirmation Label
Integrated Label
An Integrated label is the label type that FedEx uses when FedEx Ground is the pickup carrier. Figure 7-14 shows a sample Integrated label.
The integrated label contains the FedEx Ground bar code in addition to the USPS Confirmation bar code, postal indicia, ancillary
endorsements and other USPS information.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-29
Chapter 7: Coding Transactions for FedEx SmartPost
Figure 7-14: FedEx SmartPost Integrated Label, Sample 1
7-30
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Figure 7-15: FedEx SmartPost Integrated Label, Sample 2
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-31
Chapter 7: Coding Transactions for FedEx SmartPost
Figure 7-16 describes the components of the label stamp.
Postal Indicia (“Stamp”) Options
-Parcels < 1lb = Presorted Stamp (Prst 5td)
-Parcels > = 1lb = Parcel Select
-Parcels-Bound Printed Matter rst BPM
Figure 7-16: FedEx SmartPost Label Stamp
Figure 7-17 shows the components of the Delivery Confirmation Number (DCN) that displays on the label.
Application ID 420
Postal Code
Application ID 91
Tracking Number
Figure 7-17: Delivery Confirmation Number from Label
The Delivery Confirmation Number consists of the following:
• Application ID 420
• Postal Code
• Application ID 91
• Tracking Number
–2-digit service type code
–9-digit DUNS Number
–8-digit Parcel ID
–1-digit MOD 10 check digit
The last 20 digits of the Delivery Confirmation Number are the tracking number, also found in Field 29 (Tracking Number).
7-32
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Requesting a Rate Quote for FedEx SmartPost
Use the 020/120 Global Ship Request/Reply transaction to request rate quotes for FedEx SmartPost. To obtain a FedEx SmartPost courtesy
rate quote, set Field 1234 (Rate Information) to 1 — Rate Quote.
FedEx SmartPost 120 Global Ship Reply Rate Quote
Table 7-4 describes the fields returned in a FedEx SmartPost rate quote reply using a 120 Global Ship Reply Transaction.
Table 7-5: FedEx SmartPost Rate Quote Reply Fields
Transaction: 120 Global Ship Reply
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
Handling Charges Fields
Description
O
FDXS
US
Returned base transportation charge before discounts and surcharges.
O
FDXS
US
Returned value is zero (0) USD for FedEx SmartPost shipments.
O
FDXS
US
Returned value is zero (0) USD for FedEx SmartPost shipments.
Base Charge
34
Max=11.2 N
Total Surcharge Amount
35
Max=11.2 N
Total Discount Amount
36
Max=11.2 N
Note: All discounts, including Earned Discounts, if applicable, are
calculated as part of your TOTAL DISCOUNT AMOUNT, Field 36 and
thus calculated as part of your NET CHARGE AMOUNT, Field 37.
Net Charge
37
Max=11.2 N
O
FDXS
US
Returned Net Charge equals the Base Charge plus Total Surcharge
Amount minus Total Discount Amount: Field 34 + Field 35 - Field 36 =
Field 37.
Note: All discounts, including Earned Discounts, if applicable, are
calculated as part of your TOTAL DISCOUNT AMOUNT, Field 36 and
thus cal cu al ted as part of your NET CHARGE AMOUNT, Field 37.
For information about 020/120 Global Ship Request/Reply transactions, see Chapter 2: About FedEx Ship Manager Server Transactions in
this guide and the FedEx Ship Manager® Server Transaction Coding Reference Guide.
Closing a FedEx SmartPost Shipment
You can close your FedEx SmartPost shipments and create a shipping manifest at any time. You can also carry over shipping from the
previous day or for several days. When you close your FedEx SmartPost shipments, you can create a separate manifest for each Meter
number associated with a FedEx SmartPost Hub ID if you have configured this association in the FSMS Configuration Utility dialog in the
Meter Settings tab.
FedEx SmartPost does not require a fully-coded 007 End-of-Day Close Request transaction, but it does use the 007 transaction functions to
perform the close. However, a manifest file must be created to ship FedEx SmartPost, and this is generated during the Close request.
Note: When you perform a 007 End-of-Day Close Request transaction using Field 2413 (Close All Meters Flag), a separate FedEx
SmartPost manifest is created for each Meter number associated with a Hub ID.
Table 7-5 lists the fields you must use in a FedEx SmartPost 007 End-of-Day Close Request transaction.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-33
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-6: End-of-Day Close Fields for FedEx SmartPost Shipment
Action
Field ID
Field Name
Description
Transaction: 007/107 End-of-Day Close
To close all meters and produce a FedEx SmartPost Set to Y.
Manifest
Example: 2413,"Y"
Use…
Field 2413
Close All Meters Flag
Closes all meters on the server when Field 2413 is set to Y and Field 3025 is passed
in the same transaction.
To specify carrier code at end-of-day close
Set to FDXS to perform a separate FedEx SmartPost End-of-Day Close.
Use…
You may close your FedEx SmartPost shipment at the same time you close your
other FedEx shipments or close your FedEx SmartPost shipment separately. Valid
values are:
FDXS — Use this code if requesting Close for FedEx SmartPost only.
FDXA — Use this code if closing all carriers at the same time (default when field is
blank).
Note: Be sure FedEx SmartPost shipping is ready to manifest before performing a
Close All (Code=FDXA).
Field 3025
Carrier Code
Note: See the FedEx Ship Manager® Server Transaction Coding Reference Guide for details about Field 2413 and Field 3025.
FedEx SmartPost Manifest
An electronic upload of the manifest for FedEx SmartPost shipments occurs when you send a 007 End-of-Day Close Request transaction to
close out shipments in a trailer. If you choose, you can continue to create FedEx SmartPost shipments over many days until you have
processed all packages required to fill a trailer and at that time, send the 007 transaction to generate the electronic upload of the manifest.
The maximum number of packages allowed per manifest is 99,999. If a trailer is not filled and the maximum number of packages has been
reached, you must perform a Close. You can create a new manifest for the remaining portion of the trailer.
Closing with FedEx Ground as Carrier
When you perform a 007 End-of-Day Close Request transaction for a FedEx SmartPost shipment, if the designated carrier is FedEx
Delivery Confirmation Changes
The customer will not be able to turn Delivery Confirmation ON or OFF at the shipment level. Delivery confirmation is defaulted to “Y” for all
FedEx SmartPost Shipments. Delivery Confirmation exceptions are requested and set up at the account level.
Shipment and Delivery E-Mail Notifications
Delivery and shipment e-mail notifications for U.S. outbound shipments are now available. The fields in Table 7-6 may be passed in the 020
Global Ship Request for a U.S. outbound shipment. However, exception notifications are not available for FedEx SmartPost shipments.
7-34
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-7: E-Mail Notification Fields for FedEx SmartPost Shipments
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
SmartPost E-Mail Notification Fields
Description
I
FDXE
FDXG
FDXS
All
Optional
E-Mail address of the Shipper. Use this field if you want e-mail notification
sent to sender/shipper.
I
FDXE
FDXG
FDXS
All
REQUIRED*
E-Mail address of the Recipient.
I
FDXE
FDXG
FDXS
All
Field Level: Shipment except for FedEx® International DirectDistribution
Surface Solutions (IDD Surface), FedEx International Priority
DirectDistribution (IPD), FedEx International Priority DirectDistribution®
Freight (IDF) and FedEx International Economy DirectDistribution
Service (IED).
Optional
Personal customer-specified message that is delivered with all selected
notifications (FedEx ShipAlert, delivery, or exception).
Use in conjunction with Fields 1202 (Recipient’s E-mail Address), 1201
(Sender's E-mail Address), 1343 (Broker E-mail Address), and 1204
(Other E-mail Notification Addresses).
Sender's E-mail Address
1201
Max=120 A
Recipient’s E-mail Address
1202
Max=120 A
Personal Message
1203
Max=120 A
Note: Personal messages are not applicable with wireless formatted
notifications. If wireless format is selected for personal message, the
personal message will be ignored. Personal messages should only be
entered in English characters.
Other E-mail Notification Addresses
1204
v 10.6.1
Max=120 A
I
FDXE
FDXG
FDXS
All
REQUIRED*
E-mail address of others not specified in Fields 1201 (Sender's E-mail
Address), 1202 (Recipient’s E-mail Address) or 1343 (Broker E-mail
Address).
*Required when Field 1206 (Other ShipAlert Notification Flag) is set to Y.
Use Field 1551 (Other Delivery Notification Flag (POD)) to send e-mail
notifications of delivery to addresses listed in Field 1204.
Maximum of three (3) occurrences allowed.
FedEx Ship Manager® Server Developer Guide
7-35
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-7: E-Mail Notification Fields for FedEx SmartPost Shipments (Continued)
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
SmartPost E-Mail Notification Fields
Description
Other ShipAlert Notification Flag
1206
Max=1
A
I
FDXE
FDXG
FDXS
All
Field Level: Shipment.
REQUIRED*
Indicates whether FedEx ShipAlert notification is enabled.
Valid values are:
Y — Enables FedEx ShipAlert notification
N — Disables FedEx ShipAlert notification (default)
If Field 1206 is set to Y, Field 1204 (Other E-mail Notification Addresses)
must also be set to Y.
Maximum of three (3) occurrences.
O
FDXE
FDXG
FDXS
All
REQUIRED*
Provides e-mail notification of delivery to e-mail addresses entered in
Field 1204 (Other E-mail Notification Addresses).
Maximum of three (3) occurrences.
I
FDXE
FDXG
FDXS
All
REQUIRED*
Indicates the language for all notifications (delivery, ShipAlert, exception)
sent to Field 1204 () if not in English.
Maximum of three (3) occurrences.
Valid values are:
da — Danish
de — German
en — English (default)
es — Spanish (Latin America)
es — Spanish (Spain)-Locale=ES
fr — French (Canada)-Locale=CA
fr — French (Europe)
it — Italian
ja — Kanji (Japan)
ko — Korean
nl — Dutch
pt — Portuguese
sv — Swedish
zh — Chinese (Simplified)-Locale=CN
zh — Chinese (Taiwan)-Locale=TW
zh — Chinese (Hong Kong)-Locale=HK
All
Field Level: Shipment
REQUIRED*
*Required to provide e-mail notification of delivery to the Shipper.
Other Delivery Notification Flag (POD)
1551
Max=1
A
Other Language Code
1552
Max=2
A
Shipper Delivery Notification Flag (POD)
1553
7-36
Min= 1
N
Max=11.2
I
FDXE
FDXG
FDXS
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-7: E-Mail Notification Fields for FedEx SmartPost Shipments (Continued)
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
SmartPost E-Mail Notification Fields
Description
I
FDXE
FDXG
FDXS
All
Field Level: Shipment
REQUIRED*
*Required to provide e-mail notification of shipment to the shipper.
I
FDXE
FDXG
FDXS
All
REQUIRED*
Indicates the language of the Shipper Delivery, ShipAlert, and Exception
e-mail if notification is to be in a language other than English.
Valid values are:
da — Danish
de — German
en — English (default)
es — Spanish (Latin America)
es — Spanish (Spain)-Locale=ES
fr — French (Canada)-Locale=CA
fr — French (Europe)
it — Italian
ja — Kanji (Japan)
ko — Korean
nl — Dutch
pt — Portuguese
sv — Swedish
zh — Chinese (Simplified)-Locale=CN
zh — Chinese (Taiwan)-Locale=TW
zh — Chinese (Hong Kong)-Locale=HK
Shipper ShipAlert Flag
1554
Max=1
A
Shipper Language Code
1555
Max=2
A
Recipient Delivery Notification Flag (POD)
1556
Max=1
A
I
FDXE
FDXG
FDXS
All
REQUIRED*
Required to provides e-mail notification of delivery to the Recipient.
I
FDXE
FDXG
FDXS
All
REQUIRED*
Required to provide e-mail notification of shipment to the Recipient.
Recipient ShipAlert Flag
1557
v 10.6.1
Max=1
A
FedEx Ship Manager® Server Developer Guide
7-37
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-7: E-Mail Notification Fields for FedEx SmartPost Shipments (Continued)
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
SmartPost E-Mail Notification Fields
Description
I
FDXE
FDXG
FDXS
REQUIRED*
Indicates the language of the Recipient Delivery, ShipAlert, and
Exception e-mail if notification is to be in a language other than English.
Valid values are:
da — Danish
de — German
en — English (default)
es — Spanish (Latin America)
es — Spanish (Spain)-Locale=ES
fr — French (Canada)-Locale=CA
fr — French (Europe)
it — Italian
ja — Kanji (Japan)
ko — Korean
I
FDXE
FDXG
FDXS
Recipient Language Code
1558
Max=2
A
E-mail Notification Format
1964
Max=1
A
All
Field Level: Shipment except for FedEx International DirectDistribution
Surface Solutions (IDD Surface) and IPD/IDF/IED.
Optional
Indicates selected format for e-mail notification.
Each field occurrence must correspond to each occurrence of Field 1204
(Other E-mail Notification Addresses).
Maximum of three (3) occurrences allowed.
Valid values are:
H — HTML
T — Text (default)
W — Wireless
Note: Text is not valid for language/locale codes: ja, ko, zhCN, zhHK,
and zhTW. Invalid code results in HTML format.
Wireless formatted notifications do not apply to Field 1203 (Personal
Message).
7-38
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-7: E-Mail Notification Fields for FedEx SmartPost Shipments (Continued)
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
SmartPost E-Mail Notification Fields
Description
Shipper E-mail Notification Format
1965
Max=1
A
I
FDXE
FDXG
FDXS
All
Field Level: Shipment except for FedEx International DirectDistribution
Surface Solutions (IDD Surface) and IPD/IDF/IED.
Optional
Indicates selected format for e-mail notification to Shipper.
You can specify a different format for Field 1201 (Sender's E-mail
Address). This format will apply to all notifications sent to this e-mail
address.
Valid values are:
H — HTML
T — Text (default)
W — Wireless
Note: Text is not valid for language/locale codes: ja, ko, zhCN, zhHK, and
zhTW. Invalid code results in HTML format.
Wireless formatted notifications do not apply to Field 1203 (Personal
Message).
FDXE
FDXG
FDXS
INTL
Field Level: Shipment except for FedEx International DirectDistribution
Surface Solutions (IDD Surface) and IPD/IDF/IED.
Optional
Indicates selected format for e-mail notification to the Broker.
You can specify a different format for Field 1343 (Broker E-mail Address).
This format will apply to all notifications sent to this e-mail address.
Valid values are:
H — HTML
T — Text (default)
W — Wireless
Note: Text is not valid for language/locale codes: ja, ko, zhCN, zhHK, and
zhTW. Invalid code results in HTML format.
Wireless formatted notifications do not apply to Field 1203 (Personal
Message).
Broke E-Mail Notification Format
1966
v 10.6.1
Max=1
A
I
FedEx Ship Manager® Server Developer Guide
7-39
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-7: E-Mail Notification Fields for FedEx SmartPost Shipments (Continued)
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
SmartPost E-Mail Notification Fields
Description
I
FDXE
FDXG
FDXS
INTL
Field Level: Shipment except for FedEx International DirectDistribution
Surface Solutions (IDD Surface) and IPD/IDF/IED.
REQUIRED*
Indicates locale associated with language code in Field 1552 (Other
Language Code).
*Required when using Field 1552 and the language code requires a
locale code.
Maximum of three (3) occurrences.
Valid Locale values are:
ES — Spanish (Spain)
CA — French (Canada)
CN — Chinese (Simplified)
HK — Chinese (Hong Kong)
TW — Chinese (Taiwan)
Default: None, unless Field 1552 = zh, then default is CN. Invalid values
do not default.
I
FDXE
FDXG
FDXS
All
Field Level: Shipment except for FedEx International DirectDistribution
Surface Solutions (IDD Surface) and IPD/IDF/IED.
REQUIRED*
Indicates locale associated with language code in field (Shipper
Language Code)
*Required when using Field 1555 and the language code requires a
locale code.
Valid Locale values are:
ES — Spanish (Spain)
CA — French (Canada)
CN — Chinese (Simplified)
HK — Chinese (Hong Kong)
TW — Chinese (Taiwan)
Default: None, unless Shipper Language Code (1555) = zh, then CN.
Invalid combinations will not default.
Language Locale Code
1968
Max=2
A
Shipper Locale Code
1969
7-40
Max=2
A
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-7: E-Mail Notification Fields for FedEx SmartPost Shipments (Continued)
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
Recipient Locale Code
1970
Max=2
A
SmartPost E-Mail Notification Fields
Description
Transactions: 020 Global Ship Request
I
FDXE
FDXG
FDXS
All
Field Level: Shipment except for FedEx International DirectDistribution
Surface Solutions (IDD Surface) and IPD/IDF/IED.
REQUIRED*
Indicates locale associated with language code in Field 1558 (Recipient
Language Code).
*Required when using Field 1558 and the language code requires a
locale code.
Valid Locale values are:
ES — Spanish (Spain)
CA — French (Canada)
CN — Chinese (Simplified)
HK — Chinese (Hong Kong)
TW — Chinese (Taiwan)
Default: None, unless Recipient Language Code (1558) = zh, then CN.
Invalid combinations will not default.
Tracking FedEx SmartPost Shipments
FedEx recommends that you use the FedEx Web Services options for integrating FedEx shipment tracking functions into your applications.
You can find information about FedEx Web Services on the Developer Resource Center at fedex.com/developer.
FedEx SmartPost Transactions
FedEx SmartPost transactions use the 020 Global Ship Request transaction and other transactions such as 004 Tracking Number Request,
007 End-of-Day Close and 095 Label Reprint transactions, to ship packages, track shipments, complete shipping processes and reprint
labels.
020/120 Global Ship Request/Reply
Open Ship
When shipping FedEx SmartPost, you can select to process the shipment as a multiple-piece or Open Ship shipment. Open Ship allows you
to create a single FedEx shipment and add pieces to the shipment over a period of time. The Open Ship process requires an initial
transaction to create the shipment and several sequential transactions to add pieces until you are ready to confirm the shipment. Chapter 4:
FedEx Ship Manager Server Open Ship Transactions for information about Open Ship transactions.
Special Services
FedEx SmartPost transactions do not support the shipping of dry ice, alcohol, dangerous goods and other time-critical package shipments.
Special services such as Collect on Delivery (C.O.D.), Hold At Location (HAL), Inside Pickup and Delivery, Broker Select Options (BSO) and
Delivery Signature Options are also not available.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-41
Chapter 7: Coding Transactions for FedEx SmartPost
Rate Quotes and Track Shipments
Use the 020/120 Global Ship Request/Reply transaction to request rate quotes and track your shipment. Transactions track packages using
the Delivery Confirmation Number (DCN) assigned to each FedEx SmartPost package, and if FedEx Ground is the pickup carrier, you can
track by FedEx Ground tracking numbers. FedEx SmartPost customers can track their shipments at fedex.com.
See “Requesting a Rate Quote for FedEx SmartPost” on page 7-33 and See “Future Day Shipping” on page 7-44 for more information.
004 Tracking Number Request
Use this transaction to pre-assign tracking numbers to a shipment before the shipment is processed. Pre assignment allows you to provide
tracking information to your customer before the package is created.
023 Delete Request
Use this transaction before close to delete a FedEx SmartPost print returns shipment.
024 Shipment Query Request
Use this transaction to search for FedEx SmartPost shipments in the FSMS Ship History database.
033 Delete E-Mail Label Request
Use this transaction before close to delete a FedEx SmartPost Returns shipment E-mail label.
035 Meter Registration Request
Use this transaction to download FedEx SmartPost rates using the new positions added to Field 1053.
057 Demand Download Request
Use this transaction to request updated FedEx SmartPost Rates, Earned Discounts, and Delivery Confirmation Numbers.
070 Meter Query or Configuration Request
Use this transaction to:
• Configure Doc-Tabs. To define the doc-tab portion of the FedEx SmartPost label, set Field 1619 (Doc-Tab Type) to the SP value.
See “FedEx SmartPost Shipping Label Default Doc-Tab Fields” on page 7-14.
• Configure a FedEx SmartPost Detail Report. Set Field 1373 (Report Code) to 67.
See “FedEx SmartPost Detail Report” on page 7-18.
• Configure a FedEx SmartPost Manifest Report. Set Field 1373 (Report Code) to 69.
See “FedEx SmartPost Manifest Report” on page 7-21.
• Configure a Returns Report. Set Field 1373 (Report Code) to 68.
See “FedEx SmartPost Returns Report” on page 7-23.
095 Label Reprint Request
Use this transaction to reprint FedEx SmartPost labels and to print a FedEx SmartPost:
• Detail Report; set Field 1373 (Report Code) to 67.
7-42
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
• Manifest Report; set Field 1373 (Report Code) to 69.
• Returns Report. Set Field 1373 (Report Code) to 68.
007/107 End-of-Day Close Request/Reply
Perform this transaction at the end of each shipping business day to post shipping information to FedEx and to ensure that your rating and
routing information remains current.
Use this transaction to configure a FedEx SmartPost Detail Report and Manifest Report by setting Field 3025 (Carrier Code) to FDXS.
See “Closing a FedEx SmartPost Shipment” on page 7-33 for more information.
See the FedEx Ship Manager® Server Services and Shipping Guide for information about the FedEx SmartPost features implemented by
these transactions.
Transaction Methods for FedEx SmartPost
There are two supported transaction methods for FedEx SmartPost shipments.
Single-Piece Shipment
Multiple-Piece Shipment with Option of Open Ship
A FedEx SmartPost multiple-piece shipment (MPS) works the same as a FedEx Express® U.S. domestic MPS shipment. Unlike FedEx
Express U.S. domestic shipments, there is no master/child tracking number relationship for a FedEx SmartPost multiple-piece shipment;
therefore, it is tracked and delivered as a single shipment.
FedEx SmartPost uses the Open Ship method to create a shipment and add individual pieces to the shipment over a period of time. Use
Field 541 (Open Ship Flags) in a 020 Global Ship Request transaction to ship FedEx SmartPost shipments using the Open Ship shipping
process.
You cannot modify package or shipment information after you create the Open Ship shipment and begin adding pieces for FedEx
SmartPost. Therefore, you may use all Open Ship functions except flag 5 (EDIT Piece) and flag 6 (EDIT Shipment) in Field 541.
See “Creating a FedEx SmartPost Open Ship Transaction” on page 7-88. Also see Chapter 4: FedEx Ship Manager Server Open Ship
Transactions.
Transaction Rules for FedEx SmartPost
The following rules apply to FedEx SmartPost transactions:
• FedEx SmartPost supports a ship date when passed in Field 24 (Ship Date) in a 020/120 Global Ship Request/Reply transaction.
• No commitment date is required for FedEx SmartPost shipments.
• Future Day shipping is available, regardless of who is configured as the pickup carrier.
• A new surcharge is applied (Field 2803) for Non-Machinable packages.
• A new oversize package classification has been added - balloon (Field 3124).
• The maximum package dimension (length + width + height) cannot exceed 60”.
• No canned reports are available for FedEx SmartPost.
• Only one payment types is available for FedEx SmartPost: Bill Sender.
• FedEx SmartPost supports the doc-tab function on labels. To define the doc-tab portion of the FedEx SmartPost label, use the SP value
with Field 1619 (Doc-Tab Type). Doc-Tabs can also be configured via the Doc-Tab Settings tab.
• FedEx SmartPost multiple-piece shipments (MPS) work the same as a FedEx Express U.S. domestic MPS except that there is no
master/child tracking number relationship for FedEx SmartPost MPS.
• To reprint FedEx SmartPost labels, you must use the Label Reprint Utility or the 095 Label Reprint Request transaction.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-43
Chapter 7: Coding Transactions for FedEx SmartPost
• Saturday delivery is possible by USPS, and no FedEx surcharge applies in this case.
• For Open Ship shipping, you cannot edit a FedEx SmartPost package or shipment, after you create the shipment and begin adding
pieces.
• The Alternate Return Address option is available for origin-destination addresses located in the 48 contiguous United States. The
alternate return address prints in the Return Address section of the FedEx SmartPost label if it is provided in the shipment transaction.
• For Standard Mail shipments, only one Ancillary Endorsement is permitted when delivery confirmation is requested: RETURN SERVICE
REQUESTED or ADDRESS SERVICE REQUESTED.
• You cannot change from a FedEx SmartPost carrier pickup to a Ground carrier pickup without closing out all previous FedEx SmartPost
shipments, otherwise you will get a close parameter error.
Future Day Shipping
Future Day Shipping is now available for all FedEx SmartPost shipments.
If a ship date has been provided for any FedEx SmartPost shipment, regardless of the pickup carrier, then the ship date is validated using
FedEx Ground business rules.
See the section “FedEx Ground Future Day” on page 6-18 for more information on Future Day shipping.
Table 7-8: Future Day Ship Date Field
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Ship Date
24
Max=8
Description
Transactions: 107 End-of-Day Close Reply, 020 Global Ship Request, 024 Shipment Query Request
N
I
FDXS
All
Field Level: Shipment
REQUIRED*
Date of shipment.
*Required for Future Day shipping. Format: CCYYMMDD
Default: Current meter date.
For example, July 1, 2005 is coded as: 20050701
FedEx Ground and FedEx Home Delivery® ship dates can be set up to
90 days in advance, and the ship date can be set to unlimited using the
Extend 90 Day limit — FedEx Ground checkbox in the Systems Settings
tab of the FSMS Configuration Utility.
7-44
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Coding a Basic FedEx SmartPost Shipping Transaction
Use the 020 Global Ship Request transaction to create and ship a FedEx SmartPost shipment.
Table 7-9 describes the basic fields needed to code a FedEx SmartPost transaction.
Table 7-9: Fields (Required and Optional) for FedEx SmartPost 020 Transaction
Transaction: 020 Global Ship Request - Open Ship, Multiple-Piece Shipment
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
Description
Transaction Code
0
Max=3
FDXS
US
Field Level: Shipment
REQUIRED.
Indicates the start of a transaction.
For example, 0,"020" or 0,"20" signifies the start of the 020 Global Ship
Request transaction.
Customer Transaction Identifier
1
Max=30
A
I
FDXS
US
Field Level: Shipment
Optional
The transaction identifier (ID) lets you link transaction “replies” back to the
transaction “requests” in the case of a bulk shipment. FSMS does not
require this field, but it is available and recommended for customer use.
A
I
FDXS
US
Field Level: Shipment
REQUIRED*
Company name of the Shipper.
*Required for FedEx SmartPost.
I
FDXS
US
Field Level: Shipment
REQUIRED*
Primary address line of Shipper/Sender address from which the shipment
originates.
*Required field for FedEx SmartPost.
*Required to override default settings.
I
FDXS
US
Field Level: Shipment
REQUIRED*
Second address line of Shipper/Sender address. This is the address from
which the shipment originates.
*Required field for FedEx SmartPost.
*Required to override default settings.
Shipper Information
Sender Company
4
Max=35
Sender Address Line 1
5
Max=35
A
Sender Address Line 2
6
v 10.6.1
Max=35
A
FedEx Ship Manager® Server Developer Guide
7-45
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-9: Fields (Required and Optional) for FedEx SmartPost 020 Transaction (Continued)
Transaction: 020 Global Ship Request - Open Ship, Multiple-Piece Shipment
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I
FDXS
US
Field Level: Shipment
REQUIRED*
City name for the Shipper/Sender address. This is the city where the
shipment originates.
*Required field for FedEx SmartPost.
*Required to override default settings.
A
I
FDXS
US
Field Level: Shipment
REQUIRED*
State or province code of the Shipper/Sender address.
*Required field for FedEx SmartPost.
*Required to override default settings.
See Appendix C in the Transaction Coding Reference Guide for a list of
country codes.
A
I
FDXS
US
Field Level: Shipment
REQUIRED*
Postal code for the city and state or province code of the Shipper/Sender
address.
*Required field for FedEx SmartPost.
*Required to override default setting.
I
FDXS
US
Field Level: Shipment
REQUIRED*
Contact name at the Shipper company.
*Required field for FedEx SmartPost.
*Required to override default settings.
I
FDXS
US
Field Level: Shipment
REQUIRED*
Code for the country where shipment originates.
*Required field for FedEx SmartPost.
*Required to override default settings.
See Appendix C in the Transaction Coding Reference Guide for a list of
country codes.
Description
Sender City
7
Max=35
Sender State/Province
8
Max=2
Sender Postal Code
9
Max=10
Sender Contact Name
32
Max=35
A
Sender Country Code
117
7-46
Max=2
A
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-9: Fields (Required and Optional) for FedEx SmartPost 020 Transaction (Continued)
Transaction: 020 Global Ship Request - Open Ship, Multiple-Piece Shipment
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Sender Phone Number
183
Max=15
A
I
FDXS
US
Field Level: Shipment
REQUIRED*
Phone number of the shipper.
*Required field for FedEx SmartPost.
*Required to override default settings.
I
FDXS
US
Field Level: Shipment
REQUIRED*
Company name of the Recipient.
*Required for FedEx SmartPost.
*Required if shipment is being sent to a company.
If this field is not applicable, Field 12 (Recipient Name) must be
completed.
I
FDXS
US
Field Level: Shipment
REQUIRED*
Contact name at the Recipient company.
*Required if a recipient company is not provided.
*Required for 1 — Bill recipient option for Pay Type (Field 23).
*Required for FedEx SmartPost.
A
I
FDXS
US
Field Level: Shipment
REQUIRED*
Primary address line of Recipient address. This is the address to which
the shipment is sent.
*Required for FedEx SmartPost.
Max=35 A
Max=30
for FedEx
SmartPos
t
I
FDXS
US
Field Level: Shipment
REQUIRED*
City name for the Recipient address. This is the city to which the shipment
is sent.
*Required for FedEx SmartPost.
Minimum of 3 characters required for city name.
If a military address state code (AA, AE, or AP) is passed in Field 16 in
the 020 Shipping transaction for a FedEx SmartPost shipment, FSMS will
allow a value of *PO (i.e. APO, FPO, or DPO) to be passed in for the
recipient city.
Recipient Information
Recipient Company
11
Max=30
A
Recipient Contact Name
12
Max=35
A
Recipient Address Line 1
13
Max=30
Recipient City
15
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-47
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-9: Fields (Required and Optional) for FedEx SmartPost 020 Transaction (Continued)
Transaction: 020 Global Ship Request - Open Ship, Multiple-Piece Shipment
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Recipient City
15
(cont.)
Max=35 A
Max=30
for FedEx
SmartPos
t
I
FDXS
US
Valid values are:
APO — Army Post Office
FPO — Fleet Post Office
DPO — Diplomatic Post Office
If a customer attempts to process a FedEx SmartPost shipment to one of
the AA, AE, or AP state codes (Field 16) and the Recipient City (Field 15)
code begins with any value other than *PO (where * represents a wildcard
before the letters ‘PO’ as in APO, FPO, or DPO), then Error Code 2731
is returned, with the message “The city name must begin with APO, FPO,
or DPO for this destination”, and the transaction fails.
Note: If FedEx Ground shipment, city name is limited to 20 characters.
I
FDXS
US
Field Level: Shipment
REQUIRED*
Field length is 2 for U.S.,and CA
State or province code of the Recipient address.
*Required for U.S. domestic.
*Required for FedEx SmartPost.
Values for shipments to American armed forces are:
AA — Armed Forces Americas
AE — Armed Forces Europe
AP — Armed Forces Pacific
See Appendix C in the Transaction Coding Reference Guide for a list of
state and province codes.
I
FDXS
US
Field Level: Shipment
REQUIRED*
Postal code for the city and state or province code of the Recipient
address.
*Required for FedEx SmartPost.
For a list of countries that use postal codes, see Appendix C in the
Transaction Coding Reference Guide.
I
FDXS
US
Field Level: Shipment
REQUIRED*
Phone number of the Recipient address.
*Required for FedEx SmartPost.
Note: Do not include non-numeric characters such as parenthesis or
dash.
Recipient State/Province
16
Max=2
A
Recipient Postal Code
17
Max=16
A
Recipient Phone Number
18
7-48
Max=15
A
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-9: Fields (Required and Optional) for FedEx SmartPost 020 Transaction (Continued)
Transaction: 020 Global Ship Request - Open Ship, Multiple-Piece Shipment
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Max=1
N
I
Description
Pay Type
23
FDXS
US
Field Level: Shipment
REQUIRED*
*Required for FedEx SmartPost.
FedEx SmartPost allows the following payment codes:
1 — Bill Shipper (default)
6 — Bill Associated Account
Note: Bill Associated Account is for Returns only.
Recipient Country
50
Max=2
A
I
FDXS
US
Field Level: Shipment
REQUIRED*
Two-digit code indicating the country of the Recipient address.
*Required for FedEx SmartPost.
*Required for ADD Piece Open Ship function.
See Appendix C in the Transaction Coding Reference Guide for country
codes.
N
I
FDXS
US
Field Level: Shipment
REQUIRED*
*Required for FedEx SmartPost.
Only valid value for FedEx SmartPost is:
01 — Customer packaging
FDXS
US
REQUIRED*
FedEx SmartPost service type you use to ship the package. Indicates
type of shipment and postal information placed in the “stamp” area of the
label.
* Required for FedEx SmartPost.
Valid values are:
1 — Standard Mail
3 — Bound Printed Matter
4 — Obsolete
5 — Media
6 — Parcel Post
7 — SmartPost Returns
Packaging Type
1273
Max=2
SmartPost Service Type/Postal Indicia
2417
Max=2
N
I
Note: FedEx SmartPost Returns supports Print Return labels. You can
request Shipment and Delivery E-Mail Notifications for FedEx SmartPost
Returns.
Ancillary Endorsements are not supported for FedEx SmartPost
Returns.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-49
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-9: Fields (Required and Optional) for FedEx SmartPost 020 Transaction (Continued)
Transaction: 020 Global Ship Request - Open Ship, Multiple-Piece Shipment
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
SmartPost Service Type/Postal Indicia
2417
(cont.)
Max=2
N
I
FDXS
US
If customer ships a FedEx SmartPost shipment with Field 2417 (Service
Type) set to 1 (Standard Mail) and passes in Field 2416 set either to
position 01, 03, 05, or left blank, then the position of Field 2416 will default
to 4 (Return Service Requested). Customer will then receive
informational message 5042, “Your ancillary endorsement has been
changed per USPS regulation.”
If a customer is processing an 020 shipping transaction and passes in
Field 2417 (Service Type) set to 1 (Standard Mail), Field 3204 (Delivery
Confirmation) set to Y, and either does not pass Field 2416 (Ancillary
Endorsement) or passes it in blank or with a value of 1 (Carrier Leave if
no Response), 3 (Forwarding Service Requested), or 5 (Change Service
Requested), then Field 2416 will be automatically reset to value 2
(Address Service Requested). The shipment will be successful and the
customer will receive the message “Your ancillary endorsement has been
changed to 2 (Address Service Requested). Please note that the ancillary
endorsement can only be 2 (Address Service Requested) or 4 (Return
Service Requested) for FedEx SmartPost Standard Mail shipments with
Delivery Confirmation.”When processing a Returns shipment (Field 2417
set to 7):
• If the Shipper Account Number is the same as the Returns Account
Number, then Field 23 (Pay Type) will be 1 Bill Shipper.
• If the Shipper Account Number is not the same as the Returns
Account Number, then Field 23 (Pay Type) will be 6 Bill Associated
Account.
Shipper Address Line 3
2420
Max=30
A
I
FDXS
US
Optional
Third address line of the Shipper address.
I
FDXS
US
Optional
Five-digit FedEx SmartPost customer account number.
If not passed in, it defaults to the FedEx SmartPost Customer ID set
during configuration.
I
FDXS
US
Optional
Third address line of the shipment’s recipient.
I
FDXS
US
Optional
Field Level: Package
Height measurement per package.
No implied decimal places.
For FedEx SmartPost: field is optional; always enter in inches.
SmartPost Customer ID
2425
Max=5
N
Recipient Address Line 3
2944
Max=35
A
Package Information
Package Height
57
7-50
Max=3
N
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-9: Fields (Required and Optional) for FedEx SmartPost 020 Transaction (Continued)
Transaction: 020 Global Ship Request - Open Ship, Multiple-Piece Shipment
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
FDXS
US
Optional
Field Level: Package
Width measurement per package.
No implied decimal places.
For FedEx SmartPost: field is optional; always enter in inches.
N
I
FDXS
US
Optional
Field Level: Package
Length measurement per package.
No implied decimal places.
For FedEx SmartPost: field is optional; always enter in inches.
FDXS
U
Field Level: Package
REQUIRED*
Weight of package or shipment.
*Required for FedEx SmartPost shipping to specify individual package
weights. FSMS will perform the weight summation and package count.
*Required to receive rate quotes.
This weight field supports two implied decimals for ALL shipments. You
must enter individual package weights only. FSMS performs the weight
summation and package count.
FDXS
US
Field Level: Shipment
REQUIRED*
Name of contact on return address.
*Required if 1586 (Print Alternate Return Address Flag) is set to Y and
Field 1486 (Return Address Company Name) is not used.
*Required for FedEx SmartPost.
FDXS
US
Field Level: Shipment
REQUIRED*
Company name on return address.
*Required if 1586 (Print Alternate Return Address Flag) is set to Y and
Field 1485 (Return Address Contact Name) is not used.
*Required for FedEx SmartPost.
Description
Package Width
58
Max=3
Package Length
59
Max=3
Package Weight/Shipment Weight
1670
Max=10.2 N
I
Return Information
Return Address Contact Name
1485
Max=35
A
I
Return Address Company Name
1486
v 10.6.1
Max=35
A
I
FedEx Ship Manager® Server Developer Guide
7-51
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-9: Fields (Required and Optional) for FedEx SmartPost 020 Transaction (Continued)
Transaction: 020 Global Ship Request - Open Ship, Multiple-Piece Shipment
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Return Address Line 1
1487
Max=35
A
I
FDXS
US
Field Level: Shipment
REQUIRED*
First line of return address.
*Required if 1586 (Print Alternate Return Address Flag) is set to Y.
*Required for FedEx SmartPost.
A
I
FDXS
US
Field Level: Shipment
REQUIRED*
Second line of the return address.
*Required if 1586 (Print Alternate Return Address Flag) is set to Y.
*Required for FedEx SmartPost.
Max=35 A
Max=30
for FedEx
SmartPos
t
I
FDXS
US
Field Level: Shipment
REQUIRED*
City name on return address.
*Required if 1586 (Print Alternate Return Address Flag) is set to Y.
*Required for FedEx SmartPost.
I
FDXS
US
Field Level: Shipment
REQUIRED*
State or province on return address.
*Required if 1586 (Print Alternate Return Address Flag) is set to Y and
the return address country is U.S., Canada (CA), or Puerto Rico (PR).
*Required for FedEx SmartPost.
I
FDXS
US
Field Level: Shipment
REQUIRED*
Postal code on return address.
*Required if 1586 (Print Alternate Return Address Flag) is set to Y.
*Required for FedEx SmartPost.
FDXS
US
Field Level: Shipment
REQUIRED*
Phone number for return address.
*Required if 1586 (Print Alternate Return Address Flag) is set to Y.
Return Address Line 2
1488
Max=35
Return Address City
1489
Return Address State/Province
1490
Max=2
A
Return Address Postal Code
1491
Max=10
A
Return Address Phone Number
1492
7-52
Max=15
A
I
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-9: Fields (Required and Optional) for FedEx SmartPost 020 Transaction (Continued)
Transaction: 020 Global Ship Request - Open Ship, Multiple-Piece Shipment
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Return Country Code
1585
Max=2
A
I
FDXS
US
Field Level: Shipment
REQUIRED*
Code for country of return address. This code must match the origin
country code for the shipment.
*Required if 1586 (Print Alternate Return Address Flag) is set to Y.
For FedEx SmartPost, field is Optional Valid value is U.S.
See Appendix C in the Transaction Coding Reference Guide for a list of
country codes.
I
FDXS
US
Field Level: Shipment for all shipments except FedEx International
Priority DirectDistribution (IPD). For IPD shipments only, Field 1586 is
used at the package level.
REQUIRED*
Use to override the sender address on the shipping label as the return
address.
Valid values are:
Y — Print alternate return address on label
N — or not present — Do not print alternate return address (default)
*Required to override the sender address on the shipping label.
I
FDXS
US
Optional
Use this field to provide more information for the return address.
FDXS
US
Field Level: Shipment for single transactions.
Field Level: Package for 020/120 Global Ship Request/Reply Open Ship
transactions.
Optional
Indicates the Rate/Route/Time in Transit flag.* Route is for FedEx
Express and Time-in-Transit is for FedEx Ground.*
Valid values are:
1 — Rate Quote
2 — Route/Time in Transit
3 — Rate Quote and Route
*CA and U.S. origins can rate; all origins can route.
Valid FedEx SmartPost values are:
1 — Rate Quote
3 — Rate Quote and Route
Passing this field in a transaction returns a rate quote only, and the
shipment is not processed for shipping.
Print Alternate Return Address Flag
1586
Max=1
A
Return Address Line 3
2421
Max=35
A
Rate Information
Rate/Route/Time-in-Transit Flag
1234
v 10.6.1
Max=1
N
I
FedEx Ship Manager® Server Developer Guide
7-53
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-9: Fields (Required and Optional) for FedEx SmartPost 020 Transaction (Continued)
Transaction: 020 Global Ship Request - Open Ship, Multiple-Piece Shipment
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Rate/Route/Time-in-Transit Flag
1234
(cont.)
Max=1
N
I
FDXS
US
To ship a package after a rate/route request, code this field in a new 020
Shipping transaction with no value: 1234,""
Note: For Open Ship shipments you can also capture rate quotes by
setting position 3 to Field 541 (Open Ship Flags) to Y.
A
I
FDXS
US
Field Level: Package
Optional
Use this field for optional notes.
This field is a package level field and must not be used if a shipment level
customer reference number is assigned in Field 3003 (Shipment
Customer Reference Information).
If this field is used simultaneously with Field 3003, then Field 3003 is
ignored. Package level fields take precedence.
A
I
FDXE
FDXG
FHD
FDXS
All
REQUIRED
Indicates the type of download.
Format (26 characters): NNNNNNNNNNNNNNNNNNNNNNNNNN
(default)
Flag positions are:
0 — FedEx Express Domestic Rates Flag
1 — FedEx Express Tracking Numbers Flag
2 — *Software Flag (requires staged software prior to download)
3 — *FedEx Express URSA Table Flag
4 — FedEx International Rates Flag
5 — FedEx Express Invoice
6 — Meter Reconcile Flag
7 — *System Reconcile Flag
8 — ACU Registration Trans 609/605 Flag
9 — ACU Registration Trans 617/614 Flag
10 — ACU Registration Trans 615 Flag
11 — FedEx Implement Downloads Flag
12 — FedEx Express List Rates Flag
13 — *FedEx Express DAT Files Table Flag (All Shipping Table Files
which includes IATA, SASV, and HazMat)
14 — Update McAfee Flag
15 — *Discounted Ground Rates Flag
16 — Express Earned Discount Rates
17 — FedEx International List Rates Flag
18 — Intra-Canada List Rates Flag
Service Options and Notes
Reference Information
25-#
Max=39
Download Flag
1053
7-54
Max=26
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-9: Fields (Required and Optional) for FedEx SmartPost 020 Transaction (Continued)
Transaction: 020 Global Ship Request - Open Ship, Multiple-Piece Shipment
Field ID
1053
(cont.)
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Max=26
A
I
FDXE
FDXG
FHD
FDXS
Dynamic Surcharge Code
1947-#
v 10.6.1
Min=3
Max=5
N
All
Description
19 — ESRG Data Flag
20 — Ground List Rates21 — ODA/OPA Surcharge Flag
22 — FedEx SmartPost Rates
23 — FedEx SmartPost Delivery Confirmation Numbers
24 — FedEx SmartPost List Rates Flag
25 — FedEx SmartPost Earned Discount Rates
Asterisk (*) indicates “for Master meter only”. No asterisk indicates
“applies to ALL meters”.
When positions 18 or 19 are set to Y, FedEx Express International List
Rates are requested for download. To request FedEx International
DirectDistribution Surface Solutions (IDDSurface) List Rates, set position 13 to YA
Transactions:120 Global Ship Reply
O
FDXE
FDXG
FDXS
All
The following surcharge codes may be returned in 120 Global Ship Reply
transactions:
100 — Declared Value
120 — Dangerous Goods
140 — Residential
160 — C.O.D.
180 — Alaska
200 — Hawaii
220 — AHS Package
221 — AHS Weight
222 — AHS Dimension
240 — ShipAlert
260 — Oversize
310 — Appointment Delivery
330 — Date Certain Delivery
340 — Evening Delivery
350 — Signature Delivery
400 — Saturday Delivery
410 — Saturday Pickup
420 — FedEx Priority Alert
430 — Sunday Delivery
440 — Outside Pickup Area
450 — Outside Delivery Area
460 — Inside Pickup
470 — Inside Delivery
480 — Extra Hours
490 — Fuel
500 — Delivery Area
FedEx Ship Manager® Server Developer Guide
7-55
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-9: Fields (Required and Optional) for FedEx SmartPost 020 Transaction (Continued)
Transaction: 020 Global Ship Request - Open Ship, Multiple-Piece Shipment
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
1947-#
(cont.)
Min=3
Max=5
N
O
FDXE
FDXG
FDXS
All
520 — Third Party Consignee
600 — Offshore
610 — HST
620 — PST
630 — GST
640 — Piece County Verify
650 — Europe First
660 — Clearance Entry Fee (CEF)
680 — Dry Ice
700 — Delivery Confirmation Service Surcharge
720 — Non-Machinable Surcharge
I
FDXS
US
Optional
Special endorsements or delivery options specific to FedEx SmartPost.
Valid values are:
1 — Carrier Leave If No Response
2 — Address Service Requested
3 — Forwarding Service Requested
4 — Return Service Requested
5 — Change Service Requested
Note: Valid values (for Standard Mail service when delivery confirmation
is requested) are only 2 — Address Service Requested or 4 — Return
Service Requested.
Description
Ancillary Endorsements
2416
Max=2
N
Note: Ancillary Endorsements are not available for a FedEx SmartPost
Returns shipment.
If a customer is processing an 020 shipping transaction and passes in
Field 2417 (Service Type) set to 1 (Standard Mail), Field 3204 (Delivery
Confirmation) set to Y, and either does not pass Field 2416 (Ancillary
Endorsement) or passes it in blank or with a value of 1 (Carrier Leave if
no Response), 3 (Forwarding Service Requested), or 5 (Change Service
Requested) then Field 2416 will be automatically reset to value 2
(Address Service Requested. The shipment will be successful and the
customer will receive the massage “Your ancillary endorsement has been
changed to 2 (Address Service Requested). Please note that the ancillary
endorsement can only be 2 (Address Service Requested) or 4 (Return
Service Requested) for FedEx SmartPost Standard Mail shipments with
Delivery Confirmation.”
7-56
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-9: Fields (Required and Optional) for FedEx SmartPost 020 Transaction (Continued)
Transaction: 020 Global Ship Request - Open Ship, Multiple-Piece Shipment
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Package Association and Print Mode
2600
Max=2
N
I
Description
Transactions: 020 Global Ship Request
FDXE
FDXG
FDXS
US
Optional
Specifies the type of package association and print label mode to use —
that is, whether labels “print-at-end” or “print-as-you-go”.
Valid values are for FedEx Express and FedEx Ground only:
1 — (default) Domestic MPS non-associated, FedEx Express C.O.D.
MPS associated, FedEx Express International MPS associated. Prints
labels using package or shipment confirmation rules.
2 — Domestic U.S. MPS for FedEx Express and FedEx Ground services.
Package association. Prints labels with each shipment Confirm
transaction (Print-At-The-End).
3 — Domestic U.S, MPS for FedEx Express and FedEx Ground services.
Package association. Prints labels for each Create/Add Package
transaction (Print-As-You-Go).
Note: For Open Ship Print-As-You-Go (PAYG) shipments, you must
CONFIRM the shipment on the same date as CREATE, otherwise labels
will have the incorrect ship date.
4 — Package non-associated and labels printed with each Create/Add
Piece transaction for Domestic MPS; Print-As-You-Go (PAYG-NA) for
FedEx SmartPost. If customer ships FedEx SmartPost via the 020
transaction and passes in Field 2600 via the Open Ship method with a
value other than 4, and also passes Field 541 (Open Ship Flag) set to
position 1 (Create) or 4 (Add), and also passes in Field 2417 (FedEx
SmartPost Service Type/Postal Indicia), then Error Message 2645,
“Package Association is not available with this service,” will be returned.
If Field 2600 was set to position 1 or 2, left blank, or passed in with an
invalid value (0, 5–9), then labels will print at the end. If Field 2600 was
set to position 3 or 4, then labels will print with each Create and Add
Piece.
For shipping, use Open Ship or MPS.
List Non-Machinable Surcharge
2800
Transactions: 120 Global Ship Reply
Min=1
N
Max=11.2
O
FDXS
Optional
Contains the list surcharge amount for a non-machinable package.
Max=4
I/O
FDXS
REQUIRED*
*Required if user is allowed to use multiple hubs and wants to use a
different Hub ID other than the default HUB ID.
If customer passes in this field with a value other than the value in their
list of allowed HUB IDs, Error Message 2647, “Invalid Hub ID entered for
FedEx SmartPost shipment,” is returned and the transaction fails.
Hub ID
2801
v 10.6.1
N
FedEx Ship Manager® Server Developer Guide
7-57
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-9: Fields (Required and Optional) for FedEx SmartPost 020 Transaction (Continued)
Transaction: 020 Global Ship Request - Open Ship, Multiple-Piece Shipment
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I/O
FDXS
Optional
Identifies a non-machinable package.
Valid values:
Y — Yes
N — No
O
FDXS
The surcharge amount for the non-machinable package.
If Field 1234 (Rate/Route/Time in Transit) is passed in set to position 1
(rate), or if Field 541 (Open Ship) is passed in set to position 3 (rate) and
Field 2802 is passed in, or if the package dimensions indicate nonmachinable, and rating is successful, then the correct non-machinable
surcharge will be returned.
Description
Non-Machinable
2802
Max=1
Non-Machinable Surcharge
2803
Min=1
N
Max=11.2
Delivery Confirmation Service Surcharge
2804
Min=1
N
Max=11.2
O
FDXS
FedEx Ground Oversize Indicator
3124
Max=1
N
I/O
The surcharge amount for Delivery.
Transactions: 020/120 Global Ship Request/Reply
FDXG
FHD
FDXS
US
CA
Field Level: Package
Optional
Indicates if a FedEx Ground or FedEx Home Delivery package meets an
oversize condition.
FedEx Ground package oversize values are:
1 — OS I - if length+girth is > 84" and < 109" and weight is > 30 lbs.
2 — OS II - if length+girth is > 108" and < 131" and weight is < 50 lbs.
3 — OS III - if length+girth is > 108" and < 131" and weight is < 50 lbs.
4 — Balloon Package - if length+girth is > 84" but £ to 108" and weight is
<20 lbs.
FedEx Home Delivery package oversize values are:
1 — OS I - if length+girth is > 84" and < 109" and weight is < 30 lbs.
2 — OS II- if length+girth is > 108" and < 131" and weight is < 50 lbs.
3 — OS III - if length+girth is > 130" and < 166" and weight is < 70 lbs.
If you enter dimensions or dimensional criteria that meet oversize
guidelines, FSMS sets this value automatically.
Note: A $30 surcharge will be applied to packages that meet the OS 3
requirements. This surcharge is currently not supplied in the rate quote.
To apply this surcharge code to your application, add the surcharge
when this field returns a value of 3 in the 120 Global Ship Reply transaction.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Billing Number
3135
7-58
Min=1
Max=10
A/N
I/O
FDXG
FDXS
Obsolete field.
Billing number.
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-9: Fields (Required and Optional) for FedEx SmartPost 020 Transaction (Continued)
Transaction: 020 Global Ship Request - Open Ship, Multiple-Piece Shipment
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
I
FDXS
US
Obsolete
I/O
FDXS
US
Field Level: Shipment
REQUIRED.
Indicates the end of a transaction. The format is 99,"" (99 followed by a
comma and two quotation marks). All FSMS transactions must end with
99,"".
Delivery Confirmation Flag
3204
Max=1
A
END of Transaction
End of Record Indicator
99
Max=0
Null
Coding a Basic FedEx SmartPost Print Returns Label
Transaction
Table 7-10: FedEx SmartPost Print Returns Label Fields
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
Description
Transaction Code
0
Max=3
All
All
Field Level: Shipment
REQUIRED
Indicates the start of a transaction.
For example, 0,"020" or 0,"20" signifies the start of the 020 Global Ship
Request Transaction.
For shipping, use Single Shot, Single Piece, Open Ship, MPS.
All
All
Field Level: Shipment
If you include a transaction identifier in the Request transaction, the same
identifier is returned in this Field in the Reply transaction. The transaction
identifier (ID) lets you link transaction “replies” back to the transaction
“requests” which is important in the case of a bulk shipment.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Customer Transaction Identifier
1
v 10.6.1
Max=30
N
I
FedEx Ship Manager® Server Developer Guide
7-59
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-10: FedEx SmartPost Print Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Recipient Information
Recipient Company
11
Max=35
A/N
I
FDXE
FDXG
FDXS
All
Field Level: Shipment
REQUIRED*
Company name of the Recipient.
*Required if shipment is being sent to a company.
If this field is not applicable, Field 12 (Recipient Name) must be
completed.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
I
FDXE
FDXG
FDXS
All
Field Level: Shipment
REQUIRED*
Contact name at the Recipient company.
*Required if a recipient company is not provided.
*Required for all C.O.D. (U.S. service only), alcohol, bill recipient, and bill
third party.
*Required for Hold At FedEx Location service.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
I
FDXE
FDXG
FDXS
All
Field Level: Shipment
REQUIRED
Primary address line of Recipient address. This is the address to which
the shipment is sent.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
I
FDXE
FDXG
FDXS
All
Field Level: Shipment
REQUIRED*
Second address line of Recipient address. This is the address to which
the shipment is sent.
*Required if the address contains secondary address elements such as
apartment number, suite number, floor building, and so forth in addition to
the street name and street number provided in Field 13 (Recipient
Address Line 1).
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Recipient Contact Name
12
Max=35
A
Recipient Address Line 1
13
Max=35
A/N
Recipient Address Line 2
14
7-60
Max=35
A/N
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-10: FedEx SmartPost Print Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I
FDXE
FDXG
FDXS
All
Field Level: Shipment
REQUIRED
City name for the Recipient address. This is the city to which the shipment
is sent.
Minimum of 3 characters required for city name.
If a military address state code (AA, AE, or AP) is passed in Field 16 in
the 020 Shipping transaction for a FedEx SmartPost shipment, FSMS will
allow a value of *PO (i.e. APO, FPO, or DPO) to be passed in for the
recipient city.
Valid values are:
APO — Army Post Office
FPO — Fleet Post Office
DPO — Diplomatic Post Office
Note: International FedEx SmartPost shipments can only be made to
military addresses.
Note: If a customer attempts to process a FedEx SmartPost shipment to
one of the AA, AE, or AP state codes (Field 16) and the Recipient City
(Field 15) code begins with any value other than *PO (where * represents a wildcard before the letters ‘PO’ as in APO, FPO, or DPO), then
Error Message 2731, “The city name must begin with APO, FPO, or
DPO for this destination” is returned, and the transaction fails.
Note: If FedEx Ground shipment, city name is limited to 20 characters.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS
I
FDXE
FDXG
FDXS
All
Field Level: Shipment
REQUIRED
State or province code of the Recipient address.
Field length is 2 for Canada (CA), Puerto Rico (PR) and U.S. Field length
is 14 for other countries.
AA (Armed Forces Americas), AE (Armed Forces Europe), and AP
(Armed Forces Pacific) may be passed in for FedEx SmartPost
shipments.
*Required for U.S., CA and PR.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
I
FDXE
FDXG
FDXS
All
Field Level: Shipment
REQUIRED
Postal code for the city and state or province code of the Recipient
address.
*Required for countries which use postal codes.
For FedEx international shipments: Canada (CA), Puerto Rico (PR) and
U.S. must always use valid postal codes.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Description
Recipient City
15
Max=35
FedEx
Express
Max=20
FedEx
Ground
Recipient State/Province
16
Max=2
A
CA, PR,
US
Max=14
Other
countries
Recipient Postal Code
17
v 10.6.1
Max=10
A/N
FedEx Ship Manager® Server Developer Guide
7-61
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-10: FedEx SmartPost Print Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Recipient Phone Number
18
Max=15
A
I
FDXE
FDXG
FDXS
All
Field Level: Shipment
REQUIRED
Phone number of the Recipient address. This number is used for FedEx®
Collect on Delivery (C.O.D.), Hold at FedEx Location (HAL) and Alcohol
shipments.
Note: Do not include non-numeric characters such as a parenthesis or
dash.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
FedEx SmartPost Shipment Information
Payor Account Number
20
Max=9
N
I
FDXE
FDXG
FDXS
All
Field Level: Shipment
REQUIRED*.
Nine-digit FedEx account number of company or person to be billed for
the shipment.
*Required for FedEx Ground when you want to bill your recipient or a
third-party account number.
If any pay type other than 1 (bill shipper) is entered, rates are not returned
in the 125 Transaction.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Max=1
N
I
FDXE
FDXG
FDXS
All
Field Level: Shipment
REQUIRED
Pay Type
23
Code for payment type. FedEx SmartPost® payment types are:
1 — Bill Sender (default)
FedEx SmartPost® Returns payment types are:
6 — Bill Associated Account
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
7-62
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-10: FedEx SmartPost Print Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
FDXE
FDXG
FDXS
All
Field Level: Shipment
REQUIRED*
Date of shipment.
*Required for Future Day shipping. Format: CCYYMMDD
Default: Current meter date.
For example, July 1, 2005 is coded as: 20050701
For FedEx Express, the ship date can be set in advance up to the number
of days allowed by the date range in the URSA file; includes IPD, IDF, IED
and Returns services.
FedEx Ground and FedEx Home Delivery ship dates can be set up to 90
days in advance, and the ship date can be set to unlimited using the
Extend 90 Day limit — FedEx Ground checkbox in the Systems
Settings tab of the FSMS Configuration Utility.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
I
FDXE
FDXG
FDXS
US
INTL
Field Level: Package for all services except for FedEx Express
international MPS which is shipment level.
Optional
Use this field for optional notes (FedEx Express) and customer reference
number CRN (FedEx Ground).
For all other services, this field is a package-level field and must not be
used if a shipment-level customer reference number (CRN) has been
assigned in Field 3003 (Shipment Customer Reference Information).
If this field is used simultaneously with Field 3003, then Field 3003 is
ignored. Package-level fields take precedence.
This field prints on the FedEx Express shipping label, various reports, and
the FedEx Express Shipper’s Declaration for Dangerous Goods form
(FedEx Express 1421C or LZR DG DEC FORM). This value also is
displayed in the Customer Reference field on the FedEx Ground invoice.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
I
FDXE
FDXG
FDXS
All
Field Level: Shipment
Optional
Department name of Sender or shipping origin. Use to override the
default origin department setting in the FSMS Configuration Utility.
When used in the 020 Global Ship Request Transaction, the name prints
on all shipping details.
For FedEx Ground shipments, it prints on the invoice.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Description
Ship Date
24
Max=8
Reference Information
25-#
Max=39
A/N
Shipper Information
Sender/Origin Department
38
v 10.6.1
Max=35
A
FedEx Ship Manager® Server Developer Guide
7-63
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-10: FedEx SmartPost Print Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Recipient Information
Recipient Country
50
Max=2
A
I
FDXE
FDXG
FDXS
All
Field Level: Shipment
REQUIRED*
Two-digit code indicating the country of the Recipient address.
*Required for FedEx International Priority DirectDistribution (IPD), FedEx
International Economy DirectDistribution Service (IED) and FedEx
International Priority DirectDistribution Freight (IDF) shipments.
*Required for FedEx SmartPost.
*Required for ADD Piece Open Ship function.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
N
I
FDXE
FDXG
FDXS
All
For FedEx SmartPost: Field is optional; always enter in inches.
Minimum FedEx Express dimensions are in inches: 1” x 1” x 1” (L x W x
H) or in centimeters:1 cm. x 1 cm. x 1 cm. (L x W x H).
See the FedEx Service Guide for service details related to Dim Weighting
for FedEx Express and oversize conditions for FedEx Express and FedEx
Ground.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Note: FSMS does not sort dimensions. For correct dimensional weight
calculations, the longest dimension must be placed in Field 59 (Package
Length).
N
I
FDXE
FDXG
FDXS
All
Field Level: Package
REQUIRED*
Width measurement per package. No implied decimal places.
Package Information
Package Height
57-#
Max=3
Package Width
58-#
Max=3
*Required for shipping FedEx Express Freight®.
Recommended if using customer packaging to ensure accurate billing as
dimensional weighting or oversize conditions may apply.
For FedEx SmartPost: Field is optional; always enter in inches.
Minimum FedEx Express dimensions are in inches: 1" x 1" x 1" (L x W x
H); or in centimeters:1 cm. x 1 cm. x 1 cm.
(L x W x H).
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Note: FSMS does not sort dimensions. For correct dimensional weight
calculations, the longest dimension must be placed in Field 59 (Package
Length).
7-64
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-10: FedEx SmartPost Print Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
Description
Package Length
59-#
Max=3
FDXE
FDXG
FDXS
All
Field Level: Package
REQUIRED*
Length measurement per package. No implied decimal places.
*Required for shipping FedEx Express Freight.
Recommended if using customer packaging to ensure accurate billing as
dimensional weighting or oversize conditions may apply.
For FedEx SmartPost: Field is optional; always enter in inches.
Minimum FedEx Express dimensions are in inches: 1" x 1" x 1" (L x W x
H); or 1 cm. x 1 cm. x 1 cm. (L x W x H).
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
When a customer enters package dimensions for the individual FedEx
SmartPost Bound Printed Matter, Standard Mail, Parcel Select, or Media
package, the system validates that the sum of length plus the girth (2 x
height + 2 x width) does not exceed 84 inches. When this condition
occurs (exceeds sum), Error Message 0421 is returned to the customer
and the transaction fails. The error occurs at the confirmation step for all
shipping methods.
Note: FSMS does not sort dimensions. For correct dimensional weight
calculations, the longest dimension must be placed in Field 59 (Package
Length).
FDXE
FDXG
FDXS
All
Field Level: Shipment for FedEx Express international shipments
Field Level: Package FedEx Express - U.S. and FedEx Ground
REQUIRED*.
Total dollar amount declared or carriage value of the shipment. This field
supports the 14.2 numeric format and has two implied decimal places.
*Required for all U.S. shipments insured with FedEx.
Values must contain only numeric characters (no commas, "." or "$").
Note: All currency fields for FedEx Express Freight must be in USD.
When used to create/print a Bill of Lading (BOL) for FedEx Express
Freight, declared value cannot exceed $100,000 USD.
Note: Carriage Value cannot exceed the Customs Value.
Note: If you need to use a 14.2 numeric format, use Field 69 instead of
Field 26.
See the FedEx Service Guide for allowable limits.Carriage value per
package.
Note: For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Declared Value/Carriage Value
69-#
v 10.6.1
Max=14.2 N
I
FedEx Ship Manager® Server Developer Guide
7-65
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-10: FedEx SmartPost Print Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I
FDXE
FDXG
FDXS
All
Field Level: Shipment
REQUIRED* or Defaulted.
Indicates the unit of weight used for the shipment.
*Required if your shipment is calculated in kilograms (KGS).
Valid values are:
LBS — Weight in pounds (default for U.S. and export)
KGS — Weight in kilograms (default for intra-Canada and all
international)
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Note: For intra-U.S. shipments, you may enter the weight in LBS or
KGS.
N
I
FDXE
FDXG
FDXS
All
Field Level: Shipment
REQUIRED*
Total number of packages in a shipment, including the master package.
*Required for a multiple-piece shipment (MPS).
For all MPS shipments, the software performs the package count
summation based on the number of occurrences of Field 1670-#
(Package Weight/Shipment Weight) and overrides any input value.
If you do not enter Field 116, but enter 1670-1, 1670-2, 1670-3, then
FSMS counts the packages and states 3.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Note: You can use this field for FedEx international shipments if you
supply shipment Total Packages and Total Weight.
I
FDXE
FDXG
FDXS
All
Optional
Use this field to pre-validate shipping information prior to processing the
shipping transaction.
This can be used in Open Ship shipments or in a single transaction for
FedEx Express and FedEx Ground shipping.
Valid values are:
Y — Data validated (for any shipping method, but for Open Ship after
shipment is committed to the database)
P — Data validated (for Open Ship only - before shipment is committed
to database)
N — Ships and label produced
Use in conjunction with Field 541 (Open Ship Flags) set to
NNNNNNNNN.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
As a best practice, use this option on all rate and route transactions.
Description
Weight Units
75
Max=3
Package Total
116
Max=3
Service Options and Notes
Pre-Ship Validation Flag
184
7-66
Max=1
A
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-10: FedEx SmartPost Print Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Residential Delivery Flag
440
Max=1
A
I
FDXE
FDXG
FDXS
US
Field Level: Shipment
Optional
Indicates whether the shipment is for residential delivery.
Valid values are:
Y — Residential delivery
N — Non-residential delivery
The residential delivery surcharge is returned in Field 429 (Residential
Surcharge).
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
N
I
FDXE
FDXG
FDXS
All
Field Level: Shipment
REQUIRED* to ensure the tracking number obtained is from the
range assigned to the requesting meter.
Unique number assigned to a FedEx shipping account (used in each
transaction to identify the revenue/shipping activity of a shipment).
Defaults to the master meter number.
*Required for reprinting reports.
*Required if the meter number is different than the meter number
configured as the default.
Meter Number
498
Min=1
Max=9
Note: If a one-to-one relationship exists between meter numbers and
account numbers (there is no more than one meter number per account
number), then the meter number or the account number alone may be
used in the transaction.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
In FSMS version 10.0.1, meter numbers expanded to nine-digits in
length. Your assigned meter number may be any length up to nine-digits.
Open Ship Flags
541
v 10.6.1
Max=9
A
I
FDXE
FDXG
FDXS
All
REQUIRED*
Identifies transaction functions using nine one-byte flags which are set to
Y to indicate shipment level or package level flag.
*Required for Open Ship.
Specify Y in the position(s) of the Open Ship functions used for a given
transaction. Specify N in all other positions. All flags must be used and
must be either Y or N. If you enter all Ns, all Open Ship functions are
disabled.
Default: YNNNNNNNY (CREATE and CONFIRM the Open Ship
shipment.)
FedEx Ship Manager® Server Developer Guide
7-67
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-10: FedEx SmartPost Print Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I
FDXE
FDXG
FDXS
All
Each one-byte flag is defined in sequence in the following array:
1 — CREATE an Open Shipment
2 — ROUTE/Time in Transit
3 — RATE
4 — ADD a piece/package
5 — EDIT a piece/package
6 — EDIT/ADD data to the entire shipment
7 — DELETE a package
8 — DELETE the shipment
9 — CONFIRM the shipment
For shipping, use Open Ship.
A/N
I
FDXE
FDXG
FDXS
All
REQUIRED*
Set to the unique number passed in the CREATE transaction. The value
is a unique number per Open Ship shipment per meter and represents
the Open Ship Index.
*Required for Open Ship.
Note: Field 542 is not required if you are simultaneously performing a
CREATE or ADD transaction.
Examples of simultaneous transactions are: YYNNNNNNN which
performs a shipment level CREATE and Route/Time in Transit
transaction or NYNYNNNNN which performs a package level ADD and
shipment level Route/Time in Transit together in the same transaction.
For shipping, use Open Ship.
Description
Open Ship Flags
541
(cont.)
Max=9
Open Ship Index
542
Max=9
Note: Field 542 is not used for IPD open shipping. Instead use
Field 1355 (IOR Facility Code) with Field 24 (Ship Date) and Field 1274
(Service Type) to form a unique shipment
Package Sequence
1117
Max=4
A
I
FDXE
FDXG
FDXS
All
REQUIRED*
Sequence number for multiple-piece shipments (MPS).
*You must use Field 1117 for the first piece and all occurring pieces in a
multiple-piece shipment.
Valid values are positive natural numbers only (1-9999); no decimal
places are allowed.
For shipping, use MPS.
I
FDXE
FDXS
All
Field Level: Shipment
Optional
Department name for the package destination address.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Recipient Department Name
1145
7-68
Max=12
A
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-10: FedEx SmartPost Print Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Rate/Route/Time-in-Transit Flag
1234
Max=1
N
I
FDXE
FDXG
FDXS
All*
Field Level: Shipment for single transactions.
Field Level: Package for 020/120 Global Ship Request/Reply Open Ship
transactions.
Optional
Indicates the Rate/Route/Time-in-Transit flag.*
Route is for FedEx Express and Time-in-Transit is for FedEx Ground.
Valid values are:
1 — Rate Quote
2 — Route/Time in Transit
3 — Rate Quote and Route
*CA and U.S. origins can rate; all origins can route.
Valid FedEx SmartPost values are:
1 — Rate Quote
3 — Rate Quote and Route
Passing this field in a transaction returns a rate quote only, and the
shipment is not processed for shipping.
To ship a package after a rate/route request, code this field in a new 020
Request Transaction with no value: 1234,""
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
For Open Ship shipments you can also capture rate quotes by setting
position 3 to Field 541 (Open Ship Flags) to Y.
N
I
FDXE
FDXG
FDXS
All
Field Level: Shipment
REQUIRED
For FedEx Express (U.S. and international) only:
01 — Customer packaging
02 — FedEx Pak
03 — FedEx Box
04 — FedEx Tube
06 — FedEx Envelope
For FedEx International only (including U.S. Export)
15 — FedEx 10 KG Box
25 — FedEx 25 KG Box
For FedEx Ground and FedEx SmartPost:
01 — Customer packaging
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Packaging Type
1273-#
v 10.6.1
Max=2
FedEx Ship Manager® Server Developer Guide
7-69
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-10: FedEx SmartPost Print Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Recipient Telephone Extension
1277
Max=6
N
I
FDXE
FDXG
FDXS
All
Optional
Recipient telephone extension that prints on the shipping label.
Numeric value up to six digits.
Available the following shipment types:
• FedEx Ground - U.S. and FedEx International Ground®
• FedEx Express and FedEx Ground Intra-Canada Shipments
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Note: Do not include non-numeric characters such as a parenthesis or
dash.
Handling Charge Type
1588-#
Max=1
N
I
FDXE
FDXG
FDXS
All
Optional
Indicates the type of handling charge to be added to the net charge of the
shipment.
Valid values are:
0 — No handling charge
1 — Fixed handling charge amount
2 — Variable handling charge based on percentage of gross
transportation charge
3 — Variable handling charge based on percentage of net charge
4 — Variable handling charge based on percentage of net charge minus
Canada taxes (CA origin only)
Note: For FedEx Ground multiple-piece shipments (MPS), a value of 1,
2, 3, or 4 must be on the first package to enable variable handling
charge on any subsequent package of the MPS.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Note: You may also choose to configure a recurring handling charge
type in the FSMS Configuration Utility for your Transaction Distribution
shipments.
All
Optional
Handling charge as dollar amount or percentage.
If Field 1588 (Handling Charge Type) is set to 1 (Fixed handling charge
amount), Field 1595 contains a currency amount. For example, a value
of 500 means $5.00.
If Field 1588 is set to 2, 3 or 4, Field 1595 contains a percentage. For
example, a value of 500 means 5%.
This field allows up to seven (7) numeric characters, two of which are
implied decimal entries.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Handling Charge Amount or Percentage
1595-#
7-70
Max=7.2
N
I
FDXE
FDXG
FDXS
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-10: FedEx SmartPost Print Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Handling Charge Application Point
1606-#
Max=1
N
I
FDXE
FDXG
FDXS
All
Optional
Specifies at which level (package or shipment) FedEx handling charges
apply.
Valid values are:
0 or blank — Handling charge applied at the package level
1 — Handling charge applied at the shipment level
Only repeat if used at the package level.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
FDXE
FDXG
FDXS
All
Field Level: Shipment for international and intra-Canada shipments
Field Level: Package for U.S. individual packages
REQUIRED*
Weight of package or shipment.
*Required for U.S. shipping (including FedEx Ground hazardous
materials shipments) to specify individual package weights. FedEx Ship
Manager® Server (FSMS) will perform the weight summation and
package count.
*Required if Field 1493 is Y.
*Required to receive rate quotes.
This weight field supports two implied decimals for ALL shipments and
does not require any distinction between FedEx Express, FedEx Ground
or FedEx International shipping.
FSMS performs the weight summation and package count. This method
is optional for all FedEx International shipping including U.S. Export.
For all FedEx International and intra-Canada Shipping:
You may enter the total shipment weight rather than the individual
package weights. If you enter the total shipment weight, you must also
use Field 116 (Package Total) to indicate the total number of packages in
the shipment.
Maximum weights allowed are:
FedEx Express (non-Freight) — 150 lbs.
FedEx Ground — 150 lbs.
FedEx Home Delivery — 70 lbs.
Note: If Field 1670 is not passed in the transaction, all the rating fields in
the reply are null (""), zero (0), or not present.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Package Weight/Shipment Weight
1670-#
v 10.6.1
Max=8.2
N
I
FedEx Ship Manager® Server Developer Guide
7-71
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-10: FedEx SmartPost Print Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Shipment Dimensional Indicator
1686
Max=1
A
I
FDXE
FDXS
INTL
Field Level: Shipment
REQUIRED*
Indicates whether provided dimensions are applied at the shipment level
or at the individual package level.
When a customer enters package dimensions for the individual FedEx
SmartPost Bound Printed Matter, Standard Mail, Parcel Select, or Media
package, the system validates that the sum of length plus the girth
(2*height + 2*width) does not exceed 84 inches. When this condition
occurs (exceeds sum), Error Message 0421 is returned to the customer
and the transaction fails. The error occurs at the confirmation step for all
shipping methods.
Valid values are:
S — Shipment
P — Package (default)
A — All
The All option allows package level dimensions to be entered once and
applied at the package level. Use when all packages are of the same
dimension.
Note: If you use Field 1670 (Package Weight/Shipment Weight) to submit total shipment weight (available for intra-Canada and international
shipments) and Field 116 (Package Total) to indicate the total number of
packages in the shipment., then shipment level dimensions apply, and
only the first occurrence of Fields 57 (Package Height), 58 (Package
Width), and 59 (Package Length) are used if multiple occurrences are
provided.
N
I
FDXE
FDXG
FDXS
All
REQUIRED*
Total number of packages in a sequence for multiple-piece shipments
(MPS).
You must provide for first and all occurrences in a multiple-piece
shipment.
Valid values are positive natural numbers only (1-9999); no decimal
places are allowed.
For shipping, use MPS.
MPS Total Packages
1982
7-72
Max=4
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-10: FedEx SmartPost Print Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
SmartPost Service Type/Postal Indicia
2417
v 10.6.1
Max=2
N
I
FDXS
US
REQUIRED*
FedEx SmartPost service type you use to ship the package. Indicates
type of shipment and postal information placed in the “stamp” area of the
label.
* Required for FedEx SmartPost.
Valid values are:
1 — Standard Mail
3 — Bound Printed Matter
4 — Obsolete
5 — Media
6 — Parcel Post
If the customer ships a FedEx SmartPost shipment with Field 2417
(Service Type) set to 1 (Standard Mail) and passes in Field 2416 set
either to position 1, 3, 5, or left blank, the position of Field 2416 defaults
to 4 (Return Service Requested). Customer will then receive the
informational message “Your ancillary endorsement has been changed
per USPS regulation.”
If FSMS has defaulted the value in Field 2416 to the value of 2 (based on
the conditions described for Field 2417), the following informational
message (Message Code 5042) will be returned to the customer, “Your
ancillary endorsement has been changed to 2 (Address Service
Requested). Please note that ancillary endorsement can only be 2
(Address Service Requested) or 4 (Return Service Requested) for FedEx
SmartPost Standard Mail shipments with Delivery Confirmation.”
If a customer processes a 020 Shipping transaction with Field 2417
(Service Type) set to 1 (FedEx SmartPost Standard Mail) with Delivery
Confirmation, and Field 2416 (Ancillary Endorsement) is not sent in,
blank, or set to any value other than 2 (Address Service Requested) or 4
(Return Service Requested), then FSMS defaults the value for Field 2416
to 2 (Address Service Requested).
If Field 2417 (FedEx SmartPost Service Type) is passed in the 020
Shipping transaction and set to 1 (FedEx SmartPost), 3 (Bound Printed
Matter) or 5 (FedEx SmartPost Media), and if Delivery Confirmation
exception is not set in CHEERS (internal system), then Delivery
Confirmation will be ‘Y’.
The customer will not be able to turn Delivery Confirmation on or off at the
shipment level. Delivery Confirmation must be read from FedEx at the
account-level.
For shipping, use Open Ship or MPS.
See FedEx SmartPost Service Types for more information
FedEx Ship Manager® Server Developer Guide
7-73
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-10: FedEx SmartPost Print Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Package Association and Print Mode
2600
Max=2
N
I
FDXE
FDXG
FDXS
US
Optional
Specifies the type of package association and print label mode to use;
that is, whether labels “print-at-end” or “print-as-you-go”.
Valid values are for FedEx Express and FedEx Ground only:
1 — (default) Domestic MPS non-associated, FedEx Express C.O.D.
MPS associated, FedEx Express International MPS associated. Prints
labels using package or shipment confirmation rules.
2 — Domestic U.S. MPS for FedEx Express and FedEx Ground services.
Package association. Prints labels with each shipment Confirm
transaction (Print-At-The-End).
3 — Domestic U.S. MPS for FedEx Express and FedEx Ground services.
Package association. Prints labels for each Create/Add Package
transaction (Print-As-You-Go).
4 — Package non-associated and labels printed with each Create/Add
Piece transaction for Domestic MPS; Print-As-You-Go (PAYG-NA)
Note: If customer ships FedEx SmartPost via the 020 transaction and
passes in Field 2600 via the Open Ship method with a value other than
4, and also passes Field 541 (Open Ship Flag) set to position 1 (Create)
or 4 (Add), and also passes in Field 2417 (FedEx SmartPost Service
Type/Postal Indicia), Error Message 2645, “Package Association is not
available with this service,” is returned. If Field 2600 was set to position
1 or 2, left blank, or passed in with an invalid value (0, 5 - 9), labels print
at the end. If Field 2600 was set to position 3 or 4, labels print with each
Create and Add Piece.
Note: For shipping, use Open Ship or MPS
Note: You must CONFIRM the shipment on the same date as CREATE,
otherwise, the label will have the incorrect ship date
Shipment Purchase Order Number
3001
7-74
Max=30
A/N
I
FDXE
FDXG
FDXS
US
CA
INTL
Field Level: Shipment
Optional
Specifies the purchase order number for the shipment.
Use Field 3001 to print the purchase order number on a Returns label.
Use only for shipments of two or more packages to the same recipient.
This value prints on the thermal label. For intra-U.S. and intra-CA, this is
displayed on the FedEx Express laser and image labels. It is displayed in
the Ref. #2 Field on the FedEx Express invoice and P.O. # Field on the
FedEx Ground invoice.
This field can only be used for shipments of two or more packages to the
same recipient.
This field can be used in the same transaction with the other two shipment
level reference number Fields: 3002 (Shipment Invoice Number) and
3003 (Shipment Customer Reference Information).
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-10: FedEx SmartPost Print Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Shipment Invoice Number
3002
Max=30
A/N
I
FDXE
FDXG
FDXS
US
CA
Field Level: Shipment
Optional
Specifies the invoice number of the shipment.
Use to Field 3002 to print the invoice number on a Returns label. Use only
for shipments of two or more packages to the same recipient.
This value prints on the thermal label. For intra-U.S. and intra-CA, this is
displayed on the FedEx Express laser and image labels. It is displayed in
the Ref. #3 field on the FedEx Express invoice.
Use this field for shipments of two or more packages to the same
recipient.
This field can be used in the same transaction with the other two shipment
level reference number Fields: 3001 (Shipment Purchase Order Number)
and 3003 (Shipment Customer Reference Information).
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
I
FDXE
FDXG
FDXS
All
Field Level: Package
Optional
Indicates nonstandard packaging is used.
Nonstandard packaging is a container that meets one of these criteria:
• Greater than 60" on any one side (not to exceed 108")
• Not fully enclosed/encased in an outer shipping container
• Encased in an outer container made of metal, wood, hard plastic or
foamed material
Valid values are:
Y — nonstandard packaging used
N — standard packaging used (default)
If you enter dimensions or dimensional criteria that are nonstandard,
FSMS sets this flag to Y automatically. For shipping, use Single Shot,
Single Piece, Open Ship, or MPS.
Nonstandard Container Flag
3018-#
v 10.6.1
Max=1
A
FedEx Ship Manager® Server Developer Guide
7-75
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-10: FedEx SmartPost Print Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Package Purchase Order Number
3056-#
Max=30
AKE
I
FDXE
FDXG
FDXS
US
CA
INTL
Field Level: Package
Optional
When used to create or print a Bill of Lading (BOL), this prints in the
Purchase Order # section of the BOL. Each additional BOL order number
prints directly below each article description. Field 3056 is the only Field
that supplies the full set for the BOL.
For Domestic FedEx Ground and International: this Field prints the
package purchase order number to a thermal label.
For intra-U.S. and intra-CA, this is displayed on the FedEx Express laser
and image labels. It is displayed in the Ref. #2 Field ID on the FedEx
Express invoice and P.O. # field on the FedEx Ground invoice.
Note: This field is a package level field and should not be used if a shipment level purchase order number has been assigned in Field 3001
(Shipment Purchase Order Number). If this Field is used simultaneously
with Field 3001, then Field 3001 is ignored. Package level fields take
precedence.
For shipping. use Single Shot, Single Piece, Open Ship, or MPS.
A/N
I
FDXE
FDXG
FDXS
US
CA
INTL
Field Level: Package
Optional
Prints the package invoice number on the thermal label.
For intra-U.S. and intra-CA, this is displayed on the FedEx Express laser
and image labels. It is displayed in the Ref. #3 Field ID on the FedEx
Express invoice.
Field 3057 is a package level field and must not be used if a shipment
level invoice number has been assigned in Field 3002 (Shipment Invoice
Number). If this field is used simultaneously with Field 3002, then Field
3002 is ignored. Package level fields take precedence.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
N
I
FDXE
FDXG
FDXS
All
Field Level: Shipment for single transactions
Field Level: Package for 020/120 Global Ship Request/Reply Open Ship
transactions
Optional
Indicates the type of rates returned in the 120 Global Ship Reply
Transaction
1 — Discount Rates only (default)
2 — List Rates and Discount Rates
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Package Invoice Number
3057-#
Max=30
Rate Quote Type
3062
7-76
Max=1
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-10: FedEx SmartPost Print Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
End of Record Indicator
99
Max=0
NULL
I
All
All
Field Level: Shipment
REQUIRED
Indicates the end of a transaction. The format is 99,"" (99 followed by a
comma and two quotation marks). All FSMS transactions must end with
99,"".
Coding a Basic FedEx SmartPost E-Mail Returns Shipping
Transaction
Table 7-11: FedEx SmartPost E-Mail Returns Label Fields
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
Description
Transaction Code
0
Max=3
All
All
Field Level: Shipment
REQUIRED
Indicates the start of a transaction.
For example, 0,"033" or 0,"33" signifies the start of the 033 Cancel E-Mail
Label transaction.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Customer Transaction Identifier
1
Max=20
FDXE
FDXG
FDXS
REQUIRED
The Transaction ID allows the customer to link transaction Replies back
to the transaction Requests in the case of a bulk shipment. The software
does not require this field, but it is available and recommended for
customer use.
FDXE
FDXG
FDXS
REQUIRED
Required for Returns if Field 32 is not used.
The “Shipper” is the returning party.
FDXE
FDXG
FDXS
REQUIRED
Required for Returns.
Shipper Information
Sender Company
4
Max=30
Sender Address Line 1
5
v 10.6.1
Max=35
FedEx Ship Manager® Server Developer Guide
7-77
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-11: FedEx SmartPost E-Mail Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Sender Address Line 2
6
Max=35
FDXE
FDXG
FDXS
REQUIRED
Required for Returns.
FDXE
FDXG
FDXS
REQUIRED
Required for Returns.
FDXE
FDXG
FDXS
REQUIRED
Required for Returns.
FDXE
FDXG
FDXS
REQUIRED
Required for Returns.
Sender City
7
Max=35
Sender State / Province
8
Max=2
Sender Postal Code
9
Max=10
Sender FedEx Express Account Number
10
Max=9
FDXE
FDXG
FDXS
REQUIRED
Required for Returns.
FDXE
FDXG
FDXS
REQUIRED*
Required if shipment is being sent to a company. If this field is not
applicable, Field 12 (Recipient Name) must be completed.
FDXE
FDXG
FDXS
REQUIRED*
Required is shipment is being sent to an individual. If this field is not
applicable, Field 11 (Recipient Company) must be completed.
FDXE
FDXG
FDXS
REQUIRED*
The first address line of the recipient address.
FDXE
FDXG
FDXS
Optional
The second address line of the recipient address.
Recipient Information
Recipient Company
11
Max=35
Recipient Contact Name
12
Max=35
Recipient Address Line 1
13
Max=35
Recipient Address Line 2
14
7-78
Max=35
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-11: FedEx SmartPost E-Mail Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Recipient City
15
Max=
Exp-35
Gnd-34
FDXE
FDXG
FDXS
REQUIRED
A minimum of three characters are required and the leading character
cannot be numeric.
FedEx Ground is limited to 20 characters.
If a military address state code (AA, AE, or AP) is passed in Field 16 in
the 020 Shipping transaction for a FedEx SmartPost shipment, FSMS will
allow a value of *PO (i.e. APO, FPO, or DPO) to be passed in for the
recipient city.
Valid values are:
APO — Army Post Office
FPO — Fleet Post Office
DPO — Diplomatic Post Office
Note: International FedEx SmartPost shipments can only be made to
military addresses.
If a customer attempts to process a FedEx SmartPost shipment to one of
the AA, AE, or AP state codes (Field 16) and the Recipient City (Field 15)
code begins with any value other than *PO (where * represents a wildcard
before the letters ‘PO’ as in APO, FPO, or DPO), then Error Code 2731
is returned, with the message “The city name must begin with APO, FPO,
or DPO for this destination”, and the transaction fails.
Recipient State / Province
16
Max=2/14
FDXE
FDXG
FDXS
REQUIRED*
Required for U.S. Domestic, CA, PR.
Length is 2 for CA, PR, and US.
Length is 14 for all others.
FDXE
FDXG
FDXS
REQUIRED*
Required if Field 23 (Payment Code) is Bill 3rd Party.
Payor Account Number
20
Max=9
Pay Type
23
Max=1
N
I
FDXE
FDXG
FDXS
All
Field Level: Shipment
REQUIRED
Code for payment type. FedEx SmartPost® payment types are:
1 — Bill Sender (default)
FedEx SmartPost® Returns payment types are:
6 — Bill Associated Account
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
Reference Information/Package Customer Reference Number
25-#
v 10.6.1
Max=39/
30
FDXE
FDXG
FDXS
Optional
Express Usage: 39 character limit.
Ground Usage: 30 character limit.
FedEx Ship Manager® Server Developer Guide
7-79
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-11: FedEx SmartPost E-Mail Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Declared Value /Carriage Value
26-#
Max=11
FDXE
FDXG
FDXS
Optional
The declared or carriage value of the shipment. There are no implied
decimal places.
$1000 for a FedEx Express shipment and Packaging Type is Customer
Packaging, FedEx Box, or FedEx Tube®.
$500 for a FedEx Express shipment and Packaging Type is FedEx Pak®
or FedEx Envelope®.
FedEx Express Freight limits are the same as for an outbound Freight
shipment.
$100 for a FedEx Ground or FHD shipment.
Shipper Information
Sender Contact Name
32
Max=35
FDXE
FDXG
FDXS
REQUIRED
Required for Returns if Field 4 is not used.
FedEx SmartPost Shipment Information
HAL Address
44
Max=35
FDXE
FDXS
Optional
Max=35
FDXE
FDXS
Optional
FDXE
FDXS
Optional
FDXE
FDXS
Optional
FDXE
FDXS
Optional
FDXE
FDXG
FDXS
REQUIRED
See Note 1 in Appendix E of this document.
FDXE
FDXS
Optional
When set to Y, this field indicates the shipper has a Signature Release on
file with FedEx.
HAL City
46
HAL State
47
Max=2
HAL Postal Code
48
Max=10
HAL Phone Number
49
Max=15
Recipient Country
50
Max=2
Signature Release
51
7-80
Max=1
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-11: FedEx SmartPost E-Mail Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Package Information
Package Height
57-#
Max=3
FDXE
FDXG
FDXS
REQUIRED*
Required for shipping FedEx Express Freight.
Recommended if using customer packaging to ensure accurate billing.
Minimum Express dimensions in IN are 7x4x2 (LxWxH).
See the FedEx Service Reference Guide for details on Dim Weighting
(Express) and Oversize conditions (Ground and Express).
FDXE
FDXG
FDXS
REQUIRED*
Required for shipping FedEx Express Freight.
Recommended if using customer packaging to ensure accurate billing.
Minimum Express dimensions in IN are 7x4x2 (LxWxH).
FDXE
FDXG
FDXS
REQUIRED*
Required for shipping FedEx Express Freight.
Recommended if using customer packaging to ensure accurate billing.
Minimum Express dimensions in IN are 7x4x2 (LxWxH).
FDXE
FDXG
FDXS
Optional
Defaults to USD.
FDXE
FDXG
FDXS
REQUIRED
Defaults to LBS.
FDXE
FDXG
FDXS
REQUIRED
Required for Returns.
FDXE
FDXG
FDXS
REQUIRED
FDXE
FDXG
FDXS
REQUIRED*
Enter & for Residential Delivery
Package Width
58-#
Max=3
Package Length
59-#
Max=3
Customs Currency Type
68
Max=3
Weight Units
75
Max=3
Sender Country Code
117
Max=2
Sender Phone Number
183
Max=15
Required for Returns.
Residential Delivery Flag
440
v 10.6.1
Max=1
FedEx Ship Manager® Server Developer Guide
7-81
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-11: FedEx SmartPost E-Mail Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Meter Number
498
Max=6
FDXE
FDXG
FDXS
REQUIRED
Defaults to Master meter.
If one to one relationship exists between meter numbers and account
numbers, i.e. no more than one meter number per account number, then
the meter number or the account number alone may be used in the
transaction.
FDXE
FDXG
FDXS
Optional
FDXE
FDXS
REQUIRED*
Required if Field 51 is Y.
The customer’s Signature Release Number that is on file with FedEx.
FDXE
FDXS
Optional
Enter & if the package originates from an inside pickup area.
Freight Only.
FDXE
FDXS
Optional
Enter Y if the package will travel to an inside delivery area.
Freight Only.
FDXE
FDXG
FDXS
Optional
Alphanumeric identification of the FedEx middleware name.
FDXE
FDXG
FDXS
Optional
Alphanumeric identification of the FedEx middleware version.
FDXE
FDXS
REQUIRED*
Required to hold the package for pickup at the FedEx facility.
FDXE
FDXG
FDXS
Optional
Sender Fax Number
1103
Max=10
Release Authorization Number
1118
Max=10
Service Options and Notes
Inside Pickup Flag
1120
Max=1
Inside Delivery Flag
1121
Max=1
FedEx Middleware Product Name
1148
Max=4
FedEx Middleware Product Version
1149
Max=4
Hold at Location Flag
1200
Max=1
Sender’s E-mail Address
1201
7-82
Max=120
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-11: FedEx SmartPost E-Mail Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Recipient’s E-mail Address
1202
Max=120
FDXE
FDXS
REQUIRED
E-mail address of the Recipient.
FDXE
FDXG
FDXS
REQUIRED*
Ground Usage: Required if 1206 is set to Y. Only a single occurrence is
allowed.
Express Usage: Required if 1206 is set to Y. Up to three occurrences
allowed.
FDXE
FDXG
FDXS
REQUIRED*
Ground Usage: One occurrence of either Field 1206 OR 3035 are
required.
Express Usage: Up to three occurrences of Field 1206 are allowed.
FDXE
FDXS
Obsolete field.
REQUIRED
When set to Y, this field indicates the recipient signature is required for
delivery.
This field is used to override a Signature Release.
FDXE
FDXS
REQUIRED
Indicates whether the shipment contains dry ice.
*Required if shipment contains dry ice.
Valid values are:
Y — Shipment contains dry ice
N — Shipment does not contain dry ice
Enter the dry ice weight in the same unit of measure as the package
weight, e.g. LBS or KGS. Two implied decimal places regardless of
weight type.
FDXE
FDXG
FDXS
REQUIRED
01 — Customer Packaging
02 — FedEx Pak, Express only
FDXE
FDXS
REQUIRED
FDXE
FDXG
FDXS
Optional
Other E-mail Notification Addresses
1204-#
Max=120
Other ShipAlert Notification Flag
1206-#
Max=1
Signature Required Flag
1208
Max=1
Dry Ice Flag
1268
Max=1
Packaging Type
1273
Max=2
Drop Off Flag
1333
Max=1
Recipient Pager Number
1342
v 10.6.1
Max=
FedEx Ship Manager® Server Developer Guide
7-83
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-11: FedEx SmartPost E-Mail Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Block Shipment Data
1392
Max=1
FDXE
FDXS
Optional
FDXE
FDXG
FDXS
REQUIRED
FDXE
FDXS
Optional
Required for delivery notification.
If set to Y, the corresponding e-mail addresses in Field 1204 will receive
delivery notification.
Maximum of three occurrences.
FDXE
FDXS
Optional
Required to indicate the language of the Other POD and ShipAlert e-mail.
Maximum of 3 occurrences.English (en) or French (fr).
Valid values are:
en — English (default)
fr — French
Item Description
1398-#
Max=80
Other Delivery Notification Flag (POD)
1551-#
Max=1
Other Language Code
1552-#
Max=2
Shipper Delivery Notification Flag (POD)
1553
Max=1
FDXE
FDXS
Optional
Required to provide e-mail notification of shipment to the Shipper.
FDXE
FDXS
Optional
Required to provide e-mail notification of delivery to the Shipper.
FDXE
FDXS
Optional
Required to indicate the language of the Shipper POD and ShipAlert email.
Valid values are:
en — English (default)
fr — French
Shipper ShipAlert Flag
1554
Max=1
Shipper Language Code
1555
Max=2
Recipient Delivery Notification Flag (POD)
1556
Max=1
FDXE
FDXS
Optional
Required to provide e-mail notification of delivery to the Recipient.
FDXE
FDXS
Optional
Required to provide e-mail notification of delivery to the Recipient.
Recipient ShipAlert Flag
1557
7-84
Max=1
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-11: FedEx SmartPost E-Mail Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Recipient Language Code
1558
Max=2
FDXE
FDXS
Optional
Required to indicate the language of the Recipient POD and ShipAlert email.
Valid values are:
en — English (default)
fr — French
FDXE
FDXG
FDXS
Optional
If set to Y, this field indicates that the merchant has agreed to allow the
return shipment to be picked up on a Saturday and the merchant agrees
to pay the Saturday pickup surcharge. If the Return shipper generates the
label on a Friday and this flag is set to Y, it is assumed this is the only
option.
If this field is set to N, the pickup date is assumed to be the next business
day.
FDXE
FDXG
FDXS
REQUIRED*
Maximum Express (non-Freight) and Ground weights — 150 lbs.
Maximum Home Delivery weight — 70 lbs.
FDXE
FDXS
REQUIRED
Enter the dry ice weight in the same unit of measure as the package
weight, e.g. LBS or KGS. Two implied decimal places regardless of
weight type.
FDXE
FDXG
FDXS
Optional
FDXE
FDXG
FDXS
Optional
If used, the RMA Number is printed on the label and uploaded to FedEx
systems. It is then available for tracking and will be included on the
customer invoice.
FDXE
FDXG
FDXS
Optional
Saturday Pickup Flag
1646
Max=1
Package Weight / Shipment Weight
1670-#
Max=10.2
Dry Ice Weight
1684-#
Max=10.2
Saturday Delivery Flag
1690
Max=1
RMA Number
2210
Max=20
Recipient Contact Fax Number
2254
v 10.6.1
Max=
FedEx Ship Manager® Server Developer Guide
7-85
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-11: FedEx SmartPost E-Mail Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
E-Mail Label Expiration Date
2387
Max=8
FDXE
FDXG
FDXS
REQUIRED
The expiration date of the online return label.
Can be up to 30 calendar days from the date the label is requested.
Default: none
Format: CCYYMMDD
FDXE
FDXG
FDXS
Optional
An optional message that can be sent to the Returning Party designated
in Field 2392.
FDXE
FDXG
FDXS
REQUIRED
The phone number of the receiving merchant. This may be different than
the Recipient Phone Number.
The phone number length must be 10 numeric characters, e.g.
9015551212.
FDXE
FDXG
FDXS
REQUIRED
The e-mail address of the party that will be receiving the e-mail label and/
or returning the package.
Returning Party E-mail Message
2388
Max=200
Merchant Contact Phone Number
2389
Max=10
Returning Party E-mail Address
2392
Max=120
SmartPost Service Type/Postal Indicia
2417
7-86
Max=2
N
I
FDXS
US
REQUIRED*
FedEx SmartPost service type you use to ship the package. Indicates
type of shipment and postal information placed in the “stamp” area of the
label.
* Required for FedEx SmartPost.
Valid values are:
1 — Standard Mail
3 — Bound Printed Matter
4 — Obsolete
5 — Media
6 — Parcel Select
7 — FedEx SmartPost Returns
If customer ships a FedEx SmartPost shipment with Field 2417 (Service
Type) set to 1 (Standard Mail) and passes in Field 2416 set either to
position 1, 3, 5, or left blank, the position of Field 2416 defaults to 4
(Return Service Requested). The customer then receives the
informational message, “Your ancillary endorsement has been changed
per USPS regulation.”
If FSMS has defaulted the value in Field 2416 to the value of 2 (based on
the conditions described for Field 2417), the following informational
message (Message Code 5042) will be returned to the customer, “Your
ancillary endorsement has been changed to 2 (Address Service
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-11: FedEx SmartPost E-Mail Returns Label Fields (Continued)
Field ID
2417
(cont.)
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Max=2
N
I
FDXS
US
Description
Requested). Please note that ancillary endorsement can only be 2
(Address Service Requested) or 4 (Return Service Requested) for FedEx
SmartPost Standard Mail shipments with Delivery Confirmation.”
If a customer processes a 020 Shipping transaction with Field 2417
(Service Type) set to 1 (FedEx SmartPost Standard Mail) with Delivery
Confirmation, and Field 2416 (Ancillary Endorsement) is not sent in,
blank, or set to any value other than 2 (Address Service Requested) or 4
(Return Service Requested), then FSMS defaults the value for Field 2416
to 2 (Address Service Requested).
If Field 2417 (FedEx SmartPost Service Type) is passed in the 020
Shipping transaction and set to 1 (FedEx SmartPost), 3 (Bound Printed
Matter) or 5 (FedEx SmartPost Media), and if Delivery Confirmation
exception is not set in CHEERS (internal system), then Delivery
Confirmation will be ‘Y’.
The customer will not be able to turn Delivery Confirmation on or off at the
shipment level. Delivery Confirmation must be read from FedEx at the
account-level.
For shipping, use Open Ship or MPS.
Non-standard Container Flag
3018-#
Max=1
FDXG
FDXS
Optional
Y if non-standard packaging is used.
Non-standard packaging is defined as a container that is greater than 60”
on any one side.
Default: N
The software will set this flag to Y if dimensions are entered and
dimensional criteria are met.
Special Instructions / FedEx Home Delivery Instructions
3021
Max=74
FHD
FDXS
Optional
A free form field to be used to provide specific delivery instructions to the
FedEx Ground courier.
ShipAlert Pre-Delivery Alert Fax Number
3035
Max=15
FDXG
FDXS
REQUIRED*
Ground Usage: One occurrence.
FDXG
FDXS
Optional
FDXG
FDXS
Optional
Package Purchase Order Number
3056-#
Max=30
AKE
Package Invoice Number
3057-#
v 10.6.1
Max=30
FedEx Ship Manager® Server Developer Guide
7-87
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-11: FedEx SmartPost E-Mail Returns Label Fields (Continued)
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Residential Pickup Flag
3231
Max=1
FDXG
FDXS
Optional
Residential pickup is only available for FedEx Ground or FHD service.
Valid values are:
Y
N
Default: N
FDXS
Optional
Valid values are:
01 — CSP
02 — Standard - FedEx owned hardware
03 — Standard - customer owned hardware
04 — FSM Enterprise
FDXS
Optional
FedEx Vendor / Client Product Name
9744
Max=4
FedEx Vendor / Client Product Version
9745
Max=
End of Record Indicator
99
Max=0
NULL
I
All
All
Field Level: Shipment
REQUIRED
Indicates the end of a transaction. The format is 99,"" (99 followed by a
comma and two quotation marks). All FSMS transactions must end with
99,"".
Creating a FedEx SmartPost Open Ship Transaction
You can perform most Open Ship functions to prepare a FedEx SmartPost shipment. The exception are the two EDIT flags in Field 541
(Open Ship Flags):
• Position 6 (EDIT/ADD Data to the Entire Shipment).
To create a FedEx SmartPost Open Ship transaction, include all required FedEx SmartPost fields (see the FedEx Ship Manager® Server
Transaction Code Reference for a list) and use Field 541 to indicate the Open Ship flag.
Table 7-12 describes the Open Ship flags in the required Field 541 (Open Ship Flags) that are appropriate for coding a FedEx SmartPost
Open Ship transaction:
7-88
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-12: FedEx SmartPost Open Ship Flag Fields
Transaction: 020 Global Ship Request - Open Ship
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
A
I
FDXS
All
REQUIRED*
Identifies transaction functions using nine one-byte flags which are set to
Y to indicate shipment level or package level flag.
Specify Y in the position(s) of the Open Ship functions used for a given
transaction. Specify N in all other positions. All flags must be used and
must be either Y or N; if you enter all Ns, all Open Ship functions are
disabled.
Default: YNNNNNNNY (CREATE and CONFIRM the Open Ship
shipment.)
Each one-byte flag is defined in sequence in the following array:
1 — CREATE an Open Ship Shipment
2 — ROUTE/Time in Transit
3 — RATE
4 — ADD a Piece
5 — EDIT a Piece
6 — N (Not applicable for FedEx SmartPost)
7 — DELETE a Piece
8 — DELETE the Shipment
9 — CONFIRM the Shipment
*Required for Open Ship.
N
I
FDXS
US
REQUIRED*
Set to the unique number passed in the CREATE transaction. The value
is a unique number per Open Ship shipment per meter and represents
the Open Ship Index.
*Required for Open Ship.
Note: Field 542 is not required if you are simultaneously performing a
CREATE or ADD transaction.
Examples of simultaneous transactions are: YYNNNNNNN which
performs a shipment level CREATE and Route/Time in Transit
transaction or NYNYNNNNN which performs a package level ADD and
shipment level Route/Time in Transit together in the same transaction.
Description
Open Ship Flags
541
Max=9
Open Ship Index
542
v 10.6.1
Max=9
FedEx Ship Manager® Server Developer Guide
7-89
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-12: FedEx SmartPost Open Ship Flag Fields (Continued)
Transaction: 020 Global Ship Request - Open Ship
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Package Association and Print Mode
2600
Max=2
N
I
Description
Transactions: 020 Global Ship Request
FDXE
FDXG
FDXS
US
Optional
Specifies the type of package association and print label mode to use —
that is, whether labels “print-at-end” or “print-as-you-go”.
Valid values are for FedEx Express and FedEx Ground only:
1 — (default) Domestic MPS non-associated, FedEx Express C.O.D.
MPS associated, FedEx Express International MPS associated. Prints
labels using package or shipment confirmation rules.
2 — Domestic U.S. MPS for FedEx Express and FedEx Ground services.
Package association. Prints labels with each shipment Confirm
transaction (Print-At-The-End).
3 — Domestic U.S, MPS for FedEx Express and FedEx Ground services.
Package association. Prints labels for each Create/Add Package
transaction (Print-As-You-Go).
Note: For Open Ship Print-As-You-Go (PAYG) shipments, you must
CONFIRM the shipment on the same date as CREATE, otherwise labels
will have the incorrect ship date.
Note: 4 — Package non-associated and labels printed with each Create/
Add Piece transaction for Domestic MPS; Print-As-You-Go (PAYG-NA)
for FedEx SmartPost. If customer ships FedEx SmartPost via the 020
transaction and passes in Field 2600 via the Open Ship method with a
value other than 4, and also passes Field 541 (Open Ship Flag) set to
position 1 (Create) or 4 (Add), and also passes in Field 2417 (FedEx
SmartPost Service Type/Postal Indicia), then Error Message 2645,
“Package Association is not available with this service,” will be returned.
If Field 2600 was set to position 1 or 2, left blank, or passed in with an
invalid value (0, 5–9), then labels will print at the end. If Field 2600 was
set to position 3 or 4, then labels will print with each Create and Add
Piece.
For shipping, use Open Ship or MPS.
Coding Pre-assigned Tracking Numbers
You can use the 004/104 Tracking Number Request/Reply transaction to obtain pre-assigned tracking numbers for FedEx SmartPost
shipments. The following transaction rules apply when obtaining a pre-assigned tracking number using the 004/104 Tracking Number
Request/Reply transaction and when using the numbers in 020 Global Ship Request transactions.
Pre-assign Tracking Number Rules
• If Field 499 (Tracking Number Type) is set to 17 — FedEx SmartPost in a 004 Tracking Number Request transaction, then the 104
Tracking Number Reply transaction returns the Delivery Confirmation Tracking Number in Field 29 (Tracking Number).
7-90
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
• If Field 499 (Tracking Number Type) is set to 18 — FedEx SmartPost Tracking Number and Ground Tracking Number, then the 104
Tracking Number Reply transaction returns the Delivery Confirmation Tracking Number in Field 4927 (Delivery Confirmation Tracking
Number) and the Ground Tracking Number in Field 29 (Tracking Number).
• To designate whether the FedEx SmartPost tracking number is returned with or without Delivery Confirmation for a specific FedEx
SmartPost service type, use Fields 2417 (FedEx SmartPost Service Type) and 3204 (Delivery Confirmation Flag) in the 004 Tracking
Number Request transaction.
• After the pre-assigned numbers are returned in the 104 Tracking Number Reply transaction, you can use them in a 020 Global Ship
Request transaction to ship the package.
• Use Field 4926 (Pre-assigned Delivery Confirmation Tracking Number) to specify the FedEx SmartPost Delivery Confirmation Tracking
Number for a package in a 020 Global Ship Request transaction.
• Use Field 1222 (Pre-assigned Tracking Number/ProNumber) to specify the Ground Tracking Number for a package in a 020 Global Ship
Request Transaction.
Table 7-13 explains the fields described in the above rules for pre-assigning tracking numbers for FedEx SmartPost.
Table 7-13: Parcel Select Transactions and Fields
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Tracking Number Type
499
Max=2
N
Description
Transactions: 004 Tracking Number Request
I
FDXE
FDXG
FDXS
All
REQUIRED
Type of tracking number requested.
FDXS: US Valid values are:
only
1 — FedEx Express U.S. (default)
2 — FedEx Express International
3 — FedEx Express International MPS1
4 — Master C.O.D.2
5 — MPS C.O.D.
7 — Canada
8 — FedEx Priority Alert
9 — FedEx Ground or FedEx Home Delivery
10 — FedEx® International DirectDistribution (IDD Surface) master
(formerly called FedEx Transborder Distribution (TD) master)
11 — FedEx® International DirectDistribution (IDD Surface) child
(formerly called FedEx Transborder Distribution (TD) child)
17 — FedEx SmartPost
18 — FedEx SmartPost Small Shipper
20 — ETD
21 — ETD with TPC
Type 9 is for FedEx Ground and FedEx Home Delivery only. Types 1-8
are for FedEx Express.
For shipping, use Single Shot, Single Piece, Open Ship, or MPS.
v 10.6.1
1
MPS is the acronym for multiple-piece shipment.
2
C.O.D. is the acronym for Collect on Delivery service
FedEx Ship Manager® Server Developer Guide
7-91
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-13: Parcel Select Transactions and Fields (Continued)
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
SmartPost Service Type/Postal Indicia
2417
7-92
Max=2
N
I
Description
Transactions: 020 Global Ship Request
FDXS
US
REQUIRED*
FedEx SmartPost service type you use to ship the package. Indicates
type of shipment and postal information placed in the “stamp” area of the
label.
* Required for FedEx SmartPost.
Valid values are:
1 — Standard Mail
3 — Bound Printed Matter
4 — Obsolete
5 — Media
6 — Parcel Select
7 — FedEx SmartPost Returns
If customer ships a FedEx SmartPost shipment with Field 2417 (Service
Type) set to 1 (Standard Mail) and passes in Field 2416 set either to
position 1, 3, 5, or left blank, the position of Field 2416 defaults to 4
(Return Service Requested). The customer then receives the
informational message, “Your ancillary endorsement has been changed
per USPS regulation.”
If FSMS has defaulted the value in Field 2416 to the value of 2 (based on
the conditions described for Field 2417), the following informational
message (Message Code 5042) will be returned to the customer, “Your
ancillary endorsement has been changed to 2 (Address Service
Requested). Please note that ancillary endorsement can only be 2
(Address Service Requested) or 4 (Return Service Requested) for FedEx
SmartPost Standard Mail shipments with Delivery Confirmation.”
If a customer processes a 020 Shipping transaction with Field 2417
(Service Type) set to 1 (FedEx SmartPost Standard Mail) with Delivery
Confirmation, and Field 2416 (Ancillary Endorsement) is not sent in,
blank, or set to any value other than 2 (Address Service Requested) or 4
(Return Service Requested), then FSMS defaults the value for Field 2416
to 2 (Address Service Requested).
If Field 2417 (FedEx SmartPost Service Type) is passed in the 020
Shipping transaction and set to 1 (FedEx SmartPost), 3 (Bound Printed
Matter) or 5 (FedEx SmartPost Media), and if Delivery Confirmation
exception is not set in CHEERS (internal system), then Delivery
Confirmation will be ‘Y’.
The customer will not be able to turn Delivery Confirmation on or off at the
shipment level. Delivery Confirmation must be read from FedEx at the
account-level.
For shipping, use Open Ship or MPS.
See FedEx SmartPost Service Types for more information
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-13: Parcel Select Transactions and Fields (Continued)
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Delivery Confirmation Flag
3204
Max=1
A/N
Description
Transactions: 020 Global Ship Request
I
FDXS
US
Obsolete field.
Optional
Indicates if Delivery Confirmation is used or not.
Valid values are:
Y — Delivery Confirmation
N — No Delivery Confirmation
FedEx SmartPost delivery confirmation will default to the value set on the
configuration screen, if Field 2417 is set to position 1, 3, or 5. If Field 2417
is set to position 6, then it will default to Y.
Delivery Confirmation Tracking Number
Transactions: 120 Global Ship Reply
4927
US
Min=1
Max=30
N
O
FDXG
FDXS
Tracking Number
29-#
Min=12
Max=25
Optional
Returns the USPS Delivery Confirmation tracking number for a FedEx
SmartPost package when FedEx Ground is configured as the pickup
carrier.
Transactions: 104 Tracking Number Reply, 020/120 Global Ship Request/Reply,
023/123 Global Delete Request/Reply, 024 Shipment Query Request, 095/195
Label Reprint Request/Reply
A
I/O
FDXE
FDXG
FDXS
All
REQUIRED*
Tracking number of the package or piece in a multiple-piece shipment
(MPS).
*Required in conjunction with Field 541 to identify the package to ADD,
EDIT or DELETE in an Open Ship 020/120 Global Ship Transaction.
Preassigned Delivery Confirmation Tracking
Number
Transactions: 020/120 Global Ship Request/Reply
4926
US
v 10.6.1
Min=1
Max=30
N
I/O
FDXG
FDXS
Optional
Returns the Pre-assigned USPS Delivery Confirmation tracking number
for a FedEx SmartPost package when FedEx Ground is configured as the
pickup carrier.
FedEx Ship Manager® Server Developer Guide
7-93
Chapter 7: Coding Transactions for FedEx SmartPost
Table 7-13: Parcel Select Transactions and Fields (Continued)
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Preassigned Tracking Number/ProNumber
Transactions: 020 Global Ship Request
1222
All
Max=15
N
I
FDXE
FDXG
FDXS
Delivery Confirmation Bar Code
2418
Max=30
A/N
O
Field Level: Package
REQUIRED*
Tracking number to be pre-assigned to the shipment. When creating a Bill
of Lading (BOL), this number is the ProNumber.
* Required if you produce custom labels. Typically not used if you allow
FSMS to create your label.
You can omit this field if:
•
A Route/Time-in-Transit transaction is performed simultaneously
with a CREATE or an ADD transaction (for example, YYNNNNNNN
or NYNYNNNNN), and a pre-assigned tracking number is not being
used.
•
The bar code string data is not required and a Route/Time-in-Transit transaction is not performed simultaneously with a CREATE or
an ADD (for example, NYNNNNNNN).
Transactions: 120 Global Ship Reply
FDXE
FDXG
FDXS
US
Delivery Confirmation Number (DCN) generated by FSMS based upon
setup in FSMS Configuration utility.
This number prints on the FedEx SmartPost label under the DCN bar
code.
Explanation of DCN:
Digits 1-3 — Identifier (420)
Digits 4-8 — ZIP code
Digits 9-10 — Application ID (91)
Digits 11-12 — Service Type Code
Digits 13-21 — DUNS #
Digits 22-29 — Package/Parcel ID
Digit 30 — MOD 10 check digit.
The last 20 digits are the tracking number and are also found in Field 29
(Tracking Number).
Note: GND UCC/EAN bar code is returned when doing FedEx Ground or
FedEx Home Delivery. However, FedEx SmartPost does not return that
field, but instead uses Field 2418 (Delivery Confirmation Bar Code).
Best practice for generating the bar code is a FedEx SmartPost custom
label.
Note: The Delivery Confirmation Number does not duplicate within a 12
month period.
7-94
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
FedEx SmartPost Transaction Samples
Refer to these code examples to learn how to code FedEx SmartPost transactions:
• 004 Tracking Number Request transaction
• 007 End-of-Day Close Request transaction
• 107 End-of-Day Close Reply transaction
• 020 Global Ship Request transaction
• 120 Global Ship Reply transaction
• 023 Global Delete Request transaction
• 123 Global Delete Reply transaction
• 035 Meter Registration Request transaction
• 135 Meter Registration Reply transaction
• 057 Demand Download Request transaction
• 157 Demand Download Reply transaction
• Open Ship transactions
004 Tracking Number Request for FedEx SmartPost
This code example uses the 004 Tracking Number Request transaction to obtain a tracking number to a FedEx SmartPost shipment. Set
Field 2417 (SmartPost Service Type/Postal Indicia) to designate whether the FedEx SmartPost pre-assigned tracking number is returned for
a specific FedEx SmartPost service type.
Request pre-assign of FedEx SmartPost tracking number for Standard Mail shipment (2417,"1")
0,"004"1,"Assign FedEx SmartPost Tracking Number"499,"17"2417,"1"99,""
Request pre-assign of FedEx SmartPost tracking number for Bound Printed Matter shipment (2417,"3")
0,"004"1,"Assign FedEx SmartPost Tracking Number"499,"17"2417,"3"99,""
007 End-of-Day Close for FedEx SmartPost
The following code example shows how to request a Close of all FedEx SmartPost shipping transactions at the end of a shipping day by
using the 007 End-of-Day Close Request transaction.
Request Close of FedEx SmartPost shipping transactions
0,"007"1,"End of Day"498,""3025,”FDXS”99,""
107 End-of-Day Close Reply for FedEx SmartPost
This code example shows the 107 End-of-Day Close Reply transaction received as the result of a request to Close all FedEx SmartPost
shipping transactions.
End-of-Day Close Reply for FedEx SmartPost shipment
0,"107"1,"End of Day"10,"123456789"498,"0123456"1939,"11"3025,"FDXS"99,""
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-95
Chapter 7: Coding Transactions for FedEx SmartPost
020 Global Ship Request for FedEx SmartPost
The following code examples show different transaction requests based on the service types available.
Note: Fields without data, which is any field followed by empty quotation marks (""), are not required for the transaction (except for Field 99
which is required to end the transaction.
Standard Mail Shipment (2417,”1”)
0,"020"1,"Step 010”11,"ABC Co"12,"FedEx Ship Manager Server"13,"FedEx SmartPost
Shipper"14,"FEDEX PARKWAY"15,"Memphis"16,"TN"17,"38107"18,"1234567890"23,"1"25,"STD A
SHIPMENT"26,"100"50,"US"75,"lbs"117,"US"187,"PNG"1670,"50"2416,"01"2417,"1"3204,"Y"99,""
Standard Mail Shipment (2417,"1") and Carrier Leave if No Response (2416,"1")
0,"020"1,"STD A WITHOUT DC"10,""11,"RECIP COMPANY"12,"ROGER RECIPIENT"13,"123 Main Street"14,"
Suite 200"15,"Portland"16,"ME"17,"04101"18,"8005551212"20,""23,"1"24,""25,"STD A NO DCN"
26,"100"50,"US"75,"lbs"117,"US"187,"PNG"498,""1670,"50"2416,"01"2417,"1"99,""
Standard Mail Shipment (2417,"1") with Carrier Leave if No Response (2416,"1")
0,"020"1,"STD A WITH DC"10,""11,"RECIP COMPANY"12,"ROGER RECIPIENT"13,"123 Main Street"
14,"Suite 200"15,"Portland"16,"ME"17,"04101"18,"8005551212"20,""23,"1"24,""25,"STD A
WITHDC"26,"100"50,"US"75,"lbs"117,"US"187,"PNG"498,""1670,"50"2416,"01"2417,"1"99,""
Parcel Select Shipment (2417,"6") with Address Service Requested (2416,"2")
0,"020"1,"STD B SHIPMENT"10,""11,"RECIP COMPANY"12,"ROGER RECIPIENT"13,"123 Main Street"
14,"Suite 200"15,"Portland"16,"ME"17,"04101"18,"8005551212"20,""23,"1"24,""25,"STD B
SHIPMENT"26,"100"50,"US"75,"lbs"117,"US"187,"PNG"498,""1670,"100"2416,"02"2417,"6"2944,"RECIP
IENT ADD LINE 3"99,""
Bound Printed Matter Shipment (2417,"3") with Forwarding Service (2416,"3")
0,"020"1,"STD B BOUND PRINTED MATTER"10,""11,"RECIP COMPANY"12,"ROGER RECIPIENT"13,"123 Main
Street"14,"Suite 200"15,"Portland"16,"ME"17,"04101"18,"8005551212"20,""23,"1"24,""25,"BOUND
PRNTD MAT"26,"100"50,"US"75,"lbs"117,"US"187,"PNG"498,""1670,"1001"2416,"03"2417,"3"2944,"
RECIPIENT ADD LINE 3"99,""
Media Shipment (2417,"5") with Change Service Requested (2416,"5")
0,"020"1,"STD B MEDIA"10,""11,"RECIP COMPANY"12,"ROGER RECIPIENT"13,"123 Main Street"
14,"Suite 200"15,"Portland"16,"ME"17,"04101"18,"8005551212"20,""23,"1"24,""25,"STD B
MEDIA"26,"100"50,"US"75,"lbs"117,"US"187,"PNG"498,""1670,"1000"2416,"05"2417,"5"2944,"RECIPIE
NT ADD LINE 3"99,""
Parcel Select Shipment (2417,"6") with Change Service Requested (2416,"5")
0,"020"1,"STD B PARCEL SELECT"10,""11,"RECIP COMPANY"12,"ROGER RECIPIENT"13,"123 Main Street"
14,"Suite 200"15,"Portland"16,"ME"17,"04101"18,"8005551212"20,""23,"1"24,""25,"STD B
PARCELPOST"26,"100"50,"US"75,"lbs"117,"US"187,"PNG"498,""1670,"1000"2416,"05"2417,"6"2944,"
RECIPIENT ADD LINE 3"99,""
120 Global Ship Reply for FedEx SmartPost
The following code examples show the different replies you can receive to a 020 Global Ship Request transaction depending on the USPS
service type you requested for your FedEx SmartPost shipment.
Note: Fields without data (any field followed by empty quotation marks "") are not required for the transaction (except for Field 99 which is
required to close the transaction).
7-96
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
Reply to FedEx SmartPost USPS Standard Mail shipment
0,"120"1,"STANDARD MAIL SHIPMENT"10,"123456789"29,"01123456987000000413"34,"156"35,""36,""37,
"156"498,"123456"542,""1092,"5"1274,""1596,"0"1598,"0"2418,"420041019101123456987000000413"
99,""
Reply to FedEx SmartPost USPS Bound Printed Matter shipment
0,"120"1,"BOUND PRINTED MATTER SHIPMENT"10,"123456789"29,"01123456987000000422"34,"229"35,
""36,""37,"229"498,"123456"542,""1092,"5"1274,""1596,"0"1598,"0"2418,
”420041019101123456987000000422”99,""
Reply to FedEx SmartPost USPS Bound Printed Matter shipment
0,"120"1,"BOUND PRINTED MATTER"10,"123456789"29,"01123456987000000431"34,"561"35,""36,""37,
"561"498,"123456"542,""1092,"5"1274,""1596,"0"1598,"0"2418,"420041019101123456987000000431"
99,""
Reply to FedEx SmartPost USPS Media shipment
0,"120"1,"MEDIA"10,"123456789"29,"01123456987000000459"34,"561"35,""36,""37,"561"498,
"123456"542,""1092,"5"1274,""1596,"0"1598,"0"2418,"420041019101123456987000000459"99,""
Reply to FedEx SmartPost USPS Parcel Post shipment
0,"120"1,"PARCEL POST SHIPMENT"10,"123456789"29,"01123456987000000468"34,"561"35,""36,""
37,"561"498,"123456"542,""1092,"5"1274,""1596,"0"1598,"0"2418,"420041019101123456987000000468
"99,""
023/123 Global Delete Request/Reply for FedEx SmartPost
These two code examples show how to delete a FedEx SmartPost package by specifying the tracking number.
Delete a FedEx SmartPost package by tracking number
0,"023"1,"Global Delete Package"29,"01123456987000000556"498,""99,""
0,"023"1,"Global Delete Package"29,"01123456987000000565"498,""99,""
Reply to above requests to delete FedEx SmartPost packages
0,"023"1,"Global Delete Package"29,"01123456987000000556"498,""99,""
0,"023"1,"Global Delete Package"29,"01123456987000000565"498,""99,""
FedEx SmartPost Open Ship Transactions
The following code examples are specific to shipping a FedEx SmartPost shipment using the Open Ship shipping method.
ABC Company Open Ship Transaction Samples
0,"020"1,"Step 001-01"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"23,"1"25,"Bound Printed
Matter"50,"US"75,"lbs"117,"US"187,"PNG"498,"400085"541,"YNNNNNNNN"542,"z1"1670,"75"2416,"1"24
17,"3"2600,"1"3204,"Y"99,""
0,"020"1,"Step 001-02"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"23,"1"25,"Bound Printed
Matter"26,"100"50,"US"75,"lbs"117,"US"187,"PNG"498,"400085"541,"NNNYNNNNN"542,"z1"1670,"50"24
16,"1"2417,"3"3204,"Y"99,""
0,"020"1,"Step 001-03"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"25,"Bound Printed
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-97
Chapter 7: Coding Transactions for FedEx SmartPost
Matter"50,"US"75,"lbs"116,"2"117,"US"187,"PNG"498,"400085"541,"NNNNNNNNY"542,"z1"2416,"3"2417
,"3"3204,"Y"99,""
0,"020"1,"Step 001-01"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"23,"1"25,"Standard B Media
Mail"50,"US"75,"lbs"117,"US"187,"PNG"498,"400085"541,"YNNNNNNNN"542,"z2"1670,"200"2416,"1"241
7,"5"2600,"1"3204,"Y"99,""
0,"020"1,"Step 001-02"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"23,"1"25,"Standard B Media
Mail"26,"100"50,"US"75,"lbs"117,"US"187,"PNG"498,"400085"541,"NNNYNNNNN"542,"z2"1670,"300"241
6,"1"2417,"5"3204,"Y"99,""
0,"020"1,"Step 001-03"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"25,"Standard B Media
Mail"50,"US"75,"lbs"116,"2"117,"US"187,"PNG"498,"400085"541,"NNNNNNNNY"542,"z2"2416,"3"2417,"
5"3204,"Y"99,""
0,"020"1,"Step 001-01"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"23,"1"25,"Standard B Parcel
Post"50,"US"75,"lbs"117,"US"187,"PNG"498,"400085"541,"YNNNNNNNN"542,"z3"1670,"100"2416,"1"241
7,"6"2600,"1"3204,"Y"99,""
0,"020"1,"Step 001-02"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"23,"1"25,"Standard B Parcel
Post"26,"100"50,"US"75,"lbs"117,"US"187,"PNG"498,"400085"541,"NNNYNNNNN"542,"z3"1670,"200"241
6,"1"2417,"6"3204,"Y"99,""
0,"020"1,"Step 001-03"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"25,"Standard B Parcel
Post"50,"US"75,"lbs"116,"2"117,"US"187,"PNG"498,"400085"541,"NNNNNNNNY"542,"z3"2416,"3"2417,"
6"3204,"Y"99,""
0,"020"1,"Step 001-01"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"23,"1"25,"STD
Mail"50,"US"75,"lbs"117,"US"187,"PNG"498,"400085"541,"YNNNNNNNN"542,"z4"1670,"2"2416,"2"2417,
"1"2600,"1"3204,"Y"99,""
,"020"1,"Step 001-02"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"23,"1"25,"STD
Mail"26,"100"50,"US"75,"lbs"117,"US"187,"PNG"498,"400085"541,"NNNYNNNNN"542,"z4"1670,"2"2416,
"2"2417,"1"3204,"Y"99,""
0,"020"1,"Step 001-03"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"25,"STD
Mail"50,"US"75,"lbs"116,"2"117,"US"187,"PNG"498,"400085"541,"NNNNNNNNY"542,"z4"2416,"2"2417,"
1"3204,"Y"99,""
Open Ship Future Day Transactions
0,"020"1,"Step 001-01"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"23,"1"24,"20100821"25,"Bound Printed
Matter"50,"US"75,"lbs"117,"US"187,"PNG"498,"400085"541,"YNNNNNNNN"542,"z1"1670,"75"2416,"1"24
17,"3"2600,"1"3204,"Y"99,""
0,"020"1,"Step 001-02"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"23,"1"24,"20100821"25,"Bound Printed
Matter"26,"100"50,"US"75,"lbs"117,"US"187,"PNG"498,"400085"541,"NNNYNNNNN"542,"z1"1670,"50"24
16,"1"2417,"3"3204,"Y"99,""
0,"020"1,"Step 001-03"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"24,"20100821"25,"Bound Printed
Matter"50,"US"75,"lbs"116,"2"117,"US"187,"PNG"498,"400085"541,"NNNNNNNNY"542,"z1"2416,"3"2417
,"3"3204,"Y"99,""
0,"020"1,"Step 001-01"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"23,"1"24,"20100821"25,"Standard B Media
Mail"50,"US"75,"lbs"117,"US"187,"PNG"498,"400085"541,"YNNNNNNNN"542,"z2"1670,"200"2416,"1"241
7,"5"2600,"1"3204,"Y"99,""
7-98
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 7: Coding Transactions for FedEx SmartPost
0,"020"1,"Step 001-02"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"23,"1"24,"20100821"25,"Standard B Media
Mail"26,"100"50,"US"75,"lbs"117,"US"187,"PNG"498,"400085"541,"NNNYNNNNN"542,"z2"1670,"300"241
6,"1"2417,"5"3204,"Y"99,""
0,"020"1,"Step 001-03"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"24,"20100821"25,"Standard B Media
Mail"50,"US"75,"lbs"116,"2"117,"US"187,"PNG"498,"400085"541,"NNNNNNNNY"542,"z2"2416,"3"2417,"
5"3204,"Y"99,""
0,"020"1,"Step 001-01"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"23,"1"24,"20108021"25,"Standard B Parcel
Post"50,"US"75,"lbs"117,"US"187,"PNG"498,"400085"541,"YNNNNNNNN"542,"z3"1670,"100"2416,"1"241
7,"6"2600,"1"3204,"Y"99,""
0,"020"1,"Step 001-02"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"23,"1"24,"20108021"25,"Standard B Parcel
Post"26,"100"50,"US"75,"lbs"117,"US"187,"PNG"498,"400085"541,"NNNYNNNNN"542,"z3"1670,"200"241
6,"1"2417,"6"3204,"Y"99,""
0,"020"1,"Step 001-03"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"24,"20100821"25,"Standard B Parcel
Post"50,"US"75,"lbs"116,"2"117,"US"187,"PNG"498,"400085"541,"NNNNNNNNY"542,"z3"2416,"3"2417,"
6"3204,"Y"99,""
0,"020"1,"Step 001-01"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"23,"1"24,"20100821"25,"STD
Mail"50,"US"75,"lbs"117,"US"187,"PNG"498,"400085"541,"YNNNNNNNN"542,"z4"1670,"2"2416,"2"2417,
"1"2600,"1"3204,"Y"99,""
0,"020"1,"Step 001-02"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"23,"1"24,"20100821"25,"STD
Mail"26,"100"50,"US"75,"lbs"117,"US"187,"PNG"498,"400085"541,"NNNYNNNNN"542,"z4"1670,"2"2416,
"2"2417,"1"3204,"Y"99,""
0,"020"1,"Step 001-03"11,"ABCCompany"12,"FXRS"13,"SmartPost small shipper"14,"FEDEX
PARKWAY"15,"Memphis"16,"TN"17,"38017"18,"1234567890"24,"20100821"25,"STD
Mail"50,"US"75,"lbs"116,"2"117,"US"187,"PNG"498,"400085"541,"NNNNNNNNY"542,"z4"2416,"2"2417,"
1"3204,"Y"99,""
APO Shipping Transaction
0,"020"11,"COSTCO.COM CH"13,"VENDOR #66860-00"14,"999 LAKE
DRIVE"15,"Military"16,"AE"17,"09302"18,"4253136151"23,"1"25,"is"50,"US"498,""1660,"N"1670,"20
0"2417,"6"3204,"Y"99,""
0,"120"1,""10,"214877600"29,"02222222222000000040"34,"568"35,""36,""37,"568"498,"400085"542,"
"1092,"9"1274,""1596,"0"1598,"0"2418,"420093029102222222222000000040"99,""
ADD Standard Mail Package without Delivery Confirmation and with Address Service Requested
0,"020"1,"STANDARD MAIL SHIPMENT"10,""11,"RECIP COMPANY"12,"ROGER RECIPIENT"13,"123 Main
Street"14,"Suite 200"15,"Portland"16,"ME"17,"04101"18,"8005551212"20,""23,"1"24,""25,
"STANDARD MAIL SHIPMENT"26,"100"50,"US"75,"lbs"117,"US"187,"PNG"498,""541,"NNNYNNNNN"542,
"556"1670,"75"2416,"02"2417,"1"99,""
v 10.6.1
FedEx Ship Manager® Server Developer Guide
7-99
Chapter 7: Coding Transactions for FedEx SmartPost
ADD a Bound Printed Matter Package with Return Service Requested
0,"020"1,"BOUND PRINTED MATTER SHIPMENT"10,""11,"RECIP COMPANY"12,"ROGER RECIPIENT"13,"123
Main Street"14,"Suite 200"15,"Portland"16,"ME"17,"04101"18,"8005551212" 20,""23,"1"24,""25,
"BOUND PRINTED MATTER SHIPMENT"26,"100"50,"US"75,"lbs"117,"US"187,"PNG"
498,""541,"NNNYNNNNN"542,"556"1670,"850"2416,"04"2417,"3"99,""
Print-As-You-Go Labels for FedEx SmartPost
FedEx SmartPost customers can now generate shipping labels using both the FSMS Open Ship and Print-As-You-Go (PAYG) features.
Note: When using these functions for FedEx SmartPost, Print-As-You-Go Labels can only be non-associated; that is, there can be no
association between individual package numbers and total number of packages, such as 1 of 3, 2 of 3, 3 of 3. The following examples show
how to print labels as you process packages in 020 Global Ship Request transactions, rather than waiting for the final confirmation.
This example shows how to create and print a label:
0,"020"1,"Print As You Go - create/print"11,"COMPANY"12,"ROGER RECIPIENT"13,"123 Main
Street"14,"Suite 200"15,"Memphis"16,"TN"17,"38116"18,"8005551212"23,"1"25,"Bound Printed
Matter"50,"US"75,"lbs"117,"US"187,"188"498,
"124765"537,"\\127.0.0.1\ZP5"541,"YNNNNNNNN"542,"AA8822"1670,"75"2416,"1"2417,"3"2600,"4"3204
,"Y"99,""
This example shows how to add a package and print a label:
0,"020"1,"Print As You Go - add/print"11,"COMPANY"12,"ROGER RECIPIENT"13,"123 Main
Street"14,"Suite 200"15,"Memphis"16,"TN"17
,"38116"18,"8005551212"23,"1"25,"Bound Printed
Matter"26,"100"50,"US"75,"lbs"117,"US"187,"188"498,"124765"537,"\\127.0.0.1\
ZP5"541,"NNNYNNNNN"542,"AA8811"1670,"50"2416,"1"2417,"3"2600,"4"3204,"Y"99,""
This example shows how to add another package and print a label:
0,"020"1,"Bound PM - Print As You Go - add another and print"11,"COMPANY"12,"ROGER RECIPIENT"
13,"123 Main Street"14,"Suite 200"15,"Memphis"16,"TN"17,"38116"18,"8005551212"23,"1"25,"Bound
Printed Matter"26,"100"50,"US"75,"lbs
"117,"US"187,"188"498,"124765"537,"\\127.0.0.1\ZP5"541,
"NNNYNNNNN"542,"AA8811"1670,"40"2416,"1"2417,"3"2600,"4"3204,"Y"99,""
This example confirms a Print-As-You-Go FedEx SmartPost shipment transaction:
0,"020"1,"Print As You Go - confirm"11,"COMPANY"12,"FXRS"13,"123 Main Street"14,"Suite 200"
15,"Memphis"16,"TN"17,"38116"18,
"8005551212"25,"Bound Printed Matter"50,"US"75,"lbs"116,"2"
117,"US"187,"188"498,"124765"537,"\\127.0.0.1\ZP5"541,"NNNNNNNNY"
542,"AA8811"2416,"3"2417,"3" 2600,"4"3204,"Y"99,""
7-100
FedEx Ship Manager® Server Developer Guide
v 10.6.1
CHAPTER 8: CODING TRANSACTIONS FOR FEDEX
INTERNATIONAL SHIPPING
FedEx Ship Manager® Server (FSMS) includes transaction fields that enable you to implement FedEx services as an integrated shipping
solution for your international business.
This chapter provides an overview of the integrated international service offerings for FedEx Ship Manager Server. It explains what you
need to prepare an international shipment, the types of documents required for your shipment to clear customs, and where to find
information in this guide to help you code transactions for shipping internationally with FedEx in the following sections:
• FedEx International Shipping Services
• FedEx Global Trade Manager Online
• Processing an International Shipment
• International Shipping Documents
FedEx International Shipping Services
FedEx provides the shipping solutions, resources and support you want for moving your products to their international destinations. One of
the first steps in coding transactions for international shipping is determining which FedEx service your company plans to use. Table 8-1 lists
the FedEx international services supported by FSMS and where you can find information about coding transactions in this guide.
Table 8-1: FedEx International Shipping Services At-A-Glance
Your Shipping Need
Our Service
Also See...
Intra-Europe, next day
FedEx Europe First®
2 business days to Europe
FedEx International First®
In 1, 2 or 3 business days worldwide
Chapter 9: Coding Transactions
for FedEx Express International
Services
FedEx International Priority®
Within 5 business days worldwide
FedEx International Economy®
Choose your own broker
FedEx International Broker Select®
FedEx Express International Package Services
FedEx International Ground® Package Services
Economical ground delivery to Canada
FedEx International Ground®
Drop-ship option for U.S.-to-Canada shipments
FedEx International Ground® Distribution
(Contract-only service*)
Chapter 10: Coding Transactions
for FedEx International Ground
Services
This service also known as FedEx® International
DirectDistribution (IDD) Surface Solutions U.S. to
Canada.
Bulk ground shipments
FedEx Ground Multiweight® — U.S. Export only
(Contract-only service*)
Choose your own broker
FedEx International Broker Select
FedEx Express International Freight Services
In 1, 2 or 3 business days worldwide
FedEx International Priority® Freight (IPF)
Within 5 business days worldwide
FedEx International Economy® Freight (IEF)
v 10.6.1
FedEx Ship Manager® Server Developer Guide
Chapter 9: Coding Transactions
for FedEx Express International
Services
8-1
Chapter 8: Coding Transactions for FedEx International Shipping
For more information about how to configure FedEx Ship Manager Server to enable Electronic Trade Documents, please reference the
Installation and Configuration Guide. *Contact your FedEx account executive for information about FSMS contract-only Services.
For information about coding transactions for FedEx® International DirectDistribution Surface Solutions, see Chapter 11: Coding
Transactions for FedEx International DirectDistribution Surface Solutions.
For information about coding transactions for FedEx International Priority DirectDistribution®, FedEx International Economy
DirectDistribution℠ and FedEx International Priority DirectDistribution® Freight, see Chapter 12: Coding Transactions for FedEx
International Priority DirectDistribution.
FedEx Special Options for International Service
FedEx offers a number of special service options for international shipments. They include:
• Special handling for certain commodities and/or packaging
• Signature, proof of delivery and shipment alert notifications
• Special delivery options such as Saturday service, future ship date and holding a package for pickup
• Collect on Delivery and special electronic payment service
• Customs broker selection options
• Special handling for dangerous goods and hazardous materials
• Multi-weight pricing for contracted accounts
• Electronic trade documents upload prior to shipment - FedEx® Electronic Trade Documents functionality simplifies international shipping
by allowing the customer to submit international trade documentation electronically prior to completing the shipment. Documents do not
have to be attached to the shipment. This optimizes the customs clearance process by allowing documents to be reviewed for clearance
prior to the shipment’s arrival.
Note: For more information about how to configure FedEx Ship Manager Server to enable Electronic Trade Documents, please reference
the Installation and Configuration Guide. For more information on how process Electronic Trade Documents transactions, please reference
Chapter 9: Coding Transactions for FedEx Express International Services and Chapter 10: Coding Transactions for FedEx International
Ground Services.
Note: In general, be sure to research the international regulations for specific commodities you plan to ship. Depending on the Harmonized
Tariff System (HTS) classification for your commodity, your shipment may require special handling and other special services. See
fedex.com for more information about commodity classification.
Table 8-2 lists the special service options available for FedEx Express International and FedEx International Ground® services when you
implement FSMS as a solution.
Table 8-2: FedEx International Shipping Services Special Options
FedEx International Special Options
FedEx Express
FedEx Ground
Dry Ice
Yes
No
Alcohol
No
No
FedEx® Delivery Signature Options
Yes
Yes
Hold at FedEx Location
Yes
No
Saturday Service
Yes
No
Future Day
Yes
Yes
Collect on Delivery
No
Yes
Dangerous Goods
Yes
(Not applicable)
Hazardous Materials
(Not applicable)
Yes
FedEx International Broker Select
Yes
Yes
8-2
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 8: Coding Transactions for FedEx International Shipping
Table 8-2: FedEx International Shipping Services Special Options (Continued)
FedEx International Special Options
FedEx Express
FedEx Ground
FedEx Express MPS Pricing
Yes
(Not applicable)
FedEx Ground Multi-Weight Pricing
(Not applicable)
Yes
FedEx ShipAlert®
Yes
No
FedEx® Electronic Trade Document Pre-Shipment Upload
Yes
Yes
For more information about special services, see Chapter 5: Coding Transactions for FedEx Express U.S. Service and Chapter 6: Coding
Transactions for FedEx Ground U.S. Services in this guide.
Features of Electronic Trade Documents
• Create and upload customs documents, as files or images created on your own system in your preferred software format, such as DOC
(MS Word), XLS (MS Excel), TXT (plain text), RTF (Rich Text), JPG, GIF, BMP, PNG, TIF and PDF (this does not include Microsoft Word
2007 DOCX or Microsoft Excel XLSX).
• Process trade documents to and from countries that allow shipping electronic trade documents. For a list of current countries, go to this
site: images.fedex.com/international/pdf/FedExElectronicTradeDocuments_Coverage_Final.pdf.
• Add a company letterhead and signature image to the Commercial Invoice (CI), Proforma Invoice (PI), or Certificate of Origin (COO) to
facilitate customs clearance without printing paper copies.
• Gain additional time to resolve any difficulties with trade documents before the shipment arrives.
FedEx® Electronic Trade Documents (ETD) service allows customers to submit their trade documents electronically, thus alleviating the
need to manually print and attach them to the shipment. This streamlines the process for clearing customs. This feature is not available for
dangerous goods or dry ice.
Electronic Trade Documents support is provided for:
• FedEx International Ground® (IG)
–Brokerage Inclusive (BI)
–Broker Select Option (BSO)
• FedEx International Priority® (IP)
• FedEx International Economy® (IE)
• FedEx International First® (IF)
• FedEx International Priority® Freight (IPF)
• FedEx International Economy® Freight (IEF)
–Third Party Consignee (TPC) options
FedEx International DirectDistribution Surface Solutions
FedEx® International DirectDistribution Surface Solutions is a cross-border service provided by FSMS that enables a shipper to consolidate
shipments to the U.S. from Canada or Mexico and is available for shipping packages/commodities to the U.S. only. After your shipment
enters the U.S., the shipment may be managed by FedEx U.S. services, including FedEx Express®, FedEx Ground and FedEx Home
Delivery.
Table 8-3 lists the FedEx U.S. services available to a FedEx International DirectDistribution Surface Solutions shipment after it enters the
U.S.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
8-3
Chapter 8: Coding Transactions for FedEx International Shipping
Table 8-3: FedEx International DirectDistribution Surface Solutions - FedEx Express and
FedEx Ground U.S. Services
Your Shipping Need
Our Service
Also See...
First thing the next-business-day morning
FedEx First Overnight®
Next-business-day morning
FedEx Priority Overnight®
Chapter 5: Coding Transactions
for FedEx Express U.S. Service
Next-business-day afternoon.
FedEx Standard Overnight®
2 business days
FedEx 2Day®
3 business days
FedEx Express Saver®
In 1, 2 or 3 business days within the U.S.
FedEx 1Day® Freight, FedEx 2Day® Freight,
FedEx 3Day® Freight
FedEx Express Services
FedEx Ground Services
Economical ground delivery to businesses
FedEx Ground®
Economical ground delivery to residences
FedEx Home Delivery®
Chapter 6: Coding Transactions
for FedEx Ground U.S. Services
For more information about FSMS and FedEx® International DirectDistribution Surface Solutions service, see Chapter 11: Coding
Transactions for FedEx International DirectDistribution Surface Solutions.
FedEx International DirectDistribution Services
FedEx offers direct-distribution services for shippers who want to consolidate their international shipments for customs clearance at a single
entry and then, within the destination country, break the shipment down into smaller components to distribute to individual recipients.
The FedEx® International DirectDistribution service is specific to Canadian shipments and allows qualified U.S. shippers to consolidate
FedEx Ground shipments for distribution within Canada. The shipment clears Canadian customs as a single shipment and is broken down
into smaller shipments once inside Canada.
Table 8-4 lists the FedEx international direct-distribution services that you can implement with FSMS. For those services which are contractonly, contact your FedEx account executive to learn how to get approved for these services.
Table 8-4: FedEx International Direct-Distribution Services At-A-Glance
Your Shipping Need
Our Service
Also See...
FedEx Express International DirectDistribution Services
Consolidate FedEx Express® shipments to clear
FedEx International Priority DirectDistribution®
customs at a single entry, then deliver to individual (Contract-only Service*)
recipients in the destination country
Chapter 12: Coding Transactions
for FedEx International Priority
DirectDistribution
Clear shipments through customs at a single entry, FedEx International Economy DirectDistribution℠
with delivery to individual recipients in the
Service (Contract-only Service*)
destination country
FedEx International DirectDistribution Surface Solutions
Consolidate economical ground delivery shipments FedEx® International DirectDistribution Surface
to clear customs at a single entry point and then
Solutions (Contract-only Service*)
distribute to individual recipients in Canada
8-4
FedEx Ship Manager® Server Developer Guide
Chapter 10: Coding Transactions
for FedEx International Ground
Services
v 10.6.1
Chapter 8: Coding Transactions for FedEx International Shipping
Table 8-4: FedEx International Direct-Distribution Services At-A-Glance (Continued)
Your Shipping Need
Our Service
Also See...
FedEx Express International DirectDistribution Freight Service
Consolidate shipments from a single origin location FedEx International Priority DirectDistribution®
to multiple recipients in one destination country
Freight
using one FedEx® International Air Waybill
Chapter 12: Coding Transactions
for FedEx International Priority
DirectDistribution
FedEx Global Trade Manager Online
The FedEx Global Trade Manager is an online resource for FedEx international shippers on fedex.com/gtm. When you use the FedEx
Global Trade Manager, you can:
• Find the required documents for your international shipment.
• Estimate the duties and taxes that will be levied against your international shipment.
• Get origin and destination country information you need for your shipment, including statistics on demographics and business
information.
• Get shipping advisories that include important regulatory information specific to your shipment.
• Identify individuals, companies and other parties that have been denied international business transactions.
The FedEx Global Trade Manager can save you time by identifying which of the many different types of customs and international trade
documents are required for your shipment. The online tool asks you to identify the origin and destination of your shipment and the
Harmonized Tariff System (HTS) code for the product you are shipping. Based on this information plus the type of transaction your shipment
represents, the tool shows you a list of required, optional and recommended documents that are appropriate for your shipment.
FedEx International Resource Center
• In addition to these tools, the site provides links to the FedEx International Resource Center located at fedex.com/us/international/irc
where you can:
• Research your shipment and country-specific shipping regulations
• Understand how to prepare and complete an international shipments
• Select a FedEx international shipping service
• Find the FedEx international documents required for your specific shipment
• Access links to external international resources, such as NAFTA Customs.
FedEx international shipping resources are updated constantly to provide you with the latest in international alerts and regulatory changes.
Be sure to revisit the site on a regular basis for these updates.
FedEx provides the International Shipping Reference Guide to assist you with international shipments. You may download this guide from
the International Resource Center at fedex.com/us/international/irc.
Processing an International Shipment
The steps for preparing and completing an international shipment require that you:
• Research your shipment
• Pack and process the shipment
• Prepare labels
v 10.6.1
FedEx Ship Manager® Server Developer Guide
8-5
Chapter 8: Coding Transactions for FedEx International Shipping
• Print international documents
• Confirm the shipment
• Schedule FedEx pickup
You may use the Global Trade Manager at fedex.com/gtm to assist you with the tasks in this list.
Research Your Shipment
International trade and shipping regulations vary from country to country. When you research your shipment, you decrease the risks of
unwanted surprises, potential shipping delays and customs clearance issues. FedEx recommends that you follow these steps to reduce the
risk of delays and ensure timely delivery of your FedEx shipments:
1. Profile Origin and Destination Countries
Understanding the shipping and regulatory laws of the destination country to which you want to ship is a first step in the international
shipping process. To help you find information about the country you are shipping to, FedEx provides country profiles that give you
country-specific overviews and statistics relevant to international shipping. You can access these profiles from the FedEx Global Trade
Manager site. You can also access them from the FedEx International Resource Center on fedex.com/us/international/irc.
Country profiles include a list of items prohibited for import or export. They also include a list of general import and export restrictions,
special import provisions, standards and regulatory contact information. If there are special restrictions or prohibitions which are
specific to a country, these items are listed also.
The International Resource Center also has additional links to currency conversion documents, and for China and India, there are links
to the China Reference Guide and India Reference Guide provided by FedEx to assist you in your shipping to these countries.
If you are interested in understanding the import clearance process that FedEx uses to clear your shipments through customs, read the
General Import Clearance Process section in your destination country’s profile.
2. Check for Regulatory Updates
FedEx provides a list of important regulatory updates for U.S. exporters and importers. You can find this information on fedex.com/us/
international/irc in the FedEx International Shipping Resources section of the International Resource Center.
3. Check for Denied Parties
FedEx helps you to identify individuals, companies and other parties that have been denied the ability to transact international
business. This information is available to registered fedex.com users. Register for FedEx Global Trade located at fedex.com/gtm to
use this tool.
4. Research Duties and Taxes
FedEx can help you estimate the duties and taxes related to your international shipment. This information is available to registered
fedex.com users. Register for FedEx Global Trade located at fedex.com/gtm to use this tool.
5. Choose a FedEx International Service
Factors such as transit time, shipping weight and size, commodity type and value, shipping and handling fees and regulatory
restrictions will influence how you determine which FedEx international service is a fit for your need. Your FedEx account executive can
discuss service options with you and register you for Contract-Only services for international shipping.
6. Research Rates and Transit Times
The transit time for your international shipment is influenced by the
–distance from shipping origin to recipient address
–weight of the shipment
8-6
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 8: Coding Transactions for FedEx International Shipping
–FedEx shipping service you selected and
–restrictions that may apply for the final destination country.
Various regulatory clearances in addition to custom clearance may be required for certain commodities, thereby, extending the transit
time. Visit fedex.com to get an estimate on rates and transit times for your shipment.
Pack and Process the Shipment
If you research the requirements of your destination country — related to commodity, packaging, restrictions and prohibitions — before you
process your shipment, you will be able to assemble and pack your shipment with the assurance that it will meet the appropriate customs
regulations at point of entry.
FedEx Ship Manager Server gives you several transaction methods for processing your international multiple-piece shipments. These are
described in this guide in Chapter 2: About FedEx Ship Manager Server Transactions.
Open Ship Transactions
You may use the Open Ship transaction method for all FedEx international shipping services. Open Ship allows you to create and enter
information for your international shipment as it is received, rather than entering all of the shipping information only when the shipment is
ready to be processed. The shipment remains “open” accepting each item as you enter it and closing only when you confirm over a seven
day period.
The Open Ship method is described in Chapter 4: FedEx Ship Manager Server Open Ship Transactions.
Preparing a FedEx Express International Shipment
Use the following checklist to help you prepare a FedEx Express international shipment with completed documentation, labels and forms.
Note: If you have already prepared your shipment and want to know which documents are required for your specific shipment, then log on to
the FedEx Global Trade Manager at fedex.com/gtm, check the Find International Documents checkbox and click Go.
Table 8-5 lists the documents, labels and forms that may be required for a FedEx Express international shipment.
Table 8-5: Guidelines for FedEx Express International Shipment Preparation
Completed Document
Description
Commercial Invoice for FedEx Express
This document is completed by the seller/shipper/exporter and describes the goods being
transported and the parties involved in the shipping. It is the primary document used by
Customs. The document should include a detailed breakdown of all items in the shipment
and a proper description of all goods (see Table 8-8). Some countries require that an
original invoice be created on the shipper’s letterhead. The invoice should always be
signed and dated by the exporter with a statement certifying that the details provided are
true and correct representations of the contents covered in the Commercial Invoice for
FedEx Express. For shipments to Canada, provide one signed original and four copies.
Pro Forma Invoice
This document may be used for customs clearance purposes when permits need to be
acquired in advance or when the original commercial invoice is lost. See “Pro Forma
Invoice” on page 8-15.
NAFTA Certificate of Origin
This is required to obtain duty-free status for goods that qualify under the NAFTA Rules
of Origin, if applicable. See “NAFTA Certificate of Origin” on page 8-16.
Certificate of Origin
This may be required for goods that originate outside the NAFTA areas.
Shipping Label
The shipping label allows the movement of a shipment from the country of export to the
destination country using FedEx Express Services. It contains all required information
needed, such as shipper and consignee information, description of contents, and value,
that facilitates the movement of the shipment and the creation of a manifest for Customs
at origin and destination. See “Prepare the Label” on page 8-9.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
8-7
Chapter 8: Coding Transactions for FedEx International Shipping
Table 8-5: Guidelines for FedEx Express International Shipment Preparation (Continued)
Completed Document
Description
FedEx International Express Shipping Label
The label helps identify packages for special handling and international clearance.
Destination Control Statement
This statement is required for most U.S. exports and verifies that the goods in the
shipment are being exported from the United States in accordance with the Export
Administration Regulations. See “Destination Control Statement” on page 8-15.
General Agency Agreement
(for Canadian shipments)
This agreement document gives shippers the ability to grant authority to customs brokers
to act on their behalf on an ongoing basis in regard to their import shipments into Canada.
See “General Agency Agreement (GAA)” on page 8-16.
Electronic Export Information (EEI)
This electronic document is required by the U.S. Department of Census to obtain
statistical data. It was formerly known as the Shipper’s Export Declaration (SED) which
can no longer be filed (as of September 2008). See “Electronic Export Information” on
page 8-16.
Preparing a FedEx International Ground Shipment
Use the following checklist to help you prepare a FedEx International Ground shipment with completed documentation, labels and forms.
Proper completion ensures your FedEx International Ground packages and shipments are prepared properly.
If you have already prepared your shipment and want to know which documents are required for your specific shipment, then log on to the
FedEx Global Trade Manager on fedex.com/gtm, check the Find International Documents checkbox and click Go.
Table 8-6: Guidelines for FedEx International Ground Shipment Preparation
Completed Document
Description
Commercial Invoice for FedEx Ground
This document is provided by the seller/shipper/exporter and is the primary document
used by Customs for international ground shipments (to both Canada and Puerto Rico)
which require a commercial invoice. It describes the goods being transported and the
parties involved in the shipping. The invoice should clearly indicate the shipper name and
address; broker name and address; recipient name, address and phone number; and a
detailed description of the goods. See Table 8-8.
For FedEx International Broker Select® shipments to Canada, you must include contact
information for the broker designated to clear the shipment. For multiple-piece shipments
to a single recipient, only one complete set of commercial invoices is required (one
original and four copies for shipments to Canada).
This form is used for export shipments from the U.S. to Puerto Rico and
Canada (complete top section for PR and CA shipments; complete bottom section for
shipments to CA only).
Pro Forma Invoice
This document may be used for customs clearance purposes when permits need to be
acquired in advance or when the original commercial invoice is lost. See “List of
Information to Include on Commercial Invoice Pro Forma Invoice” in this guide.
FedEx International Ground bar code label
Use FSMS to create a combination bar code and address label (see Chapter 3). Or, use
a preprinted FedEx International Ground bar code label plus an address label you create
yourself.
8-8
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 8: Coding Transactions for FedEx International Shipping
Table 8-6: Guidelines for FedEx International Ground Shipment Preparation (Continued)
Completed Document
Description
Blue FedEx International Ground Shipment label This label helps identify packages for special handling and helps keep the packages of a
multiple-piece shipment (to a single recipient) together for international clearance. This
decreases the chance of a split shipment being held at customs or returned to the shipper.
For a multiple-piece shipment, fill in the boxes on the blue FedEx International Ground
Shipment label to number the packages that are part of that shipment, for example,
package 1 of 3, package 2 of 3 and package 3 of 3.
FedEx Ground Customs Document envelope
This is the plastic pouch which holds your set of commercial invoices and is affixed to the
package or, in the case of a multiple-piece shipment, to the lead package.
FedEx Ground Manifest or the
FedEx Ground Pickup Record
If you process your shipments electronically, print your daily FedEx Ground Manifest. If
you use preprinted bar code labels, complete a page from your FedEx Ground Pickup
Record. Give the manifest or pickup record to your FedEx Ground driver along with your
shipments.
NAFTA Certificate of Origin
This is required to obtain duty-free status for goods that qualify under the NAFTA Rules
of Origin, if applicable. See “NAFTA Certificate of Origin” in this guide.
Certificate of Origin
This may be required for goods that originate outside the NAFTA areas.
Destination Control Statement
This statement is required for most U.S. exports and verifies that the goods in the
shipment are being exported from the United States in accordance with the Export
Administration Regulations. See “Destination Control Statement” on page 8-15.
Electronic Export Information (EEI)
This electronic document is required by the U.S. Department of Census to obtain
statistical data. It was formerly known as the Shipper’s Export Declaration (SED) which
can no longer be filed (as of September 2008). See ““Electronic Export Information” on
page 8-16.
General Agency Agreement
This agreement document gives shippers the ability to grant authority to customs brokers
to act on their behalf on an ongoing basis in regard to their import shipments into Canada.
See “General Agency Agreement (GAA)” on page 8-16.
Request for Business Number
The Business Number is the number assigned by the Canadian Customs Revenue
Agency (CCRA) to identify importers and exporters in regard to all transactions made by
them or on their behalf. See the Global Trade Manager on fedex.com for information
about registration.
See fedex.com or call 1.800.GoFedEx 1.800.463.3339 for information about ordering preprinted FedEx International Bar Code labels, blue
FedEx International Ground Shipment labels, FedEx Ground Customs Document envelopes and FedEx Ground Pickup Records.
Prepare the Label
Proper preparation of the FedEx label for your shipment is a critical part of the shipment preparation process. All FedEx labels must adhere
to FedEx label specifications and all non-FedEx custom labels must be approved by FedEx prior to use. The blue shipping label for a FedEx
International Ground shipment is a critical form for moving a ground shipment through Customs (see “FedEx Ground Shipping Label “).
For general information about creating and printing labels, see Chapter 3: FedEx Ship Manager Server Label and Form Transactions.
Print and/or Upload International Documents
Create FSMS transactions that generate, print and/or upload any international document that you require for your shipment. For a list of
international documents that are supported by FSMS, see Table C-5: Report Codes in the FedEx Ship Manager® Server Transaction Coding
Reference Guide. The Report Code table lists the code values you can enter in Field 1373 (Report Code) in a 020 Global Ship Request
transaction to identify the document or report you want to generate and print.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
8-9
Chapter 8: Coding Transactions for FedEx International Shipping
For more information about how to configure FedEx Ship Manager Server to enable Electronic Trade Documents, please reference the
Installation and Configuration Guide.
For more information on how process Electronic Trade Documents transactions, please reference Chapter 9: Coding Transactions for
FedEx Express International Services and Chapter 10: Coding Transactions for FedEx International Ground Services.
See “International Shipping Documents” in this guide for information about commonly required documents for international shipping.
For information about how to generate and print documents and reports, see Chapter 13: Generating FedEx Shipping Forms and Reports.
The FSMS Report Viewer Utility is another option for reviewing and printing reports. It provides the option to view shipment data after Endof-Day Close and print Close Report documents for your shipments. For information about the Report Viewer Utility, see Chapter 14: FedEx
Ship Manager Server Utilities.
You can also use the FedEx Document Preparation Center on fedex.com to create and save the international documents you use most
often. If you want to use FedEx commercial invoice forms, the FedEx Documentation Preparation Center provides commercial invoice forms
that you can print with your letterhead. The FedEx Global Trade Manager also can assist you in finding international documents you need to
ship. For more information, log on to the FedEx Global Trade Manager at fedex.com/gtm.
Confirm and Ship
Use a single 020 Global Ship Request transaction to ship internationally or use the Open Ship method to accept each package as it is
entered, then close only when you confirm over a seven day period.
If you use the Open Ship method to ship, then your international shipment cannot ship until you CONFIRM the shipment. This is the final
step in the process and is performed using the Open Ship CONFIRM shipment function (see Chapter 4: FedEx Ship Manager Server Open
Ship Transactions).
When your shipment is ready to ship, be sure to print/reprint labels and complete the paperwork for your international shipment, FedEx can
pick up and route your shipment to its final destination. It is important that your international documents be accurate and complete to get
your shipment delivered within the transit times you require. This requires that as the Shipper, you prepare your shipment and the
documents that accompany it properly and be ready to hand off the shipment to FedEx on schedule.
International Shipping Documents
When you complete international shipping documents properly, you assist customs agents in verifying that your shipment complies with all
government regulations. These documents are critical to getting your shipment to its final destination.
For more information about how to configure FedEx Ship Manager Server to enable Electronic Trade Documents, please reference the
Installation and Configuration Guide.
For more information on how process Electronic Trade Documents transactions, please reference Chapter 9: Coding Transactions for
FedEx Express International Services and Chapter 10: Coding Transactions for FedEx International Ground Services.
FedEx Ship Manager Server supports the generation and printing of international documents. Information about how to code transactions
for international shipments is provided in these chapters: Chapter 9: Coding Transactions for FedEx Express International Services, Chapter
10: Coding Transactions for FedEx International Ground Services, and Chapter 11: Coding Transactions for FedEx International
DirectDistribution Surface Solutions.
Basic Information on Shipment Documents
When filing international shipping documents, make sure the following basic information about your shipment is included in the document:
–Shipper’s FedEx account number
–Shipper’s name, address, phone number and tax identification number (EIN/SSN).
–Recipient’s name, address with postal code (for postal-aware countries), phone number and tax identification number.
Be sure to include the postal code for your destination address. FedEx relies on these codes to route your shipments to countries that have
established postal code systems, such as India and China. Packages without postal codes may be delayed.
8-10
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 8: Coding Transactions for FedEx International Shipping
Fields for Basic Shipping Information
FedEx Ship Manager Server basic shipping fields are described in the “020/120 Global Ship Request/Reply Transactions” section of the
FedEx Ship Manager® Server Transaction Coding Reference Guide. Table 8-7 lists fields for the Shipper and Recipient information listed
above.
Table 8-7: Basic Fields for International Shipping Documents
Basic Shipping Information
Use Field
Field Name
Shipper Information (default is configured in FedEx Ship Manager Server Configuration Utility)
FedEx account number
498
Meter Number
Name
4
32
Sender Company
Sender Contact Name
Address
5
6
7
8
9
Sender Address Line 1
Sender Address Line 2
Sender City
Sender State
Sender Postal Code
Phone number
183
Sender Phone Number
Tax identification number
1139
Sender IRS\EIN Number
Fax number
1103
Sender Fax Number
Name
11
12
Recipient Company
Recipient Contact Name
Address
13
14
15
16
Recipient Address Line 1
Recipient Address Line 2
Recipient City
Recipient State
Postal code
17
Recipient Postal Code
Country
50
Recipient Country
Weight of shipment
1670
Package Weight/Shipment Weight
Type of packaging
1273
Packaging Type
Selected FedEx service
1274
Service Type
Recipient information
Shipment
Note: In most instances, the Shipper information will be the same information configured for your FedEx meter/account. In such cases, you
do not need to include Shipper information fields in a transaction. The 020 transaction will use the information configured for your FedEx
account. See the FedEx Ship Manager® Server Installation and Configuration Guide for FSMS configuration details.
Providing Detailed Descriptions of Goods
When the description of the contents in your international shipment are precise and well-written, the risks of customs delays decrease. Here
are a few guidelines for providing detailed descriptions of your goods.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
8-11
Chapter 8: Coding Transactions for FedEx International Shipping
Document or Commodity
Begin by determining if what you are shipping is a document or a commodity. Different countries classify documents differently, and
therefore, you should understand how the specific country to which you are shipping defines them.
In general, a document is a commodity that has no commercial value. It is typically characterized by typed, written or printed matter on paper
or another material, and does not require a commercial invoice. If the commodity has commercial value or is part of a commercial business
transaction, it may be considered a “non-document”. All commodity shipments require a commercial invoice.
To research the classification for your commodity, use the FedEx Global Trade Manager online at fedex.com/gtm. You’ll find countryspecific information to determine whether your commodity is considered to be a document or non-document for your destination. If you
determine that you need to create a commercial invoice, see “Commercial Invoice” on page 8-13.
Commodity Description
A common reason for customs delays is an inaccurate or vague shipment description. A commodity description should answer the following
questions:
• What is it?
• How many are there?
• What is it made from?
• What is the intended use?
Commodity descriptions for dangerous goods or hazardous materials have very stringent regulations and prohibitions. If you believe you
may be shipping a commodity that falls into one of these classifications, be sure to thoroughly research the shipping restrictions for your
commodity classification.
Commodity Classifications
All commodities imported and/or exported must be properly classified under the Harmonized Tariff System (HTS) codes to meet U.S. and
foreign governments' customs requirements. Use the Harmonized Tariff System (HTS) to determine the code for your commodity. The HTS
assigns six-digit codes for general categories. Countries that use the HTS are allowed to define commodities at a more detailed level than
six digits, but all definitions must correspond to the six-digit HTS system. The U.S. defines commodities using 10-digit HTS codes. For links
to the U.S. agencies which administer export and import HTS codes, visit the FedEx International Resource Center on fedex.com.
Commodity Export License
An export license is a specific grant of authority from the government to a particular exporter to export a specific product. Export licenses are
granted on a case-by-case basis for either a single transaction or for a specified period of time. The exporter must apply for the export
license. This number will be one alpha plus six numeric characters. Every license is issued with an expiration date. Commodities requiring a
Department of State license may only ship on FedEx Express using FedEx International Controlled Export (FICE) service. If you need a
further explanation about an export license, contact the FedEx Regulatory Consulting Group at 1.800.851.3336.
Customs Clearance Documents
Governments require export and import documentation for a number of different purposes, including national security, administration of
export and import laws, control of products and protection of domestic markets, compiling of statistics, health and disease control, and
protection of endangered species.
For this reason, the import and export regulations for each country vary and require different amounts of paperwork. Understanding the
types of documents and information you are required to complete can help you develop FSMS transactions that generate documents with
accurate and precise data for your shipment.
The following international documents are explained in this section.
• Commercial Invoice
• Pro Forma Invoice
• Destination Control Statement
8-12
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 8: Coding Transactions for FedEx International Shipping
• FedEx International Air Waybill
• FedEx Ground Shipping Label
• NAFTA Certificate of Origin
• General Agency Agreement (GAA)
• Electronic Export Information
Commercial Invoice
The Commercial Invoice is the official transaction record between an exporter and an importer. In most cases, it is the primary document
that Customs officials use. The document is provided by the Seller, Shipper or Exporter of the goods being transported. and all parties
involved in the shipping. The document should contain a detailed breakdown of the contents of the shipment, including answers to what it is,
what it is made from and how it is intended to be used.
The invoice should always be dated and, for FedEx Express International, signed by the exporter with a statement certifying that the details
provided are true and correct representations of the contents. The commercial invoice for FedEx International Ground does not required a
signature.
This statement is known as the Shipper’s Declaration and reads:
“I declare all the information contained in this invoice to be true and correct.”
If you are not sure whether you need to create a commercial invoice for your shipment, call 1.800.GoFedEx 1.800.463.3339 and say
“international services.” You can also use the Global Trade Manager to determine if your specific shipment requires a commercial invoice
(see “FedEx Global Trade Manager Online” on page 8-5). FedEx provides commercial invoice forms on fedex.com that you can copy onto
paper stock with your letterhead.
FedEx Express International
A Commercial Invoice for FedEx Express typically is required when you ship non-document commodities using FedEx Express service. You
must submit one signed original and two copies for Customs. Your own corporate invoice is the preferred format if it contains the specific
information listed in Table 8-8.
Create a commercial invoice (Field 1373 Report Code) using the FSMS transaction interface or use the FSMS Report Utility (Chapter 14:
FedEx Ship Manager Server Utilities). FedEx also has a commercial invoice form that you can use to print with your letterhead. Another
option is to print the FedEx Express commercial invoice provided online at the FedEx Document Preparation Center on fedex.com. For
express shipments from the U.S. to Canada, use either the Commercial Invoice or a Canada Customs Invoice.
FedEx International Ground
A Commercial Invoice for FedEx Ground is required for all shipments to Canada. You must provide one original and four copies with your
shipment for customs clearance. For FedEx International Broker Select shipments to Canada, you must include contact information for the
broker designated to clear the shipment. Table 8-8 lists the information that is required for your international shipment on the Commercial
Invoice document
.
Table 8-8: List of Information to Include on Commercial Invoice
Commercial Invoice Information
FedEx Express
FedEx Ground
Seller/Shipper Information - name, full address, country and tax identification number
Yes
Yes
Recipient/Consignee information - name, full address, country and postal code if destination is a
postal-aware country
Yes
Yes
Buyer information (if other than consignee)
Yes
Yes
Invoice Date and Number
Yes
Yes
Customer/Purchase Order Number
Yes
Yes
v 10.6.1
FedEx Ship Manager® Server Developer Guide
8-13
Chapter 8: Coding Transactions for FedEx International Shipping
Table 8-8: List of Information to Include on Commercial Invoice (Continued)
Commercial Invoice Information
FedEx Express
FedEx Ground
Export/Import Broker Information for FedEx International Ground Shipments to Canada Only
No
Yes
Contact Name
Yes
Telephone
Yes
Fax Number
Yes
Importer-of-Record (IOR) information
Yes
NRI designation
Yes
Tracking Information
Yes
Yes
FedEx International Air Waybill number
Yes
No
FedEx Ground Tracking Number
(List individual tracking ID for every package in the shipment)
No
Yes
Shipment Information
Yes
Yes
Date of Invoice/ Date of Export
Yes
Yes
Export Carrier
Yes
Yes
Export references (optional)
Optional
Optional
Country of Export
Yes
Yes
Port of Lading
Yes
Yes
Final Destination/Country of Ultimate Destination
Yes
Yes
Detailed Description of Commodity (for each commodity in shipment)
Yes
Yes
Commodity Description
Yes
Yes
Commodity Classification (including grade, construction of product, and Harmonized Tariff System Yes
(HTS) classification, as appropriate)
Yes
Technical, Generic or Scientific Name of Commodity
Yes
Yes
Country of Manufacture
Yes
Yes
Type of Packaging
Yes
Yes
Marks, Numbers and Symbols
(under which product is sold)
Yes
Yes
Quantity
Yes
Yes
Unit of Measure
Yes
Yes
Total Number of Packages
Yes
Yes
Total Gross Weight
No
Yes
Weight Units (LBS/KG)
Yes
Yes
Invoiced Costs and Amounts
Yes
Yes
Sale Price or Fair Market Value (of each item) / Unit Price
Yes
Yes
Currency of Sale
Yes
Yes
Declared Value / Amount
Yes
Yes
Terms and Conditions of Sale
Yes
Yes
Fees, Surcharges, Discounts, Duties/Taxes and other Costs
Yes
Yes
Payer of Duties and Taxes
No
Yes
Total Invoice Amount
Yes
Yes
8-14
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 8: Coding Transactions for FedEx International Shipping
Pro Forma Invoice
The Seller, Shipper or Exporter provides the Pro Forma Invoice when:
1.
It is required prior to the shipment of goods to inform perspective buyer(s) of the type and quantities of goods to be sent, their value and
such specifications as weight, size, and so forth. This information enables importers to arrange for import permits or use the invoice for
other customs clearance purposes.
2.
The original commercial invoice is lost. Customs has final discretion to use it for clearance purposes and may or may not deem its
usage acceptable. For this reason, a Pro Forma Invoice should never be used in lieu of a commercial invoice.
Destination Control Statement
The Destination Control Statement is required on your invoice, air waybill and any export control document that accompanies your shipment
to the final end-user.
The Destination Control Statement is required for most U.S. exports and should read:
“These commodities, technology or software were exported from the United States in accordance with the Export Administration
Regulations. Diversion contrary to United States law is prohibited.”
Destination control statement for U.S. exports controlled by the U.S. Department of State should read:
“These commodities are authorized by the U.S. government for export only to [country of ultimate destination] for use by [end user].
They may not be transferred, trans-shipped on a noncontinuous voyage, or otherwise be disposed of in any other country, either in their
original form or after being incorporated into other end-items, without the prior written approval of the U.S. Department of State.”
You are not required to submit a Destination Control Statement if the Export Commodity Classification Number (ECCN) of your commodity is
EAR99 or your shipment is eligible for and exported under License Exception BAG or GFT. For more information, log on to the FedEx Global
Trade Manager on fedex.com/gtm for assistance.
FedEx International Air Waybill
An air waybill or bill of lading is the transportation document that allows the movement of a shipment using FedEx Express Services from the
country of export to the country of import. It contains shipper and consignee information, a brief description of the contents, value of the
commodity for Customs, and country of manufacture for all contents — essential data for moving the shipment and creating manifest
documents at origin and destination for Customs.
For international shipments, use these guidelines for preparing your air waybill.
• For FedEx Express shipments up to 150 LBS — prepare the FedEx International Air Waybill.
• For FedEx Express package and freight shipments, including dangerous goods and special services — prepare the FedEx Expanded
Service International Air Waybill.
• For FedEx International Express Freight® (IXF) — prepare the FedEx IATA (023) Air Waybill.
FedEx Ground Shipping Label
The shipping label for FedEx Ground International is the transportation document used to allow the movement of a ground shipment from
origin to destination using FedEx Ground Services. The label form contains human-readable information required to move the shipment
from the country of export to the country of import. Like the air waybill for FedEx Express, it contains shipper and consignee information, a
brief description of the contents, value of the commodity for Customs, and country of manufacture for all contents. This information is
important for moving the shipment and generating manifests at shipping origin and destination for Customs.
For international shipments, use these guidelines for preparing your shipping label:
• For FedEx International Ground package shipments — prepare the bar code label.
• For FedEx International Ground shipments to Canada — prepare the blue FedEx Ground shipping label.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
8-15
Chapter 8: Coding Transactions for FedEx International Shipping
NAFTA Certificate of Origin
A NAFTA Certificate of Origin should be provided for goods that qualify for reduced or duty free entry as a product of one of the three North
America Free Trade Agreement (NAFTA) participants: Canada, Mexico and the United States. The certificate is completed by the exporter
or manufacturer of the goods and is provided with the commercial invoice.
The NAFTA Certificate of Origin is provided with the commercial invoice for any shipment consigned to Canada, the United States or Mexico
that is $1600 CAD or more in value and qualifies under the terms of the NAFTA. The form is available in English, French and Spanish.
For information about how to code a NAFTA Certificate of Origin transaction, see Chapter 10: Coding Transactions for FedEx International
Ground Services.
General Agency Agreement (GAA)
FedEx U.S. shippers are required to fill out a Canada Customs General Agency Agreement (GAA) form when shipping across the U.S.Canada border. An Agency Agreement provides the legal authority granted by importers to a customs broker that allows them to release
and/or account for shipments with the Canadian Customs Revenue Agency (CCRA) on behalf of the importer’s company.
If a Canadian Resident Importer would like FedEx Express to act as their customs broker in Canada on an ongoing basis, then a Limited
Agency Agreement must be completed prior to shipping into Canada. This form applies to FedEx Express shipments only.
The FedEx Trade Networks® Continuous General Agency Agreement form similarly grants FedEx Ground shippers the ability to appoint
FedEx Trade Networks (FTN) to act as their broker on an ongoing basis for import shipments into Canada. After you complete the form and
it is accepted by FedEx Trade Networks, it is in effect until either party cancels the agreement or the agreement itself expires.
For information about how to generate a GAA document, see Chapter 10: Coding Transactions for FedEx International Ground Services.
Electronic Export Information
The Electronic Export Information (EEI) is the equivalent electronic version of the Shipper’s Export Declaration (SED), Department of
Commerce (Census Bureau) form 7525-V, which can no longer be submitted to the U.S. government (as of September 30, 2008). The EEI
provides export statistics and control by reporting all pertinent export data of an international shipment transaction.
The EEI is required by the U.S. Department of Census to obtain statistical data and also by the Bureau of Industry and Security (BIS) to
assist in enforcing export controls. The EEI is required when the total value of goods classified under any Schedule B number exceeds
$2500 USD or the commodities listed require an export license. This information is mandatory and must be submitted electronically by the
exporter or agent through the Automated Export System (AES) for commodities listed on the Commerce Control List (CCL).
The EEI is not required for shipments from the U.S. to Canada unless the merchandise is subject to International Traffic in Arms Regulations
(ITAR) or requires an export license or permit. An EEI is not required for shipment to other U.S. possessions (American Samoa, Baker
Island, Commonwealth or the Northern Mariana Islands, Guam, Howland Islands, Jarvis Island, Johnston Atoll, Kingmen Reef, Midway
Islands, Navassa Island, Palmyra Atoll, and Wake Island) or from the U.S. Virgin Islands to the U.S. or Puerto Rico.
Also see Chapter 12: Coding Transactions for FedEx International Priority DirectDistribution and Chapter 13: Generating FedEx Shipping
Forms and Reports. For additional information, visit the FedEx Global Manager on fedex.com.
Where to File
Because of U.S. Government changes in the EEI process, you must file your EEI information with AESDirect at www.aesdirect.gov. This
Government-supported website facilitates your filing requirements and provides you with the appropriate shipper identification for your
packages. FedEx will apply this information with your shipment but will no longer file this information for you.
For more information regarding EEI filing, the following locations are available:
• FedEx Global Trade Manager: fedex.com/us/international
• AESDirect: www.aesdirect.gov
• U.S. Census Bureau: www.census.gov/foreign-trade/
8-16
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 8: Coding Transactions for FedEx International Shipping
When To File
You must file an EEI for all shipments from the U.S., Puerto Rico or the U.S. Virgin Islands to foreign destinations. It is also required for all
shipments between the U.S. and Puerto Rico, and from the U.S. or Puerto Rico to the U.S. Virgin Islands if any of the following apply:
• Shipment of merchandise under the same Schedule B commodity number is valued at more than $2,500 USD and is sent from the same
exporter to the same recipient on the same day. (Note: Shipments to Canada from the U.S. are exempt from this requirement.)
• The shipment contains merchandise, regardless of value, that requires an export license or permit.
• The merchandise is subject to International Traffic in Arms Regulations (ITAR), regardless of value.
• The shipment, regardless of value, is being sent to Cuba, Iran, North Korea, Sudan or Syria.
• The shipment contains rough diamonds, regardless of value (HTS 7102.10, 7102.21 and 7102.31).
An EEI is not required for shipments to other U.S. territories (American Samoa, Commonwealth of the Northern Mariana Islands, Guam,
Howland Islands and Wake Island) or from the U.S. Virgin Islands to the U.S. or Puerto Rico.
U.S. To Canada
The EEI is not required for shipments from the U.S. to Canada except when one of the following apply:
• Merchandise is subject to International Traffic in Arms Regulations (ITAR)
• Shipment requires an export license or permit
• Shipped commodity is rough diamonds.
For more information about Electronic Export Information, visit the FedEx Global Trade Manager site at fedex.com/gtm.
Information for the EEI
Identify the following information before you complete the Electronic Export Information.
• USPPI EIN and ID — if the shipper is a corporation, you’ll need the EIN Employer Identification Number (Tax ID) of the U.S. principal
party in interest.
–If the shipper is an individual, you’ll need the person’s social security number.
• Information about the relationship of parties to the transaction is required. This information indicates whether the sender and recipient are
subsidiaries or divisions of the same company or are unrelated.
• Transportation Reference No. — requires that you supply your FedEx International Air Waybill number.
• Ultimate Consignee — identify the end user of the merchandise you are shipping only if the ultimate consignee is different from the
consignee you entered on your FedEx International Air Waybill.
• Country of Ultimate Destination — indicate the country where the shipment will ultimately be used.
• D/F/ or M (Domestic or Foreign in AES) — indicate if the commodity was made or manufactured in the U.S. (D=domestic) or made or
manufactured outside the U.S. (F=foreign).
• Schedule B Number (Commodity Classification Number in AES) — enter the correct Schedule B or Harmonized Code number and units.
To find this information, go to the FedEx Global Trade Manager site on fedex.com/gtm or call the U.S. Census Bureau at
1.800.549.0595.
• Value — enter the selling price or cost of the merchandise if it has not been sold.
• License No./License Exception Symbol/Authorization (License Number/Citation in AES) — enter your export license number or license
exception symbol. To determine if you need to supply this information, call the U.S. Department of Commerce at 1.202.482.4811 or
1.714.660.0144 in Newport Beach, California or visit the Bureau of Industry and Security website at www.bis.doc.gov/.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
8-17
Chapter 8: Coding Transactions for FedEx International Shipping
AES Filing Status Field 1349
FedEx Ship Manager Server requires indication of EEI filing status for each qualifying shipment. To indicate the EEI status, use Field 1349
(AES Filing Status) with a value of S.
FTR, XTN or ITN Field 1358
U.S. Customs further requires that either a Foreign Trade Regulations (FTR) exemption or Internal Transaction Number (ITN) number be
provided for each EEI qualifying shipment.
Use Field 1358 (FTR, XTN, or ITN Entry) to provide the FTR exemption number, the Pre-Departure ITN, the Post Departure Citation, or the
AES Downtime Citation.
Note: FedEx Ship Manager Server version 8.0 forward is staged to process the changes pending U.S. government’s implementation of final
rules for EEI. Until then, edits have been relaxed to accept XTN, ITN, and FTR entries in Field 1358 as previously performed in FSMS
version 7.6.
B13A - Canadian Export Shipments
The B13A is an export declaration form filed with Canada Customs by the Canadian exporter for all outbound shipments consigned to
countries other than the United States, Puerto Rico, or the U.S. Virgin Islands. For shipments of documents and commodities, it is required
when a shipment exceeds a Customs value of $1999.99 CAD. The B13A is also required for shipments of controlled commodities, as
defined by Revenue Canada Customs and related agencies, regardless of the value.
B13A Filing Options Field 1651
FedEx Ship Manager Server provides Field 1651 (B13A Filing Options) for Canada export shipments. The values for this field are:
• No B13A Required
• Manual B13A Required
• B13A Filing Electronically
• B13A Summary Reporting
Export Data Statement Field 1652
If you declare that a B13A is not required for your shipment, then the associated “B13A Exemption Number” must also be provided in Field
1652 (Export Statement Data). Visit fedex.ca/customs to view the list of exemptions and identify the B13A exemption number that applies
to your shipment, then enter the B13A exemption number in Field 1652. Failure to provide the B13A exemption number may result in a delay
of your shipment due to Customs examination.
Note: For Product/Commodity Shipments the B13A Filing Option and associated fields must be provided for shipments of any value that are
consigned to countries other than the United States, Puerto Rico, or the U.S. Virgin Islands.
For Document Shipments the B13A Filing Option and associated fields must be provided for shipments consigned to countries other than
the United States, Puerto Rico, or the U.S. Virgin Islands and if the value exceeds:
$1999.99CAD
$999.99USD
$0 for any other currency type
The B13A information appears in B13A handling codes on the shipping label.
FedEx Trade Networks and Brokerage Services
FedEx Trade Networks helps simply international shipping by providing brokerage services to customers as an end-to-end service that
covers customs brokerage, global cargo distribution, and trade facilitation.
For information about FedEx Trade Networks, contact your FedEx account executive or call FedEx Trade Networks Customer Service Team
at 1.800.249.2953.
8-18
FedEx Ship Manager® Server Developer Guide
v 10.6.1
CHAPTER 9: CODING TRANSACTIONS FOR FEDEX
EXPRESS INTERNATIONAL SERVICES
FedEx Express® international package services ship to and from any country supported by FedEx International services.
This chapter describes how to ship FedEx Express International packages with FedEx Ship Manager® Server (FSMS) in the following
sections:
• About FedEx Express International Shipping Transactions
• Transaction Rules and Restrictions for FedEx Express International
• FedEx Express International Service Options
• Coding Transactions for FedEx Express International
• Transaction Samples
When shipping internationally, be sure to research your shipment in advance to avoid costly delays at Customs. For a checklist of
international documents that may need to accompany your FedEx Express International shipment, see Chapter 8: Coding Transactions for
FedEx International Shipping.
About FedEx Express International Shipping Transactions
Before you begin to develop FedEx Express International shipping transactions, be sure to familiarize yourself with transaction coding
basics in Chapter 2: About FedEx Ship Manager Server Transactions.
Use the 020/120 Global Ship Request/Reply transactions to create FedEx Express International shipment transactions. The basic FedEx
Express international shipping transaction uses the same fields required for Express domestic shipping (see Chapter 5: Coding
Transactions for FedEx Express U.S. Service). For information about FedEx Express international shipping transactions, see “Coding
Transactions for FedEx Express International” on page 9-6.
FedEx Ship Manager Server transactions must be formatted according to rules specified in the transaction code reference tables described
in the FedEx Ship Manager® Server Transaction Coding Reference Guide. Be sure to reference this guide if you need additional information
about a transaction field.
See the FedEx Ship Manager® Server Services and Shipping Guide for information about FedEx Express International service features and
details before you begin to code.
Transaction Rules and Restrictions for FedEx Express
International
Shipping internationally requires time up front to research your shipment and the Customs regulations for the destination country to which
you are shipping. For general information about international shipping and transactions, read Chapter 8: Coding Transactions for FedEx
International Shipping.
The following rules apply to FedEx Express International shipping with FSMS:
• You must specify the basic commodity information required for your shipment so that FedEx can expedite Customs clearance of your
packages.
• You can create your own Customs clearance documents or have FSMS generate basic documents.
–FedEx Ship Manager Server can provide a Commercial Invoice (CI), Pro Forma Invoice, and a Certificate of Origin (COO) from your
shipping data.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
9-1
Chapter 9: Coding Transactions for FedEx Express International Services
–If you need more clearance documentation, then use FedEx Global Trade Manager (GTM), which provides up-to-date country-specific
import information, a document assistance wizard, and a duties and taxes estimator tool. FedEx Global Trade Manager is available at
the following URL: fedex.com/gtm/international.
• You must provide extra thermal shipping labels with your Customs documentation (depending on your destination country) to facilitate
Customs clearance. FedEx Ship Manager Server automatically generates the correct number of labels for your destination country.
• You can use FedEx packaging for Express international shipments: FedEx® Pak, FedEx Box, FedEx® Tube, FedEx® Envelope, FedEx®
10kg Box, and FedEx® 25kg Box. You may also use your own packaging for FedEx Express international shipments.
• You can ship both standard (under 150 pounds) and freight (over 150 pounds) shipments to international destinations.
See Chapter 8 for a list of international documents and labels that may be required for your shipment and how to create them using
transaction fields.
Electronic Export Information
You must submit the Electronic Export Information (EEI) on shipments if the origin/destination is:
• From the U.S., Puerto Rico, or the U.S. Virgin Islands to international destinations
• Between the U.S. and Puerto Rico
• From the U.S. or Puerto Rico to the U.S. Virgin Islands
AND if any of the following conditions apply:
• Ship merchandise under the same Schedule B commodity number that is valued at more than $2,500 USD and is sent from the same
exporter to the same recipient on the same day. Shipments to Canada are exempt from this requirement.
• The shipment contains merchandise, regardless of the values, that requires an export license and/or permit.
• The merchandise is subject to the International Traffic and Arms Regulations (ITAR).
• The shipment contains items other than personal, interoffice, or business correspondence, regardless of value, being sent to Cuba, Iran,
Iraq, Libya, North Korea, Serbia (excluding Kosovo), Sudan, or Syria.
For general information about filing the EEI and other international documents which may be required for your shipment, see Chapter 8:
Coding Transactions for FedEx International Shipping. You’ll find URLs for additional assistance in this chapter also.
FedEx Express International Service Options
FedEx Express International provides the following international service options for packages weighing up to 150 LBS.
• FedEx International First®
• First International Priority®
• First International Economy
• FedEx Europe First
FedEx Express International Freight handles packages and handling units over 150 LBS. It provides these service options:
• FedEx International Priority® Freight
• FedEx International Economy® Freight
For information about shipping using the above services, see the FedEx Ship Manager® Server Services and Shipping Guide available as
part of the FSMS documentation set.
9-2
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 9: Coding Transactions for FedEx Express International Services
FedEx Delivery Signature Options
FedEx® Delivery signature options are required for FedEx Express International shipments to the U.S. and Canada only. Choose from the
options in Table 9-1.
Table 9-1: Delivery Signature Options for U.S. and Canada
Delivery Signature Option
U.S.
Canada
Direct Signature Requested
Yes
Yes
Indirect Signature Required
Yes
Service not offered
Adult Signature Required
Yes
Service not offered
No Signature Required
Yes
Yes
For more information regarding signature requirements to the U.S. and Canada, see Chapter 11: Coding Transactions for FedEx
International DirectDistribution Surface Solutions.
Saturday Pickup and Delivery
Saturday shipping, delivery, and pickup options are available for international shipments. The following service details apply to FedEx
Express international shipments involving Saturday service:
• U.S. export shipments to international destinations are available for pickup on Saturdays.
• For FedEx International Priority, Saturday delivery is available for shipments from the U.S. to Canada only.
• For countries that consider Saturday a regular business day (Far East and Middle East), Saturday delivery does not have to be indicated
in the shipping transaction.
• Saturday pickup and delivery is not offered for FedEx International First, FedEx International Economy®, or FedEx Express Freight
International services, except in countries where Saturday is a regular business day.
When coding for Saturday service, use Field 24 (Ship Date), Field 1266 (Saturday Delivery Flag), and Field 1267 (Saturday Pickup Flag) as
described in Table 9-2.
Table 9-2: Fields for FedEx Saturday Service
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
N
I
Description
Ship Date
24
v 10.6.1
Max=8
FDXE
US
INTL
Field Level: Shipment
REQUIRED*
Date of shipment.
*Required for Future Day shipping. Format: CCYYMMDD
Default: Current meter date.
For example, July 1, 2005 is coded as: 20050701
For FedEx Express, the ship date can be set in advance up to the number
of days allowed by the date range in the URSA file; includes IPD, IDF, IED
and Returns services.
FedEx Ship Manager® Server Developer Guide
9-3
Chapter 9: Coding Transactions for FedEx Express International Services
Table 9-2: Fields for FedEx Saturday Service (Continued)
Transaction: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Saturday Delivery Flag
1266
Max=1
A
I
FDXE
US
CA
INTL
IPD
SPOC
REQUIRED*
Specify Y if the shipment is to be delivered on a Saturday.
*Required for Saturday Delivery service.
Valid values:
Y — Saturday Delivery
N — No Saturday Delivery
Available for IPD, SPOC, IDF and IDF SPOC.
Note: Saturday Delivery FedEx Express Freight shipments are only
allowed within the U.S. or U.S. inbound.
For this shipment, use any method.
I
FDXE
All nonFreight:
US
CA
INTL
IPD
SPOC
REQUIRED*
Specify Y if the shipment is to be picked up on a Saturday.
*Required for Saturday Pickup service.
Valid values:
Y — Saturday Pickup
N — No Saturday Pickup
Available for IPD and IPD SPOC. Not valid for FedEx Express Freight.
For this shipment, use any method.
Saturday Pickup Flag
1267
Max=1
A
Inside Pickup and Delivery
You may request inside pickup and delivery in the 020 Global Ship Request transaction if you are shipping FedEx International Priority
Freight. This option is not available for international economy freight services. See Chapter 5: Coding Transactions for FedEx Express U.S.
Service for information about inside pickup and delivery transaction flags and service charges.
Dangerous Goods
FedEx Ship Manager Server supports the shipping of dangerous goods (DG) for FedEx Express under International Air Transport
Association (IATA) and 49CFR Air regulations. Any FedEx Express dangerous goods shipment can be shipped under IATA regulations, but
only shipments that are shipped within the U.S., to and from Puerto Rico, or to and from U.S. territories can be shipped under Other
Regulated Materials — Domestic (ORM-D) regulations. See Chapter 5: Coding Transactions for FedEx Express U.S. Service for information
about shipping dangerous goods in the U.S.
Note: To assist in FedEx Express dangerous goods shipping, FSMS provides an IATA table in spreadsheet format in the FedEx_Tables
file in the FedEx directory.
FedEx Ship Manager Server supports the printing of the 1421C Shipper’s Declaration of Dangerous Goods which is required for all
dangerous goods shipments. The 1421C may be printed as a multi-ply form using a dot matrix printer or you may print this form on a laser
printer using special 1421C paper (plain paper with a border of red crosshatches). The 1421C is produced at the time of shipment
confirmation.
Note: Contact your FedEx Account Executive for more information about obtaining 1421C laser forms.
9-4
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 9: Coding Transactions for FedEx Express International Services
FedEx Ship Manager Server does not prevent dangerous goods (DG) shipments to countries which do not accept them. The Dangerous
Goods checkbox appears in the Additional Options dialog box whether or not the destination country accepts dangerous goods
shipments.
Contact FedEx International Customer Service at 1-800-247-4747 to verify that the destination country will accept the shipment.
Future Day
You are allowed to create a Future Day Express international shipment for up to ten (10) calendar days from the current day. Future Day
shipments are uploaded to FedEx when you close your shipping day and retained in a file until the package future ship date equals the
current day. You must submit a 023 Global Delete Request transaction to remove Future Day shipments from this file or you may be billed
for these packages.
Cut Flowers
Depending on the customs rules for cut flowers, FSMS allows you to indicate that an international express shipment contains cut flowers
using Field 572 (Cut Flowers Flag). An additional surcharge is applied for cut flowers shipments. This flag is needed to ensure that FSMS
returns the correct shipping costs. See “Fields for Returning Shipping Costs” on page 9-22.
The following shipping rules apply:
• Destination and origin country allowances can be verified using Global Trade Manager (GTM) on fedex.com.
• An additional surcharge is applied for cut flowers shipments.
• Saturday Delivery is not allowed.
• Cut flowers shipping is not allowed for FedEx® International DirectDistribution Surface Solutions or FedEx International Priority
DirectDistribution® (IPD) shipments.
• Ground services are not allowed.
• Broker Select Option (BSO) is not allowed.
• FedEx packaging options are not allowed for cut flowers shipments.
Table 9-3 describes the required field for a cut flower shipment.
Table 9-3: FedEx Express Cut Flowers Flag
Transactions: 020 Global Ship Request
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Cut Flowers Flag
572
Max=1
Description
Transactions: 020 Global Ship Request
A
I
FDXE
INTL
Field Level: Shipment
Optional
Indicates whether cut flowers in shipment.
Applicable only to origins in LAC (Latin America), APAC (Asia and Asia
Pacific), and EMEA (Eastern Middle East, Europe and Africa).
Valid values are:
Y — Cut flowers in shipment
N — No cut flowers (default)
Note: Field 572 does not return the Cut Flower surcharge fee.
See the FedEx Ship Manager® Server Services and Shipping Guide for
cut flower shipping rules.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
9-5
Chapter 9: Coding Transactions for FedEx Express International Services
Coding Transactions for FedEx Express International
The basic FedEx Express international shipping transaction uses the same fields required for Express domestic shipping (see Chapter 5:
Coding Transactions for FedEx Express U.S. Service).
Fields for FedEx Express International Shipping
Table 9-4 describes the additional fields required for FedEx Express International shipping.
Table 9-4: Additional Required Fields for FedEx Express International Shipments
Transaction: 020 Global Ship Request - Single Shot, Multiple-Piece Shipment, Open Ship
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
A
I
Description
Recipient Country
50
Max=3
FDXE
FDXG
INTL
Field Level: Shipment
REQUIRED*
Two-digit code indicating the country of the Recipient address.
*Required for FedEx International Priority DirectDistribution (IPD), FedEx
International Economy DirectDistribution (IED) and FedEx International
Priority DirectDistribution® Freight (IDF) shipments.
*Required for FedEx SmartPost®.
*Required for ADD Piece Open Ship function.
See Appendix C in the Transaction Coding Reference Guide for country
codes.
Customs Currency Type
68
9-6
Max=3
A
I
FDXE
INTL
Field Level: Shipment
REQUIRED*
Indicates the currency in which the Customs value is expressed.
*Required for FedEx Express international shipments only; for FedEx
Express U.S. domestic shipments the value defaults to USD and for CA
origins to CAD.
Note: The value for this field is applied to Field 119 (Total Commodity
Customs Value) and Field 1030 (Commodity Line Item Unit Value).
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 9: Coding Transactions for FedEx Express International Services
Table 9-4: Additional Required Fields for FedEx Express International Shipments (Continued)
Transaction: 020 Global Ship Request - Single Shot, Multiple-Piece Shipment, Open Ship
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
N
I
FDXE
INTL
Field Level: Shipment
REQUIRED*
Indicates the terms of the sale for the shipment.
Valid values are:
1 — FCA/FOB - Free carrier/free on board
2 — CIP/CIF - Carriage and insurance paid to/costs, insurance, and
freight
3 — CPT/C&F or CFR/CPT - Carriage paid to/costs & freight
4 — EXW - Ex Works
5 — DDU - Delivered duty unpaid
6 — DDP - Delivered duty paid
*Required if Field 113 is set to Y.
A
I
FDXE
All
Field Level: Shipment
REQUIRED* or Defaulted.
Indicates the unit of weight used for the shipment.
*Required if your shipment is calculated in kilograms (KGS).
Valid values are:
LBS — Weight in pounds (default for U.S. domestic and export)
KGS — Weight in kilograms (default for intra-Canada and all
international)
Note: For intra-U.S.(domestic) shipments, you may enter the weight in
LBS or KGS.
I
FDXE
FDXG
INTL
Field Level: Shipment
REQUIRED*
Description of commodity contents for the shipment. This can be used for
free-form entry of document description when Field 2396 (Document
Description) is not used.
*Required for commodity shipments or for document shipments when
Field 190 (Document Shipment Flag) is set to Y and Field 2396 is not
used.
*Required for General Agency Agreement (GAA) if import shipment.
Note: Only 31 characters of this field print on the labels, but 450
characters are available for customer input to be used on their own
reports, including the Commercial Invoice.
Note: If both Field 79 and Field 2396 are populated in the same
transaction, Field 2396 takes precedence. Field 79 takes precedence for
IPD/IDF/IED shipments.
Description
Terms of Sale
72
Max=3
Weight Units
75
Max=3
Description of Contents
79-#
v 10.6.1
Max=450 A
FedEx Ship Manager® Server Developer Guide
9-7
Chapter 9: Coding Transactions for FedEx Express International Services
Table 9-4: Additional Required Fields for FedEx Express International Shipments (Continued)
Transaction: 020 Global Ship Request - Single Shot, Multiple-Piece Shipment, Open Ship
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
Description
Country of Manufacture
80-#
Max=2
A
I
FDXE
FDXG
INTL
Field Level: Shipment
REQUIRED.
Country code where commodity contents were produced or
manufactured in their final form. If using a commercial invoice, this field
is used at the commodity level.
For multiple countries of manufacture, you may enter "XX" EXCEPT
when shipping documents, multiple commodities, filling requests for
customs documentation or using these FedEx services:
FedEx International Priority DirectDistribution
FedEx International Priority DirectDistribution Freight
FedEx International Economy DirectDistribution℠ Service
FedEx® International DirectDistribution Surface Solutions
See Appendix C in the Transaction Coding Reference for country codes.
Commodity Quantity
82-#
Max=7
N
I
FDXE
FDXG
INTL
Field Level: Shipment
REQUIRED.
Total number of pieces of a given commodity in the entire shipment. For
example, if you are shipping 6 pencils and 4 erasers, you code 82,"6"822,"4".
*Required if Field 113 (Commercial Invoice Print and Upload Flag) is set
to Y, and you are not using Field 78 (Commodity Customs Value) or Field
119 (Total Commodity Customs Value).
Default is 1.
If FedEx is filing the commercial invoice (CI), the values sent for this field
and Field 1030 (Commodity Line Item Unit Value) determine the Total
Customs Value for the shipment.
Total Customs Value = Sum of Field 82 x Field 1030. This derived value
can be overridden by passing a value in Field 119.
If Field 113 is set to Y, Field 2404 position 1 (Commercial Invoice) should
also be set to Y to generate a commercial invoice (default).
FDXE
All
Field Level: Shipment
REQUIRED or Defaulted.
Currency used to rate the shipment.
Default for U.S. domestic shipping: USD
Default for CA Domestic shipping: CAD
U.S. Export shipping requires USD or CAD to be entered.
Canadian Export shipping requires CAD or USD to be entered.
All other origins are non-rated.
Declared Value/Rate Currency Type
1090
9-8
Max=3
A
I
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 9: Coding Transactions for FedEx Express International Services
Table 9-4: Additional Required Fields for FedEx Express International Shipments (Continued)
Transaction: 020 Global Ship Request - Single Shot, Multiple-Piece Shipment, Open Ship
Field ID
Field
Length
Data
Type
Input/ FedEx Shipping
Output Services Valid For
N
I
FDXE
All
Field Level: Package
REQUIRED.
Available for Express (U.S. domestic and international):
01 — Customer packaging
02 — FedEx Pak
03 — FedEx Box
04 — FedEx Tube
06 — FedEx Envelope
N
I
FDXE
INTL
Field Level: Shipment
REQUIRED.
Service type provided by the shipper.
Valid service types are:
FedEx International Services (including U.S. export):
01 — International Priority
03 — International Economy
06 — International First
17 — FedEx International Economy DirectDistribution Service
18 — FedEx International Priority DirectDistribution
57 — FedEx Europe First (See the FedEx Service Guide for served
countries.)
70 — International Priority Freight
Description
Packaging Type
1273
Max=2
Service Type
1274
Max=2
82 — FedEx® International DirectDistribution Surface Solutions Service
for CA/MX
84 — FedEx® International Priority DirectDistribution Freight
86 — International Economy Freight
Note: Field length of 3 for FedEx Express Freight bill of lading.
Note: For FedEx SmartPost shipping, reference Field 2417 in Table 7-9
on page 7-49.
Third Party Consignee
Third Party Consignee (TPC) is a contract service that is offered to FedEx International Priority® shippers who do not want their recipients to
know the commercial value of the shipment.
This service enables deliveries of shipments to end recipients at destinations without a commercial invoice attached.
Third Party Consignee is only allowed for certain origin/destination countries. There is a surcharge associated with this service. Shippers
who have contracted for this service may use Field 3309 (TPC Flag) in a 020 Global Ship Request transaction.
Third Party Consignee service is available for:
• FedEx International Priority
• FedEx International Priority Freight
v 10.6.1
FedEx Ship Manager® Server Developer Guide
9-9
Chapter 9: Coding Transactions for FedEx Express International Services
Third Party Consignee Fields
Table 9-5 describes the Third Party Consignee fields.
Table 9-5: Third Party Consignee Fields
Transaction: 020 Global Ship Request/Reply - Single Shot, Single Piece, Open Ship MPS
Field ID
Field
Length
Data
Type
Input\ FedEx Shipping
Output Services Valid For
Description
Payor Account Number
20
Max=9
N
I
FDXE
IPD
IDF
Field Level: Shipment
REQUIRED*
Nine-digit FedEx account number of company or person to be billed for
the shipment.
*Required for IPD/IED/IDF when Field 23 (Pay Type) = 3.
Max=1
N
I
FDXE
IPD
IDF
Field Level: Shipment
REQUIRED.
Method of payment for transportation charges.
Valid values:
1 — Bill sender
3 — Bill Third Party
6 — Bill Associated Account (Applies to FedEx SmartPost Returns)
When 3 is used, Field 20 (Payor Account Number) is required.
Max=1
A
I
FDXE
INTL
IPD
IDF
Field Level: Shipment
REQUIRED*
Third-party consignee flag.
*Required when you ship from/to certain countries and you do not want
to attach the commercial invoice to the delivery.
Affects International Priority (IP) and International Priority Freight (IPF)
service only.
Payment types allowed are: Bill sender and Bill third party.
Valid values are:
Y — Third-party consignee
N — No third-party consignee (default)
Pay Type
23
TPC Flag
3309
See the FedEx Ship Manager® Server Developer Guide for more
information on Third Party Consignee service.
List Third Party Consignee Surcharge
4027
9-10
Min=1
N
Max=11.2
O
FDXE
IPD
IDF
Positive numbers only. Two implied decimal places.
(1-9999)
See Field 3309 for Third Party Consignee.
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 9: Coding Transactions for FedEx Express International Services
FedEx Electronic Trade Documents Fields
Upload customer generated shipping documents in a 049 Pre-Shipment Document Upload Request Transaction before shipping the
shipment using the 020 Global Ship Request Transaction.
Note: Please ensure that Electronic Trade Documents has been enabled prior to using the 049 transaction. This transaction will not upload
your documents unless you have enabled Electronic Trade Documents in your meter settings tab.
Note: More details about the 020 Global Ship Request Transaction can be found on page 9-16.
Note: The Pre-Shipment Document Upload for customer generated documents should be performed prior to shipping.
049 Pre-Shipment Document Upload Request Fields
Table 9-6 lists the fields allowed by the 049 Pre-Shipment Document Upload Request transaction.
Table 9-6: 049 Pre-Shipment Document Upload Request Fields
Field ID
Field
Length
Date
Type
Input/ FedEx Shipping
Output Services Valid For
Pre-Shipment Document Upload Request
Description
N
I/O
All
All
REQUIRED
Indicates the start of any transaction.
For example, 0,"049" or 0,"49" signifies the start of the 049 Pre-Shipment
Document Upload Request transaction.
A
I/O
FDXE
FDXG
All
REQUIRED*
Two-digit code indicating the country of the Recipient address.
N
I/O
FDXE
FDXG
All
REQUIRED* or Defaults to Master Meter if not passed in transaction.
FDXE
FDXG
All
Transaction Code
0
Max=3
Recipient Country
50
Max=2
Meter Number
498
Min=1
Max=9
Note: Meter number may be any length up to nine digits.
Open Ship Index
542
Max=9
A/N
I/O
REQUIRED*
Set to the unique number passed in the CREATE transaction. The value
is a unique number per Open Ship shipment per meter and represents
the Open Ship Index.
*Required for Open Ship.
Note: Field 542 is not required if you are simultaneously performing a
CREATE or ADD transaction.
Simultaneous Field 541 (required for Open Ship) transactions examples:
•
YYNNNNNNN, which performs a shipment level CREATE and
Route/Time-in-Transit transaction.
•
NYNYNNNNN, which performs a package level ADD and shipment
level Route/Time-in-Transit together in the same transaction.
v 10.6.1
FedEx Ship Manager® Server Developer Guide
9-11
Chapter 9: Coding Transactions for FedEx Express International Services
Table 9-6: 049 Pre-Shipment Document Upload Request Fields (Continued)
Field ID
Field
Length
Date
Type
Input/ FedEx Shipping
Output Services Valid For
Pre-Shipment Document Upload Request
Description
A
I/O
Optional
ETD Indicator used to override the ETD flag on the Meter Settings tab.
This Field ID takes precedence over the configuration when passed in a
transaction.
Valid values are:
Y — Yes
N — No
ETD Indicator
2805
Max=1
FDXE
FDXG
IP
IE
IF
IPF
IE
IGF
Note: If Field ID is not sent, blank, or invalid, then the value on the
configuration screen applies.
Document Reference ID
2817-#
Min=1
Max=40
AKE
I/O
FDXE
FDXG
IP
IE
IF
IPF
IEF
IG
REQUIRED*
Used by customers to indicate a unique ID for each given Electronic
Trade Document being uploaded in the transaction.
*FXRS auto-populates if not passed in the transaction.
Note: If you create your own Document Reference ID in 049/149 PreShipment Document Upload, it is simpler to link, but if you let FedEx
create the link, it will be 40 characters long.
I/O
FDXE
FDXG
IP
IE
IF
IPF
IEF
IG
REQUIRED - in 020/120 Global Ship and 049/149 Pre-Shipment Upload
Transactions, if Field 2819 is present in the 049 Request Transaction. If
Field 2818 is not found, then an error will be returned.
This field is required to determine what type of document(s) are being
electronically uploaded. It is used with the Field 2819 (ETD Document
Filename) for Customer Generated documents (Field 2821).
Valid values are:
1 — Commercial Invoice
2 — Certificate of Origin
3 — Proforma
4 — Other
For multiple documents being uploaded in this transaction, each
occurrence of Field 2819 must have a corresponding occurrence of
Field 2818 with the valid value set. For example: If the first occurrence
of 2819 (such as 2819-1) has the following filename,
C:\Folder\CommercialInvoice.txt,
then Field 2818 and its first occurrence (2818-1) should be set to
1 (Commercial Invoice) for the document type.
It is the customer’s responsibility to ensure that the uploaded document
matches the valid value set for this Field ID.
ETD Document Type
2818-#
9-12
Max=1
N
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 9: Coding Transactions for FedEx Express International Services
Table 9-6: 049 Pre-Shipment Document Upload Request Fields (Continued)
Field ID
Field
Length
Date
Type
Input/ FedEx Shipping
Output Services Valid For
Pre-Shipment Document Upload Request
Description
I/O
IP
IE
IF
IPF
IEF
IG
REQUIRED in 049/149 Pre-Shipment Upload
Optional in 020/120 Global Ship Transaction
This field contains the fully qualified filename of the document to be
uploaded, including the valid path where this document is located.
ETD Document Filename
2819-#
Min=1
AKE
Max=255
FDXE
FDXG
Note: The maximum length for an Electronic Trade Documents filename
is 30 characters.
ETD Wait for Confirmation
2820
Max=1
A
I
FDXE
FDXG
IP
IE
IF
IPF
IEF
IG
Optional
Flag to indicate if customer wants to wait for a confirmation from the backend system that a customs document was uploaded successfully.
This Field ID takes precedence over the configuration when passed in a
transaction if there is a conflict between the transaction and the
configuration settings.
Valid values:
Y — Wait for Confirmation (equates to “Required” in the configuration)
N — Do Not Wait for Confirmation (equates to “Not Required” in the
configuration)
I
FDXE
FDXG
IP
IE
IF
IPF
IEF
IG
REQUIRED*
Flag to indicate if customer wants to override the configuration setting
between Customer Generated documents. This Field ID takes
precedence over the configuration when passed in a transaction.
Valid values are:
C — Customer Generated
F — FedEx Generated
ETD Document Generation
2821-#
Max=1
A
Note: FedEx Generated not available with 049/149 Pre-Shipment
Document Upload.
Note: This field must be used in conjunction with Fields 2818 and 2819
for all 049/149 Pre-Shipment Document Upload transactions.
End of Record Indicator
99
v 10.6.1
Max=0
NULL
I/O
All
All
REQUIRED
Indicates the end of a transaction. The format is 99,"" (99 followed by a
comma and two quotation marks). All FedEx Ship Manager® Server
transactions must end with 99,"".
FedEx Ship Manager® Server Developer Guide
9-13
Chapter 9: Coding Transactions for FedEx Express International Services
149 Pre-Shipment Document Upload Reply Fields
Table 9-7 lists the fields returned by the 149 Pre-Shipment Document Upload Reply Transaction.
Table 9-7: 049 Pre-Shipment Document Upload Reply Fields
Field ID
Field
Length
Date
Type
Input/ FedEx Shipping
Output Services Valid For
Pre-Shipment Document Upload Request
Description
N
O
All
All
Indicates the start of a transaction.
For example, 0,"049" or 0,"49" signifies the start of the 049 Pre-Shipment
Document Upload Reply Transaction.
A
O
FDXE
FDXG
All
Two-digit code indicating the country of the Recipient address.
N
O
FDXE
FDXG
All
The meter number from the input request returned in the reply.
A/N
O
FDXE
FDXG
All
Set to the unique number passed in the CREATE transaction. The value
is a unique number per Open Ship shipment per meter and represents
the Open Ship Index.
*Required for Open Ship.
Field 542 is not required if you are simultaneously performing a CREATE
or ADD transaction.
Simultaneous transactions example:
YYNNNNNNN, which performs a shipment level CREATE and Route/
Time-in-Transit transaction.
NYNYNNNNN, which performs a package level ADD and shipment level
Route/Time-in-Transit together in the same transaction.
A
I/O
FDXE
FDXG
IP
IE
IF
IPF
IEF
IG
Indicator used to override the ETD flag on the Meter Settings tab. This
Field ID takes precedence over the configuration when passed in a
transaction.
Valid values are:
Y — Yes
N — Yes
IP
IE
IF
IPF
IEF
IG
The unique ID for each ETD document from the input request returned in
the reply. If the Document Reference ID was not passed in the request,
then FXRS will auto-populate this field in the reply.
Note: If you create your own Document Reference ID in 049/149 PreShipment Document Upload, it is simpler to link, but if you let FedEx
create the link, it will be 40 characters long.
Transaction Code
0
Max=3
Recipient Country
50
Max=2
Meter Number
498
Min=1
Max=9
Open Ship Index
542
Max=9
ETD Indicator
2805
Max=1
Note: If Field ID is not sent, blank, or invalid, then the value on the configuration screen applies.
Document Reference ID
2817-#
9-14
Min=1
Max=40
AKE
O
FDXE
FDXG
FedEx Ship Manager® Server Developer Guide
v 10.6.1
Chapter 9: Coding Transactions for FedEx Express International Services
Table 9-7: 049 Pre-Shipment Document Upload Reply Fields (Continued)
Field ID
Field
Length
Date
Type
Input/ FedEx Shipping
Output Services Valid For
Pre-Shipment Document Upload Request
Description
O
FDXE
FDXG
IP
IE
IF
IPF
IEF
IG
The type of Electronic Trade Document from the input request returned
in the reply.
This field is required to determine what type of document(s) are being
electronically uploaded. It is used with the Field 2819 (ETD Document
Filename) for Customer Generated documents (Field 2821).
O
FDXE
IP
The ETD Document Filename from the input request returned in the reply.
FDXG
IE
Note: The maximum length for an Electronic Trade Documents filename
is 30 characters.
ETD Document Type
2818-#
Max=1
N
ETD Document Filename
2819-#
Min=1
AKE
Max=255
IF
IPF
IEF
IG
ETD Document Status
2822-#
Max=2
N
O
FDXE
IP
FDXG
IE
IF
IPF
IEF
IG
Indicates the status of a document within an Electronic Trade Documents
shipment when returned in the Reply transaction for Shipping (120), PreShipment (149) or Shipment Query (124).
Valid values are:
06 — Invalid File Format
01 — Successfully Uploaded
07 — Invalid Document Type
02 — Upload Pending
08 — Invalid Filename
03 — Upload Unsuccessful
09 — System Error
04 — Virus Detected
10 — Duplicate File
05 — File too Large
End of Record Indicator
99
Max=0
NULL
O
All
All
Indicates the end of a transaction. The format is 99,"" (99 followed by a
comma and two quotation marks). All FedEx Ship Man