Skip to content
Author How-tos

Add terms and conditions to checkout

Publish agreement documents and link them from the checkbox labels shoppers see at checkout. Work with your administrator and developer to confirm how your storefront defines its agreements before changing their configuration.

  • Obtain approved agreement text and the languages or store views that need it.
  • Check that you can author and publish documents and update the storefront’s placeholders sheet.
  • Ask your developer whether the storefront uses its default agreement, custom agreements, or Admin-managed Commerce agreements, and which Admin settings apply.

Confirm the applicable Admin configuration with your developer, publish the agreement documents, and update the labels for the agreement source your storefront uses.

If your developer confirms that your checkout requires the Commerce Admin setting, ask an administrator to enable it as follows:

  1. Log in to the Admin Panel.

  2. On the Admin sidebar, go to Stores > Settings > Configuration.

  3. In the left panel, expand Sales and choose Checkout.

  4. Expand the Checkout Options section.

  5. Set Enable Terms and Conditions to “Yes”.

  6. Click Save Config.

See Terms and conditions for checkout documentation for more information on how to enable the terms and conditions using the Admin Panel.

For agreement labels that link to storefront documents, create the content in Document Authoring:

  1. Create an agreement document at the intended path, such as /terms-and-conditions or a locale-specific path.
  2. Add the approved agreement text and any required links.
  3. Preview and publish the document.
  4. Open its published URL and confirm that shoppers can read it without an authoring login. Keep this URL for the checkbox label.

Use the EDS placeholders or the Admin Panel instructions in the following tabs to configure the agreement checkbox label.

For the default storefront agreement, update the placeholders sheet using the existing label key and the following information. For additional agreements, ask your developer which label keys their configuration uses.

  • An identifier: It’s the reference that identifies the label translated
  • A label: The text displayed next to the checkbox comes from the storefront placeholders for the shopper’s language. It accepts HTML links to your published agreement documents.

Similarly, the merchant can configure the translation for the validation error that appears when the user clicks the Place Order button and an agreement is not checked, using the “Checkout.TermsAndConditions.error” identifier.

Sample of placeholders sheet:

"Checkout.TermsAndConditions.label", "I have read, understand, and accept the <a href='/en/privacy-policy' target='_blank'>Terms of Use, Terms of Sales, Privacy Policy, and Return Policy</a>."
"Checkout.TermsAndConditions.error", "Please accept the Terms and Conditions to continue."

Replace the example wording with approved text and the example link with the published URL of your agreement document. Follow Change labels and placeholders to preview and publish the updated sheet.

These labels are used to render the TermsAndConditions container in the commerce-checkout.js block file.

Refer to the Adobe Commerce documentation for examples on how to use these labels.

Preview checkout for each affected store view. Confirm that the intended agreement appears, its links open the published documents, and any required manual acceptance is enforced before an order can be placed. Use your team’s test-order process rather than placing an unintended live order.