| Redisplay Messages: Compact | Brief | All | Full Show Messages: All | Without Replies| Author: | calsbricks  | | Posted: | Sep 15, 2017 12:23 | | Subject: | Re: Change to information held in Catalogue | | Viewed: | 27 times | | Topic: | Suggestions | |
| In Suggestions, calsbricks writes:
| | In Suggestions, qwertyboy writes:
| | In Suggestions, calsbricks writes:
| | The Bricklink catalogue has the perfect base for this change but it is a question
of whether the developers feel they can do it with minimum effort. Each item
in the catalogue has a PCC as well as its mould or design id number associated
with it. The PCC code is Lego's element id and it is what they print in their
instructions.
There have been lots of comments both in and out of the forum concerning part
weights and how there is a variance between colours of the same part number.
We have also experienced this. The simple way to deal with this is to add a weight
field against the PCC in the catalogue. This would allow the system to hold the
individual weights for each colour part and could be used to more accurately
provide cart weights for instant checkout when it comes out of preview.
|
I would vote no, for two reasons:
- In 627 orders processed on the other site, with them having one weight for
each part no, we haven't experienced one single issue. Weight differences
are small, the likelihood of this "screwing up" auto-checkout is minimal, and
if it does make an err, the seller can chalk it up to the cost of doing business.
- TLG is known to have made changes to their molds just to save a few cents
by requiring less ABS. These changes are done to parts that keep the exact same
PPC, and most times BL doesn't differentiate (think hollow versus solid pins
under a 1x4 brick for example). Those weight changes could actually be more significant
than the weight change for different colors. In effect, the weight-per-PPC will
almost always be an approximation, not the 100%-always-correct-weight for a PPC.
In short, I am convinced these weight differences are a non-issue for auto-checkout.
Experience proves this. I am sure others can verify this. Don't make things
more complex than they need to be.
Niek.
|
Thank you for your comment. Your opinion is noted, however I am not convinced
using the other site as a reference point is really relevant. The other site
also has proper dimensions for each part, which BL does not and as far as I can
tell from the brief look at the preview site the implementation here is different
to that over there. We sell lots and lots of bulk orders and a small difference
on an individual part can make a significant difference overall. As far as putting
that down to cost of business we will let you do that - it is of no interest
whatsoever to us. Maintaining margin/profitability is a key factor to a successful
business and taking all steps necessary to prevent additional costs is one small
part of that. With over 4000 order on this site we have no mistakes on postage
costs - once bl's implementation of instant checkout can be shown to provide
that reliability we will consider using it, however it is not of major importance
to us at the moment. There are far more important things to deal with.
|
Sorry I mis-read part of your original post. We are not trying to overly complicate
things - our suggestion, we believe, would help not hinder, and I do not believe
in any way did we say that this would prevent 'screwing up' with instant
checkout. We suggested it would help - not hinder.
As for your opinion, you are, of course entitled to it as we are to ours. You
have been around this site nearly as lone as we have so you will appreciate that
lots of people differ on what is needed, what is important etc. That is the way
life and business goes but it is more than essential to compare apples with apples
not apples and pears. In terms of coding this is a simple change and would take
any programmer less than a day to achieve it and it may, yes may help - it certainly
isn't going to hinder by any stretch of the imagination.
|
 |
| Author: | calsbricks | | Posted: | Sep 15, 2017 11:54 | | Subject: | Re: Change to information held in Catalogue | | Viewed: | 42 times | | Topic: | Suggestions | |
| In Suggestions, qwertyboy writes:
| | In Suggestions, calsbricks writes:
| | The Bricklink catalogue has the perfect base for this change but it is a question
of whether the developers feel they can do it with minimum effort. Each item
in the catalogue has a PCC as well as its mould or design id number associated
with it. The PCC code is Lego's element id and it is what they print in their
instructions.
There have been lots of comments both in and out of the forum concerning part
weights and how there is a variance between colours of the same part number.
We have also experienced this. The simple way to deal with this is to add a weight
field against the PCC in the catalogue. This would allow the system to hold the
individual weights for each colour part and could be used to more accurately
provide cart weights for instant checkout when it comes out of preview.
|
I would vote no, for two reasons:
- In 627 orders processed on the other site, with them having one weight for
each part no, we haven't experienced one single issue. Weight differences
are small, the likelihood of this "screwing up" auto-checkout is minimal, and
if it does make an err, the seller can chalk it up to the cost of doing business.
- TLG is known to have made changes to their molds just to save a few cents
by requiring less ABS. These changes are done to parts that keep the exact same
PPC, and most times BL doesn't differentiate (think hollow versus solid pins
under a 1x4 brick for example). Those weight changes could actually be more significant
than the weight change for different colors. In effect, the weight-per-PPC will
almost always be an approximation, not the 100%-always-correct-weight for a PPC.
In short, I am convinced these weight differences are a non-issue for auto-checkout.
Experience proves this. I am sure others can verify this. Don't make things
more complex than they need to be.
Niek.
|
Thank you for your comment. Your opinion is noted, however I am not convinced
using the other site as a reference point is really relevant. The other site
also has proper dimensions for each part, which BL does not and as far as I can
tell from the brief look at the preview site the implementation here is different
to that over there. We sell lots and lots of bulk orders and a small difference
on an individual part can make a significant difference overall. As far as putting
that down to cost of business we will let you do that - it is of no interest
whatsoever to us. Maintaining margin/profitability is a key factor to a successful
business and taking all steps necessary to prevent additional costs is one small
part of that. With over 4000 order on this site we have no mistakes on postage
costs - once bl's implementation of instant checkout can be shown to provide
that reliability we will consider using it, however it is not of major importance
to us at the moment. There are far more important things to deal with.
|
|
| Author: | calsbricks | | Posted: | Sep 15, 2017 10:09 | | Subject: | Change to information held in Catalogue | | Viewed: | 130 times | | Topic: | Suggestions | | Status: | Open | | Vote: | [Yes|No] | |
| The Bricklink catalogue has the perfect base for this change but it is a question
of whether the developers feel they can do it with minimum effort. Each item
in the catalogue has a PCC as well as its mould or design id number associated
with it. The PCC code is Lego's element id and it is what they print in their
instructions.
There have been lots of comments both in and out of the forum concerning part
weights and how there is a variance between colours of the same part number.
We have also experienced this. The simple way to deal with this is to add a weight
field against the PCC in the catalogue. This would allow the system to hold the
individual weights for each colour part and could be used to more accurately
provide cart weights for instant checkout when it comes out of preview.
|
|
| Author: | calsbricks | | Posted: | Sep 12, 2017 11:56 | | Subject: | Re: Moderate Forum Posts | | Viewed: | 42 times | | Topic: | Suggestions | |
| In Suggestions, StormChaser writes:
| | I suggest that members with 2 or less feedback have their forum posts moderated,
meaning that posts must be approved by a moderator before appearing in the forum.
This should resolve the issue of scammers joining BrickLink merely to post spam
in the forum.
|
Yet another +1
|
|
| Author: | calsbricks | | Posted: | Sep 11, 2017 12:15 | | Subject: | Re: Separate email addresses for buying/selling | | Viewed: | 29 times | | Topic: | Suggestions | |
| In Suggestions, stecre writes:
| | I think it would be very useful to be able to have separate email addresses for
your buying and selling activities.
I operate a store but also have wanted lists and buy from time to time and being
able to separate the various emails to different addresses would be helpful.
e.g.
To the "Buying" email address:
Any messages regarding orders you placed e.g. Invoices etc.
Wanted list notifications
To the "Selling" email address:
Any messages regarding orders received e.g. invoices, payments
Emails about Fees
Perhaps there could even be a configuration page for users to select which emails
they would like to go to which address?
Yes you can probably achieve this with filters on your email client if on a PC
but not sure about phones and other devices.
Thanks,
Steve
|
Voted yes but I think this needs to be expanded. Holding multiple address records
has its problems but it really is the only way to go. We, as a store, have 2
distinct locations - one for our storage/picking centre and one for order processing.
If Bricklink allowed us to hold multiple addresses ((including e-mail addresses)
it would make life much easier, There are issues with doing that but most organisations
have overcome those and I am sure BL can do the same.
|
|
Next Page: 5 More | 10 More | 25 More | 50 More | 100 More
|
|
