The client (recipient) did not come from Rozetka correctly

If you claim that the problem is on Rosette's side, then "Please send us the full API request (with all correct parameters) that your crm sends to receive the order."

process client search logic: 1. If there is a phone, we take the phone number and look for it in our existing ones 2. If there is an email and did not find a phone, we are looking for it in the existing ones. In your case, they didn’t find it by phone and started searching by email, here is the data that api gives about this: [user] => array ( [id] => xxx [email] => 8pjv8.хххх@gmail.com [login] => 8pjv8.хххх@gmail.com [contact_fio] => xxxx Ilya ) As you can see from them, the outlet said "here is the email of this user." By email, we already found an existing user. If in such cases you do not want to search by email, you can make a setting in action to not search by it. Takes 1h

1. There are two blocks with data in the outlet, this is the block of the recipient (who will receive the package) and the user (who ordered) http://prntscr.com/u60szt TTN needs to be created for the recipient, but this box does not make an order https://baza. cn.ua/admin/customorder/order/20273/edit/ in the order, the full name wrote the data from the block (who will receive the parcel), and the phone was taken from the block (who ordered it) http://prntscr.com/u60xyh well, some kind of nonsense it turns out it stupidly creates TTN full name of one person, phone number of another person, or is it all right? 2. How to make it so that the recipient's data would always come into the order, and not the data from the block (who ordered)? 3. TP Rozetka asks to provide "A complete request to the API (with all correct parameters) that your crm sends to receive an order" can you provide?

1. Disabling search by email should solve this problem. What is needed for this is described above. 2. see point 1 3. This makes no sense, api sockets have nothing to do with it. I described why it finds the wrong user and how it can be fixed, why additionally provide requests to some api and discuss something else?

[quote] Bodyako Dmitry wrote: I described why it finds the wrong user and how it can be fixed, why additionally provide requests to some api and discuss something else? [/quote] 1. I suppose that the outlet has different options for receiving data on the order and maybe they think that there is an error, that's why they want to receive a request to figure it out, can you provide them with such data? 2. If the box found a client by mail, then why didn’t he add the phone number specified in the order to this user (we must get actual data in the order, and not the data that was once entered into the box, or why the box didn’t write down this data in the fields of the order Client's PIB (order.order_clientname) and Client's phone (order.order_clientphone)) ?

?