This article aims to describe the integration flow between VTEX and Carrefour. By explaining how it works, it will become easier to understand the expected behavior of each step:

1. Products
2. Inventory
3. Price
4. Benefits
5. Order

Products are sent automatically, aproximately 8 hours after the integration setup has been successfully completed. For this, it is based on the registered sales policy and sends the first package of products.

Product and SKU fields are sent together in a separate batch from the offers one (which gathers SKU inventory and price information). Both batches can be uploaded at the same time - Carrefour will validate them.

For products to be displayed in Carrefour, the integration sends the following product and SKU fields:

Product	SKU
Name*	Name*
Description*	EAN*
Brand (depending on the choice in the integration setting, the information will be added in the product title)	Weight*
Specifications	Height*
-	Width*
-	Length*
-	Images*
-	Specifications

Caption: * Required fields.

Carrefour does not accept products with variations (more than one SKU).

Since batches of products and offers are sent successfully and validated by Carrefour, all variations/SKUs of the same product are displayed together in the same group.

Ex: Blue Shirt (product) | S, M, L (variations/SKUs)

With all products correctly processed and cataloged by Carrefour, offers can have the following statuses:

• Active: available for sale;
• Inactive: unavailable for sale (when the product runs out of inventory), but it still appears in the search results.

When sent successfully for the first time, the products undergo an internal cataloging process inside Carrefour. If that goes well, integration does not update product information: this would undo the ones that have already been registered.

For example, if the product description is changed, the integration will not update it in the marketplace. To make a change, you will need to contact Carrefour directly.

NOTE: a product can not be deleted in the Carrefour panel. If this happens, the integration will not be able to send it again.

When a product is sent for the first time, the inventory is sent as well. However, it is discarded by Carrefour, as they only accept inventories for products already cataloged. This policy exists so that the inventory available in the marketplace is always the most up-to-date.

However, when cataloging is complete, Carrefour does not notify VTEX. This means that our integration has no way of knowing when you can send inventories again, becoming dependent on updates made directly to the Inventory & shipping (VTEX module). As soon as Carrefour confirms the cataloging of your products, the marketplace will ask VTEX to send the inventories. But you can force this information to be sent by simply changing any stock in each of your SKUs.

Once products receive the first inveentory load, the update is made SKU by SKU whenever the inventory undergoes some change inside VTEX. This update is sent in batches every 6 minutes, which means the integration gathers all the updates from your store during 6 minutes and then sends everything at once. If the inventory update is taking longer than expected, there is probably a lot of information in queue to be updated.

When a product is first sent, the price is sent as well. However, it is discarded by Carrefour, as they only accept prices of products that have already been cataloged. This policy exists so that the price available in the marketplace is always the most up-to-date.

However, Carrefour does not notify VTEX when everything has been approved. This means that our integration has no way of knowing when it's possible to send prices again, becoming dependent on updates made directly into VTEX Prices module. As soon as Carrefour confirms the cataloging of your products, the marketplace will ask VTEX to send the prices. But you can force this information by simply making price changes on each of your SKUs.

Once products receive the first price load, the upgrade is made SKU by SKU whenever prices undergo any changes inside VTEX. This update is sent in batches every 6 minutes, which means the integration gathers all the updates from your store during 6 minutes and then sends everything at once. If the price update is taking longer than expected, there is probably a lot of information in queue to be updated.

Note that for prices with expiration date the system does not notify affiliates when the date expires. Thus, the base price will only be sent at the next price load.

For each SKU, the integration sends only the final price, based on the response of the fulfillment simulation. In a standard scenario, the price sent will always be determined considering the sales policy associated with the integration. However, there are factors that can influence the final price, such as benefits and fixed prices.

Example 1: A promotion that offers a 10% discount for a certain category.

Example 2: In the sales policy used in Carrefour, an SKU is priced at $ 10 with a fixed price of $ 15. The value that the integration sends to the marketplace is $ 15.

Attention: As the payment method is given in the marketplace, payment rules are also determined by it. Because of this, the integration can not send differentiated prices according to the payment method.

Ex: If the interest rate for installment payments is configured in VTEX, the price that is sent will still be the one that was returned by the fulfillment simulation.

Unlike a benefit used for your store's website, a marketplace benefit only discounts the value of the product, but without indicating that it is a benefit. That is, the price sent is already modified and there is no benefit tag.

The integration between VTEX and Carrefour only applies benefits that can be calculated in the fulfillment simulation. In these cases, the following conditions apply:

Discount Type	Items	Conditions
Percentage	Categories	Min/max Order value
Nominal	Brands	Min/max Item value
Nominal Shipping	Collections	Price from/for
Percentage Shipping	Products	Zip Code
Maximum Shipping	-	Type of Shipping
Free Shipping	-	-

Order details are directly influenced by factors such as delivery, price and availability.

Shipping

At the time of ordering, Carrefour querries the shipping table registered in VTEX. Our platform returns to them the available shipping options, according to the mapping informed in the integration settings. It's important to keep in mind that the query is only possible if the Shipping API is registered in the Carrefour panel.

If none of the fields in the mapping is filled correctly, it will not be possible to simulate shipping in VTEX. With this, orders placed on Carrefour will not be integrated.

If the Shipping API is not registered, Carrefour will use a contingency table to do the calculation. In this case, Carrefour sends the order information and the integration tries to make a match of the shipping calculated with the carrier that best fits within VTEX (we use the type of carrier as a parameter). If there is no match, there will be an error in the order integration. To solve this, you will need to do the shipping mapping first and then reprocess the order.

Price/Availability:

At the time the order is made, Carrefour does not check in real time the product's price or inventory availability in VTEX. The marketplace considers only the latest information sent about price and inventory.

Orders placed at Carrefour have their own statuses. In the table below you will find an explanation of each of them and the correspondence with the order status in VTEX.

Status in VTEX	Status in Carrefour	Carrefour status description
Waiting authorization to ship	STAGING	New order for which payment has not yet been approved
Grade for cancellation / Ready for Handling / Preparing Delivery	SHIPPING	Payment Approved
Invoiced	SHIPPED / CLOSED	Invoice issued
Invoiced	SHIPPED / CLOSED	Order shipped
Invoiced	No Status	Order delivered
Canceled	Canceled	Order canceled

VTEX reads the Carrefour order feed and integrates those that have Staging status in the marketplace. Orders that have any other status are not integrated and do not appear in the order integration logs (Integrations section in VTEX Admin).

During this process, the order may not be integrated for some reason. You can check what went wrong by clicking Orders, which is below the Integrations item in the Marketplace section of the Admin side menu. To solve the problem, find out what should be done for each of the main order integration errors in Carrefour and take the necessary action. After everything is OK, just reprocess the order.

After the integration takes place, orders continue to be treated with the same ID used in Carrefour.

Orders with some kind of incident are not integrated. If the incident happens after the order is integrated, a warning will be displayed on the Tracking tab in VTEX Admin.

Once the order has been successfully integrated, you can interact with it both through VTEX Admin and through the Carrefour admin panel. However, some actions may or may not be applied on both sides.

Actions that are reflected on both VTEX and Carrefour:

• Cancellation of order in Carrefour (integration alto cancels it in VTEX);
• Order invoiced in VTEX (the integration invoices and updates the order status in Carrefour, as explained below in item D).

Actions that are not reflected on both platforms:

• Cancellation of order in VTEX (the integration can not cancel it in Carrefour as well);
• Order invoiced in Carrefour (the integration can not invoice it in VTEX as well).

When an order that came from Carrefour is invoiced in VTEX, the integration upgrades the status in the marketplace to Shipped, and finally includes a field that corresponds to order delivered. But for that to happen, specific fields need to be filled. You can see more details about filling them in our ERP Integration Guide.

1- To change the status to Shipped, you will need: invoiceKey, invoiceNumber, trackingUrl, trackingNumber, courier, issuanceDate.

2- To change the order with the information delivered to the customer, you will need: courierStatus: this field can be populated automatically (via tracking updates in the carriers themselves) or manually, via API or the Orders interface (formerly Orders Management). When the field returns finished=true, the integration sends the information to the marketplace. If the field returns finished=false, the order will not be changed with the delivery information.