Business Requirements (sample)

About this sample

For a job application process, I was asked to revise a sample business requirements document. The provided example was a template purporting to be notes from several different meetings.

I left the headings from the template as they were, but edited and formatted the contents of each section.

While the original sample was done in Word, I have recreated it here with Markdown, published by my SSG, Eleventy.

Identifying elements have been scrubbed.

—Sample begins below this horizontal rule—

Table of Contents

Executive summary

Make the ERP the source of record for supplier cost to achieve

  • Better management of the frequent updates for supplier cost.
  • Improvement in the sync between ERP and PIM.


Business objectives

  • Consistent and accurate item setup process, capturing
    • Supplier cost
    • Vendor
    • UOM
  • Identify three preferred vendors per item and display for each:
    • Contract price
    • Contract expiration date
  • Capture comments when a preferred vendor is not used
  • Send cost factor (CF) alerts when CF exceeds
    • List price to customer
    • Sales price to customer



The project supports the accounting process and profitability of our industrial products.



Project scope includes

  • Phase 1.0: Inbound Item Data Requirements (due November 15)
  • Phase 1.5: IT New Development (due November 30)
  • Phase 2.0: Outbound Item Data Requirements (future; TBD)

Phase 1.0 (Inbound item data requirements)

New custom fields (ERP):

  • Vendor Contract Expiration Date
  • Vendor Cost #2
  • Vendor Cost #3
  • Cost Factor (average of landed costs for three priority vendors)

Update List Price formula

  • Cost Factor / (1 – target margin)
  • Round up to nearest 9 cents

Display on the Item Screen:

  • Preferred vendor #1 supplier cost

Shipping and Freight

  • Display Shipping/Freight at the vendor item level

Send Email Notifications when:

  • (Sales price - cost factor) / Sale price < .1
  • Price expiration date < 90 days from current date
  • List price to the customer < cost factor (CF)
  • Sales price to the customer < cost factor (CF)
  • Purchase price > vendor contract price

Phase 1.5 (IT New Development)

  1. Implement new sync process between ERP, PIM, and e-Commerce

    • Create item in PIM

      Required fields:

      • X Number
      • Description
      • UOM (default to Each)
      • Manufacturer P/N
      • Image
  2. After all required fields have data, push item to ERP

  3. Update PIM with info from ERP

    • List Price
    • UOM

    Note: PIM users can no longer modify price or cost.

  4. Sync Item to e-Commerce

Phase 2.0 (Outbound item data requirements)

  • Update cost validation process
    • Add data for multiple vendors (i.e. priority vendor #2 and #3)
  • Expose Shipping/Freight cost on the check-out page for customers
    • Base costs on aggregate weights and dimensions for combined products and box sizes
    • Regional adder
  • Implement new Database (IT) for compiling contracts and contract updates


Functional requirements

Add new ERP fields

  1. Vendor Contract Expiration Date
  2. Cost Factor
  3. Priority Vendor 2
  4. Priority Vendor 3

Sourcing Team

  • Adds Vendor Contract Expiration Date data for vendors 2 and 3

Perform Data Scrubbing

  1. Remove catalog items in PIM
    • Supplier Cost
    • Supplier Vendor
    • Unit of Measure (UOM)
  2. Update records in ERP
    • Clean On Hand items with no price
    • Clean Catalog Items with no vendor
    • Add missing Vendor Contract Expiration Date (obtain from Sourcing)
    • Update Price Expiration Date for vendor and customer (obtain from Sourcing)
  3. Identify processes for ongoing data validation

NetSuite becomes system of record

  • Purchase Price
  • List Price
  • Contract Price

Review data sync between ERP, PIM, and e-Commerce to determine process changes


Personnel requirements

Team Responsibility
Catalog Correct data set and obtain approval
Integration IS Add additional technical fields to NetSuite
Sourcing Apply updated process for updating price data in NetSuite


Reporting and quality assurance

  • New business process
    • Train users on new process
    • Verify users follow new process
  • Publicize updated sync process between solutions


Delivery schedule

Target completion dates:

  • Phase 1.0: November 15th
  • Phase 1.5: November 30th
  • Phase 2.0: TBD


Other requirements




Phase 1.0

  1. No changes to scope of work
  2. Sync between PIM and e-Commerce updates Catalog Items only

Phase 1.5

  1. Update items in ERP
  2. List price syncs from ERP → PIM
  3. Updated pricing pushes to e-Commerce