The mission of the Procurement Team at GitLab is to be a trusted business partner at driving business value through external partnerships.
Exceptions to this are:
If your purchase request is for one of the US or Netherlands entities (GitLab Inc, GitLab Federal LLC, GitLab BV, GitLab IT BV), follow the instructions on the table below.
Unsure if your vendor is new or existing?
Check the section How to Search for a Supplier in Coupa for a detailed guide.
If you would prefer to have assistance setting up a new vendor, please ping us in the #procurement channel - indicate you are requesting new vendor setup support and identify the vendor name. A member of the Procurement Team will respond with next steps.
| <$25K | >$25K | |
|---|---|---|
| New Software | - Create a “New Supplier” form in Coupa - Create a Coupa Requisition |
- Create an issue with the Intake for Software template |
| Software Renewal | - Create a Coupa Requisition | - Create an issue with the Intake for Software template |
| Add on Software | - Create an issue with the Intake for Software template | - Create an issue with the Intake for Software template |
| Subscriptions New Vendor |
- Fill out a “New Supplier” form in Coupa - Create a Coupa Requisition |
- Create a “New Supplier” form in Coupa - Create a Coupa Requisition |
| Subscriptions Existing Vendor |
- Create a Coupa Requisition | Create a Coupa Requisition |
| Field Marketing & Events New Vendor |
- Create a “New Supplier” form in Coupa - Create a Coupa Requisition |
- Create a “New Supplier” form in Coupa - Create a Coupa Requisition |
| Field Marketing & Events Existing Vendor |
- Create a Coupa Requisition | - Create a Coupa Requisition |
| Professional Services Agency/Contractor New Vendor |
- Create an issue with the Intake Form Professional Services template |
- Create an issue with the Intake Form Professional Services template |
| Professional Services Agency/Contractor Existing Vendor |
- Create a "Professional Services Request" form in Coupa - Create a Coupa Requisition |
- Create a "Professional Services Request" form in Coupa - Create a Coupa Requisition |
| PS Partner Team | - Create a "Professional Services Request" form in Coupa - Create a Coupa Requisition |
- Create a "Professional Services Request" form in Coupa - Create a Coupa Requisition |
As we implement Coupa in a phased approach, Purchase Requests for all other GitLab entities will continue to use the existing procurement issues. You can learn more about Coupa in our FAQ Page and checking the Guide Page.
Coupa is available via Okta. To access the platform:
Please note that every month all Coupa access will be reviewed and users who haven't been active in a period of 90 days will have their access removed. (Note that this number may vary depending on the license count for the current month)
If you need to request access again, please reopen your initial Access Request issue and tag the Finance Systems Admins team using @gitlab-com/business-technology/enterprise-apps/financeops in a comment.
If your job function requires you to submit purchase requests in Coupa, follow the below steps:
Individual_Bulk_Access_Request template.Best Practices
Due to the limited number of licenses available for Coupa, it is recommended that each department identify power users responsible for creating purchase requests on the team’s behalf.
Procurement operates with three main goals
Process of measurement in progress.
Response times to initial requests for review <= 2 business days
Administer, maintain, and manage the procurement purchase request issue tracker (daily, ongoing) <= 2 business days
Ensure all contracts have the correct approvals in place before signed = 100%
Ensure all fully executed vendor contracts are posted to ContractWorks = 100%
'Turn-Around' times <= 3 business days
All vendors that GitLab does business with, must legally comply with the Supplier Code of Ethics. When having discussions with your vendor regarding the contract, make them aware of this requirement.
GitLab condemns exploitation of humans through the illegal and degrading practices of human trafficking, slavery, servitude, forced labor, forced marriage, the sale/exploitation of children and adults and debt bondage (“Modern Slavery”). To combat such illegal activities, GitLab has implemented this Modern Slavery and Human Trafficking Compliance Program.
While Modern Slavery can occur in any country and in any market, some regions and sectors present higher likelihood of vioaltions. Geographies with higher incidents of slavery are India, China, Pakistan, Bangladesh, Uzbekistan, Russia, Nigeria, Indonesia and Egypt. Consumer sectors such as food, tobacco and clothing are high risk sectors; but Modern Slavery can occur in many markets.*
(*According to Source: Statista, Walk Free Foundation, https://www.statista.com/chart/4937/modern-slavery-is-a-brutal-reality-worldwide/)
All vendors, providers and entities providing services or products to GitLab (“Vendors”) are expected to comply with GitLab’s Partner Code of Ethics which specifically addresses Modern Slavery laws. Compliance with the Partner Code of Ethics will be included in Vendor contracts and/or purchase orders going forward. Existing Vendor contracts will be updated with the appropriate language upon renewal.
Those entities who are of higher risk or whom GitLab suspects may be in violation of Modern Slavery laws, may be required to complete an audit. Audits may be presented in the form of a questionnaire or may be an onsite visit. Any known or suspected violations will be raised to Legal and/or Compliance. Failure to comply with Modern Slavery laws will result in a termination of the relationship and GitLab retains all rights in law and equity.
Vendors understand and agree that violations of Modern Slavery laws may require mandatory reporting to governing authorities. GitLab has discretion if and how to best consult with Vendors for purposes of Modern Slavery reporting. GitLab is sensitive to and will take into consideration, the relationship and the risk profile of Vendor to ensure that Modern Slavery risks have been appropriately identified, assessed and addressed and that the Vendor is aware of what actions it needs to take.
GitLab will review its Modern Slavery and Human Trafficking Compliance Program on an annual basis or sooner if it is determined there is increased exposure or concerns with overall compliance. The Program may be amended from time to time by GitLab, to ensure compliance with the most current Modern Slavery laws and regulations.
GitLab’s Executive Team reviewed and approves this Modern Slavery and Human Trafficking Compliance Program.
