- Product Feeds: Product feeds must be connected to Voyado Engage for each locale (Ex: sv-SE).
- Event System in Centra: The event system must be enabled in Centra. Contact your Centra Customer Success Manager for validation.
- Back in Stock email module: A “Back in Stock” module must be added to your Engage email templates.
- API Credentials: API credentials must be set up in Centra and Voyado Engage.
Configuration of API token in Centra
Follow these steps:Create a new Integration
The Integration should have a relevant name, for example “Engage integration”.
Enable the following permissions
Write permissions:
- Event
- Allocation rule
- Market
- Product
- Product Size
- Product Variant
- Stock Change
- Store
- Warehouse
- Orders
- Returns
Subscription API for Centra
The subscription flow is not supported “out of the box” and requires front-end development. These are the steps in building a subscription flow:- Build a subscription form that is visible when the end user enters a product variant page that is considered to be out-of-stock.
- Register the subscriptions in Voyado Engage, using the Subscription API for Centra.
- Ensure that the locale field aligns with the locales associated with the product feeds in Engage (for example: “en-US”).
HTTP Method
The subscription endpoint
JSON example - Body
JSON example - Body
The email address of the user. Must be a valid email format.
Example: “john-doe@voyado.com”
The productSize.SKU value in Centra.
Example: “1234SIZEM”
If user accepts general newsletters or not.
Example: true
Unique identifier for your Centra environment.
Example: “voyadotenant-1”
Locale matching Engage product feeds.
Example: “sv-SE”
The Market ID connected to the user. Must match the Market ID in the stock change.
Example: “4”
JSON Example - Output to Engage
JSON Example - Output to Engage
JSON Example - Subscription
JSON Example - Subscription
Store field format
When you have a single Engage environment for all stores just use thetenantId value as the store field. For example: “mytenant”.
When you have multiple Engage stores (one per Centra store) combine the tenantId and CentraStoreID to a single string. For example “mytenant-124”.
This ensures each connection is uniquely identified in Engage.
Stock changes
Engage receives the current Free to Allocate (FTA) quantity for a product at the time of the stock change event. It does not calculate or use the delta (the change in quantity). This means the quantity value in the payload always reflects the latest available stock level, and not how much it changed since the last update.
| Field name Engage | Field name Centra | Type | Description | Example |
|---|---|---|---|---|
| sku* | productSize.SKU | string | The productSize.SKU in Centra. | ”1234-1” |
| quantity* | Free to allocate (FTA) | int | Available stock quantity. | 125 |
| externalId* | Market ID | string | Market ID matching subscription data. | ”4” |
Workflow
The workflow as an image: