Explore everything

DEVELOPER DOCUMENTATION

Understand the commerce model

Keep business identity, lifecycle and data ownership explicit as you build.

Tenant context#

Agora is organised around business context. Integrations must preserve the intended tenant and avoid reusing context across independent businesses. Confirm the deployment’s access and identity controls.

Products and variants#

Product information describes an offer; variants identify options that may have their own stock and prices. Keep the identifier used in an integration distinct from the name shown to a customer.

Orders, payments and fulfillment#

An order records a purchase. Payment activity and fulfillment describe separate lifecycles, so a single status flag is not enough to represent the whole business event.

Location and money context#

Stock quantities require item and location context. Financial values require currency and a known representation. Use the actual schema instead of assuming all numbers use decimal major units.

Explore Agora

Press Esc to close · Every result opens a dedicated page.

The Agora story

Founder recording with animated product sequences. View the pitch summary and further walkthroughs ↗

Supplied Agora workspace