Less manual copying
Enhanced titles, descriptions, and product features do not need to be copied product by product.
From source to Nifelo and back
Improve product data in Nifelo. Bring the result back to your source system.
Product source
Route AFile or feedCSV · XML · JSON · custom export
Route BWebshop linkProducts and variants
NifeloSmartFieldsPairing
Analyze
Improve Start export
Analyze
Improve Start export
Export from Nifelo
Route AExport file or feedImport this output back into your source system
Route BConnector updateNifelo sends the changes back to your webshop
Improved product data is returned via a supported link or export
Import product data from a file, feed or link. Nifelo brings the data together in SmartFields, checks and improves it and then makes the improved product data available again for your source system.
Via a supported connector or a new export for your source system.
Why a round trip?
Prevent your source system from lagging behind improvements in Nifelo
Product data is supplemented, improved and made more consistent in Nifelo. Without feedback, those improvements only remain in Nifelo. With a round trip you also bring the relevant results back to the system in which your products are managed.
Improvements back to your source system
Make improved product information from Nifelo also available for the system in which your products are managed.
Fewer transfer errors
By exporting enhanced fields or updating them via a link, you reduce the chance of errors due to manual copying.
From input to updated source
This is how Round Trip works
The exact return route depends on your source. The processing in Nifelo remains the same: import, structure, improve and make the desired data available again.
Import your product data
Read products from a file, feed or supported link.
Let Nifelo process the data
Link source fields to SmartFields and let Nifelo analyze, normalize and, where set, enrich the data.
Create the desired output
With a file export, you determine which product fields you want to export. With a supported connection, Nifelo determines which supported data can be returned to the platform.
Update the source system
Send data back through a supported connector or re-import the export file into the source system.
Two return routes
Update directly or bring back a new export
Nifelo can close the loop in several ways. Which route you use depends on how your source system can receive product data.
Via a supported link
With supported Shopify and WooCommerce connections, Nifelo can send selected product data directly back to the webshop.
Via a file or feed
If you work with a file or feed, Nifelo will create an export with the improved data. You can then re-import that export into the source system.
Bring back improvements
Example: update product texts while price and stock remain the same
Price and stock have not been adjusted by Nifelo in this example and therefore still have the same value as in the source system. The improved title and description do differ and may be updated during the round trip.
Product fieldValue from the sourceValue in NifeloResult
TitleLinen shirtLinen shirt – breathable and lightweight Being updated
DescriptionShort textLightweight linen shirt with a breathable finish. Being updated
Price€ 79,95€ 79,95 Remains the same
Stock1818 Remains the same
If you work with a file export, you can also create your own mapping with only the required fields, for example ID, title and description. If you use a channel template, additional mandatory fields may apply to that format.
Frequently asked questions
Good to know about Round Trip
What does round trip mean for product data?
Product data is imported from a source into Nifelo, processed and improved there and then made available again for the original source system. This can be done directly via a supported connector or via an export that you re-import.
Can each source be updated directly?
No. Direct update is only available for supported and properly configured links. For other sources, you create a file or feed with the improved product data and import it back into the source system.
Are all product fields returned?
Not automatically. With a file export, you decide which product fields are included. For a supported link, only data that is supported by that link and relevant to the update is returned.
Can I only return the product data that has been improved in Nifelo?
With a file export, you decide which product fields you include. For example, you can only export ID, title and description and leave price or stock out of the export. For direct links, the available selection depends on the supported fields of the connector.
Will price and stock remain unchanged?
If price and stock have not been adjusted in Nifelo, they still have the same value as in the source system. With a file export you can also choose whether you include these fields at all. If price or stock are deliberately changed and supported by the chosen route, they can be updated.
Do I have to approve changes first?
That depends on the chosen return route. With a file export, you determine in advance which fields you export and you can check the file before importing it into your source system. With a direct connection, the control and mounting options differ per connector.
What file formats can I use for the return?
Nifelo supports export configurations for CSV, XML and JSON, among others. Which format you import back depends on what your source system accepts.
Don't keep improvements just in Nifelo
Bring better product data back to where your products are managed
Use a supported connector or create an export with the exact product fields you want to update in the source system.
