The supplier bundle for NetSuite allows users to integrate Logicbroker's services with their NetSuite transactions. This bundle handles:
- Pulling orders from Logicbroker into NetSuite as Sales Orders
- Sending NetSuite Item Fulfillment transactions to Logicbroker (as shipments)
- Sending NetSuite Invoice transactions to Logicbroker
- Sending any closed sales order lines to Logicbroker as a cancellation acknowledgement
- Pulling cancellation requests from retailers into NetSuite and cancelling the corresponding sales order lines
- Broadcasting NetSuite inventory to Logicbroker using Logicbroker's Broadcast API endpoint
It also features a saved search, "Logicbroker Failed Exports", which allows users to conveniently view all documents that have failed to export to Logicbroker.
In NetSuite, navigate to Customization > SuiteBundler > Search & Install Bundles. Search for “Logicbroker” and select the “Logicbroker Supplier Connector” SuiteApp bundle.
You will need either Administrator privileges or the SuiteApp Marketplace permission (formerly SuiteBundler permission) in order to access this screen in NetSuite.
On the bundle’s page, click the install button to install it on your NetSuite instance.
Once the bundle has been installed, navigate to Setup > Company > Preferences > General Preferences. Scrolling down, select the Custom Preferences tab. There will now be a section labeled “Logicbroker Supplier Connector”.
Enter your Logicbroker API key and select which endpoint to use. The API key can be found in the portal under API Authentication.
You can also configure what Logicbroker status to pull orders on and what status to update them to.
If your company uses a saved search for inventory instead of the native NetSuite inventory functionality, fill in the internal IDs of all inventory saved searches that should be broadcast to Logicbroker. The values can be comma or space separated.
There are separate API keys associated with your Stage (stageportal.logicbroker.com) vs Production (portal.logicbroker.com) so you will need to log into both to generate the key, if there is no key currently generated. Also be sure to match the API key with the proper API endpoint based on environment.
We recommend you start out with your staging environment. Once you've tested everything in the staging environment, switching over to production is as easy as using your production API key and changing the API endpoint to "Production".
In order for Logicbroker to best find the customer associated with the orders being pulled, please set up all NetSuite customers with their corresponding Logicbroker Company ID, found on the Logicbroker tab.
Scheduled SuiteScripts Usage
Under Customization > Scripting > Script Deployments, locate the Logicbroker Supplier Connector entries. Their IDs will all begin with “customdeploy_lbsupp_”.
Note that there are multiple inventory-related script deployments. If you have configured saved searches to be broadcast to Logicbroker, the Logicbroker Export Saved Search Inv deployment should be used. If you are using native NetSuite inventory functionality, the Logicbroker Export Inventory should be used. Logicbroker Send Search is a helper script for the saved search functionality and should not be scheduled.
For each of the script deployments, select Edit. You should see the following screen:
To run a script for testing purposes (not scheduled), leave the Status as “Not Scheduled” and select the arrow next to the Save button to choose “Save and Execute”.
To schedule the script, change the Status to “Scheduled” and adjust the Schedule tab to suit your needs and control how often the script will run. Then click Save.