• All filenames (XML and references) must be unique.
• Tip: If you aren't using SOAP, then they must be unique between orders!
• ISO 9660 is used for the file naming convention.
• Transactions (XML and all references) are limited to 500 MB.
• Referenced files within a transaction are limited to 100 MB per file.
• The transmission of SOAP, including base64-encoded binaries, is limited to 20 MB.

The transmission of larger volumes per order requires previous discussion and/or special approval. A requirements and trend analysis must always be done in advance. Deviations from our standards and additional desires require prior discussion / quotation.

A print order consists of at least the transmission of the XML structure for an order.

The XML data contains the background data required to create an order, as well as the payload data needed for any customisation (depending on the product).

The XML data should ideally follow the ELANDERS standard. If using other data formats, please contact your project manager for a quotation for creating a data converter during a separate project in advance.

UTF-8

If XML data is transmitted through the Web service, no filename is required. If transmitting via FTP or sFTP, the filename must follow this scheme:

<your_unique_id>_<YYYYMMDDHHIISS>.xml

YYYY: Year, 4 digits

MM: Month, 2 digits

DD: Day, 2 digits

HH: Hour, 2 digits

Minute, 2 digits.

SS: Second, 2 digits

The filename identifies your transmission to us. We will report the filename (without the file ending / .xml) as a reference in responses to your system. You can find more information under Tracking.