Skip to content

Resources

The vocabulary procurement and IT argue about.

Six guides to the mechanisms behind supplier connectivity — written for the people who have to specify, approve and operate them, not for a search engine.

No gated downloads · No forms in the way

01Guides

Start with whichever argument you are currently having.

  • PunchOut catalogs

    What the round trip is, where the session boundary sits, and how to choose between PunchOut and a hosted catalog per supplier.

  • Supplier portals

    What a portal solves, what it does not, and the six questions worth asking before choosing one.

  • E-procurement software categories

    Suites, marketplaces and connectivity layers are sold with the same words. How to identify which one your gap needs.

  • Supplier catalog management

    The six fields a catalog has to carry, the six ways the data goes wrong, and the operating model that keeps it current.

  • ERP procurement integration

    The four flows that cross the boundary, and why interface count rather than interface difficulty drives the cost.

  • Procurement approval workflows

    Designing rules people follow, and keeping approval fast enough that nobody routes around it.

02How the guides fit

Where each guide sits in the chain.

The six guides are not a reading list. Each one covers one link of the same chain, and each one settles a specific argument between procurement and IT.

  1. 01The chain

    Decide what kind of product you need

    Suites, marketplaces and connectivity layers are described with the same words.

    The guide that covers it

    E-procurement software — how to compare the categories.

    The argument it settles

    “Should we extend the suite or connect what we have?”

  2. 02Suppliers

    Give suppliers a way in

    A portal is where a supplier maintains data and receives orders — or where nothing happens.

    The guide that covers it

    Supplier portal — what it solves and what it does not.

    The argument it settles

    “We already have a portal. Why is nobody publishing to it?”

  3. 03The chain

    Keep the data true

    The fields a catalog has to carry, and the six ways they go wrong.

    The guide that covers it

    Supplier catalog management — keeping data current at scale.

    The argument it settles

    “Why did a buyer order at last quarter’s price?”

  4. 04The chain

    Present it to buyers

    Hosted assortment or a catalog session — usually a per-supplier decision, not a policy.

    The guide that covers it

    PunchOut catalogs — how the round trip actually works.

    The argument it settles

    “Do we host their catalog, or punch out to it?”

  5. 05The chain

    Approve without being routed around

    Design choices that decide whether the workflow is followed or bypassed.

    The guide that covers it

    Procurement approval workflow — rules people actually follow.

    The argument it settles

    “Why does everyone order first and raise the requisition after?”

  6. 06Your systems

    Cross the boundary

    Four flows, two directions, and a cost driven by interface count.

    The guide that covers it

    ERP procurement integration — point-to-point versus a layer.

    The argument it settles

    “What will the next twenty suppliers cost us to maintain?”

No gated downloads. Each guide is a page on this site, readable without a form.

Next step

Bring your supplier list. We’ll show you the flow.

A working session with our team, using your systems and your supplier mix — not a generic slide deck.

  • 01

    Where your suppliers sit today: connected, semi-connected, or not at all

  • 02

    How each channel would route through Kelqio into your ERP and procurement platform

  • 03

    What connecting the next twenty suppliers would actually involve

Book a demo

Enterprise integration product. No credit card, no self-serve trial — a conversation with someone who knows procurement systems.