Commissary

At a glance

• Product: OpenApp Commissary
• Manufacturer: OpenApp
• Similar open-source integrations:
  • N/A

Overview

The Commissary integration is an internal commissary: a storefront where approved members buy from a catalog and their spend is tracked for out-of-band billing (no online payment is collected). It is built on dedicated relational tables rather than device metadata, so purchases, inventory, and statements are consistent, queryable, and auditable.

Core concepts:

• Catalog — products are defined once per organization (localized names, optional image and external link) and reused across commissaries.
• Commissaries — a commissary integration can contain many commissaries. Each commissary has its own timezone and currency.
• Inventory — listing a product in a commissary sets a per-commissary price and optional stock level. Leave stock empty for untracked items; set a number to enforce and decrement it on each purchase.
• Members — only authenticated, admin-approved users can buy. Guests can browse a commissary’s QR page and request to join; admins are notified (SMS + email + the in-app activity feed) and approve in the dashboard.
• Billing accounts — every member gets a personal account, but accounts can group users so one person’s purchases bill another’s account (for example, a child’s purchases billed to a parent).
• QR portals — printable, stable QR codes that link to a commissary’s public catalog and join flow.
• Statements — monthly spend per member and per commissary, viewable in the dashboard, printable, and exportable as CSV. Monthly cycles are derived from each commissary’s timezone.

Purchases, audit, and retention

Each purchase is written to an immutable ledger that snapshots the product name and price, so reports stay readable even after a product is removed. The ledger row and its audit event are committed in the same transaction, so the audit log never diverges from billing. Deleted products are soft-deleted and retained for one year before purge.

Commissary activity (purchases, catalog and inventory changes, member approvals, registrations, portal changes) is emitted to the durable audit log and surfaced in near-real-time via the dashboard activity feed and outbound webhooks. The audit log is the cross-cutting activity/security feed; the purchase ledger remains the system of record for billing.

Getting started

1. Create an integration with provider type commissary.
2. Create a commissary (set its timezone and currency).
3. Add products to the catalog, then list them in the commissary with a price and optional stock.
4. Create a QR portal and print it, or add members directly.
5. Approve join requests; members buy from the catalog and you track spend via monthly statements.

Setup reference

Integration config

No provider-specific fields.

The integration itself has no configuration — it is the container for the commissary. All management is done through the commissary endpoints (/orgs/{org}/commissaries/...) and the dashboard.