I think James has a valid point. For example in EU, we have a MOSS for submitting quarterly VAT reports. MOSS basically allows you to submit (and pay) your reports on one place and the system forwards the reports (and VAT paid) to each EU member state. If you don't (or can't - I think there are limits who can use MOSS) use MOSS, then you have to register with each EU state tax administration and report and pay VAT separately.
But for example Norway is not part of EU and they have their own VAT system where you have to register, submit reports and pay VAT. Now with Brexit, UK is going to become a more complex matter as it is going to be excluded from the EU MOSS system. Many countries have different VAT rates. And this is just EU + Norway.
I'm not sure how this works outside of EU and many countries don't care for digital sales of non-resident companies, but many do - for example recently Turkey announced a system similar to the Norway's system.
It is manageable, but it adds some overhead. On the other hand, when using AppStore, Apple is the merchant on record and the only thing I have to do for our AppStore sales is to upload an invoice to Apple in the ITC.
This is a great idea. The main disadvantage to me is the tax remittance of various local sales/digital taxes for each user. How do you plan to deal with this?
That's a really fantastic point. I would imagine they work b/c it would be against FB/IG's interests to block their own pixel. It's their in-app browser. We'll see what the data shows. If that's the case, I can do server to server events for Facebook but will be SOL for the others.
Currently, it seems all 3rd party cookies are blocked in webkit. Browsers on iOS are all based on webkit, so no way around that. There is the option to use script-writable storage (like localStorage) but those expire after 7 days of inactivity. But within that 7 days your solution could work maybe?
Have you ended up implementing this?
Yep, check out app.hashtag.expert
This is genius! Thanks for sharing :)
I think James has a valid point. For example in EU, we have a MOSS for submitting quarterly VAT reports. MOSS basically allows you to submit (and pay) your reports on one place and the system forwards the reports (and VAT paid) to each EU member state. If you don't (or can't - I think there are limits who can use MOSS) use MOSS, then you have to register with each EU state tax administration and report and pay VAT separately.
But for example Norway is not part of EU and they have their own VAT system where you have to register, submit reports and pay VAT. Now with Brexit, UK is going to become a more complex matter as it is going to be excluded from the EU MOSS system. Many countries have different VAT rates. And this is just EU + Norway.
I'm not sure how this works outside of EU and many countries don't care for digital sales of non-resident companies, but many do - for example recently Turkey announced a system similar to the Norway's system.
It is manageable, but it adds some overhead. On the other hand, when using AppStore, Apple is the merchant on record and the only thing I have to do for our AppStore sales is to upload an invoice to Apple in the ITC.
This is a great idea. The main disadvantage to me is the tax remittance of various local sales/digital taxes for each user. How do you plan to deal with this?
Nice solution! I do wonder if using the facebook/snapchat/tiktok pixels will work as webkit uses ITP which blocks 3rd party cookies by default though?
That's a really fantastic point. I would imagine they work b/c it would be against FB/IG's interests to block their own pixel. It's their in-app browser. We'll see what the data shows. If that's the case, I can do server to server events for Facebook but will be SOL for the others.
Currently, it seems all 3rd party cookies are blocked in webkit. Browsers on iOS are all based on webkit, so no way around that. There is the option to use script-writable storage (like localStorage) but those expire after 7 days of inactivity. But within that 7 days your solution could work maybe?