Applies to: All tiers · Last reviewed: 2026-06-24
What this is
A SKU mapping connects an external code from a sales channel (a storefront SKU, or an Amazon ASIN) to one or more of your warehouse products. There are two kinds:
- Alias: one external SKU resolves to exactly one product, quantity 1. Use this when a channel's SKU differs from your internal SKU.
- Bundle: one external SKU fans out to several products, or to a single product with a quantity greater than 1. This is a kit.
Find them at Catalog > SKU Mappings.
Create a bundle or alias
- Catalog > SKU Mappings > New Mapping.
- Client (required): pick the owning client first. The component product search is scoped to that client's catalogue, so choosing the client first is what makes products searchable.
- Identifier kind: SKU (default) or ASIN (for Amazon).
- Source SKU (external): the external code, for example the storefront SKU.
- Channel scope (optional): leave blank to apply to all of the client's channels, or pick one channel.
- Name (optional): a friendly display name, for example "Holiday Gift Set".
- Component products: for each component, search the Product (type the SKU) and set the Qty. Click + Add Component for each additional product. One component at quantity 1 is an alias; multiple components, or any quantity above 1, makes it a bundle.
- Click Create. The Maps To column lists the component SKUs, with
(xN)for quantities.

Import mappings by CSV
Catalog > SKU Mappings > Import CSV, one client per import. Columns: source_sku, target_sku, quantity, kind, sales_channel_id. Rows that share a source_sku form one bundle. quantity defaults to 1, kind defaults to sku (use asin for Amazon), and a blank sales_channel_id applies to all channels. There is no name column in the CSV, so add display names afterward from each mapping's Edit action.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article