Schedule or run eCommerce integration app data flows

Before your flows or Integration Apps go-live, verify that you have properly enabled scheduling.

Before you begin

Note: These examples apply to most of our Integration Apps. The flows shown are likely to be relevant to the app you are working on, but variation can occur in practice depending on the purposes of your flow. You can find information about specific integration strategies in the community forum topics.

Understanding flow scheduling rates

We recommend scheduling flows at a reasonable rate that will not place a considerable load on your connection. The integrator.io platform has preset for simple flow scheduling but also supports Cron expressions for more complex flow schedules.

Know your web service resources

The NetSuite Concurrency Governance settings may not handle aggressive web service requests that are based on NetSuite user concurrency and/or account concurrency settings. While you may have found a workaround for this scenario, it is important to understand how NetSuite handles web services. Learn more about NetSuite Concurrency Governance.

Scheduling a flow

The frequency to sync the data automatically can be customized using presets from 15 minutes to once a week or by selecting a duration of your choice. To know how to schedule the order data flow, see Scheduling flows.

Celigo maximum recommended flow run schedule settings

eCommerce application preset scheduling

Orders

• eCommerce Application Order to NetSuite Order Add: 15 | 30 | 60 minutes
• eCommerce Application Customer to NetSuite Customer Add/Update: 15 | 30 | 60 minutes

Note: The Integration Apps imports the customer information into NetSuite each time the Order Import flow runs.

• NetSuite Order to eCommerce Application Order Add: 15 | 30 | 60 minutes

Fulfillment

• NetSuite Fulfillment to eCommerce Application Fulfillment/Shipment Add

We recommend a schedule that is customized based on your fulfillment team's activities.

Example:

• For orders marked as “Shipped” throughout the business day, set the flow schedule to “Every Hour”. 
• For orders batch updated at end of the day (EOD), set the flow schedule to “Twice Daily”.
• Marketplaces: Best practices support setting this flow to “Every Two Hours”, or less depending on business need. 

Billing

NetSuite Order to NetSuite Cash Sale/Invoice Add

Webstores

If payment is captured during order placement, set schedule to “Twice Daily”.

If payment is captured after fulfillment, set schedule to every 1-4 hours.

Marketplaces

1. Since payments are managed by the eCommerce application, set the schedule to “Once Daily”, or “Twice Daily”.
2. NetSuite Billing to eCommerce Application Billing/Invoice Add

If payment is captured after fulfillment, set the schedule to every 1-4 hours.

Note: Some business use cases may require scheduling of 15-30 Minutes.

Refunds

Consider the frequency of your refunds and/or order cancellations before you schedule the 15/30 minute schedule frequency.

Note: Refunds cannot occur unless an invoice/billing record is created in the eCommerce Application.

Inventory

Before changing or setting the frequencies, consider the following:

• How frequently do you go low quantity/out of stock e.g. 2x/day or 1x/month?
• How frequently do you add items and corresponding quantities in NetSuite?
• NetSuite Inventory to eCommerce Application Add/Update

Ensure that the Always sync Inventory levels for the entire catalog field is checked.

This flow runs on a delta functionality. Delta means that the system will only pull and update the fields or records which have changed since the last update. You would set to a lower frequency setting, meaning more time between scheduling if you have a lower number of SKUs (products < 1000) but higher inventory levels.

For instance, with a higher number of product/SKU, and higher-order volumes, such as high inventory levels, and a need for more frequently updated quantity levels, schedule this flow between one and four hours.

Product

Adjust the schedule for this flow based on your frequency of catalog updates.

For example: if you make changes against the title or description of a product once a day, you should run it 2-4 times per day (Twice Daily/8h/4h), provided your catalog < 1000 items. Similarly, if your catalog contains 20,000+ items, run it less frequently.

Webstores

Price list changes are considered part of the product flow.

Marketplaces

Product data is less likely to change multiple times per day or week, however pricing updates may be more frequent. These should be scheduled based on the recommendations above. “Once Daily” for a product, and 2-4 times per day for price updates.

Cron scheduling

The CRON style of scheduling is used in all Celigo flows. There are 5 positions representing the schedule: MIN | HR | DAY | MO | WK

• minute (0 - 59)
• hour (0 - 23)
• day of the month (1 - 31)
• month (1 - 12)
• day of the week (0 - 6) (Sunday (0) to Saturday (6))

To build a cron job in integrator.io, see Cron scheduling.

Cron examples

Run a flow

Flows must be enabled to run on an ad hoc basis.

1. Click the tile for the flow.
2. Click Run () on the "Flow Name" row.
3. You need to enable the flow in order to run it. Toggle the Off/On switch.

Related links:

1. NetSuite Concurrency Governance 
2. Email Notifications on Flows and Connectors
3. User Management and Account Ownership Transfer