Hi Jim and Michael,
I have been exposed to this requirement too. The issue is not so much how to get it into BYD. It's more of capturing the information in a meaningful way. When the client receives a shipment of e.g. 1,000 ea of an item, no one whats to scan each and every item to capture the SN. Rather what we found was that if you can scan the start and end SN of the shipment, you can create code to populate the migration templates for the inbound shipment.
Next question then becomes how you are going to use the SN items in your production process and during the outbound delivery process. I have unfortunately not found a meaningful way to record the SN during the production process, other than using the "Notes" field, which by default is not scalable and error prone.
As for the outbound delivery I still may have the scalability issue. If I e.g. ship 300 ea I would still have to revert to scanning/entering a start and end SN, and have code populate the data migration template.
Hans