Skip to main content

SFTP vs API

Written by Nicolas Beal
Updated over 3 weeks ago

Connection between STS (SAM’URAI) and the Customer ERP

⚠️ Important prerequisite

  • The API is not yet available as of today; however, the SFTP is fully operational. The API is expected to be available soon.

  • In both cases (SFTP or API), the involvement of a technical contact from the customer’s IT department is mandatory. These topics are technical and require the participation of the customer’s IT team for configuration, security, testing, and deployment.


1️⃣ Context

Within our SAM’URAI storage solution range:

  • STM = software embedded in the machine (user interface screen)

  • STS = supervision software (centralization, rights management, inventory, reporting)

  • Customer ERP = the customer's management system (SAP, Oracle, Sage, etc.)

More and more customers request a connection between STS and their ERP in order to automate:

  • Stock movements

  • Consumptions

  • Users

  • C&C orders

  • etc.

Two main technical solutions exist: SFTP or API.


2️⃣ SFTP: file exchange

🔹 Simple definition

SFTP (Secure File Transfer Protocol) is a system for exchanging files deposited on a secure server.

👉 A file is deposited → The other system retrieves it → It processes it.


🔹 Operation in our context

Example:

  1. The STS generates a CSV file (for example for a consumption report)

  2. It deposits this file on an SFTP server

  3. The customer ERP retrieves the file every X minutes/hours

  4. The ERP imports the data

Conversely:

  • The ERP can deposit a file containing users, articles, etc.

  • The STS retrieves it and integrates it


🔹 Characteristics

Criteria

SFTP

Exchange type

Files

Real time

❌ No (delayed processing)

Complexity

Easy to implement

Traceability

Files can be archived

Customer IT dependency

Low to medium (light script required)


3️⃣ API: real-time communication

🔹 Simple definition

An API (Application Programming Interface) allows two software systems to communicate directly with each other in real time.

👉 The STS sends a request → The ERP responds immediately.


🔹 Operation in our context

Example:

  1. An operator takes an item from a SAM’URAI machine.

  2. The STM sends the information to the STS.

  3. The STS calls the ERP API.

  4. The ERP immediately records the stock output.

Or conversely:

  • The ERP directly sends the creation of a user to the STS.

  • The STS integrates it instantly.


🔹 Characteristics

Criteria

API

Exchange type

Direct requests

Real time

✅ Yes

Complexity

More technical

Maintenance

API version management

Traceability

System logs

Customer IT dependency

High


🔹 Advantages

✔️ Real-time communication
✔️ Immediate synchronization
✔️ Fewer files to manage
✔️ Advanced automation


🔹 Disadvantages

❌ More complex implementation
❌ Highly dependent on the customer IT system
❌ Requires advanced security (authentication, tokens, etc.)
❌ More technical maintenance


4️⃣ Summary comparison

SFTP

API

Communication mode

File exchange

Direct communication

Real time

Complexity

Medium

High

Robustness

Very stable

Depends on infrastructure

Ideal for

Customers with simple IT

Large groups / many internal changes

Data volume

Batch

Continuous


5️⃣ When to propose which solution?

👉 SFTP recommended if:

  • The customer has an older ERP

  • The IT department is limited

  • The need is not real-time

  • Data exchanges are daily / hourly

  • A quick project implementation is required


👉 API recommended if:

  • The customer requires real-time operations

  • Inventory must be synchronized immediately

  • Industry 4.0 project

  • Advanced integration (dynamic cost centers, real-time validation)

  • Modern ERP (SAP S/4HANA, Oracle Cloud, etc.)


📌 Current features available via SFTP

🔄 Flow ERP → SFTP → STS

The customer deposits a file on the SFTP server, which is then integrated by the STS.

What we can do today:

STM user updates

  • User creation

  • Modification of user information (name, surname, badge, etc.)

Product / article updates

  • Creation of new articles

  • Modification of existing articles

  • Update of references, descriptions, categories, etc.


🔄 Flow STS → SFTP → ERP

The STS generates files deposited on the SFTP server, which the ERP retrieves.

What we can export today:

Export of all reports available in the STS, including:

  • Stock movements

  • Inventory status

  • (and any other report generated by the STS)

Did this answer your question?