Bring the Catalog In
Start From the Store You Already Run.
Pull your products in from the storefront, spreadsheet, or PIM you already keep. GearDock works out what each record actually is, shows you what is missing, and gives you back a version somebody approved.
| Attribute | Value | State | Evidence |
|---|---|---|---|
| Manufacturer | Acme Medical | Sourced | Datasheet p.1 |
| Model | AM-4200 | Sourced | Datasheet p.1 |
| Flow rate range | 0.1–999 mL/h | Sourced | Datasheet p.3 |
| Regulatory status | 510(k) · FRN | Sourced | FDA record |
| Battery runtime | Not stated | Gap | No source |
| Weight | 2.4 kg / 2.6 kg | Conflict | 2 sources differ |
The Problem
Catalog Work Breaks Long Before Anyone Writes a Description
Most catalog projects stall before the writing. Teams cannot say with confidence which product a row refers to, which spreadsheet is current, or which fields were checked against a document rather than typed from memory.
- One model name covers several configurations, and the sheet does not say which one you stock.
- The whole catalog waits on its worst records, so nothing ships.
- Attribute gaps are invisible until a filter on the storefront returns nothing.
- Research is open-ended, because nobody knows which documents are actually worth chasing.
One Record
From a Spreadsheet Row to a Product Somebody Approved
The same record carries forward through every stage. Nothing is re-keyed, and every stage can see what the previous one decided and why.
Intake
Establish the product
- 01System work
Import Product Data
Bring in a spreadsheet, selected cloud file, PIM profile, or connected catalog.
- 02Human control
Establish Product Identity
Resolve each row with identifiers. Ambiguous or conflicting identity waits for a person.
Evidence
Make support visible
- 03System work
Connect Trusted Evidence
Link manuals and spec sheets to products so facts can cite exact passages.
- 04System work
Build Structured Product Facts
Surface missing, conflicting, weakly supported, and unavailable information.
Governance
Draft and decide
- 05System work
Generate Governed Content
Draft website-ready copy from supported facts, then run the Claim Firewall.
- 06Human control
Validate Claims and Resolve Issues
Run integrity and Claim Firewall checks, then resolve blocked gaps or conflicts before review.
Distribution
Release with control
- 07Human control
Review, Approve, and Release
Release approved content through a separate, recorded governance gate.
- 08System work
Distribute and Monitor
Send released content to an authorized destination and retain delivery evidence.
How It Works
What Catalog Management Actually Does
Each step depends on the one before it. The label on the right names the part of the system that does the work.
Bring products in from where they already are
Connect a storefront and discover its products, or map the columns of the spreadsheet you already keep. Each row is checked on its own rather than as a batch, so one malformed record does not stop the import.
Import and discoveryWork out which real product each row is
Before anything is written, each record is resolved to an actual manufacturer, family, model, and variant. This happens first because a well-written description attached to the wrong configuration is worse than an empty field.
Product matchingAttach the documents you hold
Manuals, spec sheets, IFUs, and service manuals become searchable, citable passages bound to the products they describe. Uploaded documents become evidence only after they have been read and their fit assessed.
Document intelligenceSee what is supported, missing, or contradicted
The completion view separates the fields your documents support from the gaps and the conflicts. The gap report names the documents worth chasing, which is what turns research from open-ended into a list.
Content completionComplete the products that are ready
Products that already have documents can be completed and published first, instead of the whole catalog waiting on its worst records. Attributes come out structured, so filters and comparison tables work without a second cleanup pass.
Governed generationApprove, release, and export as separate decisions
Approving content and releasing it are not the same act, and neither is exporting it. Keeping them apart is what lets a reviewer say “this is correct” without also saying “publish this now”.
Review and release
Why You Can Rely on It
The Mechanisms Behind the Claim
Statements about how the system is built, not adjectives about how good it is.
Approval is not release, and release is not export
Three separate decisions with three separate permissions. Content marked approved is not thereby publishable, and nothing leaves the system on approval alone.
Every organization works inside its own boundary
Products, documents, evidence, and history are scoped to your organization. Nothing is pooled across customers, and no other tenant's material can become evidence for your catalog.
Products are archived, never quietly deleted
A product keeps its sources, versions, decisions, and deliveries. Deleting it would destroy the record needed to answer a challenge, so removal archives it instead.
The history is append-only
Audit and governance events are not editable after the fact, including by administrators. A record that can be tidied up is not a record.
Boundaries
What It Does Not Do
Stated here rather than discovered later.
- GearDock is not a PIM replacement. A PIM manages data you already have; this works out what the data should say. Many teams keep both and send approved output into the PIM.
- Catalog capacity in the private beta is set per workspace during onboarding rather than sold as a number on a page.
- It does not publish anything live on its own. Every destination that can receive content receives it in an unpublished or draft state.
Common Questions
Catalog Management, Answered
Do I have to replace my PIM or my storefront?
No. GearDock sits before them. It decides which product you have and what the record should say, then hands the approved version to whatever system distributes it. Teams commonly keep their PIM and send GearDock output into it.
What if my spreadsheet is a mess?
That is the normal starting condition and the reason product matching runs before anything else. Each row is checked individually, unmatched rows are surfaced rather than guessed at, and the products that do resolve can proceed without waiting for the ones that do not.
How much of my catalog can I work on at once?
Bulk import, bulk completion, and bulk generation all exist. Actual capacity for a private beta workspace is agreed during onboarding, because it depends on catalog size, document volume, and how much research each product needs.
Go Deeper
Related Reading
Private Beta
Start With the Part of the Catalog That Already Has Documents
You do not need a clean spreadsheet to begin. Send us a sample of what you actually keep, and we will show you which products could be completed first.
Coverage
It Already Knows This Industry's Names
Model families matter and variants within them matter more. A console, its software tier, and its transducers are different things, and blurring a family into a model is how the wrong specification ends up on the right product.
- GE HealthCare
- Philips
- Siemens Healthineers
- Dräger
- Medtronic
- Mindray
- Masimo
- ResMed
- Olympus
- Stryker
- ZOLL Medical
- Baxter
- + 65 more
These are manufacturers whose product names, families, and identifier shapes GearDock resolves. They are not customers, partners, or endorsements, and no relationship with any of them is implied.