eCommerce apps best practices to optimize throughput and performance during high-volume periods (holiday season)

Contents

• Common leading practices for all eCommerce integration apps
  • Concurrency
  • Batch size and page size
  • Export and import
  • Optimize multiple connections in your integration app
  • Other leading practices
  • Other factors that drive NetSuite performance
• Shopify - NetSuite integration app
• Amazon - NetSuite integration app
• eBay - NetSuite integration app
• Magento 2 - NetSuite integration app
• Payout to Reconciliation Automation for NetSuite
• Square - NetSuite integration app
• BigCommerce - NetSuite integration app

This article provides an overview of the eCommerce integration app leading practices and recommendations for the holiday season to achieve maximum throughput. Follow these recommendations to prepare your integrations to handle a high volume of data efficiently during the holiday season when order volume is high.

Common leading practices for all eCommerce integration apps

Multiple factors impact throughput, including:

Concurrency

Concurrency is defined as two or more events processing at the same time. Each page is processed by a thread or concurrency. If the concurrency is higher, then more pages are processed in parallel. For more information, see Govern concurrency of NetSuite connections.

Example: In NetSuite, if you have a SuiteCloud Plus license, let's say the integration app concurrency per integration tile is 10. This means that the NetSuite account can manage 10 parallel requests at a given time. Therefore, the throughput of the system is directly linked to the concurrency setup.

Note: The concurrency is applicable only for imports. It is not applicable when data is exported from the source application. Concurrency specific to the other applications is covered in its respective integration app section.

Concurrency calculation in NetSuite

SC = SuiteCloud Plus license

The number of concurrent requests = NetSuite Service Tier + Number of SC plus licenses.

Example: For tier 3 NetSuite licensed accounts, the available concurrency is 5 and for each SuiteCloud Plus license, the available concurrency is 10. On a total for Tier 3 and 2 SuiteCloud Plus licensed accounts, the available concurrency is 25 i.e., 5 + (2*10)

You can view this final number in NetSuite at Setup > Integration > Integration Management > Integration Governance. To increase the concurrency further, contact NetSuite support.

For more details about NetSuite tiers and concurrency cheat sheets, refer to these documents.

Important: As of now the integrator.io platform supports a maximum of 25 concurrency per connection. If you require higherNetSuite integration concurrency, we recommend you create a secondary connection and partition flows to use the two connections (currently supported only for the Amazon - NetSuite integration app).

Batch size and page size

• Batch size is defined as the number of records fetched in a single request. This parameter is only applicable for the NetSuite export.
• Page size is defined as the number of records to be processed per page. This parameter is applicable to the destination application.

How does the batch size work in accordance with the page size?

If you define the batch size as 500 and page size as 25 when you make a request to NetSuite, it responds back with 500 results that are equally divided into 20 pages (25 records per page). The batch size and page size also depend on the concurrency set on the respective connection. If the concurrency is set to 3, the integration app submits 3 pages at a time. You have to define batch size, page size, and concurrency logically.

Example: For the inventory export flow, if you set the batch size as 1000, page size as 100, and concurrency as 5, in this scenario, the integration app processes a minimum of 100 items and a maximum of 500 items per request. If the concurrency is not used by the other integration app flows, then the integration app processes a maximum of 500 items per request.

Export and import

Any integration flow has export and import page processors.

• Exports are used to extract data from an application and can run standalone. From an integration flow perspective, the data is exported from an application in pages. Each page contains a set of data records from the application. For more information on exports, see Export data from NetSuite and Preview export data.
• After the integration flow-export side runs, it starts to create and assign pages to the import (in an asynchronous manner). Based on the concurrency set on the import connection, the pages are consumed in parallel.

Important: If the flow fails with SSS_TIME_LIMIT_EXCEEDED error, then reduce the “batchSize” in the export, so that there are fewer records in a single page to be processed by the import.

Optimize multiple connections in your Integration App

You can add additional connections to a single endpoint through which you can exercise greater control over the volume of data that is requested through the connections. This flexibility is key to getting high-volume flows to run more quickly.

When you set up multiple connections for flows based on logical prioritization rules and available “concurrency,” you can optimize the connections for improving data throughput to your API app, file server, or database system.

For more information, see Optimize multiple connections in your integration app flows for better throughput.

Other leading practices

• Schedule your integration flows in different quarter hours.
  
  Example: If you schedule the inventory flow at 12:10, schedule the fulfillment flow at 12:25, rather than having the same scheduled time.
• In NetSuite, the Log Level of all the Celigo scripts should be Error. To verify this, in NetSuite, go to Customization > Scripting > Scripts. Use the Bundle ID or Celigo, which is prefixed to the names of all the scripts, to identify Celigo Scripts. For each script, go to Deployments and set Log Level to Error.
• In the integration app > Settings > Inventory section, uncheck the Always sync inventory levels for the entire catalog checkbox to avoid syncing the inventory levels for the entire catalog. Instead, sync only a few items that have changed since the last time the flow ran.
• We recommend loading all items before the holiday season. During the holiday season, lower the frequency of item export to as low as once per day. Item export is a data-intensive flow. Therefore, it consumes a lot of processing capacity and time.
• You must refrain from bulk retries, especially for the low priority flows.
• For Inventory, Item, or Pricing flows, do not process retries for old errors because the data can be outdated.
• Don’t change the key settings or mappings just before the holiday season.

Other factors that drive NetSuite performance

In NetSuite, you need to identify the number of import scripts or workflows deployed on the NetSuite record from Customization > Scripting > Scripting Records. Many times your NetSuite account might have a user event script or workflow that reduces the performance and throughput. We recommend reducing or optimizing the scripts that are performing heavy processing. You can contact NetSuite support to identify such user events (refer to the below image for the typical data provided by NetSuite support).

These scripts can significantly increase the record creation time in NetSuite. We recommend running the on-demand flow to import a single record in NetSuite and check the time required to import it.

Based on the integration app settings, records might be resubmitted in NetSuite (for instance for overwrite tax), which might slightly increase the record creation time or update time. In this scenario, we recommend using the Default NetSuite customer if missing on the order in the integration app Settings > Order section > Customer sub-tab.

Shopify - NetSuite integration app

Connections

• Increase NetSuite connection's concurrency level. However, considering NetSuite limits, the concurrency level should not be more than 15. To do this, go to Connections. Next to the NetSuite connection, below Actions, click on the three-dotted icon > Edit connection > Advanced > Concurrency Level.
• Shopify concurrency: The recommended concurrency for Shopify (standard) users is 1 and for Shopify Plus is 3. The assigned concurrency is applicable for all the linked integration flows for that particular connection. If you require more concurrency, we recommend creating a Private App. Shopify provides additional concurrency to any private app connection as per your business needs.

Limitation: Shopify accepts only 2 API requests in Shopify (standard) edition and 4 API requests (Shopify Plus) per second. For more details, see Shopify API rate limits.

Important: The integration app does not support Private App connections if you’re using real-time integration flows.

Sandbox environment integrations

In Shopify, the rate limits work as per Application-Store combination. It's better if you disable all the sandbox environment flows to see maximum throughput for the production environment flows.

Order sync from Shopify to NetSuite

• The Shopify order to NetSuite cash sale (add) and Shopify order to NetSuite sales order (add) real-time flows can sync only one order per page. During the holiday season, it is recommended to run the Shopify order to NetSuite order (cash sale or sales order) batch flow as it syncs multiple orders per page.
  
  Note: During the non-holiday season, it’s recommended to enable the real-time flows to sync Shopify orders to NetSuite. Run the Shopify order to NetSuite order (cash sale or sales order) batch flow once or twice a day.
• Increase the NetSuite connection concurrency to a higher level as required.
• Shopify order to NetSuite order (cash sale or sales order) batch flow:
  • To run this flow, we strongly recommend selecting the Creation time option in the Filter orders by setting. (Flows > Order > next to Shopify order to NetSuite order (cash sale or sales order) ” flow settings).
  • We recommended entering very minimal lagOffSet in the Lag time to update the order status setting (Flows >  Order > Shopify order to NetSuite order (cash sale or sales order) flow settings) based on the business use case.
    
• For specific order imports, we recommend running the Sync Shopify order on-demand to NetSuite (add) flow.
• To reduce the item lookup errors, enter a value in the NetSuite SKU field setting and provide default values in the NetSuite item to track order lines when no matching SKU is found in NetSuite and NetSuite item to track Shopify order lines with no SKU value settings ( Settings > Order section > Item tab).
• Undeploy unnecessary scripts on the NetSuite sales order and cash sale (only if you’re sure).
• For the integration app premium edition users, check the Buy online, pick up in-store setting (Settings > Order > POS tab) only if the Shopify POS feature is applicable. This will avoid unnecessary calls to fetch the order fulfillments during order import.

Tax setup

• Set up tax codes/components properly in NetSuite or use the integrator.io tax configuration in the Settings > Order > Tax sub-tab:
  • Add total tax against single line item on the order OR
  • Overwrite taxes with tax with Shopify tax amounts with the Assign the default tax code to all orders checkbox checked.
• Using a proper tax setup will help to reduce the variance and also reduce extra NetSuite API calls to fix the variance.
• Ensure that the GST/VAT related settings are in sync in both Shopify and the integration app.

Customer sync

• From Shopify to NetSuite
  • Use the Default NetSuite customer if missing on Shopify order setting (Settings > Order section > Customer sub-tab) if customer details are not needed in NetSuite. You can sync the customers later using the Shopify customer to NetSuite customer (add or update) flow.
    
    Note: In this scenario, the customers are not linked to the orders.
  • Try to run the Shopify customer to NetSuite customer (add or update) and NetSuite customer to Shopify customer (add or update) flows before the holiday season and update customer data in Shopify and NetSuite to sync the data ahead.
  • Important: We recommends not running the Shopify customer to NetSuite customer (add or update) flow during the holiday season. If you run the Shopify order to NetSuite cash sale (add) or Shopify order to NetSuite sales order (add) flows, the customers are synced to NetSuite with the required data such as email ID, phone number, first name, and last name. And, if you run the customer flow after the holiday season, the integration app ensures duplicate customer records are not created and only updates the existing customer records accordingly.
• From NetSuite to Shopify
  • The NetSuite customer to Shopify customer (add or update) flow is updated as part of the Shopify - NetSuite integration app release and all customers are expected to have this updated before the holiday season.
  • We recommend that you sync customers from NetSuite to Shopify before the holiday season.
  • Set the batch size of the NetSuite export and concurrency of the Shopify import logically to avoid any bottlenecks.
  • In order to sync the line-level address data to Shopify, it’s important to set the “Shopify Store” custom field with the correct store ID on the Address sub-record.
  • To avoid conflicts do not schedule the Shopify customer to NetSuite customer (add or update) and NetSuite customer to Shopify customer (add or update) flows to run at the same time.

Transaction sync from Shopify to NetSuite

• Typically, the Shopify transaction data is synced to NetSuite for credit card reconciliation purposes. If the transaction data in NetSuite is not being leveraged, the Shopify order transaction to NetSuite custom transaction record (add) flow can be temporarily or permanently disabled (Flows > Order).

Inventory sync from NetSuite to Shopify

• Run the NetSuite inventory to Shopify inventory (add or update) and NetSuite kit and item group inventory to Shopify inventory (add or update) flows in delta mode to increase the performance by selecting the appropriate export batch size. To increase performance at the Shopify end, consider the Private App option:
  1. Create a private app in your Shopify account.
  2. Authenticate a new connection in your integrator.io account, using the private app details.
  3. Assign this new connection to the high-volume integration flows.
• Sync your inventory levels in advance of the holiday season and run as per the delta-mode during the sale time.
• Uncheck the Always sync inventory levels for the entire catalog checkbox (Settings > Inventory) to avoid setting a large amount of data to Shopify.
• Run the Shopify product ID to NetSuite item (mass update) flow (Flows > Inventory) prior to the holiday season as it involves a large volume of data. Try to run it before so that both the systems (Shopify and NetSuite) are in sync.
  
  Example: Schedule the Shopify product ID to NetSuite item (mass update) flow once before the holiday season to ensure that the item ID map is synced between Shopify and NetSuite.

Items and matrix items sync (product) from Shopify to NetSuite

• Try to load all the items/matrix items before the holiday season. During the season, lower the frequency of Item export to as low as once per day.
• Bulk updates or mass updates to item records should be scheduled during non-peak hours, and preferably should be performed in batches.

Fulfillment sync 

• From Shopify to NetSuite
  • Schedule the Shopify fulfillment to NetSuite fulfillment (add) flow during non-peak hours.
  • For the Shopify fulfillment to NetSuite fulfillment (add) flow, on the export bubble, set the page size from 100 to 500 as appropriate.
• From NetSuite to Shopify
  • Schedule the NetSuite fulfillment to Shopify fulfillment (add) flow during non-peak hours with less frequency.

Refund sync 

• From Shopify to NetSuite
  • Schedule the Shopify refund to NetSuite refund (add) flow during non-peak hours.
  • Set the page size appropriately on the Shopify export bubble.
  • Ensure that the GST/VAT settings in Shopify and the integration app are in sync.
• From NetSuite to Shopify
  • Schedule the NetSuite refund to Shopify refund (add) flow during non-peak hours and with less frequency.

Shopify payout reconciliation add-on

• Avoid setting large offset values in the Lag to bring payout related records setting to ensure better performance. 
• If you uncheck the Different store and payout currency box and try to reconcile payments that have different currency in payout and store, the flow leads to an amount mismatch variance. In order to avoid an unnecessary variance calculation, we recommend checking or unchecking the Different store and payout currency box (Settings > Payout) depending on your integration app and store setup.
• We recommend running the Shopify payout transactions to NetSuite deposit flow on the immediate next date after you sync the orders to NetSuite as sales orders with customer deposits. This is to ensure that the open customer deposits are not accumulating. If you want to first create the billing records in NetSuite and then run the Shopify payout transactions to NetSuite deposit flow, ensure not to sync the sales orders until you import the previous day’s payout report.
  
  Example: If there are sales orders from 1,2,3,4 dates and the lag offset is defined as 3, the flow runs on the 5th and it picks the payout report of 2nd; that is, all of the orders that belong to the 1st are considered. In this scenario, you shouldn't bill the orders belonging 2,3,4, or at least 3rd and 4th on the same day. You must sync the payout report for the 1st and then proceed with billing the next orders to ensure that it does not exceed the 10,000 NetSuite transaction limitation.

Recommendation: We recommend not running the flows to reconcile during the sale period. You can sync the previous payouts of all sale days once the load on the below flows reduces. Along with that, you need to adjust the flow schedules and offset them accordingly so that during any flow run, bulk transactions are not exported exceeding NetSuite’s 10,000 transactions limitation:

• Shopify Order to NetSuite Order Add 
• Shopify Order to NetSuite Cash Sale Add 
• Shopify Order to NetSuite Order/CashSale Add 
• NetSuite Fulfillment to Shopify Fulfillment Add 
• Shopify fulfillment to NetSuite item fulfillment
• NetSuite Inventory to Shopify Inventory Add/Update 
• NetSuite Kit and Item Group Inventory to Shopify Inventory Add/Update 
• Shopify Product Id to NetSuite Item Mass Update

Amazon - NetSuite integration app

Connections

• Use Secondary NetSuite Connection for high volume or low priority flows exclusively. This will help in the faster execution of the high-priority flows.
  
  Examples: 

  • Assign high-priority flows, such as order sync, to the primary connection so that other integration flows don't block the queue.
  • Settlement flows generate higher volume and lower priority data so assign them to a secondary connection.
• Set the appropriate concurrency for both the primary and secondary NetSuite connections. The connection serving high-priority flows, such as orders and fulfilments, should have a higher concurrency count.

Concurrency

For different domain accounts belonging to the same region, Amazon shares the same request quota and restore limits. If you’re selling in multiple domains within the same marketplace region, it is recommended not to schedule any Amazon integration flows at the same time in multiple domains. This is to ensure none of the integration flows exceed the throttling limits.

Example: In the European marketplace region, if you’re selling in Spain and Italy domains, do not schedule the Amazon (FBA/MFN) order to NetSuite order flow at the same time for both the domains.

Order sync from Amazon to NetSuite

• Set the following recommended settings for the date filter so that the flow works in the delta mode.
  • Filter Orders By: Last Modified
  • Duration in Days: empty
  • Go Live Date: empty (in case the account is live for months now)
• Be sure to check the Dashboard for any errors. Resolve the errors and retry to sync the orders.
• The throttling limit for the ListOrders operation is restored to 1 request per minute with a maximum request quota of 6 at a time. So if there are more requests, MWS starts throttling. You can utilize the auto-retry mechanism; however, you can retry the data only up to 5 times. Then an error message is displayed on the Dashboard. You can retry the error to sync the details correctly. For more information, see Throttling: Limits to how often you can submit requests.
• We recommend using the Allocate FBA orders to below NetSuite customer(s) setting (Settings > Order FBA section > Customers tab) for the Amazon (FBA) Order to NetSuite Order Add flow. For more information, see Configure Amazon FBA order flow settings.
• It is recommended to specify the value as 0 in the Duration in days setting (Settings > Order (FBA/MFN) section > Order tab ) so that the flow doesn’t sync (export) duplicate records.

Tax setup

• Set up all tax codes/components properly in NetSuite or use the integratori.io tax configuration in the Settings > General section > Tax tab:
  • Add total tax against single line item on the order OR
  • Overwrite taxes with tax with Amazon tax amounts 
• Using a proper tax setup will help to reduce the variance and also reduce extra NetSuite API calls to fix the variance.
• The Enable GST/VAT for your marketplace setting (Settings > General section > Tax tab) allows a dynamic approach for the GST- related orders.
• If you have a static GST set up (same tax rate for all orders), in the Settings > General > Tax sub-tab, uncheck the Enable GST/VAT for your marketplace checkbox and enter the GST/VAT rate in the Enter GST/VAT rate to apply across all orders setting.
• If you have a dynamic GST set up (tax rate changes for all the orders), check the Enable GST/VAT for your marketplace and Apply the GST/VAT rate reported by Amazon checkboxes to deduct the tax from item amount and calculate the tax. 
• Check the Exclude Tax if Marketplace Tax Collection applies checkbox (Settings > General > Tax sub-tab) to avoid the tax collection if Amazon collects and remits tax (varies region to region and is decided by Amazon).

Fulfillment sync from NetSuite to Amazon

• Amazon validates tracking IDs entered while confirming shipments. Invalid tracking IDs provided at the time of shipment confirmation will result in a warning, but the shipment will be confirmed. But these invalid tracking IDs affect the valid tracking rates which impact your Amazon account. To avoid this scenario make sure you are submitting valid tracking IDs.
• Schedule the NetSuite Fulfillment to Amazon Shipment Add flow to submit only 15 requests to Amazon per hour.
  
  Example: Schedule the NetSuite Fulfillment to Amazon Shipment Add flow once in an hour with the batch size as 200, export size as 500, and page size as 100. In this scenario, we submit 5 requests.
  Tip: Try to submit a minimal number of requests to Amazon as the limit is 15 requests or a 5 MB integration app process size limit.
• Check the Automate shipment carrier mapping checkbox to (Settings > Fulfillment), to automatically map the shipping carriers in Amazon. Alternatively, the mapping has to be done manually using the field mappings page.

Inventory sync from NetSuite to Amazon 

• Uncheck the Always sync inventory levels for the entire catalog checkbox (Settings > Inventory) to avoid sending a large amount of data to Amazon.
• Schedule the NetSuite Inventory to Amazon Inventory Add/Update and NetSuite Kit Inventory to Amazon Inventory Add/Update flows with less frequency, such as once in two hours (based on your requirements) in the delta mode.

Product sync from NetSuite to Amazon

• Load all the items before the holiday season, and during the season, lower the frequency of Item sync to as low as once per day. Item export is a heavy flow and takes time and processing on Amazon to perform.
• Bulk updates or mass updates to the item records should be scheduled during non-peak hours, and preferably done in batches.

Pricing sync from NetSuite to Amazon 

• Run the NetSuite Item Price to Amazon Product Price Add/Update flow with less frequency.
  
  Note: We don’t recommend enabling this flow during the holiday season. However, as the price fluctuates during the holiday season, schedule this flow once in an hour only with the required set of mappings.
  
  
  Important: We recommended scheduling the fulfillment, pricing, and inventory integration flows accordingly, as they share the same concurrency limit of 15 feed requests per hour. Schedule the flow so that they do not overlap for the same marketplace region.

Auto-billing sync

• We recommend running the NetSuite Order to NetSuite CashSale/Invoice Add flow after the holiday season.

Settlement sync

• Settlement flows require a lot of processing and are a lower priority; avoid running the settlement flows during the holiday season.
• If required during the holiday season, we recommend allotting these flows to the secondary connection.

Amazon Transfer Order - InboundShipments add-on

• We recommend updating the inventory levels in Amazon well ahead of the sale period.

Amazon FBA return management and FBA inventory adjustments add-on

• We recommended to use these add-ons only once or twice a day.
• Configure these add-ons using the secondary connection where low priority flows are attached.
• The FBA inventory adjustments and FBA return management report operation share the throttling limits in Amazon. So at peak times, a report might get canceled because of this. We  recommended to schedule these flows in such a way that these two will never overlap.

eBay - NetSuite integration app

Order sync (eBay to NetSuite)

• Set the recommended settings for the date filter setting so that flow works in the delta mode:
  • Filter Orders By: Last Modified
  • Duration in Days: empty
  • Go Live Date: empty (in case account is live for months now)

Tax setup

• Set up tax properly in NetSuite or use the integratori.io tax configuration in the Settings > General > Tax sub-tab:
  • Add total tax against single line item on the order OR
  • Overwrite taxes with tax with eBay tax amounts with the Assign the default tax code to all orders checkbox checked.
• Using a proper tax setup will help to reduce the variance and also reduce extra NetSuite API calls to fix the variance.

Check the Exclude Tax if Marketplace Tax Collection applies checkbox in the Settings > General section > Tax tab in order to avoid the tax collection where eBay collects and remits tax (varies region to region and is decided by eBay).

Inventory sync (NetSuite to eBay)

• Uncheck the Sync All Inventory setting to avoid sending a large amount of data to eBay.
• When you sync the matrix item inventory from NetSuite to eBay, set the eBay integration app concurrency to 1. After you sync the matrix item inventory, modify the concurrency back to its original level.
  
  Note: We recommend you sync the matrix item inventory during the non-holiday season time.
• Disable the eBay Item Id to NetSuite Mass Update flow after you sync all of the Item IDs to all eBay items.

Item and Pricing sync (NetSuite to eBay)

• We recommend you sync the prices and heavy item update operations before the holiday season. If required, run these flows during the holiday season with low frequency.

Magento 2 - NetSuite integration app

Store setup:

• In the Settings > General section > General tab, select the correct stores that belong to your website in the Select active Magento 2 stores setting.
• If you’re unable to get the record from the newly added store views, then unselect one of the stores in the Select active Magento 2 stores setting and save. Resave the setting with existing and new stores.

Order sync

• Keep the Magento 2 instance optimized, cached, and compiled to improve the API response performance for the order import and item/inventory export.

Tax setup

• Set up tax properly in NetSuite or use the integratori.io tax configuration in the Settings > General > Tax sub-tab:
  • Add total tax against single line item on the order OR
  • Overwrite taxes with tax with Magento2 tax amounts with the Assign the default tax code to all orders checkbox checked.
• Using a proper tax setup will help to reduce the variance and also reduce extra NetSuite API calls to fix the variance.

Inventory sync (NetSuite to Magento2) 

• Uncheck the Always sync inventory levels for the entire catalog check box (Settings > Inventory) to avoid sending a large amount of data to Magento.

Item and images sync (NetSuite to Magento2)

• Try to load all of the items and images before the holiday season. During the season, lower the frequency of Item export to as low as once per day. Item export is a heavy flow that takes time and processing on Magento to perform.

Payout to Reconciliation Automation for NetSuite

The Payout to Reconciliation Automation for NetSuite solves the post-holiday season reconciliation so that the open transactions don’t exceed the existing limitation of 10,000 transactions.

• NetSuite limitation: Schedule the payout flows at regular time intervals to ensure that during any flow run the total volume of transactions to be synced doesn’t increase beyond 10,000.
• Ensure the lag offset is set to a minimal value to improve flow performance.
• For the PayPal payout transactions to NetSuite deposits flow, if the PayPal report has transactions in multiple currencies, ensure that the PayPal primary currency code setting is appropriately set. This will avoid any unnecessary variances during deposit import.
• We recommend clearing the open transactions before the holiday season to avoid the 10,000 transaction NetSuite limitation.
• Validate your account settings before the holiday season to avoid integration app setup errors.
• Ensure all of the order and refund transactions are synced with undeposited fund accounts and with the correct transactions IDs in their respective fields.
• Be sure that the bank deposit account and other GL accounts belong to the same subsidiary and currency.

Square - NetSuite integration app

As the Square-NetSuite integration app is based on a POS solution, you can sync the data normally following the integration app functionality. A few suggestions are:

• Consider scheduling the Square Order to NetSuite Cash Sale flow with a higher frequency.
• If possible, do not sync tenders.
  
  Note: Enable the Square Tenders to NetSuite Custom Payments flow if you have to sync refund imports of cash sales that have a gift card applied.
• Set up the Square POS locations and be sure they are synced and selected in the Select active Square locations * setting in the Settings > General section.
• If possible, leverage the customer sync and disable the Square Customer to NetSuite Customer flow. Adda default customer for all of the cash sales.
  
  Note: You can't sync these customers again.
  

• For cash refund sync, we recommend running the “Square Refund to NetSuite Cash Refund” flow with a lower frequency, such as once or twice a day for the entire holiday sale season.
• Be sure that the concurrency for the NetSuite connection is 2 or 3, as the remaining concurrency can be utilized for other integration apps.

BigCommerce - NetSuite integration app

• We recommend scheduling the NetSuite Item Image to BigCommerce Product Image Add/Update/Delete flow at a lower frequency.
• To avoid a high-volume data flow run, sync the products and their inventory levels before the holiday season.
• We recommend selecting only the required order statuses during the holiday season.
• Set and schedule the export frequency for the inventory and fulfillment flows as “delta.” 
• Schedule the fulfillment flow at a higher frequency. Example: Once in 15 minutes.