Four headings: bringing it in, mapping it, protecting it and publishing it out.
Import
Enter the address, map the fields and rehearse without writing. You start the real import after reading the report.
Connecting a supplier feed
You connect the supplier’s product feed and map their fields to yours once. Later updates run on that same mapping.
Mapping
The supplier says “urun_adi” and you have “Product Name”. You set the mapping once, and category and brand equivalents are defined on the same screen.
Field mapping
The supplier says "urun_adi", you say "Product Name" — you set the mapping once. Category and brand equivalents are defined on the same screen.
Protection
If the product count drops unexpectedly, required fields are widely missing or category matching does not hold, the import stops and tells you why.
Thresholds that protect the catalogue
A broken supplier file cannot wipe your catalogue. The import stops itself and tells you why; you fix it and run again.
Outgoing feed
You can publish your products as XML. The other side points at a fixed address and takes the current list; you are not preparing and sending a file each time.
Feeding outwards
You can also publish your catalogue as XML. The other side points at an address and takes the current list; you are not preparing and sending a file each time.
Once a catalogue has been wrecked, nobody trusts automation again.
A broken file wipes everything
One incomplete feed deactivates hundreds of products.
Field names never match
Every supplier uses their own naming.
There is no way to rehearse
The import either works or it has already damaged the data.
Rehearse first, read the report, then run it.
SU Customer Representative
Hello, I am SU. I am here to help — you can ask me anything.
You are chatting with SU
During working hours we usually reply within a few minutes.
Hello! Write your question and our team will answer here.
Your cookie preference
We use cookies that are strictly necessary for the site to work. Analytics and marketing cookies are only enabled if you agree. See our Cookie Policy and Privacy Policy.
