Skip to content

Contract Pricing for Dynamics 365 Business Central

Every job and customer price agreement in Business Central with its expiry date, checked each night against replacement cost on the item card; the renewal drafted, the price file change keyed by a person.

Sales & estimatingUpdated Oct 202620 ERPs

See it work on Business Central.

Click through the steps. Fictional data, in Business Central’s terms; the real thing runs on Business Central.

Agreements · expiring and underwater
Illustrative
CustomerAgreementItemsExpiresMargin nowStatus
Harbor Point BuildersMaple St duplex · framing22 linesOct 3117.4%2 lines under floor
Northline DrywallPrice level 3 · boardAll drywallDec 3124.1%Holding
Cedar & Stone FramingLot 14 Birchwood · lumber9 linesOct 2421.8%Expires in 2 days
Granite Peak BuildersRoute 9 warehouse · steel6 linesNov 3014.9%1 line below cost
Bayview DecksComposite · season4 linesOct 1526.0%Expired · still selling
Floor is 20% on lumber. Mike Brennan owns the first three.

Expiring, underwater, or both. Margin from tonight’s replacement cost on the item card.

1 / 4

The problem, as it happens in Business Central.

Contract pricing at a dealer is a price level on the customer card, a job quote with lumber held for seven days, and a spreadsheet of who got what. The expiry is in the quote, the cost is in the item card, and the agreement to hold 2x4s for a builder through the framing lives in an email from March.

When dimensional moves, the yard keeps selling at the agreed number until someone notices on the margin report. When the agreement expires, nobody tells the customer, so the first ticket at the new price is a phone call. The renewal that should have been a conversation becomes an argument.

How it works.

  1. 1

    Every agreement, in one list

    Price levels, job quotes, contract prices and special pricing on the customer card, each with its expiry and the items it covers. Agreements that exist only in email are entered once by your team and tracked from then on.

  2. 2

    Checked against cost each night

    Each agreed price against replacement cost on the item card that night. A line below your margin floor, or below cost, is flagged with the number, not a colour. The rep sees it the next morning.

  3. 3

    What expires, what broke, who hears first

    A list by rep: agreements ending this week, lumber quotes past their hold, lines underwater since the last cost change. The renewal is drafted in the rep’s voice with the new numbers; the rep decides what to offer.

  4. 4

    The change is keyed by a person

    The renewal goes out when the rep sends it. The new price goes into Business Central keyed by your team, or as an import where Business Central takes one. Lunica records the new expiry and starts watching again.

How it connects to Business Central.

Lunica reads the customer card, the item card and open quotes through Business Central’s API, under a user that can only read: price levels, contract and job pricing, quote expiries, and the replacement cost and last receipt cost on every item an agreement covers. Agreements that exist only in email are entered once by your team and watched beside the rest.

Nothing lands in Business Central without a person and nothing is sent on its own. A renewal is a draft until the rep sends it. A new price goes back as a Business Central API call or import where one exists, or keyed by your team from what Lunica prepared; Lunica never changes a price level, a quote or a contract line itself.

What a week looks like.

  • Every agreement with an expiry date and the rep who owns it.
  • Underwater lines found the night cost changes, not at month end.
  • Renewals drafted with the new numbers before the old ones run out.
  • Price changes keyed by a person who saw the margin first.

Questions

Does it change our prices?

No. It finds what needs changing and drafts the renewal. The price file change is keyed by your team.

Does it write to Business Central?

No. It reads price levels, quotes and item cost. What goes back is keyed by a person or imported where Business Central takes a file.

Which cost does it use?

Replacement cost on the item card, or last receipt cost where that is what you run on. Which one is a rule you set, by category if you want.

What about agreements that aren’t in Business Central?

Entered once from the email or the handshake, with items, price and expiry. From then on they are watched like the rest.

Can it reprice a lumber quote?

It drafts the repriced lines at today’s cost under the same markup and shows the difference. The rep decides what to honor and keys the change.

Does the customer get told automatically?

No. The renewal or the notice is a draft in the rep’s name until the rep sends it.

Does it need a server?

Lunica runs on one server inside your network, whether Business Central is in Microsoft’s cloud or on your own server, set up and maintained by Lunica. It reads Dynamics 365 Business Central through Business Central’s API, under a user that can only read. There is no inbound connection from outside your network.

What does Lunica read in Business Central?

The customer card, open items and terms, purchase orders and receipts, the item card, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.

Can it post to Business Central?

Nothing lands in Business Central without a person. What belongs in Business Central goes back as a Business Central API call or import where one exists, or keyed by your team from what Lunica prepared.

What about our documents?

Invoice copies and scans keep living in the attachments on the record. Lunica reads them when a workflow needs one and never writes to them.

The same workflow, on another ERP.

Contract Pricing is written for every system on the list. You’re reading the Business Central version.

See it on your Business Central data.

Thirty minutes. We walk the workflow on Business Central data, then map it to yours.