Goods and Services ecommerce use cases #5830
ehuelsmann
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Goals
The intent is to extend the "Goods and Services" features with more e-commerce compatibility and still keep it simple to use. Cover more user cases
Current status, what do we have? (02-2020)
Proposals
( actual justification is that ecommerce need these measurement to make automatic rating request to ups, canada post, usps, and postal services )
keep a complete integrity of the data set for normal product
1 table for group attributes, and then another for the attribute them self and then work around these two
Irc/Riot discussion
Started at Irc / Riot medio february 2020 on https://vector.im/develop/#/room/#ledgersmb:matrix.org (slightly edited).
[NS]
Example:
Weight unit
The unit of measurement for weights. @@@ why don’t we have a unit of measurement for distance as well??? And maybe a unit of measurement for content?
Absolutely, you need to have a default unit for measurement, such as Metric or Imperial
ehuelsmann
But if we have alternative unit classes, which to apply to which good? And what do we use the unit for? Does it even matter that the description says "weight"? I used to put in "ea" (for "each"). Never broke anything...
[NS]
unit of measurement I mean, for tangible items
the width, height and length of products, but that why I asked if it was a valid suggestions, if there is another way to default these somewhere else, Ill eventually find it out
I understand that you may sell services that are virtual, thus, none of these apply
ill look at the unit class :)
[NS]
but having a way to choose between metric and imperial and possibly switch between them using convertion, that be cool ;)
[NS]
but the more important reason for that request
the actual justification is that ecommerce need these measurement to make automatic rating request to ups, canada post, usps, and postal services, the weight isn't enough
so I guess my real question is, would there be a way to have width, height and length (the 3-dimension of a part) input field ?
ehuelsmann
there's always a way.
but currently, there's no corresponding database field.
or fields.
based on your description, I think there should be 3 fields; ones to be handed to the "price calculator".
[NS]
well yea I would like to see 3 field added, then what we do with the data, would be up to the person, but having it would be an important part of later integration with the online shop world
a must I have to say
even if they were defaulting on 0/null to be implemented
width, height, length respectively
these are appart from an "item possible custom attributes"
because anything that is physical, such as item, any of em, has a 3d dimensions
it not essential data to accounting, but it is essential data to part/product's data set. Integration into others erp/crm or inventory shipping/handling software, etc
ehuelsmann
to be honest, not just 3d. 4d: because it also has weight.
[NS]
oh absolutely, but that one is already there
ehuelsmann
right.
[NS]
nothing urgent, nor even needed anytime soon, but do you think I can add the suggestion ?
ehuelsmann
so, while I do not necessarily disagree with you, I'm always looking to compromise to keep our application relatively simple to understand.
[NS]
but if you already have weight, dont it justify the existance of the 3 others missing dimensions ? ;p
ehuelsmann
that means that with every feature we add (or entry field), I'm looking at how we may be able to address the same requirement with what is already there, or what can be minimally added to (abuse) what's already there for the use-case.
ehuelsmann
sure.
but for my use-case (services)
I need none of the 4.
[NS]
oh it could be left blak
ehuelsmann
so for me, it just takes up screen space.
[NS]
absolutely
I have customer with their eshop who sell video. We created an option to completely hide dimensions and set them all to 0 :) the customer was happy lol
and we still had a complete integrity of the data set for normal product if it ever was needed
ehuelsmann
right. that's the type of solution I'm looking for too: keep things simple until otherwise required.
[NS]
alto, correct me if I am wrong, but the system already have 2 different input pages, one for part, and one for services
so I can aim my suggestion at the part one specifically with the mention of an option to hide these at all if needed
ehuelsmann
yes/no. the input pages look different indeed. but they're based on the same template.
hasorli
@freenode_NS:matrix.org: Parts. I would also add some more info to the parts screen. I have a customer with 1 part with 200 colours with different EAN numbers.
Their current system solves this with a "main part" with sub parts. You look up the main part, and can show all the sub parts from the main part.
[NS]
these would be attributes technically tho products attributes that could lead to a different price
to do like amazon and newegg and the like
yea we call those attribute because you would make 1 table for group attributes, and then another for the attribute them self and then work around these two
but that a major change in inventory system so it have to be very very well planned
but once it in place, it allow for effective unlimited possibility in the ecommerce world
it would also allow to be bridge with others inventory system and erp in a certain way, or at least would open the door for more compability and uses case
im use with both, virtual services and items structures
Beta Was this translation helpful? Give feedback.
All reactions