New Requirements Order

Create a Requirements Order

Use this screen (the Create a Requirements Order tile) for a special project that has no FieldPulse or BuilderTrend job behind it — there's nothing to import, so you build the RO by hand.

Being deployed (2026-09-06): the screen was updated ahead of the part that feeds it. Until the matching update is live, the Class list may come up empty, the automatic "class from the job" fill won't happen, and the green panel after a save may show the RO number as blank — the RO itself is still created correctly. Open the Requirements Orders screen to find it, and tell Logistics if you see that.

Header

• Job / Project Name searches as you type: a FieldPulse job number or name, or a QuickBooks job name. Pick the right match from the list. BuilderTrend jobs are not searched here — a BuilderTrend lookup is too slow to sit behind typing, so import those from the RO Inbox instead. If nothing matches, whatever you typed is used as the job name; nothing here checks it against QuickBooks, so check the spelling.
• BOM Name is required. It has to be unique for that job — two ROs cannot share the same job name and BOM name.
• Class is required. It offers only the four classes on the approved list (Administration, Commercial, Residential, Service — maintained on the Settings screen as RO classes). When the job you picked already carries a class, the screen fills it in for you and says where it came from; if it can't tell, the hint says so and you choose. Nothing is guessed silently.
• Required Date can be left blank. Leaving it blank does not make the RO look overdue — a blank date is simply "no date set yet."
• Notes is optional free text.

Lines

Click + Add line for each item on the RO. There's no limit to how many lines you can add.

• Type a SKU and move to the next field — the screen checks it against the item master automatically, and offers matches as you type. If it's found, the description and unit of measure fill in for you.
• If you skip the SKU and just type a description, the line switches itself to Non-Inventory — that's the normal way to put a one-off item or a service line on an order. Typing a SKU on a non-inventory line switches it back to inventory.
• An inventory line must have a SKU. If one doesn't, the screen tells you which line and won't save until you either enter the SKU or set the line to Non-Inventory.
• If a SKU you typed isn't found, the line still saves — it saves as non-inventory instead, keeps the number you typed, and raises an issue on the Issues to Resolve screen for someone to follow up. Nothing is silently dropped.

Click Save RO when you're done. The screen stays where it is and shows a green panel with the new RO number and how many lines it saved, plus Open RO ### to go look at it and + Add another RO to clear the form and key the next one.

Who can use it

Level 2 and above. A Level 3 user cannot open this screen at all.