Agiled Docs
Commerce

Create a Checkout Link

Build a focused payment link for one or more products or services.

Checkout links are public payment pages for a specific product, service, package, deposit, or bundle.

Create a checkout link when you want one focused customer action: buy this offer or submit this payment.

Use a checkout link for a direct offer. Use a storefront when customers should browse multiple offers, compare options, or choose quantities across a catalog.

  1. Open Commerce > Checkout Links.
  2. Select New Checkout Link.
  3. Enter the link Name.
  4. Choose Single Product or Multiple Products.
  5. Set the Currency.
  6. Select the product or service.
  7. Set the default quantity.
  8. Add a price override only when this link should use a special price.
  9. Restrict accepted payment methods if needed.
  10. Add custom intake fields if you need extra customer information.
  11. Add a success message or redirect URL.
  12. Set max uses or an expiration date if the offer is limited.
  13. Keep Active on when the link is ready to share.
  14. Turn on Auto-generate Invoice when paid checkout should create an invoice.
  15. Save the checkout link.

Single vs. Multiple Products

Use Single Product for a simple offer. Use Multiple Products for bundles, multi-item packages, or checkout pages where the customer buys several items together.

Keep the choice simple. If customers need to browse several unrelated offers, a storefront is usually better.

Use one checkout link per clear offer. If the same product is sold to different audiences, campaigns, or price points, create separate links so reporting, limits, and cleanup stay understandable.

Price Override

Use a price override for campaign pricing, deposits, negotiated packages, or limited offers. Leave it empty when the link should use the catalog price.

Price overrides should be reviewed before every campaign. They can make the checkout total differ from the product catalog.

Write down why the override exists in the link name, campaign notes, or internal handoff. This helps finance understand why an order or invoice does not match the catalog price later.

Intake Fields

Add custom intake fields when fulfillment needs information that payment alone does not capture. Common examples include company name, preferred date, project brief, delivery address, tax details, or onboarding notes.

Keep intake fields short and required only when necessary. Long checkout forms can reduce completion, and vague fields create orders that still need manual follow-up.

Before Sharing

Open the public checkout link in a private browser window. Confirm product, quantity, price, tax, payment method, required fields, success behavior, expiration, max uses, and invoice generation.

Complete one safe test order before sharing the link publicly. After checkout, open the order in Agiled and confirm customer details, custom-field answers, payment status, generated invoice, confirmation email, and any workflow or notification.

If you use a redirect URL, test that the customer lands on the expected page after payment. If the page is hosted outside Agiled, confirm it does not expose private order or customer details.

Deactivate old links when campaigns end, prices change, products are retired, or fulfillment instructions change. Update website buttons, proposal links, email templates, and saved documents when replacing a checkout link.

Review active checkout links monthly when prices or offers change often. A stale link can continue accepting the wrong price even when the product catalog has been updated.

On this page