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

new task: Add variants to shipping profile #202

Closed
mattsodomsky opened this issue Feb 7, 2023 · 2 comments
Closed

new task: Add variants to shipping profile #202

mattsodomsky opened this issue Feb 7, 2023 · 2 comments
Assignees
Labels
task request https://mechanic.canny.io/task-requests

Comments

@mattsodomsky
Copy link
Member

Similar to this task: https://tasks.mechanic.dev/auto-associate-products-with-a-delivery-profile-by-product-tag

But, for variants. And, because variants don't have tags, we'll need to use some other attribute(s) to assign the the shipping profile.

Sku? metafield?

@mattsodomsky mattsodomsky added the task request https://mechanic.canny.io/task-requests label Feb 7, 2023
@tekhaus
Copy link
Collaborator

tekhaus commented Feb 7, 2023

There are a lot of good candidates for the criteria to be used here. Perhaps we choose one and then other developers can adapt from there.

For example, a shipping profile could be set up for bulky/heavy items. So, in that scenario, the task could be configured to add ANY variants that are equal or greater than the shipping profile weight to that shipping profile.

There are some tasks in the library that support using almost any type of attribute on a product/variant (and one more coming soon), but it's possible that might be a bit overkill for this task.

@mattsodomsky
Copy link
Member Author

Could we do a few and then let developers go from there?

metafield and sku? (weight is interesting as well but logic might be too different?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task request https://mechanic.canny.io/task-requests
Projects
None yet
Development

No branches or pull requests

2 participants