Skip to content
Last updated

Troubleshooting Guide

This concise section covers common issues across API integration, order syncing, inventory updates, product mapping, order processing, and performance. Use it to quickly diagnose and resolve operational problems.

Credentials Issue

Symptoms: Sync failures, connection timeouts, authentication errors

Causes: Invalid credentials, expired tokens, connectivity issues

Fix:

  • Validate credentials in Configured Channels → Locations
  • Check internet settings
  • Resave credentials to refresh token
  • Contact support if unresolved

Order Sync Failures

Symptoms: Missing, delayed, or duplicated orders

Causes: Misconfigured sync settings, API lag, system errors, incorrect credentials

Fix:

  • Cross-check order in Meesho portal
  • Ensure Order Sync Toggle is ON and sync date is correct
  • Use Force Create Order in Orders → Failed Orders

Inventory Sync Discrepancies

Symptoms: Mismatched inventory across systems, overselling

Causes: Buffer stock issues, sync errors, inactive locations

Fix:

  • Audit inventory across systems
  • Check Inventory Logs for sync issues
  • Adjust buffer stock, trigger reconciliation manually
  • Confirm item is active, location is mapped, and inventory sync is ON

Product Mapping Issues

Symptoms: Products not listed or show incorrect data

Causes: Missing/incorrect Product IDs, status inactive

Fix:

  • Check Channel Mapping tab for unmapped SKUs
  • Validate and correct Meesho Product IDs
  • Use auto-mapping or upload via bulk file

Order Status Update Failures

Symptoms: Status not syncing to Meesho

Fix:

  • Update status manually in Orders tab
  • Use bulk update tools if needed

Emergency Protocol

Critical: Major outages, sync failures → Contact Fynd Support immediately

Operational: Minor issues → Log ticket, implement workarounds


Common Issues & Fixes

IssueResolution
SKU not syncingEnsure SKU mapping is correct via vendor_style_code
Inventory not updatingConfirm item is active, location is mapped, and sync is ON
Order not createdCheck for duplication, credential failure, or missing fields