Importing received orders into the warehouse system is a key process for efficient logistics, inventory tracking, and automated invoicing. Properly configured integration between Fynode and your warehouse solution ensures a smooth transfer of orders from the e-shop to the warehouse without the need for manual intervention.
¶ 1. Supported warehouse systems and import options
- Not all warehouse systems support the import of received orders!
- Supported import systems include, for example: ONIX, Money S3, mPohoda, MK-Soft, Oberon, Pohoda mServer, and others.
- Import works either:
- Automatically (at set intervals, e.g., every 30 minutes)
- Manually (by starting the process directly in Fynode interface or in the warehouse system)
An overview of import options can always be found in the specific warehouse system's guide in this Wiki section.
- After an order is received in Fynode, the record is immediately added to the export queue.
- At regular intervals (or manually), new orders are transferred to the warehouse via:
- FTP/SFTP exchange of data files (e.g., Money S3, Oberon, MK-Soft, ONIX)
- Direct API connection (e.g., Pohoda mServer, Abra Flexi, mPohoda)
- Orders are recorded on the warehouse side/in the warehouse application as new received orders/documents/receipts (depending on the system).
- In several warehouse systems, you need to set the document type into which orders are imported (e.g., "received order", "RO", ...).
- In the Fynode admin panel, go to the Warehouse section and select the warehouse system.
- Verify and fill in the correct details according to the guide (FTP, API key, database path, etc.).
- Check the option/element "Import received orders" and activate it if supported by the system.
- For some solutions (e.g., Money S3), you also specify the exact name/destination of the import file (e.g.,
{ID}.xml, special folder on FTP, etc.).
¶ 4. Processing and workflow after import
- After importing orders into the warehouse, additional workflows can automatically run:
- Creating a receipt or warehouse order
- Reserving goods or changing inventory status
- Automatic calculation and issuance of invoice based on the order
- Integration with shipping or delivery
In large warehouses, it is advisable to set up notifications/logging to monitor import success and error management.
¶ 5. Common errors and recommendations
- Orders are not importing: Check connection (FTP/API), access credentials, and existence/writing permissions to the target directory/database.
- Duplicate or missing document: Check pairing settings, document type, or import cycles (whether the file is overwritten/lost).
- Incorrect item status after import: Verify correctness of product numbers/EANs and mapping to inventory cards.
- Order is in a special state: Each system may have its own rules, so set up state conversion/transformation as needed (e.g., "new" = "received", "confirmed", etc.).
- Always test import processing with test orders before going live.
- Regularly review logs and import reports, and analyze errors.
- Ensure correct product pairing (by number/EAN) so each order is properly accounted for and does not cause warehouse errors.
- When migrating or transferring data, back up the current warehouse state and test import with a smaller dataset.
Importing orders directly into the warehouse allows you to speed up dispatch, minimize errors, and gain a perfect overview of stock and movements in real-time.