// Building products distributors · Builder POs by lot
Every builder PO for a start, checked against the house package and that lot's options.
When a production builder starts a house, its system sends your yard a purchase order for that lot: community, lot and plan, often elevation and option codes, and a price on every line. Variance and extra POs follow when something changes. Someone on your builder desk reads each one against the agreed house package and price list before the first load ships. In a free AI proof of concept, AI does that check again on copies of 20 to 30 lots your team already shipped: every PO line matched to the package, the lot's options and the agreed price, and every line that doesn't match listed for the person who confirms the order. Your reviewer, the person who knows your builder accounts best, sets that list beside what your desk caught at the time.
- Lots tested
- 20 to 30, already shipped
- POs confirmed by AI
- None
- Before any PO moves
- An NDA
// The one job
From a builder's PO to a list of lines that don't match
The PO reaches you through the builder's portal or as a PDF, one per start, sometimes split by delivery. It names the community, lot and plan, prices each line from the builder's own records, and carries codes for the options the buyer picked. Later paper lands on the same lot: a variance PO when a superintendent adds material, a revised PO when an option changes after the start. Your desk confirms the order, sends it back, or calls the builder's purchasing team.
For the test, AI reads copies of those POs beside the house package your team agreed for each plan and the price agreement in force, and drafts a check sheet for every lot: each PO line matched to a package line with item, quantity, unit and price compared, each package line the PO left out, and each variance PO tied back to the lot and line it changes. Nothing is confirmed, rejected or sent. Your reviewer compares the sheet with what your desk flagged when those lots shipped, and with any rebill or credit that came later.
line by line
// The hard parts
Why a builder's PO and your house package drift apart
The PO comes from the builder's takeoff, not yours. Oracle's guide to JD Edwards EnterpriseOne Homebuilder Management, one ERP production builders run, describes a Lot Start process that turns bids and takeoffs into lot-specific purchase orders. Bid details are kept by area, community, phase, plan, elevation and option, and the process looks for an exact match on those fields before falling back to less specific records. Takeoffs work differently: when several takeoff records match a lot, their quantities are added together. So a PO can be wrong where your package is right, with a quantity counted twice or a price taken from a general record. The draft compares each PO with your package for the same plan, elevation and options, and names the field that differs.
The price is set at the start. Smith Douglas Homes, in its annual report for 2025, says material prices for a home move until construction begins and are then locked in by purchase orders. Oracle's guide gives each bid an effective date and a cancel date, and has Lot Start compare them with the lot's commitment start date. ICI Homes' published PO terms, effective September 15, 2025, call the price on its purchase order a ceiling that can't rise without the builder's written approval in advance. A line priced under your agreement is a loss once the load ships, unless someone catches it first. The draft checks every line against the agreement in force on the date your success criteria name, usually the start, and lists lines priced from an expired list or one not yet in effect.
Changes arrive on separate paper. The same ICI Homes terms show authorized changes separately on a Variance Purchase Order or Change Order, and make the purchase order the seller's invoice once the job is complete. Oracle calls extra purchase orders field purchase orders, because they start at the construction site, and uses them for lots only. Smith Douglas says the system behind its paperless POs, which lets trade partners check their job schedules and orders online, helps it avoid variance orders. A variance PO filed to the wrong lot leaves two lots wrong. The draft ties every variance or extra PO to its lot, its original PO and the line it changes, and lists any it can't place.
The agreement may be national while the PO is local. D.R. Horton's annual report for fiscal 2025 lists negotiating national purchasing contracts among its corporate functions, while most of its direct homebuilding runs through local divisions. Smith Douglas says it sets national specifications with its distributors and has distribution agreements for lumber among other supplies. The price a division's PO should carry can sit in an agreement written somewhere else, with its own item names. The draft keys each PO line to whichever agreement, price exhibit or list you send, and marks any item the agreement doesn't name.
Who bought it on the lot matters later. Oracle's guide separates turnkey bids, where a subcontractor buys labor and materials, from takeoffs, where the builder buys and delivers the material itself, so your customer on a lot may be the builder or a framer. Notice rules can turn on that. Washington's lien statute, for one, says that on new construction of a single-family residence a notice of the right to claim a lien may be given at any time but protects only materials supplied from ten days before it, where the general rule reaches back sixty days. The draft keeps each lot's address and customer of record beside its POs; whether a notice is due is for your credit manager and counsel, and this is not legal advice. Your reviewer, usually the builder account manager or order desk lead, watches option codes, doubled lines, stale prices and stray variance POs.
// What you send
What the test needs from your builder desk
20 to 30 lots you shipped
For each lot, the builder's PO as it arrived, every variance or extra PO against it, your confirmation or sales order, and the delivery tickets. Include a lot whose options changed after the start and one your desk sent back.
Packages and price agreements
The house package your team agreed for each plan, elevation and option, and the price list, builder agreement or pricing exhibit in force when each of those lots started.
What your desk caught
Emails to the builder's purchasing team, revised POs you asked for, and the rebills and credits on those lots. That record is the answer key the draft is graded against.
NDA before any agreement
Builder agreements and price lists are confidential, so the NDA is signed before a file moves. We never sign in to a builder's portal or your ERP. If POs can't leave, your reviewer helps us build look-alike lots with the same problems in them.
// Before it starts
Settled before the first PO moves
A PO that is short one bundle may not be worth a call, so the owner decides what counts as a mismatch before anything is graded.
- Your reviewer
- Named by the owner, often the builder account manager or order desk lead
- Mismatch rule
- Which differences count: item, quantity, unit, price or a missing line
- Price date
- Which list applies to a lot: its start date, the PO date or the ship date
- Success criteria
- Written and agreed, for matched lines, missed lines and variance POs
- Sample
- Picked by your reviewer, option changes and returned POs included
- Price
- A range for running builder POs live
- NDA
- Signed before any PO or builder agreement is shared
// How it's judged
Each check sheet beside what your desk caught
| On the same 20 to 30 lots | What your desk did | The AI draft |
|---|---|---|
| Each PO matched to its community, lot, plan and elevation | Checked on your lots | Checked on your lots |
| Every PO line matched to a house package line | Checked on your lots | Checked on your lots |
| Option codes on the PO against that lot's options | Checked on your lots | Checked on your lots |
| Item, quantity and unit on every line | Checked on your lots | Checked on your lots |
| Price against the agreement in force for that lot | Checked on your lots | Checked on your lots |
| Variance and extra POs tied to the lot and line they change | Checked on your lots | Checked on your lots |
| Package lines the PO left out | Checked on your lots | Checked on your lots |
| Lines listed for your desk, and why | Checked on your lots | Checked on your lots |
// After a yes
About 30 days on new starts
Once your reviewer says yes against the success criteria, the same check runs on new builder POs and variance POs for about 30 days.
Each check sheet goes to the person who confirms builder orders, and only they accept a PO, send it back or call the builder. Nothing loads on the strength of a draft.
The live run has a fixed price agreed before you sign, and a next job is priced by itself.
// What could come next
Possible next jobs, ranked
- 01Next
Delivery tickets against the PO
What loaded on each truck compared with the PO lines for that delivery, with shorts and substitutions listed before the invoice goes out.
- 02Then
Trim and door packages
The millwork for each start drafted from the plan's door schedule, so the builder's trim PO has a package to be checked against.
- 03After that
Rebills and credits
Rebills and credit requests drafted for lines a builder disputes, with the PO, ticket and agreement attached for your desk to review and send.
// One hard limit
It never confirms, prices or returns a builder's PO.
The draft lists what differs; a person on your desk decides whether to accept the PO, ask for a revision or call the builder. During the test nothing reaches a builder, a superintendent or a builder portal, no material is ordered or loaded, and every file is a copy. Lien notices and other legal deadlines stay with your credit team and counsel, and nothing here is legal advice.
Builder POs are priced as their own job: a range before the proof of concept, then a fixed figure before you sign.
The range depends on how many starts your builders release in a month, how many plans and option codes they carry, and how many builders send POs through a portal rather than by email.
// Questions
Questions from builder desks
Do you log in to the builder's portal?
Our house packages live in the estimating program. Is that a problem?
What if the builder's PO is right and our package is wrong?
Will it tell us when to send a lien notice?
Who should our reviewer be?

Rob Eason, founder
// Book a call with Rob
Bring one lot with a variance PO on it.
Thirty minutes with Rob. Have three answers ready: your company and role, the job you'd test, and about how many builder starts reach your desk in a month. POs and price agreements stay with you until the NDA is signed.
- Co-owned a 60-employee financial services firm and sold his share to his partner.
- Ran GOSO Technologies, a Boston solar company rated 5/5 across 24 Google reviews.
- 5/5 across 83 reviews in HighLevel's Certified Admin Directory.
- 4.3/5 from 6 Google reviews of Massmarket AI.
- Every directory and Google review, critical ones included, is shown word for word at massmarket.ai/reviews.
- Takes every proof-of-concept call himself.
