Magento Platform

Magento stores hold catalog and order data in a structure built for flexibility rather than for feeding third-party marketplaces and ad channels out of the box. Product data is organized around configurable products, attribute sets, and per-store-view overrides, which makes it powerful for merchandising but harder to export in the exact shape a shopping feed or marketplace listing requires. Connecting Magento to Feedance lets you turn that catalog into properly formatted, continuously updated feeds without manually exporting and reshaping CSVs every time prices, stock levels, or listings change.

For merchants running Magento 2 or Adobe Commerce, this also means feed updates can keep pace with catalog changes made through the admin panel, rather than depending on scheduled manual exports or one-off developer scripts.

Feedance connects directly to your Magento store using the store's own APIs. During setup, you provide your store URL and authorize Feedance to access your catalog, inventory, and order data. Once authorized, Feedance reads your product and stock information on a regular basis and keeps your feeds synchronized as your store changes, without requiring any code changes or extensions to be installed on your Magento instance.

The connection is read-oriented for catalog and order information: Feedance pulls the data it needs to build and refresh your feeds, and any changes you want reflected in your store (such as marketplace-driven stock adjustments) are applied back through the same authorized connection, depending on the workflow you configure.

Feedance works with three core data entities from your Magento store. It does not access customer records, coupons, gift cards, tax or shipping configuration, or newsletter subscribers.

1. Magento 1 vs. Magento 2: Magento 1 reached end of official support in June 2020 and uses an older API surface than Magento 2. If you are still running Magento 1, confirm your store's API access is functioning correctly, since community patches and hosting environments vary widely for unsupported installations.
2. Attribute sets and the EAV model: Magento stores product data using an entity-attribute-value structure, and different products can use different attribute sets. This means fields like size, color, or custom specifications may be named or organized differently across product types in the same catalog, which is worth reviewing when mapping fields into a feed.
3. Multi-store and store view structure: Magento supports multiple websites, stores, and store views under one installation, each of which can carry its own pricing, language, or catalog visibility. If your store uses this structure, make sure the correct store view is targeted so feeds reflect the intended prices and listings.
4. Inventory across multiple sources: Magento 2 (from version 2.3 onward) supports Multi-Source Inventory, allowing stock to be split across multiple warehouses or sources. Stock totals shown in a feed reflect the store's own indexed inventory calculation, so any delay in Magento's own indexing process will carry through to feed updates.

1. From your Feedance dashboard, choose Magento as the platform you want to connect.
2. Enter your store URL and authorize Feedance to access your store's catalog, inventory, and order data.
3. Wait for the initial sync to complete, during which Feedance imports your existing product and stock data.
4. Map your Magento product fields and attributes to the fields required by your target feed or marketplace.
5. Review the mapped feed and publish it to your chosen channel.

Feedance keeps your Magento-connected feeds updated on a regular automatic schedule, so pricing, stock, and listing changes made in your store are reflected without manual re-exports. Exact sync frequency can depend on your plan and the size of your catalog; if you need near-real-time updates for fast-moving stock, this can be adjusted in your feed settings.

1. Keep attribute sets consistent across similar product types so that field mapping in Feedance stays predictable as your catalog grows.
2. Fill in key catalog fields (titles, descriptions, images, identifiers) directly in Magento, since Feedance builds feeds from the data already present in your store.
3. If you use Multi-Source Inventory, monitor Magento's own reindexing so stock levels feeding into your channels stay accurate.
4. Double-check which store view is mapped to each feed if you run multiple websites, stores, or store views, so pricing and availability match the intended market.
5. Review your field mapping after any significant catalog restructuring in Magento, such as adding new attribute sets or product types.