We are a US based eCommerce company. We import Amazon and Ebay orders into Linnworks. We have seen and been informed that "All orders downloaded from a channel (eg: Amazon, eBay, Rakuten or a website) by default assume inclusive tax (meaning you already included tax at the point of sale)."
Business in the US normally don't include tax in the displayed price to the customer, the tax is added on at the checkout.
We see that Direct Orders can be set to be either inclusive or exclusive, so why can imported orders be the same? We need a flag/check box made that would allow us to pick which tax setting we want to use for imported orders.
This setting is causing issues when the sales channel order now doesn't match the Linnworks order, and then again when it is imported to our QuickBooks account.
this is possible at an order item level as part of the import by adding a "Tax Inclusive" column to your import file
|This field is a compulsory requirement for the import. The data must exist as a column in the CSV and be mapped to the named field.|
|This field relies on dependent data that is a compulsory requirement for the import. If this field is included in the import then the dependent fields must also be mapped.|
|This field is classed as an Order Header field. All Order Header fields are used to group multiple rows of Order Items into a single order. For this to be successful all Order Header fields are required to contain the same values for a single order. More details on this can be found here.|
|Channel SKU||The SKU used to identify the purchased item on the sales channel. Linnworks will try to link this to an inventory item using the following priority. If no match is found the order item will display as an unlinked item||Item Number|
|Item Discount||Percentage discount that has been applied to the ordered item||Channel SKU|
|Item Is Service||The item is a service such as Gift Wrap and therefore is not a Linnworks Inventory Item. Set the value to 1 or YES||Channel SKU|
|Item Number||A unique row identifier for each order item within an order. The identifier can be repeated across different orders, but not within an order||Channel SKU|
|Item Price Per Unit||The individual sold price for the item that has been purchased||Channel SKU|
|Item Quantity||The quantity of items that have been purchased. If a quantity is not supplied a value of 1 is assumed.||Channel SKU|
|Item Tax rate||The tax rate that has been applied when the item was purchased||Channel SKU|
|Tax Inclusive||Defines whether or not the item's price is inclusive of tax. Leaving blank will default to false (exclusive). Setting a value of YES or 1 will be seen as inclusive.||Channel SKU|
|Item Title||The title from the sales channel for the purchased order item||Channel SKU|
Thank you Mark, but this solution seems to apply to manually imported orders via a CSV file. What about orders that are automatically imported via a download direct from the sales channel?
sorry my misunderstanding, as when you used the phrase imported orders I assumed you were referring to Data Import
Please take a look at the "Use Channel Tax" to see if this provides the solution you require
This does not help because my Amazon account isn't VCS enrolled. Plus, Amazon isn't the only sales channel affected. What about ebay? Or any other 3rd party sales channel?
For Amazon as far as I am aware they only provide the Tax value to us for clients that are VCS enrolled, which means that as we know Tax is included with the order we have to back-calculate based on the tax settings within Linnworks as per the Country/Region settings. I know for the US this will not be 100% perfect due to the tax laws within the US.
For eBay at the moment this option is not available as the order download functionality for eBay was written before this option was first implemented. We are working through the channels and adding the option, with eBay we know this needs to be implemented, however with the changes that eBay have been making to their API recently we have held off on rewriting this task until we are confident the new API is stable and available for all accounts.