Hybris Platform

Hybris is built for large, often complex product catalogs spanning multiple business units, regions, or catalog versions. Getting that data into a clean, consistent format for shopping channels, marketplaces, and other downstream systems can take significant manual effort. Connecting Hybris to Feedance lets you centralize your product, inventory, and order data in one place, apply consistent formatting rules, and keep that data flowing without building and maintaining custom scripts against the platform yourself.

Feedance connects directly to your Hybris store using your store's credentials and access permissions. Once connected, Feedance reads your product, inventory, and order data on a scheduled basis and keeps it synchronized so it is ready to use in feeds, exports, and integrations.

You stay in control of the connection at all times: access can be reviewed or revoked from your Hybris environment whenever you choose, and Feedance only requests the level of access needed to read and, where applicable, update the supported data.

• Staged vs. online catalogs. Hybris typically separates product data into a "staged" catalog version, where changes are made, and an "online" catalog version, which is what the live storefront (and connected integrations) actually serve. Product or price changes made in the staged catalog will not appear until a catalog synchronization job has run, which can introduce a delay between an edit and when it is reflected in a feed.
• ImpEx-based data model. Hybris uses its own ImpEx format for bulk importing and exporting data internally. While Feedance does not require you to work with ImpEx directly, it's a useful concept to understand if your team is troubleshooting why certain data looks unexpected, since imports can be batched and delayed by internal jobs.
• Scheduled indexing jobs. Search and catalog data in Hybris is often refreshed through scheduled cron jobs (including Solr search indexing), rather than updating instantly. This means very recent catalog changes may take some time to be fully reflected across the platform, independent of any external integration.
• On-premise vs. cloud versions. Because Hybris has been deployed both as an on-premise product and as the newer cloud-hosted SAP Commerce Cloud, the exact APIs and configuration available can vary by version and deployment. It's worth confirming which version and deployment model your store runs on before connecting.

1. Log in to your Feedance account and choose to add a new platform connection.
2. Select Hybris from the list of available platforms.
3. Enter the connection details and credentials requested for your Hybris store.
4. Authorize Feedance to access your Products, Inventory, and Orders data.
5. Confirm the connection and let Feedance complete its initial data sync.

Once connected, Feedance syncs your Hybris products, inventory, and orders on a regular scheduled basis to keep your data current. Because Hybris itself can introduce its own internal delays, such as catalog synchronization or indexing jobs, the timing you see reflected in your live storefront may occasionally lag slightly behind the moment a change was made in the backend.

• Keep product titles, descriptions, and attributes complete and consistent in Hybris, since incomplete source data carries through to any feed built from it.
• Publish catalog changes (staged to online) promptly so the data Feedance syncs reflects your intended, current catalog.
• Use clear, structured product attributes in Hybris where possible, as well-structured source data is easier to map cleanly to channel requirements.
• Review inventory accuracy regularly, since stock discrepancies are one of the most common causes of channel listing issues.
• Monitor your Feedance sync activity after making bulk catalog updates in Hybris to confirm the changes flowed through as expected.