← Back to all docs

Celerant API

Celerant Technology is a unified omnichannel retail platform delivering point of sale, eCommerce, inventory, CRM, and back-office software through its Cumulus Retail and Stratus Enterprise products. An unofficial API lets you programmatically pull orders, inventory, products, and customer records—and push updates like new orders, inventory adjustments, and customer loyalty activity—across in-store and online channels.

By Alex KlarfeldMay 30, 2026
Celerant API

What is Celerant?

Celerant Technology is a retail software vendor offering unified omnichannel management for thousands of retailers across apparel, footwear, sporting goods, firearms (FFL), pet supply, pharmacy, hardware, wine and liquor, and other specialty verticals. Retailers use Celerant to run point of sale, eCommerce, inventory, customer relationship management, loyalty, digital marketing, and back-office reporting from a single platform, synchronizing pricing, inventory, and customer data across in-store and online channels.

Core product families:

  • Cumulus Retail (cloud POS, eCommerce, inventory, loyalty, and mobile apps for small-to-mid-size retailers)
  • Stratus Enterprise (advanced customization, ERP, fulfillment, and analytics for complex multi-location retailers)
  • Point of Sale and integrated eCommerce storefronts
  • Inventory Management and back-office reporting
  • CRM, loyalty rewards, and digital marketing tools

Common data entities:

  • Products, SKUs, Pricing, Inventory levels
  • Orders, Sales transactions, Returns, Tenders
  • Customers, Loyalty accounts, Rewards
  • Purchase orders, Vendors, Receiving
  • Locations, Registers, Employees

The Celerant Integration Challenge

Retailers run mission-critical sales and inventory workloads on Celerant daily, but turning its portal- and integration-driven workflows into clean API-driven automation is non-trivial:

  • Integration over open API: Celerant emphasizes pre-built and custom-managed integrations rather than a broadly published, self-serve public API, so connecting a new system often routes through a partnership or custom development engagement
  • Two product platforms: Cumulus Retail and Stratus Enterprise have different deployment models, customization depth, and object behavior—generic integrations break across them
  • Omnichannel data spread: POS, eCommerce, and back office each touch inventory, pricing, and customer records, and keeping them reconciled across channels is error-prone
  • Per-retailer configuration: Specialty verticals (FFL firearms, pharmacy, CBD/vape) add compliance fields and workflows that vary by merchant
  • Authentication and session handling: Back-office and portal access require credentialed sessions that complicate headless, automated access
  • Batch and sync timing: Inventory, pricing, and order synchronization between POS and eCommerce runs on platform-defined cadences that downstream systems must account for

How Supergood Creates Celerant APIs

Supergood reverse-engineers authenticated browser flows and the back-office surfaces of Cumulus Retail and Stratus Enterprise to deliver a resilient API layer for your Celerant account—across POS, eCommerce, and inventory.

  • Handles username/password and MFA securely in a managed session
  • Maintains session continuity with automated refresh and change detection
  • Normalizes responses across products, orders, inventory, and customers so you integrate once and rely on consistent objects
  • Aligns with your platform (Cumulus or Stratus), vertical-specific fields, and channel configuration for accurate access

Use Celerant with AI agents: Celerant MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your platform (Cumulus or Stratus), channels, and authentication model.

  • Supergood Generates and Validates Your API

We deliver a hardened, production-ready Celerant adapter tailored to your retail configuration and entitlements.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as Celerant evolves.

celerant

API Endpoints

Authentication

POST/authenticate

Authenticate to a Celerant account (Cumulus or Stratus) using username/password, or MFA, and obtain a session token for downstream calls.

Catalog

GET/products

List products, SKUs, pricing, and inventory levels with filters for category, location, and channel.

Catalog

PATCH/inventory

Adjust inventory quantities and pricing for a SKU across in-store and eCommerce channels.

Orders

GET/orders

Retrieve POS and eCommerce orders, returns, and tender details with status and date-range filters.

Orders

POST/create_order

Create an order against the configured channel with line items, customer, and fulfillment details.

Customers

GET/customers

Pull customer profiles, loyalty accounts, and rewards activity for CRM and marketing sync.

Use Cases

Sync inventory and pricing across POS and eCommerce

- Pull product, SKU, and stock levels from Cumulus or Stratus into a central catalog - Push price and quantity adjustments back so in-store and online stay consistent - Reconcile multi-location inventory against a downstream OMS or warehouse system

Centralize orders for analytics and fulfillment

- Stream POS and eCommerce orders, returns, and tenders into a single warehouse - Route new orders to fulfillment, shipping, and accounting systems - Surface daily sales and margin reporting across all locations and channels

Keep customer and loyalty data in sync

- Pull customer profiles, loyalty balances, and rewards into a CRM or marketing platform - Trigger campaigns based on purchase history and loyalty tier - Write back enriched customer attributes for unified profiles

Automate purchasing and vendor replenishment

- Pull purchase orders, vendors, and receiving records for procurement reporting - Generate replenishment orders from inventory thresholds - Sync receiving events back to back-office and accounting systems

Technical Specifications

Authentication

Username/password and MFA handled in a managed session

Connectivity

Authenticated browser flows and back-office surfaces across Cumulus Retail and Stratus Enterprise

Response format

Normalized JSON across product, order, inventory, and customer objects

Rate limits

Adaptive throttling tuned to your account to avoid platform-side limits

Session management

Automatic session refresh, MFA replay handling, and credential rotation

Data freshness

Near real-time reads for orders and inventory with optional scheduled batch syncs

Security

Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging

Webhooks

Event-style callbacks for new orders, inventory changes, and customer/loyalty updates

Latency

Sub-second reads on cached entities; multi-second writes when posting orders or inventory adjustments

Throughput

Horizontally scaled workers sized to multi-location, omnichannel transaction volume

Reliability

Retry, backoff, and idempotency keys for order creation and inventory adjustments

Adaptation

Continuous monitoring of Celerant platform releases and account-specific configuration drift

Frequently asked questions

Yes. Supergood adapts to either platform, normalizing product, order, inventory, and customer entities so you integrate once regardless of whether you run Cumulus Retail or Stratus Enterprise.

Celerant emphasizes pre-built and custom-managed integrations rather than a broadly published, self-serve public API. Supergood works against your authenticated account surfaces, so you get a clean API without a custom integration engagement.

Yes. Supergood normalizes inventory and pricing across POS and eCommerce channels, so you can read stock levels and push adjustments that keep in-store and online consistent.

Each account is profiled against its configured fields and workflows, so vertical-specific attributes—such as FFL firearms or pharmacy compliance data—are preserved rather than dropped into a generic schema.

Orders, returns, tenders, customer profiles, and loyalty/rewards activity are exposed through the same normalized API surface, so transactional and CRM data sit alongside catalog and inventory entities.

Ready to get a real API?