Frequent price imports and catalog sync

[Former Member]

Hello experts,

in one of our projects we have the requirements that...

• prices will be added/updated by an external system via hot folder multiple times a day

• the standard staged/online workflow for products/variants is required (catalog sync staged -> online)

To achieve this, we have two basic ideas:

1. Synchronize product catalog after price import (staged -> online)

2. Somehow figure out if it's possible to exclude PriceRow from synchronization (both staged/online product refer to the same price row)

While option 1 is quite clear and straight forward to accomplish (despite it's obvious drawbacks), option 2 seems not to be supported conceptually.

What is your recommended setup regarding these requirements?

[Former Member · Accepted solution]

With hybris > 5.3 it's possible to decouple price rows from products, so both the staged as well as the online versino of the product can use the same price row instances.

See https://wiki.hybris.com/display/release5/Decoupling+PDTRows+from+Product for more details.

[Former Member]

Hi Volodymyr,

do i understand it right that you would create a specific sync job for syncing PriceRow item/price property only? This seems to be a feasible idea since this job will execute way faster then a complete catalog sync. Yet i do not know if you will run into problems when syncing a price row of a product that is not yet synced to online. So you would have to limit the sync of price rows to items that...

1. ...have a product in state 'APPROVED'...

2. ...that is already synced to online catalog version

Right? 🙂

Yet, since a sync of price rows is simply not necessary, i would still prefer a solution where you don't have to sync price rows at all.

[Former Member]

Well, you could check necessary conditions in a place you call this job before actual synchronization of price rows. But if you prefer not to sync it's up to you:)

[Former Member]

Hi Norbert

I would play with synchronization jobs. I believe we can configure what items and what properties should be synchronized, in your case it's PriceRow item and price property. Then we would call this job every time we get a price update.

I'm not sure if I'm right:)