Coming Soon · in Qualification
More Destinations, Once Each One Is Genuinely Proven
GearDock has sixteen provider profiles, and they are not all proven to the same standard. This roadmap item covers testing more of them against real provider instances and publishing the resulting proof level.
Available Today
What You Can Use Instead, Now
This capability is not released. Here is what already covers the same ground.
Sixteen provider profiles already exist across commerce, PIM, CMS, cloud files, and SFTP, and each one publishes its own proof level and publication boundary. Three routes need no bespoke connector at all: a controlled file export, an SFTP drop, and the public REST API with inbound and outbound webhooks.
When It Ships
What This Will Do
Stated as behavior rather than as benefit, so it can be checked against the release when it happens.
- Move protocol-tested providers to real-instance proof, one at a time.
- Add commerce and content destinations customers actually ask for.
- Extend outbound support where it is currently create-only or read-only.
- Publish each provider's proof level as it changes, upward or downward.
The Honest Reason
Why It Is Not Out Yet
Qualification takes a real instance of the vendor's software, a real credential, and a full round trip. Listing a provider as supported on the strength of its documentation is how integrations that fail in week two get sold, so the proof level is stated per provider and only moves when the round trip has genuinely run.
Common Questions
More Integrations, Answered
Which integrations can I actually use in the private beta?
Connections are configured with you during onboarding against your own credentials, and which ones make sense depends on your systems and each provider's proof level. Shopify is proven against a live development store; WordPress, WooCommerce, and Magento are proven against real local instances. All of them write drafts only.
Can you build a connector for my system?
Sometimes it is not needed. A reviewed generic profile can often support a system with a stable paged REST contract. A new provider profile requires us to review its contract, authentication, and endpoints.
Also on the Roadmap
The REST of What Is Coming
- Review WorkflowsStructured review, approval, and release workflows for growing catalog teams.
- Compliance CenterA focused workspace for regulatory evidence, policy readiness, and compliance operations.
- Advanced Quality ControlsDeeper integrity, reconciliation, and catalog-quality inspection tools.
- PortfolioFleet-level product oversight, risk signals, and operational intelligence.
- Teams and RolesOrganization administration, user access, and collaborative operating workflows.
Private Beta
Waiting on More Integrations?
Tell us what it is blocking. Which capability customers are actually held up by genuinely affects the order the work is done in.