Creating a Label

Web Services supports a variety of label options, including thermal, plain paper, and customizable labels. With Web Services, you can use the Ship Service to produce a wide variety of labels. In this section, you will find instructions for generating the labels you need to support your shipping application.

FedEx offers 3 label formats to support shipping services:

Thermal Labels
Laser Labels
Custom Labels

Thermal Labels

Web Services allows you to print shipping labels for all shipping types (Express, Ground, International) using a variety of thermal label printers. The following thermal label sizes are supported by Web Services:

4” x 6”—without a configurable document tab (DocTab)
4” x 6”—includes a DocTab
4” x 8”—provides space to include a graphic or text file of your choice
4” x 9”—provides space for graphics or text as well as a DocTab

If you print shipping labels using a thermal printer, you may choose label stock that includes a DocTab, a removable sticky tab with additional shipping information. See Ground Domestic Label with DocTab for a sample. You can configure this shipping information from your shipping data or choose to print configurable data that is specific to your shipping needs. See Appendix T: Express Thermal Label Samples for Express thermal label examples.

Thermal Label Elements

Thermal shipping labels contain three basic elements:

Human-readable content—this part of the label contains the shipping information from the Web Services Ship Service.
Two dimensional (2D) bar-code—the dimensional alphanumeric bar-code stores data for both FedEx Express and FedEx Ground shipments using the American National Standards Institute (ANSI) MH10.8.3 standard. The 2D bar-code is created using the Portable Document Format (PDF) 417 symbology.
FedEx-specific bar-code—ASTRA (Advanced Sorting Tracking Routing Assistance) for FedEx Express shipments; bar-code “96” for FedEx Ground and FedEx Home Delivery shipments. FedEx Ground also allows for the use of the SSCC-18 “00” bar-code.

For examples see Appendix R: Ground Plain Paper Label Samples and Appendix S: Ground Thermal Label Samples.

Generating a Thermal Label

All labels required for a shipment are generated and returned in a single buffer. For example, if a label request is made on a C.O.D. shipment, the label server returns the shipping label and a copy of the C.O.D. Return label. The label server always returns the appropriate quantity of labels for each type of shipment, so the client does not need to make multiple label calls to FedEx.

The following Web Services elements are required to generate a thermal label:

Web Services Element

Description/Valid Values

LabelSpecification/LabelFormatType

Required to receive the correct label image in the Ship Reply service:

Valid values:

COMMON2D—The label format type to receive a label.
LABEL_DATA_ONLY—The value used to receive the bar-code data if you create a custom label.

LabelSpecification/ImageType

Required to format the thermal label for the printer you use; provides the type of data stream or bitmap to be returned.

Valid values:

DPL—Unimark
EPL2—Eltron
ZPLII—Zebra

Note: These printers are all compatible with the ASCII Eltron Programming Language (EPL2) page mode.

LabelSpecification/LabelStockType

Required only for thermal labels. Specifies whether label stock has DocTab on leading or trailing end of labels or has no DocTab.

Valid values:

STOCK_4X6
STOCK_4X6.75_LEADING_DOC_TAB
STOCK_4X6.75_TRAILING_DOC_TAB
STOCK_4X8
STOCK_4X9_LEADING_DOC_TAB
STOCK_4X9_TRAILING_DOC_TAB

Sending a Thermal Label to a Local Printer or Network Printer

If you use Web Services (SOAP request) or non-SOAP requests, the returned label buffer is Base64 encoded. Therefore, before you send the commands to the printer, you must Base64 decode the buffer. You can perform Base64 encoding and decoding using built-in functions of many XML parsers or Microsoft XML Core Services (MSXML). Once decoded, the thermal label buffer contains a list of printer commands to print the label for the type of printer you select in your Ship request. To print the thermal label, send that list of commands to the configured printer port for your thermal printer. Be sure to include the CR/LF characters as you send the commands to the printer.

Note: Labels may be reprinted by sending the original thermal label buffer to the printer. However, labels should be reprinted only if the original label is damaged or lost before the package is picked up, or as a copy for your records. Duplicate labels applied to packages will cause re-labeling and, in some cases, suspension of your shipping capabilities.

Supported Thermal Printers

The following thermal printers are recommended with FedEx Web Services:

Unimark
Eltron
o Orion (EPL2)
o Eclipse (EPL2)
Zebra
o LP2443 (EPL2)
o LP2844 (EPL2)
o LP2348 Plus (EPL2)
o Z4M Plus (ZPL or EPL)
o ZP500 (ZPL or EPL)

These printers are all compatible with the ASCII Eltron Programming Language (EPL2) page mode. If your printer supports this programming language it may work as well. Check your printer user’s guide for details. Thermal printers are supported both as a direct write to the printer connected to a system serial port, and as a native Windows installed printer for LPT, Serial, or USB connections.

Number of Thermal Labels Printed Per Service

Below is a table indicating the number of each type of label needed for a specific special service. All the necessary labels are generated by a call to the FedEx Common Label Server (CLS), and CLS returns a single buffer with the exception of the C.O.D. Return labels.

U.S. Domestic

Service Type

Thermal Labels (FedEx CLS will return the appropriate number of labels in the response)

FedEx Express U.S.

1 Shipping label

FedEx Express U.S. C.O.D.

1 Shipping label

1 C.O.D. (Collect On Delivery) Return label

FedEx Ground U.S./Home Delivery

1 Shipping label

FedEx Ground U.S. C.O.D.

1 Shipping label

2 C.O.D. Return labels

U.S. Export International

Service Type

Thermal Labels (FedEx CLS will return the appropriate number of labels in the response)

FedEx Express U.S. Export International

1 Shipping label

1 Consignee label

FedEx Express U.S. Export International Broker Select Option

1 Shipping label

2 Consignee labels

FedEx Ground U.S. Export International

1 Shipping label

FedEx Ground U.S. Export International C.O.D.

1 Shipping label

2 C.O.D. Return labels

Intra-Canada

Service Type

Thermal Labels (FedEx CLS will return the appropriate number of labels in the response)

FedEx Express intra-Canada

Non-DG (Dangerous Goods)/Dry ice shipment:

1 Shipping label

FedEx Ground intra-Canada

1 Shipping label

FedEx Ground intra-Canada C.O.D.

1 Shipping label

2 C.O.D. Return labels

Canada Export International

 

Thermal Labels (FedEx CLS will return the appropriate number of labels in the response)

FedEx Express Canada Export International

Non-DG/Dry ice shipment:

1 Shipping label

2 Consignee labels

FedEx Express Canada Export International Broker Select Option

Non-DG/Dry ice shipment:

1 Shipping label

2 Consignee labels

FedEx Ground Canada (CA) Export International

1 Shipping label

DocTab Configuration

The notation for specifying DocTab value sources begins as a strict subset of standard XPath notation, with a small set of DocTab-specific extensions (described below). A path is prefixed with a small set of “aliases” that identify the object to which the rest of the path applies. The following examples should give the overall “look and feel” of the notation:

Desired element

DocTab path (string)

Shipper’s company name

REQUEST/SHIPMENT/Shipper/Contact/CompanyName

Total number of packages

REQUEST/SHIPMENT/PackageCount

Current package’s sequence number

REQUEST/PACKAGE/SequenceNumber

Current package’s weight

REQUEST/PACKAGE/Weight/Value

Shipment total net charge

REPLY/SHIPMENT/RATE/ACTUAL/TotalNetCharge/Amount

Current package’s dim weight

REPLY/PACKAGE/RATE/ACTUAL/DimWeight/Value

Every “segment” (portion between “/” separators) in these samples is the actual name of an element from the WSDL, except for the starting segments, which specify where to begin navigating to the desired data. The client developer would know what names are available from the WSDL. The notation is case-sensitive and the client should use the same names as in the WSDL.

DocTab Coding Details

All data from the customer’s description of the shipment (RequestedShipment) and the data returned to the customer (CompletedShipmentDetail) is eligible for use in the DocTab. The complete structure of those objects is necessarily complex, due to the tremendous range of service features that may occur within a FedEx shipment. The first segments of a DocTab path come from a set of alias/shortcut values that allow the customer to indicate whether the requested value is to come from one of the following:

Client or transaction detail
Request or reply data
Shipment- or package-level data
Rate data, and if so, which rate type

The prefix (leading segments) of the path specifies the above choices in that order, as shown in the following tables:

Prefix (Non-Rate Data)

Remainder of path selects data from…

CLIENT/…

The effective copy of the ClientDetail

TRANSACTION/…

The effective copy of the TransactionDetail

REQUEST/SHIPMENT/…

The effective copy of the RequestedShipment

REQUEST/PACKAGE/…

The effective copy of the current RequestedPackage

REPLY/SHIPMENT/…

The CompletedShipmentDetail

REPLY/PACKAGE/…

The current CompletedPackageDetail

Prefix (Rate Data)

Remainder of the path selects data from…

REPLY/SHIPMENT/RATE/ACTUAL/…

Shipment-level rate data (totals for actual rate applied)

REPLY/SHIPMENT/RATE/PAYOR_ACCOUNT/…

Shipment-level rate data (totals for specific returned rate type)

REPLY/SHIPMENT/RATE/RATED_LIST/…

Shipment-level rate data (totals for specific returned rate type)

REPLY/PACKAGE/RATE/ACTUAL/…

Package-level rate data (details for actual rate applied)

REPLY/PACKAGE/RATE/PAYOR_ACCOUNT/…

Package-level rate data (details for specified returned rate type)

REPLY/PACKAGE/RATE/RATED_LIST/…

Package-level rate data (details for specific returned rate type)

The rate data is taken from the appropriate instance (based on the rate type specified by the fourth segment of the path) of ShipmentRateDetail (for shipment-level data) or PackageRateDetail (for package-level data).

DocTab Specification

The RequestedShipment contains a LabelSpecification that describes each zone on the DocTab portion of the label by a DocTabZoneSpecification, located as follows:

RequestedShipment

LabelSpecification (LabelSpecification)

CustomerSpecifiedLabelDetail (CustomerSpecifiedLabelDetail)

DocTabContent (DocTabContent)

DocTabContentType (DocTabContentType)

Zone001 (DocTabContentZone001)

DocTabZoneSpecifications[] (DocTabZoneSpecification)

ZoneNumber (positiveInteger)

Header (string)

DataReference (string)

LiteralValue (string)

Justification (DocTabZoneJustificationType:string)

After identifying the zone number, the specification can indicate:

An optional header;
Either a data reference (path to a request/reply element) or a literal value (actual data to be printed), and;
An optional justification.

If both a data reference and literal value are passed, literal value takes precedence over data reference.

The data reference specifies a path to the element desired, based on a specific starting point:

Client detail data (ClientDetail),
Transaction detail data (TransactionDetail),
Request data for the entire shipment (RequestedShipment),
Request data for the current package (RequestedPackage),
Reply data for the entire shipment (CompletedShipment), or
Reply data for the current package (CompletedPackage).

The path is made up of selectors, each of which specifies a step “into” the structure of the starting-point object. For single-valued (non-array) elements, the name of the element is the selector. All examples on the previous page used single-valued elements.

Array elements are qualified by a predicate that indicates which element of the array should be used, either by position or by content. Examples of this usage would be:

Shipper’s first street address line: REQUEST/SHIPMENT/Shipper/Address/StreetLines[1]

Third-party number of shipment uploaded to FedEx InSight system: REQUEST/SHIPMENT/ShipmentContentRecords[3]/PartNumber

Shipment fuel surcharge: REPLY/PACKAGE/RATE/PAYOR_ACCOUNT/Surcharges[SurchargeType="FUEL"]/Amount

There are few cases where array elements would be needed; the most likely scenario involves data (such as surcharges and taxes).

Example—ZoneNumber 1-8 specify data elements (using the XPath notation) and Zone 9 specifies a literal value.

<LabelSpecification>

<LabelFormatType>COMMON2D</LabelFormatType>

<ImageType>EPL2</ImageType>

<LabelStockType>STOCK_4X6.75_LEADING_DOC_TAB</LabelStockType>

<LabelPrintingOrientation>TOP_EDGE_OF_TEXT_FIRST</LabelPrintingOrientation>

<CustomerSpecifiedDetail>

<DocTabContent>

<DocTabContentType>ZONE001</DocTabContentType>

<Zone001>

<DocTabZoneSpecifications>

<ZoneNumber>1</ZoneNumber>

<Header>Street</Header>

<DataField>REQUEST/SHIPMENT/Shipper/Address/StreetLines[1]</DataField>

</DocTabZoneSpecifications>

<DocTabZoneSpecifications>

<ZoneNumber>2</ZoneNumber>

<Header>Meter</Header>

<DataField>CLIENT/MeterNumber</DataField>

</DocTabZoneSpecifications>

<DocTabZoneSpecifications>

<ZoneNumber>3</ZoneNumber>

<Header>TransId</Header>

<DataField>TRANSACTION/CustomerTransactionId</DataField>

</DocTabZoneSpecifications>

<DocTabZoneSpecifications>

<ZoneNumber>4</ZoneNumber>

<Header>TotalSur</Header>

<DataField>REPLY/SHIPMENT/RATE/PAYOR_ACCOUNT/TotalSurcharges/Amount </DataField>

</DocTabZoneSpecifications>

<DocTabZoneSpecifications>

<ZoneNumber>5</ZoneNumber>

<Header>TotalWt</Header>

<DataField>REQUEST/SHIPMENT/TotalWeight/Value</DataField>

</DocTabZoneSpecifications>

<DocTabZoneSpecifications>

<ZoneNumber>6</ZoneNumber>

<Header>Date</Header><DataField>REQUEST/SHIPMENT/ShipTimestamp </DataField>

</DocTabZoneSpecifications>

<DocTabZoneSpecifications>

<ZoneNumber>7</ZoneNumber>

<Header>Contact</Header>

<DataField>REQUEST/SHIPMENT/Recipient/Contact/PersonName</DataField>

</DocTabZoneSpecifications>

<DocTabZoneSpecifications>

<ZoneNumber>8</ZoneNumber>

<Header>Insured</Header>

<DataField>REQUEST/PACKAGE/InsuredValue/Amount</DataField>

</DocTabZoneSpecifications>

<DocTabZoneSpecifications>

<ZoneNumber>9</ZoneNumber>

<Header>Literal 1</Header>

<LiteralValue>mytext</LiteralValue>

</DocTabZoneSpecifications>

</Zone001>

</DocTabContent>

</CustomerSpecifiedDetail>

</LabelSpecification>

 

Path Syntax for DocTabHelper and VPath

 

 

Laser Labels

Web Services supports label printing with a laser printer. Labels that are printed with a laser printer are generated in PDF format and do not need to be scaled or resized. These labels are usually printed on 8.5”x11” paper and folded in half to fit in the standard FedEx label pouch. The following requirements apply to PDF labels:

Adobe Reader 6.0 or higher is required to process the label.
Printer driver configuration must have printer scaling set to none.
Using an HTML wrapper is not necessary for displaying a plain paper PDF label in a browser.
Acrobat recommends the following browsers for viewing PDF documents:
o Microsoft Internet Explorer 5.5 or higher
o Netscape 7.1 or 8.0
o Firefox 1.0 or higher
o Mozilla 1.7 or higher

The PDF label option eliminates the need to specify the image orientation parameter (width and height) or the screen resolution to display the label properly in the browser.

Laser Label Elements

Laser shipping labels contain three basic elements:

Human-readable content—This part of the label contains the shipping information from the Web Services Ship Service.
Two dimensional (2D) bar-code—The dimensional alphanumeric bar-code stores data for both FedEx Express and FedEx Ground shipments using American National Standards Institute (ANSI) MH10.8.3 standard. The 2D bar-code is created using the Portable Document Format (PDF) 417 format.
FedEx-specific bar-code—ASTRA (Advanced Sorting Tracking Routing Assistance) for FedEx Express shipments; bar-code “96” for FedEx Ground and FedEx Home Delivery shipments. FedEx Ground also allows for the use of the SSCC-18 “00” bar-code when applicable.

Generating a Laser Label

The following Web Services elements are required to generate a laser label:

Web Services Element

Description/Valid Values

LabelSpecification/ LabelFormatType

Required to receive the correct label image in the Ship Reply service:

Valid values:

COMMON2D—label format type to receive a label.
LABEL_DATA_ONLY—this value is used to receive the bar-code data if you create a custom label.

LabelSpecification/ ImageType

Required to indicate label formatting. Type of data stream or bitmap to be returned:

Valid values:

PDF—plain paper
PNG—plain paper

LabelSpecification/ LabelStockType

Required only for thermal labels. Specifies whether label stock has DocTab on leading or trailing end of labels or has no DocTab.

Valid values:

PAPER_4X6
PAPER_4X8
PAPER_4X9
PAPER_7X4.75
PAPER_8.5X11_BOTTOM_HALF_LABEL
PAPER_8.5X11_TOP_HALF_LABEL

Note: If you request a plain paper label, the data returned is an encoded label image, which must be decoded prior to displaying the label file.

Supported Laser Printers

Most laser printers are supported for this label type; however, labels will not be accepted if they are printed on an ink jet printer. If you are using a color laser printer, the color definition should be set to black, even if the printer only has a black cartridge installed. This setting is necessary to achieve the correct bar-code definition for scanning at the FedEx hubs.

Printing a Laser Label

FedEx returns one laser label per shipping request, with the exception of C.O.D. labels. If you need to print multiple labels (for example, international shipments need additional copies of shipping labels to accompany the customs clearance documentation), you must request additional copies.

To prepare your package for shipment, you must:

Use the Print button on your browser to print the page containing your label.
The shipping portion of the laser label prints on the top half of an 8.5”x11” page. If you use FedEx-approved label stock that accommodates the half page label as a peel and stick, affix this portion of the label to the package. The bottom portion of the label provides terms and conditions and a recap of your tracking number. This portion of the label should be kept for your records.

If you use plain paper instead of label stock, fold the page in half and place it in a waybill pouch. Attach the pouch to your package so that the bar-code portion of the label can be read and scanned.

Note: Labels may be reprinted by sending the original PDF to the printer. However, labels should be reprinted only if the original label is damaged or lost before the package is picked up or as a copy for your records. Duplicate labels applied to packages will cause re-labeling and, in some cases, suspension of your shipping capabilities.

Number of Labels Required Per Service

U.S. Domestic

Service Type

Laser Label—PDF Format

FedEx Express U.S. Domestic C.O.D.

1 Shipping label

1 C.O.D. (Collect On Delivery) Return label

FedEx Ground/Home Delivery U.S. Domestic

1 Shipping label

FedEx Ground U.S. Domestic C.O.D.

1 Shipping label

2 C.O.D. Return labels

U.S. Export International

Service Type

Laser Label—PDF Format

FedEx Express U.S. Export International

1 Shipping label in the reply; a minimum of 3 labels must be printed—1 label on the package and 2 in the document pouch.

FedEx Express U.S. Export International Broker Select Option

1 Shipping label in the reply; a minimum of 3 labels must be printed—1 label on the package and 2 in the document pouch.

FedEx Ground U.S. Export International

1 Shipping label

FedEx Ground U.S. Export International C.O.D.

1 Shipping label

2 C.O.D. Return labels

Intra-Canada

Service Type

Laser Label—PDF Format

FedEx Express Intra-Canada

FedEx Express Intra-Canada

Non-DG (Dangerous Goods)/Dry ice shipment:

1 Shipping label

FedEx Ground Intra-Canada

1 Shipping label

FedEx Ground Intra-Canada C.O.D.

1 Shipping and 2 C.O.D. Return

Canada Export International

Service Type

Laser Label—PDF Format

FedEx Express Canada Export International

FedEx Express Canada Export International

Non-DG/Dry ice shipment:

1 Shipping label

2 Consignee labels

FedEx Express Canada Export International Broker Select Option

FedEx Express Canada Export International Broker Select Option

Non-DG/Dry ice shipment:

1 Shipping label

2 Consignee

FedEx Ground Canada (CA) Export International

1 Shipping Label

Custom Labels

To support your shipping application, Web Services provides two options for customizing your shipping label:

Place the .PNG 4x6 label graphic on your label stock. For example, you may create a packing list on an 8.5” x 11” form. As part of this form, you may also place the 4x6 .PNG label graphic instead of creating a custom label on 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 for your graphic or text.

Using a Customizable Section of a Thermal Label

Fed Web Services provides two thermal label formats that you can customize with either a graphic or text file to prevent the need for creating a custom label. These formats are:

4x8 thermal label without DocTab
4x9 thermal label with DocTab

These label types provide a 1.5 inch customizable section. This feature is only applicable to the thermal label printed on a thermal printer set to 203 DPI.

The rules for using these label formats are:

These labels support all FedEx shipping services (Express, Ground, International).
Only the shipping label can be customized. For example, if you print a 4x8 Express shipping label with your logo, the secondary consignee labels will not display it.
The customizable graphic or text must not exceed 1.5” high and 4.5” wide.
No correction is provided by FedEx. The graphic and/or text prints as it is submitted in the shipping service.
If all the necessary data for printing the graphic and/or text is not provided (for example: X and Y coordinates), a valid shipping label is returned without the customized data. You must cancel the shipment represented by this label if you attempt to recreate another label with the graphic and/or text.
Printer restrictions require the position origin at the top left quadrant of the front. Therefore, it is possible for data to start in the customizable section of the label and write down into the FedEx portion of the label (actual thermal label data). If this occurs, your logo or text will be written over with the FedEx label information. You must correct this positioning to use the shipping label.
The addition of DocTab information to the 4”x 9” label must be configured using the same process as you would use for a standard 4x6 DocTab thermal label. For more information, see DocTab Configuration.

To Add Text to the 4x8/4x9 Label

In the Ship Service WSDL, use the CustomLabelDetail (ComplexType) and choose the TextEntries element.

In the TextEntries element, six elements are required:

CustomLabelTextEntry/Postion includes—the x/y coordinates for placement of the text.
CustomLabelTextEntry/Format—contains the text to be printed on the label.
CustomLabelTextEntry/ThermalFontID—the logical font that will be translated to the appropriate printer font. Valid values: from 1 to 23.
LabelFormatType—the label format type should be set to COMMON2D.
LabelImageType—set to the language type for your hardware.
LabelStockType—set to either STOCK_4X8 or STOCK_4X9_LEADING_DOC_TAB.

To Add a Graphic to the 4x8/4x9 Label

In the Ship Service WSDL, use the CustomLabelDetail (Complex Type) and choose the GraphicEntries element.

In the GraphicEntries element, five elements are required:

Position—the x/y coordinates for placement of the graphic.
PrinterGraphicID—the file location of the graphic you want to include on the label.
LabelFormatType—the label format type should be set to COMMON2D.
LabelImageType—set to the language type for your hardware.
LabelStockType—set to either STOCK_4X8 or STOCK_4X9_LEADING_DOC_TAB.

PNG Label

Web Services provides .PNG (Portable Network Graphic) images for FedEx Express, FedEx Ground and FedEx International Express Ground labels. The .PNG label graphic is a replica of the thermal labels supported by Web Services. This label option allows you to place the .PNG label graphic on your label stock to prevent the need for creating a custom label. The .PNG label format is available for U.S. domestic shipping only (Express and Ground).

The following requirements apply when using the 4” x 6” PNG graphic embedded in your shipping document:

Label Stock

4”x6” PNG labels should only be used with peel and stick label stock. The FedEx Ground and FedEx Express label certification teams will reject 4”x6” PNG labels that are not on peel and stick label stock, including any labels printed on plain paper.

Printer

Laser printers are recommended for printing labels. Inkjet printers should not be used because of their inconsistency in creating scannable bar-codes. Due to the inconsistent print quality, the label certification teams reject most labels that are created with inkjet printers. The 4”x6” PNG label cannot be printed using a color printer unless the color definition is set to black, even if the printer only has a black cartridge installed. This setting is necessary to achieve the correct bar-code definition for scanning at the FedEx hubs.

Scaling

The image returned in your shipping transaction is 200 dots per inch (DPI) and measures 4" (W) x 6” (H) or 800 x 1200 pixels. This label has a vertical orientation and is designed to print in a 4” x 6” label area. When printed, the label should measure 4” x 6”. When you generate a PNG label image in Web Services, the image is produced in 200 DPI, which is the minimum bar-code DPI. When you view the image on your screen, most applications degrade the DPI to your screen resolution. Typically, this is 96 DPI, which is far less than the minimum bar-code DPI required. To produce the label and bar-codes in the required DPI, you must scale (or resize) the image before printing. How you scale the image depends on the application you are using to view and print the label.

Scaling Instructions for PNG Labels

To scale the PNG image for a 4x6 label in inches: 4” width and 6” length exactly.

To scale the PNG image for a 4x6 label in pixels:

If your screen resolution is 96 DPI:
o Width = 384 pixels (96 ÷ 200 x 800 = 384)
o Height = 576 pixels (95 ÷ 200 x 1200 = 576)
If your screen resolution is 72 DPI:
o Width = 288 pixels (72 ÷ 200 x 800 = 288)
o Height = 432 pixels (72 ÷ 200 x 1200 = 432)
If your screen resolution is not 96 or 72 DPI
o Width = Your screen DPI ÷ 200 x 800
o Height = Your screen DPI ÷ 200 x 1200

Submit Custom Labels to FedEx

Before you can produce custom labels in a production environment, FedEx must first test these labels to ensure that FedEx can scan them for routing and delivery. The following process outline will help you gather the information you need for label certification.

Label Sets Required

The types of printer models you support determines how many sets of labels that must be submitted to FedEx:

For FedEx Express: From the FedEx Express label test cases, submit three labels for each scenario that you will be using.
For FedEx Ground: From the FedEx Ground label test cases, submit three labels for each scenario that you will be using.

You must produce labels from each printer type you use. For example, if you use an Eltron 2348 and an Eltron 2342 to print thermal labels, you must send in three sets of labels for each of these printers.

Note: You should only produce labels for the services you will be using. For example, if you will not be shipping FedEx 2Day, you don’t need to create sample labels for this service.

Label Stock Required

Use only white label stock (near infrared for direct thermal printing). A minimum of 6 inches of vertical space is required. If correct label stock is not used, labels will not pass certification. For laser labels, high-grade pure white paper is required.

Print Quality and Layout Requirements

Problems with print quality and overall layout can cause labels to fail certification. Most problems can be easily detected and corrected before submitting labels. For each printer to be used for label submission, print one test label and go through the Label Review Checklist to determine if a problem exists before printing labels for the remaining test cases.

Label Review Checklist

Use these lists to check for problems before you submit each set of labels.

All Bar-Codes

Required for validation:

Quiet Zone¾Must always have at least .1” blank white space both above and below bar-code
Quiet Zone—Must always have at least .2” blank white space both left and right of bar-code
Validate that all bar-codes meet minimum height requirements

Print Quality

Common problems that cause labels to be rejected:

Split Bars
Faded Print/White Voids
Repeating White Voids (roller problem)
Smudging (thermal transfer)
Flaking (laser) – Toner Fusion Problem
Wrinkled in the Print (thermal transfer)
Print Contrast – direct thermal labels – Must be at least 90%

Human Readable for Ground Labels

Required for validation:

Data matches bar-code
Service Code (matches bar-code) – Human readable text may not be present on Common Label
Text 1___ Text 2___ Text 3___ (matches FedEx Ground Active Service Codes)
Home Delivery labels must have a large “H” in a box within 1” of the ship to address. The “H” must be at least .25”x .70”.
FedEx Ground Logo: see Appendix R: Ground Plain Paper Label Samples and Appendix S: Ground Thermal Label Samples. Logos are available for download from the FedEx Identity Web site fedexidentity.com.

Human Readable for Express Labels

The following elements must be printed on the label to pass certification:

FedEx Express Logo: see Appendix P: Countries Accepting Electronic Commercial Invoices (ECI) and Appendix R: Ground Plain Paper Label Samples. Logos are available for download from the FedEx Identity Web site fedexidentity.com.
Service Description
Package type, if International
Delivery day of the week (example: MON for Monday)
Deliver by date
Meter number
Ship date
Format of piece count, Master label verbiage, CRN label verbiage on all MPS
Airport Ramp ID
Postal code and routing
URSA routing prefix and suffix
Handling codes
Service area commitment
Recipient and shipper’s telephone numbers
Weight
Dims, if applicable (Dims are always required for Express Freight.)
Reference field if an alcohol shipment
Tracking number and Form ID (Tracking number must be 3 sets of 4 digits – total of 12 digits.)