The Item Master lies in NetSuite. With that, the product data needs to synced from NetSuite into Magento. This is one of the main pillars of the NetSuite Connector. As all Import processes the actual workflow execution starts in \RocketWeb\NetSuiteProduct\Model\Process\Import\Item::process(). The first part of the process is checking what to do with the Record - should it be imported (\RocketWeb\NetSuiteProduct\Model\Process\Import\Item::isMagentoImportable()). If it shouldn't be, an additional check is done to see if the Product linked to that Record already exists (\RocketWeb\NetSuite\Model\Product\Repository::countProductsByNetSuiteIds()). If it doesn't, the process skips the Record.

Most of the methods in the class call \RocketWeb\NetSuiteProduct\Model\Import\Item\Mapper::getInstance() and are just placeholders for methods that are being called. The reason for that lies with the mapping of the Item types in NetSuite and Product Types in Magento. By default, following mappings are done:

NetSuite Item Type	Magento Product Type	Instance Class
Item Group	Simple Product*	RocketWeb\NetSuiteProduct\Model\Mapper\Product\ItemGroup
Kit Item	Bundle Product	RocketWeb\NetSuiteProduct\Model\Mapper\Product\KitItem
Matrix Item	Configurable Product	RocketWeb\NetSuiteProduct\Model\Mapper\Product\MatrixItem
Inventory Item \| Assembly Item \| NonInventory Item	Simple Product	RocketWeb\NetSuiteProduct\Model\Mapper\Product\InventoryItem

* Item Group is supported only Partially

Those Instance Classes contain the logic for each specific Item type.

Process Inventory Item

This is the main logic (\RocketWeb\NetSuiteProduct\Model\Mapper\Product::mapInventoryItemToRowList()) that takes care of Product construct, data mapping and all specific logics that are needed for Magento to import a Product. Lets go thru the flow. First, we create a Product Placeholder (\RocketWeb\NetSuiteProduct\Model\Mapper\BaseData::createProduct()) as a DataObject. As part of Product Placeholder creation, we process the default fields (\RocketWeb\NetSuiteProduct\Model\Mapper\BaseData::addDefaultFieldsForNewProduct() - visibility/status/store scope/tax class/attribute set). Those are configuration values. We also set a Product name as its a required field in Magento. The Name can be overwritten by setting a custom mapping in the Configurations section which is the last part of Product Placeholder creation. It processes the Product mapping configuration.

SKU

The Product Mapping MUST contain SKU mapping. If that is not set, the SKU is not set and the code throws a DataIntegrityException.

Next part of the main logic is getting the Product Type (\RocketWeb\NetSuiteProduct\Model\Mapper\Product::getProductType()) which is then set to the Product Placeholder. Following that, we have a method \RocketWeb\NetSuiteProduct\Model\Mapper\Product::setProductData() which serves for easy Plugin access. Then we process the specific Item Type data by calling \RocketWeb\NetSuiteProduct\Model\Mapper\Product::setProductType() which is extended in each of the Instance Classes.

Once Product Type data is set, we process the Pricing. By default, we set the Base Price and Special Price. Those are based on NetSuite Item Pricing Matrix. As part of the Price setup, we also process group-specific prices (Tier Prices) which are then applied to the Product Placeholder.

One of the last steps is setting the Custom Attribute Values (\RocketWeb\NetSuiteProduct\Model\Mapper\Product::setCustomAttributeValuesBeforeMapping()). By default, those are:

nesuite_internal_id - its the internal ID of the record and used as a link between the systems
netsuite_last_import_date - it's used to skip Records that are pulled into the connector multiple times.

With all the main Product Placeholder data set, we trigger an Event netsuite_import_product_format_from_inventory_item_before which allows modifying the data if needed. The next step is to map the Related and UpSell products (\RocketWeb\NetSuiteProduct\Model\Prefetch\ProductPrefetchIdSource::mapToProduct()) and trigger a second Event netsuite_import_product_format_from_inventory_item_after. Once all of that is done, we make sure to clean up unwanted tags (\RocketWeb\NetSuiteProduct\Model\Mapper\BaseData::stripTagsForAddAttr()) and we add the Product Placeholder into a line for final import.

Product Import

The actual product import happens \RocketWeb\NetSuite\Model\ImportQueueManager::commit() which is described in Import process section.

Browser not supported