@sellshop I’d like to know this too. I’ve migrated one of my shops to thirty bees but have held back on my main shop which uses the Amazon and eBay module. These are critical for us so I need to be sure they will work properly, but how can I test this before migrating?
Currently it seems that even the unapproved items are available for download which I would not recommend. Given 1.0 is fully translated, you should download a zip, which always contains both branches, copy release 1.0 into whatever else release and upload the file again.
It would be much easier to activate the zip download/upload for every file minimum for the proof readers to exchange only those files of the new branch that were not complete yet. Crowdin doesn’t always work properly, so this would be a safer way.
From my experience I wouldn’t recommend the xliff down- and upload.
It depends on the jurisdiction, but for example in some countries you are legally obliged to keep all information that is necessary to understand a business transaction for X years. I would argue that this includes the “order” in the shop, which is why the customer’s request to delete their data is really only as outlined above.
No. It is very good when You have base unit and then multiplier/divider or something which is limit for how small pieces You can divide this item. For example 0.1 or 0.01 or why not 10. Then You can sell 0.5 and other 0.5. Both “half items” are for program completely different items and also two completely different invoices. Only client has feeling that there was one half and other half. And then You can choose payment type for each invoice. But this is my opinion and maybe there are only 1% who need this in real life.
We also use a high degree of automation in our business. We use the webservice for some things and for others we write directly to the database itself over a secure connection.
The web service is ideal for creating the listings when a site is first launched as you can upload photos and you can be sure that the site and each item will be properly set up.
On the other hand if you need to update prices for 100,000 different products (for example) it will take a long time over the webservice and require many separate calls. However if you upload a CSV file with new prices, read it into a temporary table using MySQL commands, and then use SQL joins to update the data, you can update many thousands of items in just a few seconds.
Of course writing directly to the database tables is not a recommended or supported idea. Newer versions of 30bz will probably change the database structure somewhat and any code that writes directly to the database tables many need to be rewritten to be compatible with new versions of the platform. This is the risk, but until there is a bulk update functionality in the webservice (which I hope happens!) direct table updates are the only viable way to update vast amounts of data in a reasonable amount of time.
Can you please help me with the quantity update of the articles. By the separate article variant import - I am somewhat confused? The lists contain articles with and without variants.
We get from our wholesaler update lists (xls-x and excel csv) with a column item number and a column quantity. How do we import these lists best?