Sending scan data to your ERP or WMS automatically via FTP, SFTP or REST

Scanning on the floor is step one. But scan data only becomes valuable once it lives in your own system: the ERP that tracks stock, the WMS that drives orders, or your client's logistics platform. That is exactly where things tend to go wrong in practice — USB sticks, e-mails with attachments, retyping by hand. It can be much simpler.

The bridge between scanner and system

ScanVerify is deliberately built as a bridge, not a replacement. Your current ERP or WMS stays in charge; the app handles scanning, verification and delivery of the results in a format your system already understands. No large integration project needed — you configure an export profile once, and the data arrives the way your system expects it.

Pick the format your system already knows

Every export is available in four formats with functionally identical content:

• CSV — the workhorse: importable by virtually every system and easy to inspect.
• XLSX — opens straight into Excel, useful when people also review results by hand.
• JSON — the natural format for modern APIs and web applications.
• XML — the standard in many logistics chains and older ERP integrations.

Each scan carries the barcode, timestamp and verification status (expected, unexpected or duplicate), among other fields. Photos can be included as well — embedded in the export or uploaded separately.

Three ways to deliver

The export file is sent automatically over the channel you configure:

1. FTP — still widespread in logistics; the file lands in the agreed folder on your server.
2. SFTP — the same principle, encrypted over SSH. The usual choice when security is a requirement.
3. REST — the file is sent as an HTTP request to your API, for systems that prefer a direct call over a file drop.

File names your system recognises

Import processes on the receiving end often have strict file-name requirements. In ScanVerify you therefore build names from variables such as reference, customer, direction and date — for example ORD12345_CustomerX_outbound_2026-07-24.csv. Invalid characters are cleaned automatically, so an import never chokes on a file name.

Reliable, even when the connection drops

An export must never be lost because the warehouse Wi-Fi blinked. Delivery therefore runs through a background queue: if a transfer fails, the file stays queued and is retried as soon as a connection returns. The app shows the status of every export. More on this in Offline barcode scanning in the warehouse.

Frequently asked questions

Does this work with my specific ERP or WMS?

Almost every system can import CSV, XML, JSON or XLSX, or receive a REST call. If yours reads one of these formats, you can connect it to ScanVerify. In doubt? Get in touch and describe your setup.

Do I have to reconfigure the destination for every order?

No. You store the settings in an export profile and reuse it across all your projects.

Do I need an API or webhook on my side?

Only if you choose REST. For FTP and SFTP, a server with a folder ScanVerify may write to is all it takes.