📍 Bolt Help / Platforms / Netsuite ERP / NetSuite ERP - Managed Checkout
NetSuite ERP - Managed Checkout
Learn how to integrate, configure, and update Bolt for NetSuite ERP.

The following setup guide is for merchants using NetSuite ERP for their operational activities. In this scenario, Bolt’s NetSuite ERP Bundle passes data directly from Bolt to NetSuite ERP. For other integration scenarios that involve a third-party connector (Celigo, Folio, etc), refer to your connector’s installation guides instead.

WARNING

Bolt supports Checkout for NetSuite ERP, not NetSuite’s SuiteCommerce Advanced plugin.

Before You Start

If you are migrating from a different cart platform, see the Re-platforming section.

Supported Features

Feature, Linked to Operations Guide
Create Orders in NetSuite ERP
Void Transactions
Capture and Partially Capture Cash Sales and Invoices
Refund Cash Sales and Credit Memos
Generate Links for Pay-By-Link
Re-Authorize / Recharge on Expired Cash Sale and Invoice Transactions

How to Install

NOTE

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.

Step 1: Add Bundle

  1. Log into the NetSuite Console.
  2. Navigate to Customization > Site Bundler > Search & Install Bundles. Customization Menu
  3. Search for Bolt Checkout (or the use the Bundle ID 273377). Search for the Bolt Bundle
  4. Select the bundle.
  5. Select Install. Install the Bolt Bundle

Step 2: Configure Bundle

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 API key, found in the Merchant Dashboard.

NOTE

There should only ever be one Bolt Configuration record. If the Bolt credentials need to be updated, the original record should be updated.

  1. Navigate to Customization -> List, Records, and Fields -> Record Type.
  2. Scroll to the Bolt Configuration row.
  3. Select List. Selecting the Bolt Configurations record
  4. Select Edit on the role-type you will assign to Bolt.
  5. Select the subsidiary that you want to create this configuration for.

2A. For sandbox:

  1. Select Sandbox Mode.
  2. In Sandbox API Key, add your Bolt API key found in the Merchant Dashboard. Make sure to use the key for your NetSuite division.
  3. Add your Sandbox Unindemnified Publishable Key. Adding credentials to the configuration record

2B. For production:

  1. In API Key, add your Bolt API key found in the Merchant Dashboard. Make sure to use the key for your NetSuite division.

Step 3: Add Webhook Endpoints in Merchant Dashboard

  1. Navigate to Customization > Scripting > Script Deployments.
  2. Find the script with the ID customdeploy_bolt_webhook_call (Filters > Script > Bolt Webhook Call).
  3. Select View.Bolt Webhook listview in Script Deployment section
  4. Copy the Webhook’s External URL.

NOTE

For multiple subsidiaries: appended the webhook URL with &subsidiary=<subsidiary id>.

Subsidiary IDs

  1. Navigate to the configuration record that you created: Customization > Lists, Records & Fields > Record Types.
  2. Find the Bolt Configuration row and select List.
  3. Select on View beside the configuration record that corresponds to the subsidiary that you want.
  4. Select the merchant’s subsidiary name.
  5. Find the Internal ID. This is the Subsidiary ID.

4.Add NetSuite IP Addresses to Bolt’s Auto-Approved Domains

  1. Log in to the Bolt Merchant Dashboard.
  2. Navigate to Settings > Checkout.
  3. Scroll to Auto-Approved Domains.
  4. Select Edit. A dialog box will open.
  5. Select + Add Domain. A blank text field will appear.
  6. Type the domain URL into the field.
  7. Select Update.

Optional Settings

You can review the following settings using these steps:

  1. Navigate to the configuration record that you created: Customization > Lists, Records & Fields > Record Types.
  2. Find the Bolt Configuration row and select List.
Setting Enabled Disabled
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.

Order Flow Customizations

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.

  1. Log in to NetSuite.
  2. Navigate to the Custom Settings sub-tab.
  3. Select Bolt Configuration.
  4. Check the Use Custom Settings checkbox.
  5. Populate the field Order Status by selecting Pending Fulfillment from the list.
  6. To add additional fields:
    • Scroll to Bolt Fields to Set sublist
    • Enter the internalid, type, and value of the field present on the sales order you wish to update.
  7. Save.

Example

A custom flow where Bolt’s transaction completed status updates status of the sales order from pending approval to pending fulfillment.

Delayed Capture Use Case

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:

  1. An order is created on the shopping cart platform via Bolt Checkout.
  2. The Order is then populate in NetSuite using a third-party connector.
  3. The Order gets processed in NetSuite (voided, captured, etc) and handled by Bolt.

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: hardcode string == 'authorized' If you are doing Auto-Capture: hardcode string == 'completed' BigC does not store the Bolt transaction status. transaction_state transaction_state If you are doing Manual Capture: hardcode string == 'authorized' If you are doing Auto-Capture: hardcode string == 'completed' WooC does not store the Bolt transaction status.

Update Bundle

WARNING

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.

  1. Navigate to Customization > SuiteBundler > Search & Install Bundles > List.
  2. Find the Bolt Checkout Bundle.
  3. Section Action > Update.

Uninstall Bundle

  1. Navigate to Customization > SuiteBundler > Search & Install Bundles > List.
  2. Find the Bolt Checkout Bundle.
  3. Section Action > Uninstall.

Additional Resources


Re-platforming

When re-platforming, you must keep in mind all of the following:

  • Use the Merchant Dashboard for order refunds. Do not use a platform-specific backoffice flow that’s connected to a deprecated account division.
  • Disable all of your old webhooks for the deprecated account division.
Filter by Section
Filter by Topic