JCurve Inventory Item Mapping

What Is JCurve Inventory Item Mapping?

JCurve Inventory Item Mapping is the process of linking the items stored in JCurves inventory module to the corresponding objects in external systems such as ERP, CRM, or ecommerce platforms. By establishing a reliable mapping, organizations can synchronize stock levels, pricing, and product attributes automatically, reducing manual data entry and the risk of errors.

Why Use Item Mapping?

• Data Consistency: Keeps product information identical across all business applications.
• Realtime Stock Visibility: Updates inventory changes instantly, preventing overselling.
• Operational Efficiency: Eliminates repetitive import/export tasks for the supplychain team.
• Scalability: Supports thousands of items without a proportional increase in admin effort.
• Auditability: Every mapping record includes timestamps and user IDs for traceability.

How It Works Core Concepts

1. Source Item (JCurve)

In JCurve, each inventory record has a unique ItemID. The item also contains attributes like Name, SKU, Unit of Measure, and Category.

2. Target Item (External System)

The external system maintains its own identifiercommonly called ProductCode, ItemNo, or SKU. The mapping must translate JCurve ItemID to this external key.

3. Mapping Table

JCurve stores the relationships in a dedicated table:

| MappingID | JCurveItemID | ExternalSystem | ExternalKey | IsActive | CreatedOn | CreatedBy ||-----------|--------------|----------------|------------|----------|-----------|-----------|| 1001      | 4521         | SAP            | MAT-00123  | 1        | 20240215| jdoe      || 1002      | 4522         | Shopify        | prodbluet| 1        | 20240216| jdoe      |        

4. Synchronization Engine

The engine reads the mapping table, pulls the latest inventory data from JCurve, and pushes updates to each target system using the appropriate API or filebased connector. The process can be scheduled (e.g., every 15 minutes) or triggered by events such as a stock receipt.

StepbyStep Setup Guide

Step 1 Identify Integration Points

List all external systems that require inventory data (e.g., SAP, NetSuite, Shopify, WooCommerce). For each system note the required fields, authentication method, and update frequency.

Step 2 Prepare JCurve Item Data

Ensure that every item you plan to expose has a stable, unique SKU. Clean up duplicate entries and verify that the Unit of Measure aligns with the target system.

Step 3 Create Mapping Records

1. Navigate to ConfigurationInventoryItem Mapping in JCurve.
2. Click Add New Mapping.
3. Select the JCurve item, choose the external system, and enter the external key.
4. Mark the mapping as *Active* and save.

Step 4 Configure Connectors

Each external system requires a connector configuration:

• REST API: Provide base URL, authentication token, and JSON payload template.
• SOAP Web Service: Upload the WSDL, map fields, and set security headers.
• Flat File: Define the file pattern, delimiter, and destination folder (FTP/SFTP).

Step 5 Test the Flow

Run a manual sync for a single mapping record. Verify that:

• Quantity on hand matches in both systems.
• Price updates propagate correctly.
• No error codes appear in the JCurve sync log.

Step 6 Schedule Automatic Sync

In SystemScheduler, create a job using the JCurve.Inventory.Sync service. Choose a cadence that matches your business need (e.g., every 10 minutes for highvelocity ecommerce).

Step 7 Monitor & Maintain

Set up alerts for synchronization failures and regularly review the Mapping table for stale or inactive entries.

Best Practices for Successful Mapping

• Use Immutable Keys: Prefer systemgenerated identifiers over mutable fields like product name.
• OnetoOne Mapping: Avoid manytomany relationships unless the external system explicitly supports bundles.
• Document the Mapping Logic: Keep a change log that records why a mapping was created or deactivated.
• Separate Active & Inactive Records: Use the IsActive flag instead of deleting mappings; this preserves history for audits.
• Version Control Connectors: Store connector configuration files in a versioncontrolled repository (Git, Azure DevOps, etc.).
• Test in a Sandbox First: Run all new mappings against a nonproduction environment to catch data mismatches early.
• Plan for Attribute Expansion: Include optional columns for future attributes such as BatchNumber or ExpirationDate.

Common Challenges & Solutions

Future Enhancements to Watch

JCurves roadmap includes AIassisted mapping suggestions, where the system analyses attribute similarity and proposes mappings automatically. Additionally, a visual mapping designer is planned, allowing draganddrop linking of fields between JCurve and target schemas.