Real request, clear flow: Automatically import CHECK24 orders into Billbee

The Request

A merchant wants to connect Billbee with CHECK24 and automatically import only orders from CHECK24 into Billbee.

The central question is: Can this process be implemented with Synesty and which interface is required on the CHECK24 side – API, FTP or CSV? In addition, the merchant wants to know which specific Steps and Flows are required for the implementation, whether there is already a standard template for the order import and how complex the mapping of the CHECK24 order data to the Billbee structure is in practice.

The Problem

In this use case, not only a single order import is to be implemented. The merchant wants to map a complete process: New CHECK24 orders are to be retrieved via the provided FTP access, created as orders in Billbee and, after shipping processing, reported back to CHECK24.

The challenge therefore lies in three points:

1. CHECK24 order data must be retrieved securely and regularly via FTP and processed in the provided format, for example XML or CSV.
2. The order data must be correctly mapped to the Billbee structure. This includes order number, customer data, addresses, item positions, prices, shipping costs and payment information. At the same time, mandatory fields must be checked and duplicate imports must be avoided.
3. After shipping, the tracking information must be read from Billbee, assigned to the original CHECK24 order and reported back to CHECK24 in the appropriate format.

The Result

This means the use case consists of two automated subprocesses:

1. The order import from CHECK24 to Billbee
2. Shipping notification from Billbee back to CHECK24

Data flow 1: Order import from CHECK24 to Billbee

CHECK24 → Synesty → Billbee
New CHECK24 orders are retrieved via the provided FTP access and read into Synesty. There, the order data is processed, mapped to the Billbee structure, checked and then created as an order in Billbee. This turns the manual import into an automated order flow from CHECK24 to Billbee.

Data flow 2: Shipping notification from Billbee to CHECK24

Billbee → Synesty → CHECK24
After shipping processing in Billbee, the relevant shipping information, for example tracking number and shipping service provider, is retrieved from Billbee. Synesty assigns this information to the original CHECK24 order and then reports it back to CHECK24. This also automatically returns the downstream shipping status.

Overall result

The merchant does not receive an isolated import, but an end-to-end order and shipping data process:
CHECK24 → Synesty → Billbee → Synesty → CHECK24
Synesty handles the processing between the systems: retrieval, reading, mapping, validation, creation in Billbee, retrieval of shipping data and feedback to CHECK24.

Proof

1.Subprocess: CHECK24 → Synesty → Billbee

The first data flow CHECK24 to Synesty to Billbee can be built with existing Synesty templates. Two templates are combined with each other and adapted to the specific process. The template CHECK24 - Import orders forms the basis for the CHECK24 part of the Flow. It shows how order data from CHECK24 can be read in openTRANS XML format and prepared for further processing.

For the specific Use Case, the following Steps are especially relevant from this:

FTPDownload
Retrieve order files from the CHECK24 FTP

Check24ReadOrders
Read CHECK24 orders in openTRANS XML format

Mapper
Prepare CHECK24 order data for further processing

The second part of the Flow is based on the template billbee Add Orders. This template shows how prepared order data can be created in Billbee. The relevant Steps of this template can be adopted into the existing CHECK24 Flow and reused there.

For the specific Use Case, the following Steps from the Billbee template are especially important:

Filter
Pass on only valid and complete orders

Mapper – prepare HEAD
Prepare header data for Billbee

DatastoreWriter – header data
Store order header data

DatastoreWriter – position data
Store item positions

billbeeAddOrders
Create order in Billbee

The two templates therefore already provide important building blocks for the process. However, they do not yet form a finished Flow for exactly this scenario. For the specific implementation, the Steps must be individually combined and adapted. This means: The CHECK24 part reads the order data and prepares it. The relevant Billbee Steps are then integrated into this Flow so that suitable header and position data for Billbee are created from the CHECK24 data and the order can be created via billbeeAddOrders.

This creates an adapted process Flow from two existing templates:
Retrieve CHECK24 FTP → read openTRANS orders → map data → filter valid orders → prepare Billbee header data and position data → create order in Billbee
The proof therefore lies in the combination of existing templates and individual adaptation. The technical building blocks already exist, but they must be suitably assembled, mapped and checked for the specific CHECK24-to-Billbee process.

2. Subprocess: Billbee → Synesty → CHECK24

After shipping processing in Billbee, Synesty retrieves the relevant shipping information, for example tracking number and shipping service provider. This information is then assigned to the original CHECK24 order and returned to CHECK24. An additional Flow is built individually for this feedback Flow. This supplements the two templates, because the feedback of the shipping information is a separate process step after the order import.

Possible Steps for this feedback Flow are:

billbeeGetOrders
retrieve shipped orders from Billbee

Filter
select only relevant CHECK24 orders with shipping data

Mapper
assign tracking number, shipping service provider and CHECK24 order reference

CSVWriter or TextWriter
generate feedback file in the required format

FTPUpload
report shipping status and shipment number back to CHECK24

DatastoreWriter
store feedback status

This creates the second continuous data flow:
Retrieve Billbee shipping data → assign tracking information → generate feedback to CHECK24 → report shipping status back

Conclusion:

The proof of feasibility therefore lies in the combination of existing templates and supplementary Flow Steps. The template CHECK24 - Import orders provides the basis for importing the CHECK24 orders. The template billbee Add Orders provides the basis for creating the orders in Billbee. The additional feedback Flow supplements the process by transferring the shipping information back to CHECK24. This creates a complete process with two continuous data flows:

Order import: CHECK24 → Synesty → Billbee
Shipping notification: Billbee → Synesty → CHECK24

This means the Use Case is not only theoretically possible, but can be implemented in practice with existing Synesty templates, concrete Steps and individual mapping logic.