Miva Platform

Miva stores often carry large, complex catalogs with product options and variants spread across many categories, which makes manually keeping marketplace and shopping-feed listings accurate a significant burden. Connecting Miva to Feedance lets you pull your live catalog, stock levels, and order data into one place so your product feeds stay accurate without manual exports.

Instead of maintaining separate spreadsheets or one-off export scripts, you get a single connection that keeps downstream channels aligned with what is actually in your Miva store.

Feedance connects directly to your Miva store using an authenticated API connection. You provide store connection credentials (such as your store's API access details), and Feedance uses them to securely read your catalog, inventory, and order data on a recurring basis.

No plugin installation or theme changes are required on the storefront side. Once the connection is authorized, Feedance handles scheduling, retries, and data normalization so your feeds and reports reflect current store data.

• Attributes versus Inventory Variants: Miva lets merchants model product options two different ways: simple Attributes (options attached to one product record) or Inventory Variants, where each combination of options becomes its own product record with its own SKU and stock count. Which method a store uses affects how granular product and inventory data appears when it is read.
• Long platform history, modern API layer: Miva's storefront and templating layer (Miva Script) dates back to the 1990s, but data access for integrations like Feedance goes through Miva's newer JSON API, which is the supported way to read catalog, inventory, and order data rather than older XML provisioning methods.
• Authenticated, signed API access: Miva's JSON API requires a store-issued access token, and requests can require an additional signed request header. Store owners generate these credentials in their Miva admin, and Feedance uses them solely to authenticate its own requests to your store.
• Incremental order and product queries: Miva's list-query functions support filtering (for example, by last-modified timestamp), which allows changed records to be identified without re-reading the entire catalog on every check.

1. Log in to your Feedance account and start a new platform connection, selecting Miva as the platform.
2. Generate the required API access credentials in your Miva store admin, following the on-screen instructions in Feedance.
3. Enter your store URL and credentials into Feedance to authorize the connection.
4. Let Feedance run its initial sync to import your products, inventory, and orders.
5. Review the imported data, then set up your feed rules, schedules, and export destinations.

Feedance checks your Miva store for changes on a regular automated schedule, so product, inventory, and order updates flow through without you having to trigger anything manually. Sync frequency can vary based on your plan and catalog size, and you can also trigger a manual sync from Feedance whenever you need the very latest data right away.

1. Keep product titles and descriptions complete and consistent in Miva so downstream feeds don't need manual patching.
2. Decide deliberately between Attributes and Inventory Variants for products with options, since this affects how granular your feed listings and stock counts will be.
3. Use clear, unique category assignments so feed rules based on category can target the right products.
4. Keep product images and identifiers (such as SKUs) clean and populated, since incomplete data is a common cause of rejected feed listings.
5. Review your sync history in Feedance periodically to catch and resolve any recurring connection warnings early.