database design for multiple uom and pricing for each item
Table Products
id_product| name | ....
1 | abcd | ....
---
Table Pricing
id_price | qty | price_type | price
1 | 20 | discount | 20
---
Table Unit
id_unit | fromUnit | factor | toUnit
1 | carton | 8 | pkt
2 | pkt | 24 | units
I am designing database for commercial business. Basically, each product may have multiple uom and pricing plan.
E.g. item A can be sold in carton or pkt, and there will be a default uom to be converted to.
Case:
User can order in 1 carton which equal to 192 units, or order in one
pkt which equal to 24 units.When user receive the item, the item might be in different uom. E.g. order in pkt but received in carton.
I will always convert and store the received uom, so that i can track in my inventory.
Any suggestion on how can i design my database and link the table based on the cases for multiple uom and multiple pricing issue for product? Thanks.
database-design
New contributor
add a comment |
Table Products
id_product| name | ....
1 | abcd | ....
---
Table Pricing
id_price | qty | price_type | price
1 | 20 | discount | 20
---
Table Unit
id_unit | fromUnit | factor | toUnit
1 | carton | 8 | pkt
2 | pkt | 24 | units
I am designing database for commercial business. Basically, each product may have multiple uom and pricing plan.
E.g. item A can be sold in carton or pkt, and there will be a default uom to be converted to.
Case:
User can order in 1 carton which equal to 192 units, or order in one
pkt which equal to 24 units.When user receive the item, the item might be in different uom. E.g. order in pkt but received in carton.
I will always convert and store the received uom, so that i can track in my inventory.
Any suggestion on how can i design my database and link the table based on the cases for multiple uom and multiple pricing issue for product? Thanks.
database-design
New contributor
add a comment |
Table Products
id_product| name | ....
1 | abcd | ....
---
Table Pricing
id_price | qty | price_type | price
1 | 20 | discount | 20
---
Table Unit
id_unit | fromUnit | factor | toUnit
1 | carton | 8 | pkt
2 | pkt | 24 | units
I am designing database for commercial business. Basically, each product may have multiple uom and pricing plan.
E.g. item A can be sold in carton or pkt, and there will be a default uom to be converted to.
Case:
User can order in 1 carton which equal to 192 units, or order in one
pkt which equal to 24 units.When user receive the item, the item might be in different uom. E.g. order in pkt but received in carton.
I will always convert and store the received uom, so that i can track in my inventory.
Any suggestion on how can i design my database and link the table based on the cases for multiple uom and multiple pricing issue for product? Thanks.
database-design
New contributor
Table Products
id_product| name | ....
1 | abcd | ....
---
Table Pricing
id_price | qty | price_type | price
1 | 20 | discount | 20
---
Table Unit
id_unit | fromUnit | factor | toUnit
1 | carton | 8 | pkt
2 | pkt | 24 | units
I am designing database for commercial business. Basically, each product may have multiple uom and pricing plan.
E.g. item A can be sold in carton or pkt, and there will be a default uom to be converted to.
Case:
User can order in 1 carton which equal to 192 units, or order in one
pkt which equal to 24 units.When user receive the item, the item might be in different uom. E.g. order in pkt but received in carton.
I will always convert and store the received uom, so that i can track in my inventory.
Any suggestion on how can i design my database and link the table based on the cases for multiple uom and multiple pricing issue for product? Thanks.
database-design
database-design
New contributor
New contributor
New contributor
asked 7 mins ago
CrazyCrazy
101
101
New contributor
New contributor
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Crazy is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f229699%2fdatabase-design-for-multiple-uom-and-pricing-for-each-item%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Crazy is a new contributor. Be nice, and check out our Code of Conduct.
Crazy is a new contributor. Be nice, and check out our Code of Conduct.
Crazy is a new contributor. Be nice, and check out our Code of Conduct.
Crazy is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f229699%2fdatabase-design-for-multiple-uom-and-pricing-for-each-item%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown