Product Families (SynSets)

What are Product Families (SynSets)?

Product Families, also known as 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.

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.

How SynSets Work

When you create a SynSet, you define:

1. SynSet Name: A unique identifier (can be the same as an existing SKU or 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

Automatic Stock Calculation

The system calculates how many SynSets you can form based on the SKU with the lowest available inventory.

Example:

If your “Holiday Bundle” SynSet includes:

• SKU-A: 3 units (100 in stock)
• SKU-B: 2 units (50 in stock)
• SKU-C: 1 unit (80 in stock)

SynSet Available Stock:

• SKU-A allows: 100 ÷ 3 = 33 bundles
• SKU-B allows: 50 ÷ 2 = 25 bundles ← Limiting
• SKU-C allows: 80 ÷ 1 = 80 bundles

Result: You can only create 25 Holiday Bundles before running out of SKU-B.

Create a New SynSet

You can create SynSets from two locations:

Method 1: From SKU Substitutions

1. Navigate to SKU Substitutions

   Go to Inventory → Catalog, then click the SKU Substitutions button (vector icon) in the Catalog toolbar.

2. Click “Create” Button

   Click the Create button in the SKU Substitutions page header.

3. Select “Kits” Option

   In the dialog that appears, select “Kits: Translate kits or bundles to components”.

4. Configure the SynSet

   The system will:

   • Create a temporary SynSet with name __temp_new_name__
   • 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 → Catalog.

2. Click the Three Dots Menu

   Find the SKU you want to use as the starting component and click the three dots (⋮) menu icon.

3. Select “Create Synset”

   Click Create Synset from the dropdown menu.

4. Enter SynSet Name

   In the modal dialog:

   • Synset: Enter a unique name for the SynSet (required, cannot be the same as the SKU)
   • Sku: Shows the selected SKU (read-only)
   • Click Create to create the SynSet

Completing SynSet Configuration

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

1. Complete Basic Information

   In the SynSet form (from SKU Substitutions method):

   • SynSet Name: Unique name to identify the bundle (required)
   • Description: Detailed description of the SynSet (optional)
   • Mix Max: Maximum allowed quantity for mixing/combining (optional, max 250 characters)

2. Add Component SKUs

   Add SKUs to the SynSet:

   • The initial SKU is already added (if created from Catalog method)
   • Use the “Assign” button to include products to the synset
   • Search or enter the SKU you want to include
   • Specify the Quantity of the SKU
   • Click Assign to add the SKU to the SynSet

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. Enable BOM SKU QTY (Optional)

   Check the BOM SKU QTY checkbox if you want the system to send BOM SKU quantities back to the marketplace or integrated system.

5. Select Shipping Method (Optional)

   If you want to use a specific shipping method for this SynSet, select it from the dropdown list. This shipping method will be used if the order contains only 1 unit of this item. The method will not apply if the order contains other SKUs.

6. Save the SynSet

   Click Save to save the SynSet configuration. The system will:

   • Create the SynSet with all component SKUs
   • Calculate available stock automatically
   • Update the SynSets list

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.

Stock Auto-Update

The system automatically updates SynSet stock when you load the SynSets list page (except when viewing a specific SynSet). Stock is recalculated based on component SKU inventory.

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.

BOM SKU (Bill of Materials)

The BOM SKU is a “virtual” SKU that represents the complete SynSet in external integrations:

• How It Works: When you assign a BOM SKU, that SKU is marked as “BOM” in your catalog (status_product = 'bom_sku' in history table)
• Main Use: Integrate with marketplaces (Amazon, eBay, Shopify) that require a unique SKU for the bundle
• Requirement: The BOM SKU must exist previously in your product catalog
• BOM SKU QTY: Checkbox option to enable/disable sending BOM SKU quantities back to the marketplace or integrated system
• Bulk Enable/Disable: You can enable or disable BOM SKU QTY for multiple SynSets at once using the checkbox in the table header

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”

Advanced Stock Management

The system automatically updates SynSet available stock when:

• You load the SynSets list page (stock is recalculated for all SynSets)
• Inventory is received for any component SKU
• An order including the SynSet is completed
• A component SKU’s inventory is manually adjusted

Stock Calculation Formula:

SynSet Stock = MIN(SKU Stock ÷ Required Quantity) for all SKUs

Stock Update Process:

• When you open the SynSets list, the system calls Synset->updateStock() for each SynSet
• Stock is NOT updated when viewing a specific SynSet (a=view)
• The calculation uses UnitsInStock and QtyGood from the products table
• If “Include DC quantities to Synset availability” is enabled in Distribution Centers, external DC inventory is also considered

Edit an Existing SynSet

1. Access SKU Substitutions

   Navigate to Inventory → Catalog, then click SKU Substitutions button.

2. Go to SynSets Tab

   Click on the Sets (Synsets) tab in SKU Substitutions.

3. Select the SynSet to Edit

   Find the SynSet you want to modify in the list and click on the the three dots (⋮) menu icon.

4. Update Information

   Modify any of the following fields:

   • SynSet Name: Unique name (cannot duplicate existing SynSet names)
   • Description: Detailed description
   • Mix Max: Maximum mixing quantity (max 250 characters)
   • BOM SKU: Enter SKU code (must exist in catalog)
   • BOM SKU QTY: Checkbox to enable/disable sending quantities back to marketplace
   • Shipping Method: Select from dropdown (optional)

5. Add or Remove SKUs

   • To add SKUs: Use the “Assign” button to include products to the synset
   • To remove SKUs: Use the delete option in the component SKUs list

6. Save Changes

   Click Save to confirm modifications.

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.

View SynSet Details

To view detailed information of a SynSet:

1. Access SKU Substitutions

   Navigate to Inventory → Catalog, then click SKU Substitutions button.

2. Go to SynSets Tab

   Click on the Sets (Synsets) tab to view details of the SynSets with the next information:

   • Set (Synset): Name of the Synset
   • Description: Full description text
   • Sku/UOM: Component SKUs and their quantities
   • Created Date: Date and time the SynSet was created
   • Available Stock: Current calculated stock
   • Mix Max: Maximum mixing quantity
   • BOM SKU: Assigned BOM SKU code
   • BOM SKU QTY: Whether BOM SKU QTY is enabled (Yes/No)
   • Shipping Method: Shipping method used for the SynSet
   • Allow Division: Whether to allow division of the SynSet into smaller units
   • Instructions: Special packing instructions or attachments
   • Attachment: Attachment file for the SynSet
   • Template: Template used for the SynSet

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 → Catalog, then click SKU Substitutions button.

2. Go to SynSets Tab

   Click on the Sets (Synsets) tab.

3. Export Data

   Use the export buttons in the table toolbar:

   • CSV: Exports current SynSets data to CSV format
   • EXCEL: Exports current SynSets data to Excel format

   Files are named automatically: synsets_YYYY_MM_DD_HH_mm_ss.csv or .xlsx

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. Navigate to Upload SynSet Page

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

2. Download Template

   Click the Download Template dropdown button to see available templates.

3. Select Template

   Choose a template from the dropdown list. Templates define the field mapping structure for your CSV files.

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. Navigate to Upload SynSet Page

   From SKU Substitutions → Sets (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

   • Click Choose or drag sets (synsets) file… and select your CSV file
   • Click Upload button
   • The system will upload the file and redirect to the mapping page

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 Set (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)

Legacy Upload Method (OLD VIEW)

If you prefer the older upload interface:

1. From the Upload SynSet page, click OLD VIEW button
2. This opens popup_synsetUploadCsv.php in a popup window
3. Upload your CSV file using the legacy interface
4. Optionally check Delete SynSet to remove existing SynSets before importing

CSV Import Requirements

• SynSet names must be unique: If a SynSet name already exists, the import will fail for that row
• All SKUs must exist: All SKUs mentioned in the CSV must exist in your product catalog
• CSV format: Use standard CSV format with comma-separated values
• Field mapping: If your CSV headers don’t match standard names, you’ll need to map them in the visual interface

Upload History

Access your upload history by clicking the dropdown arrow next to “OLD VIEW” and selecting Upload history, or visit MasterUploadInventorylist.php directly. This shows all your CSV upload attempts with results and status.

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.

💡 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.

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 the BOM SKU QTY option if the integration requires it
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.

Common Use Cases

1. Gift Sets and Promotional Bundles

Create SynSets for seasonal offers:

• “Valentine’s Day Gift Set” (chocolates + flowers + card)
• “Back to School Bundle” (backpack + notebooks + pencils)
• “Holiday Special Pack” (decorations + candles + treats)

2. Complementary Product Kits

Group products that are used together:

• “Skincare Routine Kit” (cleanser + toner + cream)
• “Coffee Lover Bundle” (coffee + mug + filters)
• “Artist Starter Pack” (brushes + paints + canvas)

3. Products with Components

For products shipped in parts:

• “Furniture Set” (table + 4 chairs)
• “Gaming Setup” (console + controller + HDMI cable)
• “Kitchen Appliance Kit” (blender + accessories + recipe book)

4. Quantity Discount Offers

Create quantity bundles:

• “3-Pack Protein Bars” (3x protein)
• “Family Size Combo” (4x individual servings)
• “Bulk Pack Socks” (6 pairs of socks)

Convert SynSets to Aliases

You can convert SynSets to SKU aliases (translations) for use in specific channels:

1. Click “Convert to Aliases”

   Located in the SynSets page header.

2. Select SynSets to Convert

   Select the SynSets you want to convert from the list.

3. Choose Channel (Optional)

   Select a specific channel/filename if you want the aliases to be channel-specific, or leave blank for account-wide aliases.

4. Confirm Conversion

   The system will:

   • Check that the SynSet name is not already used in inventory, translators, or UOM
   • Create SKU translations (aliases) for each component SKU using the SynSet name
   • Delete the SynSet after successful conversion
   • Show errors if any SynSet cannot be converted (e.g., name conflict)

Conversion Requirements

• The SynSet name must be unique and not already exist in products, translators, or UOM tables
• All component SKUs must exist in your catalog
• After conversion, the SynSet is deleted and cannot be recovered

Related Pages

Next Steps:

• Product Management - Learn to create and manage individual SKUs that will form part of your SynSets
• Product Catalog - Explore how to organize your complete catalog including SynSets
• Integrations - Configure SynSet synchronization with external marketplaces

See Also:

• Creating Products - Create the component SKUs needed for your SynSets
• Distribution Centers - Manage SynSet inventory across multiple warehouses
• SKU Management - Learn about SKU aliases and translations