Product
Every price will carry its source — none of that data is live yet
PaxExact's pricing model is built to track where a unit cost came from and how confident that figure is, instead of showing one unexplained number. No production pricing catalog is loaded behind it today.
What's real today
- The pricing architecture — a source class, a reason when a price can't be resolved, and a confidence on every price — is built and in production.
- No production pricing catalog is loaded yet: treat pricing as not a source of real numbers today.
- The one connected pricing source is an explicitly sandboxed vendor feed, guarded so it can never be mistaken for production data.
- Pricing suggestions from your own organization's prior priced lines exist as a mechanism, but depend on accumulated data that hasn't built up yet.
- A human-entered price always wins over any suggestion, and an unpriced line is marked unpriced, never shown as zero.
What 'source-tracked, confidence-scored' actually means
A price in PaxExact isn't just a number — it's a small record. It carries a source class (did it come from a catalog, from your own prior data, from a manual entry, or is it unverified), a state describing whether it could be resolved at all, and, when it couldn't, a specific reason rather than a silent gap.
That structure is what lets a reviewer trust a price without re-deriving it — or, just as important, immediately see that a price isn't trustworthy yet and why.
A line with no catalog match
Why there's no catalog yet
The architecture described above is real and in production, but the data behind it is not: no licensed, production pricing catalog is loaded. The one pricing source connected today is an explicitly sandboxed vendor feed — kept isolated on purpose so it can never leak into or be confused with real customer pricing.
If your evaluation of PaxExact depends on getting production-grade unit prices today, it isn't there yet. The design is meant to make that gap visible rather than to paper over it with a plausible-looking number.
Your own data, eventually
PaxExact is designed to suggest a unit price from your own organization's prior priced lines, once enough independent projects support a given figure — the mechanism requires a minimum of two distinct projects before it will offer a suggestion. That mechanism exists in the platform today; what it depends on is accumulated customer data, which simply hasn't built up yet across most organizations.
A human-entered price always wins over that suggestion. And your own data stays private to your organization — it never informs another customer's suggestions unless you explicitly opt in.
A missing price is never a zero
Server-computed totals are live today, and they're built around one rule: a missing price is never displayed as $0. When a line can't be priced, the estimate's total reports itself as incomplete rather than quietly treating the gap as free. That's a small design choice with a real consequence — nobody using PaxExact today can be misled by a total that looks finished when it isn't.
FAQ
Frequently asked
Is PaxExact's pricing data live?
No. The architecture that carries a price's source and confidence is in production, but no production pricing catalog has been loaded behind it. The only connected source today is a sandboxed vendor feed kept isolated so it's never confused with real data.
Will PaxExact ever show me a price with no explanation?
No — that's the point of the design. Every price is meant to carry a source class, or a specific reason when it can't be priced, rather than a bare number.
What happens if a line item has no price?
It's reported as unpriced, and the estimate's total is marked incomplete rather than treating the missing price as zero.
Can PaxExact use my own historical prices?
That's the intent of the own-data pricing mechanism, coming soon: once enough of your own projects support a figure, PaxExact can suggest it — but a human-entered price always wins, and your data stays private unless you opt in.
Related