Product Imports: Documentation

Import is how most catalogs enter GearDock. A spreadsheet is read, mapped to product fields, validated row by row, and held as a batch you can inspect before anything is committed.

Column Mapping

Supplier exports never share a schema, so mapping is set per import rather than fixed globally. You confirm which column carries the manufacturer, which carries the identifier, and which are descriptive. The same mapping can be reused for a file of the same shape next quarter.

Validation

Each row is validated independently. A row that fails does not stop the batch. It is recorded with the reason it failed, so a single malformed row cannot block several thousand good ones.

Common validation outcomes
Outcome	Meaning	What to do
Accepted	The row parsed and carries a usable identifier.	Proceed to matching.
Flagged	The row was read but something looks wrong, such as a malformed identifier or a missing manufacturer.	Review; often fixable at the source file.
Rejected	The row could not be interpreted as a product.	Check for merged cells, shifted columns, or header rows inside the data.

Read the Failures Before the Successes

Rejected rows cluster around a single upstream cause far more often than they are independently broken. Fixing the cause in the source file and re-importing is usually faster than correcting rows one at a time.

Batches

Every import is a batch with its own record: what was uploaded, when, by whom, how many rows were accepted, flagged, and rejected. Batches are scoped to your organization, and a batch from one organization is never visible or actionable from another.

No Patient Information

Import files must not contain patient records, clinical notes, or service reports carrying patient data. GearDock is a product catalog system and is not intended for protected health information.