Capability
Bring Your Spreadsheet in Without Adopting a New Schema First
Column mapping for the file shapes you already receive, per-row validation, batch inspection before anything is committed, and exceptions grouped by cause.
The Question This Answers
How do I get thousands of products in without a data project first?
Supplier exports never share a schema. A system that requires one before you can start has moved the hard part rather than solved it, so GearDock maps columns per import instead.
Column Mapping
You confirm which column carries the manufacturer, which carries the identifier, and which are descriptive. The mapping is saved for that file shape, so the same supplier's quarterly export becomes a repeatable import rather than a fresh decision each time.
Row-Level Validation
Each row is validated independently. A malformed row is recorded with the reason it failed and does not stop the batch, so one bad row cannot block several thousand good ones.
| Outcome | Meaning | Typical cause |
|---|---|---|
| Accepted | Read successfully, with a usable identifier. | None |
| Flagged | Parsed, but something looks wrong. | Malformed identifier, missing manufacturer, suspicious formatting. |
| Rejected | Could not be interpreted as a product. | Merged cells, shifted columns, a header row inside the data. |
Exceptions Grouped by Cause
Import failures cluster. A supplier file with a systematic formatting quirk produces many failures of the same shape, so exceptions are grouped by their underlying cause rather than listed as hundreds of individual problems. Fixing the cause in the source file and re-importing is usually faster than correcting rows one at a time, and it improves the file you will use again next quarter.
No Patient Information
Boundaries
What This Does Not Do
Stated plainly, because knowing the edges of a capability is more useful than another list of benefits.
- It does not clean your source data for you. It tells you exactly what is wrong so you can fix it at the source.
- It does not guess at ambiguous columns. Mapping is confirmed by a person.
- It does not write anything to your catalog until you have reviewed the batch.
- It does not accept protected health information.
In Sequence
What Comes Before and After
Each capability hands something specific to the next. Following the chain is usually more useful than reading them in isolation.
Questions
Common Questions
What file formats are supported?
Spreadsheet files as exported by the systems most sellers already use. If your export has an unusual shape, mapping handles it without requiring you to reformat first.
Can I re-import the same file after fixing it?
Yes, and that is usually the fastest path. Correcting the cause in the source file and re-importing beats fixing rows individually, and it improves the file for next time.
Is my import visible to other organizations?
No. Import batches, like everything else in GearDock, are scoped to a single organization and are never visible or actionable from another.
Private Beta
See This Working on Your Catalog
Capability pages describe the mechanism. A working session on your own products shows you how it behaves with your data, which is a more useful basis for a decision.