What does this integration do?
Under Turkish law No. 6563, every business sending commercial messages by SMS, email or phone must manage consent through İYS. In this integration, marketing consents collected in Shopify are written to İYS, and opt-outs recorded in İYS are written back to the store. That way no gap opens between the two systems, and the risk of messaging without consent disappears.
The data it synchronises
Sending consent records
Writing opt-outs back
Bulk consent upload
Consent per channel (SMS / email / phone)
Consent lookup before sending
Compliance reporting and logs
How the data flows
01
Consent is collected
Consent is captured per channel at touchpoints such as registration, checkout and back-in-stock alerts. Boxes are unticked by default and channels are kept separate.
02
The record is written to İYS
The consent is submitted to İYS with date, time, channel and source. The burden of proving consent sits with the store.
03
Opt-outs are read back
Opt-outs recorded in İYS are written back to the store and to your email tool. An opt-out always overrides a consent.
04
Lookup before sending
Consent status is checked before every commercial send, and sending to a number without consent is blocked.
05
Compliance record
Every action is logged; at audit, the gap between the two systems is expected to be close to zero.
What we watch for in this integration
One-way integrations accumulate risk over time; writing opt-outs back is essential
SMS, email and phone consents cannot be combined into a single checkbox
Wholesale and business buyers are in scope too; the trader exemption is assessed separately
Purchased lists, or lists of unclear origin, are never uploaded to the system
The consent gap between the two systems is reported regularly; as it grows, so does both the legal risk and the damage to customer experience
The setup process
01
Data and permission analysis
We decide which data flows in which direction, which system is the master, and what API permissions are required.
02
Mapping table
Product, variant, category, warehouse and account fields are mapped between the two systems, one by one.
03
Development and testing
The integration is built on a development store; order, return and error scenarios are tested with real data.
04
Going live
It is released through a controlled switchover, watched closely for the first few days, with the error queue monitored.
05
Monitoring and maintenance
Logging, error alerting and API version updates continue under the maintenance retainer.
What we need from you before we start
Your İYS brand registration and login details
The source and format of your existing consented list
The SMS and email tools you use
A list of the touchpoints where consent is collected