# Check Product Status

The Check Product Status API enables you to monitor the processing status of product creation, update, or deletion requests submitted to Fynd Commerce. After submitting products through the respective APIs, you receive a `trace_id` which can be used to track whether the operation completed successfully, is still processing, or encountered errors.

This endpoint provides detailed insights into batch processing results, including success counts, failure reasons, and granular error messages for individual products. It's essential for validating that product data has been correctly transmitted and processed by the Fynd Platform.

> **Request Type:** `GET`
**Scheme:** `HTTPS`
**Endpoint:** `https://{{host}}/v3/catalog/status`


Try out Fynd Konnect's Check Product Status Endpoint
br
**Common Request Headers**

| Header | Mandatory | Description |
|  --- | --- | --- |
| `x-access-token` | Yes | Access token used for authenticating API requests to Fynd Konnect |
| `Content-Type` | Yes | `application/json` |


Use Cases
* Verify successful product creation, update, or deletion
* Monitor batch processing progress for bulk operations
* Identify failed products and retrieve detailed error messages
* Track partial successes in multi-product submissions
* Validate that product data reached Fynd Platform correctly
* Debug integration issues during product synchronization


### Query Parameters

### Response Schema

### API Call Example

### Response Example

COMPLETED Stage
Response in case of multiple products getting either created, updated, or deleted fully:


```json
  {
    "trace_id": "b3bbaead9858e85d-1760266497372",
    "total": 2,
    "success": 2,
    "failed": 0,
    "status": "SUCCESS",
    "errors": {},
    "stage": "COMPLETED",
    "batch_id": "68eb89029955e2f2705c981b",
    "company_id": 6900,
    "meta": {
        "cancelled": 0,
        "cancelled_records": [],
        "failed": 0,
        "failed_records": [],
        "stage": "completed",
        "succeed": 2
    },
    "last_updated_on": "2025-10-12T10:54:59.058168372Z"
  }
```

PARTIAL Stage
Response in case some of the products in the product creation, updation, or deletion request failed due to some error:


```json
  {
    "trace_id": "b3bbaead9858e85d-1760266497372",
    "total": 2,
    "success": 2,
    "failed": 0,
    "status": "SUCCESS",
    "errors": {},
    "stage": "PARTIAL",
    "batch_id": "68eb89029955e2f2705c981b",
    "company_id": 6900,
    "meta": {
      "cancelled": 0,
      "cancelled_records": [],
      "failed": 1,
      "failed_records": [
        {
          "item_code": "AIRCOOL",
          "brand_name": "Generic",
          "message": "Template not found.",
          "error": {
            "code": 400,
            "message": "Template not found."
          }
        }
      ],
      "stage": "partial",
      "succeed": 1
    },
    "last_updated_on": "2025-10-12T10:54:59.058168372Z"
  }
```

PENDING Stage
Response when products are still being processed. This is a transitional state between submission and completion:


```json
  {
    "trace_id": "bd37ecdfc415d315-1760266895324",
    "total": 2,
    "success": 2,
    "failed": 0,
    "status": "SUCCESS",
    "errors": {},
    "stage": "RUNNING",
    "batch_id": "68eb8a8f9955e2f2705c981c",
    "company_id": 6900,
    "meta": {
      "cancelled": 0,
      "cancelled_records": [],
      "failed": 0,
      "failed_records": [],
      "stage": "pending",
      "succeed": 0
    },
    "last_updated_on": "2025-10-12T11:01:35.696033796Z"
  }
```

FAILED Stage
Response when validation errors prevent products from being processed. Common causes include invalid enum values, incorrect references, or missing mandatory fields:


```json
  {
    "trace_id": "b3bbaead9858e85d-1760266497372",
    "total": 2,
    "success": 2,
    "failed": 0,
    "status": "SUCCESS",
    "errors": {},
    "stage": "FAILED",
    "batch_id": "68eb89029955e2f2705c981b",
    "company_id": 6900,
    "meta": {
      "cancelled": 0,
      "cancelled_records": [],
      "failed": 2,
      "failed_records": [
        {
          "item_code": "AIRCOOL",
          "brand_name": "Generic",
          "message": "Template not found.",
          "error": {
            "code": 400,
            "message": "Template not found."
          }
        },
        {
          "item_code": "WNDWAC",
          "brand_name": "Generic",
          "message": "Template not found.",
          "error": {
            "code": 400,
            "message": "Template not found."
          }
        }
      ],
      "stage": "failed",
      "succeed": 0
    },
    "last_updated_on": "2025-10-12T10:59:48.824668216Z"
  }
```

## Understanding Processing Stages

| **Stage**  | `meta.stage` **Value** | **Description** | **Action Required** |
|  --- | --- | --- | --- |
| `RUNNING` | `pending` | Products are being validated and processed | Continue polling until stage changes |
| `COMPLETED` | `completed` | All products processed successfully | No action needed; products are live |
| `PARTIAL` | `partial` | Some products succeeded, others failed | Review `failed_records` and resubmit failed products |
| `FAILED` | `failed` | All products failed validation or processing | Fix errors in `failed_records` and resubmit entire batch |


#### When to Expect PENDING Stage?

Products remain in PENDING stage when:

1. Batch validation is in progress
2. Products are queued for processing
3. System is performing data validation checks
4. Large batches are being processed sequentially


> **Recommended Action:** Continue polling the status endpoint until stage changes to COMPLETED, PARTIAL, or FAILED.


#### Common Failure Causes

Products fail validation when:

1. **Invalid enum values**: Incorrect data types or values for fields with predefined options
2. **Reference errors**: Invalid category, department, brand, slug, or template that don't exist
3. **Missing mandatory fields**: Required attributes not provided (check Fetch Attributes by Product)
4. **Data format errors**: Incorrect date formats, invalid URLs, malformed identifiers
5. **Duplicate identifiers**: SKUs or slugs that already exist in the catalog


> **Recommended Action:** Review `failed_records` array, fix the issues in your source data, and resubmit the products.


## Best Practices

1. **Poll with intervals**: Check status every 5-10 seconds for PENDING/RUNNING stages to avoid excessive API calls
2. **Implement exponential backoff**: Increase polling interval for long-running operations
3. **Parse `failed_record`**: Extract error messages programmatically for automated error handling
4. **Log `trace_id`**: Maintain a mapping of trace_ids to your internal product identifiers for debugging
5. **Handle partial success**: Implement logic to resubmit only failed products from PARTIAL batches
6. **Set timeouts**: Implement reasonable timeouts (5-10 minutes) for status checks
7. **Validate before submission**: Use reference APIs (departments, categories, brands, templates) to validate data before creating products
8. **Monitor error patterns**: Track common error types to improve data quality
9. **Retry with fixes**: For FAILED batches, fix all validation errors before resubmission
10. **Archive status responses**: Store status responses for audit trails and troubleshooting


Next Steps
* To create products after fixing errors, see [Create Product](/konnect/channels/erp-wms/api-documentation/catalog/post-create-product)
* To update products after status confirmation, see [Update Product](/konnect/channels/erp-wms/api-documentation/catalog/put-update-product)
* To fetch successfully created products, see [Fetch Products](/konnect/channels/erp-wms/api-documentation/catalog/get-products)
* For validation reference data, see [Fetch Departments](/konnect/channels/erp-wms/api-documentation/catalog/get-departments), [Fetch Categories](/konnect/channels/erp-wms/api-documentation/catalog/get-categories), [Fetch Brands](/konnect/channels/erp-wms/api-documentation/catalog/get-brands)
* For complete catalog management workflow, see [Catalog Management Guide](/konnect/channels/erp-wms/whats-new/catalog-management)