SCPro

South Carolina Procurement (SCPRo) is the new online procurement platform system, based on the Ivalua platform, for sourcing competitive solicitations, contracting, supplier management and procurement activities for the state of South Carolina. Once fully implemented, it will be available to all agencies, suppliers and other government entities through the state’s South Carolina Enterprise Information System (SCEIS). 

The state is implementing SCPro to improve the state end-user and supplier purchasing and contracting experience. SCPro will:  

• Reduce complexities and paper-based and manual processes  
• Improve contract search/approval capabilities and collaboration functionality.  
• Offer improved integration for various purchasing activities that will strengthen productivity.  

 
The SCPro solution will integrate the state’s procurement technology ecosystem, create a public interface for suppliers and enable more effective state spending reports. 
 

SCPro will launch in two phases. 

Release 1 will include Supplier Management, Sourcing and Contracting functionalities for all agencies. This will go live on November 9, 2026.  

Release 2  will include Request to Order, Inventory and Plant Maintenance functionality for all agencies. This will go live in Fall 2027. 

All agencies and suppliers who use the state of South Carolina’s procurement system now or plan to in the future. This includes state agencies procuring goods and services and suppliers providing goods and services.  

Ivalua is the cloud-based software platform the state will use for eProcurement. Ivalua allows users to manage the entire procurement process in an integrated solution, from registration and onboarding of suppliers, proposal creation, evaluation, awarding and contract creation and maintenance. Ivalua connects data to optimize reporting, maximize efficiencies and simplify workflows. For the state, all finance process will remain in ECC.

South Carolina’s Ivalua solution is called SCPro.

 Yes, SCPro will replace the state’s current Supplier Relationship Management (SRM) system. SCPro is a technology solution that will help standardize procurement processes and the online shopping experience with catalog items linked to state contracts. The system has a robust rules engine with built-in compliance for purchasing and enhanced spend analytics capabilities. You will receive more information and how to prepare for any changes as we move forward with this implementation project.

Requests should be submitted from the agency’s data owner through of SCEIS GRC request as they do today. 

Yes, SFAA and Admin will use the train-the-trainer (TTT) approach. The Release 1 SCPro Train-the-Trainer program will began in September 2026 for Release 1. The training focused on developing internal training experts who can teach others in their agency.

These training experts will provide End user training scheduled for October 2026 for those agencies that do not have a TTT representative. 

The process for requesting user roles will not change in the SCPro system, Data Owners will continue to use MySCEmployee for role provisioning. 

While SCPro training is recommended and strongly encouraged, it is not required to receive a user role in SCPro. 

Yes. Finance users who are assigned an SCPro role will be included in the agency-specific user information provided to trainers. Their required training will be based on the roles and responsibilities assigned to them in SCPro.If the finance user is not currently assigned roles in SRM they will not be auto assigned roles in SCPro. 

SCPro Users will have self-service accesses to quick reference guides and additional training and support materials through MySCEmployee.

Users will have access to 68 step-by-step quick reference guides (QRGs) developed for SCPro Release 1. These guides provide clear system instructions, supported by screenshots and other visual references, to help users complete key tasks. The current library includes:

Source-to-contract (S2C) QRGs

Supplier Management (SM) QRGs

SFAA and DEA are currently working through these steps and will provide information as soon as possible.

SFAA and DEA are currently working through these steps and will provide information as soon as possible.

After Release 1 Go Live, agencies will utilize SRM for shopping carts, purchase orders and contract administration on previously awarded contracts.

For Release 1, no documents will be migrated.

SCPro will integrate with South Carolina Business Opportunities (SCBO) to automate the advertisement process. Users will no longer need to submit SCBO advertisements separately. SCPro will send email notifications to suppliers who are registered in SCPro under the same commodity code used on the solicitation. The Currently logins for SCBO will still be used to place ads for construction and for higher ed/local government.

POs are still created and managed in the SCEIS Supplier Relationship Management (SRM) module. There are also no changes to inventory or plant maintenance processes in Release 1. The only impact will occur during the freeze period where new suppliers cannot be created or existing records cannot be changed.

There are no changes to the purchase order (PO) process until fall of 2027. The full details for freeze periods and guidance for R2 has not been finalized yet but will be communicated when it is. POs will still be created and managed in the SCEIS Supplier Relationship Management(SRM) module. There are no changes to inventory or plant maintenance process in Release 1.  

Yes. Statewide verses agency contracts will be identified by a flag in the catalog.

DocuSign will not be included in SCPro.

Yes, if the contract was awarded in SCPro, users will need to access the contract in SCPro or the SCPro public contract search to access the contract unit pricing. Training on this process will be developed by the SCPro/DEA teams and be provided to agencies for their use. 

New contracts awarded in SCPro after Release 1 Go Live will be replicated into SRM as product category contracts. These contracts will still have the target value at the line-item level in SRM which will be used to prevent “overspending” on these contracts. The description, unit of measure, and unit price will be included on the purchase order. The purchase order data will be used to track the actual spend.

SCPro will accommodate the same PO document types as SRM.

SCPro identifies Purchase Options 1 and 2 which correlate to the current PO doc types in SRM. These options will drive the behavior of the system in order ensure compliance with the SC Consolidated Procurement Code. For example, selecting the options for a Sole Source PO will require the attachment of a written determination and the value of the requisition will then drive the workflow to an advertisement if required. 

Yes, approvers can assign substitute approvers during work absences.  

Non-SCEIS agencies will continue to use their own procurement systems to issue PO’s.  
SCPro’s Wave Three implementation will provide the opportunity for Higher education institutions, Political subdivisions, and Local governments to use SCPro.

Attachments to contracts will be migrated from SRM to SCPro. Access to SRM will remain available for a period of time after going live with Release 2.

SFAA does not require any specific document retention forms for agencies.  Procurement audits encompass a three-year period. Agencies are expected to provide documentation for procurements when requested by the audit staff.  It is the agency’s choice to either download data from SRM and store it offline or to utilize the SRM/SCEIS data archiving strategy for document retention.

Records will be maintained according to the retention schedules established by the Department of Archives & History.  The Records Retention Schedules are as follows:
12-726 – Purchase Order/Requisition – Retain for 3 years
12-728 – Emergency Purchases – Retain for 3 years
12-703 – Sole Source Purchases – Retain for 3 years
12-304 – Contracts – Retain for 3 years after the expiration or cancellation of the contract. Long-term access to these records may include viewing them outside of SRM.

If a requisitioner has access to multiple sites, they will need to select the appropriate site on the requisition. If the requisition lists Site A, then the workflow will follow the approval table for Site A. If the requisition lists Site B, then the workflow will follow the approval table for Site B.

For example, the requisitioner is an administrative assistant (Ann) in IT but has security roles authorizing her to enter requisitions for 3 sites – IT (Ivan is the Approver), HR (Harold is the Approver) and General Counsel (Greg is the approver). When Ann enters a requisition and lists the site as HR, that requisition will workflow to Harold. When Ann enters a different requisition and lists the site as General Counsel, that requisition will workflow to Greg.

The Procurement Office makes the change. The requisition will workflow back to the original approvers if the change increases the total value of the PO by more than 10%. 

Since there will be a single product category line in SRM for contracts awarded in SCPro, the line-item release value and the header release value will be the same. 

For R1, the value will be checked at the line-item level within SRM.  Purchase Orders which exceed this value will receive a hard stop.  After Release 2, the value will be checked at the header level within SCPro.    

Users with correct scope that is associated with the requisition will be able to see the documents throughout the process regardless of value. This applies to R2.

The requestor can enter an account assignment of “Unknown” The requisition will then workflow to a designated FI Approver to enter the account assignment information. Where there is not an FI approver, SCPro will require the Agency Buyer to update the account assignment type before they can proceed past buyer approval. If the requestor enters the account assignment information, the FI approval workflow will not be initiated. This applies to R2,.

Yes, approvers can assign substitute approvers during work absences.

Yes, a requestor can be assigned to more than one site. 

ZMRBR reporting would still be able to be run in ECC the same way it runs today. 

Yes, a site can have multiple delivery addresses.

The system sends an e-mail notification to the requestor indicating their requisition has been ordered. This notification does not include an attachment/hard copy of the purchase order (PO). However, any SCPro user can log into the SCPro system and view the PO if needed.

Currently, the system is designed to send the PO to the supplier contact. The Buyer may elect to not send an electronic copy of the PO to the supplier. Additional distribution required by the agency will need to be handled manually outside the system. 

These requisition types will NOT be routed to SFAA but will remain at the agency level to issue the PO.