WholeStack Pricing ↗
Revenue · Distribution Intent Contract: wholesale-sales-v2

A CRM that knows your discount tiers are not a suggestion.

Generic CRMs model deals. Distribution runs on contractor accounts, wholesale pricing tiers, credit limit controls, and mandatory margin approvals. WholeStack compiles your exact trade rules into a full-stack Postgres application, proven against live database constraints before launch.

Build a wholesale desk Bring an existing app See pricing
Wholesale Distribution & CRM Logistics

Operational Territory

Regional Distribution & Trade Pricing Systems
Postgres RLS · Automated Replay

What the compiled desk runs

Everything below is a database record with strict transactional rules attached, not a cosmetic custom field bolted onto a generic CRM pipeline.

https://app.wholestack.internal/wholesale-crm/orders
Verified Release: v2.4.1 · P3 PASS
Wholesale CRM Materialized Application UI

Accounts and Tiers

Contractor accounts carry an assigned tier (Silver, Gold, Platinum). The tier prices the order lines automatically.

Credit Control

Outstanding balances are checked at quote generation. Orders exceeding credit thresholds automatically pause for review.

Order Fulfillment

Accepted quotes convert to fulfillment orders. Warehouse picking teams read validated database records, never email threads.

MOD 01

Accounts and Tiers

Contractor accounts carry a pricing tier, and the tier is what prices the line — not whatever a sales rep typed into an input.

MOD 02

Quotes and Approvals

A quote past your discount threshold routes for approval before it can be sent. The write is refused until the sign-off is committed.

MOD 03

Credit Control

Credit limits are checked at order placement. Review is a state the account can enter, blocking release until resolved.

MOD 04

Order Handoff

An accepted quote becomes the order. Fulfilment reads the order record directly, eliminating transcription errors.

MOD 05

Renewals

Contract end dates drive the work queue, with uplift rules automatically computed and applied at renewal time.

MOD 06

Audit Integrity

Every price override, discount approval, and credit expansion is logged with cryptographic actor timestamps.

The rules the contract enforces

These are written as Intent Specification Language (ISL) invariants, compiled down to PostgreSQL row-level security and server action assertions. Break one and the transaction is refused at the engine boundary.

wholesale-contract.isl
Compiled to Postgres RLS · Zero Drift
domain WholesaleDistribution {
  entity ContractorAccount {
    id: UUID
    name: String
    tier: Enum[Silver, Gold, Platinum]
    credit_limit: Decimal
    current_balance: Decimal
  }

  entity Quote {
    id: UUID
    account_id: UUID -> ContractorAccount
    discount_percent: Decimal
    total_amount: Decimal
    status: Enum[Draft, PendingApproval, Approved, Sent, Accepted]
  }

  policy MarginProtection {
    invariant R01_NoQuoteBelowMarginWithoutOwnerApproval:
      forall q in Quote:
        (q.discount_percent > 0.15) implies
        (q.status == Approved requires Actor.hasRole(Role.Owner))

    invariant R02_CreditLimitEnforcement:
      forall q in Quote, a in ContractorAccount:
        (q.account_id == a.id && q.status == Accepted) implies
        (a.current_balance + q.total_amount <= a.credit_limit)
  }
}

What ShipGate checks before this launches

Distribution is where a missed rule leaks tens of thousands in unapproved discounts. ShipGate executes an adversarial verification pass against an isolated runtime before minting a SHIP verdict.

VERDICT: SHIP (VERIFIED RECEIPT)
SHA256: 4a8b79e13d90f22c6b...
100%
Contract Clause Coverage
12/12
Journey Beats Executed
0
Silent Security Leaks
PASS
Non-Vacuity Assurance
CHK 01

Requirement Coverage

Every clause in your contract has an executing test. Uncovered clauses fail the gate immediately.

CHK 02

Non-Vacuity Testing

Tests that pass because they assert nothing are treated as failures, not as coverage.

CHK 03

Security Boundaries

Each role is driven against records it must not reach. A single credential or data leak is a NO_SHIP.

CHK 04

Runtime Replay

The booted application replays real command sequences against an isolated PostgreSQL instance before release.

Frequently Asked Questions

How is this different from Salesforce or HubSpot?

Those model a generic sales pipeline and let you add custom fields. WholeStack models your exact pricing and approval rules as executable constraints, then proves the compiled application obeys them before release.

Can it price from our existing rate card?

Yes. Your rate card becomes part of the contract, including tier structure and the conditions under which a price may be overridden.

What happens when our terms change?

You change the clause and recompile. Re-verification runs against the new contract, and the change carries its own cryptographic evidence.

Do we own the code?

You own the compiled application source. WholeStack retains rights in the compiler and verification services themselves.

Bring your rate card and your approval rules.

Prototyping costs nothing and needs no card. You pay $299 once, on a verified SHIP verdict, and $79 per month per application to keep it running and re-verified.