Custom pricing for pergola dealers is a plumbing problem, not a pricing problem

Most pergola dealers do not have a pricing problem in the way the word usually means. They are not charging the wrong amount on average. They are charging a different amount, on the same spec, depending on which member of staff opened the quote on which afternoon. The variance is the problem, not the level.

The variance has a cause, and the cause is structural. A pergola dealer is sitting between a manufacturer’s pricing table that was never meant to be installed, a discount scheme that has three or four moving parts, and a buyer who keeps asking for the size that is not in the catalogue. Each of those three pressures looks like a separate spreadsheet. They are the same spreadsheet, and the dealer is rebuilding it by hand every time a buyer asks for a price.

The three structural breaks#

Walk through them in the order the quote moves on the desk: the cost comes in from the manufacturer, the discount comes off, the buyer’s options go on top.

The manufacturer’s table is missing roughly 60 percent of the installed cost. A pergola manufacturer publishes a dealer price list that covers the structure, the standard roof, the standard finishes, and a short list of factory accessories. That is the gate price. It does not carry the regional labour rate the dealer pays its install crew. It does not carry the fixings, brackets, and chemical anchors the dealer needs once it sees the substrate on site (concrete, decking, paving slab over sand, all different). It does not carry the freight modifier for shipping a 4 by 5 metre crated structure across a border. It does not carry the electrical first fix for a motorised roof. It does not carry VAT, import handling, or the regional installation permit fee. The dealer’s engineer reconstructs all of that by hand, from memory, on every quote. On a louvred aluminium build, that hidden layer is routinely 50 to 70 percent of the number the buyer eventually sees.

The multi-tier dealer discount drifts between staff. Most pergola manufacturers run dealer pricing as a base discount, plus a volume bracket that depends on year-to-date orders, plus a quarterly bonus tied to a target, plus a regional surcharge, minus a current campaign. Each rule is correct in isolation. The drift starts when two members of staff apply them in a different order, pick the wrong volume bracket because the year-to-date number is not in front of them, or forget the regional surcharge because the customer is in the next county and the previous quote was domestic. The result is the same spec quoted at two different numbers in the same week. The manufacturer’s accountant cannot reconcile it at month-end. The buyer who got the higher quote calls the dealership across town and finds out their neighbour got the lower one.

The buyer-side options double the translation step. A pergola buyer who has spent a weekend on a configurator does not ask for the standard build. They ask for a 4.5 by 4.5 metre instead of a 4 by 4. They ask for motorised side screens on three sides instead of two. They ask for the integrated rafter heating, the dimmable LED strips, and a non-standard RAL colour to match the window frames. Each one is a price modifier the dealer’s engineer has to look up, combine, and apply on top of the discounted gate price. The translation step that used to be “read the catalogue” is now “read the catalogue, apply the modifier matrix, check the compatibility rules, recompute.” On a customised build, that work doubles or triples the time a quote takes to generate, and triples the surface area where a number gets typed wrong.

Solving any one of the three by hand makes the other two worse. The engineer who carefully reconstructs the installed cost stops applying the discount logic the same way as the salesperson who happily applies the buyer-side options. The salesperson who knows the discount stack cold has no idea what the regional freight modifier is, and quotes installed prices that lose money on every build that crosses a border. The teams that get one piece right by discipline tend to get the other two pieces wrong by tiredness, because nobody can hold all three matrices in their head on a Wednesday afternoon.

What the fix looks like in practice#

The fix is not a better spreadsheet. The fix is to stop holding the rule set in a spreadsheet at all. Pricing rules belong in software, in a single library that the configurator reads from, that the buyer-facing quote reads from, that the production handoff reads from, and that any member of staff can look at without re-deriving from memory.

That library has four layers, stacked in the order the cost moves.

Layer one, the manufacturer’s base table. The structure, the roof type, the standard finishes, the standard accessories. Imported directly from the manufacturer’s dealer price feed when there is one, or maintained as a versioned table when there is not. Updated when the manufacturer publishes a new price list, not when somebody remembers to update the spreadsheet next quarter.

Layer two, the dealer’s installed cost add-ons. Regional labour rate by crew and by job complexity, fixings and brackets indexed by substrate type, freight modifier by destination, electrical first fix for motorised builds, permits, VAT and import handling. The 60 percent of cost that the manufacturer’s table is missing. Held in BOM-aware blocks, so an installation modifier (“anchor kit for paving slab over sand”) attaches to the parts list, not to a separate line on a quote.

Layer three, the discount and tier engine. Base dealer discount, volume bracket evaluated against the live year-to-date order book, quarterly bonus eligibility, regional surcharge, active campaigns. Applied in a deterministic order on every quote, by every member of staff, with the workings visible on the quote PDF so the manufacturer’s accountant can reconcile in seconds rather than days.

Layer four, the buyer-side option modifiers. Size increments outside the standard grid, motor and automation upgrades, screen add-ons, custom colours, integrated lighting and heating. Each modifier is a rule in the same library, with the compatibility constraints encoded so the configurator never lets a buyer combine an option that the manufacturer cannot ship.

1. 01

   One source of truth

   Every layer above lives in one library. The configurator on the website, the quote that prints on the salesperson's desk, the resolved parts list that lands in production, and the invoice that goes out at the end of the month all read from the same number. If the four artefacts disagree, the disagreement is a bug to fix, not a discrepancy to manage.

2. 02

   BOM-aware blocks

   Pricing rules attach to parts, not to free-text quote lines. A motorised side screen is not a 350-euro adder on a quote, it is a sub-assembly in the bill of materials with its own cost, its own labour minutes, and its own compatibility rules. When the spec changes, the parts list resolves, and the price recomputes from the resolved parts list, every time.

3. 03

   Tier logic in code, not in memory

   The discount, the volume bracket, the regional surcharge, the quarterly bonus, and any active campaign apply in the same order on every quote, with the workings visible on the PDF. The salesperson cannot apply them in the wrong order because the engine applies them, not the salesperson.

4. 04

   Manufacturer price feeds where possible

   When the manufacturer can ship a price feed (XML, JSON, even a versioned CSV), the dealer's base table updates automatically when the manufacturer publishes. When the manufacturer cannot, the dealer maintains a single versioned table that every dealership site, every staff member, and every configurator reads from. No more last-quarter's-number quotes.

5. 05

   Audit trail on every quote

   Every quote PDF carries the version of the rule library that produced it. When the manufacturer raises the base table on the fifteenth, every quote produced before the fifteenth is still defensible, and every quote produced after is on the new number. The reconciliation conversation that used to take a week at month-end becomes a query.

The four layers and the five checks above are what a real pricing rule library looks like in production at a pergola dealer. The technology to build them stopped being the hard part a long time ago. The hard part is admitting that the spreadsheet was the bottleneck, and committing the rules to a structure that the whole team can read.

What changes for the dealer on a Monday morning#

Before, Monday morning is the salesperson reading back through Friday’s contact-form inquiries, calling the buyers, writing the sizes on a notepad, walking the spec to the engineer, the engineer opening the manufacturer’s price list and the discount spreadsheet and the regional modifier table in three separate windows, picking the buyer-side options out of the option matrix, typing the numbers into a quote PDF, and emailing it back to the salesperson three days later. By Thursday, half the inquiries have already signed with the dealer down the road who quoted on Monday afternoon. The pattern is well-trodden in the post on manual quoting errors.

After, Monday morning is the salesperson opening the CRM to a stack of configured quotes the buyers built themselves over the weekend, each one priced against the live rule library, each one carrying a designed PDF that already went out to the buyer, each one with the resolved bill of materials sitting in the ERP ready for the production team to schedule. The salesperson calls the buyers whose configurations look serious. The engineer is not in the loop on standard configurations, because the standard configurations do not need an engineer. The engineer steps in on the genuinely unusual builds, which is where the engineer’s time earns its keep.

The named numbers behind the pattern sit in the case studies for Caribbean Blinds and Nordin. Both teams pulled the same lever: they moved the pricing rules out of the engineer’s spreadsheet and into a library wired to a configurator. The leads got priced before the conversation started, the conversation started where it used to end, and the dealership stopped pricing pergolas on a kitchen table on Sunday evenings.

What the rule library does not solve#

A rule library is a tool. The reason to build one is not because rule libraries sound interesting, it is because the variance between two quotes for the same spec is costing the dealer margin every week. Three honest cases where the work does not pay off, in the same shape as the post on the configurable BOM covers from the parts-list side.

For the dealerships that do not fit any of those three exemptions, which is most of the outdoor living trade, the rule library is the difference between a Sunday-evening spreadsheet and a Monday-morning inbox of priced quotes. The maths is the same maths the engineer was doing by hand. The difference is that the maths is now in the place the configurator can read it, the salesperson can read it, the production team can read it, and the accountant can reconcile it from at month-end without anyone losing a Saturday.

The closest practical first step is not the rule library itself. It is the configurator the rule library has to feed. The pergola configurator gallery covers the live builds that already run on this pattern, with the rule library underneath. The post on the configurable BOM covers the parts-list side of the same data structure, because the pricing engine and the BOM live on the same spine. Build the buyer-facing surface first, wire the rule library in week two, and let the engineer meet the configured spec instead of rewriting it on a Wednesday afternoon.

Pergola dealers do not have a pricing problem in the way the word usually means. They have a plumbing problem. The plumbing is fixable.