to select ↑↓ to navigate
Navgold

Navgold

Data Mapping and Troubleshooting

This module explains how Navgold bridges the gap between Amazon listings and Frappe items, and how to resolve common synchronization issues.

1. The Proxy SKU (The "Bridge")

The Proxy SKU is the most important data mapping in the system. It connects an Amazon Seller SKU to a specific Frappe Item and UOM.

  • Key Fields:
    • SKU Name: This must exactly match the "Seller SKU" on Amazon.
    • Item & UOM: Defines which local product is being sold.
    • ASIN: The Amazon Standard Identification Number.
    • FNSKU: The fulfillment network SKU (required for FBA).
    • Is Active: Only active Proxy SKUs are used for pricing and order syncing.
  • Bulk Mapping Tools:
    • Import Listings: Located in Navgold Settings, this tool downloads all your active Amazon listings and automatically creates or updates Proxy SKUs, matching them by SKU name.
    • Bulk Fetch FNSKU: Automatically updates missing FNSKUs for all FBA-enabled Proxy SKUs by querying Amazon's inventory API.

2. Unmapped SKU Alerts

If Amazon sends an order for a SKU that does not yet exist as a Proxy SKU in Frappe, the system protects your data integrity by blocking the order.

  • What happens?
    1. The order sync process pauses for that specific order.
    2. An Amazon Unmapped SKU record is created.
    3. The system sends a Notification Alert to the administrator.
  • How to resolve:
    1. Go to the Amazon Unmapped SKU list.
    2. Create the missing Proxy SKU mapping for that item.
    3. Once the mapping is saved, you can retry the order sync.

3. Handling Failed Syncs (Amazon Failed Sync Record)

Sometimes orders fail to sync due to network issues, missing data, or system errors.

  • The Fail Log: Every failed sync is logged in the Amazon Failed Sync Record list. It stores:
    • The Amazon Order ID.
    • The Raw Payload (the data Amazon sent).
    • A Remark explaining why it failed (e.g., "Missing Warehouse").
  • The Workflow:
    1. Review the remarks to identify the cause of the failure.
    2. Fix the underlying issue (e.g., update a setting or fix a mapping).
    3. Click the "Retry" button on the record.
    4. If successful, the record is marked as Resolved, and the official Sales Order is created.

4. Item Versioning (Next Proxy SKU)

When an Amazon listing is updated or replaced, you may need to cycle to a new Proxy SKU while keeping the old one for historical records.

  • The "Create Next Proxy SKU" button on a Proxy SKU record automatically deactivates the current one and creates a fresh draft for the same Item/UOM/ASIN, allowing you to quickly update mapping without losing data.
Last updated 1 month ago
Was this helpful?
Thanks!