Platform Integrations for Detection-First Inventory Visibility
GNIZDO is a detection-first inventory evidence layer for connected sales channels. It surfaces catalog trust, connection state, sync execution, freshness evidence, and per-channel stock, price, and listing changes. It observes each channel independently and does not act as a synchronization engine: it never automatically pushes inventory between platforms.
Supported: WooCommerce (catalog reads plus explicit, capability-gated per-item writes). Beta: Etsy (read-only, OAuth-only) and Shopify (read-only, currently in rollout). Planned: eBay.
Best next step
Create account See risky SKUs, channel state, and change evidence in GNIZDO. Security Review how API permissions and platform access are handled. FAQ Check supported platforms, data pulled, and detection-first limits.How GNIZDO Detection-First Integrations Work
Most multichannel inventory tools attempt real-time synchronization—pushing stock updates from one platform to all others whenever something changes. This approach breaks silently when API calls fail, networks timeout, or rate limits kick in.
GNIZDO takes a detection-first approach. We assume drift will happen and focus on catching it early:
- Independent channel catalogs — Each supported connected store is read as its own channel, with its own catalog evidence and sync history
- Independent channel evidence — Catalog trust, connection state, and sync execution remain separate, with freshness evidence showing when confirmed catalog data may no longer be trusted
- Per-channel change evidence — Stock drops, price changes, and listing-state changes between observations stay visible for review, including oversell-risk signals
Instead of promising perfect updates, we make drift visible so you can address it before customers are affected.
Cross-channel identity: candidates first, your confirmation decides
Cross-channel item comparisons require listings to have confirmed shared identity. A matching SKU, title, or external product ID alone does not prove two listings are the same item. GNIZDO can surface likely candidates by deterministic exact SKU or title match, but only explicit user confirmation establishes shared identity. After confirmation, GNIZDO keeps that product's channel evidence together so each channel's reported state is visible side by side. Candidate discovery is not automatic matching or an existing mapped-product aggregate view, and confirmed identity does not produce an automatic mismatch verdict on its own.
Supported: WooCommerce
Current surfaces: catalog reads, independent catalog-trust/connection/sync evidence, applicable detections, per-channel generation changes, confirmed generations, and freshness/change evidence. Write capability when a channel allows it.
The WooCommerce integration connects a store as an independent channel and reads its catalog. When that channel has write capability, an operator can send an explicit, capability-gated per-item stock or price update. GNIZDO does not automatically synchronize or remediate catalog values.
WooCommerce Catalog Reads and Explicit Writes
GNIZDO builds a trusted local snapshot of what the connected WooCommerce store currently reports:
- Latest known stock, price, and listing state for every product and variant
- Import progress and catalog completeness, so partial or failed reads are visible
- Channel connection status and the last successful observation time
- Explicit per-item stock or price corrections, only when the channel reports write capability
WooCommerce Change Detection
Between observations, GNIZDO records what changed in the channel and keeps that evidence reviewable:
- Stock drops, including products that fall to zero while a listing stays active
- Unexpected price changes that may signal margin loss or misconfiguration
- Listings appearing, disappearing, or losing stock or price data
WooCommerce Freshness and Oversell-Risk Review
Stale data is a risk on its own: a channel that has not been successfully observed recently may no longer match the store. GNIZDO flags stale channels, incomplete imports, and low-stock-plus-stale combinations so operators can review the affected SKUs before the next order lands.
Beta: Etsy (OAuth-only, read-only)
Etsy connects through its dedicated OAuth flow. It is read-only: GNIZDO reads confirmed Etsy catalog evidence (active and sold-out listing scope), runs applicable detections, and records generation changes, but it does not write catalog changes back to Etsy. Etsy is in beta, so coverage can change.
Beta: Shopify (read-only, in rollout)
Shopify connects through GNIZDO's Shopify OAuth install flow and reads its catalog: canonical stock and price evidence, confirmed generations, freshness and change evidence, and mapping eligibility. It is read-only with no write-back. Shopify is a beta integration currently in rollout — its date-backed read-only runtime is implemented but not yet generally available to all stores. Public sign-up continues to start with WooCommerce and Etsy.
Planned: eBay
eBay's inventory operates independently from other platforms, and it penalizes sellers for cancellations caused by out-of-stock situations. A planned eBay integration should make active-listing stock state, freshness, and quantity changes visible so fixed-price sellers can catch risky listings earlier. eBay is planned; there is no live eBay connection yet.
Any item-level comparison across channels additionally requires confirmed shared identity. Connecting a listing does not by itself make it comparable with another channel's listing.
Integration Architecture
Our integration approach prioritizes reliability over speed:
API Connection Management
For supported and beta integrations, GNIZDO uses scoped WooCommerce API credentials, Etsy's dedicated OAuth flow, or Shopify's OAuth install flow, and handles:
- Credential or OAuth handling scoped to the platform's supported capabilities
- Rate limit compliance to avoid API restrictions
- Retryable first-read and failed-read recovery, with cooldowns against repeated requests
- Connection, sync, and catalog-trust evidence remaining independently visible
- Capability-gated explicit WooCommerce item writes, separate from catalog observation and never automatic
- Shopify and eBay runtime connections: Shopify is a read-only beta in rollout; eBay is planned and has no live connection yet
Data Observation Cadence
A first import builds the local channel view, and periodic or manual reads refresh the latest known state:
- Each channel refreshes into its own independent local view
- Only one read runs per channel at a time; an active read is allowed to finish
- Freshness always depends on platform limits and response timing
Detection Logic
Our detection engine works channel-locally first:
- Evaluates each channel's catalog evidence, freshness, completeness, and sync execution independently
- Preserves latest known stock, pricing, and listing state for review
- Surfaces stock and price changes between observations with the evidence behind them
- Compares item values across channels only for listings with confirmed shared identity
What Integration Doesn't Include (Yet)
To set realistic expectations, the current integration surface does not include:
- An eBay runtime connection (planned, no live connection)
- Shopify as a generally available integration — it is a read-only beta in rollout
- Automatic inventory updates or remediation across platforms; supported WooCommerce writes are explicit per-item actions
- Automatic cross-channel identity — a matching SKU, title, or external ID alone is never proof of the same item; GNIZDO can surface likely candidates, but only explicit user confirmation establishes a shared mapping
- A warehouse, POS, or WMS source of physical stock truth — GNIZDO sees confirmed channel observations, not your shelf count
- Product listing creation, bulk uploads, automated repricing, fulfillment, or customer communication
We're focused on inventory evidence, historical reporting, and channel-scoped review first. Additional features come later based on seller needs.
Inventory visibility
Account access — Inspect catalog trust, connection state, sync execution, stock and price changes, and oversell-risk signals
Supported now — WooCommerce catalog reads plus capability-gated explicit per-item writes; Etsy OAuth-only read-only catalog evidence
Beta — Shopify read-only, in rollout
Planned — eBay
Pricing — Account access is available while GNIZDO validates real multichannel inventory problems
Keep the first pass focused so you can review the evidence you are dealing with:
- Which channel data looks stale or unreliable
- Which stock or price changes were unexpected
- Whether oversell risk or spreadsheet checks are creating extra work
Getting Started
If you sell through WooCommerce or Etsy and deal with stale data, unexpected changes, or oversell risk, GNIZDO provides channel evidence for these problems within each platform's supported capabilities. Shopify is a read-only beta in rollout; eBay is planned.
We don't promise perfect real-time updates or zero conflicts. We promise visibility into where your channel data drifts, so you can address it before it affects customers.
Create an account for detection-first inventory visibility. GNIZDO helps you review stale channel data, unexpected stock and price changes, and overselling-risk evidence. Catalog reads are supported for WooCommerce and Etsy; explicit per-item writes are limited to write-capable WooCommerce channels. Create account.