Holiday demand peaks at a flower-shop chain
Narciss is a chain of nine flower shops in Rzhev. Alongside in-store sales, it takes flower-delivery orders.
Seasonal peaks are the main challenge. According to the original publication, the chain handles up to 250 orders per day on holidays. Before this project, requests were managed with Google Sheets and the website CMS, which became a bottleneck on those days.
A flower-delivery order passes through several people: a manager takes it, a florist prepares the bouquet and a courier delivers it. If status and details live in a spreadsheet, each person has to check manually and the customer cannot see what is happening.
One order flow for shops, florists and couriers
The project goals were to bring all incoming channels into amoCRM, automate order-status notifications to customers, florists and couriers, integrate FloraPoint to prevent duplicate orders, and add analytics for monitoring staff and order handling.
For customers
Order flowers through a familiar messenger or social network, receive timely order-status updates and reminders of important dates.
For florists and couriers
Learn about their order tasks automatically without repeatedly checking details with a manager.
For the chain's management
See detailed analytics on shops, staff and orders.
How amoCRM connects the order, bouquet and delivery
The solution uses amoCRM as the centre of order handling, connected to intake channels, notifications and the external FloraPoint system.
amoCRM pipelines represent each handling stage from order intake to delivery.
Messengers and social networks are connected so orders enter the CRM directly.
Automatic order-status notifications go to customers, florists and couriers.
FloraPoint integration prevents duplicate orders, while important-date reminders support repeat-order offers.
What we configured for Narciss
- 01
Built amoCRM pipelines
Split order handling into stages from acceptance to delivery and configured them in the CRM.
- 02
Connected messengers and social channels
Configured orders from messengers and social networks to arrive directly in amoCRM.
- 03
Configured notifications
Automated alerts to customers, florists and couriers when an order changes status.
- 04
Integrated FloraPoint
Connected amoCRM with FloraPoint to avoid creating the same order twice.
- 05
Added important-date reminders
Configured dates that trigger offers for customers to place repeat orders.
- 06
Added analytics
Introduced reporting on staff, orders and the chain's shops.
The project catalogue also lists Yii2 and AI components in Narciss's stack. Their roles and implementation details are not described in the original publication.
Orders remain visible even during holidays
The original publication describes results qualitatively without final figures for handling speed or order volume.
- Messenger and social-media orders enter amoCRM and move through pipelines from intake to delivery.
- Customers, florists and couriers receive automatic order-status updates.
- FloraPoint integration helps avoid duplicate orders.
- Management can see detailed analytics on the shops' work.
- According to Gulian Digital's original publication, order handling became faster and clearer, while important-date campaigns increased repeat orders.
These facts come from Gulian Digital's 2023 publication on gulian.am, which also includes positive client feedback. The nine shops and peak of 250 daily orders are client-reported; speed improvements and repeat-order growth were not independently measured.
amoCRM, FloraPoint and the wider project stack
What the project included
amoCRM implementation; order pipelines from intake to delivery; messenger and social-channel integrations; customer, florist and courier notifications; FloraPoint integration to prevent duplicates; important-date offers for repeat orders; and analytics on staff, orders and shops. The project catalogue also lists Yii2 and AI, but the original publication does not describe these components.
