SKU Mapping

• The same product is listed under different SKUs in different sales channels.

• Fulfillment centers require system-specific or location-specific SKUs.

• Inventory and order data must stay synchronized across multiple systems.

Example:

• Shopify: TRAIN-101

• US 3PL: TRAIN-101-FBA

• Canada 3PL: TRAIN-101-CA

The app automatically converts between these SKUs, ensuring smooth order and fulfillment operations.

How SKU Mapping Works

• Inbound: Orders enter with a channel SKU (for example, SHOP-P2004). The system converts it to the product’s primary SKU (P2004).

• Internal Processing: Automation, routing, and inventory operations use the primary SKU.

• Outbound: When data is sent to a 3PL or external system, the app converts it to the partner’s expected SKU (for example, P2004 → 3PL-P2004).

You can confirm mappings in:

• Source documents (sourceDoc field shows the original SKU).

• Outbound events (shows converted SKU sent to partners).

• Order details page (mapped SKUs are displayed when available).

Steps

1. Product-Level SKU Mapping

Mappings are configured directly on individual products.

Steps:

1. Go to Products → All Products → Product Details page.

2. Scroll to Channel options.

3. Enter the channel-specific SKU in the Channel SKU field for each integration.

 

Example:

• Primary SKU: P2004

• Shopify SKU: SHOP-P2004

• eBay SKU: EBAY-P2004

Bulk CSV Import:

• Export the product template from the Products page.

• Enter channel SKUs in the provided columns.

• Import the file using Product Import.

• Spot-check updated products to verify mapping accuracy.

2. Connector-Level SKU Mapping

Not all, but some connectors (such as Amazon MCF) allow SKU mapping within integration settings.

 

Supported formats:

• Simple (inline):
  B7:CANB7, B8:CANB8, B9:CANB9

• JSON (multiline):

  {
    "B7": "CANB7",
    "B8": "CANB8",
    "B9": "CANB9"
  }

Use this method when a specific connector requires its own mapping format or when you want to override product-level settings.

Troubleshooting

Key Rules to Remember

• No duplicate mappings: Multiple SKUs cannot point to the same target SKU (for example, SKUB → SKUA if SKUA already exists).

• Unique mappings only: Each mapping must be distinct.

• Bidirectional conversions: Mapping applies both inbound (from channels to the app) and outbound (to 3PLs).

• Consistency required: Avoid conflicts between product-level and connector-level mappings.

Common Issues and Fixes

• Orders show the wrong SKU

  • Review Channel options for the product.

  • Check connector-level mappings for overrides.

  • Ensure only one valid mapping exists.

• No conversion occurred

  • Confirm exact SKU values (case sensitivity, spaces, characters).

  • Ensure the mapping is saved to the right product or connector.

  • Retry the order or fulfillment after fixing the mapping.

• Duplicate or ambiguous mapping error

  • Search for conflicting mappings pointing to the same target.

  • Remove duplicates and reprocess the order.

• Inventory mismatches

  • Remember that SKU mapping also affects inventory syncs.

  • Verify mappings in both product-level and connector-level configurations.

• Still failing after corrections

  • Review event logs to confirm conversions in and out.

  • Re-run failed orders or fulfillment requests once mappings are corrected.

FAQs within Troubleshooting

• Does SKU mapping affect inventory?
  Yes, inventory updates use the mapped primary SKU internally and convert to partner SKUs for outbound syncs.

• Which method should I use?
  Use product-level mapping for most cases. Use connector-level mapping only when a partner system requires overrides.

Related concepts

SKU mapping resolves a single source SKU to a single destination SKU. For substitution behavior, picking between multiple SKUs based on inventory at routing time, see Alternate SKU evaluation in Routing Rules (High-Level Concept).

Need Help?

If you need additional assistance:

• Use Ask Pippen, our AI agent, located at the top of the app page.

• Submit a support request with as much relevant detail as possible. Learn how to submit a request.

• For urgent issues, email us directly at support@pipe17.com.

We're here to help you succeed with your operations.