Ikas Platform

Ikas is designed primarily as a storefront and store-management platform, not a dedicated feed management system. Merchants who want to list products on marketplaces, comparison shopping engines, or advertising channels typically need product data formatted, mapped, and kept in sync across every destination — something Ikas's native tools are not built to handle at scale.

Connecting Ikas to Feedance lets merchants centralize product, inventory, and order data from their Ikas store and turn it into properly structured feeds for the channels they sell on, without manually exporting and reformatting files every time prices, stock levels, or order statuses change.

Feedance connects directly to your Ikas store using an authorized app connection. Once you grant access, Feedance retrieves your product catalog, stock levels, and order information directly from your store and keeps this data available for feed creation, mapping, and export to your chosen sales channels.

Because the connection is authorized at the store level, you control exactly what access Feedance has, and you can revoke that access from your Ikas dashboard at any time.

Feedance works with three core data entities on any connected platform, including Ikas:

• GraphQL-based API: Ikas's Admin API is built entirely on GraphQL rather than REST, and the platform has been evolving its API from a v1 to a v2 version. This generally means richer, more precise data queries, but it also means integrations depend on Ikas's ongoing API changes.
• Scope-based permissions: Access to store data on Ikas is granted per resource (for example, products, orders, or inventory can each be authorized separately). This is why it's important to confirm that the connection has been granted access to all three of the data types Feedance uses.
• Time-limited access sessions: Authorization sessions on Ikas's platform are refreshed periodically rather than lasting indefinitely, which is a normal part of how app connections stay secure. Feedance handles this refresh automatically, so no action is usually needed from you.
• Webhook-based updates with limited retries: Ikas can push real-time change notifications (for example, when an order or product is updated), but if a notification delivery fails, Ikas stops retrying it after a small number of attempts. Feedance's scheduled syncs act as a safety net to catch any changes a missed notification might otherwise skip.

1. Log in to your Feedance account and choose to add a new store connection.
2. Select Ikas from the list of supported platforms.
3. You'll be prompted to authorize Feedance to access your Ikas store; log in to your Ikas dashboard if requested and approve the connection.
4. Confirm that product, inventory, and order access are all enabled for the connection.
5. Once the connection is confirmed, Feedance will run an initial sync to import your store data, after which you can start building and mapping feeds.

Feedance syncs product, inventory, and order data from Ikas on a regular schedule, and it can also pick up relevant real-time updates where the platform supports them. Exact sync frequency can vary depending on your Feedance plan and the volume of data in your store, so if you rely on very time-sensitive pricing or stock changes, it's worth checking your account's current sync settings.

1. Keep product titles and descriptions complete in Ikas, since incomplete source data carries through to every feed you generate.
2. Use clear, consistent categories and variant structures in your Ikas catalog so Feedance can map them accurately to each channel's required format.
3. Keep stock levels accurate in Ikas, since out-of-date inventory is one of the most common causes of rejected listings on marketplaces and ad platforms.
4. Review your feed mappings after making major catalog changes in Ikas, such as adding new product types or restructuring categories.
5. Run a manual sync before high-traffic periods (sales, launches) to make sure your feeds reflect the latest pricing and stock.