Public Storefront Flow
Let customers browse products and start checkout from a storefront.
Public storefronts let customers browse products or services and start checkout without workspace access.
Use storefronts when browsing matters. Use checkout links when the customer should pay for one specific offer without comparing options.
Customer Flow
- Open the storefront link.
- Search or browse products.
- Select products or services.
- Start checkout.
- Complete payment or order details.
- View the success page.
Customers do not need an Agiled login to use a public storefront. The storefront should make the product name, description, price, quantity, and checkout action clear enough that the customer can complete the order without contacting your team.
If customers regularly ask what to buy, review product names, descriptions, images, categories, and whether a checkout link would be clearer than a full storefront for that offer.
Storefront Search and Pages
Storefront links support search and page navigation. Customers can use search to find products faster when the storefront contains many items.
Keep product names and descriptions consistent so search works well. If a storefront has many similar products, use categories, clear naming, and product images to help customers choose the right item.
Avoid publishing internal-only or test products. Any active product shown in the storefront can become part of a real customer order.
Before Sharing
Confirm products, prices, images, descriptions, taxes, payment settings, and success behavior before publishing the storefront link.
Also test:
- The storefront opens in a private browser window.
- Search returns the products customers expect.
- Product images and descriptions are readable on mobile.
- Checkout requires the right customer fields.
- Payment or offline order instructions match your finance setup.
- The success page appears after the order is submitted.
After An Order Is Placed
Review the order in Commerce, confirm customer details, and check whether an invoice or payment record was created. If fulfillment depends on stock, availability, or manual approval, keep the order in the right status until your team completes that review.
First Storefront Order Test
Before sending traffic to a storefront, place one low-risk test order through the same public link customers will use. Confirm product selection, quantity, tax, checkout fields, payment or offline instructions, success page, order record, invoice behavior, and fulfillment owner.
If the test order exposes confusing product copy or missing fulfillment data, fix the storefront before promoting the link.
Fulfillment Handoff
After the first real storefront order, confirm who owns fulfillment, what status the order should use, whether an invoice was generated, and whether custom checkout answers are copied to the task, project, or customer record used by the team.
Troubleshoot Customer Issues
If a customer cannot complete the storefront flow, confirm that the storefront is active, the product is active, checkout is enabled, required fields are not blocking submission, and the payment gateway is connected when online payment is required.
Collect the exact storefront URL, product selected, checkout step, browser, timestamp, and payment provider status when troubleshooting a customer issue.
If the product is visible but checkout fails, check product status, price, currency, required fields, and gateway configuration before changing storefront copy.
Post-Order Review
After the first real order:
- Confirm the order status.
- Confirm payment status.
- Check generated invoice behavior.
- Review custom answers and customer details.
- Assign fulfillment work if automation did not.
- Fix storefront or checkout setup before sending more traffic.