OregonBuys project information

Phase 1 - ORPIN Replacement key dates

  • June 16, 2021: ORPIN switches to read-only status.

  • June 16 - 30, 2021: ORPIN is in a blackout period. Processing documents is on hold as ORPIN is in read-only status and OregonBuys prepares for launch.

  • July 1, 2021: ORPIN is replaced with OregonBuys.

Click here for guidanceon how to manage procurement documents that are in process during the key dates listed above.

Agency Frequently Asked Questions 

The ​OregonBuys system will not function on Internet Explorer. Please use any other browser when accessing the system. Click this link to check which browser you're using:

​Small Procurements are not in scope for Phase 1. This functionality will be added in Phase 2.

​Reverse auction functionality isn't in the project scope. We'll consider adding it as a future enhancement. 

​Internal agency requests are in scope for Phase 2, not Phase 1. This functionality will include scenarios such as receiving a request from an internal purchaser who asks for permission to buy a specific commodity outside a unique agency rule which may exist.

​Yes, OregonBuys has a column for referencing ORPIN documents numbers on Bid Solicitations and Master Blanket Purchase Order documents (price agreement/contract document).

DAS ​CSR’s will be implemented in Phase 2. They are not in scope for Phase 1.

​Yes, state agencies and government entities will need to register for a vendor account in OregonBuys to participate in an ORS 190.
​No, the Project Steering Committee voted to not allow encumbering in OregonBuys. This decision will be revisited when the batch interface to R*STARS is potentially replaced with real-time integration.
​Yes, OregonBuys has functionality that supports BVA.

We're currently having conversations with the Buy Decision programs to see what we can do to facilitate the process in OregonBuys.

DOJ and OSCIO approvals are not currently in the project scope for OregonBuys. We'll continue to review this to see if it makes sense to include in the future.

We're actively working with OSCIO to provide direction to agencies on this topic.

Come to an OregonBuys monthly forum to see a demo of the system and get answers to questions. Click here to view a schedule of the upcoming forum sessions.

​The OregonBuys eProcurement system is fully funded by an additional 1% Vendor Collected Administrative Fee (VCAF) collected on DAS statewide price agreements. 

These VCAF costs are shared by state agencies, Oregon Cooperative Procurement Program (OrCPP) members, and vendors. The 1% fee covers deployment and use of this eProcurement tool across all state agencies. Costs integrating with any agency specific procurement or payment systems besides R*STARS and TEAMS will need to be self funded by the affected agency.

The OregonBuys eProcurement solution offers a contract administration module with robust functionality, including digital signatures. However, the contract administration module isn't included in the current project scope. We will consider adding it as a possible future enhancement.

​No. Conferences and conference trainings are not competitively sourced and won't be entered in OregonBuys.

​Generally, paying to attend training isn't considered a Procurement and won't be entered in OregonBuys.

However, if a training is solicited for, and a contract awarded, then the vendor would be paid through OregonBuys.

​If the travel is booked using a statewide (or agency specific) Price Agreement it is Procurement and needs to be paid through OregonBuys.

If booked directly with hotels or venues without any competition, it is not Procurement and doesn't need to be paid through OregonBuys.

The following SPOTS card purchases will be processed in OregonBuys:

  • Purchases from Price Agreements. 
  • Small Procurements (under $10,000 Direct Award that don’t require competition). 

SPOTS payments for utilities and non-goods and services will not be processed through OregonBuys.