Client
Pottsalat GmbH
Unit
prodct [CX] · + /skills
Duration
3 months · 2022
Shape
Rollout · platform integration
Headline
Talon.One live across ordering and checkout — loyalty mechanics and dynamic pricing engineered to real order data.
// prodct [CX] case · Pottsalat · 2022 · food delivery · loyalty & pricing rollout

Margins under pressure.
Loyalty live in 12 weeks.

Pottsalat needed loyalty and promotional pricing that reacted to real order patterns — not the blunt instrument of universal discounts. We rolled out Talon.One end-to-end: integrated into the ordering flow, the checkout, and the customer record. Rules, rewards, and dynamic price logic live in one engine that marketing can actually operate.

12 wk
// kickoff → first live campaign
// delivery-first
1 engine
// Talon.One wired to ordering + checkout + CRM
// no shadow discount logic
Marketing-operable
// rules & rewards editable without engineering tickets
// handover complete
// 01 / the situation

Flat promotions. A real pricing problem.

Pottsalat's growth was outpacing its promotional toolset. Discounts were coarse — site-wide or none — and loyalty was a plan on paper. Margins were getting thinner with every blanket promo.

The goal was sharper: differentiated pricing and rewards tied to actual behaviour. Repeat orderers, lunch-window customers, specific baskets. All without a new CRM rebuild.

  • 01

    Blunt discounting eroded margin.

    Every promo was priced for the worst-case basket.

  • 02

    No loyalty mechanics in production.

    Tier logic, rewards, earn/burn — all on slides, none shipping.

  • 03

    Marketing blocked on engineering.

    Every new rule meant a release cycle.

// 02 / approach

One engine. Wired to real data.

We picked Talon.One as the promotion engine and committed to a proper integration — not a sidecar. Ordering flow, checkout, and customer record all post to Talon.One; Talon.One is the source of truth for which rewards apply.

In parallel, we built the operator surface: the rule templates, the campaign shapes, the guardrails so marketing ships without engineering escorts.

  • A

    Talon.One wired into live order events.

    Real baskets, real customers, real timing — rules fire on actual data, not synthetics.

  • B

    Rule templates for the mechanics Pottsalat actually uses.

    Tiered earn/burn, dynamic pricing, window-based offers, winback.

  • C

    Runbook for marketing, not engineering.

    New rules, new campaigns, new segments — editable in the engine's own console.

// 03 / what we built

Four integrations. One operating surface.

[Integration]
Ordering flow → Talon.One
Basket and user context post to Talon.One at cart-update time; applicable rewards come back as line-level adjustments.
[Integration]
Checkout → Talon.One
Final price reconciliation — no discount drift between cart and confirmation.
[Integration]
CRM ↔ Talon.One
Profile attributes and earn/burn ledger mirrored both ways, so loyalty state matches customer state.
[Surface]
Marketing runbook + rule templates
Pre-baked campaign shapes, QA guardrails, change log. Marketing ships without an engineering ticket.
// 04 / outcomes

Live. Operated by the team that owns it.

12 wk
// from kickoff to first live campaign
// on plan
1 engine
// loyalty + promo + dynamic pricing in Talon.One
// no parallel logic
0 release cycles
// needed for a new rule or campaign post-launch
// marketing-operable
Handover clean
// runbook, templates, training shipped with launch
// team owns it
// similar engagement?

Promotion logic stuck in release cycles? We fix that.