Database rows first
The data structure accepts direct OEM-to-LBG rows, so coverage can grow without exposing source matching work.
Replacement reference
OEM code -> LBG SKU
Search an OEM sprocket code and use Langbiang Gravity as a cross-reference path to public LBG SKU candidates. The OEM-LBG database stays private, and final fitment still needs verification before production or purchase.
1. OEM codeMatch the customer part number.
2. Private databaseResolve OEM code to LBG SKU.
3. LBG SKUShow public Langbiang SKU candidates.
Clean sequence
Results are displayed as OEM code -> LBG SKU for clear part-number comparison, while the private database stays out of the public page.
Verify fitment
This is a cross-reference and replacement reference workflow, not a claim of OEM supply status.
Search by part number
Enter an OEM sprocket code to find public LBG SKU candidates when a private database row is available.