{"section":"known-issues","requestedLocale":"en","requestedSlug":"seller-name-is-not-provided-in-native-mkp-integrations","locale":"en","slug":"seller-name-is-not-provided-in-native-mkp-integrations","path":"docs/en/known-issues/Channels/seller-name-is-not-provided-in-native-mkp-integrations.md","branch":"main","content":"## Summary\n\nWhen downloading the orders that are sold by the store, the field *\"sellers\"* is displayed with the fields *\"Id\"* and *\"Name\"* filled out. For example: *sellers: [\\{id: \"1\", name: \"mitienda\", logo: \"\"\\}]*\n\nBut in the orders integrated by MercadoLibre only the *\"Id\"* of the seller is diplayed, since the *\"Name\"* field comes back null: *sellers: [\\{id: \"1\", name: null, logo: null\\}]*\n\nWith the implementation of multiple sellers for vendors engaged in dropshipping, it is necessary to handle logistics for each individual seller. To identify each one, you can use the field *\"Name\"* to make it more user friendly, but this value is not provided when it originates from, for example, an order downloaded from MercadoLibre.\n\n## Simulation\n\n1. Download an order from the store with the GetOrder API and it will show that the *Name* value is filled out. For example: *sellers: [\\{id: \"1\", name: \"mitienda\", logo: \"\"\\}]*\n2. Download a MercadoLibre order with the GetOrder API and it will show that the *Name* value is not filld out and the value is null. For example: *sellers: [\\{id: \"1\", name: null, logo: \"\"\\}]*\n\n## Workaround\n\nYou can identify each seller by ID and then display the user-friendly name you want in the integration of the internal side."}