To slim the project workflow, we will be happy to create XML structures for you, including adapted file references (PDFs, JPEGs, TIFFs, etc.) specifically for your products at the start of the project, based on the example data you provide.

Current version is

V 2.3.4

Orders / dispatch to non-EU

The new version contains just 4 new tags and enables you to sent us all information for non-EU shipments and a new functionality:

Changes from 2.3.3 to 2.3.4:

New functionality:
<shipping_date>2016-11-22</shipping_date>

shipping_date: products have fixed SLAs (e.g. 2 days). To transmit us orders and perform a backwards calculation, you can specify a desired shipping date greater than 2 days SLA in the future. Optional we can activate an option that enables us to produce such orders earlier, if we have free capacity. Please talk about that options with your contact person at Elanders.

New tags:

... item => item_cost => customs_declaration:
<country_of_origin>Germany</country_of_origin>
 
... invoicing => biller:
<sales_control_number>123456</sales_control_number>
 
<bank_iban_swift>123456</bank_iban_swift>
<bank_bic>123456</bank_bic>
 
<signature>YOUR NAME</signature>

To sent to non-EU you have to provide information in the following sections:

All childs here:
/root/order/invoicing/biller
/root/order/items/item/item_cost/customs_declaration

Always correct country code (iso3166_2) here:
/root/order/shipping/delivery_address/countrycode

For non-EU dispatch please add your shipper address here too:

/root/order/shipping/shipper_address

Our standard XML file contains extensive comments and is available for download here.

Current XSD: general_order_v2-3.xsd

Example XML: general_order_sample.xml

Practical example: 2016_01_21_pdi_standard_xml_v2.3.4.xml

Correct closure of tags and whitespace handling

Wrong:
<first_name>     </first_name>
<middle_name></middle_name>
<last_name>   
</last_name>

Right:
<first_name/>
<middle_name/>
<last_name/>

Special characters

Please be careful to encode special characters correctly.

We recommend consistent use of CDATA.
See also http://en.wikipedia.org/wiki/CDATA.

<![CDATA[Content]]>

The “order_data” tag is freely available for your use.

You can define free tags here within the “usual limits”, which we will then use or process outside our standards. However, these can only be informational in nature within the order data, and will be used in the context of a support case.

You can add new tags during ongoing operation, and they will automatically be detected by the system and displayed in your personal myPDI Web interface.

These additional tags will be ignored by the print workflow.

The only limitation:
You cannot remove tags after adding them, because this will cause errors (production will stop)!