Create a Storefront or Checkout Link

Use storefronts for a small catalog and checkout links for a focused one-page purchase flow.

Choose storefronts when customers need to browse. Choose checkout links when you want to send one specific offer, package, deposit, or payment page.

Start with the buying experience you want the customer to have. If the customer should compare products, use a storefront. If they should pay for one agreed offer, use a checkout link.

Storefront Steps

1. Create products or services in the product catalog.
2. Open Commerce > Storefronts.
3. Create a storefront.
4. Add products.
5. Configure storefront details and sharing options.
6. Open the public storefront and place a safe test order.
7. Review the order in Agiled.

Use a storefront when the customer should compare options. Keep the product list small enough that the customer can decide without asking for clarification.

Before sharing a storefront, review every visible product as a customer. Check names, images, descriptions, prices, tax behavior, and whether inactive or internal-only products are hidden.

If a storefront includes services, make sure descriptions explain what happens after purchase. Customers should know whether they receive a booking link, onboarding form, project kickoff, file delivery, or manual follow-up.

Checkout Link Steps

1. Create or choose a product or service.
2. Open Commerce > Checkout Links.
3. Create a checkout link.
4. Configure products, limits, expiration, fields, and payment options.
5. Share the checkout link.
6. Review submitted orders.

Use a checkout link when the customer should complete one specific purchase, deposit, or package. Review price overrides and limits carefully because links are often shared in emails, proposals, and campaigns.

Name checkout links by campaign, offer, or customer segment so the team can find and retire them later. If a link is temporary, set an expiration or usage limit instead of relying on manual cleanup.

Before Sharing

Check product status, prices, tax behavior, checkout fields, usage limits, expiration, payment gateway, confirmation behavior, and order notifications. Open the public page in a private browser window and complete a safe test order.

If the checkout asks custom questions, confirm each answer appears in the order review where fulfillment or finance can see it. Required custom fields should be reserved for information the team truly needs before accepting payment.

After Orders Arrive

Review the order, customer details, payment status, and any invoice created from the order. If fulfillment is manual, keep the order status current so the team knows what still needs work.

Compare Agiled order status with the payment provider when a customer reports a payment issue. Do not fulfill or resend invoices based only on a customer screenshot.

After the first live order, review the order, payment, invoice, customer email, and any workflow actions. Fix the product, checkout link, gateway, or workflow before sharing the page more widely if any part of the handoff is wrong.

Common Launch Mistakes

• Sharing a page before payment gateways are tested.
• Leaving internal-only products visible.
• Using old campaign prices.
• Forgetting required intake fields for fulfillment.
• Not checking whether invoices or workflows are created after payment.

Related Docs

• Storefronts
• Create a Storefront
• Checkout Links
• Orders