The Offer Management module has been discontinued and is no longer supported. The module has been replaced by Offer Status. To learn more, visit the announcement.

The Offer Management allows sellers to track the sending and syncing of their offers in marketplaces integrated with their store. The feature helps sellers identify updates and solve errors in their offers during the sending process, guaranteeing they were sent to the marketplace and synced correctly. In VTEX, an offer is an SKU from a seller that has been sent to a marketplace and whose price and inventory information have been configured.

The current document is a Software Development Kit (SDK) created to facilitate the integration between a connector and Offer Management. The SDK includes the implementation of Offer Management’s main features and a .NET library via MyGet.

The integration using this SDK follows the same concepts presented in the Offer Management Integration Guide:

Concept	Description
Feed	The feedId attribute created by the connector will identify sellers’ feeds with a channel.
Interaction	For every action that happens to an offer, whether it is a status notification or a price update, the connector creates an interaction about it.
Logs	Logs are the granular details of actions that happen within an interaction, and they are organized in a timeline. Logs registers last for ten days.

Offer Management works with the creation of a feed, followed by the creation of interactions and logs. After the log is created, it is necessary to close the interaction, and that process is what makes an offer update visible for sellers in Offer Management’s UI.

These SDK is organized in the following sections:

1. Installing dependencies
2. Offer Management APIs
3. Unified contract
4. Integration flows

Step 1 - Open the terminal and add the package to the project dependencies:

Step 2 - Inject dependencies in the project:

All of the APIs responses are contained in the object SentOffersResponse, which can be used to check if a transaction was successful or presented an error. All errors are listed in the errors attribute.

This section is organized as below:

• Installing dependencies
• Offer Management APIs
  • Authentication
  • Create feed
  • Deactivate feed
  • Create interaction
  • Create log
• Unified contract
• Integration flows
  • Catalog integration
  • Price update
  • Inventory update
  • Integration errors

This SDK does not reference all the APIs related to Offer Management, however, they can be found in VTEX API Reference under Marketplace APIs > Offer Management.

Authentication in Offer Management works as in VTEX REST APIs, as it can be seen in Authentication. Through the SentOffersCredentials class, the connector can send information about AppKey, AppToken and VTEX IO token.

The creation of a feed establishes the connection between the seller's affiliate ID and the marketplace’s ID, which corresponds to the attribute Id (also referred to as feedId).

When a feed is deactivated, all data related to the marketplace is removed from Offer Management’s UI, including channels, offers, interactions, and errors. Deactivating a feed does not mean deleting information, and the seller can restore the data through the endpoint Activate Feed.

In order to delete a feed, implement the code below:

An interaction should be created before the connector’s integration flow. The reason is that for any flow it will be necessary to inform the interaction context, whether it is a setup or a synchronization.

To create an interaction, do the following:

Logs can be created as the following:

In order to facilitate the integration with Offer Management, all the contracts presented in the previous sections were grouped in a single contract, that does the following:

1. Creates an interaction.
2. Receives a log.
3. Closes an interaction.

We highly recommend using this route when integrating with Offer Management. Other specific routes should be used only when the unified contract does not meet the connector's needs.

If the unified contract was not a solution for the connector, then this section’s specific flows must be implemented.

In order to integrate a VTEX seller’s SKU with a marketplace, the connector has to implement the flows as in the list below:

• Catalog integration
• Price update
• Inventory update
• Integration error [block:callout]

After the creation of the feed, each interaction in Offer Management must start with the same OriginType attribute used in the integration flow that is operating, whether it is about inventory, price or catalog.

In order to create catalog integration, do as the following example:

In order to update price in the integration, do as the following example:

In order to update inventory in the integration, do as the following example:

To integrate errors cases, do as the following example: