This topic aims to foster knowledge of the Marketplaces and integrations module of the VTEX platform, given that order integration errors can be frequent and common among many of our merchants.
With that in mind, the first step is to check the bridge to see whether the orders appear there with any integration error.
But what is the bridge?
The bridge is simply the Connections section, found inside the 
Marketplaces module, where you can check each order and its status — whether it was “Successfully processed” or “Processed with error”:
Why do we call this module the bridge?
Basically because of its URL, and because it acts as the bridge between integrations and VTEX:
https://{{account}}.myvtex.com/admin/bridge/#/marketplace/order
How do you investigate cases of orders not integrated due to SLA errors?
For orders with the status “Processed with error” where the error description is tied to SLA issues, we have an investigation procedure that can help resolve the error:
First, it’s worth noting that we have a Help Center article that explains this situation:
Based on the documentation above, we can outline a step-by-step guide for investigating these types of cases.
- One very useful option is to run a Shipping Simulation for the integration’s Trade Policy, the order’s SKUs and postal code, at the following link:
https://{{account}}.myvtex.com/admin/logistics/#/freight-simulation
In most cases, the Shipping Simulation alone is enough to diagnose what is causing the order integration error, but if it isn’t sufficient, there are other checks you can perform.
- Check whether there is inventory for the item in the order (the Shipping Simulation usually returns this information already). To do this, simply search for the SKU in the catalog module and click the
icon:
- After that, it’s important to check whether the available inventory for the SKU matches the stock registered in the Dock of the integration’s Trade Policy. In practice, this means you need to verify that the available inventory for the SKU in question is linked to a Dock capable of serving the Trade Policy used in the integration with the relevant Marketplace:
Inventory:
Stock:
Dock:
It’s worth noting that after making any changes, you need to go back to the bridge and “Reprocess” the order:
Possible Questions:
My order has an SLA integration error, but it’s of the FOB type and/or uses the partner’s own delivery service.
This happens because even if your delivery is of the FOB type or is carried out by the partner, the order still needs to return some delivery SLA within the platform. This is because whenever the integration identifies a new order in the marketplace that needs to be integrated into the store, it runs a fulfillment simulation to select the order’s SLA before actually creating the order. At that point, if the simulation returns that the SKU has no stock, is unavailable, or that there is no SLA available for that item at that postal code, the order will not be created in the store and the integration will show an SLA error in the bridge.
If you still have any questions about this topic, feel free to ask right here! 