Engage holds an internal article register for each tenant, containing all the articles (purchasable items) in the client’s system. The article register is used to enrich data within Engage like transactions and products of interest. The register can be created and updated in two ways:Documentation Index
Fetch the complete documentation index at: https://developer.voyado.com/llms.txt
Use this file to discover all available pages before exploring further.
- Using a product feed to populate the register
- Using sources like XML files from a PIM or ERP system
Article vs product
There is a difference between products (used for communication) and articles (used for data enrichment). These represent two separate functions and areas within the system. In more detail: An article is an individual line-item purchase on a transaction.- For example: A certain hat.
- For example: That certain hat, in the color red, available at a specific store.
- For example: The hat’s availability, review score, number of sellers, how many variations exist…
Article data
An article in Engage includes standard fields and some flexible extra fields configured per client installation. These “spare fields” are of two types:- 10 “spare” string fields (spare1, spare2 … spare10)
- 5 “spare” date/time fields (datespare1, datespare2 … datespare5)
Article enrichment
In receipts, articles generally lack any useful product data or metadata. This is to save space in the transmission and importing of transactions, but also to allow flexibility in adding product data later. This process is known as “enrichment”.The SKU
An article’s SKU code is the key to enrichment. Since an SKU exists both for the article on the transaction and in the article register, this allows the two to be connected. The SKU is mapped toArticleNr in Engage. Note that a line-item row in Engage always refers to the most detailed version of a specific article.
You can read more about this here:
