SynSets

What are SynSets?

SynSets allow you to group multiple individual SKUs and sell them together as a single unit. When a customer orders a SynSet, the system automatically deducts inventory from all included SKUs.

For example, you can create a “Gift Basket” that includes 3 chocolates, 2 candles, and 1 gift card. When someone purchases the Gift Basket, ShipEdge Core automatically reduces inventory of each individual item.

Common Use Case

Use SynSets to sell promotional bundles, gift sets, complementary product kits, or special combos without having to create separate physical SKUs.

Create a New SynSet

You can create SynSets from two locations:

Method 1: From SKU Substitutions

1. Navigate to SKU Substitutions

   Open Inventory SKU Substitutions from the Catalog toolbar (page title SKU Substitutions, vector icon in the header).

2. Click “Create” Button

   Click Create in the page header.

3. Select Kits and continue

   In the dialog New Item Subtitute, select Kits: Translate kits or bundles to components, then click Continue.

4. Configure the SynSet

   The system will:

   • Open the SynSet form for configuration
   • Allow you to add component SKUs and configure settings

Method 2: From Catalog (3-Dot Menu)

1. Navigate to Catalog

   Go to Inventory.

2. Click the Three Dots Menu

   Find the SKU you want as the first component and open the row menu (vertical ellipsis).

3. Create Synset

   Click Create Synset from the dropdown menu.

4. Complete the modal

   In the Create Synset dialog:

   • Synset: Enter a unique name (required; must not match the SKU name)
   • Sku: Read-only, shows the selected SKU
   • Click Create (or Close to cancel)

Completing SynSet Configuration

After creating a SynSet using either method, you’ll need to complete the configuration:

1. Complete basic fields

   In the Edit (Synset) or Create (Synset) dialog (SKU Substitutions):

   • Name: Unique SynSet name (required)
   • Description: Optional
   • Mix Max: Optional (number)
   • Bom SKU: Optional combobox—must be an existing product SKU
   • Shipping Method: Optional
   • Allow Division: Optional (tooltip: dividing SKUs into separate boxes during processing)
   • If manufacture is enabled for the warehouse: Instructions: (max 255 characters) and optional Attachment (PDF only, max 2MB), with a note that they print with manufacturing work orders in WMS

2. Add component SKUs

   In the assigned-items grid:

   • If you started from Catalog, the first SKU is already listed
   • Click Assign to open the picker, choose SKU/UOM and quantity
   • Specify the Quantity of the SKU
   • Click Assign to add the SKU to the SynSet
   • Optional: Assign Template (enabled when a Bom SKU is selected)
   • Remove a line with the remove control (X) in the row

3. Configure BOM SKU (Optional)

   The BOM SKU (Bill of Materials SKU) is a main SKU that represents the complete bundle:

   • Enter the SKU code (must exist in your product catalog)
   • If you specify a BOM SKU, the system will mark that SKU as “BOM” in the product catalog
   • Useful for integrating with external systems or marketplaces
   • The BOM SKU must exist in your product catalog before assigning it
   • If the SKU doesn’t exist, you’ll see an error: “BOM SKU does no exist, Create SKU”

4. Save

   Click Save. You must have at least one assigned item; otherwise the system shows It’s necessary to add at least one item.

5. Result

   After a successful save:

   • The SynSet is stored with all component SKUs
   • Available stock is calculated from components
   • The Synsets table refreshes

Creating from Catalog

When creating from the Catalog 3-dot menu, you only need to provide a SynSet name. The selected SKU is automatically added as the first component. You can then add more SKUs by accessing the SynSet through SKU Substitutions.

Creating from SKU Substitutions

When creating from SKU Substitutions, you start with a blank SynSet and add all component SKUs manually. This method gives you more control over the initial configuration.

Advanced SynSets Features

BOM SKU (Bill of Materials)

Assign a main SKU that represents the complete SynSet. Useful for integrating with marketplaces like Amazon or Shopify.

Mix Max

Define the maximum allowed quantity for mixing or combining SKUs in the SynSet. Control your bundle’s flexibility.

Custom Shipping Method

Configure a specific shipping method for the SynSet, different from standard methods.

Attached Instructions

Add special packing instructions or attachments to guide warehouse staff.

Allow Division

Enable dividing SKUs into separate boxes during processing.

BOM SKU (Bill of Materials)

The BOM SKU is a main catalog SKU that represents the complete SynSet for integrations and reporting:

• How it works: When you assign a BOM SKU, that product is treated as the BOM for the SynSet in the catalog
• Main use: Channels that need one sellable SKU for the bundle (for example Amazon, eBay, Shopify)
• Requirement: The BOM SKU must already exist in your product catalog
• BOM SKU QTY: Checkbox (tooltip in the form: Include sending BOM SKU quantity back to the cart.)
• Bulk on the list: In Synsets, the BOM SKU Qty column header includes a checkbox to toggle BOM SKU QTY for multiple rows

Manufacturing Module

Assigning a BOM SKU is the first step to using ShipEdge’s Manufacturing capabilities. Once a BOM SKU is tied to a SynSet, you can use the Manufacturing module to create internal work orders for the warehouse to physically assemble these kits and increase your finished good inventory. Learn more in the Manufacturing Setup guide.

Important

• You cannot use the same BOM SKU for multiple SynSets. Each SynSet must have its own unique BOM SKU or none at all.
• If you enter a BOM SKU that doesn’t exist, you’ll see an error: “BOM SKU does no exist, Create SKU”
• When you remove a BOM SKU from a SynSet, the system creates a history record: “Delete BOM SKU by SynSet”

Allow Division

The Allow Division option gives warehouse operators flexibility when packing orders containing SynSets:

• How it works: Check this option to enable dividing SKUs from the SynSet into separate boxes during processing.
• Main use: Useful when a SynSet contains large or bulky items that cannot fit together in a single standard box, or when items require different packaging types.
• Configuration: Found as a checkbox during SynSet creation or editing.

Edit an Existing SynSet

1. Open SKU Substitutions

   Go to SKU Substitutions (from Catalog), then open the Synsets tab.

2. Open Edit

   In the SynSets table, use the row menu (vertical ellipsis) and click Edit.

3. Update fields

   In Edit (Synset) adjust Name, Description, Mix Max, Bom SKU, BOM SKU QTY, Shipping Method, Allow Division, and (if manufacture is on) Instructions / Attachment as needed.

4. Add or remove components

   Use Assign to add SKUs/UOMs; use the row remove control to remove a component from the set.

5. Save

   Click Save.

BOM SKU Changes

When you change or remove a BOM SKU, the system creates history records and updates the products table to reflect the BOM status changes.

Import/Export SynSets

ShipEdge Core allows importing and exporting SynSet configurations via CSV files from the SKU Substitutions interface.

Export SynSets

You can export SynSets data directly from the SynSets table in SKU Substitutions:

1. Navigate to SKU Substitutions

   Go to Inventory, then click SKU Substitutions button.

2. Go to SynSets Tab

   Click on the Synsets tab.

3. Export Data

   Use the DataTables buttons above the grid:

   • CSV
   • EXCEL

   Default filenames use the pattern synsets_YYYY_MM_D__HH_mm_ss plus the file extension. Exports are limited to 5,000 rows per download; if there are more records, narrow filters and export again.

4. Filter Before Export (Optional)

   Apply filters to the table to export only specific SynSets before clicking the export button.

Export Contents

The export includes all visible columns in the SynSets table, including SynSet name, SKUs, quantities, description, stock, BOM SKU, shipping method, and other configured fields.

Download SynSet Template

You can download CSV templates for creating SynSets:

1. Open Upload (Synsets)

   From SKU Substitutions → Synsets, click Upload SynSet. The page title is Upload (Synsets).

2. Download Template

   Click Download Template and pick a template name from the list (each item downloads via the template export).

3. Templates

   Templates define how CSV columns map to SynSet fields (for example Initial Template with synset, description, bom_sku, sku, quantity, and optionally UOM_name when UOM is enabled).

Template System

The system uses configurable templates that map CSV column headers to SynSet fields. You can create and save custom templates for different CSV formats.

Upload SynSet Configurations

You can upload SynSets via CSV using the new upload system with field mapping:

1. Open Upload (Synsets)

   From SKU Substitutions → (Synsets) tab, click the Upload SynSet button.

2. Prepare Your CSV File

   Your CSV file should include columns for:

   • synset: SynSet name (required)
   • sku: Component SKU codes
   • quantity: Quantity of each SKU
   • description: SynSet description (optional)
   • mix_max: Maximum mixing quantity (optional)
   • bom_sku: BOM SKU code (optional)
   • UOM_name: UOM name if using UOM feature (optional)

3. Upload the CSV File

   • Use the file control labeled Choose or drag synsets file…
   • Click Upload
   • When the job is in Draft status, open the column mapping screen (link Continue uploading from History if you come back later)

4. Map CSV Fields (if needed)

   If your CSV headers don’t match the standard format:

   • The system shows a visual mapping interface
   • Connect CSV column headers (left side) to SynSet fields (right side)
   • Select a template from the dropdown if you have saved templates
   • The system can auto-detect the best template match

5. Configure Import Options

   • Delete (SynSet): Check this box if you want to delete existing SynSets before importing

6. Process the Import

   Click Process button. The system will:

   • Validate the CSV format and field mappings
   • Check that all SKUs exist in your catalog
   • Create new SynSets with component SKUs
   • Show processing status and results

7. Review upload history

   Check the upload history table on the same page to see:

   • Upload ID and filename
   • Upload date
   • Processing results
   • Status (Pending, Processing, Completed)

Import Tip

Always download a copy of your current SynSets before doing a bulk import. This will serve as a backup in case of errors.

Why Use SynSets?

Simplifies Catalog

Sell multiple products as one without creating additional physical SKUs.

Automatic Stock Management

Inventory is automatically calculated based on component SKUs.

Increases Sales

Create attractive bundle and kit offers to increase average order value.

Total Flexibility

Configure specific quantities, shipping methods, and custom rules for each SynSet.

💡 Best Practices

Descriptive Names

Use clear and descriptive names for your SynSets that clearly indicate what the bundle contains (e.g., “Summer-Beach-Kit”, “Gift-Set-Birthday”).

Monitor Limiting Stock

Regularly identify which component SKU is limiting SynSet stock and replenish it first.

Use BOM SKU for Integrations

If you sell on external marketplaces, always assign a unique BOM SKU to facilitate inventory synchronization.

Review Configurations Before Importing

Validate your CSV file before importing SynSets in bulk to avoid configuration errors.

Group Complementary Products

Create SynSets with products that are naturally used together to increase perceived value and sales.

Update Descriptions

Keep SynSet descriptions updated with promotion details, bundle benefits, or special instructions.

How SynSets Work

When you create a SynSet, you define:

1. SynSet Name: A unique identifier (can’t be the same as an existing SKU, must be completely new)
2. Included SKUs: The individual products that form part of the bundle
3. Quantities: How many units of each SKU are included
4. Available Stock: Automatically calculated based on component inventory

Troubleshooting

SynSet Stock Shows Zero Even Though I Have Inventory

Problem: The SynSet shows stock 0 even when component SKUs have inventory.

Solution:

• Refresh the page: Stock is recalculated when you load the SynSets list page. Try navigating away and back.
• Verify that all component SKUs have available stock
• Identify the SKU with lowest relative stock (available stock ÷ required quantity)
• That SKU is limiting SynSet stock
• Replenish the limiting SKU to increase SynSet stock

I Can’t Assign a BOM SKU

Problem: When trying to assign a BOM SKU, you receive an error or the system doesn’t allow it.

Solution:

1. Verify that the BOM SKU exists in your product catalog
2. Make sure the BOM SKU is not assigned to another SynSet
3. If the SKU doesn’t exist, create it first in the product catalog and then assign it to the SynSet

SKUs Don’t Get Added to the SynSet

Problem: When trying to add SKUs to the SynSet, they don’t save or an error appears.

Solution:

• Confirm that SKUs exist in your product catalog
• Verify that you’re entering quantities greater than zero
• Make sure the SynSet name is not the same as an existing individual SKU (unless you intentionally want it)

SynSet Doesn’t Appear in External Integrations

Problem: The created SynSet doesn’t synchronize with your connected marketplace (Shopify, Amazon, etc.).

Solution:

1. Assign a BOM SKU to the SynSet
2. Enable BOM SKU QTY if the channel expects BOM quantities synced (the in-app tooltip refers to the cart)
3. Verify inventory synchronization configuration in the integrations module
4. Review synchronization logs to identify specific errors

Error Importing SynSets CSV

Problem: When trying to import a CSV file, you receive errors or SynSets don’t get created.

Solution:

• Verify that the CSV file uses the correct format (download a template as reference)
• Make sure all SKUs mentioned in the CSV exist in your catalog
• Verify that quantities are valid numbers greater than zero
• Confirm there are no special characters that break the CSV format

Important Considerations

Stock Warning

When you delete a SynSet, the system does not automatically restore inventory. Stock adjustments already applied to orders remain unchanged.

• Unique Names: Each SynSet must have a unique name in your account. There cannot be two SynSets with the same name.
• Unique BOM SKU: A BOM SKU can only be assigned to one SynSet at a time.
• Real-Time Stock: SynSet stock is automatically recalculated whenever a component SKU’s inventory is updated.
• Integrations: To synchronize SynSets with external marketplaces, make sure to correctly configure the BOM SKU.

Convert SynSets to Aliases

From SKU Substitutions → Synsets, click Convert to Aliases (shown for seller-level accounts; warehouse-only views may not include this control).

1. Open the converter

   A dialog opens: Available Synsets to convert, with a warning that converted synset will be deleted.

2. Select synsets

   Check the rows to convert (or Select All). The list is filtered to eligible SynSets.

3. Pick an action

   Open Actions and choose either:

   • Convert to global aliases — account-wide aliases; confirm with Convert on Are you sure to convert to aliases?
   • Convert to channel aliases — pick a channel in Please chose a channel for new aliases!, then click Convert

4. Outcome

   On success, aliases are created and the SynSet is removed. Errors list per (Synset) if a name is already used by another catalog item.

Conversion Requirements

• The SynSet name must be unique and not already exist as another catalog item.
• All component SKUs must exist in your catalog
• After conversion, the SynSet is deleted and cannot be recovered

Related Pages

Next Steps:

• Product Catalog - Explore how to organize your complete catalog including SynSets

See Also:

• Creating Products - Create the component SKUs needed for your SynSets
• SKU Management - Learn about SKU aliases and translations