Skip to content

E-commerce CRM

When the same person shops from the website, the app and the marketplace, they look like three separate customers in the system; that is why who is really valuable, and which channel the budget pays off in, cannot be measured.

Web, app and marketplace records merge on the same customer card through e-mail and phone; the last purchase date, the frequency and the amount are fields on that card.

E-commerce CRM
  • Merge website, app and marketplace data into a single customer record
  • Let an abandoned cart fall in as a record; set as a rule how long afterwards the e-mail, SMS and push notification goes out
  • Measure customer value on the recency, frequency and monetary (RFM) axis
  • Compare the performance of marketplace, web and mobile channels side by side
  • Connect a single WhatsApp number to the team inbox and have conversations assigned by the rule you define
Single Customer RecordWeb, app and marketplace records are merged on the same customer card through e-mail and phone; duplicate records are reduced to a single card with a merge operation.
Abandoned Cart Recovery FlowAn abandoned cart falls in as a record and opens a follow-up task; how long afterwards the e-mail and WhatsApp message goes out is set as a rule during setup. The store connection is built specifically for the project over the API.
RFM SegmentationThe last purchase date, the frequency and the amount are fields on the customer card; the segment comes out of lists filtered on these fields.
Channel Performance AnalysisThe channel is a field on the order; the comparison of turnover and conversion by channel is taken from the report on that field.
Returns and Exchange FileA return request is a file tied to the order's own record; the reason, the shipping tracking number and the decision sit in fields, and the notification going to the customer and the confirmation coming from the warehouse accumulate under the same file.

In e-commerce the same person browses from the app in the morning, buys from the marketplace in the evening and writes about their problem over WhatsApp. When these three contacts are kept in three separate places, sending a "special for your first order" discount to the customer placing their tenth order is all too easy; the campaign budget is spent on the audience that is loyal anyway, and the undecided ones never come back.

Rapitek CRM writes the data of the three channels into the same customer record and calculates the segment from this merged history. Because the WhatsApp conversation also falls into the same record, the history of the conversation stays with the team even when the person who made the sale and the person who answers the message are different; when staff change, the relationship built with the customer does not leave along with a personal phone.

Frequently asked questions

How do we reduce the same person's records from the site and the marketplace to a single record?
Web, app and marketplace records are merged on the same customer card through e-mail and phone; duplicate records are reduced to a single card with a merge operation, and the order history is gathered under that card.
Can a message go to a customer who abandoned their cart?
When the abandoned cart falls into the CRM as a record, a follow-up task is opened; you set as a rule during setup how long afterwards the e-mail or WhatsApp message goes out. The connection that carries the cart data from your store platform into the CRM does not come out of the box; it is built specifically for the project over REST API and webhooks, and its scope is determined at the discovery meeting.
Can we tell the customer which stage their return request is at?
The return request is a file tied to the order's record; the reason, the shipping tracking number and the decision sit in fields. Because the notification going to the customer and the confirmation coming from the warehouse accumulate under the same file, the latest status is read from one place.
How long does setup take for e-commerce?
After the discovery meeting we give you a date, not a range — how many fields, how many stages and how many reports your e-commerce process requires becomes clear in that meeting. We migrate your data ourselves; the scope of the migration and its cost, if any, are worked out in the same meeting and shared in writing.
Will it integrate with my existing systems for e-commerce?
In e-commerce, web, app and marketplace records are merged on the same customer card through e-mail and phone. If you use Logo, Netsis, Mikro or SAP, your CRM talks to it — we build the connection ourselves. There is no out-of-the-box module: because the access and field structure on the other side differs from installation to installation, a single button does not work the same way everywhere. The same applies to your store platform and your marketplace accounts. The connection is set up specifically for the project over our REST API covering 183 business objects, OAuth2, webhooks and import/export. We work out its scope and cost at the discovery meeting and share them in writing.
Can more than one person use the same WhatsApp number for e-commerce?
Yes. We connect your own Meta WhatsApp Business account to the CRM; your team replies from a single business number and all messages appear in the team inbox. Conversations are assigned according to the rule you define. Managers can monitor conversations and response times. Even if staff change, the message history stays in the CRM. The Meta invoice is issued directly to you — we do not sell message packages or credits.
Made with RapitekGO

We would like to use optional cookies to measure your visit. The site works exactly the same if you decline. Cookie policy