# Troubleshooting Guide

### Credentials Issue

**Symptoms:** Sync failures, connection timeouts, or authentication errors

**Causes:**

* Invalid or mistyped Channel Credentials
* Konnect Credentials not yet shared with the Clozzet POC
* Connectivity issues


**Fix:**

* Validate the Channel Credentials in **Configured Channels → Locations** and resave to refresh the connection
* Confirm the auto-generated Konnect Credentials have been shared with your Clozzet POC, as the inbound (Clozzet → Fynd) flow depends on them
* Check your internet connectivity
* Contact Fynd Support if the issue persists


### Order Sync Failures

**Symptoms:** Missing, delayed, or duplicated orders

**Causes:**

* Order Sync toggle is off or the sync-from date is incorrect
* Konnect Credentials not configured on the Clozzet side
* API lag or system errors


**Fix:**

* Ensure the **Order Sync** toggle is ON and the sync-from date is correct
* Confirm Clozzet is using the correct Konnect Credentials to push orders
* Cross-check the order on the Clozzet side
* Contact Fynd Support if orders are still not appearing


### Inventory Sync Discrepancies

**Symptoms:** Mismatched inventory between Fynd and Clozzet leading to overselling or underselling

**Causes:**

* Buffer quantity misconfiguration
* Inactive variant or unmapped location
* Inventory Sync toggle off


**Fix:**

* Confirm the variant is **Active**, its location is mapped, and **Inventory Sync** is ON
* Check **Inventory Logs** for sync errors
* Review the buffer quantity (`Visible Stock = Total – Buffer`)
* Re-run a full inventory sync by toggling Inventory Sync during activation


### Product Mapping Issues

**Symptoms:** Variants not listed on Clozzet, or a validation error when saving a mapping

**Causes:**

* Missing or incorrect Clozzet product/variant code
* Mapping left inactive
* Invalid code rejected at validation


**Fix:**

* In **Channel Mapping**, check for unmapped variants
* Re-enter the correct Clozzet product/variant code and click **Validate**; correct the code if an error is shown
* Activate the mapping and confirm inventory is non-zero


### Bulk Mapping Partially Failed

**Symptoms:** A bulk job completes but some SKUs are not mapped

**Fix:**

* Open **Bulk Mapping History** and download the **Processed File**
* Review the SKU-level errors, then correct the affected rows (product code, buffer, or status)
* Re-upload the corrected file and run Bulk Map again


### Location Mapping Not Applying

**Symptoms:** Inventory not reaching the expected Clozzet location

**Fix:**

* Confirm the **Channel Location ID** matches the location code shared by Clozzet
* Ensure the location row status is toggled **ON**, you clicked **Done**, and then **Submit**
* If all Fynd locations should map to one Clozzet location, use **Apply to All**


### Cancellation Not Syncing

**Symptoms:** A cancellation on one platform does not appear on the other

**Fix:**

* Confirm both credential sets are in place, as cancellations rely on the bidirectional connection
* Cross-check the order state on the Clozzet side
* Contact Fynd Support if the mismatch persists


### Emergency Protocol

* **Critical issues** (major outages, widespread sync failures): Contact Fynd Support immediately
* **Operational issues** (minor errors): Log a ticket and implement any available workarounds