Storefront

Storefront covers Shop by Antly public commerce: merchant onboarding, shops, listings, carts, checkout, orders, shipping, inventory, and payments. Use this page when you are setting up the product surface, reviewing a rollout, or troubleshooting why users see a different result from an administrator.

What this surface is

• Primary purpose: Shop by Antly public commerce: merchant onboarding, shops, listings, carts, checkout, orders, shipping, inventory, and payments.
• Where users start: Shop onboarding routes include /onboarding/signup, /onboarding/activate-account, /onboarding/create-shop, and /onboarding/select-plan.
• Where administrators configure it: The shopbyantly app appears on launchpad when enabled; product and stock setup usually connects to Inventory and Billing.
• Runtime/detail surface: Customers use public catalogue and checkout surfaces while staff manage orders and fulfilment in the tenant.
• Platform connections: Storefront connects inventory variants, product listings, order workflows, payment providers, webhooks, and customer support.

Where it lives

Area	Path or surface	Use it for
User surface	Shop onboarding routes include /onboarding/signup, /onboarding/activate-account, /onboarding/create-shop, and /onboarding/select-plan.	Day-to-day work and review.
Configuration	The shopbyantly app appears on launchpad when enabled; product and stock setup usually connects to Inventory and Billing.	Setup, permissions, routing, labels, and behaviour.
Runtime/detail	Customers use public catalogue and checkout surfaces while staff manage orders and fulfilment in the tenant.	Testing the live experience users actually see.

Configure it

1. Confirm the audience for this surface and whether they are staff users, portal users, customers, public visitors, or administrators.
2. Open the owning product route: Shop onboarding routes include /onboarding/signup, /onboarding/activate-account, /onboarding/create-shop, and /onboarding/select-plan.
3. Review the configuration route and permissions before changing live behaviour: The shopbyantly app appears on launchpad when enabled; product and stock setup usually connects to Inventory and Billing.
4. Define the primary records, fields, statuses, owners, and notifications involved in this workflow.
5. Configure Shop profile, Product listing, and Cart/checkout first because they shape the rest of the rollout.
6. Add Payment provider and Order workflow only after the core path works with sample data.
7. Test the runtime surface as a restricted user, not only as a superadmin: Customers use public catalogue and checkout surfaces while staff manage orders and fulfilment in the tenant.
8. Check downstream connections after saving: Storefront connects inventory variants, product listings, order workflows, payment providers, webhooks, and customer support.
9. Record the owner, rollout date, and support path for the configuration.
10. Review the first week of activity and remove any option that users do not understand or need.

Configuration options

Option	Use when	Notes
Shop profile	The public store needs identity and branding	Configure during merchant setup.
Product listing	A product should be sold online	Connect inventory variants, price, and images.
Cart/checkout	Customers should purchase	Test tax, shipping, and payment provider behaviour.
Payment provider	Money should be collected online	Pair with Paystack, Flutterwave, Anchor, or configured provider.
Order workflow	Staff need fulfilment steps	Use tasks, tickets, or shop operations.
Inventory sync	Stock should stay accurate	Pair with Inventory module.

Operating notes

• Keep labels aligned with the words users see in the product, especially Shop profile and Product listing.
• Permissions still matter even when a menu, page, or link is visible.
• If users see empty data, check role filters, enabled apps, ownership rules, and saved filters before editing records.
• If a change affects customers or public visitors, test from a logged-out or customer account as appropriate.
• Use reports or logs to confirm the change produced the expected operational result.
• Capture configuration decisions in rollout notes so support teams know what changed.
• Do not reuse one option for unrelated processes just because it is already configured.
• Review linked notifications, workflows, dashboards, and reports after changing this surface.
• Prefer narrow changes that can be tested with sample data before a tenant-wide rollout.
• When troubleshooting, start at the route users open, then inspect configuration, permissions, and logs in that order.
• Keep retired settings hidden or archived so users do not choose outdated paths.
• Assign an owner for ongoing review; unattended configuration becomes stale quickly.

For developers

Use these pages when the surface is read or changed by code, scripts, embeds, widgets, API clients, webhooks, or realtime listeners.

• /developer/payment-links
• /developer/public-access
• /developer/inbound-webhooks
• /reference/shopbyantly

Related links

• /modules/shop-overview
• /modules/inventory-overview
• /guides/payment-links
• /guides/customer-portal