Superintelligence Prep for Plumbing Supply: Accounts and Counter Orders
The account, counter-order, substitution and pricing-rule records a plumbing supply house needs so AI agents can answer stock questions from current data.

Superintelligence prep for a plumbing supply distributor means giving AI agents the records that decide what a counter answer should be: which account is open and on what terms, what is on the shelf or inbound at each branch, which substitutions the counter may offer, and which pricing rules apply today. An agent can answer stock and price questions reliably only when those records are current, structured and bounded by clear approval limits. The work begins with an inventory of records and their owners, not with a choice of model.
Key takeaways
- Stock and price answers are only as reliable as the account, branch and pricing records behind them.
- Counter orders and substitutions need their own log, because they change what the house can promise.
- Every pricing rule needs an effective date, a source document and a named owner.
- Agents should read current records and draft or flag exceptions, while accountable staff approve substitutions, credits and special terms.
- Start with one branch and one counter question type, and set a success test before adding anything else.
Why counter answers break when the records are scattered
A counter clerk knows things the system often does not. The contractor on the phone has a negotiated rate that was agreed by phone and never entered, the discontinued valve has an approved replacement for only some accounts, and a transfer from another branch is expected before noon. When an agent is asked whether three-quarter inch press fittings are in stock and what a specific account should pay, it has to assemble those facts from several places: the inventory system, the price file, the account master and, too often, a note typed into a free-text field.
If any one of those sources is stale, the answer sounds confident and is still wrong. Customers notice quickly, and so do the people who must honor or correct the quote. The fix is not a smarter model. It is a short, explicit list of which records answer which questions, how current each one is, and who is allowed to change it. Plumbing contractors who buy from the house often also depend on dispatch and callback records that must agree with what the counter promised, so the same discipline applies there.
Which account records an agent needs
Account records decide who is asking and what they are entitled to. For each contractor, business or walk-in customer, keep:
- The legal entity and trading name, with the contacts authorized to place orders.
- The price agreement in force, its tier or negotiated rates, and its start and end dates.
- Credit terms, such as open account or prepayment, and the person who can approve an exception.
- Tax exemption documents on file and their expiry, so an agent never states a tax treatment the house cannot support.
- Approved buyers for restricted products, meaning which licensed contractor or employee may purchase them and what paperwork must accompany the sale.
- Preferred branch, pickup or delivery terms, and any job site addresses tied to the account.
Agents should read these records but never create or edit them. A change such as a new credit limit belongs to a person with authority, and the agent's permissions should reflect that boundary from the first day. The [OWASP authorization guidance](https://cheatsheetseries.owasp.org/cheatsheets/Authorization_Cheat_Sheet.html) is a useful reference for deciding which actions a non-human user may take at all.
What a counter order log must capture
The counter order is the record most often missing when a customer calls the next day asking where their order stands. Log every counter transaction with an order identifier, the account, the person who served the customer, the time, each line with quantity and unit, what was promised compared with what was handed over, any backorder or will-call commitment, and any exception a manager approved. A special order that the branch later reconciles against a supplier invoice needs the same trail.
The pattern is familiar from special orders and pickups in hardware retail, where a counter promise and a later pickup must agree. In plumbing supply the stakes are higher, because a missing fitting can stop a crew in the middle of a job. When an agent answers a question about an order, it should find the counter commitment first and the warehouse status second, not infer the promise from the shipping status alone.
Substitution rules and a decision guide
Substitutions create most of the risk in a supply house. Two parts can match in size and connection but differ in listed specification, approval status or the code requirements that apply to the installation. Keep a substitution record for each product family with the original SKU, the proposed alternate, the basis for equivalence, the person who approved it, the account or job types where it applies, and whether the customer must confirm in writing.
Use a simple decision guide to set the agent's authority:
- Same manufacturer, same listed specification and size: the agent may present the alternate, and the counter confirms the sale.
- Different manufacturer with an equivalence the house has recorded: the agent drafts the offer, and a counter staff member approves it before it reaches the customer.
- Anything tied to potable water, gas, or a component that a local code or manufacturer specification names: no agent-offered substitution, and the question routes to a licensed staff member.
- Any substitution that changes price, warranty or delivery date: the agent shows the difference and waits for an explicit human decision.
The guide is only as good as the records behind it. A substitution approved verbally across the counter is not yet a record, and an agent cannot cite it. Writing it down is the first task, and it is often the most useful one.
Pricing rules with owners and effective dates
Pricing questions rarely fail on the base price. They fail on conversions and conditions: a product bought by the foot and sold by the box, a break quantity that applies only within a single order, a supplier cost change that takes effect on a stated day, a freight threshold, or a rebate credited after the sale. Each rule should carry four fields: the rule itself, the source document it came from, its effective dates, and the owner who can change it. The same structure helps in ecommerce operations, where a catalog price that is correct in one channel can be wrong in another.
Retrieval design matters here. Retrieval-augmented generation grounds an answer in documents fetched at the time of the question rather than in what a model learned earlier, which suits prices that change often. The [Google Cloud reference architecture](https://docs.cloud.google.com/architecture/rag-capable-gen-ai-app-using-vertex-ai) describes the general pattern. The practical requirement is that the agent names the price file version it used and declines to quote when that version is missing or past its review date.
Illustrative scenario: a contractor calls a branch and asks for the account rate on a one-inch ball valve. The agent finds a negotiated tier in the account record, but the current price file is newer than the agreement's review date. Instead of quoting, it tells the counter that the rate needs confirmation, shows both records side by side, and routes the question to the account owner. This scenario is illustrative and does not describe a specific customer.
A first plan and how managed operations keep it current
Start with one branch and one counter question, such as in-stock checks for a defined list of high-volume fittings. Then work through these steps:
- Inventory the sources for that question: stock system, price file, account master, substitution notes and the counter order log.
- Mark each source as current, partly current or stale, and name the person who owns it.
- Write the agent's permissions: what it may read, what it may draft, and what it may never change or promise.
- Define the success criterion in terms a manager can check, such as a sampled stock answer that matches the branch count recorded at the time of the answer.
- Add observability so each answer records which record versions it used and whether a person approved it. The [OpenTelemetry observability primer](https://opentelemetry.io/docs/concepts/observability-primer/) explains the traces, logs and metrics that make this kind of audit trail possible.
- Review the first sample of answers with the counter team before widening the scope.
Be Human handles this as a managed service. We define the single role, map the records it reads, set approval boundaries for substitutions, credits and exceptions, and keep logs showing which record versions informed each answer. Recurring evaluations sample real counter questions and compare the answers with the system of record, while permission review and integration maintenance keep the agent aligned when a supplier changes a price file or a branch changes its stock process. Take the free Be Human AI diagnostic to find the first counter task worth handing to an agent.
Frequently asked questions
Do we need to replace our inventory or ERP system before an agent can answer stock questions? No. In most cases the agent can read existing stock and price data through a read-only connection, provided each source has a clear owner and a known update schedule. Replacing systems is a separate decision and should not block a first, narrow pilot. The useful first step is usually cleaning up the records the agent would rely on.
Should an agent offer substitutions directly to contractors? Only within limits you set in advance. Equivalent products from the same manufacturer with a recorded specification match can be offered for counter confirmation, while anything tied to code requirements, potable water or gas should route to a licensed person. The agent should always show the difference in price, warranty or delivery before the customer decides.
How do we keep an agent from quoting an outdated price? Require the agent to cite the price file version and the account agreement it used, and have it decline to answer when either is missing or past its review date. Sample its answers each week against the system of record. Pricing errors usually come from unclear effective dates, so fix the dates before tuning the agent.
Can the agent work in Portuguese as well as English? Yes, Be Human delivers remote service in English and Portuguese. The records still need consistent naming for products, units and account terms, because an agent cannot resolve a mismatch the house has not defined. Language is the easier part. The discipline of the record list is what makes answers trustworthy in either language.
Your next step
See where an AI agent fits in your company first.
Take the free Be Human AI diagnostic. A few questions about your work show which task to hand to an agent first, what it needs to know and where a person approves.
Be Human editorial guidance. Examples are illustrative unless explicitly attributed. Sources provide background; implementation choices depend on your workflow.


