Purchase status

[yettimon]

Purchase/order permanent status 'success'.

Is that possible to track actual purchase/order status from magento ?
Right now that integration works that way, that every purchase passed to that tool marked as 'successful'
Would be better to receive a purchase/order status directly from magento ?

[eduard13]

Hi @yettimon, thank you for your question. Regarding the order status, it is used "success" on purpose, meaning that the order has been successfully placed/created.

However, we might think and improve it by adding a config to whether keep the real Magento order status or success one.

Looking forward for your suggestions.

Thank you.

[yettimon]

@eduard13
Thanks for your response.
I'm not a experienced developer in magento, but i want to replace that standart 'success' status with a valid one.
Would be enough to use return something like getData('status') ?
Or is there any better way to do that ?

Thanks.

[vlmed]

Hi @yettimon. This module is very flexible to customize. You can easily replace the fields with your own. This is described in the readme file https://github.com/exponea/bloomreach-magento2-integration#how-to-add-custom-logic-for-field-rendering. The idea is to replace the class that renders the field with your own class via di.xml.
How you can do that:

1. Create your own module that will modify our extension.
2. Create your class that will render a status field. (In your case you can skip this step, because we already have that class in the module
3. Pass that class to the mapper in the di.xml.

We have prepared a custom module with solution for your request.
You can install that module and order status will be mapped to the real order status.

Bloomreach.zip
Installation steps:

1. Add that module to the app/code directory.
2. Run bin/magento setup:upgrade
bin/magento setup:di:compile
bin/magento setup:static-content:deploy
bin/magento cache:clean

Thank you

hi @yettimon , are you happy with this update? Are you receiving proper statuses? I am a product manager at Bloomreach and I'd be interested to hear more about your use cases, can you get in touch with me?

@yettimon have this patch resolved your problem? would you recommend merging this in base as an optional feature?