Before running data flows, you must set up the data flow and save the settings.
You can set up the ship methods, orders, and customer filters before you run the data flow. You can filter orders based on the time of their creation, or specific customer duration, or order status. You have options to map the ship methods between the systems. You also have options to import multiple Amazon orders into NetSuite.
Note: Revisions by Amazon to the Send to Amazon workflow have no impact on the functionality of integrator.io communications with the platform. The latest revisions are only user-interface changes, and integrator.io communicates with Amazon via their APIs. No changes have occurred to their APIs that impact Amazon FBA order flows.
General
The General tab present under Settings > Order (FBA) contains the following fields that let you control the way orders are synced to NetSuite from Amazon.
Fields |
Description |
Import order as |
Imports an Amazon FBA sales order with the NetSuite Transaction type as selected in the drop-down list. |
Automatically assign Lot/Serialised numbers |
Select this check box if you want to automatically assign numbers to the Serialized/Lot Numbered item type. Serial numbers that are created first, or Lot Item numbers that are nearing expiry, or the ones created first if the expiry date is unavailable are used for allocation. Info: By default, Amazon does not associate serial/lot information of items in the order. Therefore, in NetSuite, if items are of the lot/serialized item type, you will be unable to create an invoice without the serial/lot number. When this check box is selected, it automatically associates the serial/lot information to the items synced, and the flow runs successfully. |
Select inventory location present in NetSuite |
Select the inventory/fulfillment location present in NetSuite for both the body and line-level whenever an order is imported as Invoice/Cash Sale/Sales Order. |
Filter orders by |
Select the time filter. Based on the value selected in the drop-down, the associated orders within the specified duration are imported from Amazon to NetSuite. |
Duration in days |
Specify the duration in days to import orders. The duration is considered from now till the specified number of days in the past. Note: This field is mandatory if Creation Time is selected in Filter Orders By. |
Go Live Date |
Enter the date from when you want to start importing orders. All Amazon orders created prior to this date are ignored. When specified, this date takes precedence over the Duration setting. This date can be in the past, present, or future. |
Amazon Item Aliases |
Use this check box if you have configured item aliases in Amazon and NetSuite to link multiple Amazon SKUs with a single SKU in NetSuite. For more information on Item Aliases, refer to Item Aliases. |
The following diagram illustrates how various fields available under the General tab let you sync Amazon orders to NetSuite and also demonstrates how a delta flow works.
To understand the various fields present under the General tab better, let's assume that,
- today's date and time of flow execution is 17th January 1300 HRS and that the Amazon (FBA) Order to NetSuite Order Add flow is already run for the first time,
- you have scheduled the Amazon (FBA) Order to NetSuite Order Add flow to run after every 15 minutes,
- and the values mentioned in the table below are entered under Settings > Order (FBA) > General.
Notes:
- When the Amazon (FBA) Order to NetSuite Order Add flow is being run for the very first time, it will not sync any received/modified orders to NetSuite. integrator.io considers the first run date and time as a reference to run the flow again as per the configured schedule.
For example, if you run the Amazon (FBA) Order to NetSuite Order Add flow on 17th January 1300 HRS for the first time and schedule it to run every 15 minutes, then for the first run, no orders will be synced to NetSuite.
As per the configured schedule, the flow will run again after 15 minutes at 17th January 1315 HRS, and the orders received/modified between 17th January 1300 HRS through 17th January 1315 HRS will be synced to NetSuite.
- For users who want to go live with the Amazon - NetSuite Integration App immediately or in the future: When scheduling and running the Amazon (FBA) Order to NetSuite Order Add flow for the first time set the Filter orders by drop-down list box to Creation Time and also specify a value in the Duration in days field. Later, you must change the value to Last Modified Time. This will help you sync all the orders from Amazon to NetSuite without missing any.
Table: Illustrates various scenarios available on the General tab.
Scheduled Flow Run Date and Time in HRS |
Go Live Date |
Filter orders by |
Duration in days |
Description |
17th January 1315 HRS |
15th January |
Creation Time |
2 Note: Mandatory if Creation Time is selected in Filter orders by. |
Orders received (Creation date and time) between 15th January 0000 HRS through 17th January 1315 HRS will be synced to NetSuite. Note:
|
17th January 1315 HRS |
19th January |
Last Modified Time |
NULL |
Orders modified between 19th January 0000HRS and after will be synced to NetSuite from Amazon. |
17th January 1315 HRS |
19th January |
Last Modified Time |
2 |
Orders modified between 17th January 0000HRS and after will be synced to NetSuite from Amazon. |
17th January 1315 HRS |
NULL |
Last Modified Time |
2 |
Orders modified between 15th January 0000HRS through 17th January 1315 HRS will be synced to Amazon. |
17th January 1315 HRS |
NULL |
Last Modified Time |
NULL |
Orders modified between 17th January 1300 HRS through 17th January 1315 HRS will be synced to NetSuite. |
Shipping
This setting lets you map the shipping methods between Amazon and NetSuite. You can also provide a default value in case no match is found. Click in the row to select and map the shipping method.
- Fail Record: Select this check box if you want the order sync to fail when there is no match.
- Use Empty String as Default Value: Select this check box to sync an empty value.
- Use Null as Default Value: Select this checkbox If you wish to use null as default value.
- Use Custom Default Value: A field will be enabled then you can select from the list for a value.
Orders
- Amazon order IDs: You can provide up to 10 Amazon order ids separated by a comma (,) for an on-demand import of orders from Amazon to NetSuite.
- NetSuite discount item to track Amazon discounts: This lets you choose the corresponding NetSuite item to track promotion/discount amounts on your Amazon orders. Promotion codes applied on the Amazon SKUs are mapped to the eTail Discount Code field at the line level on the Sales Order record in NetSuite.
- Select the NetSuite item to track gift wrap amounts/taxes on the Amazon orders. You need to create an item of "Non-Inventory" type in NetSuite and add it here, the Integration App will create an order line with this item for the total Giftwrap amounts and taxes. It's recommended to unset "Can be Fulfilled/Received (isfulfillable)" on the selected item record.
- Select the NetSuite item to track shipping amounts/taxes on the Amazon orders. You need to create an item of "Non-Inventory" type in NetSuite and add it here, the Integration App will create an order line with this item for the total shipping amounts and taxes. It's recommended to unset "Can be Fulfilled/Received (isfulfillable)" on the selected item record.
Customers
- Allocate FBA orders to below NetSuite customer(s): Provide the internal ID(s) of NetSuite customers in a comma-separated format. Based on the number of customer IDs you provide, during order sync to NetSuite, the FBA orders are equally distributed among the mentioned customers. This setting lets you skip the creation of new customer records in NetSuite for each new order from Amazon.
Note: If the number of orders in a single job run is less than the number of mentioned customer ids, only the first few customers will be utilized without the random pick.
Also, If you provide an incorrect customer ID, the following error message is displayed: “Enter a valid customer internal ID(s).”
The FBA orders are allocated in a cyclic way (round-robin manner). The flow randomly picks the customer ID from the provided IDs and the order allocation continues to the next customer ID. The random pick is to ensure that the starting few customer ID(s) are not allocated with many FBA orders. Take note of some examples:
-
- If you provide three valid customer internal ID(s): 123, 456, 789. When you run the settlement flow and if you have 30000 orders, each customer is allocated with 10000 orders.
- If the flow first picks 456 as the customer ID, the first order is allocated to the customer with ID 456, the second order is allocated to the customer with ID 789, and the third-order is allocated to the customer with ID 123.
- Provide the number of customers in the setting in such a way that in a settlement period, the number of invoices on any customer does not exceed 10,000. If the average volume of orders you receive in a settlement period is 100000, provide more than 10 customer IDs. If the volume of orders is around 20000 in a settlement period, provide 3 customer IDs.
- Remove phone number if invalid on Amazon order: Let's you define a business rule where invalid phone numbers on Amazon orders are automatically removed before the order is added to NetSuite. This prevents any manual intervention to import orders with invalid phone no.s (<7 digits or alphanumeric format).
- Trim customer name if invalid on Amazon order: This lets you define a business rule where an invalid first name and last name on an Amazon order are automatically trimmed to the first 32 characters before the order is added to NetSuite. This prevents order import failures when the buyer enters more than 32 characters for the first name and/or last name fields in Amazon.
- Use Shipping Address/Name when Buyer Name is Missing: Lets you define a business rule where Buyer Name on Amazon order is missing then we should consider ShippingAddress -> Name as NetSuite first name and last name
-
-
Related topics
Comments
0 comments
Please sign in to leave a comment.