How an integration actually runs
We'll tell you what the next four weeks look like before you sign — including the parts that go wrong.
Week 1 — Discovery
- We confirm which procurement system your buyer uses and which document types they require.
- We review your catalogue structure and flag anything that will block validation.
- You get a written scope with a fixed price before any work starts.
Weeks 2–3 — Build and internal testing
- We build the PunchOut endpoint and cart return, and map your catalogue fields.
- We test against our own validator before involving your buyer.
- You see a working demo before your buyer does.
Week 3–4 — Buyer testing and go-live
- We coordinate directly with your buyer's procurement or IT contact.
- We run their test cycle, fix what they find, and re-submit.
- Go-live happens once your buyer signs off, not before.
What we need from you
- A named contact who can answer catalogue questions within a day or two.
- An introduction to your buyer's technical contact.
- Access to your ecommerce platform's admin or API credentials.
That is genuinely it. You do not need procurement integration expertise in-house.
When buyer testing fails
Buyer validation can reject a submission on the first pass. Causes include a catalogue field the buyer validates more strictly than their documentation implies, or a UNSPSC classification mismatch. Fixes for anything within the agreed scope are included; we don't bill you for iterations of our own work. If your buyer changes their requirements mid-implementation, we'll tell you before doing the work and quote it separately.
Timelines we won't promise
We won't quote you a guaranteed go-live date, because the buyer's testing queue isn't ours to control. A buyer's turnaround on a resubmission can be a couple of days or a few weeks, and that variance is on their side, not ours.
Questions about your specific setup? Email hello@quickpunchout.com.