Online Purchasing & System Integration with Guillevin
Looking to connect your systems with Guillevin?
Whether you want to purchase online, keep approvals in your purchasing platform, access Guillevin data in your software, or exchange business documents between systems, Guillevin offers different ways to work with your business. The right option depends on your purchasing process and the information you need to exchange. You can use one channel or combine solutions for example, shopping through PunchOut while exchanging invoices through EDI.
For this page, “ERP” refers to your business management system.
Not sure which option fits your business?
Tell us how you purchase today and what you would like to connect or automate. Our team will help you identify the appropriate approach.
WEBSITE - Purchase directly online
Ready to purchase online?
PUNCHOUT - Shop through your purchasing platform
Want to connect your purchasing platform?
CUSTOMER API - Connect Guillevin data to your software
Want Guillevin data in your software?
EDI - Automate business-document exchanges
Want to automate your document exchanges?
Frequently Asked Questions
Which option should my business choose?
Which option should my business choose?
Choose Guillevin.com to shop directly online, PunchOut to shop through your purchasing platform, customer APIs to connect your software, and EDI to exchange business documents. If you are unsure, our team can review your purchasing process with you.
Do I need an ERP integration to order on Guillevin.com?
Do I need an ERP integration to order on Guillevin.com?
No. You can shop directly on Guillevin.com without starting in an ERP or procurement platform. Sign in to access the information and purchasing capabilities available to your account.
What is the difference between PunchOut, a customer API, and EDI?
What is the difference between PunchOut, a customer API, and EDI?
PunchOut connects the shopping journey to your purchasing platform. A customer API lets your software retrieve information or submit orders through the applicable API. EDI exchanges agreed business documents between systems.
Can we keep our internal approvals with PunchOut?
Can we keep our internal approvals with PunchOut?
Yes. Your cart returns to your company’s system so your organization can continue its requisition, approval, cost-coding, and purchasing processes. The method for sending the approved purchase order is confirmed during onboarding.
Can Guillevin connect to our existing platform?
Can Guillevin connect to our existing platform?
The approach must be assessed with your business and technical contacts. Share your platform, purchasing process, and intended exchanges so Guillevin can confirm the scope and requirements.
Which information is available through the customer API?
Which information is available through the customer API?
The product API provides product information, customer pricing, and inventory for products available at your Guillevin branch. Your required information is confirmed when defining the integration.
Does product API access include order submission?
Does product API access include order submission?
No. Creating and submitting orders requires a separate order API, included in the agreed solution. The two capabilities must be scoped accordingly.
Which documents can we exchange through EDI?
Which documents can we exchange through EDI?
The agreed solution may include purchase orders, purchase-order acknowledgements, advance ship notices, invoices, and functional acknowledgements. The document flows are confirmed for your implementation.
Can we combine different options?
Can we combine different options?
Yes. Your organization can use more than one channel. For example, employees may shop through PunchOut while invoices are exchanged through EDI.
Who should be involved, and how do we get started?
Who should be involved, and how do we get started?
Start with your purchasing or business lead. For integrations, involve your IT team, ERP provider, or integration partner. Contact Guillevin with your objectives, current systems, and required exchanges so we can discuss scope, responsibilities, testing, and launch.


















