ConEquip Standardized Product Schema (SPS)

Inventory Upload Guide

Overview

This document explains how to provide daily inventory data to ConEquip using one of two supported upload templates. Vendors may choose the format that best fits their internal systems.

Note: This inventory upload process does not replace your existing DriverWeb or vendor portal integrations; they will continue working exactly as they do today. However, using this process can boost and enhance your DriverWeb results.

The SPS upload is a new, additional data channel that supports:

  • Showing and selling your products directly on our website
  • Providing visibility into our internal CRM for sales reps while building quotes
  • Helping our team identify which vendors can fulfill a customer need the fastest and at the best value

Participation in this program gives our reps significantly more visibility into your product offering. Vendors who consistently provide structured daily data naturally appear more often as top fulfillment options inside our sales tools. Vendors who do not participate may sometimes be overlooked simply because the data is missing or outdated.

Critical: You must send a FULL daily inventory snapshot containing ALL SKUs, for ALL conditions, from ALL locations. Missing SKUs are treated as zero inventory. Changes-only or delta files are not accepted.

Daily Submission Requirements

  • Submit exactly ONE inventory file per day
  • Each file must be a FULL daily snapshot of your inventory
  • Include ALL SKUs, for ALL product conditions, from ALL locations
  • Missing SKUs are treated as zero inventory
  • Changes-only or delta files are NOT accepted

Template Formats

Flat Template (CSV or XLSX)

One spreadsheet where each row contains the SKU, condition, location, quantity, and ConEquip price. Best for simple workflows and smaller inventories.

Use this if: You manage inventory in Excel, export one combined list, or don't use internal IDs.

Required Columns:

Column Description
SKU Your actual part number (stable, unique)
Product Condition Must use approved ConEquip SPS values
Location Name Location nickname (e.g., "Birmingham Warehouse")
Location Street Street address
Location City City name
Location State/Province State or province
Location Zip/Postal Code ZIP or postal code
Location Country Country name
Quantity On Hand Available quantity at this location for this variant
ConEquip Price (USD) Your cost to ConEquip for this SKU/condition/location

If a product appears in multiple conditions or locations, include one row per combination.

Relational Template (XLSX only)

Multiple linked sheets (Products, Product Variants, Variant Stocks, Locations, etc.), similar to how a database stores data. Best for automated exports and large catalogs.

Use this if: You use an ERP/CRM with unique IDs, export structured tables, or manage multiple warehouses at scale.

Required Sheets:

Products

Unique Identifier*, SKU*

Product Variants

Unique Identifier*, Product Identifier*, Product Condition*

Variant Stocks

Unique Identifier*, Product Variant Identifier*, Location Identifier*, Qty*, Price*

Locations

Unique Identifier*, Street*, City*, State*, Zip*, Country*

Optional Sheets:

Categories

Unique Identifier*, Category Name*

Equipment Makes

Unique Identifier*, Make Name*

Equipment Models

Unique Identifier*, Make ID*, Model Name*

Approved Product Condition Values

The Product Condition field must match one of these approved values:

New Genuine OEM contracted another manufacturer
New OEM New part from OEM dealer
New OEM Surplus New OEM part for surplus distribution
New Replacement New aftermarket, meets OEM specs
New Takeoff New OEM part from unused component
Reconditioned Used, cleaned, worn parts replaced
Reman Exchanged Remanufactured, requires core
Reman Outright Remanufactured, no core required
Resealed Only seals replaced

Need Help?

We WANT to work with you! If you have questions, run into issues, or need help getting set up, our team is here for you.

Development & Technical Support

Robert Lawrence, CIO - [email protected]

Charles May, Dev Lead - [email protected]

Vendor Relations

Ben Krentz, CBDO - [email protected]

Kevin Zilliox, Product Integration - [email protected]