What is the difference between using a Sales Order as a Reference record and Item Fulfillment as a Reference record to import orders into ShipStation?

• Sales Order–> The integrationuses sales order as a base record and creates an order in ShipStation. Once a label is generated in ShipStation for the order, ShipStation Integration will create an item fulfillment record for the corresponding sales order in NetSuite with the tracking details.
• Item Fulfillment–>The integrationwill wait until an item fulfillment record created in NetSuite for the sales order, then it will use the item fulfillment record as a base record and create an order in ShipStation. Once a label is generated in ShipStation for the order, ShipStation Integration will update the existing item fulfillment record in NetSuite and changed the item fulfillment status to Shipped along with the tracking details.

What are the Benefits of using Sales Order vs Item Fulfillment flow?

• If Sales order flow is used, ShipStation Integration will automatically create an Item Fulfillment record in NetSuite.
• If Item Fulfillment flow is used, you will have the flexibility to choose which item on the sales order to be fulfilled (when you have multiple items and do not want to fulfill all of them).

How to populate some specific information (memo, gift message, etc,..) to ShipStation?

• Add the fields in the saved search results tab which you want to populate in ShipStation from NetSuite. After adding the required field in the results tab,add the same custom label in Integartor.io flow mappings and map it to the required ShipStation field (custom field1, custom field2, internal notes, etc……).
  

How to export the orders into SS even though they have back ordered items?

• Remove the formula in NetSuite saved search which is used for preventing the line items which are backordered.
  

How to export the weights based on the unit of measurements?

• If the UOM is ‘lb’ then just add weight and weight units in the NetSuite saved search result tab. If the UOM is ‘kg’ then add the below formula in NetSuite saved search result tab.

FORMULA: “CASE WHEN {item.weightunit} = ‘kg’ THEN {item.weight}*35.274 ELSE {item.weight} END”

How to populate the preferred bin number on the order in ShipStation?

• Add the preferred bin number field in NetSuite saved search result tab then add that custom label in matrix options in Integrator.io.
  

How to add billTo Party information on the order in ShipStation?

• Add the relevant field in NetSuite saved search result tab based on what information we need to populate in the 3rd party billing information in ShipStation and Integrator.io mappings.
  

How to import images with the sales order into ShipStation?

• Add the image URL (it should be a public URL) on the item record then add that field in the NetSuite saved search result tab using below formula.

FORMULA: “CASE WHEN {item.storedisplaythumbnail} IS NOT NULL THEN {item.storedisplaythumbnail} END”

NOTE: {item.storedisplaythumbnail} – this is the field name on the item record.

How to set ShipStation Age based on the order created date?

• To use the NetSuite date created for the age in ShipStation, please follow the below steps.

Add the following column to the saved search and label it as dateCreated.

Formula (Text): TO_CHAR({datecreated},’YYYY-MM-DD HH24:MI:SS’)

Add the mapping in IO – dateCreated paymentDate

How to export harmonization code for international orders in ShipStation.

We cannot import the Harmonization and country code details from NetSuite to ShipStation using the order flow but we can set those values using the product flow (Items – Update Items from NetSuite to ShipStation). In order to update that information, the items should already be present in ShipStation and are connected (the items in both the systems can be connected using Item ID Mass Update – Update ShipStation Item ID from ShipStation to NetSuite.

Please add the fields containing that information in the NetSuite saved search results and map them in the product flow to the below fields in ShipStation.

How to improve flow performance by adjusting page size and number of connections

Want to speed things up and make everything work better? Integrator.io has options for that!

Looking to control how records are handled? Find "page size" under export Advanced. Set how many records are processed per page—defaults are 1 for fulfillment flows, 50 for sales order flows (max 100).

Need to tweak things for different flows? This setting lets you do that, optimizing data handling for each one.

Choosing the perfect page size is key to keeping your flow running smoothly.

NetSuite loves small bites! Importing data with a page size of 10-20 works best. Going bigger slows things down, taking 4-10 seconds per transaction (imagine waiting 4 minutes for NetSuite to swallow just 20 records!). Large requests are risky, especially if the network hiccups or times out. Losing connection leaves you clueless about what made it and what didn't.

ShipStation prefers 100 record meals! Imports over 100 records per page choke on ShipStation's API. Stick to the limit to avoid import hiccups.

How fast your flow runs depends on how many connections it makes at once.

ShipStation likes small crowds – keep its concurrency at 5. That uses 40 of its 40 allowed calls per minute, maximizing flow without hitting limits. Going too high (10–25) triggers retries, slowing things down.

NetSuite is picky about numbers. It depends on your account's limits and usage. For small flows (500 item fulfillments daily), 1 connection is usually enough. But if you have extra concurrency available, boosting it can speed things up.

NetSuite Connection

ShipStation Connection

Want speed for your high-volume sales orders and fulfillments? Create a special NetSuite connection! This prevents bottlenecking and keeps other flows smooth. Integration Apps let you make as many connections as you need and process things in parallel with concurrency settings. When things are busy, creating a dedicated NetSuite connection for item fulfillment NetSuite imports keeps everything chugging along. No more slowdowns for other flows because fulfillment is taking its time, and no more fulfillment delays because other things are using the same connection. Win-win!