Your product catalog is the center of everything. Hover any node to see how it connects.
The complete list of everything you sell. Comes from your ERP, product database, or master spreadsheet.
| Field | Purpose | Status |
|---|---|---|
| BaseItemCode KEY | Product SKU — the master key that links all files | Required |
| LongDesc | Primary catalog title shown in the product grid | Required |
| ShortDesc | Optional shorter product name; falls back to LongDesc if blank | Optional |
| TradeNameCode | Brand identifier (e.g., ELK) | Required |
| CategoryCodes | Product category (e.g., FLAMP) | Required |
| CollectionCodes | Product collection; required when strict catalog validation is enabled (default for most orgs) | Required* |
| NetPrice | Base price used for all price-level calculations | Required |
| ImageFileName | Product image filename | Required |
| OptionSet1..N | Links to option groups for product variations | Optional |
| PromotionPrice | Promotional pricing override (header is case-insensitive) | Required |
BaseItemCode, LongDesc, TradeNameCode, CollectionCodes, CategoryCodes, ImageFileName, and PromotionPrice are all required columns. NetPrice is essential for price-level calculations. CollectionCodes is required when strict catalog validation is active (default for most organizations).LongDesc = primary catalog title shown in the grid. ShortDesc = optional shorter line; if blank, LongDesc is used. ProductStory (in stories.csv) = extended marketing description shown in the detail view, tear sheets, and emails. Two different files, three different fields.Who can buy from you and where they want products shipped. From your CRM or accounting system.
| Field | Purpose | Status |
|---|---|---|
| BillToCode | Customer account number | Required |
| BillToName | Customer company name | Required |
| BillToAddress1 | Billing street address | Required |
| BillToCity | Billing city | Required |
| BillToState | Billing state | Required |
| BillToPostCode | Billing postal code | Required |
| DefaultPriceCode | Sets customer’s pricing level — drives automatic price selection when a rep selects this customer | Required |
| TerritoryCodes | Assigns customer to sales rep(s) — controls which customers appear on each rep’s device | Required |
| ShipToCode | Shipping location ID (one row per location) | Required |
| ShipToAddress1 | Shipping street address (required per location) | Required |
| ShipToCity | Shipping city (required per location) | Required |
| ShipToState | Shipping state (required per location) | Required |
| ShipToPostCode | Shipping postal code (required per location) | Required |
| Field | Purpose | Status |
|---|---|---|
| BaseItemCode KEY | Must match products.csv SKU | Required |
| QtyAvailable | Quantity available to promise for immediate shipment | Recommended |
| QtyOnHand | Physical inventory count in the warehouse | Optional |
| QtyReserved | Quantity committed to unshipped sales orders | Optional |
| NextReceiptDate | Date of next product receipt at your warehouse | Optional |
| NextReceiptQty | Quantity of next product receipt at your warehouse | Optional |
BaseItemCode is the only column that causes a fatal import error if missing. QtyAvailable is strongly recommended — without it, inventory data won’t be meaningful to reps in the field.Extended product descriptions, specs, care instructions, and marketing copy. Displayed in eCat’s product detail view, tear sheets, PDF catalogs, and product emails.
| Field | Purpose | Status |
|---|---|---|
| BaseItemCode KEY | Must match products.csv SKU | Required |
| ProductStory | Extended “product romance” description (header is case-insensitive) | Required |
These files enhance eCat but aren’t required to go live. Add them as your setup matures.
Summarized sales history for in-app customer reporting. One row per customer/product combination, linked via BillToCode and BaseItemCode KEY. Powers the Invoices/Favorites and On Order views inside eCat, letting reps quickly see what a customer has purchased and what’s on order.
Product variations (colors, finishes, sizes). Two files work together:
BaseItemCode is the master key connecting products to inventory, stories, options, and orders.
It walks you through logging in, navigating the interface, and where to find key settings — the right starting point before your first import.
These guides cover the day-to-day admin tasks that go hand-in-hand with managing your data.