We’re talking to Grainger and they say that Epicor supports Punch Out purchasing. According to this post:
the only path is using ARM. Anyone else doing Punch Out with cXML via ARM or other methods?
Thanks!
3 Likes
What is Punch Out?
2 Likes
12 Likes
https://www.cxml.org/index.html
cXML is very different from most other electronic business protocols. cXML is a streamlined protocol intended for consistent communication of business documents between procurement applications, e-commerce hubs and suppliers.
PunchOut is one of the “messages” used to buy things. The flow transfers the user to the suppliers web site offering a catalog of parts with negotiated pricing. The user fills their cart and checks out. This sets up a transfer back to the user with parts/quantities/pricing to create a PO in their system.
3 Likes
No, that is Super Punch Out
3 Likes
We use ARM’s process for Grainger, Amazon, Fastenal, and McMaster. Grainger provided a resource to help with the process and that made it easy to setup with their help against their test site.
We spoke with Uline who said we did not purchase enough to justify them working with us to set it up.
2 Likes
I have spoken to the Grainger person. It’s possible to download a CSV or XML file of the cart and we may proceed with that approach first. At my last gig, Amazon was pushing us away from EDI to their web services.
I did reach out to SourceDay to see if they supported cXML and they do not. Points to ARM for doing so.
1 Like
I think we made a few edits for Grainger but the default ARM setup for the most part worked in the majority of these integrations. Our team likes them because you cannot upload back into ARM non-catalog part lists.
2 Likes
We also use ARM and have punchouts configured for MSC, McMaster Carr, and Amazon. I’ve reached out to Grainger and am waiting for their team to get back to me.
We’d love to punch-out to Uline, too, if they offer it.
1 Like
We talked to McMaster and Grainger and learned ARM was the way. Grainger has an API but recommends punchout and McMaster punchout-only.
…interested in non-ARM PunchOut options.
Something like:
- Rest Request: outbound PunchOutSetupRequest to vendor.
- Web Control: Redirect or embed to url from setup response (vendor catalog)
- Webhook: Receive PunchOutOrderMessage (cXML vendor cart).
- Parser Function: Parse cXML, extract cart items.
- Creator Function: Create ERP PO Lines
Edit: Here’s a C# reference for config, templating, multi-vendor ideas:
3 Likes
I like it.
1 Like
Pretty sure we do Grainger punchout. @lindsayc am I mistaken?
She said through ARM.
1 Like
Nice but does a function wizard such as @klincecum like it and can we put enough bananas on a stick?
2 Likes
Ah, reading is hard. 
1 Like
Hi @Mark_Wonsil. Let me know, or reach out to Dan Collar from our team, if you want to check out ARM and our punchouts capability.
Cheers,
Mark
1 Like
We use a third party app called Certify but then I had to build a Jitterbit integration to move the PO’s into Epicor. We have also looked into ARM and we would prefer to go in that direction once a bigger budget is available.
Certify can do punchout on pretty much any vendor as far as I know. We currently only use Amazon and McMaster. The only true advantage of Certify that I can think of is unlimited users. They use transaction volume to determine subscription price.
You’ll have to replicate your GL as well as Suppliers although Certify does have a limited API and does allow you to push Suppliers into their system. No Part Master in the API though so you have to replicate Parts manually.
Approval structure in Certify is rather limited while ARM has much greater flexibility. No need to duplicate Master data in ARM as it is integrated with Epicor. ARM also has great A/P features as an add-on.