Order is Placed

As part of Export processes, the Order Export process also has two parts. The first part is located in an Observer \RocketWeb\NetSuiteOrder\Observer\OrderPlaceObserver::execute() and it has a simple workflow. If conditions:

Module is Enabled
Feature is Enable
Is not marked to be skipped

are all met, an Export Queue Message is created with Order ID attached to it & sent into the Queue. The Observer is linked into sales_model_service_quote_submit_success event which means it's triggered in all areas (frontend/adminhtml).

Transform Magento Order into NetSuite Sales Order

Before the transformation happens, the \RocketWeb\NetSuiteOrder\Model\Process\Export\OrderPlace::process() checks that the Order exists in Magento. The actual mapping happens in \RocketWeb\NetSuiteOrder\Model\Mapper\Order::getNetsuiteFormat().

Customer mapping

The first part of the mapping sets the Customer which is a sub-workflow, similar to Customer workflow. The method calls on \RocketWeb\NetSuiteCustomer\Model\Mapper\Customer::createNetsuiteCustomerFromOrder() which has a few pre-steps before calling the main \RocketWeb\NetSuiteCustomer\Model\Mapper\Customer::getNetsuiteFormat() mapping logic. The sub-workflow starts by extracting a customer from the Magento Order (thru ID or Email) and if it exists and has netsuite_internal_id it validates it against NetSuite and returns the ID. If it doesn't exist, it tries using externalIdString and email and if found, returns the ID. If all those tries fail, a Customer Placeholder is created and filled with information from the Order. The Customer Placeholder is then sent through \RocketWeb\NetSuiteCustomer\Model\Mapper\Customer::getNetsuiteFormat(). The rest of the process is the same as in Customer workflow.

Items

Once Customer ID is added to the Sales Order, Default Order Status is set, Location is set and OrderItemList is prepared. We loop through the Magento Order Items and check if we should skip an Item (Configurable/Bundle product is skipped as we send only the Simple product). We then add the Order Item to the Sales Order. Once all Items are processed, Discount logic is processed (\RocketWeb\NetSuiteOrder\Model\Mapper\OrderExport\Discount::addOrderLevelDiscount()). The Tax logic is handled in a separate module RocketWeb_NetSuiteTax and it takes care of preparing the Sales Order based on Configuration.

Discounts and Taxes

Afterward, Discounts and Taxes are set according to the configuration in Store Admin. For detailed logic refer to specific workflows ( 2024.1 Discounts and [techflow] Taxes ).

Shipping and Billing

The Address data mapping is hardcoded in \RocketWeb\NetSuiteOrder\Model\Mapper\OrderExport\Addresses::createAddress() and an Event netsuite_address_create_before is also triggered. Created Addresses are added to NetSuite Sales Order in \RocketWeb\NetSuiteOrder\Model\Mapper\OrderExport\Addresses::addAddresses().

Shipment mapping is processed from Configuration mapping in \RocketWeb\NetSuiteOrder\Model\Mapper\OrderExport\Shipment::addShipment(). The method \RocketWeb\NetSuiteOrder\Model\Mapper\OrderExport\Shipment::getNetsuiteShippingMethodInternalId() is used for Plugin access to allow modifications of Shipping Method used in NetSuite. The default Plugin is \RocketWeb\NetSuiteFulfillment\Plugin\NetsuiteShippingMethodInternalId::afterGetNetsuiteShippingMethodInternalId().

The payment data is split in two parts. The \RocketWeb\NetSuiteOrder\Model\Mapper\OrderExport\Payment::addPaymentMethodData() takes care of mapping the correct Payment method between Magento and NetSuite. The \RocketWeb\NetSuiteOrder\Model\Mapper\OrderExport\Payment::addPaymentProcessorData() is used to add Payment Processor data (Cybersource & PayPal are supported). In case of Cybersource, we support only Cybersource extension from Magedelight. It allows Authorization in Magento and Capture in NetSuite.

Custom Fields

The last part is the Custom Fields mapping (\RocketWeb\NetSuiteOrder\Model\Mapper\OrderExport\CustomFields::addCustomFields()). The mapping supports Standard & Custom fields in NetSuite. If you need to set a dynamic value for the Order, plugin around addCustomFields should be the correct place to do it.

Once the getNetsuiteFormat() is done, an Event netsuite_new_order_send_before is triggered allowing any global modifications if needed. We do recommend using the Plugin on getNetsuiteFormat() as Events should be used for async operations on data and not for modification of the data.

Debug

The getNetsuiteFormat() should be the main entry point for xDebug when trying to understand why a value is wrong on missing when Sales Order is created in NetSuite. For figuring out why Sales Order is NOT created in NetSuite, a better approach exists - see the How to figure out section.

Send AddRequest to NetSuite

The rest of the process() is simple. We create an AddRequest to create the Sales Order in NetSuite. The $response contains the Internal ID of newly created Sales Order which we attach to the Magento Order.

Browser not supported