You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure how this would work yet, but I'm needing some way to automatically generate the labels for orders based on the order item(s) weigh and size.
I suppose there needs to be some kind of defaults table per store with the ability to assign carriers and services for things like order weight, category, customer class, etc.
Is this a scenario for any of your clients? Any ideas of where to get started?
The text was updated successfully, but these errors were encountered:
@batonac Yo! The label generation API has worked for me in the past in previous iterations of this app. Also, I think we want to manually generate labels because you are charged per label. Both approaches have room for abuse, but only one can be charged back to the developer.
As far as setting defaults, there are multiple ways to solve this but I think that leveraging/ extending the Shipping Rule doctype makes the most sense.
@batonac, I agree with @agritheory in keeping label generation responsible to an actual user considering it's going to rack up costs. We haven't had a client who has wanted auto-generation of labels yet, but if you think it's something worth looking into, feel free to add a design spec here.
I'm not sure how this would work yet, but I'm needing some way to automatically generate the labels for orders based on the order item(s) weigh and size.
I suppose there needs to be some kind of defaults table per store with the ability to assign carriers and services for things like order weight, category, customer class, etc.
Is this a scenario for any of your clients? Any ideas of where to get started?
The text was updated successfully, but these errors were encountered: