Catalog Software for Medical Equipment Sellers
Ask About Any Medical Device. Publish What You Can Prove.
GearDock AI answers questions about medical equipment and writes your catalog content, with the source beside every fact. Unsupported statements are left out. A person approves the result before anything is released or exported.
Private beta. Workspaces are configured with your team; there is no open self-service signup.
Write a short product description for the Acme Medical AM-4200 infusion pump.
The AM-4200 is a volumetric infusion pump for adult and paediatric use. Manufacturer verified
It delivers between 0.1 and 999 mL/h across a 50 mL to 1,000 mL container range. Manufacturer verified
The device holds 510(k) clearance under product code FRN. Regulator verified
It is designed for wards where pumps move between beds during a shift. Wording only
2 statements withheld
Battery runtime and weight were drafted but no admitted source states them.
Grounded coverage
100%
Provenance accuracy
100%
Sources
4
The GearDock AI answer view, using fictional product data. Drafts still require human review, release, and destination controls.
What You Get
Four Things, Available Now
Each one is a job you are trying to finish, with the part of the system that does it named underneath. Anything not on this list is on the roadmap, said plainly.
- The flagship
GearDock AI
Ask a question or request a deliverable. Every fact comes back with its source attached.
Read more - How the writing is governed
Evidence-based content
Every statement is checked against the document behind it, and the passage sits beside the claim.
Read more - Bring the catalog in
Catalog management
Import from your store or spreadsheet, find the gaps, complete what your documents support.
Read more - Where the content goes
Integrations
16 provider profiles. Every destination receives drafts, never live listings.
Read more
- 77
- Manufacturers
- 4
- Evidence tiers
- 9
- Claim classes
- 16
- Destinations
Recognized by name, alias, or the identifier shape they use.
Your reviewed documents outrank anything found on the web.
A description is not checked the way a regulatory status is.
Every one of them receives drafts, never live listings.
The Real Problem
Catalog Work Breaks Long before Anyone Writes a Description.
The facts you need are usually sitting in a manufacturer PDF. Someone opens it, finds the figure, retypes it into a field, and the trail disappears. Do that four thousand times, across a few staff changes, and you have a catalog nobody can vouch for.
You Cannot Tell Which Product a Row Is
One model name often covers several configurations. A well-written description attached to the wrong one is worse than an empty field.
The Facts Are Locked Inside PDFs
Spec sheets and manuals hold the numbers you need. Nothing connects the page a number is printed on to the field it ends up in.
A Guess Looks Exactly Like a Fact
In a spreadsheet, a verified value, a guessed value, and a stale value are identical. The difference only shows up when a buyer challenges it.
Every System Holds a Different Copy
The PIM, the storefront, the CMS, and three local sheets each carry their own version, and none of them records why it changed.
What GearDock Does
It Builds the Product Record, Then Shows You Its Work
GearDock finds the passages in your documents that support each value, turns them into structured facts, and drafts the catalog content from those facts. The draft, the evidence behind it, the claim check, the review state, and the release control all stay on one screen, so a reviewer can check a statement in seconds instead of hunting for the source.
Ask GearDock answers questions about your own catalog in plain language, such as which products still have no supporting document or what changed on a record last month. It cites the records it drew on, and it cannot change them.
Content Plan
Product Detail Page
Acme Medical AM-4200 Volumetric Infusion Pump
The AM-4200 supports a documented flow range of 0.1–999 mL/h. Its listed weight is 2.4 kg. Battery runtime remains unverified and is excluded from this draft.
Ask GearDock
“Which source supports the flow range?”
AM-4200 datasheet, page 4. Open the cited passage to verify it.
An illustration of the workspace using fictional product data. It shows implemented workflow states and no customer information.
How It Works
Eight Stages, from a Spreadsheet Row to a Published Product
Each stage takes what the one before it produced. The system does the reading, matching, and drafting. People decide the identity questions, the approval, the release, and where content is allowed to go.
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.
GearDock and Your PIM
A PIM Manages Data You Already Have. GearDock Works Out What the Data Should Say.
PIM systems are good at storing, organizing, and distributing product records. They assume someone has already established the facts. GearDock does that earlier job: identifying the product, finding the evidence, building the facts, and getting them approved. Most teams keep their PIM and feed it from GearDock.
- Starts with
- Product data someone has already established
- Spreadsheets, part numbers, and manufacturer PDFs
- Does the work of
- Storing, organizing, enriching, and distributing records
- Identifying the product, finding the facts, drafting and approving the content
- Missing data
- Shows an empty field
- Shows what is missing, what conflicts, and what no source supports
- Together
- Stays the system that manages approved product data
- Prepares approved, source-backed records to send into it
Evidence and Review
A Draft Can Read Well and Still Be Wrong
This is the failure mode that matters. GearDock keeps the source, the claim check, the reviewer's decision, the release state, and the export record attached to the same product. When a value is missing or two documents disagree, it says so instead of writing around it.
- Generated content stays a draft until a person records a decision.
- Approval and release are two separate decisions, and export re-checks release state as it runs.
- Every factual statement keeps a link to the document passage behind it.
- Missing values, conflicting sources, and unsupported claims stay visible.
- Versions and governed actions are recorded, and no role can edit that record later.
What your team does
- Upload
- Review
- Approve
- Export
runs on
What the platform maintains
- Evidence
- Matching
- Confidence
- Claim controls
- Versioning
- Audit
- Lineage
- Organization isolation
One Connected System
One Record That Carries Everything Forward
Import, matching, evidence, drafting, review, release, and distribution are not separate tools you stitch together. Each one reads the state the previous one left on the same product record, which is why nothing is lost at a handover.
Bring data in
- Product import
- Document intelligence
- Product matching
Make it complete
- Content completion
- Governed generation
- Claim Firewall
Prove and distribute
- Review and release
- Digital thread
- Integrations
One governed product record underneath. Evidence attached at intake remains available during review, release, distribution, and later correction.
Product Import
Map your spreadsheet columns and check every row on its own.
Product Matching
Work out which real product a row is, before anything is written.
Document Intelligence
Turn manuals and spec sheets into passages you can cite.
Content Completion
Separate supported facts from gaps, conflicts, and guesses.
Claim Firewall
Compare each drafted statement against the evidence behind it.
Review and Release
Keep drafting, approval, release, and export as separate steps.
Digital Thread
Every source, version, decision, and delivery in one history.
Exports and Integrations
Send approved content out as files or to a connected system.
What Changes
What Teams Actually Get Out of It
No percentages appear here, because none have been measured with a customer. These are changes in how the work runs.
- Products that already have documents can be completed and published first, instead of the whole catalog waiting on its worst records.
- The gap report names the documents worth chasing, so research stops being open-ended.
- Attributes come out structured, so filters and comparison tables work without a second cleanup pass.
- Review runs faster because the evidence sits beside the claim rather than in a folder somewhere.
- A challenged claim can be answered from the product's own history instead of reconstructed from email.
- A new storefront or marketplace reuses the approved record rather than starting another copy of it.
Who It Is For
Five Starting Problems, One Catalog
GearDock suits teams whose bottleneck is no longer writing a single description. It is keeping identity, evidence, decisions, and distribution consistent across a catalog that keeps growing.
Where catalog work gets stuck
You list thousands of products, but most records stop at manufacturer, model number, and price.
How GearDock changes the work
Import the sheet you already keep, match the rows to real products, attach the documents you hold, and complete the fields those documents support.
What you end up with
Product pages a buyer can trust, without turning catalog cleanup into a year-long replatforming project.
Product import and matching
Where catalog work gets stuck
Manufacturer facts, unit condition, service history, and sales claims all end up in the same description field.
How GearDock changes the work
Keep the facts that belong to the model separate from the condition of the individual unit, and send unsupported claims to review.
What you end up with
Model facts you can reuse across every unit, and condition language that stands up when a buyer asks.
Evidence and governed writing
Where catalog work gets stuck
The same completion, formatting, and publishing work repeats for every SKU, and each destination drifts from the others.
How GearDock changes the work
Work from structured facts and one approved record, then send only the version that passed review to each destination.
What you end up with
Consistent attributes across the catalog and far fewer unrecorded edits made at the storefront.
Completion, review, and export
Where catalog work gets stuck
You can read the published sentence, but not the source behind it, the earlier versions, or who decided it could go out.
How GearDock changes the work
Read each claim beside its evidence, record why you approved or rejected it, and keep approval separate from release.
What you end up with
A challenge answered from the product's own history rather than reconstructed from email.
Claim Firewall and digital thread
Where catalog work gets stuck
Brands, regions, PIMs, storefronts, and shared drives each hold a different version of the same catalog.
How GearDock changes the work
Connect those systems through one workspace with approved mappings, retries, checkpoints, and a record of every delivery.
What you end up with
One way of working across systems, without any connector getting authority over what is true.
Integrations and tenant scope
Your Data Stays Yours
Every Organization Works Inside Its Own Boundary
Products, imports, documents, drafts, reviews, releases, exports, and audit records all belong to exactly one organization. Inside that workspace, roles decide what each person can see and do.
- No customer can see another organization's records.
- A connected system only ever acts inside the organization that authorized it.
- Governed decisions and changes leave an audit record behind them.
- GearDock's own internal reference library is a separate plane customers cannot reach.
That describes how the product is built. It is not a claim of SOC 2, HIPAA, or any other certification.
Organization a Workspace
- Products and documents
- Reviews and releases
- Integration activity
Organization B Workspace
- Separate records
- Separate members
- Separate connections
Founder / Internal Knowledge Plane
Separate capabilities and global knowledge resources do not become customer-visible or enter a customer workspace.
Integrations
Connect Your Systems Without Handing Them the Last Word
GearDock ships 16 provider profiles across PIM, commerce, CMS, cloud files, and SFTP. Each one states how far it has been proven. Content arrives at the destination as a draft, and a person there decides when it goes live.
Your systems
- PIM / ERP
- Commerce
- CMS
- Files / APIs
Connection layer
- Connect
- Map
- Sync
- Review
Tenant-scoped processing
Authorization, capability checks, rate governance, checkpoints, retries, idempotency, conflicts, and append-only evidence.
Controlled outcomes
- Governed records
- Released packages
- Draft destinations
- Inbound synchronization
- Outbound synchronization
- Inbound webhooks
- Outbound webhooks
- Public REST API
- Background execution
- Retries and rate limits
- Idempotency
What GearDock Does Not Do
Built for Careful Work. Not Sold as a Certification.
GearDock links statements to sources, requires human decisions, separates release from approval, keeps organizations apart, and records what happened. It does not guarantee that a manufacturer document is correct, and it holds no HIPAA, SOC 2, or FDA status. It is also not a system for patient data.
What happens when something turns out to be wrong
A spec sheet can contain an error, and reading a dense table can go wrong. Being able to trace a claim means you can find every product that relied on that document, see which versions and decisions were affected, and correct them as one recorded change rather than searching the catalog by hand.
Read Before You Decide
Software Worth Buying Explains Itself First
Start with a full workflow guide, use the documentation for exactly how each stage behaves, and read the blog for the catalog decisions that come up along the way.
Guide
From Import to Your First Exported Product
The complete path for one product: import, match, evidence, completion, generation, review, approval, release, and export.
Article
Why an AI Answer With Sources Can Still Be Wrong
A source list tells you a model consulted something. It does not tell you the sentence above it is in there. That gap has a shape, and it can be closed.
Article
Not Every Source Can Prove Every Claim
A manufacturer's brochure and its instructions for use are both official documents. They are not interchangeable, and treating them as one source type is how overreach gets into a catalog.
Common Questions
What GearDock Is, and What It Deliberately Is Not
Direct answers about what the product covers, what the AI is allowed to do, and the limits we hold to. Questions about the process itself are answered on the how-it-works page.
What is GearDock?
GearDock is catalog software for medical equipment sellers. You give it the product spreadsheets and manufacturer documents you already have. It works out which real product each row refers to, pulls the supporting facts out of those documents, drafts the catalog content, and sends it to a person for approval before anything is released or exported.
Who is GearDock for?
Teams responsible for a large medical device catalog: equipment sellers and distributors, refurbished and demo dealers, catalog and eCommerce teams, compliance reviewers, and enterprise product operations groups. The common factor is a catalog big enough that writing one description at a time has stopped working.
How is GearDock different from a PIM?
A PIM stores, organizes, and distributes product data that someone has already established. GearDock does the job before that one: deciding which product you actually have, finding the facts in your documents, showing what is missing or contradictory, and getting the content approved. Many teams keep their PIM and send GearDock output into it.
What does the AI actually do here?
It writes prose from facts that already have a source. The first draft is built directly from the evidence attached to the product, so content can be produced even when no external AI provider is available. When a provider is enabled it only rewrites that prose more readably, and its output is rejected if it drops a citation or introduces a number that does not appear in the evidence.
Does GearDock replace human review?
No, and it is built specifically not to. Generated content stays a draft until a person records a decision. Approval and release are two separate decisions, and an export re-checks the release state at the moment it runs. There is no setting that lets content reach a storefront without someone approving it.
What happens when information is missing?
The field stays empty and the gap is reported. GearDock keeps three states apart: values a source supports, values where two sources disagree, and values nothing available supports. A missing specification is shown as missing, which is exactly what tells you which document to go and find.
Can GearDock read my spreadsheets?
Yes. CSV and XLSX files are imported with column mapping, and every row is checked on its own, so a handful of bad rows cannot fail the batch. Large imports run in the background and resume rather than starting over.
Can GearDock publish to Shopify?
It can send released content to a connected Shopify store as draft products. It does not make them live. Someone on your team reviews the draft in Shopify and publishes it there, so a connector never gets the last word on what a customer sees.
Can other organizations see my products or documents?
No. Every product, document, draft, decision, and audit record belongs to exactly one organization, and content cannot cite another organization's documents as evidence. GearDock also keeps its own internal reference library on a separate plane that customer users cannot browse, search, or export.
Private Beta
See GearDock Run on Your Own Products
Private beta access suits teams with a few hundred products or more, some manufacturer documents, and someone who can judge whether the output is accurate. Tell us your catalog size and how you publish today, and we will reply about a workspace.