Any CrescoData Platform component performs internal checks on all information that is passed through, and stores all responses to any data sent out. When supported by the channel, CrescoData platform regularly checks with the channel’s system for any quality control or status reports.

For all errors that are received, CrescoData investigates and determines if they are mapping errors, platform errors or data source errors. CrescoData will attempt to resolve these errors wherever possible, as part of the monthly maintenance fee. Errors that are not resolved by CrescoData will be flagged with the channels or to the end customer to fix. Examples of such errors include:

• missing mandatory attributes for product listing
• change in input structure, and
• publishing channel API errors.

What Alerts and monitoring are available?

Internal Monitoring

Errors:

Any CrescoData Platform component performs internal checks on all information that is passed through and reports any errors into a single monitoring module and displayed in The CrescoData Management Portal.

Some checks include:

• Valid Company, Merchant and System information,
• Valid Prices,
• Mandatory attributes for Product Listing, and
• Mandatory attributes for Order Statuses Update.

This allows for checking, and fixing any errors, before attempting to pass information to the publishing destination.

Process Checks

CrescoData also regularly checks for order and product listing updates and can alert your system.

• When an order status is not updated for too long.
• When a product listing is in QA status for too long.

External Monitoring

Responses

The CrescoData platform stores all responses to any data sent out. This means any product or order update to any channel will receive a response from the publishing system. This response is stored internally and matched to the product or order that was being updated. This information is consolidated and presented in the Management Portal

Statuses

Merchants set up in the CrescoData platform can have any number of integrations connected to them. Each integration can support products being sent to or received from it. The same applies to orders which can be sent or received. When supported by the channel, the CrescoData platform regularly checks with the channel’s system for any quality control or status reports. This information is consolidated and presented in the GUI. Please see The Management Portal User Guide for more information.

Standard Operating Process

For all errors that are received, CrescoData investigates and determines if they are mapping errors, platform errors or data source errors. CrescoData will attempt to resolve these errors wherever possible, as part of the monthly maintenance fee. Errors that are not resolved by CrescoData will be flagged with the channels or to the end customer to fix. Examples of such errors include:

• missing mandatory attributes for product listing
• change in input structure, and
• publishing channel API errors.

How are Alerts made available?

Based on the data recorded above, alerts are available via:

• The CrescoData Management Portal (standard)
• Real-time notifications via an API (standard)
• Regular scheduled summaries / notifications (customisations)
• Email notifications, and (customisation)
• Summary reports (customisation)

What Alert Rules can be configured?

Alerts can be modified to follow your escalation policy. For each type of error, rules can specify:

• How often to retry sending of data
• When to send notifications
• Where notifications should be sent to in real-time
• Where notifications should be stored for regular reports, and
• Which errors need human intervention.