by Usama Ahmad | Dec 7, 2017 | News & Events
A few weeks ago, we committed we would be providing a feature to account for monthly storage fees per ASIN.
We have now started developing this and we have hit a bit of a snag.
The storage fee reports come with an ASIN and an FNSKU alongside the storage charges for one month. So, we can certainly provide a breakdown per ASIN, but when it comes to assigning the cost to a product for product profitability calculations, we need to assign it to an SKU rather than an ASIN.
See the issue?
We can certainly convert the FNSKU to an SKU, that is not a problem. However, in the cases where there is no FNSKU, we are stuck.
Cases with no FNSKU include comingled inventory and inventory where the UPC or EAN numbers are used instead.
How would you folks want to address this?
by Usama Ahmad | Dec 7, 2017 | New Features
We have just deployed the period-based VAT for Europe.
This is to accommodate the use cases where:
– A seller is not VAT registered for a period of time when just starting a new business
– A seller has exceeded the VAT threshold, registers for VAT and starts charging VAT from the date of registration
– A seller changes from the Flat VAT Rate Scheme to the Standard VAT Rate Scheme or vice-versa
– A seller falls below the VAT thresholds and ceases to charge VAT
– The tax authorities change their VAT rate (heard the one about Brexit, Y’all?)
Period-based VAT behaves like period-based COGS, whereby a specific VAT rate is applied to the orders received between the two boundary dates specified in the settings.
There is a setting at the level of the marketplace as a whole, but of course, you can also define a period-based VAT rate at an individual product level, which then overrides the marketplace VAT rate.
The marketplace and product level date ranges are independent. This provides the added flexibility be able to assign overlapping date ranges at the product level. In essence, the date ranges at product level trump the date ranges at marketplace level.
