Store
At a glance
Section titled “At a glance”- Product: OpenApp Store
- Manufacturer: OpenApp
- Similar open-source integrations:
- N/A
Overview
Section titled “Overview”Store is an org-scoped OpenApp product feature — not a device connector. Members buy from a catalog and spend is tracked for out-of-band billing (no online payment is collected). It uses dedicated relational tables rather than the integrations plugin system.
Core concepts:
- Catalog — products are defined once per organization (localized names, optional image and external link) and reused across stores.
- Stores — an organization can contain many stores. Each store has its own timezone and currency.
- Inventory — listing a product in a store sets a per-store 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 store’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 store’s public catalog and join flow.
- Statements — monthly spend per member and per store, viewable in the dashboard, printable, and exportable as CSV. Monthly cycles are derived from each store’s timezone.
Purchases, audit, and retention
Section titled “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.
Store 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
Section titled “Getting started”- Open Store in the dashboard and create a store (set its timezone and currency).
- Add products to the catalog, then list them in the store with a price and optional stock.
- Create a QR portal and print it, or add members directly.
- Approve join requests; members buy from the catalog and you track spend via monthly statements.
All management is done through the store endpoints (/orgs/{org}/stores/...) and the
dashboard Store section.