This guide outlines essential best practices for managing your Celigo Amazon-NetSuite Integration App. By following these recommendations, you can optimize your app's performance, ensure data synchronization reliability, and maintain scalability, especially during high-volume periods.
Amazon-NetSuite Integration App Management & Performance
-
Leverage Separate Integrations: Create a separate integration instance for each brand to improve organization and simplify troubleshooting. Differentiate them by including the marketplace or store in the integration name.
-
Optimize Concurrency: Avoid scheduling all Amazon flows to run simultaneously. For a multi-brand setup, staggering flow schedules across different start times can help prevent Amazon's throttling limits. You can also assign all available Celigo concurrency to a single parent connection to manage it across different integration apps.
-
Prioritize Flows: Use scheduling to prioritize critical flows. For example, run pricing and inventory flows more frequently than item or catalog exports, and consider decreasing the frequency of item exports during high-volume periods as they are data-intensive.
-
Utilize Delta Mode: Run inventory flows in "Delta" mode to sync only the items that have changed, rather than the entire catalog. This significantly reduces data processing and avoids bottlenecks.
-
Avoid Outdated Retries: Refrain from processing bulk retries for old errors in high-volume flows (inventory, item, or pricing) as the data may be outdated and could lead to new issues.
NetSuite Configuration
-
Increase Concurrency: During high-volume periods, contact NetSuite support to request an increase in your account's concurrency limit if needed.
-
Customer Records: Create a unique customer record for each marketplace and Amazon account combination to avoid exceeding NetSuite's 10,000 transaction limit for a single customer.
-
System Performance: To improve NetSuite's performance, set the log level of all Celigo-related scripts to 'Error'.
Amazon-Specific Considerations
-
Item Aliases: When using item aliases, do not select the "Active for all Amazon accounts" option if the same item exists across multiple marketplaces. This prevents alias conflicts.
-
Throttling: Be mindful of Amazon's API throttling limits. Avoid syncing large amounts of data at once, especially for multiple domains within the same region.
-
Preparation for Peak Seasons: Before a high-volume period like the holiday season, load all items into NetSuite and avoid making major changes to key settings or mappings.