Write what happens to the order
Requirements written as screens ("a customer form with these fields") invite every vendor to say yes. Requirements written as events ("an order arrives by email, is priced from the customer's contract, reserves stock in the nearest warehouse and waits for credit approval above a limit") show who can actually do it.
Walk one order, one purchase and one month-end close from start to finish, and write each step in the words your team uses.
The edge cases drive the customization
Standard flows work on every platform. Cost and risk sit in the exceptions, so name them explicitly.
- Partial deliveries and back orders.
- Returns against a specific lot or serial number.
- Price changes mid-contract, and who approves them.
- Transactions that cross entities, currencies or tax regions.
- The spreadsheet someone keeps because the current system cannot do something.
Score every line: fits, configure or gap
Ask each vendor to mark every requirement as fits (standard), configure (settings and workflow, no code) or gap (custom development). Gaps are where the budget and the long-term maintenance go, so ask for each one to be described and estimated separately.
Compare the gap lists, not the totals. Two vendors with the same total and different gaps are proposing different systems.
Agree the data before the screens
Add a short data section: your chart of accounts, the product and customer records you will migrate, and the approval rules. In our own projects these are designed and signed off in the blueprint before anything is configured, because changing them later touches everything.