Handling Inventory Items with Alias SKU
You should create separate inventory records for every item rather than creating alias stock keeping unit (SKU).
However, if you already have alias items for order processing, the NetSuite Connector can support them. Although requiring additional set up, the NetSuite Connector can support, for example, multiple SKUs in your marketplace or cart that should match with a single SKU in NetSuite when posting orders.
When using alias SKUs, you need to ensure that the ItemId for each SKU is unique when compared with any SKU across your NetSuite account. If multiple SKUs are associated with the same ItemId, it could result in posting to the wrong item in NetSuite.
The following methods enable you to handle or manage alias SKUs. Choose a method depending on your records and business scenario.
Method for Kit Items
This method will enable you to support product and order synchronization for your kit items.
For every alias of an item (for example, an item has an SKU called base), you should create a kit item that will have one component item, which will be the original item (base). The SKU of the kit item will be the alias SKU. No additional set up in the NetSuite Connector is required.
When orders are imported, they will import against the kit item, which will correctly commit inventory from the single component item.
Advantages
-
No additional set up in the NetSuite Connector is required.
-
The NetSuite Connector can synchronize these alias kit items to your marketplaces or carts.
-
If the items are synchronized to your marketplaces or carts, a kit item can contain additional data other than what is specified for the original item. A kit item can have a title, description and other information. NetSuite Connector still needs all the fields that a marketplace or cart requires populated for the kit or alias item. But the values for those fields are not referenced from the component or base item. This allows you to set different values for those fields on the alias item, rather than on the base item. But values must be specified for those fields.
-
This is a better approach than having alias SKUs. If you sell items under more than one listing, this approach enables you to manage them better.
Limitations
-
This method cannot be applied to matrix item types. If you have matrix items set up and need to support alias SKUs for these items, you should use the next method.
-
Kit items cannot be included on Transfer Orders. But if your alias SKUs need to be on transfer orders, you should use the next method.
Method for Custom Records
This method enables you to support product and order synchronization for your kit items.
To set up custom records to add aliases:
-
Go to Customization > Lists, Records, & Fields > Record Types > New.
-
In the Name field, enter a name for the record type, like Item Alias.
-
Ensure that the Include Name Field box is checked. The record names will be the alias SKUs.
-
Click Save.
-
Open the created custom record type and click the Fields subtab.
-
Click New Field.
-
In the Label field, enter a label, like Original Item.
-
In the Type dropdown field, select List/Record.
-
In the List/Record dropdown field, select Item.
For more information, see Working with Records, NetSuite Record Types and Creating a New Custom Record Type.
-
You can now create an alias item by adding new records of this type. A record name will be the alias SKU and it should have a single field for selecting the original item.
-
Open NetSuite Connector and go to Settings > Order. In Advanced Options and under the Alias SKU Settings section, enter the IDs and the field of the SKU alias records you created.
Using this method, every item can have several aliases. This means you do not need to add more fields for item aliases. As more aliases are needed, you do not have to remap anything in the NetSuite Connector when your adding them.