# Integrating AWS Marketplace with procurement systems
You can configure procurement software to integrate with AWS Marketplace following the commerce extensible markup language (cXML) protocol. This integration creates an access point into a third party's catalog, known as a *punchout*.
The integration differs slightly, based on the procurement system:
+ **Coupa** – Using the Coupa Open Buy feature, you can search AWS Marketplace from within Coupa. Coupa displays search results, and when the user chooses a product, they're redirected to AWS Marketplace to see the details. Alternatively, users of Coupa's procurement software can access the AWS Marketplace catalog in the **Shop Online** section of their home page. The user can also choose to start directly in AWS Marketplace to browse for products.
+ **SAP Ariba** – Ariba redirects users to AWS Marketplace to search for software and get details about a product. After an administrator configures the punchout integration, users of Ariba's procurement software can find AWS Marketplace software by choosing the **Catalog** tab, and then selecting the AWS Marketplace catalog. This redirects them to AWS Marketplace to find the products they're interested in.
Ariba users must initiate their purchase from within Ariba, not AWS Marketplace.
When the user wants to purchase a subscription that they're browsing in AWS Marketplace, they create a subscription request within AWS Marketplace. On the product's subscription page, instead of completing the purchase, the user requests approval. The request is sent back to a shopping cart in the procurement system to complete the approval process. The following diagram shows the process for a procurement system subscription request.
![\[Flow chart for procurement system subscription request\]](http://docs.aws.amazon.com/marketplace/latest/buyerguide/images/procurement-flow-01.png)
When the procurement system receives the request from AWS Marketplace, the procurement system starts a workflow to complete the approval process. After the request is approved, the procurement system's purchase order system automatically completes the transaction on AWS Marketplace and notifies the user that their subscription is ready to deploy. The requester doesn't need to return to AWS Marketplace to complete the purchase. However, they may want to return to AWS Marketplace for instructions on how to use the product they have purchased. AWS Marketplace sends an email message to the AWS account used to access AWS Marketplace. The email message informs the recipient that the subscription succeeded and the software is available through AWS Marketplace. The following diagram shows the approval process for a procurement system subscription request.
![\[Flowchart for procurement system subscription approval\]](http://docs.aws.amazon.com/marketplace/latest/buyerguide/images/procurement-flow-02.png)
Additional notes about integrating with procurement systems include the following:
+ SaaS products with usage-based pricing let you set a budget estimate for your expected usage. You can submit this estimate through your procurement system for approval. If you choose to get pre-approval, your actual charges will be based on your real usage and billed monthly against the approved purchase order. You will be charged based on your actual usage, regardless of your initial estimate. If your actual usage exceeds your estimated amount, you may need to submit an additional purchase requisition to cover the difference.
+ Free trials don't generate an invoice in the procurement system, because they don't have a charge associated with them.
+ Server annual agreements (including AMI, container, and Helm chart options) involve both ongoing pay-as-you-go charges and a one-time upfront charge, requiring a two-step approval process. First, submit an approval request for the pay-as-you-go agreement, which defaults to \$110,000 (this amount is not invoiced against). After AWS Marketplace receives the PO from this first approval, return to the procurement page to route for a second approval, which will show the total contract value. Once this second approval is complete, you'll have a final contract agreement.
+ Customers with PSI (Procurement System Integrations) can turn on pre-approvals for free products and BYOL products. There are two settings, one each for Free and BYOL. When the setting is enabled, orders are pre-approved in AWS Marketplace, and customers do not need to submit orders to their procurement system for approval. When the setting is disabled, customers will submit approvals via the **Request Approval** button to their procurement system. When the pre-approval setting for Free and BYOL products is disabled, \$10.00 orders are produced in the customer's procurement system. For more information regarding Procurement System Integrations, see [https://aws.amazon.com/marketplace/features/procurementsystem](https://aws.amazon.com/marketplace/features/procurementsystem)
# Configuring AWS Marketplace to integrate with Coupa
The topics in this section explain how to integrate AWS Marketplace with a Coupa procurment system
## Step 1. Set up IAM permissions
To configure the integration between AWS Marketplace and your procurement system, you start the process in AWS Marketplace and complete it in the procurement system. You use the information generated in AWS Marketplace to configure the procurement system punchout. To complete the configuration, the accounts that you use must meet the following requirements:
+ The AWS account used to complete the AWS Marketplace configuration must be the management account and have the IAM permissions defined in the `AWS managed policy: AWSMarketplaceProcurementSystemAdminFullAccess` managed policy.
We recommend that you use IAM managed permissions rather than manually configuring permissions. Using this approach is less prone to human error, and if the permissions change, the managed policy is updated. For more information about configuring and using IAM in AWS Marketplace, see [Security on AWS Marketplace](buyer-security.md) later in this guide.
+ The procurement system account used to complete the configuration must have administration access to set up a contract, supplier, and punchout catalog in the procurement system.
## Step 2. Configure AWS Marketplace to integrate with Coupa
After you have set up your IAM permissions, you are ready to configure AWS Marketplace integration with Coupa. Navigate to **Manage procurement**. In the **Manage procurement systems** pane, enter a name and description for the punchout. You can also switch the integration to test mode so that users can test the integration without creating product subscriptions until you're ready. To configure the AWS Marketplace portion of the integration, complete the following procedure.
**To configure AWS Marketplace for integrating with Coupa**
1. From [AWS Marketplace Manage Procurement Systems](https://aws.amazon.com/marketplace/eprocurement/overview), under **Procurement systems**, choose **Set up Coupa integration**.
1. On the **Manage Coupa integration** page, under **Account information**, enter the name and description of your integration.
**Note**
You might want your invoices in the AWS Billing console to reference the commerce extensible markup language (cXML) purchase order used to subscribe to your software as a service (SaaS) contract product. If so, you can enable the AWS Billing integration using a service-linked role in AWS Marketplace settings.
1. You can turn on or turn off the configuration settings for **Enable redirect** and **Test mode**, and then select **Save** to complete the integration in the AWS Marketplace system.
After you have completed the integration in AWS Marketplace, you must go on to set up the integration in Coupa. You use the information generated on this page to configure the punchout in your Coupa system.
The AWS Marketplace configuration defaults to test mode being enabled. In test mode, subscription requests go to the Coupa backend so you can see the full flow, but a final invoice is not created. This helps you complete the configuration and enable the punchout in a planned manner.
**Note**
You can toggle testing mode on or off, as needed.
Don't forget to turn off testing mode when you're finished with your integration. Otherwise, users in your system will appear to be creating requests, but no software will be purchased.
## Step 3. Configure Coupa
To configure the integration with AWS Marketplace in your Coupa system, copy the information from the **Purchase information** pane of the **Manage Coupa integration** page in AWS Marketplace. Use this information to complete the steps in the following links that guide you through configuring your Coupa procurement system:
+ [Coupa Punchout Setup](https://success.coupa.com/Suppliers/For_Customers/Toolkit/Manage_Catalogs/Punchout_Catalogs/Punchout_Setup)
+ [Configuring a Supplier for cXML Purchase Orders](https://success.coupa.com/Suppliers/For_Customers/Toolkit/Document_Exchange/cXML/Configuring_a_Supplier_for_cXML_Purchase_Orders)
**Note**
For information about UNSPSC codes used by AWS Marketplace, see [UNSPSC codes used by AWS Marketplace](procurement-system-integration.md#procurement-integration-setup-unspsc-codes) .
# Configuring AWS Marketplace to integrate with SAP Ariba
The following topics explain how to configure AWS Marketplace to work with the SAP Ariba procurement system. Configuratiuon enables users to search for and purchase AWS Marketplace software without having to leave SAP Ariba.
## Setting up IAM permissions
The configuration process starts in AWS Marketplace WS Marketplace and finishes in the SAP Ariba. You use the information generated in AWS Marketplace to configure the procurement system punchout. To complete the configuration, the accounts you use must meet the following requirements:
+ The AWS account used to complete the AWS Marketplace configuration must be the management account and have the IAM permissions defined in the `AWS managed policy: AWSMarketplaceProcurementSystemAdminFullAccess` managed policy.
We recommend that you use IAM managed permissions rather than manually configuring permissions. This approach is less prone to human error, and if the permissions change, the managed policy is updated. For more information about configuring and using IAM in AWS Marketplace, see [ Security on AWS Marketplace](https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-security.html) later in this guide.
+ The procurement system account used to complete the configuration must have administration access to set up a contract, supplier, and punchout catalog in the procurement system.
## Step 2. Configure AWS Marketplace to integrate with SAP Ariba
To configure AWS Marketplace to integrate with Ariba, you must work with the AWS Marketplace operations team to create a Level 1 punchout. For more information about SAP Ariba punchout, see [Introduction to SAP Ariba PunchOut](https://community.sap.com/t5/spend-management-blogs-by-sap/introduction-to-sap-ariba-punchout/ba-p/13457634) on the *SAP Community* website.
Gather the following information in preparation for configuring the setup:
+ Your AWS account ID. If your AWS account is part of an AWS organization, then you also need the management account ID.
+ The Ariba network ID (ANID) for your SAP Ariba system.
**To configure AWS Marketplace for integrating with Ariba**
1. From [AWS Marketplace Manage Procurement Systems](https://aws.amazon.com/marketplace/eprocurement/overview), under **Procurement systems**, choose **Set up Ariba integration**.
1. On the **Manage SAP Ariba integration** page, under **Account information**, enter the name and description of your integration, as well as the **SAP Ariba Network ID** (ANID) for your Ariba system.
**Note**
You might want your invoices in the AWS Billing console to reference the cXML purchase order used to subscribe to your SaaS contract product. If so, you can enable the AWS Billing integration using a service-linked role in AWS Marketplace settings.
1. Make sure that **Test mode** is enabled, then select **Save** to save your AWS Marketplace integration settings.
1. [Contact us](https://aws.amazon.com/marketplace/help/contact-us) to start the process of creating your SAP Ariba integration. Include the above information. AWS Marketplace sends you instructions for setting up and testing your Ariba integration.
**Note**
You need to have administrator access to your SAP Ariba system to create the *Supplier Relationship* with AWS Marketplace.
Following the instructions and configuration settings from the AWS Marketplace team, you create the integration in your SAP Ariba test environment, with AWS Marketplace running in *test mode*. In the test environment, subscription requests go to the Ariba backend so you can see the full flow including approvals, without creating a subscription in AWS Marketplace, and no invoice is generated. This approach enables testing the configuration prior to enabling the punchout in production. After your testing is complete and you are ready to move to production, [contact us](https://aws.amazon.com/marketplace/help/contact-us) to set up the account in the production environment.
**Note**
Don't forget to move to production when you're finished with testing your integration. Otherwise, users in your system will believe that they're creating requests, but no software will be purchased.
When your testing is complete, and you have worked with the AWS Marketplace team to turn off test mode, your integration is complete.
For more information about configuring SAP Ariba, see [Introduction to SAP Ariba PunchOut](https://community.sap.com/t5/spend-management-blogs-by-sap/introduction-to-sap-ariba-punchout/ba-p/13457634) on the *SAP Community*.
**Note**
For information about UNSPSC codes, see [UNSPSC codes used by AWS Marketplace](procurement-system-integration.md#procurement-integration-setup-unspsc-codes) .
## UNSPSC codes used by AWS Marketplace
AWS Marketplace uses the following United Nations Standard Products and Services code (UNSPSC) for software listings that are sent back to the procurement cart: 43232701
# Disabling procurement system integration
To disable integration with either Coupa or SAP Ariba, you must remove the punchout integration from within the procurement system. To do this, disable the auto-redirect functionality for AWS Marketplace from within either Coupa or Ariba. This disables the integration, but maintains the settings and allows it to be re-enabled easily.
If you need to completely remove the integration setup on the AWS Marketplace side, you must [contact us](https://aws.amazon.com/marketplace/help/contact-us).