April Release of Saleor: VAT support is here

VAT support, customer notes, simplified stock management, improved UX, several bug fixes & improvements

We are excited to announce the April 2018 release of Saleor!
Long awaited tax support is here, fetch the latest rates straight from the European Commission databases, decide if you want to display gross or net prices to your customers, charge or don't charge taxes on the shipping cost. Simply enter your prices the way you prefer - with or without taxes, and we will take care of the rest.

Apart from working hard on our Dashboard 2.0 (planned for June 2018), built with GraphQL and React goodness, we still managed to squeeze out a few new features!
Also, this release includes various bug fixes and improvements.

Vat Support for European Countries - #1929

Taxes can be a complex matter, but Saleor aims to make the setup as painless as possible.
In order to achieve that, we’re introducing vatlayer integration, providing reliable and up-to-date EU VAT rates.

Global tax support is coming in the future as we are planning to integrate with Avalara, so much so soon!

Improved Menu Management - #2046

Menus can be assigned from the Dashboard in the blink of an eye. Create various versions, test what works best for you and pick your favourite!

Add Notes About Your Customers - #2043

Sometimes, you need to keep notes about your customers that you can refer to them later on. Whenever you want to mark a loyal customer, add a reminder about the necessity of a free gift, or keep an eye on troublemakers - we’ve got you covered. April’s release brings you the possibility to add notes that are only visible for you as the merchant.

Simplified Stock Management - #1996

We found that multiple stocks can be a little bit of overkill for most of the e-commerces, so we've simplified things a bit.

Stock and StockLocation models were dropped, quantity and cost price can be directly assigned to each Product Variant. Right now stock management is a piece of cake! 🍰

Save Product Collections As Drafts - by @apsummers in #2109

This option is something some users have wanted for quite a while. Whenever something interrupts you, no matter if that’s a coffee break, time to go home or an annoying colleague, save collection as draft and come back to it later. In face of the sale, prepare your collection beforehand, waiting for big day to come, also draft collections can be only seen by staff!

Other Features:

• Product Variant is named automatically after its attributes - #2026
• Random data should contain more, not so random, real-life examples. (@NyanKiyoshi in #2089, #2064)

GraphQL:

• We’ve added new endpoints for ProductType and ProductVariant. #2091, #2062
• Building cross-domain client is not possible with Django’s CSRF mechanism, so we started handling authentication of API operations via custom JWT middleware. #2101
• Product data to contain Collections now. #2073
• Errors should be handled more gently on CreateToken mutation. #2082
• Change Product Attributes representation in the query result. #2111

React (Dashboard 2.0 branch):

• Added React Storybook, UI development is smoother than ever. #2028
• Jest Snapshot is a very useful tool if you want to make sure your UI does not change unexpectedly. We just integrated it with the Storybook. #2124
• Created “Products” App to manage products. #2045
• Update packages used to new versions. #2097

Fixes:

• Due to a bug children’s menu items were incorrectly displayed as parents’. Children eventually become parents, but that’s not the prefered way. (@eskerda in #2085)
• On certain browsers PDF files were not recognised properly, it shouldn’t happen anymore. (@NyanKiyoshi in #2058)
• Naming in URLs could be confusing, so we unified them. #2079
• Button in VariantPicker contained unnecessary dots. This release introduces 100% dot-free buttons. #2061
• In certain configurations placeholder images would not appear at all. Placeholders should now hold their place. #2060
• Simplify Redis settings #1898
• Have you seen nameless ProductVariant in the breadcrumbs? Neither have we so we’ve added fallback for its SKU. #1949
• And finally, fulfilment email was missing some data, we’ve just got better at fulfilling stuff. #2087

Documentation:

• Our license was not properly recognized by Github due to some small changes we had introduced - it now is. #2068
• Fix of a small spelling mistake. (@olivrg in #2085)

Performance:

• Several views should be now optimized and nicer for your database. #2059

Contributors

@apsummers, @eskerda, @NyanKiyoshi, @olivrg thank you for all the effort you put into contributing to this release, together we can make a difference!

Moved to the next release:

• We know that shipping price calculation could be handled better, we will try to handle that in the current release. #2029, #2054
• Checkouts should be saved in the database, that’s the first step for cart & checkout recovery! #2004

A big thank you 🙏 for your support and contributions! 👏

Check out our blog post about this release!