Quantcast
Channel: Celigo Help Center
Viewing all 111 articles
Browse latest View live

Credit Memo Import (Magento to NetSuite) +Plus

$
0
0

Flow Summary

The Credit Memo Import flow imports Credit Memos issued in Magento into NetSuite as Cash Refunds or Credit Memos, depending on whether the original transaction was a cash sale or a credit sale.

Flow Details

The Credit Memo Import runs at the end of the Order Import and looks for credit memos created in Magento since it was last run. The Connector only imports credit memos if they are associated with NetSuite-linked Magento orders. If  a sales order in Magento is not linked to NetSuite by the Order Import/Export flows, the related Magento credit memo is not imported. For each credit memo included in the import, the connector:

  1. Searches for cash sales associated with the order in NetSuite, and if found, generates a cash refund against the most recent cash sale.
  2. Searches for invoices associated with the order in NetSuite, and generates a corresponding credit memo against the most recent invoice.

Flow Schedule and Monitoring

The Credit Memo Import flow follows the same schedule as the Order Import flow. The flow can be monitored from the Integration Dashboard. Please click here for more information.


Real-time Order Cancellation Import (Magento to NetSuite) +Plus

$
0
0

Flow Summary

When an Order is cancelled in Magento which has not been billed, it is cancelled in NetSuite and the inventory is re-stocked automatically by this flow in real-time. The flow also supports partial cancellation where even if the part of the order has been billed and rest is cancelled in NetSuite, the remaining items in NetSuite are closed in NetSuite.

Partner Channel Support using native Salesforce Opportunity Partner functionality (Salesforce Plus)

$
0
0

Generating a Quote

In addition to the standard Opportunity to Quote sync in Salesforce Standard, Salesforce Plus connector now lets you generate quotes with additional options. This feature lets you sync the primary partner of the opportunity and the currency of the quote from Salesforce to NetSuite. Both accounts should be multi-currency enabled for the currency sync to work. The primary partner in the account is synced to a customized field as shown in the figure.
image87

Generating a Sales Order

Salesforce Plus, in addition to the Standard sync feature, allows you to sync your Partner Opportunity to a Sales Order in NetSuite and also syncs partner Information. The primary partner fields are synced to the customized Bill To field and the currency is synced to the Currency field in the Sales Order. Billing address of the main account is mapped to the Bill To field and shipping address of the primary partner is mapped to the Ship To field of the sales-order generated.

The below image shows how the addresses are mapped:
Generating-a Sales-Order

Financials Export– Salesforce Connector Plus

$
0
0

In addition to the Standard feature of bringing back header data of various transaction types related to the corresponding account, Salesforce Plus provides the following:

Pdf files generated for different transactions in NetSuite are exported to Salesforce and are synced along with the corresponding financial object. All financial objects are associated with the account in a Financial tab present on the account object.
The individual pdf details for a financial can be seen by clicking on the Document link present on the financial in salesforce.

Financials-Export1

Multiple transaction types in NetSuite are supported for generation of Pdf files. These include: PurchaseOrder, Invoice, CustomerPayment, CashRefund, CreditMemo, CustomerRefund, CustomerDeposit and CashSale, Sales Order and Quotes.
Financials-Export2

To generate the pdf make sure the Attach PDF field present on the corresponding deployment of the user event script is on.
Financials-Export3

Export NetSuite Sales Order Line Items to Salesforce – Salesforce Connector Plus

$
0
0

The Salesforce Connector Plus creates a NetSuite sales order from a Salesforce opportunity; however, there can be additional information that is added onto the sales order that would differ from the Salesforce opportunity. Furthermore, sales orders for enterprise and/or account management may be created directly into NetSuite and not Salesforce. In such cases, users are able to see additional Line Item information from Netsuite.
These line items are synced back along with the Sales Order and are attached on the corresponding Sales Order page. The line items have been added as new customized salesforce objects sales order line items in Salesforce.
Export-NetSuite-Sales-Order-Line-Items

Export Contract Renewal Records To Salesforce Opportunities – Salesforce Plus

$
0
0

Salesforce Connector Plus, lets you sync opportunities, quotes and sales-orders generated via Contract Renewals module in NetSuite to Salesforce as opportunities. Note, this export will work only if the Contract Renewals module is installed in your NetSuite account.

Note: Records are only synced on ‘Create New’ in NetSuite and not on ‘Update’ of existing records.

Export Opportunity(NetSuite) to Opportunity(Salesforce)

Opportunity generated in netsuite can be synced back automatically to Salesforce. The following figure shows a standard opportunity created in NetSuite after the Contract Renewal module of NetSuite is installed.
Export-Contract-Renewal-Records1
The above opportunity is synced to Salesforce Opportunity below:
Export-Contract-Renewal-Records2
Note: For the above sync to happen, the items and End User in the Opportunity must be synced to Salesforce.

Export Quote (NetSuite) to Opportunity (Salesforce)

A quote created from NetSuite is synced in real time to the Salesforce account and creates a New Opportunity in Salesforce.

The below figure shows an Quote created in NetSuite with all Items and End Users already synced to Salesforce:
Export-Contract-Renewal-Records3
The above Quote when saved allows the creation of a new Opportunity in Salesforce as shown here:
Export-Contract-Renewal-Records4
Note: For the above sync to happen, the items and End User in the Opportunity must be synced to Salesforce.

Sales Order (NetSuite) to Opportunity (Salesforce)

A Sales Order created from a Quote in NetSuite which is already synced, will add the details of the Sales Order to the Sales Order tab under the Opportunity in Salesforce.

Below is an image of a Sales Order created from an existing quote in NetSuite that is synced to an Opportunity in Salesforce.
Export-Contract-Renewal-Records5
On saving the Sales Order, as shown above in NetSuite, a corresponding Sales Order is created in Salesforce and attached to the Opportunity (created from NetSuite quote previously).
Above Sales Order is synced to Salesforce Opportunity in real time under the Sales Orders tab as below:
Export-Contract-Renewal-Records6
A new Sales Order created in NetSuite will be synced as a New Opportunity in Salesforce.

Below figure shows a new Sales Order entered in NetSuite:
Export-Contract-Renewal-Records7
The corresponding New Opportunity is created in Salesforce with Sales Order attached to the Opportunity:
Export-Contract-Renewal-Records8

Inventory Export (NetSuite to eBay)

$
0
0

Flow Summary

The Inventory Export flow exports an item’s Quantity and Stock Availability from NetSuite to eBay. All other item fields are handled by the Item Export[Link Needed] flow.

 

Very Important: Only items  whose eBay Item Id field is populated are exported. This fields is populated automatically once you export the item using connector (The field can be found under the Custom Tab named eBay Item Id)

Flow Details

The Inventory Export flow processes all inventory items. It only includes the value in an item’s “Quantity Available” standard NetSuite field. Quantities from other standard fields such as “Quantity On Hand” or any custom fields are not included. Items marked as drop ship in NetSuite are not included in the export.

By default, the “eBay Item Id” field in NetSuite is used to find the corresponding product “SKU” or “Product Id” in ebay for the update.

Multi-Location Inventory

The Inventory Export flow supports standard NetSuite inventory management along with multi-location inventory management. If you use multi-location inventory, the Connector sums the quantity available for each location and sends the total quantity available  to eBay. If only certain locations should be considered for exporting inventory to eBay, it is possible to specify them.

Flow Schedule and Monitoring

 

Inventory Export runs every 30 minutes to export items’ Quantities and their Stock Availabilities from NetSuite to eBay. It only exports the available quantity of items for which the Last Modified Date is a time after the export last ran.

 

Connector also runs a Weekly Inventory Export  to export the items’ Quantities and their Stock Availabilities from NetSuite to eBay for all eligible items. The Weekly Inventory Export runs by default every Sunday morning US Pacific Time. Both of the flow schedules are customizable and can also be run on-demand. These flows can be monitored from the Integration Dashboard. Please click here for more information.

 

Note: Please note that ebay does not update item quantity to zero from NetSuite.

Item Export (NetSuite to eBay)

$
0
0

Flow Summary

The Item export flow exports an item’s field data from NetSuite to eBay.  This flow is a real-time flow – it is triggered when an item that has an eBay listing associated is saved. In the case of any new item created, the user is given an opportunity to verify and create an eBay listing for the same.

When the user submits an eBay listing and saves it (with or without verifying the eBay listing), the item is listed on eBay and the eBay details are populated for the record. Similarly, on every subsequent update of the item record in NetSuite, the eBay listing is updated.

The following item types are supported:

  • Inventory Item (non-matrix)
  • Lot Numbered Inventory Item (non-matrix)
  • Serialized Inventory Item (non-matrix)

Note: All other item types are not yet supported by the eBay Real-Time Item Export.

Flow Process

When an export is triggered, the Connector adds a new listing in eBay using the NetSuite item data. If the listing has already been created by the Connector previously, the Connector will revise the existing listing on eBay with the NetSuite data.

Once the listing is created in eBay, the Connector sets the eBay Item ID field in the eBay Item Listing form  to maintain a hard link between the NetSuite item and the eBay Listing.  Also, the Listing’s Start Time,End Time, Listing Fee retrieved from eBay will be stored in the Item Listing form in NetSuite after the addition/revision of a successful listing. If more than one listing with a similar SKU is found in eBay, the item export fails, and an error is logged in the integration  logs.

When the Connector is installed, it creates a custom record “eBay Item listing”. This custom record contains all the relevant fields for adding/revising a eBay Listing like Primary Category,Listing Duration, Return Policy, etc.

Note that matching Item Categories will not be created by the Connector. These will need to be setup manually in NetSuite to enable a 1:1 mapping of Item Categories between systems.

Flow Schedule and Monitoring

The Item Export flow runs in real time as soon as  the Item record is saved in NetSuite.

Pricing Export

Connector will sync the price field value from a user-defined NetSuite Price Level to the eBay Listing Start Price. This can also be configured to sync the value field from a custom field if required.

Payment Methods

Paypal is supported by default. More payment methods can be exported as of the sync if required.

Image Export

Image URLs can be synced from NetSuite to eBay. These images will need to hosted on an external server.

Note that uploading actual image files is not supported yet.

 Note: eBay API only allows 1 Self Hosted Picture/12 eBay Server Hosted Pictures to be uploaded for an Item Listing. Connector supports export of one image URL from a NetSuite Field (which is the URL of the Image on External Server) to eBay. eBay only supports HTTP/FTP protocol for Image Export.

Default Mappings

The following mappings are installed by default. Please consult your Celigo project resource for mapping additional fields, as it might not be possible to map certain fields.

NetSuite Field

eBay Field

Notes

Display Name / Code

Title

Updates the first time only. Later the value has to be updated manually in listing.

Sales Description

Description

Sales Description standard field is mapped to custom field “Description” on eBay Item Listing form that in turn maps to eBay Description field

Primary Category

Category

Custom field on eBay Item Listing form.

Buy It Now Price

Buy It Now Price

Custom field on eBay Item Listing form

Listing Duration

Custom field on eBay Item Listing form.

Condition

Condition

Custom field on eBay Item Listing form.

Location Postal Code

Location Postal Code

Custom field on eBay Item Listing form. The value of location is auto populated in eBay by the postal code.

Shipping Service

Shipping Service

Custom field on eBay Item Listing form.

Shipping Service Cost

Shipping Service Cost

Custom field on eBay Item Listing form.

Handling Time (in business days)

Delivery

Custom field on eBay Item Listing form.

Free Shipping

Free Shipping

Custom field on eBay Item Listing form.

Returns Accepted option

Returns Accepted option

Custom field on eBay Item Listing form.

Refund Option

Refund Option

Custom field on eBay Item Listing form.

Return Policy Description

Return Policy Description

Custom field on eBay Item Listing form.

Return Duration

Return Duration

Custom field on eBay Item Listing form.

Note: All the fields in the “eBay Item Listing” form are custom fields with self-explanatory labels and mapped to the fields in eBay by same or similar names.

Once user tries to create an eBay listing, The Listing Response Details section is populated in the eBay Listing Form. The details are Item ID, Start and End Times of the Listing, Fee charged on inserting/revising the listing. If there is any warning/error in creation or update of eBay listing the corresponding messages are stored in the respective fields.


Fulfillment Export (NetSuite to eBay)

$
0
0

Flow Summary

The Fulfillment Export flow exports item fulfillments from NetSuite to eBay. The flow is triggered as soon as the Item Fulfillment record is saved in NetSuite.

Flow Details

The flow exports NetSuite’s Item Fulfillment record and creates a corresponding eBayshipment record. The Shipment record is created with the same items and quantity as present in the NetSuite fulfillment record. The flow also exports the “Package Tracking Numbers”, “Shipping Carrier”  on the fulfillment record.

Flow Schedule and Monitoring

The Fulfillment Export flow runs in real time as soon as  the Order is fulfillment in NetSuite.It also supports bulk fulfilling of orders in NetSuite.

Handling Export Failure

In case of a failed export,  the errors are logged for  the corresponding fulfillment record under Custom tab > Celigo Integration Log. In order to re-try the fulfillment export flow, correct the error and save  the record once again.

All the errors are also logged in the Celigo Integration Dashboard.

 

Note: Partial Fulfillment is not supported in eBay connector as of now.

 

Overview

$
0
0

With the Celigo eBay Connector, you can combine the selling power of eBay with your NetSuite system. This allows you to leverage NetSuite’s “One system, no-limits” philosophy by using a single system for your product and order-related data and minimizing double-entry.

Using the eBay Connector for NetSuite, retailers combine the powerful brand of eBay.com with the proven back office features of NetSuite. Since the integration is fully automated, you focus on increasing sales and accurately managing the resulting orders, instead of wasting time manually keeping your eBay and NetSuite accounts in sync.

The following flows are currently supported:

Sales Orders Imported to NetSuite

Orders placed on eBay are automatically imported into your NetSuite account in real time. The order information with Customer details is imported to NetSuite

Fulfillments Exported to eBay

Sales orders in NetSuite are checked to see if you have shipped any of the items. If so, the connector looks up the items and time fulfilled, the shipping item used, and the tracking number(s) assigned and sends that data to eBay.

Items Exported to eBay

Inventory items in NetSuite are sent to eBay in real time as soon as the eBay listing is created.

Stock Levels Exported to eBay

The current available quantities of your NetSuite inventory items are kept up to date in eBayl to prevent over-selling. The available quantity may represent that available in one or more NetSuite locations.

CloudExtend Behaviour – Exception Case Scenarios

$
0
0

Optional Attendees

  • Case: Optional Attendees
  • Action: Create
  • Scenario: Event created in Google or NetSuite with optional attendees
  • CloudExtend Calendar Sync Behavior:CloudExtend will sync the optional attendees of this event to the other system as a Required Attendee in this release. This will be improved upon with migration to Google’s latest APIs

Multi-day events spanning across several days

  • Case: Multi-day Events
  • Action: Create
  • Scenario: Event created in Google over a period of several days
  • CloudExtend Calendar Sync Behavior:Since NetSuite does not support multi-day events, the event from google when synced will be divided into multiple events one for each day of the event period.

Editing a Multi-day event in NetSuite

  • Case: Multi-day Events
  • Action: Edit
  • Scenario: User tries to edit one of the multiple events in NetSuite synced from a multi-day event in Google
  • CloudExtend Calendar Sync Behavior:Edit on any of the multi-day events synced from Google is not allowed and an error is shown to user.

Deleting of Multi-day event in NetSuite

  • Case: Multi-day Events
  • Action: Delete
  • Scenario: Any one of the multiple events in NetSuite synced from a multi-day event in Google is deleted
  • CloudExtend Calendar Sync Behavior:All the events corresponding to the orginial multi-day event are deleted in NetSuite and subsequently the multi-day event in Google is deleted.

Multi-day event sync for different timezones

  • Case: Multi-day Events
  • Action: Create
  • Scenario: Time zone difference exists between NetSuite Company and Google User Calendar. Event is created in Google Calendar spanning over multiple days
  • CloudExtend Calendar Sync Behavior:Multiple events are created one per each day spanning over the entire duration of the event from Google. The splits in NetSuite are done based on the Company time zone of the NetSuite account and then converted to the NetSuite user calendar’s timezone. Note: In this case, it might be possible that an event in NetSuite is created where the End Time is earlier than the Start Time. This is a NetSuite Limitation. The user has to assume in this case, that the event ends at the End Time on the following day.
  • Example:Google Calendar Timezone: PST
    NetSuite Company Timezone: CST
    NetSuite User Timezone: PST

    An event is created in Google as follows:

    Start Time: 11/24/2013 8 am
    End Time: 11/26/2013 8 am

    Event is created as below in NetSuite:

    Event 1 of 4: Date 11/24/2013 Start Time: 8 am End Time: 1:59 am
    Event 2 of 4: Date 11/25/2013 Start Time: 2 am End Time: 1:59 am
    Event 3 of 4: Date 11/26/2013 Start Time: 2 am End Time: 8.00 am

Recurring events created on day of week with a timezone difference

  • Case: Recurring events
  • Action: Create
  • Scenario: Recurring Events created as follows in Google Calendar: Select Repeat, Monthly, day of week AND there is a timezone difference between the Google Calendar and NetSuite Company
  • CloudExtend Calendar Sync Behavior:Whenever the criteria is a weekday from the first or last week of the month AND there is a time zone difference that exists between the Google user and the NetSuite Company, the sync is only done when upon conversion into the NetSuite company timezone, the day of week condition remaiNetSuite same for all events in the destination recurring series. All other cases of recurring events are synced accurately.
  • ExampleNote: Unlike Google Events which can be specified in different timezones on one calendar, NetSuite allows creation of events only in the timezone of the user’s Calendar

    Google Calendar Timezone: PDT
    NetSuite Company Timezone: IST

    An event is created in Google as follows:

    Start Time: 10/31/2013 4 pm PDT (Thursday)
    Repeat Monthly By Day of The Week (Last Thursday of Month)

    Converting to destination timezone of IST this event series looks like:

    Source Series Event 1: Oct 31st at 4 pm PDT (Last Thursday of Month)
    Soure Series Event 2: Nov 28th at 4 pm PDT (Last Thursday of Month)
    Destination Series Event 1: Nov 1st at 4:30 am IST (First Friday of Month)
    Destination Series Event 2: Nov 29th at 4:30 am IST(Last Thursday of Month)

    In the above case, it is not possible to replicate the source series into destination coNetSuiteistently and hence the sync will not happen.

    However, in a case such as below, the sync will occur seamlessly

    Google Calendar Timezone: PDT
    NetSuite Company Timezone: IST

    An event is created in Google as follows:

    Start Time: 10/21/2013 2 am PDT (Monday)
    Repeat Monthly By Day of The Week (Third Monday of Month)
    Source Series Event 1: Oct 21st at 2 am PDT (Third Monday of Month)
    Destination Series Event 1: Oct 21st at 2:30 pm IST (Third Monday of Month)
    Source Series Event 2: Nov 18th at 2 am PDT (Third Monday of Month)
    Destination Series Event 2: Nov 18th at 2:30 pm IST(Third Monday of Month)

Recurring events created in Google after the 28th of a month

  • Case: Recurring events
  • Action: Create
  • Scenario: Recurring Events created in Google Calendar: Select Repeat, Monthly, day of month after the 28th.
  • CloudExtend Calendar Sync Behavior:Event is not synced to NetSuite as NetSuite does not allow recurring events on a date after the 28th of every month.

Recurring events of all types

  • Case: Recurring events
  • Action: Create
  • Scenario: Recurring Events of all types created in NetSuite regardless of existence of a timezone difference between the two calendars
  • CloudExtend Calendar Sync Behavior:Events are synced to Google Calendar and are created as per the timezone of the originating event.

Timezone change on Company Calendar

  • Case: Recurring events
  • Action: Create
  • Scenario: Events created on a weekly recurring basis in Google Calendar and the timezone of the NetSuite company is changed after the event is synced to NetSuite
  • CloudExtend Calendar Sync Behavior:The NetSuite calendar has a limitation of not being able to change a recurring event’s time accurately whenever the Company’s timezone is changed

Google events with Privacy Setting

  • Case: All events
  • Action: Create
  • Scenario: Events with Privacy Setting:Default/Public
  • CloudExtend Calendar Sync Behavior:All events with Privacy setting as Public/Default will be imported to NetSuite as a Public event. Private events in Google are not imported to NetSuite
  • Example:Note: This may change in a future update

NetSuite events with Privacy Setting

  • Case: All events
  • Action: Create
  • Scenario: Private and Show me as Busy events created in NetSuite
  • CloudExtend Calendar Sync Behavior:Private/Show me as Busy events created in NetSuite are not synced to Google

All day events with timezone difference

  • Case: All day events
  • Action: Create
  • Scenario: Create an All day event in Google or NetSuite. There is a timezone difference between the two Calendars.
  • CloudExtend Calendar Sync Behavior:All day events remain on the same date in both Calendars despite timezone difference between the two Calendars

Preferred form for imports into NetSuite

  • Case: All events
  • Action: Any action
  • Scenario: Event created/updated in Google. A preferred form is set for Imports in the Calendar wizard for CloudExtend Setup.
  • CloudExtend Calendar Sync Behavior:All events are created using the validation of default form and not the preferred form. If a user tries to edit the synced event on NetSuite, the preferred form’s validation rules apply. This is a limitation of NetSuite’s Calendar.

Event created by an external person

  • Case: All events
  • Action: Create
  • Scenario: An event is created in Google by an organizer who has a different domain than the licensed domain. The said event has attendees on the event who are from the licensed domain.
  • CloudExtend Calendar Sync Behavior:This event will sync to NetSuite, but will not sync the organizer information. The synced event will select one of the attendees of the licensed domain as the organizer of the event. Also, any updates to this event in NetSuite will not sync back to the original event in Google. All further updates from Google, however, will sync to NetSuite event.

Licensing

$
0
0

From release 2.1.1 onwards, CloudExtend Calendar license is made an organizational license.

All employees with a NetSuite and Google Calendar access in the organization will be able to sync their events between the two Calendars.

Enabling Sync

To enable an employee for Calendar sync, run the CloudExtend Setup Wizard and navigate to Step 3. Check the box under the Calendar column corresponding to the particular employee and click Next.

On enabling an employee for the sync, all events in which the employee is an attendee/organizer will sync to the other system.

Disabling Sync

During CloudExtend setup, the Customer may choose to turn off the Calendar sync for all employees by checking and then unchecking the ‘All’ Option as shown below:

To disable sync for an employee, uncheck the box under Calendar next to the particular employee and click Next.

Note, if at least one attendee in an event is enabled for the above Calendar sync, the event will sync to all attendees regardless of whether they are enabled/disabled for the sync.

Disabling the sync for an employee will only limit the number of events that are synced to his Calendar but not completely disable the Calendar sync for the particular employee.

Release Notes

Amazon Order Report Feed (High Order Volume flow)

$
0
0

Order Import:

  • Amazon Order Report Import (High Volume Order Import)
    • The Amazon Order Report Feed downloads new Order Reports from Seller Central and creates new sales orders, creates or updates customers in NetSuite, and acknowledges the import of the Order Report back to Amazon so that they can remove that report.
    • Important! Seller Central regularly generates reports of new orders place in a window of time (15 mins). You must request to receive regularly scheduled XML Order Reports from Seller Central Technical Support before this feed can be enabled.
    • Technical :
      • API Section : Reports
      • Report Type : _GET_ORDERS_DATA_

 

Customer Import:

Amazon also sends customer details with Order data. Amazon connector can import this customer data in following configurations :

  • One Default Customer : All the Amazon imported orders will have a default customer. Shipping address will be directly added to the sales order.
  • Individual Customers as a Child of Default Customer: Connector will create individual customer records, as a child of default dummy Parent customer, say “Amazon”. This enables you to easily filter out your Amazon customers from legitimate leads (Amazon.com prohibits marketing directly to Amazon customers) in your system when utilizing NetSuite Sales Force Automation and Marketing features such as email blasts.
  • Individual Customers :  Connector will create individual customer records.

 

While importing orders with any of Individual Customer setup, the Connector can check to see if a customer record already exists in your NetSuite system with the same Amazon anonymized email address as the one provided by Seller Central in the order feed. If so, it attaches that customer to the sales order. If a matching customer is not found, a new customer record is created in NetSuite. If an existing customer record is used, the addresses provided in the order are added to the customer address book and set as the new defaults.

The following mappings between the Amazon Order Report and the NetSuite customer are configured for your connector:

Amazon Customer Mappings

Seller Central NetSuite Notes
Contact Buyer First Name NetSuite splits the first and last name values into separate fields.
Email This data is hidden in Seller Central.
Phone Phone
Child Of Designates this Customer as a sub-customer of the “dummy” Amazon Customer.
Individual Tells NetSuite that this is a person and not a company.
Address Tab Shipping Address The following shipping address fields are mapped together: Addressee, Phone, Address Line 1, Address Line 2, Address Line 3, City, State, Country, Zip Code. The address is set as the default shipping address.

The following mappings between the Amazon Order Report and NetSuite sales order are configured for your connector:

 

Amazon Order Mappings

Seller Central NetSuite Notes
Order ID Order # “Allow Override” must be enabled in NetSuite under Setup > Company > Auto-Generated Numbers for this mapping to function.
Order ID External ID
Order ID PO #
Purchase Date Date
Shipping Service Ship Via See Setting Your Amazon Ship Method Mappings.
Amazon Transaction (custom) Checkbox for identifying Amazon orders.

 

Amazon Order Mappings (Line Items)

Seller Central NetSuite Notes
Merchant SKU Item See below*
Quantity Quantity
Description Product Name
Price Level Sets the price level for all items to Custom in order to force NetSuite to use the price charged on Amazon.
Price Rate
Shipping Amazon Shipping (custom) Amazon shipping amount charged for that item.
Tax Amazon Tax (custom) Amazon tax amount charged for that item.

*When adding line items to the NetSuite sales order, the Merchant SKU field mapping that you have specified is used to look up the equivalent item in NetSuite, given that each Amazon Merchant SKU is provided for each item on the Amazon order. By default, we use the Item Name/ Number field in NetSuite, but this mapping may be configured to look in any other text field that you prefer in NetSuite, including a custom field you may have created.

Important! If the field used to map to the Amazon Merchant SKU is empty for a given item or does not contain an exact case-sensitive match to the SKU provided in the Order Feed, the connector will have no way to identify which item should be used on the Sales Order and will fail to import the order. An error message will be generated, and an email alert will be sent to notify your team.

It is also possible to configure your connector to use a “many-to-one” lookup of your Merchant SKUs. Some sellers prefer to list their items multiple times in Seller Central with different SKUs; one common case is when an item may used for different purposes or when it is compatible with several types of related items or categories.

This enhancement uses a special custom record called ‘Item Alias’  in your account to create a mapping between items in NS to the multiple related SKUs on Amazon for the purposes of importing orders. Once these alias records are populated with the alternate Merchant SKUs for a given item  the connector will first attempt to find an item in NetSuite that matches the Item Name/Number of the Merchant SKU. Otherwise, the connector consults the table of item alias records to find your items by their alternate naming. Currently, the connector does not provide a way to create or update multiple listings in Amazon based on a single item in NetSuite. This feature is available for an additional one-time setup fee.

After the customer data is processed, the connector adds the new sales order to NetSuite. Once the order is successfully created, the financial totals calculated by NetSuite are compared to those calculated by Seller Central. The following data is compared and checked for a variance:

  • Grand Total
  • Tax Total
  • Shipping Tax Total
  • Shipping Total

 

If a variance is found for any one of these totals, the sales order in NetSuite is updated with those amounts on the Amazon tab of the Sales Order in the fields shown below.

Enhanced Gmail Subtab

$
0
0

a) List of all attached emails and attachments

The new Gmail Subtab has been enhanced to list all your attached messages and attachments at one place

b) Compose and Attach to current record

There is even more you can do from the tab – It is possible to even send an email and attach it directly to the currently opened record.

(i) Click Compose – You should see a Pop-up for composing an email

(ii) Type your message and Click Celigo Send

iii) The newly sent mail will appear within few seconds on the record. If there were any attachments in the mail, click refresh button on the tab after 30 seconds.


Attach to Parent Company

$
0
0

When an email is attached to an entity record, the CloudExtend application will also search for the record’s parent company and attach the same email to the parent company record both under the Communication sub-tab and the Gmail sub-tab.

For example, if a user attaches an email to Jack Welch, which is a contact record, CloudExtend will also attach the record to the parent company to which Jack belongs; Christy Catering, in this case.

You may choose to turn off this feature by clicking on the widget as shown in the image and turning off the Attach To Company feature.

Attach to Parent

Please note, currently only entity record types of Contact is supported for this feature.

Attaching Messages to NetSuite Records

$
0
0

Following NetSuite records are supported to be associated emails to:

  • Calendar Event
  • Cash Refund
  • Cash Sale
  • Contact
  • Credit Memo*
  • Customer
  • Customer Payment*
  • Employee
  • Invoice*
  • Job*
  • Lead
  • Opportunity
  • Partner*
  • Phone Call
  • Prospect
  • Purchase Order*
  • Quote
  • Return Authorization*
  • Sales Order
  • Support Case
  • Task
  • Vendor*

*Added new in CloudExtend for Gmail 2.0 Release

a) Attaching currently opened email

Once Logged in, click on Celigo O to bring the widget

It automatically brings up the search results that corresponds to – To, CC, BCC, From fields of the current mail.

You may change the text in Search Box to search by something else “eg- type the customer/employee name” , it will bring up all the records with the given search text.

When an email gets attached to the records a notification is shown

You can click on record link to view the record in NetSuite.

See Enhanced Gmail Subtab on seeing attached messages/attachment right within NetSuite.

 

b) Attach an email while sending using Celigo Send button

c) You can attach an email even while replying an email

 

d) Create a NetSuite record within Gmail and attach the current email to it

 

Logging into NetSuite

$
0
0

a) Click on “Celigo O icon”

If you do not have a session with NetSuite, a Login Screen would be prompted

i) Logging using Standard Sign-on Method: [Ref#0]

Type your username and password and click enter/or click Sign In

ii) Logging using OpenID Single Sign On

Help on setting up OpenID can be found here

Click Automatic and then click on Continue Button

Overview

$
0
0

Celigo MarketReach Connectors consist of Three Marketplaces integration (connectors) with NetSuite namely Rakuten,  Sears, and Newegg. MarketReach Connectors also come loaded with Two leading Comparison Shopping Engine connectors – Google Shopping and Nextag.

Rakuten, Sears, and Newegg flows

The following flows are currently supported for Sears, Rakuten and Newegg connectors:

Sales Orders & Customers Imported to NetSuite

Orders placed on Sears, Rakuten, and Newegg are imported into your NetSuite account on scheduled intervals. The order information with Customer details is imported to NetSuite.  There is a duplicate order check incorporated in the connector.

Fulfillment Information Exported

Sales orders in NetSuite associated with MarketReach connectors (Sears, Rakuten, Newegg) are checked to see if you have shipped any of the items. If so, the connector looks up the items and time fulfilled, the shipping item used, and the tracking number(s) assigned and sends that data to the respective marketplace.

Stock Levels & Pricing Exported

The current available quantities of your NetSuite inventory items are kept up to date in MarketReach connectors (Sears, Rakuten, Newegg)  to prevent over-selling. The available quantity may represent that available in one or more NetSuite locations. Also the price is updated for Rakuten and Newegg items by this flow using Price level set in NetSuite.

Note that Sears connector does not transfer Pricing as it is not supported by Sears API.

 

Google Shopping and Nextag Integration

Google Shopping and Nextag are industry leading Comparison Shopping Engines. The connectors are CSV and FTP based.

Comparison shopping engines allow users to filter and compare products based on price, features and other criteria.  Celigo’s Google Shopping and Nextag Connectors offer these useful integrations: Uploads product feeds selectively from NetSuite via CSV, Creates product ads directly from NetSuite Items, Schedules feeds on a daily basis, Adds, edits or deletes ad listings.

 

 

 

Sales Order Import

$
0
0

Flow Summary

The Rakuten connector’s Sales Order Import flow imports orders placed on your Rakuten marketplace into your NetSuite account.  The connector will import orders your new orders from tab-separated text files stored on the Rakuten FTP servers.  If one or more files are available in your marketplace’s FTP folder the connector will download these files and map their orders as NetSuite sales order records.  If there are multiple files to import they will be downloaded in separate order import jobs.

After all new orders are found in Rakuten, the connector maps them and imports them one at a time.   The connector does not support exporting sales order updates from NetSuite to the original order in Rakuten.  After the flow finishes it will trigger the  Rakuten inventory export flow to export the latest inventory numbers from NetSuite to Rakuten.

If the order cannot be imported the connector will log an error in both the Celigo Integration Log and in a special copy of the import file.  You can check the error file, correct the underlying error in your NetSuite account, and then re-import the failed order with the connector.

Multi-Currency Support

If you are running a NetSuite multi-currency account the connector also checks the currency on the imported order and sets that currency on the NetSuite customer record while importing the order, and NetSuite will automatically source the order’s currency from the attached customer record.  NetSuite only allows this field to be set while no transactions exist for the given customer, so it is usually not possible to update the currency of a customer imported from Rakuten. In the case where a customer already exists in NetSuite and the currency is not known, the connector sets the correct currency when an order arrives. The connector also reports an error if a customer attempts to change his or her currency setting and that operation is not allowed by NetSuite

Duplicate Order Check

The Connector creates custom fields in NetSuite labeled “eTail OrderID” and “eTail Channel: during installation. The order’s ID in Rakuten will be mapped to the “eTail Order ID” and the “P/O Number” fields in NetSuite.  In addition the connector will generate a special ExternalID for the order that indicates it was imported by the Celigo eTail Marketreach connector.   While importing a new sales order, the connector first checks whether there is an existing sales order in NetSuite with the same ExternalID as the mapped sales order.  If the search finds a match the new order is considered a duplicate and not imported.

 

Order Total Variance Handling

It is possible that order total might not match between the two systems if things such as tax rates don’t match. The connector has the ability to calculate any variance that arises related to the order total. After each order is imported into NetSuite, the connector immediately pulls the order out of NetSuite to compare calculated total fields with what was sent from Rakuten. These fields include Tax Total, Ship Total, and Order Total. If there is any difference between the values calculated by NetSuite and the values sent from Rakuten, the difference is stored in one of the variance custom fields below. You may report on these fields in NetSuite on a periodic basis and adjust your G/L with a journal entry if variance values exist.

rktndocs_ordimp_variances.png

Flow Schedule and Monitoring

The Sales Order Import flow runs 24/7 on an hourly basis. It can be adjusted to run every 30 minutes upon request.

Default Field Mappings

By default, the following mappings are installed. Please consult your Celigo project developer for mapping additional fields, as it might not be possible to map certain fields.

Viewing all 111 articles
Browse latest View live