Fix supplier barcode order numbers

[30350n]

Seems like the logic for retrieving a purchase order from an order number from a supplier barcode got broken when refactoring. This fixes the logic and also some supplier specific details.

[netlify]

✅ Deploy Preview for inventree-web-pui-preview ready!

Name	Link
🔨 Latest commit	f459df0
🔍 Latest deploy log	https://app.netlify.com/sites/inventree-web-pui-preview/deploys/659ecc5c3c1c3900088c1f4f
😎 Deploy Preview	https://deploy-preview-6158--inventree-web-pui-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 100 (no change from production) Accessibility: 86 (no change from production) Best Practices: 92 (no change from production) SEO: 70 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[30350n]

(I'll add some test cases later to confirm this keeps working in later versions.)

[SchrodingersGat]

@30350n can you please provide some more specific information about how the current implementation is "broken"?

[30350n]

Sure!

1. The current implementation always checks for both the PO and CPO matching, if both are present in the barcode. Having a match on one of them should be sufficient.
2. LCSCs and TMEs barcode POs were incorrectly labeled as CPOs. TME actually has a CPO field though, which hasn't been used.
3. Mouser uses the ecia barcode 'K' field for both, POs and CPOs interchangeably (yeah I know, don't ask me why).

[30350n]

Actuall the implementation I came up is kind of convoluted I guess, I'll try to refactor it a bit.

[30350n]

Not sure if this makes it better 😅

[SchrodingersGat]

@30350n if you have the data on hand to test that this works, I'm satisfied with that. please keep an eye on whether this continues to work

[30350n]

Thanks, will definitely do! I actually also wanted to confirm everythings actually working correctly with some tests but didn't find time to implement them yet. I'll try to get that down the coming days and create another PR 👍

(I did quickly test this on my production server though and it did the trick.)