Skip to main content
Hiveku Commerce is a business management suite for service-based and B2B companies — invoicing, estimates, contracts with e-signatures, recurring subscriptions, and a client payment portal. Think QuickBooks Online plus DocuSign plus Stripe Billing, all wired into the same project where your CRM, marketing, and website already live.

​
Who it’s for

Commerce is built for service businesses, agencies, consultancies, and B2B SaaS companies that bill other companies — not for retailers or DTC stores. Typical fit:
  • Marketing agencies billing monthly retainers
  • Consulting firms invoicing milestone-based projects
  • Professional services billing time and deliverables
  • B2B SaaS with custom enterprise contracts and invoicing
  • Any business sending estimates, contracts, and invoices to clients regularly
If your business model is “customer signs up online, picks a plan, gets charged automatically,” Stripe Billing in code is usually a better fit. Commerce is for the relationship-driven, contracted, account-managed motion.

​
What it is — and what it isn’t

Commerce is built for the workflow of selling services and managing client relationships, not for running a public storefront. The two patterns serve different audiences and need different tools.
Use caseTool
Sell products on a public website (self-serve checkout)Build product pages with Stripe — see Add Product Pages
Invoice B2B clients, send estimates, manage retainersCommerce module (this section)
Subscription billing for app users (in-app upgrades)Stripe Billing in code, or Commerce subscriptions for managed retainers
If a customer would log in to your product to manage their plan, that’s a Stripe-in-code job. If you’d email them an invoice and expect them to pay it from a link, that’s Commerce.

​
What you can do

  • Invoice clients — Draft, send, track, and reconcile invoices with line items, tax, and discounts. PDF download, payment link, automated reminders.
  • Send estimates and quotes — Pre-sales proposals that prospects approve online. Convert accepted estimates to invoices with one click.
  • Manage contracts and e-signatures — Templates with variable fields, multi-signer workflows, audit trail, and signed-PDF storage.
  • Bill on a schedule — Recurring subscriptions (monthly, quarterly, annual) for retainers and SaaS-style plans, plus usage-based billing.
  • Run a client portal — Public, branded link where clients view invoices, pay them, see contract status, and download statements.
  • Process payments — Connect Stripe or Authorize.Net per account. Cards, ACH where supported, Apple Pay and Google Pay.
  • Track receivables — AR aging by 0–30, 31–60, 61–90, and 90+ buckets. MRR, ARR, churn, and cash-collected reporting.
  • Handle taxes — Per-jurisdiction rates and tax-exempt client flags applied automatically to invoices.

​
Why it’s bundled into Hiveku

Most service businesses cobble together separate tools — a billing tool, a quoting tool, a contract tool, a portal — and live with the integration tax. Each tool has its own client list, its own data model, its own login. The same client gets entered into four systems with four different spellings of their company name. Commerce shares one client list with your CRM, one company record, one source of truth. A contact you added in CRM is the same contact who pays an invoice — no syncing, no duplicates. When the AI assistant or a workflow needs to act on a client, it sees the full picture: their deals, their invoices, their contracts, their payment history.

​
Where it lives

The Commerce UI is at /dashboard/commerce/ with sections for each capability:
  • /dashboard/commerce/ — Overview dashboard
  • /dashboard/commerce/products/ — Catalog
  • /dashboard/commerce/invoices/ — Invoice list and editor
  • /dashboard/commerce/estimates/ — Estimate list and editor
  • /dashboard/commerce/contracts/ — Contracts and templates
  • /dashboard/commerce/subscriptions/ — Recurring billing
  • /dashboard/commerce/schedules/ — Scheduled invoice generation
  • /dashboard/commerce/payments/ — Payment methods and transactions
  • /dashboard/commerce/reports/ — Revenue and AR analytics
  • /dashboard/commerce/usage/ — Usage tracking for usage-based billing
  • /dashboard/commerce/settings/ — Tax, payment processor, and dunning configuration
Data lives in the crm_* tables (invoices, estimates, products, subscriptions, contracts, signature envelopes, payment integrations), and the API is exposed under /api/crm/* for automation and custom integrations.

​
Setup flow

1

Connect a payment processor

Authorize Stripe via OAuth or add Authorize.Net credentials in Settings. Without a processor connected, you can still draft invoices but clients can’t pay them online.
2

Add tax settings

Configure your default tax jurisdictions and any tax-exempt client flags so invoices calculate correctly from the first send.
3

Build your product and service catalog

Add the items you sell — services, retainers, plans, one-time products — to the Products catalog. Line items on invoices, estimates, and subscriptions pull from here.
4

Brand the client portal

Upload your logo and set portal colors so the experience feels like an extension of your brand, not a generic billing page.
5

Send your first invoice or estimate

Pick a client, add line items, send. The client gets a portal link by email; you watch the status update from sent to paid.

​
Where to start

Send Your First Invoice

End-to-end walkthrough from connecting Stripe to marking an invoice paid.

Products & Services

Build the catalog that powers invoices, estimates, and subscriptions.

Invoices

Draft, send, track, and reconcile invoices with full status tracking.

Estimates

Pre-sales quotes that convert to invoices on acceptance.

Contracts & E-Signatures

Send MSAs, SOWs, and NDAs for legally binding electronic signature.

Subscriptions

Recurring billing for retainers, SaaS plans, and usage-based services.

Client Portal

The branded public-facing surface clients use to pay and review documents.

Payments

Connect Stripe or Authorize.Net and manage saved payment methods.

Reports & Analytics

AR aging, MRR, ARR, churn, and cash-collected reporting.

​
How it fits with the rest of Hiveku

Commerce shares contacts and companies with your CRM — the same client record holds their deals, their invoices, and their contract history. Workflows and AI automations can react to Commerce events (invoice overdue, estimate accepted, subscription about to renew) and trigger emails, tasks, or follow-up sequences. Reports flow into the same dashboards as your sales and marketing data. A few common cross-module patterns:
  • Deal won → Estimate sent → Contract signed → Invoice billed. A single record chain from the CRM deal through to cash collected, all stitched together via cross-references.
  • Subscription renewed → Email automation → Follow-up task. Trigger relationship-deepening actions off the renewal event without manual coordination.
  • Invoice overdue → Reminder email → AR report. The collections loop that keeps cash flowing — see Track AR Aging.
  • Contract executed → Project kickoff workflow. Auto-create tasks, calendar invites, and onboarding emails when a contract is fully signed.

​
Where the data lives

Commerce data is stored in the crm_* tables alongside CRM contacts and companies:
  • crm_products — Catalog
  • crm_invoices, crm_invoice_line_items — Invoices and their line items
  • crm_estimates, crm_estimate_line_items — Estimates and their line items
  • crm_subscriptions — Recurring billing schedules
  • crm_contracts, crm_signature_envelopes — Contracts and signature workflows
  • crm_payment_integrations — Connected processors (Stripe, Authorize.Net)
  • crm_client_portal_sessions — Magic-link portal sessions
The API at /api/crm/* exposes everything for automation, custom integrations, and workflow triggers.
If you’re new to Commerce, start with Send Your First Invoice. It walks the entire path — connect Stripe, add a product, build the invoice, watch the client pay — in one sitting.