Capability
Released Content Leaves Through One Gate, and the Gate Checks Again
Package released content as files or publish it to a connected destination, with release state re-checked at the moment the export runs.
The Question This Answers
How does released content actually reach my storefront?
Export is the last stage, and it is deliberately suspicious of everything that came before it.
Re-Checking at Execution
Release state is verified at the moment an export runs, not trusted from when the export was requested. Content can be withdrawn after approval, and re-checking at execution means a queued or retried job cannot carry out a decision that has since been reversed.
Destinations
| Destination | Status | What it does |
|---|---|---|
| Shopify | Proven | OAuth store connection, paginated product discovery, and creating or updating products as DRAFT. |
| File export | Proven | Packages released content for download, for systems without a direct connector. |
| Other commerce, CMS, PIM, file, and API profiles | Implemented with varied proof | Profiles are executable, but proof level, customer configuration, publication boundary, and public activation must be evaluated separately. |
Shopify Publishing Creates Drafts
What Is Recorded
- Which version of which product was exported.
- Where it was sent, and when.
- Who initiated it.
- The result, including failures and retries.
Boundaries
What This Does Not Do
Stated plainly, because knowing the edges of a capability is more useful than another list of benefits.
- Content that is approved but not released cannot be exported, under any configuration.
- GearDock does not set Shopify products live.
- Provider profiles have different proof levels; implementation does not imply a publicly activated customer connection.
- It does not reconcile changes made directly in the destination system back into GearDock.
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 if I edit the product in Shopify afterwards?
Those edits live in Shopify. GearDock records what it sent and when; it does not read your storefront changes back into the product record.
Can I export to a platform you do not support?
File export covers many cases. GearDock also has provider profiles across PIM, commerce, CMS, cloud-file, API, webhook, and SFTP workflows, but every direct connection requires a supported profile, approved customer configuration, and qualification before activation.
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.