We audited an existing WordPress and WooCommerce store selling products for children. Delivery calculations, order exchange with 1C and customer notifications were improved in stages, retaining the existing store without a complete rebuild.
All case studies
Online store technical audit
Improvements to an existing WordPress/WooCommerce store: CDEK shipping, 1C order exchange, notifications and back-in-stock alerts without a complete rebuild.
Images2Video1
SolutionWordPress/WooCommerce audit and integrations
StatusDelivered project
Project interface
Screens from the delivered solution.
Select a screen to open the full image.
Project video
See the solution in action.
Play the recording, seek to any point or open it full screen.
Client task and starting point
Technical issues had accumulated in CDEK shipping calculations, order and status exchange with 1C, receipt processing and customer notifications. Some checkout scenarios did not show shipping options or pickup points, while store and 1C statuses diverged.
Parts of order handling required manual oversight. Sales reporting was difficult for accounting staff, and legacy mechanisms remained in the administration area. The task was to identify causes and resolve them step by step.
What was implemented
An audit of WordPress/WooCommerce, hosting, logs and integrations, followed by improvements to CDEK shipping, 1C order exchange, dispatch dates, notifications and a back-in-stock waiting list.
- Reviewed WordPress/WooCommerce, hosting, logs and existing integrations.
- Fixed CDEK integration and shipping calculations: postcode lookup for manually entered cities, display of the city used for the quote, and country switching for overseas cities.
- Synchronised store and 1C statuses, configured the payment, processing, dispatch and completion sequence, and updated statuses from CDEK events.
- Re-exported previously stuck orders to 1C with their current statuses.
- Added a «ДатаОтправки» (dispatch date) field that retains the actual dispatch date regardless of later status changes.
- Checked the existing Robokassa integration, initial and final receipt scenarios, and fiscal-operation logs.
- Configured customer tracking-number delivery and improved order emails.
- Added a waiting list: customers leave an email for an unavailable item and receive a notification when it returns to stock.
- Reviewed legacy administration functions, technical access, webhooks and data transfers to external services.
- Prepared the store for a later transition to a new acquiring and online cash-register setup.
How the solution works
- 01
Checkout and shipping
The customer places an order and selects CDEK and a city. The store determines shipping-calculation inputs and displays available pickup points.
- 02
Payment and 1C exchange
After payment, the order receives the corresponding status and is transferred to 1C. Previously stuck orders were re-exported with current information.
- 03
Dispatch and statuses
After CDEK shipment creation and acceptance, the store records dispatch and preserves the dispatch date. Delivery events update order statuses; the customer receives tracking information and notifications.
- 04
Reporting and stock
Accounting staff report by the actual dispatch date. Customers can leave an email for an unavailable item and receive a back-in-stock notification.
Technical logic and integrations
The work was carried out within the existing WordPress/WooCommerce store through an audit and staged improvements, without replacing the whole website.
CDEK events are linked to order statuses, and the 1C exchange transfers current data. A separate «ДатаОтправки» field remains unchanged after subsequent status updates and is used for reporting.
The existing Robokassa receipt workflow was reviewed through receipt scenarios and operation logs. A new acquiring and cash-register setup was prepared as a later stage and is not claimed as a completed migration.
The project materials list WordPress, WooCommerce, CDEK, 1C, Robokassa, SMS.ru, email, Bitrix24 and external webhooks. Credentials, keys and internal addresses are not published.
WordPressWooCommerceCDEK1CRobokassaSMS.ruEmailBitrix24Webhooks
Business value
The project materials report around 300–700 unsuccessful CDEK calculations per day when cities were entered manually. After the changes, this fell to about 30 per day; most remaining cases relate to users leaving their input incomplete.
Order statuses update automatically from actual delivery events, and current information is transferred to 1C. Previously stuck orders were re-exported.
A separate dispatch-date field lets accounting staff report by the actual dispatch day regardless of the current order status.
The supplied description reports fewer manual actions in order handling, delivery oversight and reconciliation between the store and 1C.
The main stage was completed in September 2026. The solution is used in the live store, with technical support and further improvements continuing.
Have a similar workflow?Tell us what needs to change. We can discuss the working logic without a long questionnaire.
Discuss a similar project Have a similar task?