Contact
Detail A1Client · Belgium
In production

Shopping Event VIP

We run the whole product: the web app, the mobile apps, the CRM, payments and the servers behind them.

Partner since20201August 2020, ongoing
Members200,000+Registered members
PlatformsWeb · iOS · AndroidPlus a staff check-in app
Quvor team8People on the account
Email cost−43%Per email, after our own CRM and a cheaper sender

Note 1The partnership began in August 2020. ↩

A–A
The business

Members-only fashion sales, run on consignment.

Model
Consignment, nothing paid upfront by brands
Channels
Physical events, members-only online sales
Revenue
Margin, early-access tickets, Shopify
Languages
Dutch, French
B–B
What we own

One central service holds the rules. Everything members and staff touch is built on it.

Where members and staff meet it
N1

Web app

Server-rendered, in Dutch and French

N2

Mobile apps

iOS and Android, wallet passes, receipt scanning

N3

Check-in app

Staff scan QR tickets at events

N4

International sites

A sister site in 7 languages

H · ×4 instances

Data hub

The shared rules: booking, capacity, payments, tickets and wallet passes

S1

CRM and campaigns

Segments, automations, a delivery log per member

S2

Background service

Transactional email, Shopify sync, a win-back flow

S3

Payments

Checkout and refunds for early-access tickets

S4

Email sending

SES with a dedicated IP, Postmark as fallback

Behind it
Fig. 2 — System map. Every part shown is built and maintained by Quvor.
C–C
The work, in detail

Six pieces of the product, and what changed.

Detail C1Member email
In production
C1

Our own CRM, then cheaper sending

−43%per email

Our own CRM replaced ActiveCampaign, then sending moved to SES with a dedicated IP.

How we did it
Problem
Member email ran on ActiveCampaign, a general marketing tool. Sending millions of emails to segments built from the platform’s own membership data needed a system made for it.
What we did
We built a CRM: campaigns with automations, triggers and delays, segments built from AND/OR conditions, and a delivery log for every member, with bounces and complaints tracked. Sends go out in batches of 500, so a 60,000-member send is spread over about 10 hours by design. Then we moved sending from Postmark to SES with a dedicated IP, and kept Postmark as the fallback.
Outcome
Before our CRM, ActiveCampaign cost about $1,000 a month, when they had far fewer contacts. In March 2025, sending 2.58 million emails with a dedicated IP cost $675. 43% cheaper per email at similar volume, with a dedicated IP that the old plan did not include. The bill now follows volume, so a quieter month costs less.
Member email · two steps
Step 1 · CRMActiveCampaign→Our own CRMwas about $1,000 a month, for far fewer contacts
Step 2 · SendingPostmark→SES, dedicated IP
MonthEmailsCost
Dec 2024 · Postmark2.45M$1,119.40
Mar 2025 · SES2.58M$674.55
Saved$444.85/mo
About $5,340 a year at that volume · batches of 500
Detail C2Accounts
Done
C2

Off WordPress without password resets

0password resets

Members moved off WordPress and kept their passwords.

How we did it
Problem
Member accounts lived on the old WordPress site. Moving to a new platform usually means asking every member to set a new password.
What we did
Each member’s password moves over silently the first time they log in on the new platform. Nothing changes for the member.
Outcome
Members kept their passwords. Nobody was asked to reset.
First login · new platform
  1. 1Member logs in with their old password
  2. 2The platform recognises the old password
  3. 3It moves to the new platform, and the member is signed in
Forced resetsNone
Detail C3Booking and payments
In production
C3

One rule set for web and mobile

1rule set

The same rules run web, iOS, Android and event check-in.

How we did it
Problem
When each app carries its own copy of the booking and payment rules, the copies drift apart, and members see different answers on different screens.
What we did
The rules live once, in the data hub: capacity per slot, clashes between bookings, member roles, payments with refunds, PDF tickets and wallet passes. The web app, the iOS and Android apps and the staff check-in app all call the same rules.
Outcome
One set of rules behind web, iOS, Android and event check-in.
Data hub · shared rules
RulesBookingCapacityClashesRolesPayments and refundsPDF ticketsWallet passes
Used byWebiOSAndroidCheck-in app
Detail C4International
Live
C4

A platform for more than one market

7languages

A sister site on the same platform, with a daily product import.

How we did it
Problem
Selling in more markets needs sites that each speak the local language, with a product catalogue that stays current without manual work.
What we did
We built a sister site on the same platform in 7 languages, with Dutch for both the Netherlands and Belgium, and a daily import that brings in discounted products from affiliate networks.
Outcome
One platform that can carry more than one site and more than one language. It is live.
Sister site
LanguagesENDEFRNLESITPL
ProductsDaily import←affiliate networks
StatusLive
Detail C5AI for the team
In use
C5

AI agents the team actually uses

16docs written for AI retrieval

Agents built on them answer what the docs already cover, so nobody is pulled away from their work.

How we did it
Problem
The operations team kept asking questions that were already answered somewhere in the documentation.
What we did
We wrote 16 engineering docs for AI retrieval and put agents on top of them: a Slack assistant, an agent that searches the wiki, and agents that draft newsletters and partner onboarding documents.
Outcome
Questions that are already documented get answered without pulling a person away from their work.
Knowledge · agents
Docs16written for AI retrieval
AgentsSlack assistantWiki searchNewslettersPartner onboarding
Detail C6Project management
In production
C6

Collab: one place for their team and ours

2,940tasks89% of them done

Their staff and our team plan, review and log every piece of work in it. In use within its first week, in October 2025.

How we did it
Problem
Their staff and our developers needed one place to plan work, review it and see what was delivered.
What we did
We built Collab on the platform their product already runs on, with our own extension: projects, epics, sprints, story points, tasks, reviews, approvals and work logs. Unplanned work gets story points too, so it shows in velocity. Their ambassador programme runs in it as well.
Outcome
By October 2026: 2,940 tasks, 2,604 of them done. 515 reviews, 300 of them code reviews, and 202 approvals. About 4,900 hours of work logged by 17 people across both teams.
Collab · Oct 2025 – Oct 2026
Reviews300 code129 content53 design
Approvals202
Planning48 projects61 epics29 sprints284 stories
People62from both companies
D–D
Also built

Everything else we have built for them.

Delivery dashboard
Built on Collab: their sprint delivery, live, with velocity, epic progress and work logs. Since May 2026.
Blog pipeline
AI research and drafting. A person reviews every post, and finished posts arrive as drafts in their CMS.
Ambassador portal
Where brand ambassadors apply and are evaluated, inside Collab: 733 ambassadors and 15 campaigns since April 2026.
Product images
Supplier photos of any size become storefront images, with AI deciding the crop. A proof of concept.
E–E
In their words
“When we started with Quvor, Shopping Event VIP was a Belgian site that had outgrown its tech. Today they run our whole platform: our Belgian site, our international sites and the back office behind them, for more than 200,000 members. A big part of our success is thanks to Quvor. They don’t just deliver and leave. They stay, they know our business, and they keep building with us.”
Domien Van Eynde · CMO, Shopping Event VIP
F–F
All work Next caseTribeCrafter