When integrating orders fulfilled by VTEX sellers, it is important to include tracking codes and invoice data. There are some requirements needed, before connectors can make sure that invoice and tracking code were sent to the marketplace:

• The tracking code and invoice information must be contained within the VTEX Order.
• Connectors should offer a secure endpoint to receive VTEX notification from our Retrieve feed order status endpoint updating tracking code and invoice data
• Tracking code and other data about the order’s delivery will only be made available to orders where the seller is in charge of delivery.

The invoice sent by VTEX consists of a notification for the connector's URL, with the following structure:

http://{{marketplaceServicesEndpoint}}/pub/orders/{{orderId}}/invoice.

If the connector does not take that into account in their integration, they might receive an error 400 in VTEX's Send Invoice requests.

The diagram below describes the notification flow, for integrating tracking code and invoice data:

Follow the steps below to integrate them, once receiving the notification. Make sure to review our Recommendations page before you start.

1. VTEX Orders receive tracking and/or invoice data. This information can be inserted via Invoice notification from VTEX or manually in VTEX Admin. After receiving invoice information, the order status is updated to invoiced in VTEX. In this case, it is not possible to cancel the order anymore.
2. VTEX OMS notifies the connector through the URL informed in the Place Fulfillment Order API by the connector through the property marketplaceServicesEndpoint, once the order is inserted in VTEX.
3. Connector collects information sent through the notification. a. To collect information about invoice, use the properties:
   • invoiceNumer: invoice’s ID code.
   • invoiceUrl: URL that leads to the invoice document.
   • embeddedInvoice: invoice document’s XML file.
   • invoiceValue: value declared in the invoice.
   • invoiceKey: invoice’s key. b. To collect information about tracking code, use the properties:
   • courier: carrier’s name.
   • trackingNumber: number used by the carrier to identify the delivery
   • trackingUrl: carrier’s URL used by clients to track the order’s delivery.
4. Connector transforms the information to the expected format in the marketplace.
5. Connector sends the information to the marketplace.
6. Marketplace validates and records information, and responds with a success or failure status.
7. Connector generates an Order log for each situation.

Note that:

• An order can have more than one invoice with partial values
• The tracking code and/or invoice can be filled in at different moments. In this case it is important to understand the flow demanded by the marketplace for sending separate information.
• Not all fields listed are demanded by the marketplace. Keep in mind to check which ones are in fact mandatory and the correct moment to send them.

Make sure that all steps are logged as either success or failure, to offer the operation's full traceability. Check out the Order logs page to learn more

Use the endpoints described below to perform this step. It is important to note that when consuming this API, the connector must have a valid VTEX App Key and App Token.

All parameters in the endpoints below must be declared in the request. In case one of the parameters does not have a value, you must still send it as null.

Use the request example below to perform the Shopping Cart Simulation. Check out our Shopping cart Simulation API Reference to know more details.

Use the request example below to place fulfillment order. Check out our Place fulfillment order API Reference to know more details.

Use the request example below to authorize dispatch. Check out our Authorize Dispatch API Reference to know more details.