Message scope is unclear
Order and invoice messages require separate decisions.
Professional support for library collections and private collectorsFrom Düsseldorf to the World
A standard name begins a profile; it does not prove a live connection.
Our library supply service covers Russian and Ukrainian books only.
Describe your library taskThe technical exchange is scoped and tested with the library before operational use.
01
Order and invoice messages require separate decisions.
Identifiers and delivery must be verified.
02
Operational use requires an agreed message profile, codes, validation cases, security, and test exchange.
03 / Example of an agreed profile
We accept the library's existing acquisition data, verify the title and availability, and return the agreed fields to the library workflow.
ISBN, title list, order reference, and the acquisition fields required by your library.
We map fields, check required values, and prepare a limited test specimen for acceptance.
Verified bibliographic data, price, and status through the agreed format and transport route.
Illustrative example. Field mapping, character set, validation, and transport are agreed before a pilot.
UNH+<message-ref>+ORDERS:D:96A:UN:EAN008'
LIN+1++9785171608392:EN'
QTY+21:<quantity>'
RFF+ON:<library-order-reference>'
UNT+<segment-count>+<message-ref>'
transport · identifiers · optional segments → <agreed pilot profile>04
Name business messages in scope.
Agree IDs, folders, validation.
Exchange test messages.
05
A test order has library reference, ISBN lines, and acknowledgement.
06
The exact exchange is visible.
Acceptance follows test results.
07 / Exlibrus