MapsterLink

EDI and file exchange as a service Partner data arrives, gets translated and delivered. You just see that it all came through.

We connect your trading partners via SFTP, AS2, API or e‑mail. We check their files, translate them and deliver them to your system. Operations are on us – you get a portal with every transfer.

Send us a sample file and see the result before you commit to anything.

  • 24/7monitoring and support
  • 4ways to transfer
  • 2×schema check, input and output
  • 100 %of transfers traceable in the portal
Transfer
  • SFTP
  • AS2
  • HTTP API
  • E-mail
Formats
  • EDIFACT
  • XML
  • JSON
  • CSV
  • TXT
  • Excel
  • PDF and attachments

Sound familiar?

Every partner sends data differently

One supplier sends EDIFACT over AS2. Another uploads CSV to FTP. A third has its own API and a fourth e-mails the file.

Your system, meanwhile, wants one format. That is how scripts appear that only one person understands, data gets retyped by hand and errors take ages to find.

“Did that invoice ever arrive?”With us, you have the answer in seconds.

We connect your partners, build the translation from your samples and watch operations around the clock. You get the data exactly the way you need it.

How a message travels

From your partner all the way to your system

Every dot is one message. One order can produce several outputs, and an invalid message is stopped before it reaches you. Try the switches above the diagram.

regular message file per line item original unchanged delivery retry error, alert, 503 API reply

Swipe the diagram sideways.

Synchronous API
The sender gets the reply only after processing.
Asynchronous API
The message goes to the queue, the receipt comes at once.
Destination maintenance
Messages wait in the queue and continue in the same order.

More about the service →

Features

Everything you need to exchange data with your partners

One service for EDI, file transfer and API integration. We set up whatever your partners need.

Connections SFTP, AS2, API and e-mail

  • Your own SFTP server – every partner gets a locked folder, sign-in with a password or SSH key and an optional storage limit.
  • The partner's SFTP and folders – we pick files up and deliver them, polling every few seconds or on a schedule (cron).
  • AS2 – signing, encryption and MDN receipts, certificates and several AS2 ID pairs.
  • REST API – synchronous or asynchronous intake, tokens for API clients and automatic OpenAPI (Swagger) documentation for the partner.
  • E-mail – attachments received from a mailbox (IMAP), outputs sent as attachments or ZIP with your own subject and HTML text.
More on this

Format translation EDIFACT, XML, JSON, CSV, Excel

  • Any combination – EDIFACT, XML, JSON, CSV, fixed-width TXT and Excel (xlsx, xls) as input and output.
  • Several outputs from one message – each in its own format and to its own destinations, even a separate file per line item.
  • Outputs by condition – for example orders to your ERP and returns to the warehouse from the same file.
  • Lookup tables and calculations – unit and partner codes, totals, date and number formats.
  • Document numbering – sequences such as FA2026-000042 and file names taken from the content.
  • Pass-through – PDFs, images and other attachments travel unchanged.
More on this

Data checks validation of input and output

  • Input schema – from XSD, JSON Schema or a sample file: required fields, types, allowed values and patterns.
  • Custom checks – business rules with a precise reply to the sender.
  • Output check – before delivery, so nothing that does not fit reaches your system.
  • Ignore without an error – messages you do not need are handled quietly.
  • Encoding – UTF-8 and windows-1250 are detected automatically.
More on this

Reliable operations nothing gets lost

  • A queue for every message type – the order is kept, independent files can run in parallel.
  • Delivery retries – when a destination does not respond, delivery is repeated after a set pause.
  • Recovery after restart – a received file is stored before processing and unfinished work continues.
  • Pauses and maintenance – planned in advance – messages wait in the queue or are politely declined.
  • Test and production – separate environments with their own accounts, addresses and tokens.
  • Data retention – how many days files and history are kept is up to you.
More on this

Portal overview every transfer traceable

  • Overview – processed files, success rate and errors for 7, 14 or 30 days.
  • Transfer detail – a graph from receipt to delivery, the received and the created file to download.
  • Search and filters – by status, date and even file content.
  • Process or send again – the whole transfer or a single output, depending on the rights granted.
  • E-mail alerts – on errors or when storage is filling up.
  • Billing – usage in the current month and invoices with a PAY by square QR code.
More on this

Security and access everyone sees only their own

  • Separated partner data – a partner never sees another partner's data.
  • Roles – read only, or also upload and reprocessing.
  • Encrypted credentials – passwords and keys for connections are encrypted in the database (AES-GCM).
  • Sign-in protection – account lockout, blocking of suspicious IP addresses and automatic sign-out.
  • Audit trail – a history of changes and a log of every API call.
More on this

Your portal

Every transfer in plain sight

Sign in and see only your data: how many files arrived, how they turned out and where they went.

For every transfer you will find the received file and the result. You can download both.

  • Overview for 7, 14 or 30 days
  • Transfer detail step by step
  • Errors with an explanation of what is wrong

See the portal demos

Portal screens

See what you will see

Swipe sideways and click a picture to enlarge it. When enlarged, you can zoom in and move around. The portal is shown in Slovak.

1 / 6
Overview How many files arrived in the chosen period and how many were fine.
Transfers Every received file with its result. Filter by status and date, search even in the content.
Transfer detail A graph of the message from receipt to delivery.
Received and sent files Contents side by side and neatly formatted.
Errors explained What exactly is wrong and in which step.
Status by message type Every message type separately, including its outputs.

Who does what

You get the overview. We take care of the rest.

What we take care of

  • Connecting partners. Accounts, folders, certificates and agreeing the details with the partner.
  • Translation and checks. Mapping built from your samples and schema checks on input and output.
  • Testing before go-live. Every change goes through the test environment first.
  • 24/7 operations. We see errors before you start looking for them.
  • Changes as needed. A new partner, a new field or a different format.

What you get

  • Data in your format exactly where you want it.
  • A portal for you and your colleagues with the history of every transfer.
  • E-mail alerts on errors, if you want them.
  • Extended rights to upload and reprocess files, as agreed.
  • Support that solves the problem, not a ticket.

How we start

From a sample file to live operation

Your part ends at step two. We handle the rest.

  1. 01

    A short call

    Tell us who you exchange data with and where it hurts today.

  2. 02

    Sample files

    Send a few real messages and tell us what you need from them.

  3. 03

    Design and test

    We prepare the translation and checks. You verify the results in the test environment.

  4. 04

    Go-live

    We switch to production, you get the portal and we watch over operations.

Working with us and pricing

Questions

Frequently asked questions about EDI and file exchange

More answers, including pricing, are under working with us.

What is EDI and who does MapsterLink help?

EDI (electronic data interchange) is the automated exchange of orders, delivery notes, invoices and other documents between companies. It helps any business that receives or sends data to several trading partners – manufacturers, distributors, online shops, warehouses and carriers. We take care of the connections, the translation and the day-to-day operation.

What is the difference between SFTP, AS2, API and e-mail?

SFTP is a secure transfer of files into a folder. AS2 sends signed and encrypted messages with a delivery receipt (MDN) and is used mainly by retail chains. An API (REST) is a direct call between systems, synchronous or asynchronous. E-mail suits partners without IT – the file arrives as an attachment. We support all four, for receiving as well as sending.

Can you translate EDIFACT to XML, JSON, CSV or Excel?

Yes. We translate EDIFACT, XML, JSON, CSV, fixed-width TXT and Excel (xlsx, xls) in any combination. One message can produce several outputs in different formats for different systems – for example an invoice as XML for your ERP and a summary as CSV for accounting.

Does our partner have to change or install anything?

No. Your partner keeps sending data the way they are used to and nothing is installed on your side. The partner gets their own credentials and sees only their own folder or API.

What happens to a faulty file or during an outage?

A faulty file is stopped by the schema check and never reaches your system. The portal shows exactly what is wrong and an e-mail alert can be sent. When your system does not respond, delivery is retried. Received files are stored before processing, so nothing is lost even when a server restarts.

How are our data and access protected?

Every partner sees only their own data. Passwords and keys for connections are stored encrypted, sign-in is protected by account lockout and blocking of suspicious IP addresses, and SFTP folders are isolated from each other. Every change and every API call is logged.

Have a partner who sends data differently?

Send us a sample file. We will show you what the result looks like in your format.

Write to us