Oxid Platform

Running a self-hosted platform like Oxid means product data, stock levels, and order records live entirely inside your own store environment. Feedance connects to that environment so your product information can be turned into accurate, up-to-date feeds for marketplaces, comparison shopping engines, and advertising channels without manual exports or spreadsheet work.

Because Oxid supports flexible catalog structures, including product variants and multi-shop setups, keeping external channels aligned with what is actually in your store can become time-consuming as your catalog grows. Feedance centralizes that work: it reads your Oxid product and inventory data, keeps it synchronized, and reflects order updates back into your workflow, so your listings stay consistent wherever they appear.

Feedance connects directly to your Oxid store using the credentials and access details you provide during setup. Once the connection is authorized, Feedance communicates with your store on a scheduled basis to retrieve product and inventory data and to pick up new and updated orders.

This connection is configured once per store. After that, Feedance handles the ongoing data exchange automatically, so you do not need to manually export files or repeat the setup each time your catalog changes.

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

A few characteristics of how Oxid is built and deployed are worth keeping in mind when connecting it to any external tool:

• Products are called "articles" internally. Oxid's data model refers to products as articles, and a single article can have multiple variants defined through selection lists (for example size or color). Feed tools need to correctly distinguish parent products from their variants when mapping catalog data.
• Self-hosted deployment varies by installation. Because Oxid is self-hosted and comes in different editions (Community, Professional, Enterprise) and versions, the exact configuration, server access, and available interfaces can differ from one store to another, which may affect initial connection setup.
• Multi-shop ("Mall") structures exist in Enterprise editions. Oxid's Enterprise edition supports subshop, supershop, and multishop configurations that split or share catalogs across multiple linked shop instances. On these setups, it is important to confirm which specific shop instance is being connected.

1. Create or log in to your Feedance account and choose to add a new store connection.
2. Select Oxid as the platform you want to connect.
3. Enter the access details for your Oxid store when prompted, and authorize Feedance to connect.
4. Let Feedance perform its initial sync to pull in your products, inventory, and recent orders.
5. Review the imported data, then set up your feeds and destinations using the synced catalog.

Feedance syncs product, inventory, and order data from your Oxid store on a regular scheduled basis so that feeds and reports reflect recent changes without requiring manual action. Exact sync timing can vary depending on your plan and store size, and a manual sync can typically be triggered as well when you need the latest data immediately.

1. Keep product titles and descriptions complete and consistent in Oxid, since this is the source data Feedance uses to build your feeds.
2. Make sure variant attributes, such as size or color selection lists, are filled in correctly so variants map cleanly to channel listings.
3. Keep stock levels accurate in Oxid so exported feeds do not advertise products that are out of stock.
4. If you run a multi-shop setup, double-check that the correct shop instance is connected before publishing feeds.
5. Review synced data in Feedance after major catalog changes in Oxid to confirm everything carried over as expected.