Public Checkout Flow
Understand what customers see when they use a storefront or checkout link.
The public checkout flow is the customer-facing path for storefront and checkout link purchases.
Test it the same way a customer will use it, outside your signed-in workspace.
Use a private browser window for testing so your signed-in session does not hide public-page problems.
Run this test before campaigns, website updates, launches, and pricing changes. Public checkout issues are easier to fix before traffic arrives.
Also retest after changing payment gateways, product prices, tax rules, checkout fields, redirects, custom domains, or invoice generation settings.
What Customers Do
Customers open the public link, review the product or service, enter required customer information, answer any custom intake fields, choose an available payment method, and complete checkout.
If a custom field affects fulfillment, make it clear and required. If it is only nice to have, avoid blocking checkout with it.
Customer Information
Checkout collects required customer details such as name and email. Storefronts can also collect phone when configured as optional.
Review customer details on the resulting order before fulfillment or invoicing.
If customer information is incomplete, fix the checkout fields before sending more traffic to the link.
If the buyer enters the wrong email, correct the resulting order or customer record before sending receipts, invoices, or fulfillment messages.
After Payment
After successful checkout, the customer sees the configured success message or is sent to the configured redirect URL. If invoice generation is enabled, Agiled creates the invoice after payment is completed.
If the customer is redirected away from Agiled, confirm the redirect page still explains what happens next.
If the redirect points to your website, test it after website deployments too. Checkout can succeed while the external success page becomes stale.
Test Before Sharing
Before sharing a live public link, check:
- The product or service is correct.
- The price, currency, tax, and quantity are correct.
- The payment methods are available.
- Required custom fields make sense.
- The success message or redirect URL is correct.
- The order appears in Commerce > Orders after checkout.
Also confirm the customer receives expected confirmation, the payment appears in the provider dashboard, and any generated invoice has the correct line items.
After Checkout
Review the order, payment status, customer details, generated invoice, and any workflow or fulfillment task. Fix the source storefront or checkout link before sending more traffic if anything looks wrong.
Troubleshooting
If payment methods do not appear, check gateway setup, currency support, product price, and workspace payment settings.
If the order is created but fulfillment does not happen, check workflow runs and the order status.
If payment succeeds in the provider but the order does not update, collect the provider transaction ID, customer email, checkout link, and order timestamp.
Handoff To Fulfillment
After checkout, confirm who owns delivery. A successful payment should lead to the next operational step: order processing, project creation, booking, file delivery, onboarding, or a manual task.
If no workflow creates that step automatically, assign it from the order review so paid purchases do not sit unfulfilled.
First Paid Order Review
For the first real paid checkout, compare the public success page, order record, invoice behavior, payment record, gateway transaction, customer email, and fulfillment status. Do this before sending more traffic to the link.
If payment succeeds but fulfillment context is missing, fix custom fields, order review, or workflow handoff before promoting the checkout link.