ShipWorks Templates: Comprehensive Technical Guide
ShipWorks templates are an integral part of the ShipWorks system, allowing businesses to generate reports, shipping labels, and customer communications with ease. These templates are highly customizable, enabling users to tailor the output to meet specific business needs. This article delves into the technical aspects of ShipWorks templates, focusing on how they are constructed using HTML and XSLT v1 to transform data from the "XML Source" template.
Intended Audience
This article is intended for users who are curious about the inner workings of ShipWorks templates and may wish to understand the basics of template modifications. While a typical ShipWorks user or operator might not need this information for day-to-day operations, it is valuable for those looking to customize templates beyond the standard configurations.
ShipWorks provides several avenues for you to get help with modifying and customizing templates. In case you want to avoid all the technical reading and just get help).
-
Support Team: You can contact our support team for assistance with template customizations. Simple modifications are often handled free of charge, while more complex customizations may incur a fee.
-
Help Documentation: Our comprehensive help documentation includes numerous examples of common template modifications. This resource is an excellent starting point for users looking to make changes to their templates.
-
ChatGPT: ChatGPT is an excellent resource for getting help with ShipWorks templates. By providing ChatGPT with a detailed context of the ShipWorks template system, including the XML source data for an example order and an example packing slip template code, users can receive high-quality assistance with modifications.
-
Community Forums: The ShipWorks community forums are a valuable resource where users can ask questions, share tips, and collaborate on template modifications.
ShipWorks templates are customizable documents used for various purposes within the ShipWorks software. These templates can be used for:
-
Business reporting
-
Exporting data
-
Communicating with customers via email
ShipWorks offers a comprehensive array of pre-configured reports that are available out of the box. These reports are tailored to meet your business needs without requiring any customization. They empower you with insightful analytics, allowing you to make informed decisions and optimize your shipping workflows effortlessly.
The following Pre-configured reports and templates are available in ShipWorks:
-
Shipment Notification Email
-
Invoices
-
Packing Slips
-
Customer Detail Export
-
Orders with Items Export
-
Package Level Details Export
-
Tracking Numbers Export
-
Order Charges Breakdown Financial Report
-
Shipments by Provider Report
-
Shipping Cost by Carrier Financial Report
-
Shipping Profit and Loss Financial Report
-
Order Status Report
-
Order Summary Report
-
Orders by Time of Day Report
-
Shipper Productivity Report
-
Pick Lists, grouped and sorted by:
-
Item SKU
-
Item Location
-
Item Name
-
Item Quantity
-
-
Product Trend Reports, grouped and sorted by:
-
Order Total
-
Item Name
-
Item Quantity
-
Item SKU
-
The Template Manager is the central location to manage, create, and edit ShipWorks templates.
To view the ShipWorks Template Manager,
The Template Manager popup lets you choose how to preview a template, which helps to edit report template types.
Blank Preview
The preview may be blank if you open Template Manager and the Preview filter you selected has zero orders.
Let’s delve into the technical aspects of ShipWorks templates, explaining how they are constructed and used.
XML Source
The XML Source is the backbone of any ShipWorks template or output. It contains all the relevant data about orders, shipments, customers, and more. When a report is run, ShipWorks generates this XML Source dynamically, which is then used by the template to create the desired output. See the Appendix for an example of an XML Source document for a single order.
XSLT v1
XSLT v1 is a powerful language for transforming XML documents into other formats, such as HTML. In the context of ShipWorks templates, XSLT is used to read the XML Source and apply transformations to generate the final document.
HTML
HTML is used within ShipWorks templates to define the structure and presentation of the output. By combining XSLT and HTML, you can create highly customized and visually appealing documents.
View or Print XML Source
You can view/output the XML Source for an order or group of orders in ShipWorks by selecting the orders, clicking Output, View (or Compose Email or Save), and choose the XML Source template in the System\Utility folder at the bottom of the list.
-
Generating the XML Source:
Whenever ShipWorks runs a report or processes shipping labels for one or more orders, it creates an XML Source document in memory for these orders. This document serves as the backbone of raw data input for any templates (and for tokenized fields).
-
Constructing the Template:
ShipWorks templates are constructed using a combination of HTML syntax for general structure and formatting and the XSLT v1 code completes the data transformation. This process involves selecting specific XML elements and attributes, applying formatting rules, and integrating them into the HTML structure.
-
Transforming Data:
The XSLT v1 processor takes the XML Source data and applies any of the XSLT code to transform and produce the final output along with the HTML. In other words, the XSLT code pulls the desired bits of data from the XML Source report for each order(s) and outputs them in the desired, pretty format.
Here is an example of the default Email Shipment Notification template code. Notice the different elements of both HTML and XSLT.
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sw="http://www.interapptive.com/shipworks" extension-element-prefixes="sw"> <!-- Imports --> <xsl:import href="System\Snippets" /> <xsl:output method="html" encoding="utf-8" /> <!-- Start of template --> <xsl:template match="/"><xsl:apply-templates /></xsl:template> <xsl:template match="ShipWorks"> <!-- Default font. Specified as a variable since GMail and Outlook behave differently. --> <xsl:variable name="pageFont" select="'font-family: Tahoma; font-size: 10pt;'" /> <html> <head> <title>Shipment Notification</title> <style> body, table { <xsl:value-of select="$pageFont" /> } </style> </head> <body style="{$pageFont}"> <xsl:variable name="order" select="Customer/Order[1]" /> <xsl:variable name="address" select="$order/Address[@type='bill']" /> <xsl:value-of select="$address/FirstName" />, <p> Your order <!-- Shared Snippet --> #<xsl:call-template name="OrderNumber"> <xsl:with-param name="order" select="$order" /> </xsl:call-template> has shipped and the tracking information is below. Thank you for your business! </p> <p> <xsl:if test="count($order/Shipment[Status = 'Processed']) = 0"> <i>(No shipments)</i> </xsl:if> <xsl:for-each select="$order/Shipment[Status = 'Processed']"> Shipped on <b><xsl:value-of select="sw:ToShortDate(ShippedDate)" /></b> using <b><xsl:value-of select="ServiceUsed" /></b>: <b><xsl:call-template name="TrackingLink" /></b> <br /> </xsl:for-each> </p> <p> Sincerely,<br /> <xsl:value-of select="Store/Address/Company" /> </p> </body> </html> </xsl:template> </xsl:stylesheet>
Here is how the code looks in the Template editor.
ShipWorks templates come with a variety of settings that allow you to control different aspects of your templates. These settings are divided into several main sections: Printing, Page (or Label) Setup, General, Saving, and Email.
The Printing section allows you to select your printer and tray for this template. These printer settings are unique to each computer in your environment where ShipWorks is installed.
In the Page (or label) Setup section, you can configure the sizes and orientation of your paper or label for when you print and output them. Labels can be configured to print numerous or one per page (in any orientation), and they come with a variety of Avery and Dymo preformatted label setups. This section will show Label Setup only when the Template type is Label.
Here you can configure the following:
-
Template Type: Determines the type of output. Options include Standard, Label, Report, and Thermal.
-
Standard: Typical output processed uniquely for each order, like printing an invoice for each chosen order on standard paper.
-
Label: For printing shipping, address, and similar types of labels, such as 4x6" shipping labels or Avery address labels.
-
Report: Processes multiple orders at once with a single consolidated report output.
-
Thermal: Special format used by ShipWorks for sending direct thermal (EPL/ZPL format) files to a Zebra thermal printer.
-
-
Output Format: Determines how the report should output when saved/emailed. Options include HTML, Text, and XML.
-
Output Encoding: Chooses how the files are encoded when saved. Options include Unicode (UTF-7), UTF-8 (default), Unicode (UTF-16), UTF-32, Windows (ISO-8859-1), and ASCII.
-
Process For Each: Determines the context in which to process each entity (like order, item, shipment). Options include Automatic (default), Customer, Order, Shipment, and Order Item. For example, if you select Order Item, ShipWorks will process the template as if you had selected each individual order item in the order.
The Saving section allows you to configure how the template outputs or saves. You can choose the default file name and location (which can be a network drive) and configure how the application prompts the user when saving files. These fields are tokenized for convenience.
The Email section lets you choose which email account configured in ShipWorks is used to send this template via email. You can also set the default To, CC, BCC, and Subject fields. These input fields are tokenized and can use tokens/XSLT to automate tasks, such as setting the email address to be the order number bill to email value.
To accommodate unique brands using the software, you can uniquely configure the From email account for each Template and for each store you have configured within ShipWorks.
There is a special template called Snippets within the ShipWorks template system. Snippets are reusable pieces of template code that can be called and accessed from within any other standard template. The primary purpose of Snippets is to promote reusability and consistency across multiple templates.
Snippets reside in the System\Snippets folder in the Template structure. You can add or edit them just like standard templates. To ensure uniformity and save you time on template maintenance, when a Snippet is updated, the changes automatically cascade to all templates that include it.
Here is an example of the Invoice Ship To Snippet which is used in most ShipWorks default included templates.
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:sw="http://www.interapptive.com/shipworks" extension-element-prefixes="sw"> <xsl:import href="System\Snippets\FormatAddress" /> <xsl:output method="html" encoding="utf-8" indent="yes" /> <xsl:template name="InvoiceShipTo"> <xsl:param name="order" /> <xsl:variable name="showAddress" select="$order/IsManual = 'true' or /ShipWorks/Store[@ID = $order/@storeID]/StoreType != 'eBay' or $order/eBay/CheckoutComplete = 'true'" /> <xsl:if test="$showAddress"> <xsl:call-template name="FormatAddress"> <xsl:with-param name="address" select="$order/Address[@type='ship']" /> </xsl:call-template> </xsl:if> <xsl:if test="not($showAddress)"> <font color="#FF0000"> <b>Checkout incomplete.</b> </font> <br /> Winning Buyer: <xsl:value-of select="$order/eBay/BuyerID" /> </xsl:if> </xsl:template> </xsl:stylesheet>
Here is an example of how this Snippet is called or imported by another template.
<xsl:call-template name="InvoiceShipTo"> <xsl:with-param name="order" select="$order" /> </xsl:call-template>
ShipWorks offers a unique feature that enhances the main UI by allowing templates to be displayed in the main grid, either in place of or alongside the standard data columns for each order. The Normal with Template view and Template Only view features both enable you to show additional information that wouldn't normally appear in the grid.
For instance, if your item data includes URLs for product images, you could configure the grid to display all the usual fields and, below them, images of all the products in the order. Another example is to highlight item quantities with a red box outlined when the quantity is greater than one, programmatically in the UI. This visual cue can help warehouse shippers avoid mistakes.
Want to color code rows based on item categories or similar? Template view can do it!
Anything you can put on a webpage you can show along with order data in the main grid. Get creative!
You can access this feature by clicking on View > Normal with Template or Template Only, and then select your desired template.
You can uniquely customize Grid views in ShipWorks for each filter configured and for each user. Customization provides tailored views to suit specific needs, and it allows for a highly flexible and personalized user experience.
ShipWorks comes bundled with two default Normal with Template view templates: Item Details and Notes. These two templates can be found in the System\Grid (Detail View) folder.
-
Item Details: This template displays all item names, quantities, SKUs, etc., for each order. The standard ShipWorks grid will only show these details for single-item orders without using the items panel for each order.
-
Notes: This template shows any, and all, notes associated with each order directly in the grid. This template eliminates the need to select each order and view the notes panel one order at a time.
Using Image Assets
When you update code to include an image asset, such as
<img src="\\example-network-drive\folder\image.jpg" />
,
once the template is saved, ShipWorks will save the asset image in the ShipWorks database and load it from the database going forward.
This action ensures the template does not fail to display if the image is ever moved. The exception to this rule is if the source location is a network drive, such as <img src=\\example-network-drive\folder\image.jpg/>
.
The code tab and editor in ShipWorks come equipped with these powerful features to enhance your template editing experience.
-
Syntax color coordination helps you to be more effective when making template edits.
-
Maroon: HTML, XSLT, and other syntaxes are color-coded as follows: elements like
<body>
are maroon -
Red: Element attributes like
style
in<body style=
are red -
Blue: Attribute values like the
example
part of<body style="example"
are blue -
Black: Normal static text that will output is black
-
Green: commented syntax like
<!-- example -->
is green
-
-
Automatic creation of necessary closing tags is another helpful editing feature. For example, if you type
<body>
, the editor will automatically populate the corresponding</body>
closing tag. -
Maintain Visual Simplicity: This feature helps by allowing you to tab new sections or tab parent-child sections within each other. You can even highlight groups of text and press the tab key (or shift+tab for reverse) to adjust the indentation of all selected
code
at once.
These features collectively make the template editing process more efficient and user-friendly.
ShipWorks templates offer a robust and flexible way to customize your business documents. By understanding the basics of XML, XSLT, and HTML, you can create and modify templates to suit your specific needs. Whether you are generating reports, shipping labels, or customer communications, ShipWorks templates provide the tools to streamline and enhance your business processes.
For further assistance, our support team, help documentation, community forums, and ChatGPT are available to help you make the most of the ShipWorks template system.
HTML seems pretty common but what is XSLT v1?
XSLT (Extensible Stylesheet Language Transformations) is a language for transforming XML documents into other formats like HTML, plain text, or other XML formats.
XSLT v1.0 is the first version of this language, and it provides a robust set of tools for handling XML data.
The following are descriptions and samples of common code and syntax elements as they might relate to using templates in ShipWorks.
-
XSLT Stylesheet Declaration:
An XSLT stylesheet is an XML document with specific elements and attributes. The root element of an XSLT stylesheet in ShipWorks is
<xsl:stylesheet>
.<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <!-- XSLT and or HTML code goes here --> </xsl:stylesheet>
-
Template Rules / Match:
Templates define how specific elements in the source XML document should be transformed. A template is defined using the
<xsl:template>
element and typically includes a `match` attribute to specify the XML elements it applies to.<xsl:template match="/"><xsl:apply-templates /></xsl:template> <xsl:template match="ShipWorks">
-
Value-of Element
The
<xsl:value-of>
element is used to extract the value of an XML element or attribute and output it.<xsl:value-of select="ServiceUsed" /> or <xsl:value-of select="//Order/Address[@type='bill']/LastName" /> or <xsl:value-of select="Store/Address/Company" /> or <xsl:value-of select="//Order/Number" />
-
For-Each Element
The
<xsl:for-each>
element is used to loop through a set of nodes.<xsl:for-each select="$order/Shipment[Status = 'Processed']"> Shipped on <b><xsl:value-of select="sw:ToShortDate(ShippedDate)" /></b> using <b><xsl:value-of select="ServiceUsed" /></b>: <b><xsl:call-template name="TrackingLink" /></b> <br /></xsl:for-each>
-
If Element
The
<xsl:if>
element provides conditional processing.<xsl:if test="count($order/Shipment[Status = 'Processed']) = 0"> <i>(No shipments)</i> </xsl:if> or <xsl:if test=”//Order/Number = ‘123’”>This is order # 123!</xsl:if>
-
Variable Element
The
<xsl:variable>
element provides ways to create variables used for additional manipulation.<xsl:variable name="order" select="//Order” /> Order #: <xsl:value-of select=”$order/Number” />
To determine the proper XSLT path syntax based on our XML Source report, you can follow these steps:
-
Identify the starting point in the XML structure.
-
Use double slashes // to start from anywhere in the XML document.
-
Identify the hierarchy by noting the nested elements.
-
If filtering by an attribute, use square brackets [] with the attribute name and value.
-
For example, if you want to grab the SKU value from an Item element within an Order, you can use the path //Order/Item/SKU because Item is a child of Order and SKU is a child of Item.
If you need to filter by an attribute, such as the address with type="from"
, you can use the following path: //Address[@type='from']
.
This syntax selects the Address element where the type attribute equals "from".
Here's an example to illustrate both scenarios in XSLT. The below example will generate an HTML document displaying all SKU values from Item elements within an Order, as well as the details of the Address element where type is "from".
<?xml version="1.0" encoding="utf-8"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:output method="html" encoding="utf-8" /> <!-- Start of template --> <xsl:template match="/"> <html> <head> <title>Example</title> </head> <body> <h2>Order Items</h2> <table border="1"> <tr> <th>SKU</th> </tr> <xsl:for-each select="//Order/Item"> <tr> <td><xsl:value-of select="SKU" /></td> </tr> </xsl:for-each> </table> <h2>From Address</h2> <xsl:for-each select="//Address[@type='from']"> <p><b>Company:</b> <xsl:value-of select="Company" /></p> <p><b>Line1:</b> <xsl:value-of select="Line1" /></p> <p><b>City:</b> <xsl:value-of select="City" /></p> <p><b>State:</b> <xsl:value-of select="StateCode" /></p> <p><b>Postal Code:</b> <xsl:value-of select="PostalCode" /></p> </xsl:for-each> </body> </html> </xsl:template> </xsl:stylesheet>
Below is an example of the XML Source output for an international order with a UPS-processed shipment to Great Britain.
See More Store and Marketplace-specific Fields
The following example does not contain every possible field. View the XML Source with your own orders in ShipWorks to see additional store and marketplace-specific fields.
<?xml version="1.0" encoding="utf-8"?> <ShipWorks> <Generated>2024-07-19T02:08:22.6835825Z</Generated> <Timestamp>1721354902</Timestamp> <UniqueID>{0de9f028-30f6-48c0-a1a4-b5c645a29828}</UniqueID> <Context>Order</Context> <Template> <Name>XML Source</Name> <Folder>System\Utility</Folder> <Output> <ContentWidth>7</ContentWidth> <ContentHeight>9.5</ContentHeight> </Output> </Template> <User ID="1002"> <Username>user-bbdev7@example.com</Username> <IsAdmin>true</IsAdmin> </User> <Store ID="1005"> <StoreName>Example Store</StoreName> <StoreType ID="28"> <Code>GENERIC</Code> <Name>Generic - Module</Name> </StoreType> <LastDownload>2024-07-19T01:53:16.333Z</LastDownload> <Address type="company"> <Company>ShipWorks-Auctane QA-Testing</Company> <Line1>4301 Bull Creek Rd</Line1> <Line2></Line2> <Line3></Line3> <City>Austin</City> <StateCode>TX</StateCode> <StateName>Texas</StateName> <PostalCode>78731</PostalCode> <CountryCode>US</CountryCode> <CountryName>United States</CountryName> <Phone>8009527784</Phone> <Fax></Fax> <Email>My-Warehouse@example.com</Email> <Website>http://www.shipworks.com</Website> <AddressValidationStatus>Not Checked</AddressValidationStatus> <ResidentialStatus>Unknown</ResidentialStatus> <POBox>Unknown</POBox> <USTerritory>Unknown</USTerritory> <MilitaryAddress>Unknown</MilitaryAddress> </Address> </Store> <Customer ID="2012"> <Summary> <TotalSpent>10.0000</TotalSpent> <OrdersPlaced>1</OrdersPlaced> </Summary> <Address type="ship"> <FullName>test london</FullName> <FirstName>test</FirstName> <MiddleName></MiddleName> <LastName>london</LastName> <Company></Company> <Line1>200 Grays Inn Road</Line1> <Line2></Line2> <Line3></Line3> <City>London</City> <StateCode></StateCode> <StateName></StateName> <PostalCode>WC1X 8XZ</PostalCode> <CountryCode>GB</CountryCode> <CountryName>Great Britain</CountryName> <Phone></Phone> <Fax></Fax> <Email>exanp@example.com</Email> <Website></Website> <AddressValidationStatus>Not Checked</AddressValidationStatus> <ResidentialStatus>Unknown</ResidentialStatus> <POBox>Unknown</POBox> <USTerritory>Unknown</USTerritory> <MilitaryAddress>Unknown</MilitaryAddress> </Address> <Address type="bill"> <FullName></FullName> <FirstName></FirstName> <MiddleName></MiddleName> <LastName></LastName> <Company></Company> <Line1></Line1> <Line2></Line2> <Line3></Line3> <City></City> <StateCode></StateCode> <StateName></StateName> <PostalCode></PostalCode> <CountryCode>US</CountryCode> <CountryName>United States</CountryName> <Phone></Phone> <Fax></Fax> <Email></Email> <Website></Website> <AddressValidationStatus>Not Checked</AddressValidationStatus> <ResidentialStatus>Unknown</ResidentialStatus> <POBox>Unknown</POBox> <USTerritory>Unknown</USTerritory> <MilitaryAddress>Unknown</MilitaryAddress> </Address> <Order ID="3006" storeID="1005"> <Number>3-M</Number> <Date>2024-07-18T21:53:17.51Z</Date> <Status>Shipped</Status> <OnlineStatus></OnlineStatus> <IsManual>true</IsManual> <RequestedShipping></RequestedShipping> <Total>10</Total> <ChannelOrderID></ChannelOrderID> <ShipByDate></ShipByDate> <DeliverByDate></DeliverByDate> <CustomField1></CustomField1> <CustomField2></CustomField2> <CustomField3></CustomField3> <CustomField4></CustomField4> <CustomField5></CustomField5> <CustomField6></CustomField6> <CustomField7></CustomField7> <CustomField8></CustomField8> <CustomField9></CustomField9> <CustomField10></CustomField10> <Address type="ship"> <FullName>test london</FullName> <FirstName>test</FirstName> <MiddleName></MiddleName> <LastName>london</LastName> <Company></Company> <Line1>21223 Grays Inn Road</Line1> <Line2></Line2> <Line3></Line3> <City>London</City> <StateCode></StateCode> <StateName></StateName> <PostalCode>WC1X 8XZ</PostalCode> <CountryCode>GB</CountryCode> <CountryName>Great Britain</CountryName> <Phone></Phone> <Fax></Fax> <Email>exanp@example.com</Email> <Website></Website> <AddressValidationStatus>Not Checked</AddressValidationStatus> <ResidentialStatus>Unknown</ResidentialStatus> <POBox>Unknown</POBox> <USTerritory>Unknown</USTerritory> <MilitaryAddress>Unknown</MilitaryAddress> </Address> <Address type="bill"> <FullName></FullName> <FirstName></FirstName> <MiddleName></MiddleName> <LastName></LastName> <Company></Company> <Line1></Line1> <Line2></Line2> <Line3></Line3> <City></City> <StateCode></StateCode> <StateName></StateName> <PostalCode></PostalCode> <CountryCode>US</CountryCode> <CountryName>United States</CountryName> <Phone></Phone> <Fax></Fax> <Email></Email> <Website></Website> <AddressValidationStatus>Not Checked</AddressValidationStatus> <ResidentialStatus>Unknown</ResidentialStatus> <POBox>Unknown</POBox> <USTerritory>Unknown</USTerritory> <MilitaryAddress>Unknown</MilitaryAddress> </Address> <Item ID="3013"> <Name>Item Name 20240718045316</Name> <Code></Code> <SKU>SKU20240718045316</SKU> <Description></Description> <Location></Location> <ISBN></ISBN> <UPC></UPC> <Thumbnail></Thumbnail> <Image></Image> <UnitPrice>10</UnitPrice> <UnitPriceWithOptions>10</UnitPriceWithOptions> <UnitCost>0</UnitCost> <Weight>1</Weight> <Quantity>1</Quantity> <TotalPrice>10</TotalPrice> <TotalPriceWithOptions>10</TotalPriceWithOptions> <TotalCost>0</TotalCost> <TotalWeight>1</TotalWeight> <Status></Status> <IsManual>true</IsManual> <HarmonizedCode></HarmonizedCode> <Length>6</Length> <Width>6</Width> <Height>8</Height> <Brand></Brand> <MPN></MPN> <CustomField1></CustomField1> <CustomField2></CustomField2> <CustomField3></CustomField3> <CustomField4></CustomField4> <CustomField5></CustomField5> <CustomField6></CustomField6> <CustomField7></CustomField7> <CustomField8></CustomField8> <CustomField9></CustomField9> <CustomField10></CustomField10> </Item> <Payment /> <Shipment ID="3031"> <ShipmentType code="0">UPS</ShipmentType> <Status>Processed</Status> <DeliveryStatus>Accepted</DeliveryStatus> <DeliveryDate></DeliveryDate> <EstimatedDeliveryDate>2024-07-24T07:00:00Z</EstimatedDeliveryDate> <Processed>true</Processed> <ProcessedDate>2024-07-18T21:54:32.87Z</ProcessedDate> <ProcessedUser ID="1002"> <Username>user-bbdev7@example.com</Username> <IsAdmin>true</IsAdmin> </ProcessedUser> <Voided>false</Voided> <VoidedDate></VoidedDate> <ShippedDate>2024-07-18T05:00:00Z</ShippedDate> <ServiceUsed>UPS Worldwide Expedited®</ServiceUsed> <Account>ABC123</Account> <ReturnShipment>false</ReturnShipment> <TrackingNumber>1ZABC1236793649375</TrackingNumber> <TotalCharges>195.9500</TotalCharges> <TotalWeight>1</TotalWeight> <Address type="ship"> <FullName>test london</FullName> <FirstName>test</FirstName> <MiddleName></MiddleName> <LastName>london</LastName> <Company></Company> <Line1>200 Grays Inn Road</Line1> <Line2></Line2> <Line3></Line3> <City>London</City> <StateCode></StateCode> <StateName></StateName> <PostalCode>WC1X 8XZ</PostalCode> <CountryCode>GB</CountryCode> <CountryName>Great Britain</CountryName> <Phone>8009527784</Phone> <Fax></Fax> <Email>exanp@example.com</Email> <Website></Website> <AddressValidationStatus>Not Checked</AddressValidationStatus> <ResidentialStatus>Unknown</ResidentialStatus> <POBox>Unknown</POBox> <USTerritory>Unknown</USTerritory> <MilitaryAddress>Unknown</MilitaryAddress> </Address> <Address type="from"> <FullName>ShipWorks test</FullName> <FirstName>ShipWorks</FirstName> <MiddleName></MiddleName> <LastName>test</LastName> <Company>ShipWorks-Auctane QA-Testing</Company> <Line1>4301 Bull Creek Rd</Line1> <Line2></Line2> <Line3></Line3> <City>Austin</City> <StateCode>TX</StateCode> <StateName>Texas</StateName> <PostalCode>78731</PostalCode> <CountryCode>US</CountryCode> <CountryName>United States</CountryName> <Phone>8009527784</Phone> <Fax></Fax> <Email>My-Warehouse@example.com</Email> <Website>http://www.shipworks.com</Website> <AddressValidationStatus>Not Checked</AddressValidationStatus> <ResidentialStatus>Unknown</ResidentialStatus> <POBox>Unknown</POBox> <USTerritory>Unknown</USTerritory> <MilitaryAddress>Unknown</MilitaryAddress> </Address> <CustomsItem> <Description>Item Name 20240718045316</Description> <Quantity>1</Quantity> <UnitValue>10.0000</UnitValue> <TotalValue>10.0000</TotalValue> <Weight>1</Weight> <TotalWeight>1</TotalWeight> <OriginCountryCode>US</OriginCountryCode> <OriginCountryName>United States</OriginCountryName> <HarmonizedCode></HarmonizedCode> </CustomsItem> <BestRateEvent>None</BestRateEvent> <ShipSense> <Status>NotApplied</Status> <ChangeSets /> </ShipSense> <BilledType>Unknown</BilledType> <BilledWeight>0</BilledWeight> <Package ID="3063" TrackingNumber="1ZABC1236793649375"> <Insurance> <Provider>None</Provider> <InsuredValue>0</InsuredValue> </Insurance> <Dimensions> <Length>6</Length> <Width>6</Width> <Height>8</Height> </Dimensions> <TotalWeight>1</TotalWeight> </Package> <TIN>GB1234567890 (IOSS)</TIN> <Labels type="image"> <Package ID="3063"> <Primary> <Label name="Label" orientation="tall" width="1200" height="1800" widthInches="4" heightInches="6">5d0fd778.png</Label> <Label name="Label" orientation="wide" width="1800" height="1200" widthInches="6" heightInches="4">5d0fd778-rot90.png</Label> </Primary> <Supplemental> <Label name="Form" orientation="tall" width="2550" height="3300" widthInches="8.5" heightInches="11">da8db0fd.png</Label> <Label name="Form" orientation="tall" width="2550" height="3300" widthInches="8.5" heightInches="11">da8db0fd.png</Label> <Label name="Form" orientation="tall" width="2550" height="3300" widthInches="8.5" heightInches="11">da8db0fd.png</Label> <Label name="Form" orientation="wide" width="3300" height="2550" widthInches="11" heightInches="8.5">da8db0fd-rot90.png</Label> <Label name="Form" orientation="wide" width="3300" height="2550" widthInches="11" heightInches="8.5">da8db0fd-rot90.png</Label> <Label name="Form" orientation="wide" width="3300" height="2550" widthInches="11" heightInches="8.5">da8db0fd-rot90.png</Label> </Supplemental> </Package> </Labels> <RequestedLabelFormat>Standard</RequestedLabelFormat> </Shipment> </Order> </Customer> </ShipWorks>
Still Need Help?
Please feel free to reach out to one of our awesome Technical Support Representatives in St. Louis. We are happy to help.
Have a comment to share about this article? We'd love to hear from you. You must be logged in to your Support Portal account to leave a comment.
Comments
0 comments