Product Feed Types and Scheduling
Norce Commerce Product Feed supports four export types. Understanding when to use each is key to keeping your target system accurate without over-fetching data.
Feed types
| Type | Contents | Use for |
|---|---|---|
| Product (Full) | Complete product data — texts, images, parametrics, prices, availability, suppliers | Populating the full index on initial setup or periodic full refresh |
| Product (Delta) | Same fields as Product Full, but only products changed since deltaFromDate | Catching content, structure, or flag changes between full exports |
| ProductStatus (Full) | Smaller payload — prices, availability, flags, and supplier info only | Full refresh of frequently changing data |
| ProductStatus (Delta) | Same as ProductStatus Full, but only changed products since deltaFromDate | High-frequency updates for price and availability |
- Product Delta is triggered by content, structure, and flag changes. It is not triggered by price or onhand changes.
- ProductStatus Delta is triggered only by price/price list and onhand changes.
Use both together to cover all change types.
Product Full and Delta
The Product feed contains the largest amount of data and is used to populate search services with content, images, parametrics, prices, and other information. It returns all products matching the channel's configuration — active and expiring products for the configured price lists and languages.
Delta timing
Set deltaFromDate to a time slightly further back than the last successful delta export, to account for processing duration.
For example: if the last successful delta ran 10 minutes ago and the average export takes about 1 minute, set deltaFromDate to 11 minutes before now.
ProductStatus (Full and Delta)
The ProductStatus feed contains a smaller set of fields — primarily prices, availability, flags, and supplier information. Because this data changes more frequently than content, ProductStatus is designed to be fetched at higher frequency with lower overhead.
Whenever possible, use ProductStatus for high-frequency updates — its smaller size makes it faster to process than a full Product feed.
Recommended scheduling
It is your responsibility to schedule exports. This gives you control over timing and makes it easier to track failures.
| Feed type | Recommended frequency |
|---|---|
| Product Full | Once a week or once a day |
| Product Delta | 2–6 times a day |
| ProductStatus (Full or Delta) | 1–4 times an hour |
If a delta import fails, the next full export will correct any inconsistencies — so full exports act as a safety net.
Further Reading
- Configuring Product Feed Channels — channel settings, included data, and delta change tracking setup
- Building a Product Feed Receiver — how to trigger exports and consume the feed data