{"section":"announcements","requestedLocale":"en","requestedSlug":"2019-03-12-now-its-easier-to-sell-the-products-from-your-physical-stores-in","locale":"en","slug":"2019-03-12-now-its-easier-to-sell-the-products-from-your-physical-stores-in","path":"docs/en/announcements/2019/march/2019-03-12-now-its-easier-to-sell-the-products-from-your-physical-stores-in.md","branch":"main","content":"You can now easily sell products from your entire network of physical stores in __external marketplaces__. Through the __Multilevel Omnichannel Inventory__, the [franchise accounts](/en/tutorial/what-are-franchise-account-and-seller-white-label) are fully integrated with the main account immediately after being created. This means that when the main account sets up an integration with an external marketplace, the franchise accounts' inventory will also be considered in the process, ie, it will no longer be necessary to manage each franchise account individually in order to integrate it into the marketplace.\n\n## Main benefits\n\n- Setup of the integration with an external marketplace in one account only, the main one.\n- Omnichannel power in your business; you can use the franchise accounts for pickup points, for example.\n- Simplification of Checkout APIs.\n\n## What you need to do\n\nThe only necessary setting is the integration of the main account with the external marketplace. Once this is done, the inventories of all franchise accounts linked to the main one will also be sent to the marketplace. This is a new franchise account feature, which is active and ready to make your life easier whenever you need to integrate your operation with marketplaces.\n\n> ⚠️ ** For now, automatic integration of the franchise accounts inventory is only available when the marketplace is not a VTEX one**.\n\n## What has changed\n\nThe Multilevel Omnichannel Inventory brought a new ally for omnichannel operations. However, to be used, the store that will be exclusively a __marketplace__ in the order flow (the link closest to the customer), must adjust its __Checkout APIs__ according to the changes below:\n\n- `AffiliateId`, `marketplacePaymentValue`, `marketplaceOrderGroup` and `marketplaceServicesEndpoint` are the 4 new required Checkout PlaceOrder fields. The `paymentData` field is no longer required.\n- New route for progressing the order after marketplace approval (Marketplace Order Authorization).\n- The Marketplace needs to support the new route so it can be notified of a seller (or an intermediate agent) cancellation and to receive the invoice from the seller (or the intermediate agent).\n\nTo learn more about Multilevel Omnichannel Inventory and changes to the Checkout APIs, visit [this Help article](/en/docs/tutorials/multilevel-omnichannel-inventory).\n\n> ❗
  • The Recursive Marketplace is now called **Multilevel Omnichannel Inventory.**
  • The feature does not allow you to [change seller.](/en/docs/tutorials/change-seller)
  • This solution is aimed at integrating with external marketplaces, not those that are [natively integrated with VTEX.](/en/docs/tutorials/marketplace-strategies-at-vtex).
  • Learn more about usage restrictions in the article [Multilevel Omnichannel Inventory](/en/docs/tutorials/multilevel-omnichannel-inventory) e confira as restrições de uso detalhadamente.
    • "}