The Jet.com order IDs in FarApp are not the same order IDs that Jet.com references. FarApp uses Jet.com's longer merchant order ID values instead of the more readable Jet.com reference order IDs. The reason FarApp does this is because Jet's documentation states the following regarding their reference order IDs:
Jet's human readable order ID number that may have a small chance of collision overtime.
However the documentation for the merchant order ID states:
Jet's unique ID for a given merchant order.
FarApp must guarantee uniqueness of all order IDs for a given connector. Otherwise, collisions will prevent an order from importing. However, FarApp does record the readable reference order ID in its transaction ID field. If you'd like, you can map this FarApp field to a field of your choosing in your backend system (e.g. NetSuite). Please note that it cannot be one of the two fields described here since those are used by FarApp in a specific way: https://support.farapp.com/hc/en-us/articles/216635428-Order-Processing-Required-Fields.