Articles in this section

Best practices to optimize e-commerce app throughput & performance during high-volume periods (holiday season)

Saikumar Rachamalla
Updated

This article outlines the best practices and readiness steps for managing e-commerce integrations during high order volumes. It includes a readiness checklist and an action plan to help you prepare before, during, and after the holiday season. You’ll find general and advanced best practices that apply across all integrations, along with app-specific recommendations to address high order volumes, prevent bottlenecks, and ensure smooth operations.

Holiday readiness checklist

Review and validate flows

  • Audit active flows (orders, billing, fulfillments, returns, and payouts) 

  • Test field mappings and settings for discounts, gift options, shipping methods, and tax fields.

  • Check flow schedules (real-time vs batch) to match peak demand.

  • Run sample test orders in the staging/sandbox environment, before the rush.

Monitor API and rate limits

  • Review platform API limits

  • Stagger or throttle flow runs to avoid hitting rate limit errors.

  • Enable concurrency controls and retry logic in the integration app. (Also, see: Monitor and manage retries for details on tracking and managing retry runs.)

  • For failed API calls, use the Auto-recover rate limit errors setting under the Advanced section of the connection.

  • Set NetSuite concurrency ≤15. Use a custom app connection if more throughput is needed.

Increase visibility and alerts
Data quality and inventory sync

  • Confirm real-time inventory sync (ERP - marketplaces) to avoid overselling.

  • Ensure consistency of SKU, pricing, and promotions across all systems.

  • Validate holiday SKUs and promotional items sync correctly.

    Note

    For troubleshooting during peak, monitor dashboards closely, adjust batch sizes if needed, and verify recent configuration or connection changes before escalating.

Capacity and scaling prep

  • Tune Celigo concurrency & throughput settings for peak traffic.

  • Clear old logs and optimize schedules to reduce bottlenecks.

  • Verify on-premise agent capacity and uptime monitoring (if applicable).

Business rule alignment

  • Update flows with holiday promotions (gift wrapping, free shipping thresholds).

  • Validate tax, duty, and compliance rules for marketplaces.

  • Ensure return/refund flows are enabled and tested.

Support and escalation plan

  • Submit a support ticket. 

  • Documentfallback proceduresfor critical flows.

  • Assign on-call coverage with at least one admin for urgent fixes.

Post-holiday planning

Customer action plan (before, during, and after peak)

Here’s a stage-wise plan with clear responsibilities and timelines.

Stage-wise action plan

What to Do / Check 

Role 

When 

Pre-season (4–6 weeks before peak) 

Inventory audit: 

Ensure all items, SKUs, and matrix items are loaded and matched across systems. Pre-sync product/item flows.

Integration Owner, Merch Ops

~6 weeks before

Run high-volume updates in advance:  

Complete bulk updates (e.g., Shopify product ID to NetSuite item mass updates) ahead of time to avoid delays during peak.

Integration Owner

~5–6 weeks before

Disable unused or non-critical flows: 

Turn off rare exports or low-priority syncs.

Integration Owner

~4–5 weeks before

Review NetSuite scripts: set Celigo log level to Error only; disable or optimize heavy workflows.

NetSuite Admin / IT

~4 weeks before

Plan concurrency:  

Set up additional connections/custom apps (e.g., Shopify). Test connection performance and allocation.

Integration Owner

~4 weeks before

Increase concurrency for high-priority flows: 

Raise concurrency for key flows (e.g., 20 for orders/customers). Keep back-office flows lower (e.g., 5). Respect integrator.io’s 25 concurrency per connection limit.

Integration Owner / IT

~4 weeks before

Adjust batch sizes: 

Reduce export batch size if flows fail with SSS_TIME_LIMIT_EXCEEDED (NetSuite’s 5-minute limit).

Integration Owner

~4 weeks before

Validate settings: 

Enable inventory delta sync and disable Always sync full inventory.

Integration Owner

~3–4 weeks before

Standardize configurations: 

Avoid changing mappings, logic, or key settings right before peak.

Integration Owner

~3–4 weeks before

Validate tax and account mappings: 

Confirm tax codes, currencies, and customer configurations to prevent extra API calls.

Finance and Integration Owner

~3 weeks before

Clean up open transactions:  

Reduce old or pending transactions to prevent exceeding NetSuite’s 10,000-transaction limit.

Finance / Integration Owner

~3 weeks before

Identify low-priority flows: 

Mark refunds, payouts, images, and other non-critical flows to throttle or disable during peak.

Integration Owner / Ops

~3 weeks before

During Peak 

Switch high-volume order flows (e.g., Shopify - NetSuite) from real-time to batch mode for better throughput.

Integration Owner

Ongoing

Monitor dashboards: 

Enable real-time alerts for failures, slowdowns, or connection throttling, and perform periodic reviews of connection status.

Engineering / Support

Daily

Stagger schedules: 

Avoid overlapping heavy flows (inventory, fulfillment, refunds). Use quarter-hour scheduling (e.g., inventory at 12:10, fulfillment at 12:25).

Integration Owner

Daily adjustments

Schedule during off-peak hours:  

Run fulfillment, refund, and other heavy flows during non-peak periods to reduce strain.

Integration Owner

Ongoing

Amazon-specific scheduling: 

Don’t overlap fulfillment, pricing, and inventory flows for the same region (Amazon allows only 15 feed requests/hour).

Integration Owner

Ongoing

Manage concurrency: 

Limit parallel flows on Shopify/NetSuite to avoid overload. Partition flows across primary and secondary connections — assign high-priority flows (orders/fulfillments) to primary and low-priority (settlements/refunds) to secondary.

Integration Owner / NetSuite Admin / IT

Ongoing

Run customer syncs only when necessary: 

Use the Default NetSuite customer if missing setting to minimize extra calls.

Customer Ops

As needed

Disable sandbox flows: 

Suspend non-production integrations during holiday season.

Integration Owner

During peak

Optimize lag time and page size: 

Use minimal lag for real-time freshness; larger page sizes improve throughput but test to avoid API/memory issues.

Integration Owner / Engineering

Ongoing

Post-peak 

Run reconciliation flows:  

Match orders, refunds, payouts, and deposits across systems.

Finance / Integration Owner

After peak subsides

Restore full catalog/item syncs and product flows. 

Integration Owner

Post-peak

Review metrics:  

Analyze error rates, latency, and throughput. Document lessons and optimizations for next season.

Ops / Engineering / PM

1–2 weeks post-peak

Clean up: 

Restore and optimize temporary settings. Re-enable any scripts or flows disabled for the holiday period.

Integration Owner / IT

Post-peak

Document configurations:  

Save tested batch sizes, concurrency levels, and lag settings for future use.

Integration Owner

Post-peak

Note

After the holiday season, process any backlogs, reset flow frequencies to normal, and reconcile transactions to ensure data completeness.

General best practices for holiday season (All e-commerce integrations)

General best practices

NetSuite performance

  • Concurrency Limits: To raise concurrency across NetSuite connections beyond your account limit, contact NetSuite Support. For more information, refer to Govern concurrency of NetSuite connections.

    • Check limits in Setup > Integration > Integration Management > Integration Governance.

  • Script Logging: Set all Celigo scripts’ Log Level = Error.

    Path: Customization > Scripting > Scripts > locate Celigo scripts (by bundle ID prefix) > open Deployments > set Log Level = Error.

  • Optimize scripts and workflows:

    • Go to Customization > Scripting > Scripting Records to identify how many scripts/workflows are deployed on a record.

    • Heavy user event scripts or workflows can slow down record creation. Work with NetSuite Support to optimize or reduce them. (refer to the typical data provided by NetSuite support)

  • Measure record creation time:

    • Run an on-demand flow to import a single record into NetSuite.

    • Check how long it takes to complete. This helps identify performance bottlenecks.

  • Resubmission impact:

    • To avoid order failures due to missing customers, enable the Default NetSuite customer if missing under: Integration app > Settings > Order > Customer subtab.

Shopify – NetSuite integration app

Critical actions for holiday season

  • Switch to batch order sync (multiple orders per page) instead of real-time. Use the Creation Time filter with minimal lag offset.

  • Pre-load items before peak; use delta mode; disable Always sync full inventory.

  • Set NetSuite concurrency ≤15. Use a custom app connection if more throughput is needed.

  • Disable Shopify to NetSuite customer flow; use the Default NetSuite customer if missing.

  • Run refunds/payout reconciliation off-peak; set fulfillment/refund page size 100–500.

  • Reduce the batch size for high-volume or resource-intensive flows, such as Order and Refund imports, to improve performance and reliability.

Detailed best practices

Concurrency and API limits

  • Shopify Standard: concurrency = 1.

  • Shopify Plus: concurrency = 3.

  • OAuth-based connection: concurrency = 4.

  • Create a Custom App connection for additional concurrency (basic auth only).

  • Shopify API limits:

Important

  • Do not assign real-time flows to custom app connections.

  • You will not be able to select the API version of the app; it is predefined for the integration app's connection.

Order sync

  • Use real-time flows (cash sale or sales order) when you need up-to-date data, as they process one order per page.

  • During peak, switch to batch flows, which process multiple orders per page for better performance.

  • Outside peak times, revert to real-time flows for freshness, and run batch flows once or twice a day as needed.

  • Use the Creation Time filter.

  • Set Lag for the next flow run and Sync Orders created prior to carefully to avoid missing/duplicate orders.

  • Run Sync Shopify order on-demand to NetSuite flow for specific imports.

  • Provide default NetSuite SKU/item values to reduce lookup errors.

  • Undeploy unnecessary NetSuite scripts if safe.

  • For premium users: enable Buy online, pick up in-store only if needed.

  • For Shopify Markets: enable Sync records in local currency.

  • Map each province to the corresponding non-inventory item for state taxes.

Tax setup

  • Configure tax codes properly or use integrator.io tax config.

  • Options:

    • Add total tax as a single line item.

    • Overwrite taxes with Shopify amounts + assign default tax code.

  • Ensure GST/VAT settings match across Shopify and NetSuite.

Customer sync

  • Shopify to NetSuite:

    • Use the Default NetSuite customer if missing.

    • Run customer sync flows before peak to update data.

Important

Do not run Shopify to NetSuite customer flows during the holiday season.

  • NetSuite to Shopify:

    • Run sync before peak.

    • Set batch size/concurrency logically.

    • Set the “Shopify Store” custom field on addresses.

    • Avoid scheduling customer syncs in both directions at the same time.

Transaction sync

  • Disable Shopify order transaction to NetSuite custom transaction if not needed.

Inventory sync (NetSuite to Shopify)

  • For high-volume flows, consider custom app connections.

  • Run Shopify product ID to NetSuite item (mass update) before peak.

Item/Matrix Item sync

Note

The REST flows are no longer supported. You must configure and start using the corresponding GraphQL flows instead.

  • Load all items/matrix items before the peak.

  • During the season, lower exports to once/day.

  • Run bulk/mass updates off-peak.

  • For Shopify Markets: confirm markets and price lists are set up.

  • Ensure metafields are defined/validated properly.

Fulfillment sync

Note

The REST flows are no longer supported. You must configure and start using the corresponding GraphQL flows instead.

  • Shopify to NetSuite: schedule off-peak; set export page size 100–500.

  • NetSuite to Shopify: schedule off-peak with lower frequency.

GraphQL flows considerations (Item/matrix item sync and Fulfillment sync) 

  • Shopify GraphQL APIs use cost-based rate limits of 100 points per second (limit varies depending on your Shopify store plan).

  • If throttling errors occur, reduce Shopify Connection concurrency to stay within rate limits.

    Note

    Avoid bulk retries on throttling errors. Allow the system to back off or retry later to prevent additional failures.

Refund sync

  • Shopify to NetSuite: schedule off-peak; set export page size appropriately; ensure GST/VAT settings match.

  • NetSuite to Shopify: schedule off-peak; select substitute items for adjustments.

Shopify payout reconciliation add-on

  • Avoid large lag offsets in payout flows.

  • Review the Different store and payout currency settings.

  • Run payout-to-deposit flows the day after order sync to avoid accumulating open deposits.

  • Set the Duration to reconcile transactions setting to limit the retrieval of older transactions and prevent over-fetching, which can slow down flow runs.

  • Adjust flow schedules/offsets to avoid exceeding NetSuite’s 10,000 transaction limit.

    Important

    Do not run reconciliation during peak; sync payouts after load reduces.

Optimize performance by configuring mappings (applicable for Fulfillment and Refund flows)

The recommended mappings unlock Celigo’s optimized import process for fulfillments and refunds, allowing the integration app to process high volumes more efficiently during peak.

For setting up these mappings, see Optimize performance by configuring fulfillment mappings and Optimize performance by configuring refund mappings.

Amazon – NetSuite integration app

Connection Concurrency

  • Do not schedule flows for multiple domains in the same region at the same time.

  • Amazon shares the request quota only across domains in the EU region.

  • In multi-brand setups, consider assigning available Celigo concurrency to a single parent connection and scheduling flows across apps from that connection to coordinate throughput.

    Important

    Do not schedule flows across multiple domains simultaneously (e.g., Spain + Italy in the EU marketplace).

Order sync (Amazon to NetSuite)

  • Set recommended filters for delta mode:

    • Filter orders by: Last Modified

    • Duration in days: empty

    • Go live date: empty

  • Always check the Dashboard for errors to resolve and retry.

  • Respect ListOrders throttling (1 request/min, quota of 6). Enable auto-retry. Limit fulfillment to 15 requests/hour. For more information, see Throttling: Limits to how often you can submit requests.

  • Use Allocate FBA orders to NetSuite customer(s) setting (Settings > Order FBA > Customers). For more information, see Configure Amazon FBA order flow settings.

  • Set Duration in days = 0 in Settings > Order (FBA/MFN) to avoid duplicates.

Tax setup

  • Configure tax codes in NetSuite or use integrator.io tax config.

  • Options:

    • Add total tax as a single line item, OR

    • Overwrite with Amazon tax amounts.

  • Enable GST/VAT:

    • Static GST to enter a fixed rate.

    • Dynamic GST to apply the reported rate.

  • Use Exclude Tax if Marketplace Tax Collection applies to avoid duplication when Amazon remits taxes.

Fulfillment sync (NetSuite to Amazon)

  • Amazon validates tracking IDs — invalid IDs lower your account’s valid tracking rate. Always use correct IDs.

  • Schedule NetSuite Fulfillment to Amazon Shipment Add with:

    • Batch size 200

    • Export size 500

    • Page size 100

      Important

      Limit to 15 requests/hour or 5 MB payload.

  • Enable Automate shipment carrier mapping (Settings > Fulfillment).

Inventory sync (NetSuite to Amazon)

  • Run flows in delta mode, less frequently (e.g., once every 2 hours).

  • Apply the same rules to Kit Inventory sync.

  • Run inventory/product syncs in delta mode with reduced frequency (avoid full catalog syncs).

Product sync (NetSuite to Amazon)

  • Load items before peak.

  • Run bulk/mass updates off-peak, in batches.

  • During season: reduce item sync frequency to once/day.

  • Update custom categories whenever Amazon updates category templates (Settings > Product > Custom category). See Add a custom category to the product flow.

  • When using item aliases, do not select Active for all Amazon accounts if the same item exists across multiple marketplaces to avoid alias conflicts.

  • Run inventory/product syncs in delta mode with reduced frequency (avoid full catalog syncs).

  • Use only the pricing and inventory flows to update pricing and quantity. Disable the Product flow during peak seasons if there are no product updates to reduce unnecessary processing.

Pricing sync (NetSuite to Amazon)

  • Run at low frequency; avoid enabling during peak.

  • If needed during peak: schedule once/hour with minimal mappings.

Auto-billing sync

  • Run NetSuite Order to Cash Sale/Invoice Add only after the holiday season.

Settlement sync

  • Run pricing and settlement flows sparingly or after peak; use secondary connections.

Amazon Transfer Order – Inbound Shipments

  • Update inventory levels well before sale periods.

Amazon FBA Add-ons (Return Management and Inventory Adjustments)

  • Run only once or twice/day.

  • Configure secondary connections.

    Important

    These share throttling limits; schedule them so they don’t overlap.

eBay – NetSuite integration app

  • Order sync (eBay to NetSuite)

    • Use Last Modified as the filter so the flow works in delta mode.

    • Leave Duration in days and Go live date blank (for accounts already live).

  • Tax setup

    • Configure tax codes/components in NetSuite or use integrator.io tax config (Settings > General > Tax).

    •  Options:

      • Add total tax against a single line item, OR

      • Overwrite with eBay tax amounts (Assign the default tax code to all orders).

    • Enable Exclude Tax if Marketplace Tax Collection applies to prevent duplication when eBay collects/remits tax.

  • Inventorysync (NetSuite to eBay): During peak, uncheck Sync all ended listings with NetSuite for better performance.

    • For matrix item inventory, set concurrency = 1 during sync, then reset to normal.

    • Disable eBay Item ID to NetSuite Mass Update after IDs are synced.

  • Item and Pricing sync (NetSuite to eBay)

    • Sync prices and item updates before holiday season.

    • If required during peak, run with low frequency to reduce load.

    • Disable eBay Item ID to NetSuite Mass Update after IDs are synced.

Magento 2 – NetSuite integration app

  • Keep the Magento 2 instance optimized, cached, and compiled for better API performance.

  • Pre-load items and images before holiday season to reduce processing overhead.

  • Lower the item export frequency to once per day during peak periods.

  • Store setup

    • Verify active Magento 2 stores under Settings > General > General tab.

    • If new store views are added and records don’t sync, deselect an existing store in the 'Select active Magento 2 stores' setting, save, and then reselect all required stores.

  • Order sync: Keep the Magento 2 environment optimized (compiled, cached, indexed) to improve API response performance during order imports and item/inventory exports.

  • Tax setup

    • Validate tax setup across both NetSuite and Magento.

    • Configure tax codes properly in NetSuite or use integrator.io tax configuration (Settings > General > Tax).

    •  Options:

      • Add total tax against a single line item on the order (OR)

      • Overwrite taxes with Magento 2 tax amounts (Assign the default tax code to all orders).

    • Using a proper tax setup reduces variances and prevents unnecessary API calls.

  • Item and Image sync (NetSuite to Magento 2)

    • Pre-load all items and images before the holiday season.

    • During peak: lower item export frequency to once/day.

Important

Item exports are resource-intensive; schedule heavy item updates during off-peak hours if necessary.

Square – NetSuite integration app

  • Set NetSuite connection concurrency to 2–3 to free capacity for other integration apps.

  • Orders

    • The app is POS-based, so order data syncs as usual.

    • Consider scheduling the Square Order to NetSuite Cash Sale flow at a higher frequency to maintain throughput.

  • Disable Square to NetSuite customer sync; instead, use a default customer for all cash sales.

    Important

    Customers synced in this manner cannot be resynced later.

  • Tenders

    • Avoid syncing tenders unless required for refunds.

    • Enable the Square Tenders to NetSuite Custom Payments flow only if you must sync gift card or cash sale refunds.

  • POS setup

    • Ensure all Square POS locations are correctly configured and selected in Settings > General > General tab.

  • Schedule the Square Refund to NetSuite Cash Refund flow at a lower frequency (1–2 times per day) throughout the holiday season.

  • Product modifiers 

    • In the setting Sync Square product modifier to NetSuite (Settings > Order > Order), map the correct NetSuite items to Square modifiers to avoid mismatches or variances.

      Important

      If unmapped, modifiers may cause unwanted variances in orders.

    • On the NetSuite sales order, the modifier name appears in the description field only if you add the item description mapping in the Square Order to NetSuite Order flow.

BigCommerce – NetSuite integration app

  • Pre-sync products and inventory before peak to avoid large data runs during the season.

  • Use delta mode for inventory and fulfillment flows.

  • Schedule the fulfillment flow at a higher frequency (every 15 minutes) to keep order statuses updated without causing bottlenecks.

  • Avoid running the following flows during the season:

    • BigCommerce Customer to NetSuite Customer Add/Update

    • NetSuite Item to BigCommerce Product Add/Update

    • NetSuite Item Image to BigCommerce Product Image Add/Update/Delete 

  • Run refunds and cancellation flows at a low frequency during off-peak hours. 

    • NetSuite Cancellation to BigCommerce Cancellation Add 

    • NetSuite Refund to BigCommerce Refund Add

Payout to Reconciliation Automation for NetSuite

  • Pre-holiday preparation: Clear all open transactions before the holiday season so you start peak operations below NetSuite’s transaction threshold.

  • Schedule payout flows at regular intervals to keep transaction volumes below NetSuite’s 10,000 transaction limit.

  • For PayPal payout flows with multi-currency, ensure the PayPal primary currency code is set correctly to prevent variances.

  • Validate account settings before the holiday season to prevent setup errors.

  • Always set minimal lag offsets to improve payout flow performance and avoid overlapping or missed transactions.

  • Ensure all order and refund transactions are synced with undeposited funds accounts and carry the correct transaction IDs.

  • Confirm that the bank deposit account and other GL accounts are aligned with the same subsidiary and currency.