Product Update: Column Mapping, Import History and Per-Client API Keys

Column mapping for spreadsheet imports

Inventory exports never share a schema. Instead of asking you to reshape your file, the importer now reads your headers and lets you map them onto our fields, with a row preview before anything is written.

Your mapping is remembered per client, so recurring uploads from the same system are a two-click job after the first time.

Import history

Every upload and every third-party push now writes to import history: source, filename, row count, successes, failures, and the per-row reason for each failure. When four vehicles out of two hundred do not appear, you can see exactly why.

Per-client API keys for the extension

The Chrome extension previously rode on your login session. It now authenticates with a scoped API key generated in posting settings.

This matters for a few reasons:

• The key is stored as a hash. Nobody, including us, can read it back after generation.
• It is scoped to one client and to the extension endpoints only.
• Revoking it is instant and does not touch anyone's login.

Generate yours under settings in the dashboard. The previous session-based flow is deprecated and will stop working next month.

Package limits enforced at the database

Vehicle ceilings and daily posting caps are now enforced inside the database itself rather than only in the interface, so an import can no longer overshoot your plan.