Integration Summary
Summary of the key steps to integrate with the Rampart Group Purchasing Platform.
1. Single Sign-On Integration
The SSO (Single Sign-On) integration will allow clients to move seamlessly between your platform and the Rampart GPO platform without needing to log in more than once. Once authenticated on either platform, users will be able to navigate back and forth without interruption—creating a unified and secure experience across both systems.1.1. Why do we need it?
This integration is essential for creating a seamless client experience. It reduces login friction, improves overall usability, and positions our platforms as fully connected. We will also need client emails and business names to communicate with contracted vendors and subscribe clients to GPO contracts.1.2. GPO Platform Button
Somewhere in the Partner platform we will need to place a [Partner] Negotiated Pricing button to allow clients to navigate to the GPO Platform.2. Client Communication
A large part of what will make our partnership successful is the ability to communicate savings opportunities to clients. There are two main types of client communications we will need to feature potential savings opportunities:2.1. In-App Notifications
Whenever a client buys something for which we have Negotiated Pricing, we want to notify the client of the potential savings available through In-App Notifications. In-App Notifications are sent to the client in a few specific cases where we detect a purchase for which we have negotiated pricing:- Client writes a Purchase Order (PO)
- Client processes an invoice
- Client swipes a corporate credit card
- Client purchases an item through punch-out or a marketplace.
2.2. Client Emails
Following the same principle as In-App Notifications, whenever a client makes a purchase for which we detect potential savings, we want to let the client know about these savings by sending over an email. Savings Emails are sent to the client in a few specific cases where we detect a purchase for which we have negotiated pricing:- Client writes a Purchase Order (PO)
- Client processes an invoice
- Client swipes a corporate credit card
- Client purchases an item through punch-out or a marketplace.
Savings Analysis Completed
Savings Analysis Completed
This notification is sent when Rampart completes a savings analysis for a client. It typically includes a summary of potential savings opportunities and recommended next steps.
Savings Analysis Completed Follow-up
Savings Analysis Completed Follow-up
This notification is sent to the client when Rampart completes a savings analysis. Follow-up emails are typically sent 2, 5, and 10 days after the initial analysis.
Potential Savings Detected
Potential Savings Detected
This notification alerts clients when the system identifies new potential savings opportunities. It highlights specific areas where cost reduction is possible and provides actionable insights.
Monthly Savings Report
Monthly Savings Report
A regular monthly communication that summarizes savings achieved, ongoing initiatives, and future opportunities. This helps clients track their cost reduction progress over time.
Contract Opt-in Request
Contract Opt-in Request
This notification is sent when a client needs to opt in to a new contract or service. It includes details about the contract terms and instructions for completing the opt-in process.
Contract Opt-in Confirmation
Contract Opt-in Confirmation
A confirmation notification sent when a client successfully opts in to a contract. It confirms the opt-in action and provides information about next steps or implementation timelines.
3. Spend Data Integration (Optional)
Spend Data Integration is the process of programmatically sharing client purchase activity with Rampart via our API integration. This includes records of purchase orders, invoices, corporate card transactions, and marketplace purchases. By integrating this data, Rampart can analyze client spending, match purchases to our negotiated pricing, and automatically identify potential savings opportunities.3.1. What spend data needs to be sent over?
-
For each Purchase Orders & Invoices:
- Vendor name
- Purchase date
- SKU number
- Item name/description
- Unit price
- Quantity purchased
- Unit
-
Credit Card Transactions:
- Vendor name
- Purchase date
- Amount (excluding taxes ideally)
3.2. Why do we need spend data?
By default, Rampart relies on vendor connections and clients manually uploading their purchase documents to perform Savings Analyses. Whenever a Partner provides us that spend data, we can:- Pre-fill Savings Analyses for clients
- Better estimate savings before engaging clients
- Help us improve our savings reporting to clients after they activated GPO contracts