Marketplace Integrations and Automated Actions Supplementary Terms

1. Scope and connection authority

1.1. These terms are an annex to the Terms of Use between the Company that provides the Riseluc service and the User; on marketplace connections and Automated Actions they take precedence over the Terms of Use. An "Automated Action" is any write request Riseluc sends to the marketplace on the User's behalf (price, stock, content, answer, order action).

1.2. When you connect a store, you authorise the Company to connect to the marketplace's official integration interface (API) on behalf of that store. You must own the store or have the owner's permission to grant this authority.

1.3. Access credentials are encrypted with AES-256-GCM before they are written to the database and are used only for the work described in these terms. On Amazon you never enter a password; you grant access on Amazon's consent page. You can withdraw the authority at any time by deleting the store in the Riseluc dashboard, or by regenerating the key, changing the password or removing the app's access in the marketplace's panel.

1.4. Requests to Trendyol are sent with Trendyol's mandatory integrator identity ("Verimle", the brand's former name); price and stock updates to n11 are sent with the integrator name "Riseluc".

2. Data read

2.1. Product and catalogue, order, finance and reconciliation, return, shipping and customer question data are read through the connection. Which feature is available on which marketplace is shown on the Marketplace coverage page.

2.2. Buyer data is kept to a minimum: the name, address and contact details of Amazon buyers are never stored; shipping records are written with buyer details removed; shipping labels and invoice files are passed through and not stored in Riseluc. The processing of personal data is governed by the Data Processing Agreement.

• Marketplace coverage
• Data Processing Agreement

3. Automated Actions

The Company sends only the actions below to your store, and only when you turn on the relevant feature or approve the action.

• Margin-protected repricing: Trendyol, Amazon, eMAG, Hepsiburada (not available on n11). How it starts: off by default; you turn on the store rule and the per-product switch. You set the minimum profit amount or rate; repricing never writes a price below the floor price calculated from your cost and rule, and leaves products whose floor cannot be calculated untouched. Starter plan and above.
• Automatic stock updates: all five marketplaces. How it starts: off by default in each store; no stock is written until you turn it on. On eMAG it writes only to single-warehouse offers.
• Shared stock pool: across your stores. How it starts: off by default, you turn it on; a product with the same barcode counts as one stock, and a sale on one channel is also deducted from the stock in your other stores. It reaches the marketplace through each store's automatic stock update switch. Pro plan and above.
• Stock sync from a supplier XML feed: Pro plan and above. How it starts: off by default for each feed; you preview first, and when you approve, only the central stock in Riseluc is updated. It reaches the marketplace through each store's automatic stock update switch.
• Bulk price and stock editing: all five marketplaces. How it starts: changes are previewed before they are sent and you approve them; on n11, prices are written only this way. Starter plan and above.
• Product title, description and attributes: title and description on Trendyol and Amazon, attributes on Trendyol only. How it starts: with your approval for each submission.
• Product images (photo studio): Trendyol and Amazon. How it starts: you send them in the approval window; on Trendyol the gallery as it was before sending is saved and can be restored.
• Product video: Trendyol only. How it starts: when you choose "Upload to Trendyol".
• Answers to customer questions: Trendyol, Hepsiburada, n11. How it starts: an answer goes out only when you send it; AI only prepares a draft.
• Order actions: on Trendyol, status updates, sending the invoice and getting the shipping label; on eMAG, confirming the order and moving it to Prepared, sending the invoice link and creating the AWB (shipping label). How it starts: each one at your request.
• Cross-border export: on Trendyol and Amazon, price and stock only for a listing that already exists in the target store; on eMAG, an offer on a product already in the eMAG catalogue (Starter plan and above; 25, 200 or unlimited products depending on the plan). How it starts: with your approval for each submission; stock is transferred once.
• eMAG product draft: eMAG only, Pro plan and above. How it starts: for a product not in the eMAG catalogue, the name and description are translated with AI into eMAG's language and a draft that is not active and not on sale is opened on eMAG; eMAG does not start reviewing the product until you complete its category and attributes in the eMAG panel.
• Shipping desi dispute and deduction dispute: Trendyol only. How it starts: Riseluc only prepares a draft; you send the dispute to Trendyol and Trendyol decides the outcome. The amount in the draft is an estimated upper bound.
• Lucy; the price, stock, content, cost and question answer changes it suggests are written only when you press "Apply" on the approval card.

4. Repricing and responsibility

4.1. The lower limit of repricing is set by your cost and your minimum profit rule; the final price decision is yours. The Company is not responsible for the price at which products sell, whether the Buybox is won or the number of units sold.

4.2. How often repricing runs and how many prices it writes per day are not committed; a daily write limit is applied to prevent runaway writes. On Hepsiburada and n11, price writes are processed later on the marketplace side; the actual price appears at the next catalogue sync. On eMAG, repricing waits on an offer whose price has not yet been approved.

4.3. Monitoring your sales, stock levels and the warnings the marketplace sends you is your responsibility. A wrong price or overselling (selling a product that is out of stock) can lead the marketplace to restrict your store or apply penalties.

4.4. If, because of its own software error, the Company writes a price below the floor price calculated from your rule, or a value you did not turn on or approve, it is liable for your resulting direct loss within the limitation of liability in the Terms of Use. When the Company notices such an error, it stops the related writes and informs the affected User without undue delay.

5. Marketplace rules and changes

5.1. Complying with the marketplace's seller agreement and its price and campaign rules is your responsibility. Using a Riseluc feature does not mean you are acting in line with those rules.

5.2. Marketplaces may change or close their integration interfaces without notice. A feature may then stop working for a while; the Company informs the affected Users and, if necessary, pauses writes until it is safe. The Company is not liable for losses arising from a marketplace's change.

5.3. The Amazon, Hepsiburada and n11 connections were built to the marketplaces' official API documentation and have not yet been verified on a live seller account. On eMAG, reading works; the flows that write to eMAG (price, stock, offers, drafts and order actions) have not yet been tried on a live eMAG account. Stock sync from supplier XML has not yet run on a live account either. On eMAG, Hepsiburada and n11, profit is marked as "estimated".

6. Amazon-specific provisions

When using the Amazon Selling Partner API, the Company must comply with Amazon's Data Protection Policy and Acceptable Use Policy. Accordingly:

• The name, address, email and tax details of Amazon buyers are not stored in Riseluc and are not sent to AI.
• Data received from Amazon is not sold, is not used for advertising and is not included in category comparison statistics.
• A security incident affecting Amazon data is reported to Amazon (security@amazon.com) within 24 hours of detection, and the affected User is informed without undue delay and in any case within 48 hours.
• When you delete your Amazon store in the Riseluc dashboard, that store's Amazon refresh token and the product, order and finance records received from Amazon are deleted; the sales summary of sold products (no buyer information) is deleted automatically after 30 days. Removing the app's access in Amazon Seller Central cuts off Riseluc's access; to have the records in Riseluc deleted, also delete the store in the Riseluc dashboard.
• Amazon may audit the Company's handling of Amazon data under its developer terms.

7. Public pages and category comparison

7.1. Information such as product reviews, store ratings and search results is read from the marketplaces' public pages through a data collection service provider. This data may be delayed or incomplete.

7.2. Category comparison is shown only for categories researched by at least 5 different Users and containing at least 20 products; a category that falls below the threshold is removed. This way no single User's research or data is revealed.

8. Relationship with marketplaces

The Company has no partnership, dealership or agency relationship with Trendyol, Hepsiburada, n11, Amazon or eMAG; these marketplaces do not approve or endorse Riseluc. Their names and logos are their owners' trademarks.

9. End of the connection

When you delete a store in the Riseluc dashboard, its access credentials and its product, order and finance records are deleted, and Automated Actions stop. The sales summary kept for a deleted store's sold products is deleted automatically after 30 days; other retention periods are in the Retention Period section of the KVKK Privacy Notice.

• KVKK Privacy Notice