Markin + Shopify
Orders, catalogue and margin as decision inputs.
Optimising for conversion alone reliably grows unprofitable orders. With margin in the input, Markin can decline a discount that would have converted and still lost money.
Read onlyTriggered event
What Markin reads
- Order and refund history
- Catalogue, price and margin
- Cart and checkout events
What Markin writes back
- Decision events for downstream lifecycle tools
How the connection works
| Pattern | What it means here |
|---|---|
| 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. |
Shopify questions
- How does Markin connect to Shopify?
- Read only, Triggered event. Markin reads signal from this system. Nothing is written back and no schema is changed.
- What does Markin read from Shopify?
- Order and refund history; Catalogue, price and margin; Cart and checkout events.
- What does Markin write back into Shopify?
- Decision events for downstream lifecycle tools
- 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.