Zid Platform

Zid stores hold product, stock, and order data natively, but getting that data into the exact structure and format each shopping channel, marketplace, or ad platform expects is a separate job. Feedance connects directly to your Zid store, reads your catalog and stock levels, and turns them into properly formatted feeds — so you are not manually exporting, editing, and re-uploading spreadsheets every time a price or stock level changes.

Because the connection is direct, updates made in Zid (a new product, a price change, a stock adjustment) flow through to your feeds without a manual export step, which reduces listing errors, out-of-stock surprises, and the ongoing maintenance overhead of running a multi-channel catalog from a Zid store.

Feedance connects to Zid using secure, token-based authorization. When you link your store, you approve access through Zid's own authorization screen, and Feedance receives a scoped access token rather than your store password. That token is what Feedance uses to read your product catalog, stock levels, and order data, and to keep your feeds synchronized going forward.

Access can be reviewed or revoked from your Zid store's connected-apps settings at any time, and Feedance only requests the level of access it needs to build and maintain your feeds.

Feedance works with exactly three data entities from any connected platform, including Zid:

Feedance does not access or use Zid customer records, coupons, shipping or tax settings, or any other store data outside of products, inventory, and orders.

• Bilingual catalog data: Zid stores product names and descriptions in separate Arabic and English fields, so if your store sells in both languages it is worth double-checking which language your feed is pulling from and that both versions are filled in.
• Variant configuration matters: Zid only returns variant details, such as size or color options, for products that have been explicitly configured with variants in the Zid dashboard; a simple, non-variant product will not have that data to sync.
• Product endpoint rate limits: Zid enforces its own request-rate limit on product-related API calls per connected app per store, which is a normal part of how the platform protects itself during large catalog syncs and is handled automatically rather than something you need to configure.
• Bulk update batching: Zid's own bulk product update endpoint is capped at a limited number of products per request, so very large catalogs are naturally synced in batches rather than a single call.

1. Log in to your Feedance account and choose to add a new platform connection.
2. Select Zid from the list of supported platforms.
3. You will be redirected to Zid's own authorization screen; log in to your Zid store and approve the requested access.
4. Once redirected back to Feedance, confirm your store details and select the products you want included in your feeds.
5. Save the connection and let Feedance run its first sync to pull in your products, inventory, and orders.

Feedance keeps your Zid-connected feeds updated on a regular, automated schedule so that prices, stock levels, and new products stay current without manual re-exporting. Very large catalogs or high-volume stock changes may take a little longer to fully propagate across a sync cycle, but there is no manual export or upload step required on your part.

1. Keep product titles, descriptions, and images complete and consistent in Zid, since incomplete listings tend to carry straight through into thin or rejected feed entries.
2. Make sure every product has an accurate SKU and barcode set in Zid, as these are typically what shopping channels use to match and de-duplicate listings.
3. Configure variants properly in Zid for any product that comes in multiple sizes or colors, rather than listing each variation as a separate standalone product.
4. Keep stock quantities accurate and avoid marking items as unlimited stock unless that is genuinely the case, so channels do not oversell or hide in-stock items unnecessarily.
5. Avoid pushing very large bulk edits directly in Zid right before you need a feed refreshed, since Zid's own product API limits mean large batches take a bit of time to fully process.