The following setup guide pertains to merchants who want to use NetSuite for their operational activities. In this scenario, Bolt NetSuite passes data directly from Bolt to NetSuite. For other integration scenarios that involve a third-party connector (Celigo, Folio, etc), refer to your connector’s installation guides instead.
Before beginning installation, reach out to your Customer Success Manager to get set up with another division on your account. You must also add NetSuite’s IP addresses to the Bolt Merchant Dashboard.
You must create a role record assigned to Bolt for each subsidiary store that is using Bolt Checkout. This role record must include your Bolt production keys, found in the Merchant Dashboard.
There should only ever be one Bolt Configuration record. If the Bolt credentials need to be updated, the original record should be updated.
customdeploy_bolt_webhook_call(Filters > Script > Bolt Webhook Call).
For multiple subsidiaries: appended the webhook URL with
domain URLinto the field.
You can review NetSuite order statuses and platform operations in our Platform Operations guide.
You can review the following settings using these steps:
|Auth Capture||Immediately authorizes and then captures the payment after entering credit card information into the Bolt Checkout window.||Authorizes the payment only; the transaction is only captured after Billing the order in NetSuite.|
|Sandbox Mode||Directs orders to your Bolt sandbox environment.||Directs orders to your Bolt production environment.|
|Recharge Enable||Enables ability to add items to an existing order that has already been authorized.||Disables ability to add items to an existing order.|
|Auto Capture on Recharge||Immediately captures any additional modifications made to a Sales Order that has already been authorized. Requires Recharge Enable.||Disables capture of additional modifications to the Sales Order until the Sales order has been billed.|
|Enable Skip Hook Notifications on Refunds||Prevents Bolt from sending a webhook that notifies all other divisions that the transaction has been refunded.||Send a webhook to notify other divisions associated with the merchant that the transaction has been refunded.|
You can define custom flows for sales orders that rely on the transaction status from Bolt using a Bolt Configuration custom record. You can also have some standard/custom fields set by our system, this can be configured in the Bolt Fields to Set sublist on a Bolt Configuration record.
Pending Fulfillmentfrom the list.
valueof the field present on the sales order you wish to update.
A custom flow where Bolt’s transaction
completed status updates status of the sales order from
pending approval to
The following use case can be set up by defining a Bolt Fields to Set sublist on a Bolt Configuration file. These optional field mappings enable merchants to suit the following use case:
To accommodate this, the Bolt Transaction Status (
custbody_bolt_transaction_status) and Bolt Transaction Reference (
custbody_bolt_reference_number)fields must be passed into NetSuite and mapped to the related fields unique to the eCommerce platform (Magento Commerce, BigCommerce, etc).
|Name||NetSuite Field name||BigCommerce||Magento 1||Magento 2||WooCommerce|
|Bolt Transaction Reference||custbody_bolt_reference_number||From the OrderNotes field, parse out the transaction ref number Example: Payment Transaction ID GHRC-CMHK-CYRD (This is appended to the end of the order notes field)||transaction_reference||transaction_reference||bolt_transaction_reference_id|
|Bolt Transaction Status||custbody_bolt_transaction_status||If you are doing Manual Capture:
||transaction_state||transaction_state||If you are doing Manual Capture:
You are not able to revert to a previous version after upgrading your Bolt bundle for NetSuite ERP. Ensure you are ready to adopt upgrades before consuming the update.