Catalog logs

StatusDescription
SuccessOccurs when the exchange of messages between VTEX, connector and marketplace flow successfully.
ErrorOccurs when the exchange of messages between VTEX, connector and marketplace present errors due to communication (500) or business errors (400). Recommendations: for 500 errors, it is highly recommended to use the contingency flow through the reprocessing queue with at least 10 attempts. After the attempt number is exceeded, we recommend using a DEADLETTER queue for infinite retrials.
AlertOccurs when the exchange of messages between VTEX, connector and marketplace are able to process, but with a needed action from one of the systems involved.
PendingOccurs when the exchange of messages between VTEX, connector and marketplace are in progress. Ex. SKUs are still in the connector’s processing queue, or waiting an async response from the marketplace.

Log endpoints

Connectors must offer an endpoint that allows the integration app to collect and present logs in the standard report screen. The endpoint should follow the format:

{urlBase}/{vtexaccount}/logs/

For this endpoint the parameters date and status should be included, following the status described in the Log messages table:

https://{urlBase}/logs/?DateAt=aaaa-mm-dd&status=all https://{urlBase}/logs/?DateAt=aaaa-mm-dd&status=sucess,error

The endpoint should return the payload described below, so the list of error messages can be assembled:

{ 
"Messages":[ 
   { 
"id": "13", 
"Operation": "", 
"Direction": "", 
"ContentSource": "", 
"ContentTransalted": "", 
"ContentDestination": "", 
"BusinessMessage": "", 
"Status": "", 
       }
    ]
 }

Content of the messages

The messages contained in logs should follow the standard defined below, allowing the user who operates VTEX platform and catalog to understand the situation:

  1. Operation ID (id): allows to identify the unique log in any sort of operation.
  2. Operation: identifies if an operation is a Catalog change, Offer creation, Price update, Inventory update, Order status update, Invoice sending, Tracking code sending.
  3. Direction: allows to identify the origin and destination of the information. Ex. VTEX to Marketplace.
  4. Content Source: payload sent by the origin solution. Ex. Order’s json, connected from the marketplace, allowing to identify the original message sent by the origin app.
  5. Content Translated: message generated by the connector with transformations, filers and enrichments needed, allowing sellers to understand the actions executed.
  6. Content destination: original payload sent by the destination software after processing trial.
  7. Business message: in case of errors, message explaining the error under the business contexto, with guidance on how to solve the problem.
  8. Status: should include the statuses of success, error, warning and pending.

Log messages

Each step of the catalog integration requires a specific set of Log messages. The list below points out which messages to use for each step, and the table describes all messages.

CodeEventUser messageError statusResponse
S1When sending the SKU registration to the marketplaceThe SKU (VTEXId + name) was created in the marketplace with the code (marketplace ID). Link for the SKU within the marketplace.Success201
A1When using the shopping cart simulation through the fulfillment API, the SKU is not retrieved in the items objectOops, we couldn’t obtain the SKU price of (SKU_Id). Please check if the items below are configured correctly in the VTEX platform.
On product registration, check if it is associated with the trade policy.
On inventory simulation, check if the carrier attending the SKU exists.
On price configuration, check if there’s a price associated with the trade policy.
Warning400
A2When checking if the SKU is inactiveOops, the SKU is inactive in VTEX. We recommend that you check:
In Catalog, identify the SKU and check if the field “Activate SKU” is checked.
In Catalog, check if the image is uploaded.
In inventory simulation, check if the carrier attending the SKU exists.
On price configuration, check if there’s a price associated with the trade policy.
Warning400
A3When transforming the SKU’s registration data AND having to insert a standard value since VTEX doesn’t possess it.Oops, we couldn’t find the values needed for product registration, with standard values accepted by the marketplace. {list containing FIELD and VALUE attributed}Warning200
E1When transforming SKU registration data to the format demanded by the marketplace.Oops, we couldn't prepare the SKU registration in the marketplace due to {list all errors occurred during data transformation, and in case any data infringes marketplace rules}.
(Connectors should list all errors at once, so the user knows all actions needed to send the SKU).
Error400
E2When trying to communicate with the marketplace API used to register the productOops, the product registration in the {name} marketplace is unavailable right now. Don’t worry - we’ll try again in a few minutes. In case the problem persists, get in touch with the marketplace.Error500
E3When sending the product registration to the marketplace, and obtaining failure for sending incorrect data.Oops, we couldn't prepare the SKU registration in the marketplace due to {list all errors occurred during data transformation, and in case any data infringes marketplace rules}.
(Connectors should list all errors at once, so the user knows all actions needed to send the SKU).
Error400
E4When trying to collect the category or attribute mapping from the mapper.Oops, we couldn’t find the category {name of the category} mapping of the {SKU name + ID} SKU in the marketplace. Please access the link below to perform this mapping. {Link indicating the store’s mapper}.Error400
E5When trying to communicate with the mapping API from the mapper.OOps, the VTEX category mapping is unavailable right now. Don’t worry - we’ll try again in a few minutes. In case the problem persists, get in touch with the marketplace.Error500

📘

Connector documentation

The table above should be a part of the connector’s documentation. During the development and testing of the integration, if any other error scenarios are identified, and are not already mapped in this table, connectors should add it in their own documentation.


Did this page help you?