#discodanne

1 messages · Page 1 of 1 (latest)

polar currentBOT
wild sky
#

Products are always service. The type field is legacy cruft actually(the good type was only used for our legacy Orders API which was deprecated several years ago). It's confusing but we haven't cleaned this up yet

I don't know what hierarchy_level_0 is , from what I can tell it's an internal field that is unfortunately leaking out, so really you should ignore it

#

to me I would use metadata to mark if something is physical or a service for my own product cataloguing, and as you say, separately there is a category to set for tax calculation purposes

pulsar marlin
#

I suspected that type was deprecated since its not in the documentation anymore. Glad to have that cleared up. Do you have any go to logic that I could use to determine if a product is goods or service?
hierarchy_level_0 would work if it actually got return from the api. Since it can be "service" | "physical" | "digital" having that would solve al my issues.

#

So the only way to categories products is to set metadata on all products?

wild sky
#

ignore hierarchy_level_0 please

wild sky
pulsar marlin
#

For what I know shippable cant be set when creating a product from the dashboard?

wild sky
#

probably not, I think it's also a field related to the old concept of type:good

#

that's why I said metadata as the easiest/best option