Services

What we actually do

The work behind the three tiers — what gets built, who does which part, and what your side of it costs in time. Prices live on the pricing page.

The short version

A buyer has told you their procurement system needs something — a PunchOut catalogue, electronic invoicing, or both — usually with a date attached. We build the connection that satisfies it, deal with the buyer's technical team on your behalf, and keep it working afterwards.

You provide product data in a spreadsheet and one commercial contact. No developer. Roughly two hours a week during testing, and very little either side of that.

Three services

Each maps to one published tier. Most suppliers arrive needing the first, because that is what their buyer asked for.

Most suppliers start here
PunchOut

PunchOut catalogue integration

Sold as Connect

A working PunchOut catalogue your buyer can shop from.

$199/month what’s included →

What we do

  • Build and host the PunchOut endpoint that speaks to your buyer’s system.
  • Connect it to your existing catalogue, whether that is Shopify, WooCommerce, a custom store, or a product database.
  • Implement buyer-specific pricing so each buyer sees their contract terms.
  • Map your product data to the classification the buyer requires, including UNSPSC coding and unit-of-measure normalisation.

Two to four weeks of build work for a straightforward integration against an existing catalogue site.

See what’s involved
Automation

PO, ASN and invoice automation

Sold as Order Loop

Everything in Connect, plus the documents that follow the order.

$349/month what’s included →

What we do

  • Receive purchase orders from the buyer’s system as cXML and deliver them into your ERP or order system.
  • Generate and transmit advance shipping notices when you dispatch.
  • Produce cXML invoices that reference the correct purchase order and line items, formatted to that buyer’s requirements.
  • Handle the three-way match fields — PO reference, line identifiers, quantities, tax treatment — that determine whether an invoice reconciles.

Three to six weeks of build work, depending on how accessible your order system is.

See what’s involved
Website + Integration

Custom catalogue build

Sold as Full Enablement

For suppliers with no catalogue site to punch out to yet.

From $599/month what’s included →

What we do

  • Consolidate your product data from whatever sources it currently lives in.
  • Structure and classify it, including UNSPSC coding and unit-of-measure normalisation.
  • Build a catalogue site designed for procurement buyers rather than consumers.
  • Implement per-buyer contract pricing.

Four to eight weeks, driven mainly by catalogue size and the condition of the underlying data rather than by the integration itself.

See what’s involved

Who does what

The division of labour is the part suppliers most often get wrong when estimating this internally.

We talk to the buyer Credential exchange, cXML validation, test cycles and go-live approval, directly with their technical team. This consumes more calendar than the build does.
We own the endpoint Hosted, monitored and fixed by us — including when the buyer changes their catalogue rules a year from now.
You own the commercial terms What you sell, at what price, to whom. We implement the pricing you have agreed; we never sit between you and your customer.
You own the product data You supply it and it stays yours. We structure, classify and map it — and if you leave, it goes with you.

By procurement platform

If you already know which system your buyer runs, start here — each page covers that platform's specific requirements and the traps that cost suppliers weeks.

SAP Ariba Your buyer runs SAP Ariba and has told you a PunchOut catalogue is required. Here is exactly what that means technically, what Ariba will ask you for, and where suppliers most often lose weeks. Coupa Your buyer runs Coupa and wants a PunchOut catalogue. Coupa is generally the most straightforward of the major platforms to integrate with — here is what it actually involves and where it still catches suppliers out. Oracle Procurement Oracle is the platform where suppliers most often build the wrong thing — because "Oracle" means two quite different systems, and the punchout requirements are not the same. JAGGAER JAGGAER is strongest in higher education, healthcare and public-sector research buying — sectors with unusually strict contract-compliance expectations. That shapes what it asks of a supplier catalogue.

By what you sell

The same service, but the problem you arrive with is not the same one.

Distributors Your catalogue is large, it changes constantly, and much of the product data was written by someone else. A manufacturer sends a price file in their format, you resell under your own terms, and the description that reaches your customer has passed through two systems that disagree about what a unit is. Manufacturers You may have a handful of enterprise customers, and one of them is large enough that losing it would reshape the year. That account has just told you their procurement platform requires a PunchOut catalogue, with a date attached. E-commerce teams You already have a storefront that works. It converts, it is maintained, and you have opinions about it. Now sales has come back from an enterprise account with a requirement involving cXML, and the question is what it does to your platform.

Still deciding whether to build, buy or outsource?

We wrote a fair comparison of all three — self-serve tooling, a done-for-you provider, and hiring a developer — on cost, time, and who owns the problem when it breaks.

Read the comparison See pricing