Duplicate lot's

robernat

When overviewing ones own inventory a number of duplicate lot's might show up (does in my case).
Unfortunatly this is related to non identical lot's, but BO's still interpretes them and shows them as being 'duplicate'...

The system does not separate new from used lot's (neither subcondition of used) and neither looks at the bulk setting of certain lot's.
These different types of lot's should not show as 'duplicate' lot's

Example: I have part '2825' 3 times in my store: one lot of 'new' ones, one lot of 'used' ones and one lot of 'used, with bulk=25'. The system calls them being 'duplicate lot's' but they are not for obvious reasons...

Admin, can this please be resolved as checking for duplicate lot's is a handy tool to catch listing errors and allows to merge certain lot's if really duplicate by mistake, it's not efficient to have to browse through hundreds of lot's who are asz a matter of fact *not* duplicate lot's.

Thanks, Eric

Lawrence

The system considers items with different bulk quantities to be a duplicate lot. I think it gets a bit confused, and once it has found a duplicate lot, it then so is all items fitting that criteria, regardless of condition. In general, it does not consider items with a different condition to be a duplicate.

robernat

Apparently it 'auto-solved', I launched BOBL sync last night and while it was running, about a 100 duplicate lot's showed up. I was checking those straight away to make sure there where no flukes, but apparently the sync adjusts things in batches (like personal note). Not unlikely BO wasnt able to catch up right away due to the high load of creating lot's in my store (over 4000 in about an hour).
Anyway, thanks for clarifying, no duplicate lot's are showing up now (not even the ones with bulksettings), so perfect :-)

Stragus

As seen from the web interface, inventory updates are always slightly delayed (unless viewing lots directly under the "Sell" tab for a part). It takes a few minutes to show up, I assume it's because BrickOwl regularly integrates all changes from the last couple minutes in batches...