---
title: Markin + PrestaShop
url: https://markin.ai/integrations/prestashop
category: Commerce, billing and subscriptions
description: Connect Markin to PrestaShop: use customers, orders, carts, catalogue and stock to choose and measure each shopper's next profitable action.
---

# Markin + PrestaShop

> Commerce context in, profitable customer decisions out.

**Job:** Turn PrestaShop commerce data into the next profitable customer action.

A Markin and PrestaShop setup reads customers, orders, carts, catalogue and stock to decide the next profitable action for each shopper, then activates it through the channels and storefront you already run.

PrestaShop contains the commercial context a growth decision needs: what someone bought, what they abandoned, what is available and what margin remains. Markin turns that context into a ranked action and measures whether it created incremental revenue.

## What can you ask Markin to do in PrestaShop?

- How do I increase repeat purchase revenue in PrestaShop?
- How do I use PrestaShop data for next best action?
- How do I reduce discount waste in PrestaShop?
- How do I measure incremental revenue from PrestaShop offers?

## What Markin does in PrestaShop

- Read customers, addresses and consent state.
- Read orders, line items, discounts and refunds.
- Read carts and abandoned checkout context.
- Read catalogue, price and stock availability.
- Identify repeat-purchase, cross-sell and win-back opportunities.
- Choose the next action with margin and inventory constraints applied.
- Write the decision back for activation through CRM or the storefront.
- Keep a randomised holdout to measure incremental revenue and margin.

## The growth work behind PrestaShop

### Read the estate

- Read consent, subscription and channel eligibility state before anything else.
- Read contact history so past sends count as pressure on the customer.

### Find where revenue is leaking

- Spot onboarding steps where activation falls off and revenue never starts.
- Spot pricing and packaging mismatch between what people buy and what they use.

### Explain why

- Rank drivers by how much of the movement each one accounts for.
- Check whether the same driver is present in comparable segments.

### Write hypotheses worth funding

- Rank the portfolio by expected value, not by seniority.
- Drop hypotheses that a past experiment already answered.

### Decide per customer

- Choose the next best action for each customer, for each moment.
- Arbitrate between every action competing for that same customer.

### Execute in the tools you already run

- Leave the estate exactly as it was if Markin stops writing.
- Write decisions into the CRM, engagement and warehouse systems already in production.

### Prove it caused the revenue

- Stop an experiment early when the evidence is conclusive either way.
- Refuse to call a result that has not cleared the evidence standard.

### Retire, govern and hand over

- Re-test assumptions that decay, such as price sensitivity and seasonality.
- Log every read, decision and write with its reason for audit.

Full catalogue: [Everything a growth team does, running every day.](https://markin.ai/growth-work)

## Activation patterns

- **Read only.** Markin reads signal from this system. Nothing is written back and no schema is changed.
- **Triggered event.** Markin emits an event that starts or advances a journey. Near-immediate, and the channel keeps its own governance.
- **Decision API.** The surface asks Markin for a decision at render time and receives one action plus its reason, with a defined fallback.

## What Markin reads from PrestaShop

- Customers, addresses and consent state
- Orders, carts, discounts and refunds
- Catalogue, prices and stock availability

## What Markin writes back

- Customer-level decisions for CRM activation
- Offer or recommendation decisions for storefront surfaces

## Used together with

- [klaviyo](https://markin.ai/integrations/klaviyo)
- [stripe](https://markin.ai/integrations/stripe)
- [google-ads](https://markin.ai/integrations/google-ads)
- [meta-ads](https://markin.ai/integrations/meta-ads)
- [segment](https://markin.ai/integrations/segment)
- [snowflake](https://markin.ai/integrations/snowflake)

## Related

- [Solution: revenue-expansion](https://markin.ai/solutions/revenue-expansion)
- [Solution: lifecycle-automation](https://markin.ai/solutions/lifecycle-automation)

## FAQ

**How does Markin connect to PrestaShop?**

Read only, Triggered event, Decision API. Markin reads signal from this system. Nothing is written back and no schema is changed.

**What does Markin read from PrestaShop?**

Customers, addresses and consent state; Orders, carts, discounts and refunds; Catalogue, prices and stock availability.

**What does Markin write back into PrestaShop?**

Customer-level decisions for CRM activation Offer or recommendation decisions for storefront surfaces

**Do we have to move our data to Markin?**

No. Markin reads from your warehouse, product events and operational systems in place, on your compute, under the access rules your data team already set. Nothing is copied into a separate customer base and there is no vendor-side profile store to migrate off later.

**Does Markin replace our engagement platform or CDP?**

No, and it should not. Your engagement platform keeps the channel, the templates, the deliverability and the governance. Your CDP keeps identity and consent. Markin adds the layer neither has: deciding which action deserves to exist for each customer, and proving it against a holdout.

**What if the system we use is not listed?**

The four activation patterns cover almost everything: attribute write-back, triggered event, decision API and direct surface rendering. Any system that exposes an API, accepts a table, or can read a warehouse column can receive decisions. New connectors are built during deployment, typically in days.

Source: https://markin.ai/integrations/prestashop