CSV import misses matches when the printed number includes the set size

Expected Behavior

I downloaded the Ludex CSV import template, opened it in a spreadsheet and copied each card's exact printed or Slab number into the card_number field.

Actual behavior

Kevin Durant · 2007–08 Topps Rookie Set: 2 of 14 returned 0 matched, 1 needing identification. In a controlled preview, changing only card_number to 2 returned 1 match.
Gengar · 2022 Lost Origin Trainer Gallery: TG06/TG30 did not match and TG06 matched. The Ludex export also lists TG06.
Mega Gengar ex · 2026 Ascended Heroes: 284/217 did not match. Both 284 and #284 matched. In this example, the leading # was accepted.

Customer details

Tristan Balint · Ludex Collections web (Early Beta) · My Collection → Add Cards → Import CSV

Reproduction / Investigation Notes

Download the CSV template and create one row for a card listed above. Format card_number as text.
Enter the full printed number on card or slab, upload the CSV

Why the full number matters

My 1st instincts were copy it exactly how the slab or printed number shows for best results.
Pokémon: 284/217 shows that card 284 falls beyond the main set of 217. The number 284 alone loses that comparison. The slab identifies this card’s specific rarity as Special Illustration Rare. A historical example is Dark Raichu 83/82, which PSA identifies as a Secret Rare.