Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shipping Tax #70

Open
tomaszfelczyk opened this issue Oct 19, 2018 · 3 comments
Open

Shipping Tax #70

tomaszfelczyk opened this issue Oct 19, 2018 · 3 comments
Labels
Feature New feature proposals.

Comments

@tomaszfelczyk
Copy link

Shipping Tax is hardcoded to zero.

@bartoszpietrzak1994
Copy link
Contributor

Hello Tomasz,

Indeed, it's a missing feature. Since we want to spend some time in the nearest future on stabilizing plugins, we will for sure investigate this issue in order to provide the most extensible and functional solution.

@Zales0123 Zales0123 added the Feature New feature proposals. label Nov 26, 2018
@tomaszfelczyk
Copy link
Author

tomaszfelczyk commented Nov 26, 2018

Hi @bartoszpietrzak1994 ,
Thanks for the reply.

  1. In my opinion, this plugin could be more generic and support more than one type of docs with individual sequence numbers (receipts/invoices/credit memos etc.) and templates. This will be really helpful if in future in case of using external cash registers in POS or just in case you generate a simple receipt for each order in the first channel and VAT invoice in another channel (B2B).

  2. In Sylius we already have sequence generator used in OrderBundle. Have you thought about decoupling it to independent Bundle/Plugin with the support of many sequences?

@Zales0123
Copy link
Member

Hello, Tomasz 🖖

  1. You're right, however, we really focus right now on delivering the best basic functionalities, which is also easy to extend or customize - the same purpose, as for Sylius itself :) we will for sure be thinking about additional features after plugin's stable release.
  2. We were thinking about it some time ago, the idea had gone due to lack of time and resources, but, again, I'm sure we will do something with it in the future (hopefully not-so-far :))

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature New feature proposals.
Projects
None yet
Development

No branches or pull requests

3 participants