Platform overview

Developer fundamentals for building on Ordergroove.
View as Markdown

Ordergroove powers subscription commerce for iconic brands. This section covers the concepts you need to start building on the platform, whether you’re integrating a new storefront or extending an existing one.

Data model

Ordergroove’s data model is designed for flexibility, with automation via REST and GraphQL APIs. Data is stored in a relational database, with one-to-one and one-to-many relationships between four primary objects:

  • Customer — shoppers and their account data
  • Subscription — one subscription per product, with frequency, offer, and status
  • Items — the individual line items on an order
  • Order — a recurring or one-time shipment generated from a subscription

See Data model at a glance for a full walk-through.

Systems landscape

Ordergroove’s platform has six major integration components that power your relationship commerce experience. Most eCommerce platforms have prebuilt apps or cartridges that automate the majority of these components, but understanding each one helps when you’re building custom integrations.

See Systems landscape map for the full diagram and breakdown.

API authentication

You can authenticate requests using either an API key or an HMAC signature. API keys can be viewed and managed in the Ordergroove Dashboard. For details, see Webhooks and APIs.

Launching a new subscription program

Ordergroove has a proven process to bring new merchants up to speed quickly. If you’re assisting on a new build, familiarize yourself with the onboarding stages, steps, and timeline so you know what to expect.

Feedback and support

Reach out to your Ordergroove contact if anything is missing or unclear. We continuously roll out new documentation and feature recipes, and we’d love to hear what would help make your life easier.