Hi, thanks for the great work on clz.
I would like to track the lots that I bought together and how much I paid for them all, I was using the storage box field with a format: date - lot_identifier - price like [20201021 - 595 - £9.44], but now I started using that field properly so I was thinking on alternatives already existing.
I tried the personal notes but that field is not a field you can group by.
I understand that the notes field is a free text so not a good idea to allow to group by it ,so would you please consider adding one “purchase lot info” or similar that would allow to group by it?
While on the subject, maybe it would be possible to add another field “purchase lot price”.
You could use a tag to mention that a group of comics is part of a purchasing lot field, and perhaps just add the purchase price of the lot to just one of the comics (so your statistics would be correct).
This would be a workaround.
I’ve taken note of your request here.
Side question:
If you’d have a Purchase Lot field, with a subfield inside (the purchase price) (this is technically a bit difficult), what would you expect to happen if you fill in the purchasing lot purchase price field, when it comes to your stats, if you’ve also (accidentally or not) filled in a purchase price for 1 comic in the regular purchase price field? Would that field just be ignored?
I’ll try the tag, I did not think of the tags as that is not as easily edited as a normal field is.
I wanted the very simple informational only fields as I know it can become very complicated to create a real shared lot grouping feature that would have the price paid, total books in the lot, and for such pricing info that can be used to automate filling the individual purchase price.
The ideal world would be more like having a “lot building” mode where you would add the books and say they’re part of the lot. And when you finish adding the books, you would say close lot, what would track how many books there is in the original lot and to calculate the individual purchase price using an equal share of the total price and then that information would become static.
I used the storage box to avoid having to count all the books in advance and then when I finished and knew the quantity of books I would group by the box and fill the purchase price to all books in the lot.
If you would remove one or more books, that initial information should not change as the price paid for the lot and the decision you have used to define on individual purchase price did not change.
In such case, I also normally move the book to another collection and the statistics would not work across collections anyway.
I tried now after many years, it’s a better way to work with it as you can add them with the spaces included if you want and they’re added directly.
In the past I I think I remember having to click to add them first but I can’t remember what the issue was and I never used again until now.
So no issues on the tagging mechanism that I could find now, but it would still be great to have the extra fields if one day you ‘re able to do it.
Thanks in advance.
@CLZ_AJ I was just entering some books, and I remembered it was about not having the auto completion to it.
If you’re adding with a copy and paste tag just accept it, otherwise you need to go into the tag management and select the tag
I also use tags for this, but I think that a field for invoice/receipt/itemid(eBay) number would be useful not only lot tracking, but also expense tracking. This field would be a complement to the price paid and store fields.
What exactly would you do with this information?
Is it like a sales tracker for eBay, taxes, stuff like that?
“Expense tracking” is already possible with the Purchase Price I think - but adding the ebay item id/invoice/receipt.. not sure.
We do plan to allow more images per item, where you could upload an image of your receipt from your LCS.
You can also already use the LINKS tab to put an eBay link if you like.
Or a link to an online receipt if you have it.
For tax purposes, I need to report any profits when selling books. Being able to track which invoice/item (record of purchase) is needed for this reason. The IRS will not simply accept an arbitrary value entered into a price field. Further the price reflect several components: book price, sales tax, shipping, improvements (bag & boarding, CGC fees, pressing fees, etc.). In the case of shipping, combined shipping would need to be divided across all books in the order to be recorded properly.
TDLR; having a field to point at the purchase record would be very helpful. I am currently storing this info in a JSON object within personal notes.
Thanks for the extra information as to why you would like these fields.
Are you using this for like an actual business, or is this a personal selling/buying venture?
Personal selling. I buy a lot of 100 books or more hoping to find some gems and then sell off the rest to offset costs and to reduce required storage space. And at current I am not doing much selling, but rather fighting with eBay.
I understand, hah, fighting with eBay, got that right :).
It’s just in your other posts I noticed something like “We scan the bar code on our comics to jump to the record for that book.” - (on our side, we see users use “we” often when they are actually a company) and entering SKU (which to us usually indicate Stock Keeping Unit, which in turn is usually for business keeping stocks of inventory).