FAQ

GNIZDO looks for stale channel data, missing or inconsistent listings, delayed updates, freshness gaps, unexpected stock and price changes, and overselling-risk signals in each connected channel. Cross-channel item comparisons — same-item stock mismatch or price drift across channels — require listings with explicit or confirmed shared identity; a matching SKU alone is not enough.

No. GNIZDO does not make automatic cross-channel inventory changes. It shows where channel state is drifting so a human or operator can review the evidence before acting. That is intentional: blind sync can hide the root cause of mismatches instead of making it easier to fix.

You send the context you have: affected channels, one SKU or listing example, what each channel shows, and what you expected. GNIZDO reviews the SKU, channel, and state pattern to see whether it fits mismatch, freshness, price-drift, or oversell-risk detection. The next step may be early-access setup or a direct recommendation.

Usually a few days. Timing depends on catalog complexity and how much context is provided. One clear SKU or listing example, with the current state on each channel and when the issue was noticed, is often enough to make the first review useful.

WooCommerce is the supported integration today, with read-only catalog observation. Etsy, eBay, and Shopify are planned integrations — sellers there face the same problems, but those channels are not live yet. Amazon may appear in educational guides only.

Where available, GNIZDO reads SKU and listing identifiers, stock quantity or stock status, price, listing status, channel timestamps or freshness signals, and sync or channel status. The purpose is detection and review, not hidden automation.

Submitted review details are stored so the case can be reviewed. When channel connection is enabled, connected channel observations build a local read model for mismatch, freshness, price-drift, and oversell-risk review. GNIZDO does not collect broadly beyond what is needed for that purpose.

The landing and review flow does not ask for payment details or platform passwords. When channel connection is enabled, GNIZDO uses approved platform APIs and access depends on the permissions approved during setup. Contact us before connecting a channel if you have GDPR, security, or data-processing requirements.

Start with the highest-risk SKUs and channels: low-stock fast movers, high-volume listings, products with recent cancellations, or channels where updates look stale. Large catalogs are reviewed by focusing on risk first, not by trying to inspect every SKU manually.

Yes. GNIZDO is designed as a detection layer, not a replacement for every operations tool. It can help identify where channel state, freshness, stock, or price data no longer agree, even when another tool handles day-to-day operations.

Those products are broader operations or sync suites. GNIZDO is not trying to replace them immediately. It focuses on truth, freshness, mismatch evidence, and risk detection, so it can sit beside operations tools as a detection-first inventory layer.

Send the affected channels, one SKU or listing example, what each channel currently shows, what you expected to happen, and when the issue was noticed. Screenshots, order examples, or recent channel-update timing can help if they are available.

Yes. Inventory risk reviews are free for now, with no surprise billing. If paid plans are introduced later, pricing will be clear before anything changes.