# How to edit your legal agreements

> Customise the distance sales, pre-contractual, membership and KVKK texts, publish versions, and see exactly who accepted which version and when.

Canonical page: https://magazamhazir.com/es/yardim/yasal-sozlesmeler
Menu path in the store admin: Ayarlar > Yasal Sözleşmeler
Requires plugin(s): ai-features
Last updated: 2026-09-01

Your store runs on four legal texts: the Distance Sales Agreement, the Pre-Contractual Information Form, the Membership Agreement and the KVKK Privacy Notice. All four ship ready to use. To change one you edit it and publish a new version — and the system records which version each customer accepted and when, which is precisely what you need in a dispute.

## Antes de empezar

- A panel account that can see the settings
- Your company's legal name, address, tax details and contact information
- Legal advice, if you are making substantive changes to the wording

## Pasos

### 1. Open the agreements list {#adim-1}

Settings > Legal Agreements lists the four texts. Each row shows whether it is Default or Customized and when it was Last updated. If you have never touched them they all read Default — which does not mean they are inactive: the default texts are live and customers accept them.

### 2. Fill in your company details first {#adim-2}

The texts pull your company details in through variables: Full legal company name, Company address (for legal notices), Tax office, Tax identification number, MERSİS number, Trade registry number, KEP address and your contact details. Anything you have not filled in renders blank in the agreement — the panel flags what is missing and links you straight to the form.

### 3. Edit the text {#adim-3}

Open an agreement and click Edit. You write in the Agreement Markdown field and Preview on the right shows the result. The Variables list holds the fields you can use; Click to insert drops one in at the cursor. The variables currently in use are highlighted too, so you notice if you delete one by accident.

### 4. Let AI help with the wording {#adim-4}

If you would rather not write from scratch, use the AI Agreement Assistant: describe what you want and the assistant rewrites the agreement. It shows the available variables too, so what it produces pulls your company details from the right place. You still read and save the result yourself — the assistant does not publish anything.

### 5. Publish a new version {#adim-5}

Saving updates the text; what changes the official text shown to customers is Publish new version, and the panel asks you to confirm. The Version history table lists each version with its Version, Status, Published date and Acceptances; status is Published, Draft or Archived. A content hash is kept per version, so it can be proven the text did not change afterwards.

### 6. Audit the acceptance records {#adim-6}

View acceptances on a version opens the audit list of the customers who accepted it. Each row carries the Customer, Version, Context, Order, Accepted at and IP. You can search by email or name and open the related order directly. In a dispute, this is the record that shows who accepted what and when.

## Consejos

### Missing company details make an incomplete agreement

Even with the text finished, an empty field such as MERSİS or KEP renders blank in the agreement, and the panel warns you in advance. Close the gaps in the Store Information list before you start editing the wording.

### Preview before publishing

A mistake in the Markdown or a deleted variable only shows up in Preview. Publish new version turns that text into the official one customers accept — look at it first.

### Versions are what preserve the history

Publishing a new version does not delete the old one, it archives it — and the customers who accepted the old version stay tied to that version. That is why publishing a version, rather than editing the text in place, is the only auditable route.

## Preguntas frecuentes

### If I never edit them, do I effectively have no agreements?

No. All four texts are live in their default form and customers accept them. Default in the list means you have not changed it, not that it is inactive.

### What is the difference between Save and Publish new version?

Save updates the text. Publish new version makes that text the official one shown to customers and adds a row to the version history. Because acceptance records are tied to versions, a substantive change needs publishing.

### I broke the text — can I get it back?

Reset to default restores the factory template, and the panel asks you to confirm first. You can also view an older version from the version history and reuse its content.

### Why is the IP kept in the acceptance records?

It is part of the evidence that a customer accepted the agreement: who accepted which version, in which context, when and from what address. A content hash is kept per version too, so it can be shown the accepted text did not change afterwards.