My Laravel-based shipping site is accidentally generating two identical Tracking IDs every time 2 users screate a shipment, and it’s starting to cause real confusion in our fulfilment flow. I have full source-code and database access ready for you, so you can dive straight into the controller logic, Eloquent models and any related MySQL constraints. The duplication shows up only at the moment the shipment record is first saved; all other processes (order updates, user registration, etc.) work fine. I need the underlying cause identified and patched—whether that means refactoring the ID-generation method, introducing an atomic transaction or adding a unique index in a migration—so that each shipment ends up with one and only one unique identifier. Deliverable: a clean Git commit or pull request that fixes the bug and includes any necessary migration or test coverage to prove the issue no longer occurs. Please keep existing functionality intact and leave brief inline comments explaining the change so my in-house team can follow along.