When providing a test order or test product to your FarApp Integration Specialist, it is important to keep several things in mind.
- First and foremost; these are being used for testing. There is a chance something will not sync correctly. You want to be careful about which order or product you select for a test. Don't select your top-selling SKU for the product sync test because there is a chance the price or quantity or some other important piece of data will not sync correctly. You don't want to run a product sync test only to find out you have synced the incorrect price and sold the SKU at that price. You also shouldn't provide a test order with items you know are out of stock in NetSuite because that order won't be able to be fulfilled in NetSuite. In short, keep the purpose in mind when making your selections.
- The order or product you select should be a good representation of your data. For example, if 90% of your SKUs are matrix items, you will want to be sure to test with a product that is a matrix item in NetSuite. Your test order should have data populated for all the fields you expect FarApp to sync to NetSuite. For example, if you want the memo field to sync over from the marketplace/cart orders then make sure your test order contains data in the field you will map to the memo field in NetSuite. A test order or product that is not a good representation of your typical data is not a good test.