For Fluid power, hose and fitting distributors
Fluid power: the same assembly quoted twice at two counters, at prices that are not close.
Counter pricing is local by nature, and the margin in this trade is on the crimping bench rather than the shelf — which is the half your ERP is least likely to hold a cost for.
A working session on your numbers, not a slide deck. No account, no card, and nothing connected until you say so.
Four things that go wrong on a fluid power book
Named rather than categorized. “Margin erosion” is a heading a reader cannot check against their own week; each of these is something that happened on a Tuesday, and if none of them is familiar then this is the wrong page and the rest of it will not improve.
Problem one
Two branches, two prices, one customer
The same assembly quoted a week apart at two counters, at prices that are not close. Neither counter did anything wrong: there was no floor in front of either of them at the moment they typed, and no reason for one to know what the other had said. Each branch has its own habits, its own long-standing accounts and its own idea of what a job is worth, and none of that is written down anywhere the others can read. Each branch is also right that it knows its own market better than a central list would, and that is what makes this hard rather than easy: the local judgement is real, and so is the inconsistency it produces.
- Neither counter can see the other's quote history
- Neither is breaking a written rule, because there isn't one
- The customer is frequently the one who notices
- The local judgement is real, and so is the inconsistency
Problem two
It gets settled by honouring the lower number
What follows the discovery is not a pricing conversation but a credibility one, and it is usually settled the quick way: the lower price is applied across the account. So the cheapest quote any branch has ever given becomes the price everywhere, and the branch that was pricing correctly has its number replaced by the one that was not. Nobody records that this happened, either. The new price is simply the price, and the reason it is the price — a credibility problem at one counter eighteen months ago — is attached to it nowhere.
- The resolution is a concession made to protect trust, not margin
- It propagates to every branch at once
- And it is now the reference for the next quote at all of them
- Nothing records why the account is on that price
Problem three
The margin is on the bench, and the bench has no cost line
A fabricated hose assembly is where the spread in this trade actually is — the crimping bench rather than the shelf. But an assembly built to order at the counter very often carries no item-level cost in the ERP at all, only its components do. So the half of the business that earns the most is the half nothing can check, this year or any year. So the decision this trade most needs to make — whether the service capability earns what it costs to run — is the one the ERP cannot inform, in either direction. Nobody knows whether the bench is the profit or the subsidy.
- Components are costed; the made-up assembly frequently is not
- Labour and crimp time are rarely on the line at all
- A margin figure over this half averages real numbers with absences
- Nobody knows whether the bench is the profit or the subsidy
Problem four
A spec and a price, decided in one breath
A counter picks the hose, the two ends and the length, and puts a number on the result. Which components that number assumed is not recorded, so the same assembly is not comparable to itself next month — let alone to the version the other branch built. There is nothing to reconcile because there is nothing written down to reconcile against. It also means two quotes for the same job can both be right and still differ. Without the component list behind each number, a comparison between them is a comparison of two things that were never the same.
- The assembly is a decision, not a catalog item
- Two builds of "the same" assembly may differ in components
- So a price comparison between them is not actually a comparison
- Two right quotes for one job, not comparable to each other
What it costs is the way it accumulates
Two separate leaks, and only one of them is a pricing decision. They need different answers and one of them PIE cannot give.
How it compounds
The first compounds through the account. An inconsistency the customer finds resets the whole relationship to the lowest number in it, that number becomes the reference at every branch, and the next inconsistency resets it again from there. The second does not compound at all — it is simply invisible. Where an assembly carries no cost there is nothing to compare a price to, so the question "are we making money on hose assembly" has never been answered on your book, in either direction.
Why nothing catches it
The honest answer to the second one is UNKNOWN, and this platform will give you that answer rather than a figure. A cost estimated from components would be a plausible number with a real provenance stamp on it — worse than no number, because the screens would look complete and a decision would get made off them.
No figure on this page is a claim about your book. There are no industry averages here and no recovered-margin percentages: the only numbers on the page are on the card further down, and they are sample figures re-derived by a test from the operands the card itself shows.
What a fluid power desk does about it today
Not a list of mistakes. Every one of these is a sensible response to a real constraint, which is exactly why it has survived — and the last one is usually the most rational of them. A product that does not understand why the current answer is the current answer has nothing useful to replace it with.
A branch price list
Real, and usually respected for stocked components. It has nothing to say about an assembly that does not exist until somebody builds it, which is where the money is.
The counter's judgement
Somebody who has built this assembly a hundred times knows roughly what it should go out at. That is genuine expertise, it is correct more often than not, and it is different at every branch by a margin nobody has measured.
A cost built by hand, sometimes
On a large job somebody adds up the components and adds something for the bench. It is the right answer and it takes ten minutes, so it happens on the jobs big enough to justify it and not on the ones that make up the volume.
Nothing, on assemblies
Stated plainly: for most made-up lines there is no check, because there is no cost to check against. This is a data problem before it is a pricing problem, and any tool that claims otherwise is estimating.
Where PIE intervenes, and at which moment
Every figure below is deterministic arithmetic over rows your ERP already wrote, stamped with the version of the margin policy that judged it. The AI on this platform reads those numbers and phrases them; it never produces one. What is not listed here does not apply to a fluid power book, and the limits further down say which of those are permanent.
One policy, however many counters
The floor is computed from the AP-invoice line your ERP already wrote and applied identically at every branch, at the moment the line is priced. A breach routes to a named approver, so the exception is visible centrally while it is being asked for rather than discovered in a margin report — and the branch that prices correctly stops being the one whose number gets overwritten.
Where there is no cost, the answer is UNKNOWN
A fabricated assembly that carries no item-level cost gets no estimated one. PIE reports the line as unmeasured and says so on every screen that would otherwise have used the figure, and a month in which it could not measure reads UNKNOWN rather than zero. This is the same rule that governs a book with no purchase cost anywhere, and on this trade it is the most important sentence on the page.
Accounts drifting away from one branch
Decline and dormancy are computed from invoice history and need no cost at all, so they work on the assembly half of the book exactly as well as on the stocked half. A customer quietly moving their hose business is visible before the renewal conversation rather than during it.
The enquiry, resolved against your own book
Paste what arrived and PIE reads it into lines, resolving each against the catalog you uploaded — exact match first, nearest neighbour over the description otherwise. It is deterministic, so two branches pasting the same text get the same answer, which is a small thing that this trade does not currently have. It finds the line in your own book and proposes no substitute from another manufacturer's.
One quote line, start to finish
One stocked component line, because that is the half a floor can speak to. What happens to the assembly line beside it is step five, and it is the honest half of this example.
1/2 in R2AT x 36 in JIC-JIC
200 units for A repeat account in Ohio, quoted at $41.20 — routed to a sales manager, no individual owner. The platform holds it, not the salesperson.
| Quoted unit pricethis quote | $41.20 |
| Effective unit costbill | $38.08 |
| Margin flooryour margin policy | $44.80 |
| Recommendedthis customer’s own history | $48.70 |
| Margin at this pricecomputed | 7.6% |
The manager’s decision card, as the product draws it — with sample figures, because no customer’s numbers belong on a public page.
The enquiry arrives at one counter
It is pasted as it came and read into lines. The component line resolves against your catalog to the item on the card; the assembly line on the same enquiry resolves too, and carries no cost.
The counter prices the component line
They see the floor, the recommended price and what this customer has paid before — the same three figures the other branch would see for the same item, computed from the same policy. Not cost, and not margin.
The floor answers, identically at every branch
Cost, divided by one minus the margin floor your policy sets, on the AP-invoice cost your ERP already wrote. On the card the asked-for price is below it. The policy is one policy — that is the whole intervention on this trade's stocked half.
The line is held, centrally and visibly
It routes to a named approver with the rule named, and the hold is visible to whoever owns pricing rather than to the branch alone. If it is cleared, the clearing is an append-only row carrying the policy version in force.
And the assembly line says UNKNOWN
No floor, no margin, no estimate. It is reported as unmeasured, on this screen and on every other one that would have used the figure. That is the correct answer and it is also the limitation: on a book where most of the value is fabricated, most of this page's first intervention does not apply. Settle that on the call before anything else.
Sample figures throughout. No customer’s numbers appear on a public page, every figure on the card is re-derived by a test from the same operands it shows, and the floor is cost divided by one minus the margin floor your policy sets — nothing rounded in your favor, because a floor rounded down is a floor that has moved.
The limits, before you find them in week three
Every item below is a thing this platform does not do on a fluid power book today. They are on the page because a capability list is not what a distributor who has survived one implementation believes — and because the alternative is you discovering them after a pilot.
- A fabricated assembly usually carries no item-level cost, and PIE will not invent one. On the half of this trade where the margin actually sits — hose assembly, not components off the shelf — the floor may have nothing to check, and the honest answer is UNKNOWN rather than a number. Ask about this on the call before anything else; it decides whether the rest of the page is worth having.
- Configuration is not modelled. PIE prices a line; it does not build a specification, check a pressure rating or validate that two ends fit.
- Special pricing agreements and manufacturer rebates are not modelled, so where purchases are claimed back the computed floor sits above your real one.
- Quotes are not imported from any ERP, so a win rate has no denominator until you start quoting here.
- Nothing resolves until a price list has been uploaded and its decoding confirmed by a person.
Why it can be trusted
The AI never computes a single number.
Your business data and your rules determine the number. AI explains it.
Same inputs, same answer, every time — with a paper trail.
- Deterministic calculations — every figure is arithmetic on your own records; turn AI off and every number still works
- Auditable decisions — each number names the policy that produced it, so a price you quoted last quarter still explains itself
- Your data — read from your own books, used for you alone, exportable and erasable on request; AI runs on your own account
- Your rules — you set the floors and thresholds, and PIE holds every quote to them
- Provenance — every row carries the connector, the connection and the id it came from, so nothing in PIE claims a source it did not have
What fluid power distributors ask first
Our assemblies are built at the counter. Will PIE price them?
It will check whatever price is typed against a floor — if your ERP holds a cost for that assembly. Where it does not, PIE reports the line as UNKNOWN rather than estimating a cost from components. This is the question worth settling first, because on many fluid power books the assembly half is where the margin is.
Does one policy work across branches with different customers?
The policy sets floors; it does not set prices. Two branches serving different accounts still quote differently — what they no longer do is quote below a floor without somebody named signing for it.
What does PIE do to my ERP?
Reads it. On Prophet 21, Sage X3 and Sage 100 it cannot write at all; on NetSuite, Acumatica, Dynamics 365 Business Central and Zoho Books the one record it can create is the quote, and only with a permission granted separately for that.
Can a salesperson see cost or margin?
No. The server omits those fields, so there is nothing to read out of a network tab, and a rule whose boundary is cost is withheld too.
Which of the seven this trade runs
Prophet 21 — Epicor names fluid power in its own vertical list — with Business Central and Acumatica at the mid-market end. Worth reading your system's page for one reason in particular on this trade: whether it holds a cost on a made-up assembly decides how much of this page applies to you.
Your book already knows where the margin went.
30–45 minutes, your own numbers on the screen, and an honest answer about what PIE can and cannot see on a fluid power book.