Use cases
These guides show how to combine the ShopiMind API, custom data and their relations to solve concrete marketing automation and e-commerce problems.
Each case follows the same structure:
- The business need — the concrete problem.
- The ShopiMind solution — the architecture used (definitions, relations, overrides).
- The data model — schema of the objects and their relations.
- Implementation — step by step, with API call examples.
- Going further — variants, optimizations, edge cases.
Available cases
| Case | Who for | Key benefit |
|---|---|---|
| Veterinary pricing | Pet shop, B2B referenced via prescribers | Each customer sees the price negotiated by their vet across all ShopiMind marketing content: post-purchase and recommendation emails, abandoned cart recovery, popins, smart content. |
| Dedicated account manager | B2B, key accounts | Segmentation by manager, bulk campaigns targeting their portfolio, personalized signature in messages. |
More use cases coming
Custom data (with relations + overrides) is a generic mechanism. Any business object that can be modeled in JSON can fit into a ShopiMind scenario. If you have a use case that doesn't match the ones listed above, contact your ShopiMind representative — it's likely achievable with the building blocks described in Custom data.
Limits to know
- The price override currently covers only the
products.priceandproducts.price_discountfields (three priority sources max per field).