The catalog task
The same products appear on the website and in the CRM. Product records, variants, photos and prices need updates, and the operator needs to know which actions completed. Connected workflows handle these tasks and return operation results.
Implemented features
Each operation has its own workflow and checks. Service responses are tracked separately so that a completion report can distinguish a successful step from a failed one.
- Product creation with an SKU duplicate check and data sent to WooCommerce and KeyCRM.
- Photos from Telegram: main image selection, a gallery and images assigned to color variants.
- Price changes: the WooCommerce response is checked before the next update in KeyCRM.
- Availability updates with an operation preview and operator confirmation.
- Change history and supported field restoration after checking the current state.
Checks before changes
SKUs, product variants and target fields are matched before catalog changes. Creation, availability and restoration workflows include checks and confirmation steps. Missing information is returned to the operator for clarification.
Development outcome
The implemented workflows manage catalog operations through Telegram and exchange data between the website and CRM. Shared history and operation responses help inspect changes and review partially completed actions.
Adapting it to another store
I first check the catalog structure, SKU rules, APIs and permitted actions. We agree on the source of price and availability data, operator confirmations and partial-result reporting. Scope, cost and support are assessed for the specific process.
This technical project describes implemented features and the solution structure. Store data is anonymized; no measured time savings or sales growth are claimed.