PartGrid.ai

Dealer price control

Set dealer-specific prices without copying your catalog.

PartGrid layers dealer pricing on top of your source and collection prices. Target all parts or a part group, preview the result, and keep every displayed price explainable.

Reusable rules per dealer collection
Part-group targeting and priorities
Manual overrides with price-path context

Resolved dealer price

How one catalog price becomes a dealer price

Catalog price

€100.00

Collection rule

+5% → €105.00

Dealer rule

+12% → €117.60

Price ending

Round to .99 → €117.99

Displayed price

€117.99

Price source

Dealer rule • Benelux collection

Dealer parts preview

PG-1042

Hydraulic seal

€117.99

Dealer rule

PG-2088

Drive belt

€49.00

Manual override

PG-3106

Filter kit

€82.95

Collection rule

Why spreadsheets break down

One dealer network should not require dozens of copied price lists.

Dealer margins, regional agreements, campaign periods, and product-line exceptions quickly make copied catalogs difficult to maintain. PartGrid keeps the source catalog intact and applies pricing in the dealer context where it is needed.

Catalog copies drift

Separate dealer files fall out of sync with current parts, descriptions, and base prices.

Broad markups miss exceptions

A single percentage across the full catalog cannot protect minimums or handle selected product lines.

Teams cannot explain a price

When formulas live in spreadsheets, support and sales teams struggle to trace the displayed result.

Temporary agreements become permanent

Campaign and seasonal prices remain active when start and end dates are managed manually.

Pricing workflow

Build the rule once, attach it where it belongs.

Dealer pricing rules are assigned to a dealer collection, so pricing stays connected to the catalog relationship, audience, and parts it is meant for.

1

Choose the dealer collection

Work inside the specific dealer relationship instead of changing pricing globally.

2

Select the target

Apply the rule to all parts or to an OEM-owned part group for more precise control.

3

Configure calculation and timing

Set formula steps, priority, active state, and optional start and end dates.

4

Preview and verify

Review matching parts and resolved prices before relying on the rule in dealer workflows.

Rule configuration

Benelux service dealers

Target

Wear parts group

Priority

20 • evaluated first

Active window

1 Sep – 31 Dec

Formula

+12% • minimum €25 • end in .99

Preview

428 matching parts

Supported calculations

Combine practical pricing steps.

Rules can use multiple validated formula steps, so teams can model common dealer adjustments without hiding the calculation in a spreadsheet.

Percentage markup

Increase the incoming price by a configured percentage.

Percentage discount

Reduce the incoming price by a configured percentage.

Fixed addition

Add a fixed amount in the resolved currency.

Fixed subtraction

Subtract a fixed amount from the incoming price.

Minimum price

Prevent the calculated result from falling below a floor.

Maximum price

Cap the calculated result where an upper limit is required.

Rounding and price endings

Round normally or apply a commercial ending such as .99.

Layered price resolution

Keep source pricing, dealer logic, and exceptions separate.

PartGrid resolves a dealer price in clear layers. Each layer has a defined role, so teams do not need to overwrite the original catalog price to support a dealer agreement.

A price your team can defend.

Dealer-facing workspaces can show whether a price came from the catalog, currency conversion, a collection rule, a dealer rule, or a manual override.

Catalog price

Start with the catalog price in the requested currency, or a converted price when conversion is allowed.

Collection rule

Apply an OEM or source-collection adjustment before dealer-specific logic.

Dealer rule

Use the first active matching rule according to priority and rule order.

Manual override

Replace the calculated result for one dealer collection, part, and currency when an exception is needed.

Explanation path

Return the price source and calculation path alongside the resolved value.

Granular control

Cover common dealer agreements without turning pricing into a black box.

Use targeted rules for repeatable logic and explicit overrides for the small number of parts that need special treatment.

Part-group targeting

Limit a rule to a reusable subset such as wear parts, filters, or a selected product family.

Priorities and first-match behavior

Control which valid rule wins when more than one rule could apply.

Date windows and active states

Prepare a rule in advance and restrict it to the period in which it should be used.

Per-part manual overrides

Set one explicit dealer price without changing the rule or the source catalog.

Common use cases

Adapt one catalog to different dealer commercial models.

The same source parts can support regional, channel, and dealer-specific pricing while remaining part of one governed catalog.

Regional dealer margin

Apply a consistent markup for a dealer collection serving one market.

Campaign-period pricing

Schedule a temporary discount or markup for a defined sales period.

Minimum-price protection

Keep discounted or converted prices above a required floor.

Consistent price endings

Present calculated prices with a commercial ending such as .99.

Product-line discounts

Target a part group instead of discounting the entire catalog.

One-off dealer exceptions

Override a single part and currency while leaving the broader rule intact.

Fits your pricing stack

Practical dealer price control, not a replacement for your ERP.

PartGrid is designed to control the price resolved inside dealer catalog experiences. It can sit alongside the systems that own master data, contracts, tax, and finance.

Explore dealer workspaces

Keep master product and base-price data in the systems that already own it.

Use PartGrid to resolve the price shown inside dealer collections and parts workspaces.

Connect the resulting catalog experience to commerce, quote, or support workflows.

Frequently asked questions

What teams usually want to know before rollout.

Dealer pricing should be flexible enough for real commercial agreements and clear enough for operations teams to trust.

Can prices differ per dealer?+
Yes. Rules are attached to a dealer collection, so separate dealer relationships can resolve prices differently without duplicating the source parts catalog.
Can a rule target only part of the catalog?+
Yes. A dealer rule can apply to all parts or target an OEM-owned part group, where configured.
What happens when multiple rules match?+
PartGrid evaluates active rules in priority order and applies the first valid match. Rule order is used when priorities are equal.
Can dealer prices be scheduled?+
Yes. Rules can have optional start and end dates in addition to an active or inactive state.
Can one part have a manual dealer price?+
Yes. A manual override can replace the calculated result for a specific dealer collection, part, and currency.
Can teams preview the result?+
The pricing workflow supports rule previews and resolved-price context so teams can verify the target and calculation before operational use.
Does PartGrid calculate tax or replace contract pricing?+
No. This capability should be used as a dealer catalog pricing layer alongside ERP, contract, tax, and finance systems where those processes are managed.

Make dealer pricing easier to manage and easier to explain.

See how PartGrid can apply reusable dealer rules, targeted part-group pricing, and explicit exceptions across your dealer catalog workflows.

Dealer Pricing Rules for Parts Catalogs | PartGrid