JBI Flat File — Product Master (v2)
Filename: inv_mast.txt
Delivery path: <your-folder>/inv/v2/inv_mast.txt
FTP host: ftp.jbi.bike
Version: v2
Format: Tab-delimited UTF-8 text, header row in line 1, LF (\n) line terminator
Overview
The Product Master file is the slim v2 replacement for the legacy product master. It contains one row per active SKU with the core attributes you need to load products into a POS, e-commerce site, or inventory system: identity, pricing, dimensions, and the regulatory/shipping flags that drive freight and online-sales decisions.
Compared to the legacy inv_mast.txt, the v2 file trims the column set down to a stable, customer-friendly subset and uses simpler header names (brand instead of Brand_Name, uom instead of unit_of_measure, etc.).
Delivery
| Property |
Value |
| Host |
ftp.jbi.bike |
| Protocol |
FTP |
| Path |
<your-folder>/inv/v2/inv_mast.txt |
| Update schedule |
4:05 AM EST daily |
| Coverage |
Active SKUs only (status = 'active') |
Many modern browsers no longer support FTP. We recommend a dedicated FTP client such as FileZilla, Cyberduck, or WinSCP.
File Format
- Delimiter: Tab (
\t)
- Encoding: UTF-8
- Line terminator:
\n
- Header row: Yes — column names are in row 1, in the order listed below
- Quoting: None. Any double-quote (
") or apostrophe (') found in the source data is replaced with a backtick (`) before write, so each tab-separated value is safe to split on the tab character without quote-aware parsing.
Field Reference (25 columns)
Identity
| # |
Field |
Description |
| 1 |
item_id |
J&B part number (SKU) |
| 2 |
description |
Product invoice description |
| 3 |
brand |
Brand name |
| 4 |
model |
Model name |
| 5 |
upc_ean |
UPC or EAN barcode |
| 6 |
supplier_part_no |
Manufacturer's own part number |
Packaging & Pricing
| # |
Field |
Description |
| 7 |
case_qty |
Quantity in a full case lot |
| 8 |
uom |
Unit of measure |
| 9 |
price |
Dealer each-price |
| 10 |
msrp |
Manufacturer's suggested retail price |
| 11 |
map |
Minimum advertised price |
Physical Dimensions
| # |
Field |
Description |
| 12 |
weight |
Packaged weight (lbs) |
| 13 |
length |
Packaged length |
| 14 |
width |
Packaged width |
| 15 |
height |
Packaged height |
| 16 |
cube |
Packaged volume in cubic inches, rounded to 2 decimals |
Regulatory & Compliance
| # |
Field |
Description |
| 17 |
ormd |
ORM-D / Limited Quantity hazardous goods flag (Y, N) |
| 18 |
warning_label |
Prop 65 warning label ID |
| 19 |
date_created |
Date the SKU was created |
Shipping & Sales Flags
| # |
Field |
Description |
| 20 |
restricted_online |
Restricted from online sales (Y, N) |
| 21 |
dropshipable |
Drop-shippable (Y, N) |
| 22 |
nfa |
Non-Freight-Allowed (Y, N) |
| 23 |
nfas |
Freight allowable when split-shipped (Y, N) |
Purchase Limits
| # |
Field |
Description |
| 24 |
qty_restriction |
Purchase quantity limit per period |
| 25 |
qty_restriction_period |
Limit period — D = Daily, W = Weekly, M = Monthly |
Notes
- Only active SKUs are included. Discontinued or inactive items are omitted entirely; if a SKU disappears from the file, treat it as no longer offered.
- Rows are sorted ascending by
item_id.
- Empty values are emitted as empty strings — there is nothing between the surrounding tab characters.
- Values that are blank in the source database (no MAP price, no future MAP, etc.) will appear as empty fields, not literal
NULL.
Document version: 1.0 — 2026-05-23
For questions or to request FTP access, contact JBI.